Re: 4.0.1 -> 5.0

[Neal Hogan <nealhogan%gmail.com@localhost>]

On Mon, May 4, 2009 at 4:51 PM, Steven Bellovin <smb%cs.columbia.edu@localhost> 
wrote:
> 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