https://bugzilla.novell.com/show_bug.cgi?id=248860 teheo@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |imotgm@yahoo.com ------- Comment #27 from teheo@novell.com 2007-04-07 04:03 MST ------- Weird, as long as the file name matches the device ID and it contains the line, it should work, hmmm, unless you have it loaded in initrd. This is "Load Module in initrd" option in yast->hardware->disk controllers->it8212 controller. If it's checked, uncheck it and press apply, initrd will be generated without it821x drivers. If it's already unchecked, please double check the filename and the content is correct. You can find out the PCI device ID by running 'lspci -nn'. If booting is too painful, I suggesting disabling the controller in the BIOS menu if possible or disconnect the disks physically. In the Mandrivia boot log, the kernel is 2.6.17 so pata_it821x isn't there yet. IRQ routing is different but I don't think that's significant as IRQ seems to be working in the suse kernel too. Hmmm... Okay, this is interesting. The mdv kernel is choking on harddrives too. hdg: 390721968 sectors (200049 MB) w/8192KiB Cache, CHS=24321/255/63, BUG hdg:hdg: recal_intr: status=0x51 { DriveReady SeekComplete Error } hdg: recal_intr: error=0x04 { DriveStatusError } hdc: dma_intr: status=0x51 { DriveReady SeekComplete Error } hdc: dma_intr: error=0x84 { DriveStatusError BadCRC } ide: failed opcode was: unknown hdc: dma_timer_expiry: dma status == 0x60 hdc: DMA timeout retry hdc: timeout waiting for DMA hdg is attached to it821x and hdc to sata_nv. BadCRC and DMA timeout expiry indicate transmission failure on the IDE cables. It seems like something is wrong system-wide. IDE layer sometimes reacts okay to such error conditions, at other times, it can lock the machine up hard. That's one of the reasons why new libata drivers are being implemented. libata error handling is reliable but tends to take a long time under certain conditions - being worked in the devel tree. Well, sometimes, drivers don't even matter because some IDE controllers just hold PCI bus and never releases on certain error conditions. No software can save the machine from that. 10.2 reacting especially badly might be caused not by kernel changes but by userland changes. Automounting, indexing kind of stuff. As you can see from the 10.2 boot.msg w/ pata_it821x, the drive doesn't spew error messages during detection phase and reading the partition proceeds without any problem. So, the driver and controller is working. It's only later that things go bad. In older distributions, after detection nothing much really happens, but we're doing a lot of automatic things lately. Anyways, you need to fix the root cause and my current best bet is power supply. I think it's either overloaded or dying out (they do, really). Please try to lessen power consumption by disconnecting some devices or try to connect them differently. It would be best if you've got an extra powersupply to try out. They're really cheap these days. If it's not PSU, please scream at me. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.