Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c]

2009-10-18 Thread Julian Elischer
Harsha wrote: On Sat, Oct 17, 2009 at 11:42 PM, Julian Elischer wrote: Harsha wrote: wrote: Looks like a NULL pointer dereference, so perhaps a more traditional bug -- could you convert ifindex_alloc_locked+0x71 to a line of code? You can do this using kgdb on the kernel symbols file, perhap

Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c]

2009-10-18 Thread Harsha
On Sat, Oct 17, 2009 at 11:42 PM, Julian Elischer wrote: > Harsha wrote: >> wrote: >>> >>> Looks like a NULL pointer dereference, so perhaps a more traditional bug >>> -- >>> could you convert ifindex_alloc_locked+0x71 to a line of code? You can do >>> this using kgdb on the kernel symbols file,

Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c]

2009-10-17 Thread Julian Elischer
Harsha wrote: Hi Robert, Apologies for not getting earlier. On Mon, Oct 12, 2009 at 6:46 AM, Robert N. M. Watson wrote: Looks like a NULL pointer dereference, so perhaps a more traditional bug -- could you convert ifindex_alloc_locked+0x71 to a line of code? You can do this using kgdb on the

Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c]

2009-10-17 Thread Harsha
Hi Robert, Apologies for not getting earlier. On Mon, Oct 12, 2009 at 6:46 AM, Robert N. M. Watson wrote: > > Looks like a NULL pointer dereference, so perhaps a more traditional bug -- > could you convert ifindex_alloc_locked+0x71 to a line of code? You can do > this using kgdb on the kernel sy

Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c]

2009-10-12 Thread Robert N. M. Watson
On 12 Oct 2009, at 05:38, Harsha wrote: Thanks a lot for the clarification. I had assumed that the lock was non-sleepable looking at this log - Kernel page fault with the following non-sleepable locks held: exclusive rw ifnet_rw (ifnet_rw) r = 0 (0xc0f63464) locked @ /usr/src/sys/net/if.c:409

Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c]

2009-10-11 Thread Harsha
Hi Robert, On Sun, Oct 11, 2009 at 1:30 PM, Robert Watson wrote: > Giant is a bit special in that the long-term sleep code in the kernel knows > to drop it when sleeping, and re-acquire when waking up.  So, unlike all > other mutexes, it should be OK to hold it in this case, as Giant will simply

Re: Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c]

2009-10-11 Thread Robert Watson
On Sun, 11 Oct 2009, Harsha Srinath wrote: I'm running an updated HEAD kernel and got a page fault in ifindex_alloc_locked() in if.c. I figured that the problem was caused by the (pluggable) network card of my laptop and found that during the initialization of the interface, cb_event_thread()

Page fault in IFNET_WLOCK_ASSERT [if.c and pccbb.c]

2009-10-11 Thread Harsha Srinath
Hi all, I'm running an updated HEAD kernel and got a page fault in ifindex_alloc_locked() in if.c. I figured that the problem was caused by the (pluggable) network card of my laptop and found that during the initialization of the interface, cb_event_thread() takes the giant lock and up the call ch