Re: 4.0.1 -> 5.0

[christos%astron.com@localhost (Christos Zoulas)]

In article 
<ab7b49bc0905050939q17f6d2e6n5c029da03b0eabc4%mail.gmail.com@localhost>,
Neal Hogan  <nealhogan%gmail.com@localhost> wrote:
>On Mon, May 4, 2009 at 5:54 PM, Neal Hogan <nealhogan%gmail.com@localhost> 
>wrote:
>> 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.
>>>> >
>>>> > 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?
>>
>> console . . . network IP: fine (i.e., roses?)
>>
>
>Below is my dmesg with audio disable, which allowed my system to fully
>boot the 5.0 kernel.  Everything is still quite slow and I have yet to
>complete the 4.0.1 -> 5.0 upgrade. I have yet to upgrade base, comp,
>and etc.
>
>Do you think I should even bother, given that 5.0 seems to not be
>cooperating well with my machine at this point?  Would it help my
>situation or netBSD's situation to continue with the upgrade?

You have very little memory. I'd suggest that you trim down what you
don't use in the kernel and just configure the devices you want. Perhaps
you are constantly swapping?

christos