[kernel] vm_page_fault: block notifier/writer

[diver]

Since some revisions (2-3 days) Haiku running in VirtualBox start to drop to KDL after several minutes.

[diver]

It seems that I can't add attachments to Trac. Oh well..

[axeld]

Please save it until that annoying Trac problem is resolved, thanks!

[diver]

With recent revision back trace became much shorter:

PANIC: vm_page_fault: unhandled page fault in kernel space at 0x1, ip 0x800033c90

Welcome to Kernel Debugging Land...
Thread 143 "w>Deskbar "
kernel stack : 0x90b73000 to 0x90b77000[[BR]]user stack : 0x700c3000 to 0x70103000
frame caller <image>:function + offset

[*** READ FAULT at 0x80059b19, pc: 0x80035200 ***]

[axeld]

At least the stack crawl should now look better again. Apart from that, it seems like the crawl of the last comment doesn't have much in common with the previous one.

I'm using VirtualBox myself on my laptop, and never saw anything like this either (also I used version 2.0.2 until today). Is there anything special you are doing to reproduce this problem?

[diver]

Replying to axeld:

Is there anything special you are doing to reproduce this problem?

Nope, it just hanged when I leaved it running for some time (about 10 min.) Also with recent revision it survived about an hour until i shutdown VirtualBox myself. So it could be fixed already, I will retest and post back my results.

[diver]

Ok, I left Haiku running in VirtualBox 2.0.2 today morning and now, 7 hours later, it still running. So I think we could close this bug, I'll reopen it if I have this crash again.

[axeld]

Okay, thanks for the update.

[diver]

Happens to me again in hrev28510.

[axeld]

This problem could have been caused by a bug I fixed in hrev28516 - please retry with a version later than that one.

[diver]

Another crash in 28524.

[axeld]

With what stack trace, please?

[diver]

I'm trying to get one, but VirtualBox doesn't let me get to vm showing guru mediatation error. I'll try again.

[diver]

Here you are.

[diver]

Oh now, it's not about block notifier/writer which i got earler today.

[axeld]

(In #3108) This seems to be a duplicate of #2845

[axeld]

The stack trace you posted doesn't look good at all, and might very well be a VirtualBox problem.

The one from #3108 looks related to this problem, though. In any case, I'm not bumping this to R1/alpha unless this happens on real hardware (I've never seen this yet, and I'm using VirtualBox on my laptop as well).

[diver]

It seems like a bug in VirtualBox, see ​http://www.virtualbox.org/ticket/2588

[Adek336]

hrev28884 on real hardware when using Transmission, 9 minutes uptime, syslog has "kernel thread accessing invalid user memory", I was able to suspend the thread and continue although not very well (Deskbar froze, command sync in terminal wouldn't finish, could not open new terminal tab; on the other hand, transmission was still able to download)

[Adek336]

Happened two more times, perhaps induced by heavy syslog traffic.

[diver]

I still can reproduce it in vbox 2.0.2, but not under vmware.

[diver]

Can't reproduce it anymore in VirtualBox 3.0.4

[Disreali]

I am experiencing this issue when testing hrev32402 with VirtualBox 3.0.4-hrev50677 on Windows Vista host. I'll get less than thirty or so minutes and it kdl's. Each time it kdl's I had been checking e-mail on yahoo, so I thought it may have been bezilla, but umccullough directed me here.

[Disreali]

No longer experiencing this issue with hrev32448. Though, from reading this ticket, the issue seems to come and go depending on the haiku revision.

[Disreali]

I was running Haiku R1A1 hrev32991 in VirualBox 3.0.4. I had Virtualbox in the background for a minute or two and whan I went back to it, Haiku had crashed. mmlr tried to help debug.

Copied from duplicate ticket: see ticket:4449 for screenshots

[bonefish]

There's a chance that hrev34655 fixes the problem. Closing. Please reopen if the issue persists.