https://bugzilla.kernel.org/show_bug.cgi?id=24702 Summary: Possible bug - crash during IDE interface probing. Product: IO/Storage Version: 2.5 Kernel Version: 2.6.36.2 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: IDE AssignedTo: io_ide@xxxxxxxxxxxxxxxxxxxx ReportedBy: software+linux-kernel@xxxxxxxxxxxxxxx Regression: No With 2.6.36.1, IDE probing worked. Kernel boots. With 2.6.36.2, IDE probing crashed kernel. Hardware: AMD Athlon (x86) 32-bit single-core. SiS5513 IDE interface. PC Chips 810MLR motherboard (from 2002). GCC 4.5.1. [The machine is due for retirement soon. Its replacement may be ordered before 2010 ends.] When I upgraded (using the same basic configuration file) from .1 to .2, the .2 kernel repeatedly crashed at the point where it displayed on the screen "found SiS5513 IDE interface" and listed it's PCI/IRQ/port numbers, but before it printed any such device (hard drive, cdrom, etc.) found on the interface cable. Interrupts appear disabled as a keyboard CTRL+ALT+DEL was non-functional, nor was screen buffer lookback or keyboard LEDs for caps, num, or scroll lock. Since the kernel initalization never finished, I have no logs. A review of the changelog for .2 did not yield any change to the IDE driver, but some DMA and IRQ stuff was changed. It's quite possible that some kernel configuration setting combinations yield a non-working kernel. However, I saw no differences that explain such. Therefore, I must ask first: Is there a bug here? If so, with what? If not, then where did my configuration go wrong? Thanks. -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
