3.4/3.5 kernels not booting in intel 945/950 chipset

3.4/3.5 kernels not booting in intel 945/950 chipset

[Ian Malone]

Hi,

I'm using Fedora 17 and have the following bug:
https://bugzilla.redhat.com/show_bug.cgi?id=834318 where 3.4 and 3.5
series kernels run into a kernel panic during boot which appears to be
related to ACPI, on a Sony VGN-C2M/W Vaio
http://www.sony.co.uk/support/en/product/VGN-C2M_W/specifications
(Intel 945/950 chipset, core 2 duo).

acpidump is attached to the Fedora bug:
https://bugzilla.redhat.com/attachment.cgi?id=593488

As are screenshots of the startup messages:
https://bugzilla.redhat.com/attachment.cgi?id=593486
https://bugzilla.redhat.com/attachment.cgi?id=593487

Passing acpi=off allows the machine to boot. Another reporter has
found what might be the same problem on a Mac Pro. I've tried Fedora's
3.4.0 and 3.5.0-rc6 packaged kernels (as in bug entry) as well as a
number of 3.4.x updates.

Does anyone have any suggestions for things to try or any more
information I could collect?

Thanks for your time,
Ian
-- 
imalone
http://ibmalone.blogspot.co.uk

Re: 3.4/3.5 kernels not booting in intel 945/950 chipset

[Thomas Renninger]

Hi,

On Wednesday, July 11, 2012 06:26:24 PM Ian Malone wrote:
> Hi,
> 
> I'm using Fedora 17 and have the following bug:
> https://bugzilla.redhat.com/show_bug.cgi?id=834318 where 3.4 and 3.5
> series kernels run into a kernel panic during boot which appears to be
> related to ACPI, on a Sony VGN-C2M/W Vaio
> http://www.sony.co.uk/support/en/product/VGN-C2M_W/specifications
> (Intel 945/950 chipset, core 2 duo).
> 
> acpidump is attached to the Fedora bug:
> https://bugzilla.redhat.com/attachment.cgi?id=593488
> 
> As are screenshots of the startup messages:
> https://bugzilla.redhat.com/attachment.cgi?id=593486

This one gets fixed by:
ACPICA: Fix possible fault in return package object repair code
which was sent on this list by Lin Ming recently.

https://bugzilla.kernel.org/show_bug.cgi?id=44171

The fix hopefully still shows up in 3.5 pretty soon.
I just re-sent it with stable@ in CC, so the fix should show
up in 3.4 as well sooner or later.

      Thomas