FileVault 2 seems to be causing kernel boot panics

Hello,
I'm on a 10.8.2 Mountain Lion OS X (13-inch, Mid 2010), no new updates are available. I turned on FileVault 2 a few months ago and since then I've had a lot of kernel panics while booting. Sometimes it just booted ok and sometimes it panicked. Sometimes even twice in a row. Sometimes it created a crash report, sometimes it did not.
This is actually a clean-ish install, it's not an upgrade from Lion. I don't use Parallels Desktop or VMware as other threads sometimes mention. I don't use any NTFS driver. Although I do have Flash Player, GPGPreferences, Growl and Java plugins installed (I don't know if they have anything to do with those drivers).
Before I turned the Vault on, no boot panics.
After I turned it on, sometimes panic, sometimes not, couldn't find any system in it. About 50 % chance of a crash.
After I turned it back off, no panics so far.
So I turned it off today and tried restarting about twenty times (shut downs, restarts) and no kernel panic so far. I also installed Memtest and had it run in single user mode once and everything was ok.
I have three very similar general protection fault reports, I'm going to post the latest one here but if anyone wants to take a look at the other ones, please let me know.
Problem is I don't know if this is my hardware error or FileVault error.
Thank you,
Ollie
Interval Since Last Panic Report:  127214 sec
Panics Since Last Report:          2
Anonymous UUID:                    [edited]
Wed Dec  5 09:07:48 2012
panic(cpu 0 caller 0xffffff80004b7bd5): Kernel trap at 0xffffff800042d507, type 13=general protection, registers:
CR0: 0x000000008001003b, CR2: 0x00007fff9513f578, CR3: 0x00000000030cb000, CR4: 0x0000000000000660
RAX: 0xffffff800b26c550, RBX: 0xffffff800b26c550, RCX: 0xffffff807859bfc0, RDX: 0xffffff8078598000
RSP: 0xffffff807859be00, RBP: 0xffffff807859be40, RSI: 0x01ffff800b02e550, RDI: 0xffffff800b26c550
R8:  0xffffff800b26c550, R9:  0xffffffffffffffff, R10: 0x00000000ffffffff, R11: 0x00000000ffffff80
R12: 0xffffff8072dcd000, R13: 0x0000000000000000, R14: 0x01ffff800b02e550, R15: 0x0000000000000000
RFL: 0x0000000000010086, RIP: 0xffffff800042d507, CS:  0x0000000000000008, SS:  0x0000000000000000
Fault CR2: 0x00007fff9513f578, Error code: 0x0000000000000000, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff807859baa0 : 0xffffff800041d626
0xffffff807859bb10 : 0xffffff80004b7bd5
0xffffff807859bce0 : 0xffffff80004ce4ed
0xffffff807859bd00 : 0xffffff800042d507
0xffffff807859be40 : 0xffffff800042e74f
0xffffff807859bec0 : 0xffffff800042da0c
0xffffff807859bf00 : 0xffffff800041c7f7
0xffffff807859bf20 : 0xffffff7f8143463f
0xffffff807859bf40 : 0xffffff7f8142dad5
0xffffff807859bf60 : 0xffffff800043dcde
0xffffff807859bfb0 : 0xffffff80004b26b7
      Kernel Extensions in backtrace:
         com.apple.driver.AppleUSBHub(5.2.5)[A70C7553-FFEA-355F-A292-6E2B0023FADD]@0xffffff7f8142b000->0xffffff7f8143ffff
            dependency: com.apple.iokit.IOUSBFamily(5.4.0)[C3094550-7F58-3933-A4F7-CD33AE83F8B9]@0xffffff7f812bb000
BSD process name corresponding to current thread: kernel_task
Boot args: -v
Mac OS version:
Not yet set
Kernel version:
Darwin Kernel Version 12.2.0: Sat Aug 25 00:48:52 PDT 2012; root:xnu-2050.18.24~1/RELEASE_X86_64
Kernel UUID: 69A5853F-375A-3EF4-9247-478FD0247333
Kernel slide:     0x0000000000200000
Kernel text base: 0xffffff8000400000
System model name: MacBookPro7,1 (Mac-F222BEC8)
System uptime in nanoseconds: 1905729740
last loaded kext at 1757726027: com.apple.driver.AppleUSBTCButtons  235.4 (addr 0xffffff7f820f1000, size 20480)
loaded kexts:
com.apple.driver.AppleUSBTCButtons  235.4
com.apple.driver.AppleIRController  320.15
com.apple.driver.AppleUSBTCKeyEventDriver 235.4
com.apple.driver.AppleUSBTCKeyboard 235.4
com.apple.driver.CoreStorageFsck  274.7
com.apple.driver.AppleUSBCardReader 3.1.0
com.apple.driver.AppleFileSystemDriver  3.0.1
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless 1.0.0d1
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib 1.0.0d1
com.apple.BootCache 34
com.apple.iokit.SCSITaskUserClient  3.5.1
com.apple.driver.XsanFilter 404
com.apple.iokit.IOAHCIBlockStorage  2.2.2
com.apple.iokit.AppleBCM5701Ethernet  3.2.5b3
com.apple.driver.AppleIntelCPUPowerManagementClient 196.0.0
com.apple.driver.AirPort.Brcm4331 602.15.22
com.apple.driver.AppleFWOHCI  4.9.6
com.apple.driver.AppleAHCIPort  2.4.1
com.apple.driver.AppleUSBHub  5.2.5
com.apple.driver.AppleUSBEHCI 5.4.0
com.apple.driver.AppleSmartBatteryManager 161.0.0
com.apple.driver.AppleUSBOHCI 5.2.5
com.apple.driver.AppleEFINVRAM  1.6.1
com.apple.driver.AppleRTC 1.5
com.apple.driver.AppleHPET  1.7
com.apple.driver.AppleACPIButtons 1.6
com.apple.driver.AppleSMBIOS  1.9
com.apple.driver.AppleACPIEC  1.6
com.apple.driver.AppleAPIC  1.6
com.apple.nke.applicationfirewall 4.0.39
com.apple.security.quarantine 2
com.apple.driver.AppleIntelCPUPowerManagement 196.0.0
com.apple.driver.AppleUSBMultitouch 235.7
com.apple.iokit.IOUSBHIDDriver  5.2.5
com.apple.iokit.IOSCSIBlockCommandsDevice 3.5.1
com.apple.iokit.IOUSBMassStorageClass 3.5.0
com.apple.driver.AppleUSBMergeNub 5.2.5
com.apple.driver.AppleUSBComposite  5.2.5
com.apple.driver.CoreStorage  274.7
com.apple.iokit.IOSCSIMultimediaCommandsDevice  3.5.1
com.apple.iokit.IOBDStorageFamily 1.7
com.apple.iokit.IODVDStorageFamily  1.7.1
com.apple.iokit.IOCDStorageFamily 1.7.1
com.apple.iokit.IOAHCISerialATAPI 2.5.0
com.apple.iokit.IOSCSIArchitectureModelFamily 3.5.1
com.apple.iokit.IOEthernetAVBController 1.0.2b1
com.apple.iokit.IO80211Family 500.15
com.apple.iokit.IONetworkingFamily  3.0
com.apple.iokit.IOFireWireFamily  4.5.5
com.apple.driver.AppleMCP89RootPortPM 1.11
com.apple.iokit.IOAHCIFamily  2.2.1
com.apple.iokit.IOUSBUserClient 5.2.5
com.apple.iokit.IOUSBFamily 5.4.0
com.apple.driver.NVSMU  2.2.9
com.apple.driver.AppleEFIRuntime  1.6.1
com.apple.iokit.IOHIDFamily 1.8.0
com.apple.iokit.IOSMBusFamily 1.1
com.apple.security.sandbox  220
com.apple.kext.AppleMatch 1.0.0d1
com.apple.security.TMSafetyNet  7
com.apple.driver.DiskImages 344
com.apple.iokit.IOStorageFamily 1.8
com.apple.driver.AppleKeyStore  28.21
com.apple.driver.AppleACPIPlatform  1.6
com.apple.iokit.IOPCIFamily 2.7.2
com.apple.iokit.IOACPIFamily  1.4
com.apple.kec.corecrypto  1.0
System Profile:
Model: MacBookPro7,1, BootROM MBP71.0039.B0E, 2 processors, Intel Core 2 Duo, 2.4 GHz, 4 GB, SMC 1.62f6
Graphics: NVIDIA GeForce 320M, NVIDIA GeForce 320M, PCI, 256 MB
Memory Module: BANK 0/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x384A53463235363634485A2D314731443120
Memory Module: BANK 1/DIMM0, 2 GB, DDR3, 1067 MHz, 0x802C, 0x384A53463235363634485A2D314731443120
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8D), Broadcom BCM43xx 1.0 (5.106.98.81.22)
Bluetooth: Version 4.0.9f33 10885, 2 service, 11 devices, 1 incoming serial ports
Network Service: Ethernet, Ethernet, en0
Serial ATA Device: Hitachi HTS545025B9SA02, 250.06 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: Built-in iSight, apple_vendor_id, 0x8507, 0x24600000 / 2
USB Device: Internal Memory Card Reader, apple_vendor_id, 0x8403, 0x26100000 / 2
USB Device: USB-PS/2 Optical Mouse, 0x046d  (Logitech Inc.), 0xc01e, 0x04100000 / 2
USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x06600000 / 5
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8213, 0x06610000 / 8
USB Device: IR Receiver, apple_vendor_id, 0x8242, 0x06500000 / 4
USB Device: USB Keyboard, 0x04f2  (Chicony Electronics Co., Ltd.), 0x0116, 0x06400000 / 3
USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0237, 0x06300000 / 2

There are other reports of kernel panics like this one with FileVault. The cause seems to be an OS bug that only affects certain models and/or aftermarket SSD's. Make sure your system is fully updated. If it is, the only workaround I know of is to deactivate FileVault.

Similar Messages

  • Airport causing kernel panics and kp in safe boot.

    Last week I got my first kernel panic in years. It happened while I was asleep and checking an extrenal drive for bad blocks with TechTool. It turns out that the drive indeed had bad blocks and found that the cpu was shut down when I awoke. I started up the computer and it wasn't able to stay on for more than 10 min max before the next kernel panic. I checked here for more advice on kernel panics and started to try to narrow the number of culprits. Everything was unplugged and still kp. Instaled a new drive with a week older system from Time Machine and still kp. Reset NVRAM and replaced pyhsical RAM and still kp. Removed the Airport Extreme card and still kp. Booted into Safe Mode after all of the previously mentioned and still kp. I'm now going to take the drive and swap it into another body that I have to see if the root is actually on the drive on the physical hardware of the cpu.
    I was interested in this thread and read all of the links that jpl posted. Airport causing Kernel Panic (?) Jason then replied that it had been solved due to a "permissions problem" I wish he gave more info on what exactly he did to resolve the problem as it's been almost a week now without any work being done for me.
    I've also noticed this very strange behavior that might shed some light onto the issue. When I open System Prefs and close the window there is a strange colored pattern that will always flash after the window has been closed. I tried to post it to my me page but for somereason it wouldn't play for me so there's that and the YouTube version too.
    https://www.me.com/gallery/#100008/Prefs%20Screen
    http://www.youtube.com/watch?v=2zrTt88YdBo
    In addition when the computer has started up and the system loads. Checking Activity Monitor shows that there are 50 or more threads active for the the kernel_task. Inspecting this doesn't seem to show any useful information.
    Finally here are a few of the recent crashes I hope that someone might be able to shed some light on this extremely frustrating problem for me.
    Tue Oct 25 18:54:16 2011
    panic(cpu 0 caller 0x000AE584): "Uncorrectable machine check: pc = 00000000000A388C, msr = 0000000000141000, dsisr = 42000000, dar = 0000000000272008\n" "  AsyncSrc = 0000000000000000, CoreFIR = 0000000000000000\n" "     L2FIR = 0000000000000000,  BusFir = 0000000080000000\n"@/SourceCache/xnu/xnu-1228/osfmk/ppc/trap.c:975
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AE584 0x000AE804 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x2fc12c80)
          PC=0x000A388C; MSR=0x00141000; DAR=0x00272008; DSISR=0x42000000; LR=0x000A37C8; R1=0x2E947B40; XCP=0x00000008 (0x200 - Machine check)
          Backtrace:
    0x00000000 0x000A09C8 0x0009E2EC 0x0006B3C0 0x0006C728 0x0003BE1C
             0x0029361C 0x0029364C 0x0030924C 0x000B24C8 0x00000000
       Exception state (sv=0x249dba00)
          PC=0x9195435C; MSR=0x0000F030; DAR=0x00272000; DSISR=0x42000000; LR=0x00001FA8; R1=0xBFFFFB00; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: PubSubAgent
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    Tue Oct 25 19:09:54 2011
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FFFFFFFF PC=0x0000000000040DE4
    Latest crash info for cpu 0:
       Exception state (sv=0x3c19ca00)
          PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
    Proceeding back via exception chain:
       Exception state (sv=0x3c19ca00)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x3297b500)
          PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: mdworker
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): copyin/out has no recovery point
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEB88 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x3c19ca00)
          PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
       Exception state (sv=0x3297b500)
          PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: mdworker
    Wed Oct 26 15:31:02 2011
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000000FFFFFFFF PC=0x0000000000040DE4
    Latest crash info for cpu 0:
       Exception state (sv=0x3c19ca00)
          PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
    Proceeding back via exception chain:
       Exception state (sv=0x3c19ca00)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x3297b500)
          PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: mdworker
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): copyin/out has no recovery point
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEB88 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x3c19ca00)
          PC=0x00040DE4; MSR=0x00001030; DAR=0xFFFFFFFF; DSISR=0x40000000; LR=0x00040D94; R1=0x33B63D50; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x0293EA14 0x0004147C 0x0001EB60 0x00025960 0x000B264C 0x00000000
       Exception state (sv=0x3297b500)
          PC=0x919419D8; MSR=0x0000D030; DAR=0x0073C000; DSISR=0x42000000; LR=0x91948900; R1=0xF00807A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: mdworker
    Wed Oct 26 22:17:42 2011
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000010 PC=0x0000000000082EF8
    Latest crash info for cpu 0:
       Exception state (sv=0x2514ea00)
          PC=0x00082EF8; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x00082ECC; R1=0x24F6BB60; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x00000000 0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718
             0x0006C728 0x00296378 0x0030924C 0x000B24C8 0x00000000
    Proceeding back via exception chain:
       Exception state (sv=0x2514ea00)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x2509d500)
          PC=0x9194AF64; MSR=0x0000D930; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE9A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEA90 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x2514ea00)
          PC=0x00082EF8; MSR=0x00009030; DAR=0x00000010; DSISR=0x40000000; LR=0x00082ECC; R1=0x24F6BB60; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x00000000 0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718
             0x0006C728 0x00296378 0x0030924C 0x000B24C8 0x00000000
       Exception state (sv=0x2509d500)
          PC=0x9194AF64; MSR=0x0000D930; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE9A0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Thu Oct 27 11:28:35 2011
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000004 PC=0x00000000000848E0
    Latest crash info for cpu 0:
       Exception state (sv=0x248ff500)
          PC=0x000848E0; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x000848AC; R1=0x30063BB0; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718 0x0006C728
             0x00296378 0x0030924C 0x000B24C8 0x00000000
    Proceeding back via exception chain:
       Exception state (sv=0x248ff500)
          previously dumped as "Latest" state. skipping...
       Exception state (sv=0x248fd280)
          PC=0x9194AF64; MSR=0x0000D030; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE7F0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Mac OS version:
    9A581
    Kernel version:
    Darwin Kernel Version 9.0.0: Tue Oct  9 21:37:58 PDT 2007; root:xnu-1228~1/RELEASE_PPC
    panic(cpu 0 caller 0xFFFF0003): 0x300 - Data access
    Latest stack backtrace for cpu 0:
          Backtrace:
             0x0009AD18 0x0009B6BC 0x00029DC4 0x000AEA90 0x000B22F8
    Proceeding back via exception chain:
       Exception state (sv=0x248ff500)
          PC=0x000848E0; MSR=0x00009030; DAR=0x00000004; DSISR=0x42000000; LR=0x000848AC; R1=0x30063BB0; XCP=0x0000000C (0x300 - Data access)
          Backtrace:
    0x000848C0 0x00077BD0 0x0007823C 0x0007920C 0x0006B718 0x0006C728
             0x00296378 0x0030924C 0x000B24C8 0x00000000
       Exception state (sv=0x248fd280)
          PC=0x9194AF64; MSR=0x0000D030; DAR=0xE1000000; DSISR=0x42000000; LR=0x9194CC90; R1=0xBFFFE7F0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: launchd
    Thanks in advance,
    Max

    My vision is pretty poor, still cant see it, but...
    At this point I think you should get Applejack...
    http://www.macupdate.com/info.php/id/15667/applejack
    After installing, reboot holding down CMD+s, (+s), then when the DOS like prompt shows, type in...
    applejack AUTO
    Then let it do all 6 of it's things.
    At least it'll eliminate some questions if it doesn't fix it.
    The 6 things it does are...
    Correct any Disk problems.
    Repair Permissions.
    Clear out Cache Files.
    Repair/check several plist files.
    Dump the VM files for a fresh start.
    Trash old Log files.
    First reboot will be slower, sometimes 2 or 3 restarts will be required for full benefit... my guess is files relying upon other files relying upon other files! :-)
    Disconnect the USB cable from any Uninterruptible Power Supply so the system doesn't shut down in the middle of the process.

  • RAID mirror with software utility caused kernel panic every time

    Using disc utility to make a mirror of 2 drives, click create and i get kernel panic and have to power off machine. if i try to start the machine with either of the two disks in it (together or individually) i get same kernel panic and have to power off.
    The disks are in an external storage array (sonnet d500). I have a second storage array with raided disks in and i have raided disk inside the mac too. these all work fine..
    originally 2 weeks ago i had the 2 disks working in a group of 4 disks set as a mirror of 2 striped disks. One disk in this setup failed and with this config you can never 'recover'or rebuild it - you get a degraded mirror and you can backup the data, but you must completely rebuild the raid again as the mirror of stripes never lets you add a new disk in again.period. not good.
    I replaced the failed disk and rebuilt the mirror of stripes. this lasted a day until a second disk failed (all 4 were bought at same time so i was kind of expecting that to happen once one failed).
    i replaced the second faulty hdd and thought about my disk usage and decided i would not make another mirror of stripes and i would make 2 mirrors instead for safe-ish storage and then transfer data to a striped raid set for editing from instead of direct from the mirror of stripes volume.
    i tried to delete the raid but got a kernel panic
    if i started the machine with any of the 4 disks i would get a kernel panic.
    i moved the disks one by one into an older G5 running Tiger and managed to erase the raid info on 2 of them. The two new ones had some strange raid info and the Tiger machien thought there was an extra disk in the machine and would not erase or partition or allow me to destroy the raid whatever i tried.
    I will be moving these now into an old XP PC to try to erase the boot records etc and erase them to be able to use them again in either mac pro or G5. painful..
    so.. i ended up with 2 erased drives and have 2 new drives with dodgy raid info that causes kernel panics on the leopard machine and wont go in the Tiger machine.
    The two erased drives are what ive now been trying to use in the mac pro to create a mirror - this now caused kernel panics when creating the mirror to start with and when installed in the machine at all. so i will be erasing them again in the tiger machine soon (its busy erasing with zeros another new disk that i added to the Tiger machine 2 weeks ago which seems to have some fault when raided!!! but thats another story).
    so.. is anyone else having problems with creating basic mirror in 10.5.4 or is it just me??
    i have a sonnet tempo e4p card with 2 external sata disk enclosures, latest firmware for the e4p card. all other previously existing raid volumes are working fine. i have one set of 2 striped disks, one set of 3 striped disks and one set of 2 stripes which are mirrored - all happy and working fine. but i cant make a new mirror of 2 disks...
    I phoned Apple support and they said all raid info was kept on the disk itself and nothing on the actual machine and suggested i take the machine to an apple care centre for some tlc (although its disk i am having a problem with). since all my other disk arrays work fine i don't really want to rebuild the whole machine from scratch if i can avoid it.
    Any suggestions of what i can try ??

    well it turns out the new disk i bought just werent any good. my g5 powermac raid mirror issue was related to one new disk with lots of bad blocks (speed tools showed that up) so i have learnt my lesson on cheap non raid disks for raid..
    am waiting on a couple of new ultrastar enterprise disks to tuen up so i can go back to the macpro and try to add a mirror again.
    i am still stuck wih several new disks that i cannot format now in the macpro on leopard or on the g5 powermac with tiger.
    ive tried softraid and that cant do it, speedtools pcformat util cant do it, disk utility crashes when i try to eras them and diskutil from termianl starts then doenst get anywhere and my pc sata card doesnt work so my last resort pc option still doesnt help me clear the partition map on these drives - ones that diskutility on leopard made for me - and drives which still cause kernel panics on the macpro if i put them in it..
    here is what diskutil says on my g5:
    /dev/disk0
    #: type name size identifier
    0: GUIDpartitionscheme *465.8 GB disk0
    1: EFI 200.0 MB disk0s1
    2: Apple_RAID 465.4 GB disk0s2
    3: Apple_Boot 128.0 MB disk0s3
    /dev/disk1
    #: type name size identifier
    0: Applepartitionscheme *233.8 GB disk1
    1: Applepartitionmap 31.5 KB disk1s1
    2: Apple_HFS Macintosh HD 233.6 GB disk1s3
    /dev/disk2
    #: type name size identifier
    0: *465.4 GB disk2
    /dev/disk3
    #: type name size identifier
    0: Applepartitionscheme *931.5 GB disk3
    1: Applepartitionmap 31.5 KB disk3s1
    2: Apple_HFS backup1T 931.4 GB disk3s3
    /dev/disk4
    #: type name size identifier
    0: Applepartitionscheme *931.5 GB disk4
    1: Applepartitionmap 31.5 KB disk4s1
    2: Apple_HFS tempi 931.4 GB disk4s3
    disk0 is the one with the bad partition info.
    it thinks it has a double raid as the console shows on startup:
    (both store45 and cache it thinks are on this disk - cache was my old mirror of stripes set on other machine, store45 was new name for my mirror, so seems like it hadnt deleted the original raid partition info before making new info which now kernel panics)
    Jul 18 18:48:05 localhost kernel[0]: AppleRAID::degradeSet - starting the set "STORE45" (B9C48619-6B2C-4547-A01E-4864754EA7E2).
    Jul 18 18:48:35 localhost kernel[0]: AppleRAID::degradeSet - starting the set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B).
    Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "STORE45" (C0E139A4-2A6D-49C6-8F77-202AF7F9285D), member 50207BE5-E487-410E-8E8E-C4C4DCD2687B, set byte offset = 999527018496.
    Jul 18 18:48:35 localhost kernel[0]: AppleRAID::completeRAIDRequest - error 0xe00002c2 detected for set "CACHE" (64F914A5-5556-4A44-AEE2-DC437868766B), member C0E139A4-2A6D-49C6-8F77-202AF7F9285D, set byte offset = 999527018496.
    so currently i have 2 new 500gb disks which cant be partitioned back to anything at all on either machine. looks like i will have to buy a new pc to reformat them..
    any suggestions of how to clear the partition map info and get them back to freespace ??

  • Battery Update Causing Kernel Panics?

    It seems that ever since I installed the Battery Update it's been causing Kernel Panics on my MBP. Three since yesterday in fact. Has anyone else been experiencing this?
    MacBook Pro 1.83 GHz   Mac OS X (10.4.9)   1 GB RAM, 80 GB HDD, ATI Radeon X1600

    Hmm I have seen multiple posts on the computer not booting the OS (gets to the grey apple with spinning gear screen) but so far I think you are the first I have seen reporting kernel panics.
    Can you boot to the install cd? I'd try running the disk utility from the install disk and verify/repair permissions and verify the disk as well. (repair disk if verification fails)
    Here is an article that may help ya:
    Resolve startup issues and perform disk maintenance with Disk Utility and fsck
    http://docs.info.apple.com/article.html?artnum=106214

  • Using 2 memory modules causes kernel panic

    In early 2009 I upgraded my memory from 512 to 2 GB, 2 modules of 1GB each. This past January (just shy of 2 years later) I got a kernel panic. I tested running with a single module, and one module caused panic, the other was fine. Both slots function with the good module. So I got two new matched replacement chips from OWC, put them in and got kernel panics during the boot process. Yesterday I spent testing memory configurations and found this:
    1. chip 1 alone runs fine and passes all Rember memory tests in slot 1.
    2. chip 2 alone runs fine in slot 1 and 2, passes all memory tests in slot 2.
    3. chips 1 and 2 together, in either slot, cause kernel panics before the OS is loaded.
    Has anyone seen this problem? Will it go away if I use top of the line (Apple) memory chips?
    When the kernel panics started back in January, an AppleCare advanced advisor said he had the same problem and he had to remove one module to stop the kernel panics. Running on 1GB doesn't work for me because I tend to max out the memory and programs like Mail, Safari, Photoshop, etc. become unreponsive all together.
    thanks -

    I have spent more time on the phone with OWC about this than I care to remember. Their latest request is that I use an eraser to clean the metal contacts on the chips; if that fails, I get to send the chips back. Whether I get a refund or yet another set of replacement chips, I don't know. They are not experts on Apple machines, that is clear.

  • Scanner Causing Kernel Panics

    I have an old Agfa SnapScan 1212u USB scanner and up until today it has worked fine. Then suddenly it started causing Kernal Panics. It happens about 30% of the time. It scans the first 10% then throws up the Kernel Panic message and I'm forced to restart. I have run the Disk Repair Utility, repaired permissions, reinstalled the Agfa Scanwise driver, deleted all scanner related preferences and disconnected all other USB devices but nothing seems to work. The only software update I've done recently is the August and Java Security updates. Could either of these things be the problem? This is the first time I've had Kernel Panics on my Mac Mini. I doubt it's caused by the ram. It has worked flawlessly since I put in the 1GB module in July.
    Does anyone have any ideas?
    Cheers
    djon

    Well, I downloaded Vuescan and set it up but now I have another problem. Vuescan constantly crashes. Sometimes it crashes when I'm changing settings and sometimes is crashes after a scan. I set the memory settings very high so it shouldn't be a memory issue. I've tried just about everything to get this scanner working with Vuescan. I even installed a fresh copy of Panther on my Firewire drive but it only reduced the crashes not eliminate them. I'd like to get Vuescan working because it seems to make better scans than Scanwise did. At least it doesn't cause Kernel Panics. Does anyone have any idea what's going on? I'm beginning to think that it might be a hardware problem with the scanner.
    djon

  • External LaCie Multi Recorder causing kernel panics since reloading OS

    I just replaced my main internal hd with a new 1TB WD Caviar Black. I migrated all of my user information from my old drive via Time Machine & all seemed well. Since I did a fresh, zero out data install of the OS on the new drive, I need to reinstall my programs. Some of my older programs are kept on DVD-RAM disks that I've had since my old G4. To access these files I use my LaCie Multi recorder which was working fine prior to the HD switch.
    When I put my DVD-RAM disk into the drive it's now causing kernel panics.
    Anyone know what could have caused this or how I might correct the problem?
    Thanks.

    Okay, it seems that I've got a bad disk. I connected the drive to my laptop & used another dvd & all worked as it should. Put my program back-up disk in & it caused a panic.
    New question, is there any way to repair the disk?
    I've got DiskWarrior & TechTool Deluxe but I'm not sure how I might go about the repair as the panic occurs while the drive is trying to access the disk.

  • Rt3062 causing kernel panics

    Hi all,
    I've got an rt3062 chipset wireless card and it's been causing kernel panics ever since the upgrade to linux-3.0.
    I was using the driver and firmware supplied by ralink and compiling it as the rt3562sta driver and it used to work great but it doesnt seem to support anything higher than kernel 2.6.39.
    I'm not exactly sure which error logs to post, so...
    Anybody else having this issue? and maybe find a workaround?
    Thanks

    I am using the same combination, successfully, with kernel 3.0.7-1. I do not recall having to do anything special to get it to work.
    06:00.0 Network controller: Ralink corp. Device 3062
        Subsystem: Ralink corp. Device 3062
        Flags: bus master, slow devsel, latency 32, IRQ 19
        Memory at fbdf0000 (32-bit, non-prefetchable) [size=64K]
        Capabilities: [40] Power Management version 3
        Kernel driver in use: rt2860
        Kernel modules: rt3562sta, rt2800pci
    Tim

  • ITunes causing kernel panics because I'm streaming to multiple Airplay Speakers?

    Any idea what is causing kernel panics that seems to have started when I began streaming to multiple Airplay Speakers?  iTunes is listed as the culprit in the crash report.

    My question:  is there a way to select multiple speakers from AppleTV for Airplay?
    Unfortunately not.

  • PS Extended CS6 causing kernel panics

    I've been getting one or two a week. Haven't figured out yet what triggers it, but it only happens in CS6. I did recently reinstall the entire OS, so that's clean. Here's the latest panic info the reboot generates to send to Apple. Doesn't mean anything to me, other than the panic notation near the top of the info tells you what it thinks happened.
    Interval Since Last Panic Report:  141469 sec
    Anonymous UUID:                    44199F46-5B6B-42C5-9E13-29CB09291223
    Mon Sep 24 14:40:11 2012
    panic(cpu 2 caller 0xffffff80002094e7): "thread_invoke: preemption_level -1, possible cause: unlocking an unlocked mutex or spinlock"@/SourceCache/xnu/xnu-1504.15.3/osfmk/kern/sched_prim.c:1471
    Backtrace (CPU 2), Frame : Return Address
    0xffffff8149e83d70 : 0xffffff8000204d15
    0xffffff8149e83e70 : 0xffffff80002094e7
    0xffffff8149e83ef0 : 0xffffff8000209acb
    0xffffff8149e83f60 : 0xffffff800053b02d
    0xffffff8149e83fa0 : 0xffffff80002c8527
    BSD process name corresponding to current thread: kernel_task
    Mac OS version:
    10K549
    Kernel version:
    Darwin Kernel Version 10.8.0: Tue Jun  7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64
    System model name: MacPro5,1 (Mac-F221BEC8)
    System uptime in nanoseconds: 26760035257178
    unloaded kexts:
    com.apple.iokit.IOFireWireSBP2          4.0.6 (addr 0xffffff7f80e4a000, size 0x73728) - last unloaded 25651433036012
    loaded kexts:
    com.aladdin.kext.aksfridge          1.0.2
    com.dvdfab.kext.fabio          1
    com.hzsystems.terminus.driver          4
    com.microsoft.driver.MicrosoftKeyboardUSB          8.2
    com.microsoft.driver.MicrosoftKeyboard          8.2
    com.Logitech.Control Center.HID Driver          3.6.0
    com.apple.filesystems.afpfs          9.7.1 - last loaded 23445647212129
    com.apple.nke.asp_tcp          5.0
    com.apple.driver.AppleHWSensor          1.9.3d0
    com.apple.driver.AppleTyMCEDriver          1.0.2d2
    com.apple.driver.AGPM          100.12.31
    com.apple.driver.AppleUpstreamUserClient          3.5.7
    com.apple.driver.AppleMCCSControl          1.0.20
    com.apple.driver.AppleMikeyHIDDriver          1.2.0
    com.apple.kext.ATIFramebuffer          6.3.6
    com.apple.driver.AppleHDA          2.0.5f14
    com.apple.driver.AppleMikeyDriver          2.0.5f14
    com.apple.driver.AudioAUUC          1.57
    com.apple.filesystems.ntfs          3.4
    com.apple.ATIRadeonX3000          6.3.6
    com.apple.filesystems.autofs          2.1.0
    com.apple.Dont_Steal_Mac_OS_X          7.0.0
    com.apple.driver.AudioIPCDriver          1.1.6
    com.apple.driver.ACPI_SMC_PlatformPlugin          4.7.0a1
    com.apple.driver.AppleLPC          1.5.1
    com.apple.iokit.IOAHCIBlockStorage          1.6.4
    com.apple.iokit.SCSITaskUserClient          2.6.8
    com.apple.BootCache          31.1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib          1.0.0d1
    com.apple.driver.AppleFWOHCI          4.7.3
    com.apple.driver.AppleUSBOHCI          4.2.0
    com.apple.driver.AppleUSBHub          4.2.4
    com.apple.driver.AirPortBrcm43224          428.42.4
    com.apple.driver.AppleAHCIPort          2.1.7
    com.apple.driver.Intel82574L          2.1.8b1
    com.apple.driver.AppleUSBEHCI          4.2.4
    com.apple.driver.AppleUSBUHCI          4.2.0
    com.apple.driver.AppleEFINVRAM          1.4.0
    com.apple.driver.AppleRTC          1.3.1
    com.apple.driver.AppleHPET          1.5
    com.apple.driver.AppleACPIButtons          1.3.6
    com.apple.driver.AppleSMBIOS          1.7
    com.apple.driver.AppleACPIEC          1.3.6
    com.apple.driver.AppleAPIC          1.4
    com.apple.driver.AppleIntelCPUPowerManagementClient          142.6.0
    com.apple.security.sandbox          1
    com.apple.security.quarantine          0
    com.apple.nke.applicationfirewall          2.1.14
    com.apple.driver.AppleIntelCPUPowerManagement          142.6.0
    com.apple.driver.AppleProfileReadCounterAction          17
    com.apple.driver.DspFuncLib          2.0.5f14
    com.apple.driver.AppleProfileTimestampAction          10
    com.apple.driver.AppleProfileThreadInfoAction          14
    com.apple.driver.AppleProfileRegisterStateAction          10
    com.apple.driver.AppleProfileKEventAction          10
    com.apple.driver.AppleProfileCallstackAction          20
    com.apple.iokit.IONDRVSupport          2.2.1
    com.apple.driver.AppleSMBusController          1.0.10d0
    com.apple.kext.ATI5000Controller          6.3.6
    com.apple.kext.ATISupport          6.3.6
    com.apple.iokit.IOFireWireIP          2.0.3
    com.apple.iokit.IOSurface          74.2
    com.apple.iokit.IOBluetoothSerialManager          2.4.5f3
    com.apple.iokit.IOSerialFamily          10.0.3
    com.apple.iokit.IOAudioFamily          1.8.3fc2
    com.apple.kext.OSvKernDSPLib          1.3
    com.apple.driver.AppleHDAController          2.0.5f14
    com.apple.iokit.IOGraphicsFamily          2.2.1
    com.apple.iokit.IOHDAFamily          2.0.5f14
    com.apple.iokit.AppleProfileFamily          41
    com.apple.driver.AppleSMC          3.1.0d5
    com.apple.driver.IOPlatformPluginFamily          4.7.0a1
    com.apple.driver.AppleSMBusPCI          1.0.10d0
    com.apple.driver.BroadcomUSBBluetoothHCIController          2.4.5f3
    com.apple.driver.AppleUSBBluetoothHCIController          2.4.5f3
    com.apple.driver.IOBluetoothHIDDriver          2.4.5f3
    com.apple.iokit.IOBluetoothFamily          2.4.5f3
    com.apple.iokit.IOUSBHIDDriver          4.2.0
    com.apple.driver.AppleUSBMergeNub          4.2.4
    com.apple.driver.AppleUSBComposite          3.9.0
    com.apple.driver.XsanFilter          402.1
    com.apple.iokit.IOSCSIMultimediaCommandsDevice          2.6.8
    com.apple.iokit.IOBDStorageFamily          1.6
    com.apple.iokit.IODVDStorageFamily          1.6
    com.apple.iokit.IOCDStorageFamily          1.6.1
    com.apple.iokit.IOFireWireFamily          4.2.6
    com.apple.iokit.IOAHCISerialATAPI          1.2.6
    com.apple.iokit.IOSCSIArchitectureModelFamily          2.6.8
    com.apple.iokit.IO80211Family          320.1
    com.apple.iokit.IOUSBUserClient          4.2.4
    com.apple.iokit.IOAHCIFamily          2.0.6
    com.apple.iokit.IONetworkingFamily          1.10
    com.apple.iokit.IOUSBFamily          4.2.4
    com.apple.driver.AppleEFIRuntime          1.4.0
    com.apple.iokit.IOHIDFamily          1.6.6
    com.apple.iokit.IOSMBusFamily          1.1
    com.apple.kext.AppleMatch          1.0.0d1
    com.apple.security.TMSafetyNet          6
    com.apple.driver.DiskImages          289.1
    com.apple.iokit.IOStorageFamily          1.6.3
    com.apple.driver.AppleACPIPlatform          1.3.6
    com.apple.iokit.IOPCIFamily          2.6.5
    com.apple.iokit.IOACPIFamily          1.3.0
    Model: MacPro5,1, BootROM MP51.007F.B03, 6 processors, 6-Core Intel Xeon, 3.33 GHz, 16 GB, SMC 1.39f11
    Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
    Memory Module: global_name
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.10.131.42.4)
    Bluetooth: Version 2.4.5f3, 2 service, 12 devices, 1 incoming serial ports
    Network Service: Ethernet 2, Ethernet, en1
    PCI Card: pci104c,823f, sppci_ieee1394openhci, Slot-3@6,0,0
    PCI Card: pci1033,35, sppci_usbopenhost, Slot-3@8,0,0
    PCI Card: pci1033,e0, USB Enhanced Host Controller, Slot-3@8,0,1
    PCI Card: pci1033,35, sppci_usbopenhost, Slot-4@11,0,0
    PCI Card: pci1033,35, sppci_usbopenhost, Slot-4@11,0,1
    PCI Card: pci1033,e0, USB Enhanced Host Controller, Slot-4@11,0,2
    PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
    Serial ATA Device: HL-DT-ST DVD-RW GH61N
    Serial ATA Device: HL-DT-ST BD-RE  GGW-H20L
    Serial ATA Device: WDC WD1001FALS-41Y6A1, 931.51 GB
    Serial ATA Device: Hitachi HDS722020ALA330, 1.82 TB
    Serial ATA Device: WDC WD3200AAKS-00VYA0, 298.09 GB
    USB Device: Hub, 0x0409  (NEC Corporation), 0x005a, 0xfd300000 / 2
    USB Device: EIZO USB HID Monitor, 0x056d  (Eizo), 0x0002, 0xfd330000 / 3
    USB Device: USB 2.0 Hub [MTT], 0x1a40  (TERMINUS TECHNOLOGY INC.), 0x0101, 0x40400000 / 2
    USB Device: HASP4 USB 1.33, 0x0529  (Aladdin Knowledge Systems), 0x0001, 0x00200000 / 3
    USB Device: SII Smart Label Printer 200, 0x0619  (Seiko Instruments Inc.), 0x0104, 0x00100000 / 2
    USB Device: HASP4 USB 1.33, 0x0529  (Aladdin Knowledge Systems), 0x0001, 0xff100000 / 2
    USB Device: HASP HL 3.25, 0x0529  (Aladdin Knowledge Systems), 0x0001, 0xfe200000 / 2
    USB Device: Natural® Ergonomic Keyboard 4000, 0x045e  (Microsoft Corporation), 0x00db, 0x1a200000 / 2
    USB Device: BRCM2046 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x5a100000 / 2
    USB Device: Bluetooth USB Host Controller, 0x05ac  (Apple Inc.), 0x8215, 0x5a110000 / 3
    USB Device: USB Receiver, 0x046d  (Logitech Inc.), 0xc52f, 0x1d100000 / 2
    FireWire Device: built-in_hub, Up to 800 Mb/sec
    FireWire Device: unknown_device, 0xD016, Up to 200 Mb/sec

    Only OS bugs, driver bugs, or hardware problems can cause kernel panics.
    Yes, that is normally the case. I brought this up here because while working in PS is the only time this happens. I know it doesn't make sense, but there it is.
    Not sure why the crash report stated 10.8.0. It's incorrect on two counts. For one, I'm working in Snow Leopard, 10.6.8. I do have Mountain Lion installed on a separate drive for testing, but that already is at 10.8.2. Regardless, it's not the OS I was even in, so I don't know why it reported 10.8.0 as the kernel.
    Anyway, I noticed (after posting this of course) that there was a 13.0.1 update for PS CS6. I applied that and we'll see how it goes from there as the update is noted as fixing a number of crashing problems.

  • GRUB caused kernel panic

    I was recommended install grub instead lilo (under lilo everything was OK). I proceeded exactly according the Grub ArchWiki: installed grub
    grub-install /dev/hda
    removed lilo 
    pacman -R lilo
    and configured menu.lst. After reboot grub loaded vmlinuz26 and the bott process run until "kernel panic". The last line told that the root partition was not recognized. The root partition in kernel option was defined as
    root=/dev/discs/disc0/part3
    just as it is in fstab. What is wrong with that??? I checked grub config lines several times, there were no mistypings there...

    Just as a clarification - the title says that GRUB caused a kernel panic - this is not true.  GRUB loads the kernel.  Either GRUB fails, or the kernel panics - they do not work together.
    In this case, GRUB passes parameters to the kernel.  It is the root= parameter which failed, and the kernel itself paniced (Unable to mount root device).

  • Readynas duo mounted over ethernet causes kernel panics

    I've found out what is causing kernel panics on my machines, but i'm not sure how to resolve it. I have a g4 laptop and a new mac mini, both mount the readynas via mount_afp using a LoginHook. When the laptop or the mini go to sleep, the ethernet connection is powered off and at some point the readynas goes to sleep as well. So, when the laptop/mini wake from sleep, they have trouble re-establishing the mount to the readynas (as it needs time to spin it's drives up) and then the laptop/mini kernel panic...shouldn't this really be just a lost connection message, rather than a full fledged panic!

    This is where we have a difference of opinion...If i can mount an external box over ethernet/firewire/usb and it causes the machine to kernel panic, then the software is not robust enough to handle the exception cases. Running 10.4.x for years with the same external hardware never yielded such results.

  • Boot panic

    My configuration is:
    Athlon XP2100+
    512 DDRAM
    2 9.1GB SCSI HDs
    Adaptec 29160N
    3C905CTX NIC
    Solaris 8 10/01
    At Webstart installation, I let it default to interactive. Then I get:
    boot panic: trap type e, error at <different addresses>
    I'm booting from the CD-ROM with a downloaded copy. Occasionally I
    have seen messages like:
    bogus sector number
    short read. 0x2000 char read
    just before the panic
    I thought about replacing the CD-ROM, but then and just for the sake
    of confirming, I installed W2K using the same configuration without
    any problems.
    Any hint on what it may be causing this situation?
    Thanks beforehand for your comments.

    jensvdb wrote:
    Spider.007 wrote:
    The same problem is described here: https://bbs.archlinux.org/viewtopic.php?id=82065 However, I don't know whether something was fixed in the package, or in the kernel. Either way, you might be able to work around this problem by installing an old kernel from /var/cache/pacman/pkg.
    You need to chroot from a live-cd into your existing system to install that
    Yeah, I've seen that thread. I have already looked up on how to downgrade my kernel (wiki: https://wiki.archlinux.org/index.php/Do … g_Packages), but that page only talks about downgrading packages... Your message was quiete clear. Many thanks for the suggestion, I'll try it out and report the results.
    Okay, I've installed the LTS kernel now (2.6.32.31-1) and so far, so good.

  • Could a Dashboard widget be the cause of my Panics?

    Hello everyone,
    For the past few months, I've gotten a kernel panic on the average of about once a week. I started looking a the kernel logs and I discovered that 18 out of the 19 kernel panics my powerbook experienced this year had something eerily in common: the current thread for all of them was DashboardClient.
    Now what's frustrating is that all loaded widgets are labeled as "DashboardClient" in the activity monitor so I don't know how I'm suppose to figure out which one, save for process of elimination.
    But could a dashboard widget be the source of my kernel panics?
    Also, my drive's directory structure is spotless. No errors, defraged, disk warrior, etc. and I'm current with my updates.
    If anyone could help me I'd really appreciate it!
    Here's a panic dump from the latest panic:
    Wed Apr 28 15:32:17 2010
    Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x0000000000000008 PC=0x00000000000AD208
    Latest crash info for cpu 0:
    Exception state (sv=0x30195780)
    PC=0x000AD208; MSR=0x00009030; DAR=0x00000008; DSISR=0x40000000; LR=0x0007C270; R1=0x302A7A70; XCP=0x0000000C (0x300 - Data access)
    Backtrace:
    0x0007C270 0x0007CC54 0x0006E040 0x0006EB68 0x0003AB18 0x0029B170
    0x0029B29C 0x0029BA74 0x0029BB94 0x003100AC 0x000B4448 0x9816C485
    Proceeding back via exception chain:
    Exception state (sv=0x30195780)
    previously dumped as "Latest" state. skipping...
    Exception state (sv=0x37fe1a00)
    PC=0x95492954; MSR=0x0000D030; DAR=0xE34BCCA8; DSISR=0x40000000; LR=0x95492948; R1=0xBFFF99B0; XCP=0x00000030 (0xC00 - System call)
    BSD process name corresponding to current thread: DashboardClient
    Mac OS version:
    9L31a
    Kernel version:
    Darwin Kernel Version 9.8.0: Wed Jul 15 16:57:01 PDT 2009; root:xnu-1228.15.4~1/RELEASE_PPC
    System model name: PowerBook5,6
    System uptime in nanoseconds: 373029901008580
    unloaded kexts:
    com.apple.driver.AppleUSBTCKeyEventDriver 1.7.4f1 - last unloaded 5772792683945
    loaded kexts....

    Yes, a widget can cause kernel panics — particularly an old one that hasn't been updated as needed for compatibility with a more recent OS version.
    Starting with the widgets that you know you've added yourself, open each of your installed widgets and put it through its paces doing whatever it does, in an effort to provoke a kernel panic on purpose. While you have it open (if no KP occurs), consult the website of its developer to see whether any updates are available for it, and apply any that are appropriate. (Avoid any update that is designated as compatible ONLY with Snow Leopard or Intel machines, if you run across any such.)
    If you get through updating all your widgets without a KP, just keep using your Powerbook and see what happens. It's unfortunate that you may have to wait several weeks to conclude that the problem has or hasn't been solved, but it may take that long if your KPs up to now have only occurred about weekly.
    Message was edited by: eww

  • [Repaired] Bad blocks cause kernel blocking to the device

    I got
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Unhandled sense code
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] Sense Key : 0x3 [current]
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] ASC=0x14 ASCQ=0x0
    May 10 10:08:13 qslap kernel: sd 4:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 25 42 ea af 00 00 01 00
    May 10 10:08:13 qslap kernel: end_request: I/O error, dev sdb, sector 625142447
    May 10 10:08:13 qslap kernel: Buffer I/O error on device sdb, logical block 78142805
    in system log when I try to access /dev/sdb in some way (for example, plug in, fdisk, gparted, but not palimpsest).
    This kind of log repeats several times and blocks any access to that device for tens of seconds (Seems kernel keep retrying, not give up the first time), which is annoying.
    From palimpsest, I can see:
    Current Pending Sector Count: Value: 1 sector
    Uncorrectable Sector Count: Value: 1 sector
    It says when write fails, "Current Pending Sector" will be remapped automatically by hardware.
    I got the sector size = 512 bytes:
    # fdisk -lu /dev/sdb
    Disk /dev/sdb: 320.1 GB, 320072933376 bytes
    255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xaaaaaaaa
    Disk /dev/sdb doesn't contain a valid partition table
    badblocks detects the bad sector well:
    # badblocks -svw -b 512 /dev/sdb 625142447 625142447
    Checking for bad blocks in read-write mode
    From block 625142447 to 625142447
    Testing with pattern 0xaa: 625142447one, 0:20 elapsed
    done
    Reading and comparing: done
    Testing with pattern 0x55: done
    Reading and comparing: done
    Testing with pattern 0xff: done
    Reading and comparing: done
    Testing with pattern 0x00: done
    Reading and comparing: done
    Pass completed, 1 bad blocks found.
    From above, you can see that write a block one time takes 20 seconds due to kernel blocking.
    badblocks writes 4 times,  ~80 seconds.
    Note: badblocks doesn't find any bad blocks when performing a full disk read-only test.
    However, the sector wasn't automatically remapped (badblocks has already written that sector)
    the kernel is still generating logs and blocking, which is very annoying.
    I also tried to write at that sector directly, no luck:
    # dd if=/dev/zero of=/dev/sdb bs=512 count=1 seek=625142447
    dd: writing `/dev/sdb': Input/output error
    1+0 records in
    0+0 records out
    0 bytes (0 B) copied, 7.26951 s, 0.0 kB/s
    What should I do to let the hardware remap that sector?
    If no way due to hardware limitation, then how can I mute the annoying log and let the kernel not blocking ?
    Additional: I am looking for a way to let kernel not blocking, give up at the begining asap, or let the hardware SMART mark that sector not to be 'Pending', not for a way to create fs with bad blocks marked.
    I know if I provide a list of badblocks to mkfs.*** to create a fs, these blocks will not be used.
    However, when I plug in the removable harddisk, BEFORE performing ANY r/w instructions, the kernel starts to generate logs and /dev/sdb is not visible in tens of seconds. Same situation occurs when I run / fdisk / gparted (these programs are not responsible for tens of seconds due to kernel blocking) ...
    I guess that SMART does these checks automatically and cause kernel blocking, while SMART can't handle these things well.
    This is the output of smartctl -a /dev/sdb -d sat, which may be helpful:
    smartctl 5.39.1 2010-01-28 r3054 [i686-pc-linux-gnu] (local build)
    Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net
    === START OF INFORMATION SECTION ===
    Model Family: Seagate Momentus 5400.5 series
    Device Model: ST9320320AS
    Serial Number: 5SX3YFQ8
    Firmware Version: SD03
    User Capacity: 320,072,933,376 bytes
    Device is: In smartctl database [for details use: -P show]
    ATA Version is: 8
    ATA Standard is: ATA-8-ACS revision 4
    Local Time is: Mon May 10 11:25:42 2010 CST
    SMART support is: Available - device has SMART capability.
    SMART support is: Enabled
    === START OF READ SMART DATA SECTION ===
    SMART overall-health self-assessment test result: PASSED
    See vendor-specific Attribute list for marginal Attributes.
    General SMART Values:
    Offline data collection status: (0x00) Offline data collection activity
    was never started.
    Auto Offline Data Collection: Disabled.
    Self-test execution status: ( 121) The previous self-test completed having
    the read element of the test failed.
    Total time to complete Offline
    data collection: ( 700) seconds.
    Offline data collection
    capabilities: (0x73) SMART execute Offline immediate.
    Auto Offline data collection on/off support.
    Suspend Offline collection upon new
    command.
    No Offline surface scan supported.
    Self-test supported.
    Conveyance Self-test supported.
    Selective Self-test supported.
    SMART capabilities: (0x0003) Saves SMART data before entering
    power-saving mode.
    Supports SMART auto save timer.
    Error logging capability: (0x01) Error logging supported.
    General Purpose Logging supported.
    Short self-test routine
    recommended polling time: ( 1) minutes.
    Extended self-test routine
    recommended polling time: ( 114) minutes.
    Conveyance self-test routine
    recommended polling time: ( 2) minutes.
    SCT capabilities: (0x103f) SCT Status supported.
    SCT Feature Control supported.
    SCT Data Table supported.
    SMART Attributes Data Structure revision number: 10
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000f 094 088 006 Pre-fail Always - 182650280
    3 Spin_Up_Time 0x0003 099 099 000 Pre-fail Always - 0
    4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 595
    5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000f 075 060 030 Pre-fail Always - 30942693
    9 Power_On_Hours 0x0032 095 095 000 Old_age Always - 4482
    10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 1
    12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 579
    184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0
    187 Reported_Uncorrect 0x0032 001 001 000 Old_age Always - 1812
    188 Command_Timeout 0x0032 100 099 000 Old_age Always - 2
    189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0
    190 Airflow_Temperature_Cel 0x0022 067 039 045 Old_age Always In_the_past 33 (0 166 39 23)
    191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 98
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 48
    193 Load_Cycle_Count 0x0032 011 011 000 Old_age Always - 178621
    194 Temperature_Celsius 0x0022 033 061 000 Old_age Always - 33 (0 12 0 0)
    195 Hardware_ECC_Recovered 0x001a 060 039 000 Old_age Always - 182650280
    197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 1
    198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 1
    199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0
    SMART Error Log Version: 1
    ATA Error Count: 1979 (device log contains only the most recent five errors)
    CR = Command Register [HEX]
    FR = Features Register [HEX]
    SC = Sector Count Register [HEX]
    SN = Sector Number Register [HEX]
    CL = Cylinder Low Register [HEX]
    CH = Cylinder High Register [HEX]
    DH = Device/Head Register [HEX]
    DC = Device Command Register [HEX]
    ER = Error register [HEX]
    ST = Status register [HEX]
    Powered_Up_Time is measured from power on, and printed as
    DDd+hh:mm:SS.sss where DD=days, hh=hours, mm=minutes,
    SS=sec, and sss=millisec. It "wraps" after 49.710 days.
    Error 1979 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:15.498 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:13.155 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    Error 1978 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:13.155 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    Error 1977 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.887 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.886 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:10.885 READ DMA EXT
    Error 1976 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:08.457 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:06.082 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.814 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    Error 1975 occurred at disk power-on lifetime: 4480 hours (186 days + 16 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    40 51 00 ff ff ff 0f Error: UNC at LBA = 0x0fffffff = 268435455
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    25 da 01 ff ff ff 4f 00 13:43:06.082 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.814 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    25 da 01 ff ff ff 4f 00 13:43:03.813 READ DMA EXT
    SMART Self-test log structure revision number 1
    Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error
    # 1 Extended offline Completed: read failure 90% 4480 625142447
    # 2 Short offline Completed: read failure 90% 4474 625142447
    # 3 Extended offline Completed: read failure 90% 4474 625142447
    # 4 Short offline Completed: read failure 90% 4474 625142447
    # 5 Conveyance offline Completed: read failure 90% 4473 625142447
    # 6 Short offline Completed: read failure 90% 4473 625142447
    SMART Selective self-test log data structure revision number 1
    SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS
    1 0 0 Not_testing
    2 0 0 Not_testing
    3 0 0 Not_testing
    4 0 0 Not_testing
    5 0 0 Not_testing
    Selective self-test flags (0x0):
    After scanning selected spans, do NOT read-scan remainder of disk.
    If Selective self-test is pending on power-up, resume after 0 minute delay.
    Last edited by b6fan (2010-05-10 07:18:46)

    Bad block repaired by SeaTools for DOS.
    Seems only SeaTools for DOS can repair this issue.

Maybe you are looking for

  • How to display data in the same tab components ?

    Hi, I have a tabbed pane and contains 3 tabs. I have entered some value in the text field and clicked the enter button in the 3rd tab.This enter button contains some validation code and after validation it will display some data in the text area in t

  • Running Manual Reconcillation

    Hi All Am running first time Manual Reconciliation for my client, please advise me and what all fields need to take care and how the transactions takes place. i have one more doubt.. the user already posted this entry, before clearing the vendor line

  • File sharing windows 7 and xp problem

    Hello All,, I am working within domain environment using windows server 2012 R2 as domain controller and my client computers are windows 7 professional and windows XP ,,, the problem is windows XP can NOT access the shared files on windows 7 computer

  • Jasper Report Problem

    hi 2 all, am trying to use jasper report in my project, am using jasper 0.5.2 older version , i put the itext-1.3.1.jar jdt-compiler.jar jasperreports-1.1.0.jarin my project web-apps lib now am getting problem is,when i try to get .jasper file from t

  • How to pass a command line argument to the sequence?

    Hi, My GUI is written in VB.NET. I can read the command line argument in the GUI, using: Me.AxApplicationMgr.CommandLineArguments(). But I don't know how to pass it on to my sequence file which the GUI invokes. How do I read the command line argument