search

oscarmore2 / macfuse

Automatically exported from code.google.com/p/macfuse
Other
0 stars 0 forks source link

Kernel panic #90

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
This is probably not a macfuse issue, but I hadn't had anything like a
kernel panic before, and I wasn't doing anything notable when it happened.
 I figured that it was better to report it since I can't read the error report.

I installed macfuse a few days ago, and haven't used it yet.  At the time
of the crash I was just typing some notes in TextMate.

panic(cpu 1 caller 0x001A3135): Unresolved kernel trap (CPU 1, Type 14=page
fault), registers:
CR0: 0x8001003b, CR2: 0x0000001c, CR3: 0x016e3000, CR4: 0x000006e0
EAX: 0x00000000, EBX: 0x0000001c, ECX: 0x025f7000, EDX: 0x0000085f
CR2: 0x0000001c, EBP: 0x0bee3fa8, ESI: 0x0085ed40, EDI: 0x00000001
EFL: 0x00010246, EIP: 0x00141a75, CS:  0x00000008, DS:  0x0bee0010

Backtrace, Format - Frame : Return Address (4 potential args on stack) 
0xbee3d88 : 0x128d1f (0x3c9540 0xbee3dac 0x131df4 0x0) 
0xbee3dc8 : 0x1a3135 (0x3cf1f4 0x1 0xe 0x3cea24) 
0xbee3ed8 : 0x19a8d4 (0xbee3ee8 0x1d47d48 0xe 0x190048) 
0xbee3fa8 : 0x178c44 (0x178be8 0x0 0x0 0x1fc00000) 
0xbee3fc8 : 0x19a74c (0x1 0x0 0x19d0b5 0x31a5dc4) Backtrace
terminated-invalid frame pointer 0x0

Kernel version:
Darwin Kernel Version 8.8.1: Mon Sep 25 19:42:00 PDT 2006;
root:xnu-792.13.8.obj~1/RELEASE_I386

Model: MacBook1,1, BootROM MB11.0061.B03, 2 processors, Intel Core Duo,
1.83 GHz, 512 MB
Graphics: Intel GMA 950, GMA 950, Built-In, spdisplays_integrated_vram
Memory Module: BANK 0/DIMM0, 256 MB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 256 MB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x168C, 0x86), 0.1.30
Bluetooth: Version 1.7.9f12, 2 service, 0 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: TOSHIBA MK6034GSX, 55.89 GB
Parallel ATA Device: MATSHITACD-RW  CW-8221
USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12
Mb/sec, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA

Original issue reported on code.google.com by ric...@gmail.com on 5 Feb 2007 at 7:29

GoogleCodeExporter commented 9 years ago 
Just installing MacFUSE shouldn't cause a kernel panic. In fact, even if you do 
use MacFUSE, it doesn't do 
anything unless you have a MacFUSE volume mounted currently.

Based on your kernel version, your panic looks like a result of the following 
function call chain:

panic() <- kernel_trap() <- lo_alltraps() <- vm_pageout_continue() <- 
call_continuation() ...

The rest is garbled, but this tells us enough to conclude that this is the 
vm_pageout() path and the kernel died 
on a page fault. This is sometimes a result of bad hardware (RAM or disk) -- 
not always, but since nothing of 
note was apparently happening here, bad hardware *could* be the cause. Then 
again, in such complex 
systems, there can be bugs anywhere too.

Original comment by si...@gmail.com on 5 Feb 2007 at 8:13

GoogleCodeExporter commented 9 years ago 
Marking this as "invalid" because it's apparently unrelated to MacFUSE. 
Nevertheless, please keep reporting 
anything that's plausibly suspicious.

Original comment by si...@gmail.com on 5 Feb 2007 at 10:18