linux-kernel - Re: 2.6.29: EXT4: __ext4_get_inode

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Thu, 26 Mar 2009 00:43:38 +0200
From:	Niel Lambrechts <niel.lambrechts@...il.com>
To:	Pavel Machek <pavel@....cz>,
	"linux.kernel" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.29: EXT4: __ext4_get_inode_loc errors after s2disk

On 03/26/2009 12:30 AM, Pavel Machek wrote:
> On Tue 2009-03-24 22:25:57, Niel Lambrechts wrote:
>> 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.
> 
> what kind of disk/what kind of controller is that?

Hi Pavel,

It is a Lenovo W500 Thinkpad.

lspci shows:

00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI
Controller (rev 03)

and for the disk, hdparm shows:
/dev/sda:

 Model=HITACHI HTS722020K9SA00  FDE            , FwRev=DC4LC75A,
SerialNo=080726DP0470DTGMUNPC
 Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=4
 BuffType=DualPortCache, BuffSize=15203kB, MaxMultSect=16, MultSect=?16?
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=390721968
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio1 pio2 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
 AdvancedPM=yes: mode=0x80 (128) WriteCache=enabled
 Drive conforms to: unknown:  ATA/ATAPI-2,3,4,5,6,7

 * signifies the current active mode

Niel
--
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/