Hi, Jeremy, Thanks for the information about this issue. I'm in the power user category, never compiled the kernel before (well, maybe a couple of times), pretty knowledgeable about stuff but not enough to read the alias. I write training material for servers for a living so I'm good technically but not to with it when it comes to Linux troubleshooting.
So I'm looking for a pretty simple workaround, if one exists. Responses inline > Hi David, > > I don't know if you follow the linux-ide mailing list, but there's been > a ton of work done on SATA error handling, the sata_nv driver, and NCQ > support between 2.6.16 and 2.6.25. > > I have been paying attention, looking to find SATA Port Multiplier > support the moment it's ready. I don't think it's in Hardy kernel BTW. > > I'm curious to know more about your issue. Are you setting Write Cache > off? That triggers it for me since it doesn't take much write load to > cause multiple outstanding commands that way. Nope. Just a plain vanilla setup on a Sun Ultra 40 (not the M2). I can send you dmesg output from Hardy and/or SuSE w/2.6.19 kernel if you like. The nVidia chipset on this machine is suspected of being a problem, according to some other threads I've read. > > What filesystem are you using, do you use device-mapper, anything else > about your setup, like smartd, mdadm daemon, that might be accessing the > drives? Just plain old ext3 (I think - I don't have the system in front of me right now). > > My impression of Hardy (which is supposed to be a long-term release - > LTS) is that it's going out on schedule, no matter how many unresolved > issues... sadly it feels like windows a bit. I'm a bit upset they > deferred this patch, yet managed to find the time to introduce other > kernel changes that disabled a number of sound cards. > > so a word to the wise, test like crazy, 2.6 series is undergoing a ton > of changes upstream as well. buyer beware. Understood. But I'm basically just a hobbyist / power user type so no big deal. > > As for kernel command line, I haven't tried these, but you can turn off > ADMA mode, as well as NCQ. But the real fix is the patch I mentioned in > the Ubuntu ticket. It gives the exact GIT commit ID, as well as a > reference to the mailing list post about it. You can rebuild your kernel > from source + that patch for a fix. If you know the command-line options to do that, that would be great. I'd give it a try tonight. If you could point me at a tutorial on obtaining and applying a patch, that would be nice, too. I could probably figure it out. > > I may have to use the Hardy kernel source + that patch until they > release the fix, or go back to Gutsy kernel and patch in the dme1737 > hardware monitor driver. I can certainly wait for 8.04.1, or switch off to another distro with a more up to date kernel if need be. I have no good reason to get off of SuSE other than I want my home machine to have the same configuration as my work machine. Thanks, David > > > On Tue, 2008-04-15 at 14:34 +0000, David Goldsmith wrote: >> I believe I've hit the same bug running Hardy beta on a Sun Ultra 40 >> with HDS7225S. >> >> I've had related kernel problems since about 2.6.20 and am eager to get >> off of SuSE 10.2 (running 2.6.19), which is the last kernel I've been >> able to boot reliably. Far less errors in the kernel supplied with >> Hardy, but I still hit this bug about every other boot. >> >> Any word on the prospects of a fix for this in Hardy, and if not, how >> might I go about getting a patch? Or, is there a boot param I might use >> as a workaround? >> >> Thanks, >> >> David >> > -- > Jeremy Jackson > Coplanar Networks > (519)489-4903 > http://www.coplanar.net > [EMAIL PROTECTED] > > -- > sata_nv regression, reboots system > https://bugs.launchpad.net/bugs/210637 > You received this bug notification because you are a direct subscriber > of the bug. > > -- sata_nv regression, reboots system https://bugs.launchpad.net/bugs/210637 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
