At Tue Dec 01 01:04:55 -0500 2009, Tejun Heo wrote: > On 11/13/2009 04:43 AM, Alex Vandiver wrote: > > ata2.00 is always the port which is reset. The only other person to > > see that error seems to have been Tim Blechmann, in > > <4AC9C373.80603@xxxxxxxxxx>, which had similar symtoms. lspci -v for > > this machine's IDE controllers is: > > Can you please attach full dmesg output after such event? My original post included both 'goodboot' and 'badboot' files, which were the dmesg output from a successful boot, and a failed boot with the event -- is that not what you are looking for? Apologies if I'm misunderstanding. I tried 2.6.32-rc6 at the time as well -- it happened to have the fault much more often, and showed that both ata2.00 and ata2.01 could be affected. I've attached dmesg output from a successful boot, as well as dmesg output from a boot which affected sdc, and a boot which affected sdd. - Alex -- Networking -- only one letter away from not working
Attachment:
goodboot.2.6.32-rc6
Description: Binary data
Attachment:
sdc-badboot.2.6.32-rc6
Description: Binary data
Attachment:
sdd-badboot.2.6.32-rc6
Description: Binary data
