Bug 11826
Summary: | extreme slowness of IO stuff using 2.6.28-rc1 | ||
---|---|---|---|
Product: | Timers | Reporter: | Yves-Alexis Perez (corsac) |
Component: | Other | Assignee: | Jeff Garzik (jgarzik) |
Status: | CLOSED CODE_FIX | ||
Severity: | normal | CC: | alex.shi, elendil, rjw, trenn |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.28-rc1 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 11808 | ||
Attachments: |
.config for 2.6.28-rc1 on T61
dmesg for 2.6.28-rc1 on T61 |
Description
Yves-Alexis Perez
2008-10-25 04:25:57 UTC
Created attachment 18434 [details]
.config for 2.6.28-rc1 on T61
As a side note, the boot process until the next lockup, where I need to press alt again, etc. And when the laptop is finally booted, it's nearly usable, when one uses the keyboard constantly. But it still blocks when some io is done without keyboard events. But maybe it has nothing to do with ata stuff, and maybe it's a luks problem, where it needs enough interupts and entropy generation from it, but it sounds a bit weird. I'm attaching the dmesg when booted. Created attachment 18435 [details]
dmesg for 2.6.28-rc1 on T61
Looks like you're having an IRQ routing problem. Does pci=noacpi help? How about irqpoll? pci=noacpi doesn't help. irqpoll seems to fix the problem. btw, when activating the luks encrypted volume, I first get: alg: cipher: Test 1 failed on encryption for aes-asm Not sure if it's related, (and it fixes the problem but kind of break the trackpoint, so not really a usable workaround :) ) Thomas, this one looks like an IRQ routing problem. Any ideas? FTR, -rc2 doesn't fix the problem. *** Bug 11893 has been marked as a duplicate of this bug. *** References : http://marc.info/?l=linux-kernel&m=122521238402963&w=4 Handled-By : Arjan van de Ven <arjan@linux.intel.com> Notify-Also : "Carlos R. Mafra" <crmafra2@gmail.com> Notify-Also : Frans Pop <elendil@planet.nl> On Sunday, 2 of November 2008, Yves-Alexis Perez wrote:
> On dim, 2008-11-02 at 17:06 +0100, Rafael J. Wysocki wrote:
> > The following bug entry is on the current list of known regressions
> > from 2.6.27. Please verify if it still should be listed and let me
> > know
> > (either way).
>
> Yes it should be :)
First-Bad-Commit : dc4304f7deee29fcdf6a2b62f7146ea7f505fd42 *** Bug 11987 has been marked as a duplicate of this bug. *** I've tried with -rc4 and it *seems* fixed. I'll check during next days it's ok. |