[haiku-bugs] Re: [Haiku] #5878: [I/O Scheduler] rw_lock_read_unlock(): lock not read-locked
- From: "bonefish" <trac@xxxxxxxxxxxx>
- Date: Sun, 02 May 2010 13:52:19 -0000
#5878: [I/O Scheduler] rw_lock_read_unlock(): lock not read-locked
---------------------------+------------------------------------------------
Reporter: damoklas | Owner: axeld
Type: bug | Status: new
Priority: normal | Milestone: R1/alpha2
Component: System/Kernel | Version: R1/Development
Keywords: | Blockedby:
Platform: All | Blocking:
---------------------------+------------------------------------------------
Comment(by bonefish):
Mmh, I've never seen this myself before. I wonder why it happens so often
on your machine. Could you add a syslog from directly after booting,
please. Did you do anything special with respect to disks? Any USB disk
plugging/unplugging?
When you run into the bug next, it would be great, if you could execute a
few more kernel debugger commands that might provide helpful info. When
you have a look at the stack trace, there are lines containing
{{{IORequest<...>}}} with a green number between the pointy braces. Two
different numbers in in total. For each of them please execute the
following:
- {{{io_request <request>}}} (replace <request> by the number).
- {{{io_request_owner <owner>}}} (replace <owner> by the number the first
command printed after {{{owner:}}}, unless that was 0x00000000).
BTW, in most cases when being dropped into KDL a stack trace is printed
automatically -- if that one is fully visible, there's no need to type
"bt" in such a case.
--
Ticket URL: <http://dev.haiku-os.org/ticket/5878#comment:3>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
