https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c1 --- Comment #1 from Robert Davies 2008-12-06 10:45:50 MST --- By swapping the disk onto mobo PATA controller I've managed to install onto the disk. FWIW 11.1 rc1 has similar looking errors as soon as I mounted a reiserfs filesystem on /dev/sdb5, when it started checking the transaction log, including the "ata3: soft resetting link". -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c3 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |rob.opensuse.linux@googlemail.com --- Comment #3 from Tejun Heo 2008-12-07 18:58:45 MST --- I'm sorry that I can't do much about pata_pdc202xx_old :-( but the IDE driver is still enabled. ~/os/suse/head/config/x86_64> grep PDC202XX default CONFIG_BLK_DEV_PDC202XX_OLD=m CONFIG_BLK_DEV_PDC202XX_NEW=m and the installation image _DOES_ contain pdc202xx_old.ko. Can you please try "brokenmodules=pata_pdc202xx_old" again? After the installation media boots, switch to vc2 (ctrl-alt-f2), plug in a usb stick or start networking and fetch /var/log/boot.msg and attach it here. It should have worked the same way as SL110 but our module loading mechanism has changed for SL111 and there have been a few problems. Thanks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c5 Robert Davies changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |NEW Info Provider|rob.opensuse.linux@googlemail.com | --- Comment #5 from Robert Davies 2008-12-08 07:06:57 MST --- oak:/boot # lsmod | grep pdc202 libata 160612 2 pata_amd,pata_pdc202xx_old rob@oak:~> cat /proc/cmdline root=/dev/VolGroup00/LogVol00 resume=/dev/disk/by-id/ata-ST360015A_3KB0LA20-part10 splash=silent vga=0x317 brokenmodules=pata_pdc202xx_old rob@oak:/etc/sysconfig> grep INITRD kernel INITRD_MODULES="processor thermal fan jbd ext3 dm_mod edd" DOMU_INITRD_MODULES="xennet xenblk" Whoops! Is the problem that initrd-2.6.27.7-8-default includes pata_pdc202xx_old, rather than pdc202xx_old IDE driver? Now in past, the initrd was built on install for the host using the INITRD_MODULES line in /etc/sysconfig/kernel. It included the pata_amd and pata_pdc202xx_old modules IIRC (though it's documented in the old bug reports I haven't checked). So I think I had to alter that and rebuild the initrd's. I cannot find a reference to INITRD_MODULES any more in the /sbin/mkinitrd* scripts. Automagic changes are great, if they generally work, and they provide the Admin a way of over-riding, when they don't. At present I am stumped, because I don't see how with YaST2 or with this mkinitrd how I'm meant to configure the system to avoid pata_pdc202xx_old. oak:/boot # grep INITRD /etc/sysconfig/kernel INITRD_MODULES="processor thermal fan jbd ext3 dm_mod edd" DOMU_INITRD_MODULES="xennet xenblk" oak:/boot # find /{,usr/}sbin -name '*initrd*' | xargs grep INITRD Binary file /sbin/.mkinitrd.swp matches /sbin/mkinitrd: egrep -h '%param_' $INITRD_PATH/setup/*.sh | sed 's/^.*_\(.\): \(.*\)$/ tmp_option=\$(read_options_eval \1 \2); [ \"$tmp_option\" ] \&\& cmd_option[\${#cmd_option[@]}]=\"\$tmp_option\"/' > $tmp_dir/$$.params /sbin/mkinitrd:.SH MKINITRD /sbin/mkinitrd:INITRD_PATH=/lib/mkinitrd /sbin/mkinitrd: for setupfile in $INITRD_PATH/setup/*.sh; do /sbin/mkinitrd:scripts_mtime=$( stat -c "%X" "$INITRD_PATH/scripts" ) /sbin/mkinitrd:setup_mtime=$( stat -c "%X" "$INITRD_PATH/setup" ) /sbin/mkinitrd:boot_mtime=$( stat -c "%X" "$INITRD_PATH/boot" ) Can someone involved in the changed module loading mechanism, explain how to select between the driver modules? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c7 --- Comment #7 from Robert Davies 2008-12-08 07:55:25 MST --- Created an attachment (id=258651) --> (https://bugzilla.novell.com/attachment.cgi?id=258651) Live CD boot log requested -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c9 --- Comment #9 from Robert Davies 2008-12-08 13:15:43 MST --- Created an attachment (id=258723) --> (https://bugzilla.novell.com/attachment.cgi?id=258723) Crude benchmark comparing pdc202xx_pld and libata host controller Identical disks, so the numbers should be about the same. There may be an additional case against libata versus old IDE drivers on performance grounds. Note the consistency of the /dev/hda results compared to the much slower /dev/sda. IIRC in past the first disk (libata) was a bit quicker than the 2nd with old IDE driver. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c11 --- Comment #11 from Tejun Heo 2008-12-08 19:08:58 MST --- Also, several more questions to get this fixed. 1. What happens if you just use the pata driver? How does it fail? Can you please post kernel log of the failure or screen shot (ctrl-alt-f4 from installation system) of the failure? 2. Is the benchmark from the same hardware configuration? Minute performance difference can exist in either direction but that's a lot of difference. Can you post kernel logs from both configurations? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c13 --- Comment #13 from Robert Davies 2008-12-09 08:44:11 MST --- Created an attachment (id=258943) --> (https://bugzilla.novell.com/attachment.cgi?id=258943) OS 11.1-RC1 generated YaST2 HW Info -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c15 --- Comment #15 from Robert Davies 2008-12-09 08:50:37 MST --- Created an attachment (id=258947) --> (https://bugzilla.novell.com/attachment.cgi?id=258947) Boot log showing 'resetting link' errors -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c17 --- Comment #17 from Robert Davies 2008-12-09 09:04:39 MST --- So to summarise : 1) Installation fails to disk on PDC20265, at stage where partitioning and filesystems are built. Disk error returned means first pata_pdc202xx_old hosted filesystem wasn't built. 2) When "it works", there's a large number of errors going to messages, subsequent performance is unusably slow. These symptoms occur on hardware that was happily running pata_amd & pdc202xx_old minutes before. pdc202xx_old still appears to work in OS11.1-RC1, the problem is how to avoid pata_pdc202xx_old. As pata_pdc202xx_old bugs have remained for more than a year, with no fix in sight, surely it is a mistake to ship with this experimental driver enabled, if there is no working brokenmodules (or broken_modules) work round. Most OpenSUSE users afflicted by this error, will not have the persistance required to work through this, and will siimply blame the distro. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #258947|application/octet-stream |text/plain mime type| | -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User agraf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c20 Alexander Graf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bwalle@novell.com --- Comment #20 from Alexander Graf 2008-12-10 00:25:49 MST --- Tejun, the default way to override which module to load is to put it into the INITRD_MODULES in /etc/sysconfig/kernel. The modules specified there are loaded in the given order and precede the udev detection. Since we're not including legacy drivers automatically, this change requires a rebuild of the initrd though. If you want to reorder priorities from your point of view, you're pretty lost. I can't think of a way you could possibly detect easily how to switch from one driver to another, as the whole detection is based on the assumption that the "booted system" should be reproduced. So you can either have the user add the module to INITRD_MODULES or have him boot from a "sane" installation medium, that uses the correct driver and build the initrd from there. Btw: bwalle is the new mkinitrd maintainer. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c22 --- Comment #22 from Robert Davies 2008-12-10 08:03:34 MST --- Tejun : I'd be very happy to let you have the controller. I should may be try it in another box, to see if it magically starts working like Alan Cox's does. I have a vague memory there may have been a firmware upgrade, that required "another OS" that I didn't have to apply it (but I may have a copy of original docs and/or packaging). As everything worked at time with the 2.4 ATA (IDE) drivers, it may explain why some ppl have problems, and others not if it could bite us now, after code reworked in pata_*. Alexander : In OS10.3 I did have to rebuild the initrd, and yes I did have pdc202xx_old in the INITRD_MODULES line. So IIRC actually in 10.3 I had to do more than just use "brokenmodules=pdc202xx_old" to get a working system. Now it has built the module with pdc202xx_old (included however pata_pdc202xx_old to, but I guess it's memory is freed with the initrd when unloaded when / is mounted and /lib/modules becomes available). This faithfully does same as my self compiled kernel without pata_pdc202xx_old module. Unfortunately somehow (used tune2fs -L) I broke the logical volume that / is in and it won't mount, in 11.1 now, thought it still does in 10.3. But I think I can fix it by copying root into a new logical volume :) So no worries, it'll be one less Fedora-ism on the box. *grin* The need for driver selection is because in OpenSUSE, some newish "experimental" code, needs to be tested by enthusiasts, before it gets given to enterprise customers. In this case, patapdc202xx_old appears to work reliably for some, and very unreliably for others, depending on some as yet unknown factors in the hardware configurations. So whilst it'd help me considerably, if pata_pdc202xx_old was disabled, it wouldn't get that code the usage in the wild. So for install to work on some boxes, there needs to be a way for the guru to over-ride the default choices. Question 1 : Does the initrd respect "brokenmodules=X" and skip X module, and look for another driver? If so, then would a solution be to add "duplicate" modules into the initrd? Idea 1 : Creating a custom boot iso image CD, which loads and then ejects requesting the Live (or installation) CD/DVD. How hard would a build custom boot CD tool be? Idea 2 : Support an alternative boot, using an initrd without pata_*, using older IDE drivers, rather than the experimental ones. The drawback to this, is that everytime an issue comes up with new "experimental" code, and tried and tested "legacy" code, you'ld need to make another option. The complexity of permutations would rapidly become unworkable, as someone may need different permutations of options. In general, the assumption that "the booted system should be reproduced", is not a very safe one, because a competent sysadmin may need a number of different kernels + initrd's to effectively make profiles. It's also not totally unknown for /boot to be shared across more than 1 distro, or releases of that distro (it may not have been 'supported' but it used to work). However I think by altering INITRD_MODULES and building single kernel & initrd with command line option to mkinitrd, I think the effect of "hardware profiles" is actually achievable on an installed system. Frankly if it is too hard to work with modules and initrd's, what'll happen is that folk will start messing with custom compiled kernels, rather than use generic and create support problems and worsen security through lack of automatic updates. Steffen: I did a egrep -i in /etc/modprobe.d and nothing shows up for pdc202 The problem is that the boot code seems to be loading the module, via the initrd,despite the brokenmodules=X parameter, and there they're just relying on ordering when building the initrd. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User snwint@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c24 --- Comment #24 from Steffen Winterfeldt 2008-12-10 08:17:59 MST --- The module can't get loaded during install. Please check /etc/modprobe.d/ during install time (e.g., when yast comes up first). The module must show up there. If not, maybe there's a spelling error (check /proc/cmdline). -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c26 --- Comment #26 from Tejun Heo 2008-12-10 21:09:01 MST --- So, I suppose the brokenmodules story boils down to live CD initrd doesn't honor brokenmodules and confirmed. Ekk.... this isn't too pretty. Does anyone know who should I cc for live CD initrd problems? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c28 --- Comment #28 from Robert Davies 2008-12-11 02:04:42 MST --- 11.1-RC1 is currently borked on the box, the LVM won't find the Volgroup, though it loads fine and works in 10.3. I think it must be a problem with the initrd built with the pdc202xx_old driver, as the generic kernel boot became 'infected' after making the changes suggested by Alexander. If I can't find how I screwed the LVM, I'll sling in another disk and use good old partitions directly. But I can provide rapidly 10.3 data, for pdc202xx_old and pata_pdc202xx_old. The build-suse-kiso, sounds good, I'll have to give it a spin and see if it's going to be usable by the kind of ppl who post questions on forums. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User agraf@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c30 Alexander Graf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |snorp@novell.com, ms@novell.com --- Comment #30 from Alexander Graf 2008-12-11 03:03:18 MST --- The live CD initrd is created by kiwi, so I'll add ms to CC. Since he's on vacation for the rest of the year though, I'll also add James, as he's the only guy I know atm who knows that code. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c32 --- Comment #32 from Robert Davies 2008-12-11 03:08:14 MST --- Created an attachment (id=259374) --> (https://bugzilla.novell.com/attachment.cgi?id=259374) Live CD boot log requested pata_pdc202xx_old -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c34 --- Comment #34 from Robert Davies 2008-12-11 03:43:09 MST --- Created an attachment (id=259383) --> (https://bugzilla.novell.com/attachment.cgi?id=259383) Net Install CD boot log requested pdc202xx_old -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c36 --- Comment #36 from Tejun Heo 2008-12-11 20:19:03 MST --- Hmm... the lspci output attached on #31 doesn't contain output for the pdc controller. Maybe it's truncated? Eh... can you just ship the controller to me? It's already too late for SL111 anyway and having the controller locally makes things much easier for 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c38 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |NEEDINFO Info Provider| |rob.opensuse.linux@googlemail.com --- Comment #38 from Tejun Heo 2008-12-13 20:01:54 MST --- Thanks for the info, Robert. The problem doesn't seem to be in mode programming but rather in bmdma_setup. Does libata.force=3:udma/25 make any difference? I'll also prep a debug patch soon. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c40 --- Comment #40 from Tejun Heo 2008-12-13 21:18:10 MST --- Okay, kernel built. Please fetch default-base, default and default-extra from the following URL and test it. http://htj.dyndns.org/export/testing/head-i586-bug457037_dbg0/ Thanks. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c42 Robert Davies changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|rob.opensuse.linux@googlemail.com | --- Comment #42 from Robert Davies 2008-12-14 06:43:19 MST --- Created an attachment (id=259960) --> (https://bugzilla.novell.com/attachment.cgi?id=259960) Boot Log with dbg0 kernel rpm Linux version 2.6.27.9-bug457037_dbg0_5367a2d7-default (geeko@buildhost) (gcc version 4.3.2 [ oak:/sw/build # hdparm -tT /dev/sda; hdparm -tT /dev/sdb /dev/sda: Timing cached reads: 468 MB in 2.00 seconds = 233.46 MB/sec Timing buffered disk reads: 90 MB in 3.09 seconds = 29.09 MB/sec /dev/sdb: Timing cached reads: 284 MB in 2.01 seconds = 141.57 MB/sec Timing buffered disk reads: 8 MB in 3.25 seconds = 2.46 MB/sec oak:/sw/build # Looks like it fell back to PIO on adding swap from /dev/sdb -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c44 Robert Davies changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|rob.opensuse.linux@googlemail.com | --- Comment #44 from Robert Davies 2008-12-14 09:47:31 MST --- Created an attachment (id=259963) --> (https://bugzilla.novell.com/attachment.cgi?id=259963) Consequence of forcing udma/25 The SCSI layer errors which cause the box to temporarily freeze, repeat. Log shows v. slow boot up, as /dev/sdb is accessed. -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c46 Robert Davies changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|rob.opensuse.linux@googlemail.com | --- Comment #46 from Robert Davies 2008-12-16 00:35:48 MST --- Moving the PDC202 controller to a PIII, i820 box with a Maxtor 20GB disk, I could not initially reproduce the problem with a Maxtor 20GB disk. Then booting up with one of the Seagate ST360015A 60GB disks, I have the SCSI errors with a failed write (ATA bus error) as in the AMD-768. So that explains the reproducability problem. Will you have access to this model disk? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c48 --- Comment #48 from Robert Davies 2008-12-16 01:20:18 MST --- Unfortunately I can't check that theory out with a different disk, from around 2003, I only have those 2 Seagates the "in drive" at the time. An older 10GB Barracuda ST310220A works same as the Maxtor. Oh this might be interesting! http://lkml.indiana.edu/hypermail/linux/kernel/0102.3/0623.html Partition Check: hde: [PTBL] [1826/255/63] hde1 hde2 < hde5hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } hde: dma_intr: error=0x10 { SectorIdNotFound }, LBAsect=32885055, sector=0 hde: dma_intr: status=0x51 { DriveReady SeekComplete Error } [last repeats 3-4 times] hde: DMA disabled pata_pdc202xx_old shows : <6>ata3.00: configured for UDMA/66 <6>ata3: EH complete <4>ata3.00: limiting speed to UDMA/33:PIO4 <3>ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 <3>ata3.00: BMDMA stat 0x24 <3>ata3.00: cmd ca/00:08:68:5c:fd/00:00:00:00:00/e2 tag 0 dma 4096 out <3> res 51/84:00:68:5c:fd/00:00:00:00:00/e2 Emask 0x10 (ATA bus error) <3>ata3.00: status: { DRDY ERR } <3>ata3.00: error: { ICRC ABRT } <6>ata3: soft resetting link The Asus A7V mobo had an onboard PDC20265, like the BP6 had the HPT366 PATA IDE controller. That thread suggests at the time at least someone ran into DMA issue; so perhaps there's a clue if some IDE/ATA driver changes were made for newer disks in/around 2001? -- 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.

https://bugzilla.novell.com/show_bug.cgi?id=457037 User rob.opensuse.linux@googlemail.com added comment https://bugzilla.novell.com/show_bug.cgi?id=457037#c50 --- Comment #50 from Robert Davies 2008-12-22 05:34:34 MST --- Better Work Round Rather than changing the drivers etc etc. Boot Linux off the system disk, and simply replace the Promise controller with a newer Ultra 133 TX2, which uses a different driver. They're inexpensive and changing the card out will take less time, than simplifying a system down, and installing. A bonus will be a disk transfer rate that matches the Onboard IDE controller, rather than about 2MB/s less that was achievable with the old IDE driver, on the older card. -- 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.