Re: Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow

[Martin Knoblauch]

----- Original Message ----

> From: jim owens <jowens@xxxxxx>
> To: Martin Knoblauch <knobi@xxxxxxxxxxxx>
> Cc: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>; Kay Sievers <kay.sievers@xxxxxxxx>; Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>; efault@xxxxxx; viro@xxxxxxxxxxxxxxxxxx; rjw@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; shemminger@xxxxxxxxxx; matthew@xxxxxx; mike.miller@xxxxxx
> Sent: Saturday, June 20, 2009 6:37:34 PM
> Subject: Re: Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow
> 
> Martin Knoblauch wrote:
> > ----- Original Message ----
> > 
> >> From: Jesse Barnes 
> >> To: Martin Knoblauch 
> >> Cc: Kay Sievers ; Andrew Morton 
> ; efault@xxxxxx; viro@xxxxxxxxxxxxxxxxxx; 
> rjw@xxxxxxx; linux-kernel@xxxxxxxxxxxxxxx; shemminger@xxxxxxxxxx; 
> matthew@xxxxxx; mike.miller@xxxxxx
> >> Sent: Tuesday, June 16, 2009 9:25:47 PM
> >> Subject: Re: Analyzed/Solved/Bisected: Booting 2.6.30-rc2-git7 very slow
> >> 
> >> On Thu, 28 May 2009 02:14:46 -0700 (PDT)
> >> Martin Knoblauch wrote:
> >>>> I expect the duplicate comes from a left-over mount in initramfs
> >>>> which isn't a duplicate in the sense of a bug in vfs or mount or
> >>>> anything. I guess, it is just still mounted in the initial kernel
> >>>> rootfs, below the root from the disk. It could be that a umount
> >>>> from initramfs did go wrong because of a changed timing.
> >>>> 
> >>>  This is what I suspect as well. I know for sure that the first
> >>> sysfs-line in /proc/mounts
> >>> 
> >>> | none /sys sysfs rw 0 0
> >>> 
> >>> is already there (2.6.29-rc1 and up) when entering startup-skripts.
> >>> It is supposed to be unmounted before, but something seems to prevent
> >>> it. I have idea how to capture debug output from the initrd/init
> >>> script :-(
> >> What's the latest here Martin?  It sounded like this was a userspace
> >> issue, with something reading the VPD over and over?  Or was it just a
> >> longer timeout that caused a specific driver to slow everything down?
> >> 
> > 
> >  Not sure about the VPD thing. Anyway, no real news. Still happens in 2.6.30. 
> But it only happens on a certain HW platform (HP/DL380G4). The folks at HP try 
> to reproduce in their environment.
> > 
> > Cheers
> > Martin
> 
> I reproduced this and verified Martin's analysis.  Conclusions:
>

 Cool, so I am not seeing gremlins :-)

Cheers
Martin 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/