https://bugzilla.novell.com/show_bug.cgi?id=474879 User DOlsson@WEB.de added comment https://bugzilla.novell.com/show_bug.cgi?id=474879#c1 --- Comment #1 from Dennis Olsson 2009-02-11 11:30:20 MST --- Created an attachment (id=271988) --> (https://bugzilla.novell.com/attachment.cgi?id=271988) Output from "lspci -nn" -- 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=474879 User DOlsson@WEB.de added comment https://bugzilla.novell.com/show_bug.cgi?id=474879#c3 --- Comment #3 from Dennis Olsson 2009-02-11 11:41:26 MST --- Created an attachment (id=271995) --> (https://bugzilla.novell.com/attachment.cgi?id=271995) Tar (-cjf) file containing: boot.msg lsmod lspci-nn messages partitions-0before partitions-1after Booting with brokenmodules=pata_hpt37x results in disc order: hpt: sd[abc] sil: sd[defg] usb: sdh meaning that the "1" = "/dev/sda1" and "" = "/dev/sdb1". How come that this order is used? - Doing a "fsck -fn 1" => always results in OK. - Doing a "fsck -f 1" => always results in OK. - Doing a "fsck -fn 1" => always results in OK. - Doing a "fsck -f 1" => always results in drive crash. Rebooting same issue => Reset needed. -- 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=474879 User DOlsson@WEB.de added comment https://bugzilla.novell.com/show_bug.cgi?id=474879#c5 --- Comment #5 from Dennis Olsson 2009-02-11 11:45:20 MST --- Created an attachment (id=271997) --> (https://bugzilla.novell.com/attachment.cgi?id=271997) Tar (-cjf) file containing: boot.msg lsmod lspci-nn messages partitions-0before partitions-1after Booting with brokenmodules=pata_hpt3x2n,hpt366 results in disc order: sil: sd[abcd] usb: sde hpt: sd[fgh] meaning that the "1" = "/dev/sdf1" and "" = "/dev/sdg1". - Doing a "fsck -fn 1" => always results in OK. - Doing a "fsck -f 1" => always results in OK. - Doing a "fsck -fn 1" => always results in OK. - Doing a "fsck -f 1" => always results in drive crash. Rebooting same issue => Reset needed. Although the "brokenmodules=pata_hpt3x2n,hpt366" has been given, both of these drivers are *still* being loaded and used (see "lsmod" and "boot.msg")!! Why?? -- 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=474879 User DOlsson@WEB.de added comment https://bugzilla.novell.com/show_bug.cgi?id=474879#c7 --- Comment #7 from Dennis Olsson 2009-02-11 11:48:56 MST --- Created an attachment (id=272002) --> (https://bugzilla.novell.com/attachment.cgi?id=272002) Tar (-cjf) file containing: boot.msg lsmod lspci-nn messages partitions-0before Booting with irqpoll as suggested in the error messages found in "/var/log/message", results in disc order: sil: sd[abcd] usb: sde hpt: sd[fgh] meaning that the "1" = "/dev/sdf1" and "" = "/dev/sdg1". How come that this order is used? - Doing a "fsck -fn 1" => always results in OK. - Doing a "fsck -f 1" => always results in OK. - Doing a "fsck -fn 1" => always results in OK. - Doing a "fsck -f 1" => always results in total system death! After having received the "bootnew: 11/64256 files ..." line from "fsck", the system is completely dead! No reaction on ALT-Fx, RETURN or CTRL-ALT-DEL -- Only pushing "reset" button gets the system back running. And, although a "tail -f /var/log/messages" was running in the background, no messages were displayed after the last line from "fsck" (as was the case in during the other crashes). -- 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=474879 Cyril Hrubis changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.pr |kernel-maintainers@forge.pr |ovo.novell.com |ovo.novell.com -- 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=474879 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=474879#c9 Tejun Heo changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO Info Provider| |DOlsson@WEB.de --- Comment #9 from Tejun Heo 2009-02-25 01:13:38 MST --- Hello, sorry about the delay. * Highpoint controllers curiously share the same PCI ID for completely different controllers. So, the driver loader (udev in this case) doesn't know in prior which driver to load. Only the drivers themselves can determine whether they can drive the controller during initialization, so they take turn until the correct one (pata_hpt3x2n in this case) grabs the controller. And the hpt366 driver is the original IDE driver which is there only for debugging and falling back when the new libata ones don't work as in your case. * Device names are not guaranteed to be stable. libata no longer pre-allocates device nodes to specific port as IDE did (just can't do it in reasonable way anymore). It generally stays stable with PCI devices but there is no guarantee. USB probing is done asynchronously, so depending on luck, it can end up anywhere. Plus, with upcoming parallel libata probing, things will get even more dynamic. So, devices should be selected via unique device ID (the default) or filesystem labels. This also allows putting in extra controllers or moving drives around can be done without worrying about device node renames. * There are still some rough edges on a few libata drivers for old PATA controllers, mostly due to lack of hardware availability and test coverage. Are you interested in shipping the controller to me so that I can work on it? I'll pay for the shipping + replacement controller. 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=474879 User DOlsson@WEB.de added comment https://bugzilla.novell.com/show_bug.cgi?id=474879#c11 --- Comment #11 from Dennis Olsson 2009-03-08 13:55:34 MST --- Hello Tejun. Well, this drive complex turns out to be a lot more complex than expected. Anyway, I did find a bug in "pata_hpt3x2n.c" line 585, which explains my confusion reading through the log file: drivers/ata/pata_hpt3x2n.c:585 printk(KERN_INFO "pata_hpt37x: bus clock %dMHz, using 66MHz DPLL.\n", pci_mhz); should read: printk(KERN_INFO "pata_hpt3x2n: bus clock %dMHz, using 66MHz DPLL.\n", pci_mhz); Also, I have tried to boot from openSUSE 10.3 and openSUSE 11.0 GM DVDs: openSUSE 10.3: - During driver probing: HighPoint HPT372A/372N drivers: pata_hpt37x, pata_hpt3x2n, hpt366 loading: pata_hpt37x - lsmod shows all hpt drivers as being loaded Using the "pata_hpt37x" driver here in openSUSE 10.3, the driver works. Discs accessable via "/dev/hd[acd]". openSUSE 11.0: - During driver probing: HighPoint HPT372A/372N drivers: pata_hpt37x, pata_hpt3x2n, hpt366 loading: pata_hpt3x2n - lsmod shows *only* "pata_hpt3x2n" driver as being loaded System crashes just as under openSUSE 11.1, when using the discs "/dev/sd[efg]" associated with the controller. OpenSUSE 11.1: - During driver probing: HighPoint HPT372A/372N drivers: pata_hpt37x, pata_hpt3x2n*, hpt366 - lsmod shows all hpt drivers as being loaded Hope this info is of some help to you. ++CHeers/DO++ -- 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=474879 User teheo@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=474879#c13 --- Comment #13 from Tejun Heo 2009-03-08 18:09:19 MST --- Alright, just sent. -- 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.