Re: ndis0 interrrupt storm
Paul B. Mahol wrote: On 5/20/09, Chris Whitehouse wrote: has this died a death? Anything else I can do? Should I file a PR? Perhaps donate some money, not to me directly :) , file a PR, send card with complete machine so that problem can be completly and promptly explored and etc... yes specially the first. I could send the card but not the laptop though. I need message from DB kernel that is posted right away before kernel puts panic message. It is the trace for thread caused locking problems www.fishercroft.plus.com/ndis.panic.bt.5.jpg www.fishercroft.plus.com/ndis.panic.bt.6.jpg www.fishercroft.plus.com/ndis.panic.bt.7.jpg Just remmember that panic is one problem and interrupts storm is another. Ok Paul, I don't mind too much if this doesnt get fixed for me, I don't want to waste your time when some other solution like a supported usb wifi is not so expensive. If it is good for other people to get it fixed that's different, I'll do what I can to help. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
On 5/20/09, Chris Whitehouse wrote: > Chris Whitehouse wrote: >> Paul B. Mahol wrote: >>> On 5/13/09, Chris Whitehouse wrote: Paul B. Mahol wrote: > On 5/12/09, Chris Whitehouse wrote: >> Paul B. Mahol wrote: >>> Just typing bt on db prompt for now should be enough. >> panic: sleeping thread >> cpuid = 0 >> KDB: enter: panic >> [thread pid 1497 tid 100073 ] >> Stopped atkdb_enter+0x3a: movl$0,kdb_why >> db> bt >> Tracing pid 1497 tid 100073 td 0xc356c900 >> kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d4001b68,0,...) at kdb_enter+0x3a >> panic(c0c42726,,0,cc,4,...) at panic+0x136 >> propagate_priority(c0d9df84,0,c0c4249e,2e1,c356d180,...) at >> propagate_priority+0x18c >> turnstile_wait(c356d180,c37b2240,0,18d,c34fc06c,...) at >> turnstile_wait+0x44d >> _mtx_lock_sleep(c34fc06c,c356c900,0,c38de072,6b4,...) at >> mtx_lock_sleep+0x18e >> _mtx_lock_flags(c34fc06c,0,c38de072,6b4,c089dc98,...) at >> mtx_lock_flags+0xf7 >> ndis_ticktask(c3821700,c34fc000,c37e8e3c,c3916bd0,c38fc6e0,...) at >> ndis_ticktask+0x3a >> _end(c37e8e3c,d4001d38,c0c39438,333,c37ab548,...) at _end+0x321d >> fork_exit(c38fc600,c37e8e3c,d4001d38) at fork_exit+0xb8 >> fork_trampoline() at fork_trampoline+0x8 >> --- trap 0, eip = 0 esp = 0xd4001d70, ebp = 0 --- >> >> >> Typed by hand but I'm pretty sure it is correct. >> >> Don't know if it is significant but repeating the panic gave quite >> a few >> different values. > Post them too. If only numbers are different and stack is same that > could help even more. Is photos ok or do you need text? >>> >>> Whatever, just let it be complete. >> >> http://www.fishercroft.plus.com/ndis.panic.bt.1 >> http://www.fishercroft.plus.com/ndis.panic.bt.2 >> http://www.fishercroft.plus.com/ndis.panic.bt.3 >> http://www.fishercroft.plus.com/ndis.panic.bt.4 >> >> >> >>> > This is on i386? > yes > > has this died a death? Anything else I can do? Should I file a PR? Perhaps donate some money, not to me directly :) , file a PR, send card with complete machine so that problem can be completly and promptly explored and etc... I need message from DB kernel that is posted right away before kernel puts panic message. It is the trace for thread caused locking problems Just remmember that panic is one problem and interrupts storm is another. > I don't mind waiting if something is happening, just don't want to get > stuck in /dev/void. > > Chris > -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Chris Whitehouse wrote: Paul B. Mahol wrote: On 5/13/09, Chris Whitehouse wrote: Paul B. Mahol wrote: On 5/12/09, Chris Whitehouse wrote: Paul B. Mahol wrote: Just typing bt on db prompt for now should be enough. panic: sleeping thread cpuid = 0 KDB: enter: panic [thread pid 1497 tid 100073 ] Stopped atkdb_enter+0x3a: movl$0,kdb_why db> bt Tracing pid 1497 tid 100073 td 0xc356c900 kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d4001b68,0,...) at kdb_enter+0x3a panic(c0c42726,,0,cc,4,...) at panic+0x136 propagate_priority(c0d9df84,0,c0c4249e,2e1,c356d180,...) at propagate_priority+0x18c turnstile_wait(c356d180,c37b2240,0,18d,c34fc06c,...) at turnstile_wait+0x44d _mtx_lock_sleep(c34fc06c,c356c900,0,c38de072,6b4,...) at mtx_lock_sleep+0x18e _mtx_lock_flags(c34fc06c,0,c38de072,6b4,c089dc98,...) at mtx_lock_flags+0xf7 ndis_ticktask(c3821700,c34fc000,c37e8e3c,c3916bd0,c38fc6e0,...) at ndis_ticktask+0x3a _end(c37e8e3c,d4001d38,c0c39438,333,c37ab548,...) at _end+0x321d fork_exit(c38fc600,c37e8e3c,d4001d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0 esp = 0xd4001d70, ebp = 0 --- Typed by hand but I'm pretty sure it is correct. Don't know if it is significant but repeating the panic gave quite a few different values. Post them too. If only numbers are different and stack is same that could help even more. Is photos ok or do you need text? Whatever, just let it be complete. http://www.fishercroft.plus.com/ndis.panic.bt.1 http://www.fishercroft.plus.com/ndis.panic.bt.2 http://www.fishercroft.plus.com/ndis.panic.bt.3 http://www.fishercroft.plus.com/ndis.panic.bt.4 This is on i386? yes has this died a death? Anything else I can do? Should I file a PR? I don't mind waiting if something is happening, just don't want to get stuck in /dev/void. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Paul B. Mahol wrote: On 5/13/09, Chris Whitehouse wrote: Paul B. Mahol wrote: On 5/12/09, Chris Whitehouse wrote: Paul B. Mahol wrote: Just typing bt on db prompt for now should be enough. panic: sleeping thread cpuid = 0 KDB: enter: panic [thread pid 1497 tid 100073 ] Stopped atkdb_enter+0x3a: movl$0,kdb_why db> bt Tracing pid 1497 tid 100073 td 0xc356c900 kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d4001b68,0,...) at kdb_enter+0x3a panic(c0c42726,,0,cc,4,...) at panic+0x136 propagate_priority(c0d9df84,0,c0c4249e,2e1,c356d180,...) at propagate_priority+0x18c turnstile_wait(c356d180,c37b2240,0,18d,c34fc06c,...) at turnstile_wait+0x44d _mtx_lock_sleep(c34fc06c,c356c900,0,c38de072,6b4,...) at mtx_lock_sleep+0x18e _mtx_lock_flags(c34fc06c,0,c38de072,6b4,c089dc98,...) at mtx_lock_flags+0xf7 ndis_ticktask(c3821700,c34fc000,c37e8e3c,c3916bd0,c38fc6e0,...) at ndis_ticktask+0x3a _end(c37e8e3c,d4001d38,c0c39438,333,c37ab548,...) at _end+0x321d fork_exit(c38fc600,c37e8e3c,d4001d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0 esp = 0xd4001d70, ebp = 0 --- Typed by hand but I'm pretty sure it is correct. Don't know if it is significant but repeating the panic gave quite a few different values. Post them too. If only numbers are different and stack is same that could help even more. Is photos ok or do you need text? Whatever, just let it be complete. http://www.fishercroft.plus.com/ndis.panic.bt.1 http://www.fishercroft.plus.com/ndis.panic.bt.2 http://www.fishercroft.plus.com/ndis.panic.bt.3 http://www.fishercroft.plus.com/ndis.panic.bt.4 This is on i386? yes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
On 5/13/09, Chris Whitehouse wrote: > Paul B. Mahol wrote: >> On 5/12/09, Chris Whitehouse wrote: >>> Paul B. Mahol wrote: Just typing bt on db prompt for now should be enough. >>> panic: sleeping thread >>> cpuid = 0 >>> KDB: enter: panic >>> [thread pid 1497 tid 100073 ] >>> Stopped atkdb_enter+0x3a: movl$0,kdb_why >>> db> bt >>> Tracing pid 1497 tid 100073 td 0xc356c900 >>> kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d4001b68,0,...) at kdb_enter+0x3a >>> panic(c0c42726,,0,cc,4,...) at panic+0x136 >>> propagate_priority(c0d9df84,0,c0c4249e,2e1,c356d180,...) at >>> propagate_priority+0x18c >>> turnstile_wait(c356d180,c37b2240,0,18d,c34fc06c,...) at >>> turnstile_wait+0x44d >>> _mtx_lock_sleep(c34fc06c,c356c900,0,c38de072,6b4,...) at >>> mtx_lock_sleep+0x18e >>> _mtx_lock_flags(c34fc06c,0,c38de072,6b4,c089dc98,...) at >>> mtx_lock_flags+0xf7 >>> ndis_ticktask(c3821700,c34fc000,c37e8e3c,c3916bd0,c38fc6e0,...) at >>> ndis_ticktask+0x3a >>> _end(c37e8e3c,d4001d38,c0c39438,333,c37ab548,...) at _end+0x321d >>> fork_exit(c38fc600,c37e8e3c,d4001d38) at fork_exit+0xb8 >>> fork_trampoline() at fork_trampoline+0x8 >>> --- trap 0, eip = 0 esp = 0xd4001d70, ebp = 0 --- >>> >>> >>> Typed by hand but I'm pretty sure it is correct. >>> >>> Don't know if it is significant but repeating the panic gave quite a few >>> different values. >> >> Post them too. If only numbers are different and stack is same that >> could help even more. > > Is photos ok or do you need text? Whatever, just let it be complete. >> This is on i386? >> > > yes > -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Paul B. Mahol wrote: On 5/12/09, Chris Whitehouse wrote: Paul B. Mahol wrote: Just typing bt on db prompt for now should be enough. panic: sleeping thread cpuid = 0 KDB: enter: panic [thread pid 1497 tid 100073 ] Stopped atkdb_enter+0x3a: movl$0,kdb_why db> bt Tracing pid 1497 tid 100073 td 0xc356c900 kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d4001b68,0,...) at kdb_enter+0x3a panic(c0c42726,,0,cc,4,...) at panic+0x136 propagate_priority(c0d9df84,0,c0c4249e,2e1,c356d180,...) at propagate_priority+0x18c turnstile_wait(c356d180,c37b2240,0,18d,c34fc06c,...) at turnstile_wait+0x44d _mtx_lock_sleep(c34fc06c,c356c900,0,c38de072,6b4,...) at mtx_lock_sleep+0x18e _mtx_lock_flags(c34fc06c,0,c38de072,6b4,c089dc98,...) at mtx_lock_flags+0xf7 ndis_ticktask(c3821700,c34fc000,c37e8e3c,c3916bd0,c38fc6e0,...) at ndis_ticktask+0x3a _end(c37e8e3c,d4001d38,c0c39438,333,c37ab548,...) at _end+0x321d fork_exit(c38fc600,c37e8e3c,d4001d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0 esp = 0xd4001d70, ebp = 0 --- Typed by hand but I'm pretty sure it is correct. Don't know if it is significant but repeating the panic gave quite a few different values. Post them too. If only numbers are different and stack is same that could help even more. Is photos ok or do you need text? This is on i386? yes ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
On 5/12/09, Chris Whitehouse wrote: > Paul B. Mahol wrote: >> >> Just typing bt on db prompt for now should be enough. > > panic: sleeping thread > cpuid = 0 > KDB: enter: panic > [thread pid 1497 tid 100073 ] > Stopped atkdb_enter+0x3a: movl$0,kdb_why > db> bt > Tracing pid 1497 tid 100073 td 0xc356c900 > kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d4001b68,0,...) at kdb_enter+0x3a > panic(c0c42726,,0,cc,4,...) at panic+0x136 > propagate_priority(c0d9df84,0,c0c4249e,2e1,c356d180,...) at > propagate_priority+0x18c > turnstile_wait(c356d180,c37b2240,0,18d,c34fc06c,...) at turnstile_wait+0x44d > _mtx_lock_sleep(c34fc06c,c356c900,0,c38de072,6b4,...) at > mtx_lock_sleep+0x18e > _mtx_lock_flags(c34fc06c,0,c38de072,6b4,c089dc98,...) at mtx_lock_flags+0xf7 > ndis_ticktask(c3821700,c34fc000,c37e8e3c,c3916bd0,c38fc6e0,...) at > ndis_ticktask+0x3a > _end(c37e8e3c,d4001d38,c0c39438,333,c37ab548,...) at _end+0x321d > fork_exit(c38fc600,c37e8e3c,d4001d38) at fork_exit+0xb8 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0 esp = 0xd4001d70, ebp = 0 --- > > > Typed by hand but I'm pretty sure it is correct. > > Don't know if it is significant but repeating the panic gave quite a few > different values. Post them too. If only numbers are different and stack is same that could help even more. This is on i386? -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Paul B. Mahol wrote: Just typing bt on db prompt for now should be enough. panic: sleeping thread cpuid = 0 KDB: enter: panic [thread pid 1497 tid 100073 ] Stopped atkdb_enter+0x3a: movl$0,kdb_why db> bt Tracing pid 1497 tid 100073 td 0xc356c900 kdb_enter(c0c3d8fa,c0c3d8fa,c0c42726,d4001b68,0,...) at kdb_enter+0x3a panic(c0c42726,,0,cc,4,...) at panic+0x136 propagate_priority(c0d9df84,0,c0c4249e,2e1,c356d180,...) at propagate_priority+0x18c turnstile_wait(c356d180,c37b2240,0,18d,c34fc06c,...) at turnstile_wait+0x44d _mtx_lock_sleep(c34fc06c,c356c900,0,c38de072,6b4,...) at mtx_lock_sleep+0x18e _mtx_lock_flags(c34fc06c,0,c38de072,6b4,c089dc98,...) at mtx_lock_flags+0xf7 ndis_ticktask(c3821700,c34fc000,c37e8e3c,c3916bd0,c38fc6e0,...) at ndis_ticktask+0x3a _end(c37e8e3c,d4001d38,c0c39438,333,c37ab548,...) at _end+0x321d fork_exit(c38fc600,c37e8e3c,d4001d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0 esp = 0xd4001d70, ebp = 0 --- Typed by hand but I'm pretty sure it is correct. Don't know if it is significant but repeating the panic gave quite a few different values. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
On 5/11/09, Chris Whitehouse wrote: > Paul B. Mahol wrote: >> On 5/8/09, Chris Whitehouse wrote: >>> Paul B. Mahol wrote: On 5/7/09, Chris Whitehouse wrote: > In the meantime I've tried the three possible drivers (XP, NT and an > unlabelled one). I've also installed a recent 8-current snapshot, > updated to latest source and built world, and tried the XP driver. > Still > get interrupt storms everywhere, also a panic (I think) in 8-current. > > Should I give up or are there other things to try? Panic should not happen. Please provide backtrace(or crashdump or textdump) >>> `fetch http://www.fishercroft.plus.com/vmcore.1.gz' should get a >>> crashdump from a non-debug kernel, see below. It's about 17mb >>> >>> I built a driver with the XP driver using ndisgen and the same source as >>> my recent build world. >>> >>> I kldload the driver module which also loads ndis.ko and if_ndis.ko. >>> >>> I've got >>> wlans_ndis0="wlan0" >>> in rc.conf and I get ndis0 and wlan0 created when I plug in the card. >>> >>> The interrupt storm starts when I do >>> >>> # ifconfig wlan0 >>> >>> The panic occurs maybe a minute or two after the ifconfig. >>> >>> I got a panic but I couldn't get a crashdump with the GENERIC kernel >>> (nothing relevant to dumpon or savecore happened at all, no boot >>> messages, nothing in /var/crash). >>> I did get a bunch of stuff on ttyv0, I can post a photo somewhere if >>> required. Or is there a way to get the screen output in text format? >>> >>> I built a kernel with the following changes >>> >>> #cpuI486_CPU >>> #cpuI586_CPU >>> >>> #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug >> >> Oh no, crash dump is useless with that option commented in kernel. >> [You can alway just look at documentation installed in /usr/share/doc/, >> for example developers handbook] >> >>> symbols >>> >>> #optionsKDB # Enable kernel debugger support. >>> #optionsDDB # Support DDB. >>> #optionsGDB # Support remote GDB. >>> #optionsINVARIANTS # Enable calls of extra sanity >>> checking >>> #optionsINVARIANT_SUPPORT # Extra sanity checks of >>> internal structures, required by INVARIANTS >>> #optionsWITNESS # Enable checks to detect >>> deadlocks and cycles >>> #optionsWITNESS_SKIPSPIN# Don't run witness on spinlocks >>> for speed >> Both KDB, DDB, GDB, WITNESS and INVARIANTS are usefull in debugging >> kernel. >> So please uncomment all that debugging support. >> After all you can build two kernels, and use boot loader command or >> nextboot(8) >> > I tried with GENERIC and with my no-debug kernel. The panic happened > with both but there was no crashdump with the GENERIC. All other > settings were the same, eg no change to rc.conf. My setup seems to be > right according to the developers handbook section 10.1. > > Is there something special I have to do with -CURRENT to get the crashdump? Just typing bt on db prompt for now should be enough. > >>> >>> >>> I got on ttyv0: >>> >>> interrupt storm detected on "irq11:"; throttling interrupt source >>> >>> repeated about 20 times then >>> >>> Sleeping thread (tid 100084, pid 0) owns a non-sleepable lock >> >> Heh, thats is bug, now only remains to find where it is caused. >> > I got this screendump (copied and pasted) from ttyv0 before the panic > with GENERIC. It was repeated maybe 20 times then dropped to db> prompt. > > interrupt storm detected on "irq11:"; throttling interrupt source > Waiting on "KeWFS" with the following non-sleepable locks held: > exclusive sleep mutex ndis0 (network driver) r = 0 (0xc34fd06c) locked @ > /usr/sr > c/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:3432 > KDB: stack backtrace: > db_trace_self_wrapper(c0c40c0b,d40e3ac0,c089d245,c3888072,d68,...) at > db_trace_s > elf_wrapper+0x26 > kdb_backtrace(c3888072,d68,,c0eca774,d40e3af8,...) at > kdb_backtrace+0x29 > > _witness_debugger(c0c42f9c,d40e3b0c,4,1,0,...) at _witness_debugger+0x25 > witness_warn(5,c38a24d0,c0c37d7c,c389ea81,d40e3b3c,...) at > witness_warn+0x1fd > _cv_timedwait(d40e3b6c,c38a24d0,1389,,c38cafc8,...) at > _cv_timedwait+0xc > 6 > KeWaitForSingleObject(c38cafc0,0,0,0,d40e3bbc,...) at > KeWaitForSingleObject+0x1b > 0 > ndis_set_info(c34fd000,d01011a,0,d40e3bf8,c37b2524,...) at > ndis_set_info+0x1c8 > ndis_scan_start(c3a14000,0,c0c5286b,36e,80246,...) at ndis_scan_start+0xe8 > scan_task(c3a04800,1,c0c42357,54,c38c485c,...) at scan_task+0x150 > taskqueue_run(c38c4840,c38c485c,0,c0c33ff4,0,...) at taskqueue_run+0x10b > taskqueue_thread_loop(c3a14074,d40e3d38,c0c39438,333,c0d88ca0,...) at > taskqueue_ > thread_loop+0x68 > fork_exit(c08963e0,c3a14074,d40e3d38) at fork_exit+0xb8 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0, eip = 0, esp = 0xd40e3d70, ebp = 0 --- > interrupt storm detected
Re: ndis0 interrrupt storm
Paul B. Mahol wrote: On 5/8/09, Chris Whitehouse wrote: Paul B. Mahol wrote: On 5/7/09, Chris Whitehouse wrote: In the meantime I've tried the three possible drivers (XP, NT and an unlabelled one). I've also installed a recent 8-current snapshot, updated to latest source and built world, and tried the XP driver. Still get interrupt storms everywhere, also a panic (I think) in 8-current. Should I give up or are there other things to try? Panic should not happen. Please provide backtrace(or crashdump or textdump) `fetch http://www.fishercroft.plus.com/vmcore.1.gz' should get a crashdump from a non-debug kernel, see below. It's about 17mb I built a driver with the XP driver using ndisgen and the same source as my recent build world. I kldload the driver module which also loads ndis.ko and if_ndis.ko. I've got wlans_ndis0="wlan0" in rc.conf and I get ndis0 and wlan0 created when I plug in the card. The interrupt storm starts when I do # ifconfig wlan0 The panic occurs maybe a minute or two after the ifconfig. I got a panic but I couldn't get a crashdump with the GENERIC kernel (nothing relevant to dumpon or savecore happened at all, no boot messages, nothing in /var/crash). I did get a bunch of stuff on ttyv0, I can post a photo somewhere if required. Or is there a way to get the screen output in text format? I built a kernel with the following changes #cpuI486_CPU #cpuI586_CPU #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug Oh no, crash dump is useless with that option commented in kernel. [You can alway just look at documentation installed in /usr/share/doc/, for example developers handbook] symbols #optionsKDB # Enable kernel debugger support. #optionsDDB # Support DDB. #optionsGDB # Support remote GDB. #optionsINVARIANTS # Enable calls of extra sanity checking #optionsINVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS #optionsWITNESS # Enable checks to detect deadlocks and cycles #optionsWITNESS_SKIPSPIN# Don't run witness on spinlocks for speed Both KDB, DDB, GDB, WITNESS and INVARIANTS are usefull in debugging kernel. So please uncomment all that debugging support. After all you can build two kernels, and use boot loader command or nextboot(8) I tried with GENERIC and with my no-debug kernel. The panic happened with both but there was no crashdump with the GENERIC. All other settings were the same, eg no change to rc.conf. My setup seems to be right according to the developers handbook section 10.1. Is there something special I have to do with -CURRENT to get the crashdump? I got on ttyv0: interrupt storm detected on "irq11:"; throttling interrupt source repeated about 20 times then Sleeping thread (tid 100084, pid 0) owns a non-sleepable lock Heh, thats is bug, now only remains to find where it is caused. I got this screendump (copied and pasted) from ttyv0 before the panic with GENERIC. It was repeated maybe 20 times then dropped to db> prompt. interrupt storm detected on "irq11:"; throttling interrupt source Waiting on "KeWFS" with the following non-sleepable locks held: exclusive sleep mutex ndis0 (network driver) r = 0 (0xc34fd06c) locked @ /usr/sr c/sys/modules/if_ndis/../../dev/if_ndis/if_ndis.c:3432 KDB: stack backtrace: db_trace_self_wrapper(c0c40c0b,d40e3ac0,c089d245,c3888072,d68,...) at db_trace_s elf_wrapper+0x26 kdb_backtrace(c3888072,d68,,c0eca774,d40e3af8,...) at kdb_backtrace+0x29 _witness_debugger(c0c42f9c,d40e3b0c,4,1,0,...) at _witness_debugger+0x25 witness_warn(5,c38a24d0,c0c37d7c,c389ea81,d40e3b3c,...) at witness_warn+0x1fd _cv_timedwait(d40e3b6c,c38a24d0,1389,,c38cafc8,...) at _cv_timedwait+0xc 6 KeWaitForSingleObject(c38cafc0,0,0,0,d40e3bbc,...) at KeWaitForSingleObject+0x1b 0 ndis_set_info(c34fd000,d01011a,0,d40e3bf8,c37b2524,...) at ndis_set_info+0x1c8 ndis_scan_start(c3a14000,0,c0c5286b,36e,80246,...) at ndis_scan_start+0xe8 scan_task(c3a04800,1,c0c42357,54,c38c485c,...) at scan_task+0x150 taskqueue_run(c38c4840,c38c485c,0,c0c33ff4,0,...) at taskqueue_run+0x10b taskqueue_thread_loop(c3a14074,d40e3d38,c0c39438,333,c0d88ca0,...) at taskqueue_ thread_loop+0x68 fork_exit(c08963e0,c3a14074,d40e3d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xd40e3d70, ebp = 0 --- interrupt storm detected on "irq11:"; throttling interrupt source panic: sleeping thread cpuid = 0 Uptime:17m26s Physical memory: 434 MB Dumping 79 MB: 64 48 32 16 Dump complete (The above typed by hand) Let me know if there is more I can do but (caveat) I'm not a developer and I only put CURRENT on the machine to test if the problem had been fixed, ie please don't flame me if you ask me really difficult stuff and I don't understand it :) You can always
Re: ndis0 interrrupt storm
On 5/8/09, Chris Whitehouse wrote: > Paul B. Mahol wrote: >> On 5/7/09, Chris Whitehouse wrote: >> >>> In the meantime I've tried the three possible drivers (XP, NT and an >>> unlabelled one). I've also installed a recent 8-current snapshot, >>> updated to latest source and built world, and tried the XP driver. Still >>> get interrupt storms everywhere, also a panic (I think) in 8-current. >>> >>> Should I give up or are there other things to try? >> >> Panic should not happen. Please provide backtrace(or crashdump or >> textdump) > > `fetch http://www.fishercroft.plus.com/vmcore.1.gz' should get a > crashdump from a non-debug kernel, see below. It's about 17mb > > I built a driver with the XP driver using ndisgen and the same source as > my recent build world. > > I kldload the driver module which also loads ndis.ko and if_ndis.ko. > > I've got > wlans_ndis0="wlan0" > in rc.conf and I get ndis0 and wlan0 created when I plug in the card. > > The interrupt storm starts when I do > > # ifconfig wlan0 > > The panic occurs maybe a minute or two after the ifconfig. > > I got a panic but I couldn't get a crashdump with the GENERIC kernel > (nothing relevant to dumpon or savecore happened at all, no boot > messages, nothing in /var/crash). > I did get a bunch of stuff on ttyv0, I can post a photo somewhere if > required. Or is there a way to get the screen output in text format? > > I built a kernel with the following changes > > #cpuI486_CPU > #cpuI586_CPU > > #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug Oh no, crash dump is useless with that option commented in kernel. [You can alway just look at documentation installed in /usr/share/doc/, for example developers handbook] > symbols > > #optionsKDB # Enable kernel debugger support. > #optionsDDB # Support DDB. > #optionsGDB # Support remote GDB. > #optionsINVARIANTS # Enable calls of extra sanity > checking > #optionsINVARIANT_SUPPORT # Extra sanity checks of > internal structures, required by INVARIANTS > #optionsWITNESS # Enable checks to detect > deadlocks and cycles > #optionsWITNESS_SKIPSPIN# Don't run witness on spinlocks > for speed Both KDB, DDB, GDB, WITNESS and INVARIANTS are usefull in debugging kernel. So please uncomment all that debugging support. After all you can build two kernels, and use boot loader command or nextboot(8) > > > > I got on ttyv0: > > interrupt storm detected on "irq11:"; throttling interrupt source > > repeated about 20 times then > > Sleeping thread (tid 100084, pid 0) owns a non-sleepable lock Heh, thats is bug, now only remains to find where it is caused. > panic: sleeping thread > cpuid = 0 > Uptime:17m26s > Physical memory: 434 MB > Dumping 79 MB: 64 48 32 16 > Dump complete > > (The above typed by hand) > > Let me know if there is more I can do but (caveat) I'm not a developer > and I only put CURRENT on the machine to test if the problem had been > fixed, ie please don't flame me if you ask me really difficult stuff and > I don't understand it :) You can always ask me off list for anything that you don't understand. -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Paul B. Mahol wrote: On 5/7/09, Chris Whitehouse wrote: In the meantime I've tried the three possible drivers (XP, NT and an unlabelled one). I've also installed a recent 8-current snapshot, updated to latest source and built world, and tried the XP driver. Still get interrupt storms everywhere, also a panic (I think) in 8-current. Should I give up or are there other things to try? Panic should not happen. Please provide backtrace(or crashdump or textdump) `fetch http://www.fishercroft.plus.com/vmcore.1.gz' should get a crashdump from a non-debug kernel, see below. It's about 17mb I built a driver with the XP driver using ndisgen and the same source as my recent build world. I kldload the driver module which also loads ndis.ko and if_ndis.ko. I've got wlans_ndis0="wlan0" in rc.conf and I get ndis0 and wlan0 created when I plug in the card. The interrupt storm starts when I do # ifconfig wlan0 The panic occurs maybe a minute or two after the ifconfig. I got a panic but I couldn't get a crashdump with the GENERIC kernel (nothing relevant to dumpon or savecore happened at all, no boot messages, nothing in /var/crash). I did get a bunch of stuff on ttyv0, I can post a photo somewhere if required. Or is there a way to get the screen output in text format? I built a kernel with the following changes #cpuI486_CPU #cpuI586_CPU #makeoptionsDEBUG=-g# Build kernel with gdb(1) debug symbols #optionsKDB # Enable kernel debugger support. #optionsDDB # Support DDB. #optionsGDB # Support remote GDB. #optionsINVARIANTS # Enable calls of extra sanity checking #optionsINVARIANT_SUPPORT # Extra sanity checks of internal structures, required by INVARIANTS #optionsWITNESS # Enable checks to detect deadlocks and cycles #optionsWITNESS_SKIPSPIN# Don't run witness on spinlocks for speed I got on ttyv0: interrupt storm detected on "irq11:"; throttling interrupt source repeated about 20 times then Sleeping thread (tid 100084, pid 0) owns a non-sleepable lock panic: sleeping thread cpuid = 0 Uptime:17m26s Physical memory: 434 MB Dumping 79 MB: 64 48 32 16 Dump complete (The above typed by hand) Let me know if there is more I can do but (caveat) I'm not a developer and I only put CURRENT on the machine to test if the problem had been fixed, ie please don't flame me if you ask me really difficult stuff and I don't understand it :) uname -a FreeBSD eight.config 8.0-CURRENT FreeBSD 8.0-CURRENT #0: Fri May 8 11:20:35 BST 2009 r...@eight.config:/usr/obj/usr/src/sys/MYKERNEL i386 Thanks Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
On 5/7/09, Chris Whitehouse wrote: > Tim Judd wrote: >> I think project evil (ndis) requires a specific driver version, such as >> the >> WinXP drivers versus the Vista or 2000 or anything else. >> >> >> >> What drivers did you use? Any other drivers available on the manufacturer >> website? >> >> >> If you're not using XP, I recall reading that XP is the preferred driver >> for >> the recent project evil versions. >> >> >> --TJ >> ___ >> freebsd-questions@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to >> "freebsd-questions-unsubscr...@freebsd.org" >> > Sorry about the delay replying, I've been away. > > In the meantime I've tried the three possible drivers (XP, NT and an > unlabelled one). I've also installed a recent 8-current snapshot, > updated to latest source and built world, and tried the XP driver. Still > get interrupt storms everywhere, also a panic (I think) in 8-current. > > Should I give up or are there other things to try? Panic should not happen. Please provide backtrace(or crashdump or textdump) -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Tim Judd wrote: I think project evil (ndis) requires a specific driver version, such as the WinXP drivers versus the Vista or 2000 or anything else. What drivers did you use? Any other drivers available on the manufacturer website? If you're not using XP, I recall reading that XP is the preferred driver for the recent project evil versions. --TJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" Sorry about the delay replying, I've been away. In the meantime I've tried the three possible drivers (XP, NT and an unlabelled one). I've also installed a recent 8-current snapshot, updated to latest source and built world, and tried the XP driver. Still get interrupt storms everywhere, also a panic (I think) in 8-current. Should I give up or are there other things to try? Thanks Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Tim Judd wrote: I think project evil (ndis) requires a specific driver version, such as the WinXP drivers versus the Vista or 2000 or anything else. What drivers did you use? Any other drivers available on the manufacturer website? If you're not using XP, I recall reading that XP is the preferred driver for the recent project evil versions. --TJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org" I believe I read about XP being preferred as well. I downloaded the latest drivers zip file from the linksys website, it includes 3 drivers for this chipset, a generic one, one for NT and one for XP. I used the XP one. I might try the others just in case but I am away for afew days so won't be able to have another look till next week. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Paul B. Mahol wrote: On 5/2/09, Paul B. Mahol wrote: On 5/1/09, Chris Whitehouse wrote: Paul B. Mahol wrote: On 4/29/09, Chris Whitehouse wrote: Hi all I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a Marvell 8335 chip. I've created a module with ndisgen and I can see ndis0. When I up it with ifconfig I immediately get repeated messages: Apr 28 23:23:19 pcbsd kernel: interrupt storm detected on "irq11:"; throttling interrupt source As soon as I down the interface the messages stop. I've also tried starting ndis0 with polling # ifconfig ndis0 inet 192.168.1.20 polling but still get the messages. I guess this driver doesn't support polling. Or I've got the syntax wrong. That command is not currently efective at all for ndisX(I yet have to see if it is possible). According to vmstat -i irq11 is used by cbb0 and pcm0. ndis0 is on irq9 irq9: cbb1 ndis0++ This is on PCBSD 7.1 which is FreeBSD 7.2-PRERELEASE Any way I can get this thing working? Try yo disable cbbX if you dont use it or enable MSI for pcm0 (if possible). This is a pcmcia card in a laptop so cbb is needed :( There is no reference to msi in the pcm man page so I guess it is not available for this system. (Paul I saw a post from you on multimedia about msi in hdac and sure enough there is a reference to msi in snd_hda(4) man page). Am I looking in the right place? msi for snd_hda(if that is your sound driver) should be enabled by default on CURRENT (dunno about 7): hint.hdac.%d.msi=1 my driver is snd_t4dwave and msi is not mentioned in the man page. Does that mean it's not available? You could try to use different dev.ndis.0.InterruptNumber for ndis0. Changing it via sysctl is not supported, you will need to modify right line(s) in inf file, or in .h file generated with ndiscvt(1) via ndisgen(8) Dunno if that will work (never tried) Tried, doesnt work. Polling could be enabled if miniport driver for your card supports it, look output of sysctl dev.ndis.0 no reference to polling in sysctl dev.ndis hmm not looking good so far Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
On 5/2/09, Paul B. Mahol wrote: > On 5/1/09, Chris Whitehouse wrote: >> Paul B. Mahol wrote: >>> On 4/29/09, Chris Whitehouse wrote: Hi all I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a Marvell 8335 chip. I've created a module with ndisgen and I can see ndis0. When I up it with ifconfig I immediately get repeated messages: Apr 28 23:23:19 pcbsd kernel: interrupt storm detected on "irq11:"; throttling interrupt source As soon as I down the interface the messages stop. I've also tried starting ndis0 with polling # ifconfig ndis0 inet 192.168.1.20 polling but still get the messages. I guess this driver doesn't support polling. Or I've got the syntax wrong. >>> >>> That command is not currently efective at all for ndisX(I yet have to >>> see if it is possible). >>> According to vmstat -i irq11 is used by cbb0 and pcm0. ndis0 is on irq9 irq9: cbb1 ndis0++ This is on PCBSD 7.1 which is FreeBSD 7.2-PRERELEASE Any way I can get this thing working? >>> >>> Try yo disable cbbX if you dont use it or enable MSI for pcm0 (if >>> possible). >> >> This is a pcmcia card in a laptop so cbb is needed :( There is no >> reference to msi in the pcm man page so I guess it is not available for >> this system. (Paul I saw a post from you on multimedia about msi in hdac >> and sure enough there is a reference to msi in snd_hda(4) man page). Am >> I looking in the right place? > > msi for snd_hda(if that is your sound driver) should be enabled by default > on CURRENT (dunno about 7): > hint.hdac.%d.msi=1 > > You could try to use different dev.ndis.0.InterruptNumber for ndis0. > Changing it via sysctl is not supported, you will need to modify right > line(s) > in inf file, or in .h file generated with ndiscvt(1) via ndisgen(8) > > Dunno if that will work (never tried) Tried, doesnt work. Polling could be enabled if miniport driver for your card supports it, look output of sysctl dev.ndis.0 -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
I think project evil (ndis) requires a specific driver version, such as the WinXP drivers versus the Vista or 2000 or anything else. What drivers did you use? Any other drivers available on the manufacturer website? If you're not using XP, I recall reading that XP is the preferred driver for the recent project evil versions. --TJ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
On 5/1/09, Chris Whitehouse wrote: > Paul B. Mahol wrote: >> On 4/29/09, Chris Whitehouse wrote: >>> Hi all >>> >>> I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a >>> Marvell 8335 chip. I've created a module with ndisgen and I can see >>> ndis0. When I up it with ifconfig I immediately get repeated messages: >>> >>> Apr 28 23:23:19 pcbsd kernel: interrupt storm detected on "irq11:"; >>> throttling interrupt source >>> >>> As soon as I down the interface the messages stop. >>> >>> I've also tried starting ndis0 with polling >>> >>> # ifconfig ndis0 inet 192.168.1.20 polling >>> >>> but still get the messages. I guess this driver doesn't support polling. >>> Or I've got the syntax wrong. >> >> That command is not currently efective at all for ndisX(I yet have to >> see if it is possible). >> >>> According to vmstat -i irq11 is used by cbb0 and pcm0. ndis0 is on irq9 >>> >>> irq9: cbb1 ndis0++ >>> >>> This is on PCBSD 7.1 which is FreeBSD 7.2-PRERELEASE >>> >>> Any way I can get this thing working? >> >> Try yo disable cbbX if you dont use it or enable MSI for pcm0 (if >> possible). > > This is a pcmcia card in a laptop so cbb is needed :( There is no > reference to msi in the pcm man page so I guess it is not available for > this system. (Paul I saw a post from you on multimedia about msi in hdac > and sure enough there is a reference to msi in snd_hda(4) man page). Am > I looking in the right place? msi for snd_hda(if that is your sound driver) should be enabled by default on CURRENT (dunno about 7): hint.hdac.%d.msi=1 You could try to use different dev.ndis.0.InterruptNumber for ndis0. Changing it via sysctl is not supported, you will need to modify right line(s) in inf file, or in .h file generated with ndiscvt(1) via ndisgen(8) Dunno if that will work (never tried) -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
Paul B. Mahol wrote: On 4/29/09, Chris Whitehouse wrote: Hi all I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a Marvell 8335 chip. I've created a module with ndisgen and I can see ndis0. When I up it with ifconfig I immediately get repeated messages: Apr 28 23:23:19 pcbsd kernel: interrupt storm detected on "irq11:"; throttling interrupt source As soon as I down the interface the messages stop. I've also tried starting ndis0 with polling # ifconfig ndis0 inet 192.168.1.20 polling but still get the messages. I guess this driver doesn't support polling. Or I've got the syntax wrong. That command is not currently efective at all for ndisX(I yet have to see if it is possible). According to vmstat -i irq11 is used by cbb0 and pcm0. ndis0 is on irq9 irq9: cbb1 ndis0++ This is on PCBSD 7.1 which is FreeBSD 7.2-PRERELEASE Any way I can get this thing working? Try yo disable cbbX if you dont use it or enable MSI for pcm0 (if possible). This is a pcmcia card in a laptop so cbb is needed :( There is no reference to msi in the pcm man page so I guess it is not available for this system. (Paul I saw a post from you on multimedia about msi in hdac and sure enough there is a reference to msi in snd_hda(4) man page). Am I looking in the right place? The bios is minimal so can't turn off sound or one channel of cbb. Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
Re: ndis0 interrrupt storm
On 4/29/09, Chris Whitehouse wrote: > Hi all > > I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a > Marvell 8335 chip. I've created a module with ndisgen and I can see > ndis0. When I up it with ifconfig I immediately get repeated messages: > > Apr 28 23:23:19 pcbsd kernel: interrupt storm detected on "irq11:"; > throttling interrupt source > > As soon as I down the interface the messages stop. > > I've also tried starting ndis0 with polling > > # ifconfig ndis0 inet 192.168.1.20 polling > > but still get the messages. I guess this driver doesn't support polling. > Or I've got the syntax wrong. That command is not currently efective at all for ndisX(I yet have to see if it is possible). > According to vmstat -i irq11 is used by cbb0 and pcm0. ndis0 is on irq9 > > irq9: cbb1 ndis0++ > > This is on PCBSD 7.1 which is FreeBSD 7.2-PRERELEASE > > Any way I can get this thing working? Try yo disable cbbX if you dont use it or enable MSI for pcm0 (if possible). -- Paul ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
ndis0 interrrupt storm
Hi all I'm trying to get a Linksys WPC54Gv5 wireless pccard working. It has a Marvell 8335 chip. I've created a module with ndisgen and I can see ndis0. When I up it with ifconfig I immediately get repeated messages: Apr 28 23:23:19 pcbsd kernel: interrupt storm detected on "irq11:"; throttling interrupt source As soon as I down the interface the messages stop. I've also tried starting ndis0 with polling # ifconfig ndis0 inet 192.168.1.20 polling but still get the messages. I guess this driver doesn't support polling. Or I've got the syntax wrong. According to vmstat -i irq11 is used by cbb0 and pcm0. ndis0 is on irq9 irq9: cbb1 ndis0++ This is on PCBSD 7.1 which is FreeBSD 7.2-PRERELEASE Any way I can get this thing working? Thanks Chris ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"
