Bug 16562 - 2.6.35: cpu_idle bug report / on i7 870 cpu (x86_64)
Summary: 2.6.35: cpu_idle bug report / on i7 870 cpu (x86_64)
Alias: None
Product: Platform Specific/Hardware
Classification: Unclassified
Component: x86-64 (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: platform_x86_64@kernel-bugs.osdl.org
Depends on:
Blocks: 16055
  Show dependency tree
Reported: 2010-08-11 14:10 UTC by Maciej Rutecki
Modified: 2012-08-13 15:46 UTC (History)
4 users (show)

See Also:
Kernel Version: 2.6.35
Regression: Yes
Bisected commit-id:


Description Maciej Rutecki 2010-08-11 14:10:10 UTC
Subject    : 2.6.35: cpu_idle bug report / on i7 870 cpu (x86_64)
Submitter  : Justin Piszcz <jpiszcz@lucidpixels.com>
Date       : 2010-08-06 22:09
Message-ID : alpine.DEB.2.00.1008061800530.5241@p34.internal.lan
References : http://marc.info/?l=linux-kernel&m=128113260904048&w=2

This entry is being used for tracking a regression from 2.6.34. Please don't
close it until the problem is fixed in the mainline.
Comment 1 Justin Piszcz 2010-09-21 08:36:46 UTC

Please close this bug for now, I have a case open with 3ware regarding the controllers that appear to be causing I/O lockups, when the tests were performed (w/cpu_idle), it turned out that I have cron jobs that run at certain times (rss2email) and when they run, they produce a certain kind of I/O that locks up the machine until the controller(s) reset with 2.6.35.x, with 2.6.34.x the problem does not occur.

[  593.967176] 3w-9xxx: scsi0: WARNING: (0x06:0x0037): Character ioctl (0x108)
timed out, resetting card.
[  730.483812] 3w-9xxx: scsi0: WARNING: (0x06:0x0037): Character ioctl (0x108)
timed out, resetting card.
Comment 2 Justin Piszcz 2010-09-21 09:11:10 UTC

It may be CPU related afterall according to this post that I found, I am going to test what he found and see if the 2.6.35.x kernel is stable with the options he recommends to be disabled.
Comment 3 Rafael J. Wysocki 2010-09-21 18:14:44 UTC
Well, failing with CONFIG_NOHZ is still a bug and the fact that it didn't occur with 2.6.34 means we've changed something that triggers it recently.

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