Re: Storage related regression in linux-next 20120824

2012-09-11 Thread Zheng Liu
On Sun, Sep 09, 2012 at 04:50:47PM -0400, Jeff Garzik wrote: > On 09/09/2012 04:36 PM, Hugh Dickins wrote: > >On Sun, Sep 9, 2012 at 1:28 PM, Jeff Garzik wrote: > >>I'll send Linus a patch to disable. > > > >Thanks, but no, the change in question hasn't reached Linus yet, it's > >just a linux-next

Re: Storage related regression in linux-next 20120824

2012-09-10 Thread Hugh Dickins
On Sun, 9 Sep 2012, Jeff Garzik wrote: > On 09/09/2012 04:11 PM, Arvydas Sidorenko wrote: > > > I think you know your way around SCSI/libata much better than I do. > > > > > > I just bisected linux-next, and it comes down to the commit below, which > > > introduces the regression for me, and I'm g

Re: Storage related regression in linux-next 20120824

2012-09-09 Thread Jeff Garzik
On 09/09/2012 04:36 PM, Hugh Dickins wrote: On Sun, Sep 9, 2012 at 1:28 PM, Jeff Garzik wrote: I'll send Linus a patch to disable. Thanks, but no, the change in question hasn't reached Linus yet, it's just a linux-next or mmotm thing - isn't it? Yep, libata-dev#upstream. Sorry, got my own

Re: Storage related regression in linux-next 20120824

2012-09-09 Thread Hugh Dickins
On Sun, Sep 9, 2012 at 1:28 PM, Jeff Garzik wrote: > I'll send Linus a patch to disable. Thanks, but no, the change in question hasn't reached Linus yet, it's just a linux-next or mmotm thing - isn't it? I'll reply again later, but just about to rush out, and thought it best to clear this up qui

Re: Storage related regression in linux-next 20120824

2012-09-09 Thread Jeff Garzik
On 09/09/2012 04:11 PM, Arvydas Sidorenko wrote: I think you know your way around SCSI/libata much better than I do. I just bisected linux-next, and it comes down to the commit below, which introduces the regression for me, and I'm guessing for you also. Maybe it can be fixed up to satisfy us,

Re: Storage related regression in linux-next 20120824

2012-09-09 Thread Arvydas Sidorenko
> I think you know your way around SCSI/libata much better than I do. > > I just bisected linux-next, and it comes down to the commit below, which > introduces the regression for me, and I'm guessing for you also. Maybe > it can be fixed up to satisfy us, but otherwise will have to be reverted: >

Re: Storage related regression in linux-next 20120824

2012-09-09 Thread Hugh Dickins
On Mon, 27 Aug 2012, Arvydas Sidorenko wrote: > On 08/27/2012 06:39 PM, Arvydas Sidorenko wrote: > > > Can you pastebin 'dmesg' and 'lspci'? Did this occur only once, or is > > > it reproducible? > > > > > > Jeff > > It does happen every time when booting into -next 20120824. I don't know

Storage regression in v3.6-rc3 was: Storage related regression in linux-next 20120824

2012-08-29 Thread Dieter Ries
Hi again, On 08/27/2012 06:39 PM, Dieter Ries wrote: > On 08/27/2012 04:40 PM, Jeff Garzik wrote: >> On Mon, Aug 27, 2012 at 4:59 AM, Arvydas Sidorenko wrote: >>> linux-next 20120824 introduced regression on Mac mini 2011 - /root partition >>> gets mounted as read-only and it stays so even when t

Re: Storage related regression in linux-next 20120824

2012-08-27 Thread Dieter Ries
Hi, On 08/27/2012 04:40 PM, Jeff Garzik wrote: > On Mon, Aug 27, 2012 at 4:59 AM, Arvydas Sidorenko 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

Re: Storage related regression in linux-next 20120824

2012-08-27 Thread Jeff Garzik
On Mon, Aug 27, 2012 at 4:59 AM, Arvydas Sidorenko 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`

Storage related regression in linux-next 20120824

2012-08-27 Thread Arvydas Sidorenko
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: -