On 03/25/2009 03:30 AM, Theodore Tso wrote:
> On Tue, Mar 24, 2009 at 10:25:57PM +0200, Niel Lambrechts wrote:
>> Hi,
>>
>> After upgrading to 2.6.29 I get the below errors after resuming from
>> hibernating with s2disk. I ran fsck and tried doing the same thing again
>> in 2.6.28.9-pae, but do not get any errors there.
> 
> The ext4 errors are interleaved with hardware errors, and the ext4
> errors are about I/O errors.
> 
> EXT4-fs error (device sda6): __ext4_get_inode_loc: unable to read inode block - inode=2346519
> EXT4-fs error (device sda6) in ext4_reserve_inode_write: IO failure
> 
> This looks more like a hibernation problem than an ext4 problem.
> Looks like the hard drive is being left in some inconsistent state
> after resuming from hibernation.
> 
>      	   	       		   	   - Ted

Thanks for the info Theodore, this is definitely looks like some type of
regression in 2.6.29, as the problem is not evident when I s2disk using
2.6.28.9, even after multiple suspend/resume cycles.

I found some 'ATA bus errors' and 'SError' messages in
/var/log/messages, so I've attached the messages from both 2.6.29 and
2.6.28 for comparison.

Regards,
Niel
---