Re: Strange boot messages under 6.0-STABLE

2005-11-15 Thread David Scheidt
On Mon, Nov 14, 2005 at 03:01:19PM -0500, Kris Kennaway wrote:
 On Mon, Nov 14, 2005 at 06:45:15PM +0100, Ales wrote:
  During boot process under 6.0-STABLE I spoted some strange messages.
  
  Nov 14 18:18:45 romcek savecore: reboot after panic: page fault
  Nov 14 18:18:45 romcek savecore: no dump, not enough free space on 
 
 Your system panicked at some point in the past, but it can't save the
 dump for the reason specified.

If you just want to prevent the message from printing at the next boot
time, run 'savecore -c'.  If you want to try and retrieve the dump,
you can specify an alternate location to save the dump on the savecore
command line.

David
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Strange boot messages under 6.0-STABLE

2005-11-14 Thread Ales

During boot process under 6.0-STABLE I spoted some strange messages.

...
...
Nov 14 18:18:45 romcek kernel: cd0 at ata1 bus 0 target 0 lun 0
Nov 14 18:18:45 romcek kernel: cd0: SONY DVD RW DW-Q28A KYS1 Removable 
CD-ROM SCSI-0 device

Nov 14 18:18:45 romcek kernel: cd0: 33.000MB/s transfers
Nov 14 18:18:45 romcek kernel: cd0: Attempt to query device size failed: 
NOT READY, Medium not present

Nov 14 18:18:45 romcek kernel: Trying to mount root from ufs:/dev/ad4s1a
Nov 14 18:18:45 romcek savecore: reboot after panic: page fault
Nov 14 18:18:45 romcek savecore: no dump, not enough free space on 
device (143858 available, need 523842)

Nov 14 18:18:45 romcek savecore: unsaved dumps found but not saved
Nov 14 18:22:01 romcek /usr/libexec/save-entropy[722]: 
/var/db/entropy/saved-entropy.8 is not a regular file, and therefore it 
will not be rotated. Entropy file harvesting is aborted.

.

That reboot after panic message is strange, because the box is running 
normally.

Can someone plese tell me why I'm geting those messages.

My system is 6.0-STABLE and I upgraded from 5.4.

FreeBSD 6.0-STABLE #4: Sun Nov 6 14:09:42 CET 2005

Aleš
Slovenia
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Strange boot messages under 6.0-STABLE

2005-11-14 Thread Kris Kennaway
On Mon, Nov 14, 2005 at 06:45:15PM +0100, Ales wrote:
 During boot process under 6.0-STABLE I spoted some strange messages.
 
 ...
 ...
 Nov 14 18:18:45 romcek kernel: cd0 at ata1 bus 0 target 0 lun 0
 Nov 14 18:18:45 romcek kernel: cd0: SONY DVD RW DW-Q28A KYS1 Removable 
 CD-ROM SCSI-0 device
 Nov 14 18:18:45 romcek kernel: cd0: 33.000MB/s transfers
 Nov 14 18:18:45 romcek kernel: cd0: Attempt to query device size failed: 
 NOT READY, Medium not present
 Nov 14 18:18:45 romcek kernel: Trying to mount root from ufs:/dev/ad4s1a
 Nov 14 18:18:45 romcek savecore: reboot after panic: page fault
 Nov 14 18:18:45 romcek savecore: no dump, not enough free space on 
 device (143858 available, need 523842)
 Nov 14 18:18:45 romcek savecore: unsaved dumps found but not saved
 Nov 14 18:22:01 romcek /usr/libexec/save-entropy[722]: 
 /var/db/entropy/saved-entropy.8 is not a regular file, and therefore it 
 will not be rotated. Entropy file harvesting is aborted.
 .
 
 That reboot after panic message is strange, because the box is running 
 normally.
 Can someone plese tell me why I'm geting those messages.

Your system panicked at some point in the past, but it can't save the
dump for the reason specified.

Also, the message about entropy is important and should be attended to.

Kris

pgpRuBvrkJ7js.pgp
Description: PGP signature


Re: Strange boot messages under 6.0-STABLE

2005-11-14 Thread Doug White
On Mon, 14 Nov 2005, Kris Kennaway wrote:

  That reboot after panic message is strange, because the box is running
  normally.
  Can someone plese tell me why I'm geting those messages.

 Your system panicked at some point in the past, but it can't save the
 dump for the reason specified.

Note that if you're never going to attempt to recover this crashdump you
can clear it by running 'savecore -c'.

-- 
Doug White|  FreeBSD: The Power to Serve
[EMAIL PROTECTED]  |  www.FreeBSD.org
___
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to [EMAIL PROTECTED]