* Florian Philipp <li...@binarywings.net> [121225 07:16]: > Am 23.12.2012 20:23, schrieb fe...@crowfix.com: > > > > I have since had some time to explore this and find it related to the > > kernel; 3.6.10 works fine, while 3.7.1 fails. If I reset during the > > 3.7.1 boot while it is spewing its error messages, but before the > > kernel ultimately panics, I can reboot with 3.6.10, but if 3.7.1 goes > > all the way to the panic, I have to power off and wait a few minutes > > before a 3.6.10 reboot is succesful. This is repeatable, but I > > haven't bothered to see how long the system must be off; "a few > > minutes" is enough. > > > > There are two error messages during the 3.7.1 boot, repeated for all > > SATA drives: > > > > ata5.00: qc timeout (cmd 0x2f) ata5.00: failed to set xfermode > > (err_mask=0x40) > > > > The code that prints these messages has not been changed since 2011 so I > guess it is a driver issue. You never posted which driver you use > exactly and your kernel config enables all. Therefore I cannot look further. > > The best way to find out what's wrong is to bisect the kernel, i.e. > finding the exact commit that caused the issue to appear. > > http://wiki.gentoo.org/wiki/Kernel_git-bisect > > Unfortunately, there have been 1545 commits between 3.6 and 3.7. With > blind bisection you need 39 kernels to find the issue. Maybe `git log` > can give you a hint which commits might be relevant. > > Regards, > Florian Philipp >
A me too on the problem the original poster is seeing. I too am seeing this on a server I have. 3.7.0 and 3.7.1 both don't work but 3.6.10 works fine. I'm using the sata_mv driver with a SuperMicro (two actually) cards with Marvell MV88SX6081's. These chips and their driver have had some issues in the past. I also looked for changes in the driver and didn't see any. Though I did see some libata changes. I haven't had time to do a git bisect yet. Todd
