Bug 804602 - ite_cir: Kernel panic during bootup in kernel versions > 3.2.7-1
Summary: ite_cir: Kernel panic during bootup in kernel versions > 3.2.7-1
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 16
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Jarod Wilson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-03-19 11:44 UTC by Stephen So
Modified: 2012-06-01 18:14 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-01 18:14:26 UTC
Type: ---


Attachments (Terms of Use)
Photo of the error messages during lockup (1.27 MB, image/jpeg)
2012-03-19 11:44 UTC, Stephen So
no flags Details

Description Stephen So 2012-03-19 11:44:35 UTC
Created attachment 571092 [details]
Photo of the error messages during lockup

Description of problem:

The last set of kernel updates have caused kernel panics during bootup. Unfortunately this is not recorded in the system logs. So I can only take a photo of the screen during the lockup. The last known working kernel version (which I am using now) is kernel-3.2.7-1.fc16.x86_64.

Version-Release number of selected component (if applicable):

kernel-3.2.10-3.fc16.x86_64

How reproducible:

Always

Steps to Reproduce:
1.  Start PC and boot into Fedora 16
2.  
3.
  
Actual results:

After a while, the kernel panics

Expected results:

Should boot normally

Additional info:

The error messages are long and scroll off the screen.  I've taken a photo of the messages.  They do not show up in /var/log/messages

Comment 1 Stephen So 2012-03-23 00:16:42 UTC
Even the latest kernel update kernel-3.3.0-4.fc16.x86_64 has this problem.

Found a similar issue here:

https://bbs.archlinux.org/viewtopic.php?pid=1073958

After blacklisting the ite_cir module, booting now works!!

Comment 2 Jarod Wilson 2012-03-23 14:54:21 UTC
I'll dig out my ite-cir hardware and see what I can see.

Comment 3 Jarod Wilson 2012-04-19 20:57:02 UTC
There's a patch underway for this, it actually looks like a problem that could hit multiple lpc super i/o based CIR drivers. Will make sure that all gets upstream shortly, with stable cc'd.

Comment 4 Stephen So 2012-05-30 02:06:20 UTC
Just wanted to report that this problem still exists in the new Fedora 17 on kernel-3.3.4-5.fc17.x86_64

Comment 5 Jarod Wilson 2012-05-30 16:08:49 UTC
Try 3.3.7-whatever from updates, not sure if it has the fix, but this did get merged upstream and head to multiple stable trees as well. Worst case, I'm certain this is fixed in 3.4, and f17 will be rebased to a 3.4 kernel later this week, iirc.

Comment 6 Stephen So 2012-06-01 12:36:15 UTC
I can confirm that the problem has gone away with the latest kernel 3.3.7-1

Comment 7 Stephen So 2012-06-01 12:36:57 UTC
I can confirm that the problem has gone away with the latest kernel 3.3.7-1


Note You need to log in before you can comment on or make changes to this bug.