Opened 12 years ago

Closed 12 years ago

#1547 closed bug (invalid)

Panic in vfs_mount_boot_file_system()

Reported by: korli Owned by: axeld
Priority: critical Milestone: R1
Component: System/Kernel Version: R1/pre-alpha1
Keywords: Cc: bonefish
Blocked By: Blocking:
Has a Patch: no Platform: All


KDiskSystem::Unload(): partitioning_systems/session/v1 -> 0 KDiskDeviceManager::_AddDiskSystem() done: No error file system: file_systems/cdda/v1 KDiskDeviceManager::_AddDiskSystem(file_systems/cdda/v1) KDiskSystem::Load(): file_systems/cdda/v1 -> 1 KDiskSystem::Unload(): file_systems/cdda/v1 -> 0 KDiskDeviceManager::_AddDiskSystem() done: No error vm_soft_fault: va 0xe182f320 not covered by area in address space vm_page_fault: vm_soft_fault returned error 'Bad address' on fault at 0xe182f320, ip 0x800a2a33, write 0, user 0, thread 0x8 PANIC: vm_page_fault: unhandled page fault in kernel space at 0xe182f320, ip 0x800a2a33

Welcome to Kernel Debugging Land... Running on CPU 0 kdebug> bt stack trace for thread 0x8 "main2"

kernel stack: 0x800fa000 to 0x800fe000

frame caller <image>:function + offset 800fd828 (+ 52) 8008c1eb <kernel>:invoke_command + 0x0073 800fd85c (+ 48) 8008c332 <kernel>:kernel_debugger_loop + 0x0102 800fd88c (+ 32) 8008cd8e <kernel>:kernel_debugger + 0x00b6 800fd8ac (+ 192) 8008cccd <kernel>:panic + 0x0029 800fd96c (+ 64) 8005d936 <kernel>:vm_page_fault + 0x00a6 800fd9ac (+ 176) 800955ca <kernel>:i386_handle_trap + 0x023a iframe at 0x800fda64 (end = 0x800fdab8)

eax 0xe182f320 ebx 0xc ecx 0x90a2b850 edx 0x90a3c200 esi 0x800fdb48 edi 0x90a2e01e ebp 0x800fdac8 esp 0x800fda94 eip 0x800a2a33 eflags 0x210206 vector: 0xe, error code: 0x0

800fda5c (+ 108) 800a2a33 <kernel>:strncmp + 0x0023 800fdac8 (+ 144) 8002ff75 <kernel>:iterator_get_next_moduleFP15module_iteratorPcPUl + 0x0439 800fdb58 (+ 64) 800306e4 <kernel>:read_next_module_name + 0x0044 800fdb98 (+ 64) 8007b558 <kernel>:_RescanDiskSystemsQ38BPrivate10DiskDevice18KDiskDeviceManagerb + 0x0064 800fdbd8 (+ 64) 8007b66c <kernel>:RescanDiskSystemsQ38BPrivate10DiskDevice18KDiskDeviceManager + 0x0028 800fdc18 (+ 816) 8005553a <kernel>:vfs_mount_boot_file_system + 0x018a 800fdf48 (+ 144) 8002f255 <kernel>:main2 + 0x00d1 800fdfd8 (+ 32) 8003de57 <kernel>:_create_kernel_thread_kentryFv + 0x001b 800fdff8 (+2146443272) 8003ddec <kernel>:thread_kthread_exitFv + 0x0000 kdebug>

Change History (5)

comment:1 by korli, 12 years ago

Cc: bonefish added
Priority: normalcritical

comment:2 by mmlr, 12 years ago

I had the exact same thing over here. Traced it down to the leftover "dos" filesystem add-on if you update an existing installation. If you remove "/boot/beos/system/add-ons/kernel/filesystems/dos" booting works as usual. But obviously it'd be nice if the crash could be avoided.

comment:3 by bonefish, 12 years ago

It's not really possible to avoid crashing in this situation. The FS and partitioning system module API changed and since we don't want to increment the interface version number with every change during development, the kernel has no way of knowing that a module is obsolete.

comment:4 by jackburton, 12 years ago

Should this be marked as Invalid ?

comment:5 by bonefish, 12 years ago

Resolution: invalid
Status: newclosed
Note: See TracTickets for help on using tickets.