| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Thu, 14 Apr 2011 23:32:27 -0400 From: Mark Lord <kernel@...savvy.com> To: Mikael Abrahamsson <swmike@....pp.se> CC: Bruce Stenning <b.stenning@...igovision.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "linux-ide@...r.kernel.org" <linux-ide@...r.kernel.org> Subject: Re: sata_mv port lockup on hotplug (kernel 2.6.38.2) On 11-04-14 11:15 PM, Mikael Abrahamsson wrote: > On Fri, 8 Apr 2011, Bruce Stenning wrote: > >> The 2.6.38.2 kernel still exhibits the same lockups that we see with the >> 2.6.26 kernel. > > Hi. > > I have some input on this. I have one of these controllers and had problems with > one channel where if I had a drive in that hotswap bay, the controller wouldn't > even POST at boot. It just stuck in the detection phase in the controller BIOS. > > When I tested hotplugging into that bay when the system was running, I received > a kernel warning (it's not powered on at the moment so I can't provide the > output, if it's important I can get it). I would like to see the output, next time you can get it. The thing with the 6041 chip, is that I actually have all of the Marvell documentation and errata info for the chip. So in theory, we know everything about it, and there are no secret failure modes yet to be discovered. The sata_mv driver does not depend on the board's BIOS for anything either. That's the theory, anyway. :) Cheers -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists