linux-kernel - Re: Storage related regression in linux-next 20120824

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 for Android: free password hash cracker in your pocket

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

Message-ID: <503BA2C9.8040203@gmx.de>
Date:	Mon, 27 Aug 2012 18:39:37 +0200
From:	Dieter Ries <clip3@....de>
To:	Jeff Garzik <jgarzik@...ox.com>
CC:	Arvydas Sidorenko <asido4@...il.com>, linux-kernel@...r.kernel.org,
	IDE/ATA development list <linux-ide@...r.kernel.org>,
	Dieter Ries <mail@...terries.net>
Subject: Re: Storage related regression in linux-next 20120824

Hi,

On 08/27/2012 04:40 PM, Jeff Garzik wrote:
> On Mon, Aug 27, 2012 at 4:59 AM, Arvydas Sidorenko <asido4@...il.com> wrote:
>> linux-next 20120824 introduced regression on Mac mini 2011 - /root partition
>> gets mounted as read-only and it stays so even when trying to reboot into
>> previously working kernel. In order to make it work on older kernel again
>> `fsck` needs to be executed:
>> ----------------------------------------------------------------------
>> Root partition uses ext4 filesystem on Intel 330 SSD connected to SATA3.
>> dmesg shows that journaling was disabled:
>> ----------------------------------------------------------------------
>> I haven't bisected to which exactly tree introduces the regression,
>> but I can tell
>> that linux-next 20120813 and v3.6-rc3 work fine.

I think I experienced this with v3.6-rc3 today as well. I thought my ssd
(ocz vertex3) was broken first, but then I saw this mail.

Never happened before on 3.5.something.

I am trying to reproduce it right now, it happened 2 times before I read
the mail, I didnt keep the dmesg. Now it's taking it's time to occurr
again...

Anyway, here comes lspci, and a dmesg (without the problem showing up
yet) is attached.

Cheers,

Dieter

00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core
Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series
Chipset Family MEI Controller #1 (rev 04)
00:16.3 Serial controller: Intel Corporation 6 Series/C200 Series
Chipset Family KT Controller (rev 04)
00:19.0 Ethernet controller: Intel Corporation 82579LM Gigabit Network
Connection (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 2 (rev b4)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 5 (rev b4)
00:1c.6 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 7 (rev b4)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation QM67 Express Chipset Family LPC
Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset
Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family
SMBus Controller (rev 04)
03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205
(rev 34)
0d:00.0 SD Host controller: Ricoh Co Ltd PCIe SDXC/MMC Host Controller
(rev ff)
0e:00.0 USB controller: NEC Corporation uPD720200 USB 3.0 Host
Controller (rev ff)



> 
> Can you pastebin 'dmesg' and 'lspci'?  Did this occur only once, or is
> it reproducible?
> 
>      Jeff
> --
> 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/
> 



View attachment "kernel36rc3failbefore" of type "text/plain" (25737 bytes)