[arch-dev-public] linux-3.6.2-1 ready for [core]?
Hi guys, Upstream changes: http://kernelnewbies.org/LinuxChanges Please report any issues that stops moving this series to [core]. Thanks. greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
Am 13.10.2012 08:32, schrieb Tobias Powalowski:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that stops moving this series to [core]. Thanks.
I think it is ready. Let's move this after signoffs are there.
On Sat, Oct 13, 2012 at 08:32:41AM +0200, Tobias Powalowski wrote:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that stops moving this series to [core]. Thanks.
greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
I have a reliably reproduced WARN_ONCE on boot, but I'm sure that if I were to disable CONFIG_INTEL_IDLE (a new option), it'd go away. It seems to be harmless. Call Trace: <IRQ> [<ffffffff8105bede>] ? warn_slowpath_common+0x76/0x8a [<ffffffff811ae8f6>] ? __blk_put_request+0xd8/0xf8 [<ffffffff811aeb83>] ? blk_end_bidi_request+0x36/0x53 [<ffffffff812606a5>] ? scsi_io_completion+0x15e/0x448 [<ffffffff8127dcb3>] ? ahci_interrupt+0x543/0x590 [<ffffffff811b33f5>] ? blk_done_softirq+0x5d/0x6c [<ffffffff8106201b>] ? __do_softirq+0x99/0x13b [<ffffffff81391cac>] ? call_softirq+0x1c/0x30 [<ffffffff8102cd5d>] ? do_softirq+0x2c/0x5f [<ffffffff810622e9>] ? irq_exit+0x3f/0xa4 [<ffffffff8102caa4>] ? do_IRQ+0x90/0xa6 [<ffffffff81390427>] ? common_interrupt+0x67/0x67 <EOI> [<ffffffff811ff31f>] ? intel_idle+0xe6/0x10b [<ffffffff811ff2fa>] ? intel_idle+0xc1/0x10b [<ffffffff812bb6cf>] ? cpuidle_enter_state+0xa/0x31 [<ffffffff812bb75b>] ? cpuidle_idle_call+0x65/0x93 [<ffffffff810327ba>] ? cpu_idle+0x9d/0xf6 [<ffffffff8167fa2d>] ? start_kernel+0x380/0x38b [<ffffffff8167f4c4>] ? do_early_param+0x83/0x83 d
Am 13.10.2012 12:15, schrieb Dave Reisner:
On Sat, Oct 13, 2012 at 08:32:41AM +0200, Tobias Powalowski wrote:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that stops moving this series to [core]. Thanks.
greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
I have a reliably reproduced WARN_ONCE on boot, but I'm sure that if I were to disable CONFIG_INTEL_IDLE (a new option), it'd go away. It seems to be harmless.
intel idle is far from new, it has been around for at least a year.
On Sat, Oct 13, 2012 at 01:16:58PM +0200, Thomas Bächler wrote:
Am 13.10.2012 12:15, schrieb Dave Reisner:
On Sat, Oct 13, 2012 at 08:32:41AM +0200, Tobias Powalowski wrote:
Hi guys,
Upstream changes: http://kernelnewbies.org/LinuxChanges
Please report any issues that stops moving this series to [core]. Thanks.
greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
I have a reliably reproduced WARN_ONCE on boot, but I'm sure that if I were to disable CONFIG_INTEL_IDLE (a new option), it'd go away. It seems to be harmless.
intel idle is far from new, it has been around for at least a year.
Huh, since 2010 apparently. Strange that it hasn't bothered me until now. Guess I need to report this.
participants (3)
-
Dave Reisner
-
Thomas Bächler
-
Tobias Powalowski