Re: 4.0.1 -> 5.0

[Steven Bellovin <smb%cs.columbia.edu@localhost>]

On Mon, 4 May 2009 16:33:41 -0500
Neal Hogan <nealhogan%gmail.com@localhost> wrote:

> On Mon, May 4, 2009 at 4:09 PM, Neal Hogan <nealhogan%gmail.com@localhost>
> wrote:
> > On Mon, May 4, 2009 at 1:15 PM, Christos Zoulas
> > <christos%zoulas.com@localhost> wrote:
> >> On May 4, 12:34pm, nealhogan%gmail.com@localhost (Neal Hogan) wrote:
> >> -- Subject: Re: 4.0.1 -> 5.0
> >>
> >> | On Sun, May 3, 2009 at 5:40 PM, Christos Zoulas
> >> <christos%zoulas.com@localhost> wrote= | :
> >> | > On May 3, =A04:44pm, nealhogan%gmail.com@localhost (Neal Hogan) wrote:
> >> | > -- Subject: Re: 4.0.1 -> 5.0
> >> | >
> >> | > | They match what is in the posted dmesg, accept for the ACPI
> >> lines | > | (15-16) and lines 35 & 46 of the posted dmesg are not
> >> in the "new" one | > | . I went line by line ;)
> >> | > |
> >> | > | As has been the case, =A0I get a network address and then
> >> the stuff | > | after that (building db's, starting syslogd, etc.)
> >> is when things drag | > | . . .
> >> | >
> >> | > I'd start disabling devices with
> >> | > boot -d
> >> | > disable foo
> >> |
> >> | Any plan of attack? Likely causes? Where to start and proceed?
> >> |
> >> | I sincerely would like to help, but don't want to spend my day
> >> | rebooting my machine . . . it's not my main computer.
> >> |
> >> | Thanks!
> >> |
> >> |
> >> | Also, you meant *boot -c*, right?
> >>
> >> Yes. There are two approaches:
> >> Â Â Â Â1. disable most of the devices you really don't need and
> >> see if that fixes the problem.
> >> Â Â Â Â2. disable the clock source related devices one by one.
> >
> > Well, I got it to boot by disabling audio. The boot still takes a
> > long time (longer than a normal 4.0.1 boot) and logging in as root
> > is heading into the unbearable . . . after waiting 10 minutes after
> > entering *root* as the login name,I have yet to get a password
> > prompt.
> 
> Ok . . . I exaggerated a bit it was only a five min wait for a
> password prompt (it felt like 10). After 300 seconds the login attempt
> timed out and I successfully logged in after that.
> 
That smells like a network delay.  Were you logging in at the console
or over the net?