>Not sure if the right answer is for drivers not to call ether_ifattach()
>until the point-of-no-failure (lots of drivers are wrong then) or
>initialize other parts earlier.
The other "obvious" method is to rearrange the sysinit priorities
(/sys/sys/kernel.h) so that all network domains are initia
>Can you provide a backtrace that leads to this?
Sure. In case it's not obvious, the __rw_rlock at the top of the
trace is working on a lock that has never been initialized (the
first of the two ipv4 PCBs).
Chris
Booting...
GDB: no debug ports present
KDB: debugger backends: ddb
KDB: current ba
Hi,
- Original Message -
> From: "Gleb Smirnoff"
> To: "Chris Torek"
> Cc: freebsd-hackers@freebsd.org
> Sent: Tuesday, April 2, 2013 3:57:08 AM
> Subject: Re: boot time crash in if_detach_internal()
>
> On Mon, Apr 01, 2013 at 03:45:19AM -
On Mon, Apr 01, 2013 at 03:45:19AM -0600, Chris Torek wrote:
C> I have been poking about with the bhyve virtualization code in
C> FreeBSD 10-current, and managed to crash FreeBSD during its
C> bootstrap process due to the fact that if_detach is called
C> from boot time configuration code, before th
I have been poking about with the bhyve virtualization code in
FreeBSD 10-current, and managed to crash FreeBSD during its
bootstrap process due to the fact that if_detach is called
from boot time configuration code, before the internal domain
system initialization has happened.
I added the follow
5 matches
Mail list logo
