[haiku-bugs] [Haiku] #7555: Reproducible kernel panic while backing up to NFS
- From: "dstromberg" <trac@xxxxxxxxxxxx>
- Date: Sun, 22 May 2011 20:06:15 -0000
#7555: Reproducible kernel panic while backing up to NFS
--------------------------+-------------------------
Reporter: dstromberg | Owner: nobody
Type: bug | Status: new
Priority: normal | Milestone: R1
Component: File Systems | Version: R1/alpha3
Keywords: | Blocked By:
Blocking: | Has a Patch: 0
Platform: x86 |
--------------------------+-------------------------
Hi.
I have a reproducible kernel panic, using Haiku R1 Alpha 3 -r 41650 - IOW,
a very recent nightly build. I'm running it in VirtualBox 3.2.8 OSE
r64453 with an emulated, bridged Intel Pro/1000 MT Desktop 82540EM network
adapter.
When it happens, I'm testing a backup engine written in CPython, using an
unmodified /boot/common/bin/python. This code is at
http://stromberg.dnsalias.org/~dstromberg/backshift/
The engine reads and writes an NFS filesystem. Some of the directories
are quite large.
Running the engine's automated tests against a local filesystem (created
by the installer) works well, despite a plethora of such tests.
The script tracebacks on an os.fsync(), and then crashes. If I skip the
fsync with the equivalent of "if os.uname()[0] != 'Haiku'", it still
crashes, but without a (Python) traceback (or rather, no Python traceback
until I type "co" in the kernel debugger).
Haiku enters KDL of its own volition.
I'm very inexperienced with BeOS/Haiku, and only slightly experienced with
VirtualBox - what's the best way to get information to you, the kernel
developers, for such a crash?
I'll be attaching a screenshot with the kernel traceback.
Thanks!
--
Ticket URL: <http://dev.haiku-os.org/ticket/7555>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.
Other related posts:
