Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
Hi Ralf, I've pushed a fix to master (commit id 349101038ee08e27625f3a09b566f4921af14eb6). It should fix the issue. Cheers, Antonio Huete 2011/8/11 Ralf Schmitt > Antonio Huete Jimenez writes: > > > Hi, > > > > I'm having exactly the same issue. > > > > Ralf, please post a 'ifconfig -a' > > > > cognac# ifconfig -a > re0: flags=8843 mtu 1500 >options=1b >inet6 fe80::225:22ff:fe6d:9b7a%re0 prefixlen 64 scopeid 0x1 >inet 192.168.10.41 netmask 0xf000 broadcast 192.168.15.255 >ether 00:25:22:6d:9b:7a >media: Ethernet autoselect (1000baseT ) >status: active > faith0: flags=8002 mtu 1500 > lo0: flags=8049 mtu 16384 >options=3 >inet 127.0.0.1 netmask 0xff00 >inet6 ::1 prefixlen 128 >inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 > ppp0: flags=8010 mtu 1500 > sl0: flags=c010 mtu 552 > > -- > Cheers > Ralf >
Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
Ralf Schmitt writes: > Ralf Schmitt writes: > >> >> while removing the network cable from the machine, I now even got a >> kernel panic and debugger prompt. Are there any docs on how to report >> those? > > http://www.dragonflybsd.org/docs/howtos/HowToCreateACoreDump/ > > With the help from #dragonflybsd and the above page I was able to create > a crashdump. It's available for download here: > > http://systemexit.de/dragonfly-crash-network-cable-remove/crash.tgz (kgdb) bt #0 _get_mycpu (di=) at ./machine/thread.h:69 #1 md_dumpsys (di=) at /usr/src/sys/platform/pc64/x86_64/dump_machdep.c:263 #2 0x8047e8d5 in dumpsys () at /usr/src/sys/kern/kern_shutdown.c:927 #3 0x8029a3dc in db_fncall (dummy1=, dummy2=, dummy3=, dummy4=) at /usr/src/sys/ddb/db_command.c:542 #4 0x8029a8af in db_command () at /usr/src/sys/ddb/db_command.c:344 #5 db_command_loop () at /usr/src/sys/ddb/db_command.c:470 #6 0x8029d761 in db_trap (type=, code=) at /usr/src/sys/ddb/db_trap.c:71 #7 0x8071e238 in kdb_trap (type=, code=, regs=) at /usr/src/sys/platform/pc64/x86_64/db_interface.c:176 #8 0x80723d66 in trap (frame=0xffe08d6f3aa8) at /usr/src/sys/platform/pc64/x86_64/trap.c:701 #9 0x8071c77e in calltrap () at /usr/src/sys/platform/pc64/x86_64/exception.S:187 #10 0x8071e0cf in breakpoint (msg=) at ./cpu/cpufunc.h:73 #11 Debugger (msg=) at /usr/src/sys/platform/pc64/x86_64/db_interface.c:361 #12 0x8047f1c4 in panic ( fmt=0x807cf400 "rtrequest1_msghandler: rtrequest table error was not on cpu #0") at /usr/src/sys/kern/kern_shutdown.c:824 #13 0x80525eb9 in rtrequest1_msghandler (msg=) at /usr/src/sys/net/route.c:812 #14 0x805250c0 in rtable_service_loop (dummy=) at /usr/src/sys/net/route.c:202 #15 0x80489acf in lwkt_deschedule_self (td=0x0) at /usr/src/sys/kern/lwkt_thread.c:283 Backtrace stopped: previous frame inner to this frame (corrupt stack?) Judging from the backtrace it looks like some routing information should be updated. Im running dhclient on this machine and if I turn it off I can unplug the network cable and plug it in again without getting a kernel panic. -- Cheers Ralf
Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
Ralf Schmitt writes: > > while removing the network cable from the machine, I now even got a > kernel panic and debugger prompt. Are there any docs on how to report > those? http://www.dragonflybsd.org/docs/howtos/HowToCreateACoreDump/ With the help from #dragonflybsd and the above page I was able to create a crashdump. It's available for download here: http://systemexit.de/dragonfly-crash-network-cable-remove/crash.tgz -- Cheers Ralf
Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
Antonio Huete Jimenez writes: > Hi, > > I'm having exactly the same issue. > > Ralf, please post a 'ifconfig -a' > cognac# ifconfig -a re0: flags=8843 mtu 1500 options=1b inet6 fe80::225:22ff:fe6d:9b7a%re0 prefixlen 64 scopeid 0x1 inet 192.168.10.41 netmask 0xf000 broadcast 192.168.15.255 ether 00:25:22:6d:9b:7a media: Ethernet autoselect (1000baseT ) status: active faith0: flags=8002 mtu 1500 lo0: flags=8049 mtu 16384 options=3 inet 127.0.0.1 netmask 0xff00 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x3 ppp0: flags=8010 mtu 1500 sl0: flags=c010 mtu 552 -- Cheers Ralf
Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
Hi, I'm having exactly the same issue. Ralf, please post a 'ifconfig -a' Cheers, Antonio Huete 2011/8/11 Ralf Schmitt > Francois Tigeot writes: > > >> | panic: rtrequest1_msghandler: rtrequest table error was not on cpy #0 > >> | cpuid = 4 > > > > What is the exact version of your system (uname -a) ? > > > > This is suspiciously close to a problem I had in the last few months. > > DragonFly cognac.brainbot.com 2.11-DEVELOPMENT DragonFly > v2.11.0.651.g448b3-DEVELOPMENT #1: Thu Aug 11 11:36:40 CEST 2011 > r...@cognac.brainbot.com:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64 > > -- > Cheers > Ralf >
Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
Francois Tigeot writes: >> | panic: rtrequest1_msghandler: rtrequest table error was not on cpy #0 >> | cpuid = 4 > > What is the exact version of your system (uname -a) ? > > This is suspiciously close to a problem I had in the last few months. DragonFly cognac.brainbot.com 2.11-DEVELOPMENT DragonFly v2.11.0.651.g448b3-DEVELOPMENT #1: Thu Aug 11 11:36:40 CEST 2011 r...@cognac.brainbot.com:/usr/obj/usr/src/sys/X86_64_GENERIC x86_64 -- Cheers Ralf
Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
On Thu, Aug 11, 2011 at 03:54:45PM +0200, Ralf Schmitt wrote: > > while removing the network cable from the machine, I now even got a > kernel panic and debugger prompt. Are there any docs on how to report > those? > > The error is something like (hand transcripted): > , > | panic: rtrequest1_msghandler: rtrequest table error was not on cpy #0 > | cpuid = 4 What is the exact version of your system (uname -a) ? This is suspiciously close to a problem I had in the last few months. -- Francois Tigeot
Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
Justin Sherrill writes:
> Maybe check 'arp -a', and see if there's more than one machine
> configured with that IP?
arp -a says:
,
| muni.brainbot.com (192.168.10.173) at 00:19:db:cd:fc:67 on re0 [ethernet]
| gw.brainbot.com (192.168.10.210) at (incomplete) on re0 [ethernet]
| ? (192.168.10.250) at 00:18:f3:08:30:16 on re0 [ethernet]
`
(the local machine uses 192.168.10.41. I'm pretty sure there's no other
machine using that IP).
while removing the network cable from the machine, I now even got a
kernel panic and debugger prompt. Are there any docs on how to report
those?
The error is something like (hand transcripted):
,
| panic: rtrequest1_msghandler: rtrequest table error was not on cpy #0
| cpuid = 4
| Trace beginning at frame 0xffe08d6f3b70
| panic() at panic+0x1ed
| panic() at panic+0x1ed
| rtrequest1_msghandler() at rtrequest1_msghandler+0x130
| rtable_service_loop() at rtable_service_loop+0x2c
| Debugger("panic")
|
| CPU4 stopping CPUs: 0x0002f
| stopped
| Stopped at Debugger+0x39: movb $0,0x60d6d6(%rip)
| db>
`
--
Cheers
Ralf
Re: arpresolve: can't allocate llinfo for 127.0.0.1 rt
Maybe check 'arp -a', and see if there's more than one machine configured with that IP? On Thu, Aug 11, 2011 at 9:01 AM, Ralf Schmitt wrote: > Hi, > > when I try to login to the local machine with ssh, it doesn't work: > , > | # ssh -v root@192.168.10.41 > | OpenSSH_5.8p1-hpn13v11 DragonFly-20110408, OpenSSL 1.0.0d 8 Feb 2011 > | debug1: Reading configuration data /etc/ssh/ssh_config > | debug1: Connecting to 192.168.10.41 [192.168.10.41] port 22. > | ssh: connect to host 192.168.10.41 port 22: Operation timed out > ` > and ssh seems to hang until the connection attempt times out. > > I get the following messages on the console > > ,---- > | arplookup 127.0.0.1 failed: could not allocate llinfo > | arpresolve: can't allocate llinfo for 127.0.0.1 rt > | arplookup 127.0.0.1 failed: could not allocate llinfo > | arpresolve: can't allocate llinfo for 127.0.0.1 rt > | arplookup 127.0.0.1 failed: could not allocate llinfo > | arpresolve: can't allocate llinfo for 127.0.0.1 rt > | arplookup 127.0.0.1 failed: could not allocate llinfo > | arpresolve: can't allocate llinfo for 127.0.0.1 rt > | arplookup 127.0.0.1 failed: could not allocate llinfo > | arpresolve: can't allocate llinfo for 127.0.0.1 rt > ` > > ssh 127.0.0.1 works fine, as does login from another machine. > > I'm using X86_64_GENERIC kernel compiled from git. > > Anyone know what's going on? > > -- > Cheers > Ralf >
arpresolve: can't allocate llinfo for 127.0.0.1 rt
Hi, when I try to login to the local machine with ssh, it doesn't work: , | # ssh -v root@192.168.10.41 | OpenSSH_5.8p1-hpn13v11 DragonFly-20110408, OpenSSL 1.0.0d 8 Feb 2011 | debug1: Reading configuration data /etc/ssh/ssh_config | debug1: Connecting to 192.168.10.41 [192.168.10.41] port 22. | ssh: connect to host 192.168.10.41 port 22: Operation timed out ` and ssh seems to hang until the connection attempt times out. I get the following messages on the console , | arplookup 127.0.0.1 failed: could not allocate llinfo | arpresolve: can't allocate llinfo for 127.0.0.1 rt | arplookup 127.0.0.1 failed: could not allocate llinfo | arpresolve: can't allocate llinfo for 127.0.0.1 rt | arplookup 127.0.0.1 failed: could not allocate llinfo | arpresolve: can't allocate llinfo for 127.0.0.1 rt | arplookup 127.0.0.1 failed: could not allocate llinfo | arpresolve: can't allocate llinfo for 127.0.0.1 rt | arplookup 127.0.0.1 failed: could not allocate llinfo | arpresolve: can't allocate llinfo for 127.0.0.1 rt ` ssh 127.0.0.1 works fine, as does login from another machine. I'm using X86_64_GENERIC kernel compiled from git. Anyone know what's going on? -- Cheers Ralf
