Re: Unable to do a clean reboot

2003-02-20 Thread David Kleiner
Thank you, Tony!

I certainly have SCHED_ULE in my kernel config - that explains it. 

Grateful,

David

On Thu, Feb 20, 2003 at 09:34:47AM +0200, Tony Harverson wrote:
 Hey There..
 
 I would guess you're using SCHED_ULE in your Kernel config?  It seems to
 cause shutdown problems that haven't been addressed yet..
 
 Tony
 
 -Original Message-
 From: David Kleiner [mailto:[EMAIL PROTECTED]] 
 Sent: 20 February 2003 05:45
 To: [EMAIL PROTECTED]
 Subject: Unable to do a clean reboot
 
 
 Hi,
 
 Since I went to -current by way of 5.0-Rel, I was unable to
 do a clean shutdown or reboot.  No matter how I tried it, 
 2-8 buffers always remain there during sync'ing.  
 
 It goes like this:
 
 Waiting (max 60 seconds) for system process `vnlru' to stop...stopped
 Waiting (max 60 seconds) for system process `bufdaemon' to
 stop...stopped Waiting (max 60 seconds) for system process `syncer' to
 stop...stopped
 
 syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
 2 2 giving up on 2 buffers
 
 
 wallaby# uname -a
 FreeBSD wallaby.pacbell.net 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Tue Feb
 18 21:06:18 PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/W
 i386
 
 It's a PCGR505-TE Sony Vaio laptop with this disk:
 
 ad0: 38154MB FUJITSU MHS2040AT [77520/16/63] at ata0-master UDMA100
 
 Any suggestions?
 
 Thank you,
 
 David
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message
 
 To Unsubscribe: send mail to [EMAIL PROTECTED]
 with unsubscribe freebsd-current in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



Unable to do a clean reboot

2003-02-19 Thread David Kleiner
Hi,

Since I went to -current by way of 5.0-Rel, I was unable to
do a clean shutdown or reboot.  No matter how I tried it, 
2-8 buffers always remain there during sync'ing.  

It goes like this:

Waiting (max 60 seconds) for system process `vnlru' to stop...stopped
Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped
Waiting (max 60 seconds) for system process `syncer' to stop...stopped

syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
giving up on 2 buffers


wallaby# uname -a
FreeBSD wallaby.pacbell.net 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Tue Feb 18 21:06:18 
PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/W  i386

It's a PCGR505-TE Sony Vaio laptop with this disk:

ad0: 38154MB FUJITSU MHS2040AT [77520/16/63] at ata0-master UDMA100

Any suggestions?

Thank you,

David

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message



RE: Unable to do a clean reboot

2003-02-19 Thread Tony Harverson
Hey There..

I would guess you're using SCHED_ULE in your Kernel config?  It seems to
cause shutdown problems that haven't been addressed yet..

Tony

-Original Message-
From: David Kleiner [mailto:[EMAIL PROTECTED]] 
Sent: 20 February 2003 05:45
To: [EMAIL PROTECTED]
Subject: Unable to do a clean reboot


Hi,

Since I went to -current by way of 5.0-Rel, I was unable to
do a clean shutdown or reboot.  No matter how I tried it, 
2-8 buffers always remain there during sync'ing.  

It goes like this:

Waiting (max 60 seconds) for system process `vnlru' to stop...stopped
Waiting (max 60 seconds) for system process `bufdaemon' to
stop...stopped Waiting (max 60 seconds) for system process `syncer' to
stop...stopped

syncing disks, buffers remaining... 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2 2
2 2 giving up on 2 buffers


wallaby# uname -a
FreeBSD wallaby.pacbell.net 5.0-CURRENT FreeBSD 5.0-CURRENT #10: Tue Feb
18 21:06:18 PST 2003 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/W
i386

It's a PCGR505-TE Sony Vaio laptop with this disk:

ad0: 38154MB FUJITSU MHS2040AT [77520/16/63] at ata0-master UDMA100

Any suggestions?

Thank you,

David

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message

To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message