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'
> >
>
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 #dra
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 a
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 br
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 (un
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 Dra
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
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
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 alloc
rt 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 12
10 matches
Mail list logo
