LOR's wi ad0 and so on

Daniel Dvořák dandee at hellteam.net
Wed Aug 24 19:25:35 GMT 2005


I found out that if I do this:
ifconfig vr0 down
reboot
than it is okay and this sleeping locks does not cause kernel panic, which
normally happens when I do not do "ifconfig vr0 down" command.
I mean it does not appear in /var/log/messages too.

Dan 

-----Original Message-----
From: owner-freebsd-current at freebsd.org
[mailto:owner-freebsd-current at freebsd.org] On Behalf Of Daniel Dvořák
Sent: Wednesday, August 24, 2005 4:51 PM
To: freebsd-current at freebsd.org
Subject: RE: LOR's wi ad0 and so on

Hi,

thank you for recommendation and finaly I have compared my LOR´s with your
list of reported LOR´s.

I will send one strange in this e-mail, which may be it is not LOR, but it
has same format like LOR and this is the most serious, because twice time
when it was logged in messages, always it was accompanied with kernel panic
after boot or shutdown -r now commands. The others LOR´s I will send in
another e-mail.

Dan

Sleeping on "itrmh" with the following non-sleepable locks held:
exclusive sleep mutex vr0 (network driver) r = 0 (0xc15d8938) locked @
/usr/src/sys/pci/if_vr.c:806
KDB: stack backtrace:
kdb_backtrace(c08cbbf4,d1432a28,1,c1615600,c198c624) at kdb_backtrace+0x2e
witness_warn(5,c155dc80,c07d9494,c07d6679,80246) at witness_warn+0x1d3
msleep(c1615600,c155dc80,a0,c07d6679,0) at msleep+0x62
ithread_remove_handler(c1615600,d1432a90,c0787071,c1615600,d1432ab8) at
ithread_remove_handler+0x155
intr_remove_handler(c1615600,d1432ab8,c05896d5,c155d100,c15e2d80) at
intr_remove_handler+0x11
nexus_teardown_intr(c155d100,c15e2d80,c1615b80,c1615600,c15e2d80) at
nexus_teardown_intr+0x11
bus_generic_teardown_intr(c15e2380,c15e2d80,c1615b80,c1615600,c15e2d80) at
bus_generic_teardown_intr+0x75
bus_generic_teardown_intr(c15e1e80,c15e2d80,c1615b80,c1615600,c15e2d80) at
bus_generic_teardown_intr+0x75
bus_generic_teardown_intr(c15e2780,c15e2d80,c1615b80,c1615600,c15e2d80) at
bus_generic_teardown_intr+0x75
bus_teardown_intr(c15e2d80,c1615b80,c1615600,326,c1620800) at
bus_teardown_intr+0x72
vr_detach(c15e2d80,d1432b7c,c05889bf,c15e2d80,c1581028) at vr_detach+0x114
vr_shutdown(c15e2d80,c1581028,c0824378) at vr_shutdown+0x11
device_shutdown(c15e2d80,c15e2780,d1432ba4,c05889bf,c15e2780) at
device_shutdown+0x4f
bus_generic_shutdown(c15e2780,c15bb028,c0824378) at
bus_generic_shutdown+0x28
device_shutdown(c15e2780,c15e1e80,d1432bcc,c05889bf,c15e1e80) at
device_shutdown+0x4f
bus_generic_shutdown(c15e1e80,c15ba028,c0824378) at
bus_generic_shutdown+0x28
device_shutdown(c15e1e80,c15e2380,d1432bf4,c09e79d5,c15e2380) at
device_shutdown+0x4f
bus_generic_shutdown(c15e2380,1,c0a02e3d,2a2,d1432c0c) at
bus_generic_shutdown+0x28
acpi_shutdown(c15e2380,c15bf828,c0824378) at acpi_shutdown+0x35
device_shutdown(c15e2380,c155d100,d1432c34,c05889bf,c155d100) at
device_shutdown+0x4f
bus_generic_shutdown(c155d100,c15a4828,c0824378) at
bus_generic_shutdown+0x28
device_shutdown(c155d100,c155d580,d1432c5c,c05889bf,c155d580) at
device_shutdown+0x4f
bus_generic_shutdown(c155d580,c157b028,c0824378) at
bus_generic_shutdown+0x28
device_shutdown(c155d580,c1520000,c152000c,d1432c88,c05634c5) at
device_shutdown+0x4f
root_bus_module_handler(c1528200,2,0,c1503aa0,d1432cbc) at
root_bus_module_handler+0xcf
module_shutdown(0,0,c07d8cd9,190,0) at module_shutdown+0x55
boot(0,0,c07d8cd9,a1,d1432d30) at boot+0x690
reboot(c198e300,d1432d04,4,421,1) at reboot+0x46
syscall(3b,3b,3b,0,4e) at syscall+0x2c0
Xint0x80_syscall() at Xint0x80_syscall+0x1f
--- syscall (55, FreeBSD ELF32, reboot), eip = 0x280ac07b, esp = 0xbfbfec2c,
ebp = 0xbfbfec78 ---
panic: sleeping thread (tid 100097) owns a non-sleepable lock cpuid = 0
KDB: enter: panic





-----Original Message-----
From: owner-freebsd-current at freebsd.org
[mailto:owner-freebsd-current at freebsd.org] On Behalf Of Bjoern A. Zeeb
Sent: Monday, August 22, 2005 7:01 AM
To: dandee at volny.cz
Cc: freebsd-current at freebsd.org
Subject: Re: LOR's wi ad0 and so on

On Sun, 21 Aug 2005, [iso-8859-2] Daniel Dvo?ák wrote:

Hi,

> I returned from my holidays and watch log. Many lock order reversal is 
> present in my system with beta 1.
>
> Maybe I am barking up the wrong tree. If so I am sorry for spamming.
>
> But I think that somebody maybe want to see it, so I am sending this:
>
> roztyly# uname -a
>
> FreeBSD roztyly.jspoj.czf 6.0-BETA1 FreeBSD 6.0-BETA1 #0: Sun Jul 17
> 22:10:34 CEST 2005
stayd at roztyly.jspoj.czf:/usr/obj/usr/src/sys/ROZTYLY
> i386

[lots of almost unreadable logfile lines]

> There are many more lor´s, but they repeat in same way like that.


The logfiles pasted in are almost unreadable because of duplicate line
breaks etc.

Could you please check with
	http://sources.zabbadoz.net/freebsd/lor.html
and only report those LORs that are not listed there.

If mailing please check that your MUA doesn't do duplicate line breaks and
line wraps for the LOR parts... You may also leave out syslog prefixes
(timestamp, hostname, ..) if possible.


Thanks.

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
_______________________________________________
freebsd-current at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"

-----Original Message-----
From: owner-freebsd-current at freebsd.org
[mailto:owner-freebsd-current at freebsd.org] On Behalf Of Bjoern A. Zeeb
Sent: Monday, August 22, 2005 7:01 AM
To: dandee at volny.cz
Cc: freebsd-current at freebsd.org
Subject: Re: LOR's wi ad0 and so on

On Sun, 21 Aug 2005, [iso-8859-2] Daniel Dvo?ák wrote:

Hi,

> I returned from my holidays and watch log. Many lock order reversal is 
> present in my system with beta 1.
>
> Maybe I am barking up the wrong tree. If so I am sorry for spamming.
>
> But I think that somebody maybe want to see it, so I am sending this:
>
> roztyly# uname -a
>
> FreeBSD roztyly.jspoj.czf 6.0-BETA1 FreeBSD 6.0-BETA1 #0: Sun Jul 17
> 22:10:34 CEST 2005
stayd at roztyly.jspoj.czf:/usr/obj/usr/src/sys/ROZTYLY
> i386

[lots of almost unreadable logfile lines]

> There are many more lor´s, but they repeat in same way like that.


The logfiles pasted in are almost unreadable because of duplicate line
breaks etc.

Could you please check with
	http://sources.zabbadoz.net/freebsd/lor.html
and only report those LORs that are not listed there.

If mailing please check that your MUA doesn't do duplicate line breaks and
line wraps for the LOR parts... You may also leave out syslog prefixes
(timestamp, hostname, ..) if possible.


Thanks.

-- 
Bjoern A. Zeeb				bzeeb at Zabbadoz dot NeT
_______________________________________________
freebsd-current at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"

_______________________________________________
freebsd-current at freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"



More information about the freebsd-current mailing list