[OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w)

[Matt Connolly]

I've experienced the "interrupt storm" (at that's what I think it is - ever increasing kernel cpu usage and slowing down machine) on a new sandy bridge Xeon E3.

As far as I'm aware there is a fix for this in the prestable package repo. I just updated my publisher to that on my Xeon machine about 2 days ago, and it's looking good so far.

Might be worth giving that a try.

-Matt


On 08/02/2012, at 5:00 AM, Lou Picciano wrote:

> Geoff, 
> 
> On the face of it, this looks remarkably like the power management and interrupt issues many (including Yours Truly!) are seeing on SandyBridge CPUs (our is an i7-2600K). These problems often manifest as an 'Interrupt Storm'. Check the bug lists for reports - and some suggested workarounds. 
> 
> Trying to work through what I think is the next iteration of this problem; that I can reliably crash our build machine with the -j(n) option to gcc. 
> 
> More to follow... 
> 
> Lou Picciano 
> 
> ----- Original Message -----
> From: "Geoff Simmons" <geoff at uplex.de> 
> To: openindiana-discuss at openindiana.org 
> Cc: "Nils Goroll" <nils.goroll at uplex.de> 
> Sent: Tuesday, February 7, 2012 7:55:22 AM 
> Subject: [OpenIndiana-discuss] Kernel panic with Intel i7-2670QM CPU (HP EliteBook 8560w) 
> 
> -----BEGIN PGP SIGNED MESSAGE----- 
> Hash: SHA256 
> 
> Hello all, 
> 
> A colleague attempted to boot oi_151a from CD on an HP EliteBook 8560w 
> laptop: 
> 
> http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/321957-321957-64295-3740645-4307559-5071171.html 
> 
> ... the variant with Intel i7-2670QM. He got an immediate kernel panic, 
> and thinks that he saw a message about the CPU before the screen went 
> blank; which leads us to believe that 2670QM may be too "new" for oi_151a. 
> 
> Has anyone else tried booting OpenIndiana with this CPU, or confirm 
> whether or not it can be used? Or are we looking at the wrong 
> explanation for the kernel panic? 
> 
> He also tried some other variations of Solaris: 
> 
> - - OpenSolaris snv_134 booted from an SSD also led to immediate kernel 
> panic. 
> 
> - - Solaris 11 11/11 also got a kernel panic. 
> 
> - - Oddly, OpenSolaris snv_111 could be booted, after issuing warnings 
> about a parser error in the cpudrv or cpupm module. But neither ethernet 
> nor wireless were recognized, and the old nvidia driver didn't work 
> (that could be updated). 
> 
> 
> Thanks, 
> Geoff 
> - -- 
> ** * * UPLEX - Nils Goroll Systemoptimierung 
> 
> Schwanenwik 24 
> 22087 Hamburg 
> 
> Tel +49 40 2880 5731 
> Mob +49 176 636 90917 
> Fax +49 40 42949753 
> 
> http://uplex.de 
> -----BEGIN PGP SIGNATURE----- 
> Version: GnuPG v1.4.10 (SunOS) 
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ 
> 
> iQIcBAEBCAAGBQJPMR86AAoJEOUwvh9pJNURxRUP/RfxscL2wmySc4SlE5T2ucju 
> vDRK/NHvkghW3/tTJ48nY2550NNxMxKELS2CZE02xV+Ivqh9w+zIuy/Olob5YkX/ 
> a0+5n/WQoWor9IcZj0baoxcQhMMTgIdohH2I2PPwpQNSeF2uNy1kX9+hh9/+dMBL 
> zXHYXqdWch6WA16YKHX3+SemEzlXkP3B68WqXLfXvh0BDyPGfrgNZJcRoGUg6JJC 
> p6916iBwuHynq1oCziH1o6ywIwOIIWo6vDiszllH3gdlJsP+Q3YcbkLxn4a7y7Q4 
> CBIvvcxpWUeTgPfwgjkOZs0b2V/hm5BAHyUaKqCDSFNG9weNC8xoOiHo35TmQ9NM 
> rdPAmqQbQicAnIOn98b3w1be4ZLppeONPa59sI3+w+Mz+6iMrSkJR0tUwTxT1UMO 
> 4PW6BfZD4ffLsszGoRnqWMMGi/9D3EVnmXTvVFI6durXCY+ZMb2LPMl53HIX5tw9 
> EAaHZSUUb3Wj0nf2DcfO2xZZDD08ykLA0mJaebFnKSObY0BukF4Uq47FVnJDDcyP 
> 6QrYu1hKv7n4Bf6qjh2mH+8Wu+v0NWWUa8FfjN4FduvYDbQwZLVC1f+CUXFyAm6g 
> i+r0kxyNNhpeAFpZA5j8cKZgPsP2tzVC/QLsmJhIwyw78FJLSoVvPfFTsVEvDIDu 
> 6BHl2di/YMYlIsIqInXE 
> =pIlf 
> -----END PGP SIGNATURE----- 
> 
> _______________________________________________ 
> OpenIndiana-discuss mailing list 
> OpenIndiana-discuss at openindiana.org 
> http://openindiana.org/mailman/listinfo/openindiana-discuss 
> _______________________________________________
> OpenIndiana-discuss mailing list
> OpenIndiana-discuss at openindiana.org
> http://openindiana.org/mailman/listinfo/openindiana-discuss