Kirk McKusick wrote:
> Just rebuilt -current this morning. Background fsck is still
> causing a "soft lockup". I thought the conclusion was we were
> going to disable it for 5.0.
>
> What do you mean by background fsck causing a "soft lockup"?
> Is it failing? Is it deadlocking the system? Do you have a
> specific test case that shows the problem? Needless to say
> it is working fine on my system and on my regression tests.
> The only problem that I am having with 5.0 as of last night
> is getting login to work on my console.
What happens is that at first I can login, but the system seems
slow. I then got as far as running 'top' but it never refreshed its
display and subsequently all keystrokes were ignored. Changing
virtual terminals still works OK, but they are effectively dead too.
I'm imagining processes getting stuck on some lock one by one.
Top did get as far as showing the background fsck process, which
had a priority of -6 or something.
The previous time it didn't even spit out a login prompt, but
that may just be due to experimental noise.
For me, it appears easy to reproduce...
1. Boot -current system
2. Pull the power cable out
3. Put the power cable back in
4. Let the box boot; it notes backgroud fsck
5. Login and try to do something
I can give you more details about my system separately if you like.
Thanks,
-Archie
__________________________________________________________________________
Archie Cobbs * Packet Design * http://www.packetdesign.com
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
