Summary: | System lockup, pdc20265, asus-a7v multiple drives. | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Dennis Östergren <swed> |
Component: | [OLD] Core system | Assignee: | Gentoo Kernel Bug Wranglers and Kernel Maintainers <kernel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | critical | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | http://bugzilla.kernel.org/show_bug.cgi?id=2494 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Dennis Östergren
2004-08-23 23:13:22 UTC
Hello, I'm not screaming YES, just yet, but it seems as if the following URI: http://forums.gentoo.org/viewtopic.php?p=1417524#1417524 solved my problem as well. The lines in question are : Edit : /usr/src/linux/drivers/ide/ide-io.c and change the lines as indicated : - if (hwif->irq != masked_irq) + if (masked_irq != IDE_NO_IRQ && hwif->irq != masked_irq) - if (hwif->irq != masked_irq) + if (masked_irq != IDE_NO_IRQ && hwif->irq != masked_irq) I performed the above changes and it "appears" to have worked. I'll do some more testing... Please paste in the output of `cat /proc/interrupts`. Hello, I've successfully managed to transfer some 40 GB of data, 20GB from one drive to the other and back again, without hickups, and without any strange entries to dmesg. I don't know if the applied patch can be regarded as a proper fix for whatever problem I had, but after applying it, I'm unable to reproduce the problem. Output from /proc/interrupts: gentoo mp3 # cat /proc/interrupts CPU0 0: 1425082 XT-PIC timer 1: 7122 XT-PIC keyboard 2: 0 XT-PIC cascade 5: 1319433 XT-PIC eth0 9: 0 XT-PIC Ensoniq AudioPCI 10: 1553067 XT-PIC ide2, ide3 11: 267968 XT-PIC nvidia 12: 67914 XT-PIC PS/2 Mouse 15: 13 XT-PIC ide1 NMI: 0 LOC: 1425020 ERR: 453 Hm, ide2 and ide3 are on the same interrupt which is possibly why you were getting this problem. Either way, this bug exists in the upstream kernel so could you file a bug at http://bugme.osdl.org with the patch so the upstream developers can get it included or look further at the issue? Thanks! Sure, will do. |