I'm not running Ubuntu Hardy on the laptop, where I've been experiencing said bug. But I can confirm that this bug is fixed for me in stock 2.6.23.1-12, which is my current kernel on this SIS630-laptop.
So I guess it's safe, to mark _this_ bug as FIXED for hardy.
Yaztromo's symptoms seem to be a different bug to me, too. BTW: Not only does the pata_sis module decrease performance significantly when compared to the old sis5513 module, it is still marked EXPERIMENTAL in kernel-config (even in 2.6.24). Maybe it would really be a wise idea to stick with the old IDE-module until pata_sis has stabilized. The differering device names (hda vs. sda) could be circumvented by some simple udev-rule. In my oppinion this would be a good idea at least for the server-kernel.
( Although I don't think any clever mind would build an important server on SIS-hardware. ;-)
I'm not running Ubuntu Hardy on the laptop, where I've been experiencing said bug. But I can confirm that this bug is fixed for me in stock 2.6.23.1-12, which is my current kernel on this SIS630-laptop.
So I guess it's safe, to mark _this_ bug as FIXED for hardy.
Yaztromo's symptoms seem to be a different bug to me, too. BTW: Not only does the pata_sis module decrease performance significantly when compared to the old sis5513 module, it is still marked EXPERIMENTAL in kernel-config (even in 2.6.24). Maybe it would really be a wise idea to stick with the old IDE-module until pata_sis has stabilized. The differering device names (hda vs. sda) could be circumvented by some simple udev-rule. In my oppinion this would be a good idea at least for the server-kernel.
( Although I don't think any clever mind would build an important server on SIS-hardware. ;-)