07-29-2004 12:58 PM - edited 03-02-2019 05:24 PM
Hi,
I get all of these messages on my router when the router boots up. I'm not sure what they are if it is a problem or what? It seemed to scroll through a few times with these messages repeating. The router did eventually boot up but it seemed to take a while.
Thanks,
George
Traceback= 8016F8F0 8015CBA0 801A21DC 801A2264 801A23C8 801A1F70 800C40A4 801CB
0D4 801CA578 801CA620 801CACA0 801CA974 801C9B08 801C61B0 801C8FE8 8016608C
00:00:02: %SYS-2-INTSCHED: 'sleep for' at level 5
-Process= "Init", i
-Process= "Init", ipl= 5, pid= 2
-Traceback= 8016F8F
-Traceback= 8016F8F0 8015CBA0 801A21DC 801A2264 801A23C8 801A1F70 800C40A4 801CB
0D4 801CA578 801CA6
0D4 801CA578 801CA620 801CACA0 801CA974 801C9B08 801C61B0 801C8FE8 8016608C
%SYS-2-INTSCHED: 's
00:00:02: %SYS-2-INTSCHED: 'sleep for' a
-Process= "Init", ipl= 5, pid= 2
-Process= "Init", ipl= 5, pid= 2ack= 8016F8F0 8015CBA0 801A2300
-Process= "Init", ipl= 5, pid= 2
0D4 801CA578 801CA6
-Traceback= 8016F8F0 8015CBA0 801A2300 801A23C8 801A1F70 800C40A4 801CB0D4 801CA
%SYS-2-INTSCHED: 'sleep for'
578 801CA620 801CACA0 801CA974 801C9B08 801C61B0 801C8FE8 8016608C 8016613Cpid= 2
-Traceback= 8016F8F0 8015CBA0 801A23
00:00:02: %SYS-2-INTSCHED: 'sleep for' at level 5
-Process= "Init", ipl= 5, pid= 2CA620 801CACA0 801CA974 801C9B08
-Process= "Init", ipl=
%SYS-2-INTSCHED: 's
-Traceback= 8016F8F0 8015CBA0 801A2300 801A23C8 801A1F70 800C40A4 801CB0D4 801CA= 5, pid= 2
-Traceback= 8016F8F0 8015CBA0 801A23
578 801CA620 801CACA0 801CA974 801C9B08 801C61B0 801C8FE8 8016608C 8016613C
578 801CA620 801CACA0 801C
00:00:02: %SYS-2-INTSCHED: 'sleep for' at level 5
-Process= "Init", ipl= 5, pid= 2INTSCHED: 'sleep for' at level 5
-Traceback= 8016F8F
-Traceback= 8016F8F0 8015CBA0 801A21DC 801A2264 801A23C8 801A1F70 800C40A4 801CB
578 801CA620 801CAC
0D4 801CA578 801CA620 801CACA0 801CA974 801C9B08 801C61B0 801C8FE8 8016608C
%SYS-2-INTSCHED: 's
07-30-2004 05:48 AM
I would open a tac case , From CCO
Error Message
%SYS-2-INTSCHED : '[chars]' at level [dec]
Explanation The scheduler was entered from an interrupt service routine (ISR).
Recommended Action Copy the error message exactly as it appears on the console or in the system log, include the stack trace, and report it to your Cisco technical support representative.
07-30-2004 10:07 AM
Tracebacks are a sign of a software problem. Is this perhaps a new copy of the IOS on the router (or perhpas a new router)? If so I would try a different copy of the IOS or a different version of IOS in hopes that the problem is something in the particular instance of the IOS that might not be in others. If this is a router that has been running and then the problem started, I would look to see if anything has changed recently.
HTH
Rick
07-30-2004 11:23 AM
I am getting ready to change the router config because of a hardware firewall configuration I need to change the IP around to be public on the ethernet port and then take NAT out and let the firewall do that.
Here is my config IP addresses are not real but the rest is what is currently on my router do you see anything on there that might cause this problem.
I don't have a whole lot of experience here but I do know enough to be dangerous I guess you could say :)
!
version 12.1
no service single-slot-reload-enable
no service pad
service tcp-keepalives-in
service tcp-keepalives-out
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname router
!
logging rate-limit console 10 except errors
enable secret 5
!
memory-size iomem 25
ip subnet-zero
no ip source-route
no ip gratuitous-arps
no ip finger
no ip domain-lookup
!
no ip bootp server
ip audit attack action alarm drop reset
ip audit notify log
ip audit po max-events 100
ip audit smtp spam 100
!
!
cns event-service server
!
!
!
interface FastEthernet0
description connected to EthernetLAN
ip address 172.22.1.15 255.255.255.0
ip nat inside
speed auto
full-duplex
!
interface Serial0
description connected to Internet
ip address 35.45.122.42 255.255.255.252
no ip redirects
no ip unreachables
no ip proxy-arp
ip nat outside
encapsulation ppp
service-module t1 clock source internal
service-module t1 timeslots 13-24
service-module t1 remote-alarm-enable
!
router rip
version 2
passive-interface Serial0
network 172.22.0.0
no auto-summary
!
ip nat inside source list 1 interface Serial0 overload
ip nat inside source static tcp 172.22.1.16 3389 35.45.122.42 3389 extendable
ip nat inside source static tcp 172.22.1.16 21 35.45.122.42 21 extendable
ip nat inside source static tcp 172.22.1.16 80 35.45.122.42 80 extendable
ip nat inside source static udp 172.22.1.16 1433 35.45.122.42 1433 extendable
ip nat inside source static tcp 172.22.1.16 1433 35.45.122.42 1433 extendable
ip nat inside source static tcp 172.22.1.11 5631 35.45.122.42 5631 extendable
ip nat inside source static udp 172.22.1.11 5632 35.45.122.42 5632 extendable
ip nat inside source static udp 172.22.1.3 5632 35.45.122.42 5632 extendable
ip nat inside source static tcp 172.22.1.3 5631 35.45.122.42 5631 extendable
ip nat inside source static udp 172.22.1.11 3389 35.45.122.42 3389 extendable
ip kerberos source-interface any
ip classless
ip route 0.0.0.0 0.0.0.0 Serial0
no ip http server
!
access-list 1 permit 172.22.1.0 0.0.0.255
no cdp run
banner motd
WARNING: You are connected to a Unauthorized access and use of this
network will be vigorously prosecuted.
!
line con 0
exec-timeout 0 0
password 7
login
transport input none
line aux 0
no exec
exec-timeout 0 1
login
transport output none
line vty 0 4
password 7
login
!
no scheduler allocate
end
07-30-2004 12:31 PM
I do not see anything here that looks like it should cause problems. But sometimes these things are quite subtle, and I have seen a few situations where something that looked innocent in the config could interfere with a router booting. I can suggest a fairly simple experiment to evaluate whether there is something in the config that is involved (assuming that you are on the console port of the router). Set the router to ignore NVRAM at bootup by setting the config register. In global config mode use this command: config-register 0x2142. Then reboot the router. When it boots it will not read the config in NVRAM. If it boots cleanly then it means that there is in fact something in the config that is causing this. If it still has a problem booting then we have ruled out anything in the config.
When the router boots you will have an empty config. Go into enable mode (there will not be a password) and into config mode. In global config mode use this command: config-register 0x2102 and it will set the config register back to normal. Reboot the router (it will tell you that the config has changed and ask if you want to save the config - the answer is NO !
Now when the router reboots it will read the config in NVRAM and you will be back to normal.
HTH
Rick
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide