Opened 11 years ago

Closed 2 years ago

Last modified 14 months ago

#5474 closed bug (not reproducible)

[kernel] PANIC: got an in use page 0x8107c040 from the free pages list

Reported by: diver Owned by: mmlr
Priority: high Milestone:
Component: System/Kernel Version: R1/Development
Keywords: port heap Cc:
Blocked By: Blocking: #5864, #6960, #8025, #10498
Platform: All


I was playing with HaikuLauncher and Arora comparing site rendering when I got this panic.
Observed with hrev35610 in VirtualBox 3.0.12

Attachments (2)

kdl.png (32.2 KB ) - added by diver 11 years ago.
KDL.JPG (130.3 KB ) - added by humdinger 9 years ago.
another one of that sort

Download all attachments as: .zip

Change History (22)

by diver, 11 years ago

Attachment: kdl.png added

comment:1 by axeld, 11 years ago

Owner: changed from axeld to mmlr
Status: newassigned

I got that, too, a few weeks ago (which led me to add the page address to the panic).

comment:2 by mmlr, 11 years ago

BTW just to avoid any misunderstandings the page in this case isn't a page in the VM page sense, it is a heap "page" which is a part of a heap area. In any case since this is only happening in the port code it's probably an edge case the separate port heap exposes. It might just be an unfortunate heap config for example. Can take a look in any case. As always a reproducible test case would be very much appreciated of course.

comment:3 by bonefish, 11 years ago

Blocking: 5864 added

(In #5864) Duplicate of #5474.

comment:4 by bonefish, 11 years ago

Milestone: R1R1/alpha2

comment:5 by bonefish, 11 years ago

Keywords: port heap added

comment:6 by scottmc, 10 years ago

Milestone: R1/alpha3R1/beta1

comment:7 by bonefish, 10 years ago

Blocking: 6960 added

(In #6960) Duplicate of 5474.

comment:8 by bonefish, 10 years ago

Blocking: 8025 added

(In #8025) Replying to humdinger:

Attached the KDL and a backtrace, which looks almost identical...

They should, as the back traces are just started from different points within the kernel debugger. Unless the automatic back trace wraps and isn't fully readable, there's no need to add another one.

Anyway, closing as dup of #5474.

comment:9 by humdinger, 9 years ago

Got another one of those: "PANIC: got an in use page 0x001b7040 from the free page list".
Attaching KDL pic here, just in case. Sorry, it's blurry as hell...

by humdinger, 9 years ago

Attachment: KDL.JPG added

another one of that sort

comment:10 by bonefish, 7 years ago

Blocking: 10498 added

(In #10498) Duplicate of #5474.

comment:11 by ttcoder, 7 years ago

Cc: degea@… added

comment:12 by kallisti5, 7 years ago

Milestone: R1/beta1R1/alpha5
Priority: normalhigh

comment:13 by pulkomandy, 7 years ago

Milestone: R1/alpha5R1/beta1

comment:14 by pulkomandy, 6 years ago

Last time this was reported is hrev45824, 1.5 years ago. Does it still happen?

comment:15 by diver, 6 years ago

Dunno but #10498 was closed 12 months ago as a dupe of this one.

comment:16 by ttcoder, 6 years ago

But that was with my (back then) months-old setup so 12 months + n months = 1.5 years makes perfect sense yes.

Anyway, zero report whatsoever since that occurence here (neither from me, dsuden, or clients).

PS - can an admin please un-Cc me (wether this gets closed or not regardless) as I use the Cc property to know which tickets I want to keep on my 'radar screen', and this one I no longer need, thanks. Or maybe that kind of operation needs to be done with a separate email, please kindly tell me how if so.

Last edited 6 years ago by ttcoder (previous) (diff)

comment:17 by pulkomandy, 6 years ago

Cc: degea@… removed

comment:18 by pulkomandy, 6 years ago

Milestone: R1/beta1R1

Moving out of beta1 then, not happening often enough to be troublesome I think.

comment:19 by waddlesplash, 2 years ago

Resolution: not reproducible
Status: assignedclosed

No more reports since that one, so that's 5.5 years with nobody seeing this. Closing as not reproducible.

comment:20 by nielx, 14 months ago

Milestone: R1

Remove milestone for tickets with status = closed and resolution != fixed

Note: See TracTickets for help on using tickets.