Report 10.X Core DSDT

TIP: If you get PANIC with no CLUES

Just a little tip that I found trying some DSDT stuff. If you get a Kernel Panic, and the output info gives you poor information and no clues, check if you have installed the lspcidrv.kext (for lspci comand). That driver which is very…

Primary Author: @dragonspeed Published 2010-08-15
Collection: OSx86 Core & 10.X
Archival Footprint: 23,080 historical reads · 3 curated field notes (from 4 dispatches) · 2010-08-15 – 2012-09-11
Credited Voices (4): @dragonspeed @Drule @todesto @bcoco85

Just a little tip that I found trying some DSDT stuff.

If you get a Kernel Panic, and the output info gives you poor information and no clues,
check if you have installed the lspcidrv.kext (for lspci comand).

That driver which is very useful, can be problematic, i.e: I got panics just turning on and off my bluetooth mighty mouse. Removed and everything perfect again, and I suspect that it happens specially 10.6.4 ( I am using Legacy Kernel 10.4)

So LSPCIDRV.KEXT: Just use it when you need it and, remove it when you don't

Regards,
Dragon

Synthesized Community Field Notes

3 technical responses curated from 4 original dispatches

Field Note #1 @Drule 2010-08-16

Thanks for the tip, I will have to give it a try, as I've been having the occasional 'double kernel panic' randomly show up on my legacy 10.6.4 build. My BT MagicMouse also freezes up every once in a while, so who knows maybe this will fix that Completely forgot I'd added that kext.

UPDATE: Removed it and ran Kext Utility to clean everything up … no change, still get intermittent mouse problems, and occasionally a double kernel panic on boot. Back to the DSDT I go.

Field Note #2 @todesto 2012-09-02

Thanks for the info. That is why my boot gets stuck at IObluetooth sometimes (booting with -v) then moves on or get panic. I'm gonna remove it. but what does this kext do?

Field Note #3 @bcoco85 2012-09-11

i had random panics with nawcom legacy kernel for 10.6.8
the only solution was avn legacy kernel for 10.6.8
but im trying removing this lspcidrvkext, im testing the behavior in both kernels-

first thing i noticed is that i have no more to set npci=0x2000 in order to start. it start good without that.

Sources & Contributor Provenance (4 credited usernames · Thread #6475)

Username	Dossier Contribution	Dispatches	Active Window
@dragonspeed	Primary Author	1	2010-08-15
@Drule	Contributor	1	2010-08-16
@todesto	Contributor	1	2012-09-02
@bcoco85	Contributor	1	2012-09-11

Synthesized Community Field Notes

More in 10.X Core