Jeffrey Ross wrote: > Dean S. Messing wrote: > > I'm experiencing strange "stalls" (lockups) in my system that last for > > half a minute or so. Can anybody give me a clue for how to fix this? > > > > I've discovered that they coincide with these messages being > > written to /var/log/messges: > > > > Jun 5 15:07:23 localhost kernel: ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen > > Jun 5 15:07:23 localhost kernel: ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x4a data 8 in > > Jun 5 15:07:23 localhost kernel: res 40/00:03:00:00:00/00:00:00:00:00/a0 Emask 0x4 (timeout) > > Jun 5 15:07:30 localhost kernel: ata2: port is slow to respond, please be patient (Status 0xd0) > > Jun 5 15:07:53 localhost kernel: ata2: port failed to respond (30 secs, Status 0xd0) > > Jun 5 15:07:53 localhost kernel: ata2: soft resetting port > > Jun 5 15:07:54 localhost kernel: ata2.00: configured for UDMA/33 > > Jun 5 15:07:54 localhost kernel: ata2: EH complete > > .....<snip>..... > > > > Dean > > > > > Dean, I am also experiencing lockups on Fedora 7 and I also get the same > messages in the logs. Question did "combined_mode=libata" resolve the > issue for now? No, they are occurring with the option. I set the option some time ago under 2.6.19. It seems like I started geting the lockups after that. Not sure, though. I noticed them mostly while working in XP (guest OS) w/in VMWare under FC6 (host). Everything would just lock for half a minute or more. I wrote it off to "windows misbehavior". Then (I think) it happened while using Linux directly. I then noticed these "ata2" messages in /var/log/messages and googled around, discovering some notices that it might be related to some "libata code" and tighter error checking introduced into 2.6.19. So I switched to 2.6.20 over the weekend hoping it would go away. No go. I see from your message that it's in 2.6.21 as well. Dean
