Bug #1989

Panic on reboot, DFly 2.8.2

Added by dl almost 4 years ago. Updated almost 4 years ago.

Status:NewStart date:
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-

Description

Hi!

I have had my DFly [1] server running for almost 2 months, and after
trying to reboot it, it panicked:

I let the memory dump to hd and ran kgdb:

root@pick:/var/crash# kgdb kern.2 vmcore.2
GNU gdb (GDB) 7.0
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-dragonfly".
For bug reporting instructions, please see:
<http://bugs.dragonflybsd.org/&gt;...
Reading symbols from /var/crash/kern.2...done.

Unread portion of the kernel message buffer:

Reading symbols from /boot/kernel/acpi.ko...done.
Loaded symbols for /boot/kernel/acpi.ko
Reading symbols from /boot/kernel/ahci.ko...done.
Loaded symbols for /boot/kernel/ahci.ko
Reading symbols from /boot/kernel/ehci.ko...done.
Loaded symbols for /boot/kernel/ehci.ko
_get_mycpu (di=0xffffffff808d4a20) at ./machine/thread.h:73
73 __asm ("movq %%gs:globaldata,%0" : "=r" (gd) : "m"(__mycpu__dummy));
(kgdb) bt
#0 _get_mycpu (di=0xffffffff808d4a20) at ./machine/thread.h:73
#1 md_dumpsys (di=0xffffffff808d4a20)
at /usr/src/sys/platform/pc64/x86_64/dump_machdep.c:262
#2 0xffffffff80363d26 in dumpsys () at
/usr/src/sys/kern/kern_shutdown.c:881
#3 0xffffffff80364415 in boot (howto=-2004318071)
at /usr/src/sys/kern/kern_shutdown.c:388
#4 0xffffffff803647e6 in panic (fmt=0xffffffff806287d4 "from debugger")
at /usr/src/sys/kern/kern_shutdown.c:787
#5 0xffffffff801920d5 in db_panic (addr=<value optimized out>,
have_addr=0, count=0, modif=0x0) at /usr/src/sys/ddb/db_command.c:448
#6 0xffffffff8019278b in db_command () at /usr/src/sys/ddb/db_command.c:344
#7 db_command_loop () at /usr/src/sys/ddb/db_command.c:470
#8 0xffffffff80195551 in db_trap (type=<value optimized out>,
code=<value optimized out>) at /usr/src/sys/ddb/db_trap.c:71
#9 0xffffffff805f39a0 in kdb_trap (type=3, code=0, regs=0xffffffe07cc6a6b8)
at /usr/src/sys/platform/pc64/x86_64/db_interface.c:176
#10 0xffffffff805f9591 in trap (frame=0xffffffe07cc6a6b8)
at /usr/src/sys/platform/pc64/x86_64/trap.c:706
#11 0xffffffff805f1f5e in calltrap ()
at /usr/src/sys/platform/pc64/x86_64/exception.S:180
#12 0xffffffff805f3835 in breakpoint (msg=<value optimized out>)
at ./cpu/cpufunc.h:73
#13 Debugger (msg=<value optimized out>)
4/db_interface.c:359
#14 0xffffffff803647df in panic (fmt=0xffffffff8061d2aa "assertion: %s
in %s")
at /usr/src/sys/kern/kern_shutdown.c:785
#15 0xffffffff80356288 in lf_destroy_range (range=<value optimized out>)
at /usr/src/sys/kern/kern_lockf.c:857
#16 0xffffffff80357052 in lf_setlock (lock=0xffffffe07bbe3240,
owner=0xffffffe07b34b068, type=2, flags=<value optimized out>,
start=0, end=9223372036854775807) at /usr/src/sys/kern/kern_lockf.c:747
#17 0xffffffff8035728a in lf_advlock (ap=0xffffffe07cc6a9c8,
lock=0xffffffe07bbe3240, size=<value optimized out>)
at /usr/src/sys/kern/kern_lockf.c:263
#18 0xffffffff80559c84 in hammer_vop_advlock (ap=0xffffffff809798b8)
at /usr/src/sys/vfs/hammer/hammer_vnops.c:847
#19 0xffffffff803e1582 in vop_advlock (ops=0xffffffe0534277c0, vp=0x780,
id=0x1 <Address 0x1 out of bounds>, op=0, fl=0x0, flags=-2137548576)
at /usr/src/sys/kern/vfs_vopops.c:909
#20 0xffffffff80346fb4 in fdrop (fp=0xffffffe07b34b068)
at /usr/src/sys/kern/kern_descrip.c:2418
#21 0xffffffff803472dd in closef (fp=0xffffffe07b34b068,
p=0xffffffe052640070)
at /usr/src/sys/kern/kern_descrip.c:2362
#22 0xffffffff80349c99 in kern_close (fd=3)
at /usr/src/sys/kern/kern_descrip.c:857
#23 0xffffffff80349dac iat /usr/src/sys/kern/kern_descrip.c:816
#24 0xffffffff805f9df9 in syscall2 (frame=0xffffffe07cc6abf8)
at /usr/src/sys/platform/pc64/x86_64/trap.c:1179
#25 0xffffffff805f219f in Xfast_syscall ()
at /usr/src/sys/platform/pc64/x86_64/exception.S:313
#26 0x000000000000002b in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
n sys_close (uap=<value optimized out>)

Any ideas what could have gone wrong?
For reference I put the memory dump temporarily online (~1GB BZIP2 +
Kernel) here:
http://pick.xiqit.de/vmcore.2.bz2 ~988M
http://pick.xiqit.de/kern.2.bz2 ~14M

In case more information is needed, don't hesitate to contact me!

Thanks,
Damian

[1]: root@pick:/usr/pkg/share/httpd/htdocs# uname -a
DragonFly pick 2.8-RELEASE DragonFly v2.8.2.7.g0d8fd-RELEASE #3: Tue Nov
2 15:24:24 CET 2010 root@pick:/usr/obj/usr/src/sys/X86_64_GENERIC_SMP
x86_64

History

#1 Updated by y0n3t4n1 almost 4 years ago

:
> #15 0xffffffff80356288 in lf_destroy_range (range=<value optimized out>)
> at /usr/src/sys/kern/kern_lockf.c:857
> #16 0xffffffff80357052 in lf_setlock (lock=0xffffffe07bbe3240,
> owner=0xffffffe07b34b068, type=2, flags=<value optimized out>,
> start=0, end=9223372036854775807) at
> /usr/src/sys/kern/kern_lockf.c:747

Apparently a fix has been added to DragonFly_RELEASE_2_8 branch:
http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/20b10249803190a9d3299b2e6f2a71c4fe2918e4

> [1]: root@pick:/usr/pkg/share/httpd/htdocs# uname -a
> DragonFly pick 2.8-RELEASE DragonFly v2.8.2.7.g0d8fd-RELEASE #3: Tue
> Nov 2 15:24:24 CET 2010
> root@pick:/usr/obj/usr/src/sys/X86_64_GENERIC_SMP x86_64

In fact there have been many fixes after this version(0d8fd):
http://gitweb.dragonflybsd.org/dragonfly.git/shortlog/refs/heads/DragonFly_RELEASE_2_8

Cheers.

#2 Updated by dl almost 4 years ago

Am 15.02.2011 um 14:00 schrieb YONETANI Tomokazu:

> On Tue, Feb 15, 2011 at 02:24:35AM +0100, Damian Lubosch wrote:
> :
>> #15 0xffffffff80356288 in lf_destroy_range (range=<value optimized out>)
>> at /usr/src/sys/kern/kern_lockf.c:857
>> #16 0xffffffff80357052 in lf_setlock (lock=0xffffffe07bbe3240,
>> owner=0xffffffe07b34b068, type=2, flags=<value optimized out>,
>> start=0, end=9223372036854775807) at
>> /usr/src/sys/kern/kern_lockf.c:747
>
> Apparently a fix has been added to DragonFly_RELEASE_2_8 branch:
> http://gitweb.dragonflybsd.org/dragonfly.git/commitdiff/20b10249803190a9d3299b2e6f2a71c4fe2918e4
>

Hi Tomokazu!

Thanks for the hint! I updated the sources to most recent DragonFly_RELEASE_2_8 and compiled an new kernel.

Best regards
Damian

#3 Updated by tuxillo almost 4 years ago

Hi Damian,

Was this solved eventually with the upgrade to the newest 2.8.2 or whatever you did?

Cheers,
Antonio Huete

#4 Updated by dl almost 4 years ago

>
> Antonio Huete Jimenez <> added the comment:
>
> Hi Damian,
>
> Was this solved eventually with the upgrade to the newest 2.8.2 or
> whatever you did?
>
> Cheers,
> Antonio Huete
>
> ----------
> priority: -> bug
>

Hi Antonio,

It was solved after I applied the most recent kernel patches from the
Stable Release.

Best regards,
Damian

Also available in: Atom PDF