https://bugzilla.novell.com/show_bug.cgi?id=244309 fabian.herschel@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |ASSIGNED Info Provider|fabian.herschel@novell.com | ------- Comment #7 from fabian.herschel@novell.com 2007-03-23 01:26 MST ------- Unfortunately the parameter did not changed the problem status (if I got your explanation about libata.ata_acpi=0 correctly this was not expected?). But yes, the annoying error messages are gone: furka:~ # hwinfo 2>&1 | grep -i error sit0: GLINK ethtool error: Invalid argument After setting libata.ata_acpi=0 the complete kernel command line is: furka:~ # cat /proc/cmdline root=/dev/sda2 vga=0x31a nolapic resume=/dev/sda1 splash=silent libata.ata_acpi=0 Now my questions: 1. Which info should I provide now? 2. Can the problem be forced by the nolapic param (don't know where it came from) - I will test asap, what happens, if I remove it. 3. You claimed two advantages of your parameter (a) error messages b) verify). How could I get the verification result that ACPI failures are not mysteriously interacting with command executions? -- 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.