Opened 8 years ago

Closed 8 years ago

#8448 closed bug (fixed)

[kernel] PANIC: acquire_spinlock(): Failed to acquire spinlock 0x8019a3ec for a long time!

Reported by: diver Owned by: bonefish
Priority: normal Milestone: R1
Component: System/Kernel Version: R1/Development
Keywords: Cc: mr.Noisy
Blocked By: Blocking:
Has a Patch: no Platform: All

Description (last modified by diver)

This is hrev43952 gcc2hybrid. Freshly initialized BFS partiton.

installoptionalpackage python subversion
wget http://ports-space.haiku-files.org/dev-util/bakefile-0.2.8-x86-gcc2-2010-07-15.zip
unzip bakefile-0.2.8-x86-gcc2-2010-07-15.zip -d /boot
svn co http://svn.osdrawer.net/wx-haiku
cd wx-haiku/wx/trunk
./rebake.sh

Several seconds later haiku freezes followed by KDL after another several seconds.
During "svn co" I got these messages in syslog:

KERN: slab memory manager: created area 0xf4001000 (114331)
KERN: slab memory manager: created area 0xf4801000 (117476)
KERN: slab memory manager: created area 0xf5001000 (120514)
KERN: bfs: InitCheck:314: Bad data
KERN: bfs: inode at 11307 is already deleted!
KERN: bfs: InitCheck:314: Bad data
KERN: bfs: inode at 11307 is already deleted!
KERN: slab memory manager: created area 0xf5801000 (187973)
KERN: slab memory manager: created area 0xf6001000 (188095)
KERN: slab memory manager: created area 0xf6801000 (188100)
KERN: slab memory manager: created area 0xf7001000 (188104)
KERN: slab memory manager: created area 0xf7801000 (188115)

Attachments (5)

bakefile-0.2.8-x86-gcc2-2010-07-15.zip (607.8 KB ) - added by diver 8 years ago.
IMG_0004.JPG (1.8 MB ) - added by diver 8 years ago.
KDL
IMG_0006.JPG (3.0 MB ) - added by diver 8 years ago.
syslog from KDL
IMG_0010.JPG (1.8 MB ) - added by diver 8 years ago.
bt 8226
IMG_0013.JPG (1.8 MB ) - added by diver 8 years ago.
bt 8227

Change History (11)

by diver, 8 years ago

Attachment: IMG_0004.JPG added

KDL

by diver, 8 years ago

Attachment: IMG_0006.JPG added

syslog from KDL

comment:1 by diver, 8 years ago

kdebug> spinlock 0x8019a3ec
spinlock 0x8019a3ec:
  locked 0x800655a9
kdebug> ls 0x800655a9
0x800655a9 = switch_sem_etc + 0x1b5 (kernel_x86)
kdebug>

comment:2 by diver, 8 years ago

Cc: mr.Noisy added

comment:3 by bonefish, 8 years ago

An ls for the spinlock itself would be interesting, too. And a stack trace of the thread holding the spinlock. It should be running ATM (running). Is this reproducible?

The BFS inode corruptions might be interesting for Axel.

comment:4 by diver, 8 years ago

Description: modified (diff)
kdebug> ls 0x8019a3ec
0x8019a3ec = gSchedulerLock + 0x0 (kernel_x86)

kdebug> running
thread          id    state   wait for   object  cpu pri   stack       team  name
0xf10bb100    8226  running           -            0  10   0x80798000  8226  python
0xf10bacb0    8227  running           -            1  10   0x80790000  8227  python

This is reproducible, but this time there were no bfs errors apart from bfs_read_link:1501: Invalid Argument.

by diver, 8 years ago

Attachment: IMG_0010.JPG added

bt 8226

by diver, 8 years ago

Attachment: IMG_0013.JPG added

bt 8227

comment:5 by bonefish, 8 years ago

Status: newin-progress

Problem understood. Working on it...

comment:6 by bonefish, 8 years ago

Resolution: fixed
Status: in-progressclosed

Should be fixed in hrev43955.

Note: See TracTickets for help on using tickets.