Reproducible kernel panic while backing up to NFS
|Reported by:||dstromberg||Owned by:||nobody|
|Has a Patch:||no||Platform:||x86|
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 hrev64453 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() != '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.