Adsl lichtje blijft knipperen!

Zit je met opmerkingen en een paar vragen over dommel / schedom? Post ze dan hier maar.
Plaats reactie
ubremoved_10624
Member
Member
Berichten: 54
Lid geworden op: 02 okt 2008, 17:36

Hallo ik heb sinds 2 dagen het probleem dat mijn adsl lichtje blijft knipperen. Het stopt alleen is met flikkeren nadat ik hem een paar keer reboot maar daarna valt die nog is uit .. De weken daarvoor was alles gewoon perfect. Dit is mijn log mss kunnen jullie er iets uitopmaken.
Jan 1 00:00:06 Inf <EVENT> syslog: TMOND: My PID is 91
Jan 1 00:00:06 Inf <EVENT> syslog: TMOND: Starting Watchdog...
Jan 1 00:00:06 Inf <EVENT> syslog: TMOND: Watchdog started. Timeout is set to 4s.
Jan 1 00:00:08 Inf <EVENT> scm: 000-00-00 Starting Service Management Framework, Version 2 (2.0.1)
Jan 1 00:00:09 Inf <EVENT> scm: 016-00-00 scm::DeviceInfo::Service created
Jan 1 00:00:09 Inf <EVENT> scm: 017-00-00 scm::DeviceConfig::Service created
Jan 1 00:00:09 Inf <EVENT> scm: 055-00-00 FileVerification::Verificator created
Jan 1 00:00:09 Inf <EVENT> scm: 056-00-00 FileVerification::Creator created
Jan 1 00:00:09 Inf <EVENT> scm: 058-00-00 scm::SoftwareImageInstaller::ImageOnFlashService created
Jan 1 00:00:09 Inf <EVENT> scm: 057-00-00 scm::PlatformInfo Service created
Jan 1 00:00:09 Inf <EVENT> scm: 022-00-00 scm::SoftwareImageMngmt::Service created
Jan 1 00:00:09 Inf <EVENT> scm: 025-00-00 scm::DownloadAgent created
Jan 1 00:00:09 Inf <EVENT> scm: 085-00-00 FileDownload::Service created
Jan 1 00:00:09 Inf <EVENT> scm: 084-00-00 FileUpload::Service created
Jan 1 00:00:09 Inf <EVENT> scm: 107-00-00 scm::FileUpgrade::Service created
Jan 1 00:00:09 Inf <EVENT> scm: 026-00-00 scm::LoggingService created.
Jan 1 00:00:09 Inf <EVENT> scm: 027-00-00 scm::PasswordService created.
Jan 1 00:00:09 Inf <EVENT> scm: 095-00-00 Security::Service created
Jan 1 00:00:09 Inf <EVENT> scm: 066-00-00 CM_ADSL: loading Annex-A firmware
Jan 1 00:00:09 Inf <EVENT> scm: 071-00-00 CM_ATM: constructor
Jan 1 00:00:09 Inf <EVENT> scm: 092-00-00 scm:: MacService created.
Jan 1 00:00:09 Inf <EVENT> scm: 092-00-00 MAC:: init:ethcount = 8
Jan 1 00:00:09 Inf <EVENT> scm: 092-00-00 MAC:: init:ethaddress = 00:01:E3:A3:67:68
Jan 1 00:00:09 Inf <EVENT> scm: 044-00-00 scm::LinkComponent created.
Jan 1 00:00:09 Inf <EVENT> scm: 047-00-00 scm::BridgingComponent created.
Jan 1 00:00:09 Inf <EVENT> scm: 046-00-00 scm::DHCPComponent created.
Jan 1 00:00:09 Inf <EVENT> scm: 042-00-00 scm::RoutingComponent created.
Jan 1 00:00:09 Inf <EVENT> scm: 045-00-00 scm::IPComponent created.
Jan 1 00:00:09 Inf <EVENT> scm: 049-00-00 PPP:: processChildEvent, ppp_cm is down, ignore event [92]
Jan 1 00:00:09 Inf <EVENT> scm: 033-00-00 scm::DHCPComponentManager created [ID=33]
Jan 1 00:00:09 Inf <EVENT> scm: 032-00-00 scm::DnsServerComponentManager created.
Jan 1 00:00:09 Inf <EVENT> scm: 050-00-00 scm::QDisciplineComponentManager created. [ID=50]
Jan 1 00:00:09 Inf <EVENT> scm: 090-00-00 scm::IcProxyCM created. [ID=90])
Jan 1 00:00:09 Inf <EVENT> scm: 096-101-00 created CM_DYNAMICCLASSIFICATION [96]
Jan 1 00:00:09 Inf <EVENT> scm: 077-00-00 scm::FirewallComponent created [77]
Jan 1 00:00:09 Inf <EVENT> scm: 067-00-00 scm::SipAlgComponentManager created
Jan 1 00:00:09 Inf <EVENT> scm: 065-00-00 scm::EthernetSwitchADM6996ComponentManager created
Jan 1 00:00:09 Inf <EVENT> scm: 080-00-00 scm::IPTVComponentManager created. [ID 80]
Jan 1 00:00:10 Inf <EVENT> scm: 074-00-00 L2XP: scm::FtestComponentManager created [ID=74]
Jan 1 00:00:10 Inf <EVENT> scm: 029-00-00 scm::TR69Component--created
Jan 1 00:00:10 Inf <EVENT> scm: 083-00-00 scm::TimeService created.
Jan 1 00:00:10 Inf <EVENT> scm: 028-00-00 scm::AllegroComponent created
Jan 1 00:00:10 Inf <EVENT> scm: 048-00-00 scm::ssh server created
Jan 1 00:00:10 Inf <EVENT> scm: 051-00-00 scm::PingDiagnostic created.
Jan 1 00:00:10 Inf <EVENT> scm: 052-00-00 scm::DynDnsComponent created
Jan 1 00:00:10 Inf <EVENT> scm: 053-00-00 scm::TraceRouteDiagnostic created.
Jan 1 00:00:10 Inf <EVENT> scm: 054-00-00 scm::Diagnostic created.
Jan 1 00:00:10 Inf <EVENT> scm: 086-00-00 PortTriggering component created.
Jan 1 00:00:10 Inf <EVENT> scm: 088-00-00 scm::WanReconnectSchedulingService created. [ID=88])
Jan 1 00:00:10 Inf <EVENT> scm: 089-00-00 STUNService component created
Jan 1 00:00:10 Inf <EVENT> scm: 102-00-00 Host:Component manager: Created [102]
Jan 1 00:00:10 Inf <EVENT> scm: 000-00-00 rtpsd::ComponentManager Created [103]
Jan 1 00:00:10 Inf <EVENT> scm: 094-00-00 FirmwareUpdate--Created
Jan 1 00:00:10 Inf <EVENT> scm: 015-00-00 scm::ManagedParametersService [IGD] created
Jan 1 00:00:10 Inf <EVENT> scm: 060-00-00 HTTPclient recieved event 125
Jan 1 00:00:10 Inf <EVENT> scm: 060-00-00 HTTPClient: allegro state received DOWN, allegroTaskDataPtr 0
Jan 1 00:00:10 Inf <EVENT> scm: 028-00-00 AllegroComponent: send state: 0, allegroTaskDataPtr: 0 to component_id: 60
Jan 1 00:00:10 Inf <EVENT> scm: 061-00-00 FileTransfer::Agent created
Jan 1 00:00:10 Inf <EVENT> scm: 062-00-00 HTTPclient recieved event 125
Jan 1 00:00:10 Inf <EVENT> scm: 062-00-00 HTTPClient: allegro state received DOWN, allegroTaskDataPtr 0
Jan 1 00:00:10 Inf <EVENT> scm: 028-00-00 AllegroComponent: send state: 0, allegroTaskDataPtr: 0 to component_id: 62
Jan 1 00:00:10 Inf <EVENT> scm: 030-00-00 TR69Agent--Created
Jan 1 00:00:10 Inf <EVENT> scm: 014-00-00 Updating system running level from 1 to 3
Jan 1 00:00:10 Inf <EVENT> scm: 014-00-00 Start component 16 (DeviceInfoService)
Jan 1 00:00:10 Inf <EVENT> scm: 014-00-00 Start component 17 (DeviceConfigService)
Jan 1 00:00:10 Inf <EVENT> scm: 017-00-00 Start requested, retrieving DeviceConfig settings
Jan 1 00:00:10 Inf <EVENT> scm: 017-00-00 active configfile version 52.3_100.0
Jan 1 00:00:10 Inf <EVENT> scm: 017-00-00 runtime image version 52.3_100.0
Jan 1 00:00:10 Inf <EVENT> scm: 000-00-00 Version 1: 52 -- 3 -- 0
Jan 1 00:00:10 Inf <EVENT> scm: 000-00-00 Version 2: 52 -- 3 -- 0
Jan 1 00:00:10 Inf <EVENT> scm: 017-00-00 no configfile up/downgrade needed
Jan 1 00:00:10 Err <EVENT> scm: 017-05-00 Unable to create Device Config File for elements file: Elements file does not exist.
Jan 1 00:00:10 Inf <EVENT> scm: 017-00-00 checkCopyDefault
Jan 1 00:00:10 Inf <EVENT> scm: 000-00-00 Version 1: 0 -- 0 -- 0
Jan 1 00:00:10 Inf <EVENT> scm: 000-00-00 Version 2: 34 -- 7 -- 0
Jan 1 00:00:10 Inf <EVENT> scm: 017-00-00 Configuring services with settings from configuration file
Jan 1 00:00:23 Inf <EVENT> scm: 017-00-00 Configuring services with settings from /config/system_configfile_f
Jan 1 00:00:23 Inf <EVENT> scm: 017-00-00 Configuring services with settings from /config/system_configfile_r
Jan 1 00:00:23 Inf <EVENT> scm: 017-00-00 Provisioning mode = Dormant
Jan 1 00:00:23 Inf <EVENT> scm: 017-00-00 Provisioning complete
Jan Jan 1 00:00:26 War <EVENT> kernel: Porta WLAN EEPROM driver: v0.3
Jan 1 00:00:26 War <EVENT> kernel: -> wlan_eesim_write 0x0 4096
Jan 1 00:00:26 War <EVENT> kernel: wlan_eesim_write ok
Jan 1 00:00:26 War <EVENT> kernel: Copyright (c) 2005-2006 Atheros Communications, Inc. All Rights Reserved
Jan 1 00:00:27 War <EVENT> kernel: Copyright (c) 2001-2004 Atheros Communications, Inc, All Rights Reserved
Jan 1 00:00:27 War <EVENT> kernel: wifi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
Jan 1 00:00:27 War <EVENT> kernel: wifi0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps
Jan 1 00:00:27 War <EVENT> kernel: wifi0: mac 7.8 phy 4.5 radio 5.6
Jan 1 00:00:27 War <EVENT> kernel: wifi0: Use hw queue 1 for WME_AC_BE traffic
Jan 1 00:00:27 War <EVENT> kernel: wifi0: Use hw queue 0 for WME_AC_BK traffic
Jan 1 00:00:27 War <EVENT> kernel: wifi0: Use hw queue 2 for WME_AC_VI traffic
Jan 1 00:00:27 War <EVENT> kernel: wifi0: Use hw queue 3 for WME_AC_VO traffic
Jan 1 00:00:27 War <EVENT> kernel: wifi0: Use hw queue 8 for CAB traffic
Jan 1 00:00:27 War <EVENT> kernel: wifi0: Use hw queue 9 for beacons
Jan 1 00:00:30 War <EVENT> scm: 032-03-00 DnsComponentManager:processChildEvent ignoring event while not started
Jan 1 00:00:30 War <EVENT> scm: 032-03-00 DnsComponentManager:processChildEvent ignoring event while not started
Jan 1 00:00:30 War <EVENT> scm: 032-03-00 DnsComponentManager:processChildEvent ignoring event while not started
Jan Jan 1 00:00:33 War <EVENT> scm: 033-01-00 DhcpComponentManager state==idle (ignore event)
Jan 1 00:00:33 War <EVENT> scm: 032-03-00 DnsComponentManager:processChildEvent ignoring event while not started
Jan 1 00:00:33 Err <EVENT> scm: 086-00-00 PortTriggering received EV_NET_IPSTATUS
Jan 1 00:00:34 Err <EVENT> scm: 077-00-00 Commit failed: iptFix sent back commit_failed
Jan 1 00:00:34 Err <EVENT> scm: 077-00-00 Commit failed: iptFix sent back commit_failed
Jan 1 00:00:34 War <EVENT> scm: 080-01-00 IPTVCm: processChildEvent state==Idle (ignore event)
Jan 1 01:00:40 War <EVENT> scm: 077-00-00 FW::resolveInterface: interface none not in service
Jan 1 01:00:45 War <EVENT> kernel: usb-uhci.c: Detected 2 ports
Jan 1 01:00:45 Err <EVENT> kernel: usb.c============> setting epmaxpacket from 0 to 8 !!!!!!
Jan 1 01:00:45 War <EVENT> kernel: usb-uhci.c: Detected 2 ports
Jan 1 01:00:45 Err <EVENT> kernel: usb.c============> setting epmaxpacket from 0 to 8 !!!!!!
Jan 1 01:00:45 War <EVENT> kernel: PCI: 00:0d.2 PCI cache line size set incorrectly (0 bytes) by BIOS/FW, correcting to 32
Jan 1 01:00:45 Err <EVENT> kernel: ehci_hcd 00:0d.2: USB 2.0 enabled, EHCI 1.00, driver 2003-Dec-29/2.4
Jan 1 01:00:45 Err <EVENT> kernel: usb.c============> setting epmaxpacket from 0 to 64 !!!!!!
Jan 1 01:00:46 War <EVENT> scm: 070-00-00 UPnP: Service is disabled.
Jan 1 01:00:47 War <EVENT> kernel: drv_amazon:FIO_AMAZON_INIT
Jan 1 01:00:47 War <EVENT> kernel: Board_InitPlatform!
Jan 1 01:00:47 War <EVENT> kernel: SPI_Init!
Jan 1 01:00:47 War <EVENT> kernel: Board_InitIrq!
Jan 1 01:00:47 War <EVENT> kernel: init finished!
Jan 1 01:00:47 War <EVENT> kernel: drv_amazon:reset deactivated!
Jan 1 01:00:48 Deb <EVENT> kernel:

<7>WARN: No dc threshold configuration in BBD => default threshold configuration is programmed
Jan 1 01:00:48 War <EVENT> kernel:

kernel: Duslic debug: open device!
Jan 1 01:00:48 War <EVENT> kernel: cpc5621_open: open devNum=0, chNum=0, pDev=00000000, CPC5621_Devices=c00c2348
Jan 1 01:00:48 War <EVENT> kernel: cpc5621_open: open devNum=0, chNum=0, pDev=80272c80
Jan 1 01:00:50 War <EVENT> scm: 050-20-00 QDisciplineCM:handleEvent skipping EV_Link_InterfaceStatus (no linuxdevice name)
Jan 1 01:00:50 Err <EVENT> scm: 086-00-00 PortTriggering received EV_NET_IPSTATUS
Jan 1 01:01:09 War <EVENT> kernel:
Jan 1 01:01:09 War <EVENT> kernel:
Jan 1 01:01:09 War <EVENT> kernel: new reboot
Jan 1 01:01:09 War <EVENT> kernel:
Jan 1 01:01:09 War <EVENT> kernel: start download pages
Jan 1 01:01:09 War <EVENT> kernel:
Jan 1 01:01:43 War <EVENT> kernel: pages downloadedkernel:
Jan 1 01:01:44 Err <EVENT> kernel: channel is fastkernel: set_qsb: Class=1 MAX_PCR=0 PCR=0 MIN_PCR=0 SCR=0 MBS=0 CDV=15
Jan 1 01:01:44 Err <EVENT> kernel: set_qsb: tprs:0 twfq:16383 ts:0 taus:0
Jan 1 01:01:44 Err <EVENT> scm: 077-00-00 FirewallComponent::NAT Notification. Unable to remove NAT for address none
Jan 1 01:01:56 Err <EVENT> scm: 049-00-00 PPP:: EV_COMM_RX_DATA error code NONE
Jan Jan 1 01:01:58 Err <EVENT> scm: 077-00-00 Commit failed: iptFix sent back commit_failed
Jan 1 01:01:58 Err <EVENT> scm: 077-00-00 Commit failed: iptFix sent back commit_failed
Nov 1 10:56:08 Err <EVENT> scm: 086-00-00 PortTriggering received EV_NET_IPSTATUS
Nov 1 10:56:08 Err <EVENT> scm: 086-00-00 PortTriggering add NAT rule: 83.101.4.242
Nov 1 10:58:22 War <EVENT> scm: 995-00-00 WebGUI::prepareDataForPageLoad Apply Rollback on existing scm session:
---

Kan iemand mij helpen? Mvg , ub_removed10624
Gebruikersavatar
brooklyn
Elite Poster
Elite Poster
Berichten: 1252
Lid geworden op: 15 jun 2004, 20:25
Locatie: West-Vlaanderen aan de kust

heb je al eens een hard reboot gedaan?
Afbeelding
PC1: Intel Core 2 Duo E6600 - 2GB DDR2 SDRAM PC6400 - ASUS P5B Deluxe - GeForce 8800GTS 320MB DDR3 - Western Digital 35GB Raptor - 3.1TB HD space
PC2: AMD3600 - 1GB DDR - ASUS A8N Deluxe - ATI 3850 -
Dvico Tvix 6500A user
ubremoved_10624
Member
Member
Berichten: 54
Lid geworden op: 02 okt 2008, 17:36

brooklyn schreef:heb je al eens een hard reboot gedaan?

Ik heb het probleem gevonden! Mag slotje op!
Gebruikersavatar
AnD
Elite Poster
Elite Poster
Berichten: 3824
Lid geworden op: 18 okt 2003, 12:29
Locatie: Hasselt
Uitgedeelde bedankjes: 393 keer
Bedankt: 87 keer

IanDesmet schreef:
brooklyn schreef:heb je al eens een hard reboot gedaan?

Ik heb het probleem gevonden! Mag slotje op!
Wat was het probleem ?
ubremoved_10624
Member
Member
Berichten: 54
Lid geworden op: 02 okt 2008, 17:36

AnD schreef:
IanDesmet schreef:
brooklyn schreef:heb je al eens een hard reboot gedaan?

Ik heb het probleem gevonden! Mag slotje op!
Wat was het probleem ?

Het was door de overschakeling naar dommel en mijn alarm had problemen met connectie daardoor. Slotje !
Plaats reactie

Terug naar “Dommel”