syncing failed on shutdown: giving up on 1 buffer

Tim Legant tim at catseye.net
Thu Nov 25 18:51:35 PST 2004


On Fri, 2004-11-19 at 16:18 -0800, Matthew Dillon wrote:

> Raphael Marmier wrote:

> :After which, I /sbin/reboot:
> :
> :# /sbin/reboot
> :boot() called on cpu#1
> :Waiting (max 60 seconds) for system thread vnlru to stop...stopped
> :Waiting [...] bufdaemon to stop...stopped
> :Waiting [...] syncer to stop...stopped
> :
> :syncing disks... 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
> :giving up on 1 buffers
> :Debugger("busy buffer problem")

>     We get reports of this occuring occassionally on SMP system and we
>     haven't quite figured out the cause yet.  If this is repeatable on
>     your system and you can get a kernel core out of it that would be 
>     helpful (make sure you are compiling up debug kernels, which we have
>     a default in GENERIC so you should be unless you removed the makeoptions
>     line for it).

It's (mostly) repeatable and, since no one else seems to have replied,
here's a link to a core and dmesg.

http://www.catseye.net/~thl/DragonFly/

Also, I have no idea if this will help but...  The following text is
what showed up on the console as the core dump ended.

6 5 4 3 2 1 0 error2 0
succeeded
LWKT_WAIT_IPQ WARNING! 1 wait 0 (-6)
panic: LWKT_WAIT_IPQ
mp_lock = 00000001; cpuid = 1; lapic.id = 00000000
boot() called on cpu#1
Uptime: 2m7s
Dump already in progress, bailing...
LWKT_WAIT_IPQ WARNING! 1 wait 0 (-7)
panic: LWKT_WAIT_IPQ
mp_lock = 00000001; cpuid = 1; lapic.id = 00000000
boot() called on cpu#1
Uptime: 2m7s
Dump already in progress, bailing...
LWKT_WAIT_IPQ WARNING! 1 wait 0 (-8)
panic: LWKT_WAIT_IPQ
mp_lock = 00000001; cpuid = 1; lapic.id = 00000000
boot() called on cpu#1
Uptime: 2m7s
Dump already in progress, bailing...

If you need anything else from me, up to and including ssh access, just
let me know.


Tim







More information about the Kernel mailing list