[PC-BSD Testing] Testing Digest, Vol 41, Issue 14

Ian Robinson fitchkendall at gmail.com
Mon Jun 21 12:08:27 PDT 2010


Ian Robinson reported:

> I was doing an upgrade over top of PCBSD 8.0.  I was also running top
 > in an x-term terminal.  The installer was going through the process of
 > removing the 8.0 packages and had not reached the point where the
 > installation progress bar begins to display.  About ten minutes of
 > operation into the upgrade as measured by the clock counter in top
 > (i.e., measuring from boot-up), the system locked as shown by no
 > activity in the installer, or in top, and mouse cursor would not
 > move.  Then the computer spontaneously rebooted.
 >
 > Subsequent retries to "upgrade" all resulted in spontaneous reboots.
 > Attempts to start the system failed because key packages had been
 > removed by this point.  I had to start a fresh install.  No harm done
 > as all important data was backed up before beginning the upgrade.
 >
 > There is great merit to having the installer report its activities to
 > the user, and even when they fly by so fast you cannot always read
 > them, you do get a sense to what is going on.
 >
 > Ian Robinson
 > Salem, Ohio

Kris Moore said:

> Doh! Please don't re-install from scratch until you report something in :)

IR:  SORRY.  :(

 > This sounds like a kernel panic, and we'll need to see if we can find
 > what the error is exactly. For future reference, the way to do this is such:
 >
 > * Start install
 > * Switch to "console" with Ctrl-Alt-F1
 >
 > Monitor the console for any kernel messages. When the kernel panics, it
 > should give you 15 seconds to press a key to pause the auto-reboot. If
 > you can, take a pic of the panic message, or send the details over by
 > transcribing them. That'll let us figure out if its a driver bug, kernel
 > bug, etc.

15 SECONDS WAS ABOUT THE TIME BETWEEN FREEZE & REBOOT.
DO YOU WANT ME TO TRY AN UPGRADE OVER TOP OF THIS FRESH INSTALL?

Ian Robinson
Salem, Ohio

On 6/21/10, testing-request at lists.pcbsd.org
<testing-request at lists.pcbsd.org> wrote:
> Send Testing mailing list submissions to
> 	testing at lists.pcbsd.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.pcbsd.org/mailman/listinfo/testing
> or, via email, send a message with subject or body 'help' to
> 	testing-request at lists.pcbsd.org
>
> You can reach the person managing the list at
> 	testing-owner at lists.pcbsd.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Testing digest..."
>
>
> Today's Topics:
>
>    1. Re: PCBSD 8.1-RC1 spontaneous reboot during upgrade (Kris Moore)
>    2. nVidia Legacy Driver Issues (Ian Robinson)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 21 Jun 2010 14:14:00 -0400
> From: Kris Moore <kris at pcbsd.org>
> To: testing at lists.pcbsd.org
> Subject: Re: [PC-BSD Testing] PCBSD 8.1-RC1 spontaneous reboot during
> 	upgrade
> Message-ID: <4C1FABE8.6010503 at pcbsd.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 06/21/2010 14:10, Ian Robinson wrote:
>> This report is unrelated to any of my prior posts because this is on a
>> different computer.
>>
>> Testing PCBSD 8.1-RC1 on an HP Vectra VL420, P4 @ 1.6 GHz, 1.5 GHz
>> RAM, nVidia GeForce 5 Series w/ 256 Mb RAM.
>>
>> I was doing an upgrade over top of PCBSD 8.0.  I was also running top
>> in an x-term terminal.  The installer was going through the process of
>> removing the 8.0 packages and had not reached the point where the
>> installation progress bar begins to display.  About ten minutes of
>> operation into the upgrade as measured by the clock counter in top
>> (i.e., measuring from boot-up), the system locked as shown by no
>> activity in the installer, or in top, and mouse cursor would not
>> move.  Then the computer spontaneously rebooted.
>>
>> Subsequent retries to "upgrade" all resulted in spontaneous reboots.
>> Attempts to start the system failed because key packages had been
>> removed by this point.  I had to start a fresh install.  No harm done
>> as all important data was backed up before beginning the upgrade.
>>
>> There is great merit to having the installer report its activities to
>> the user, and even when they fly by so fast you cannot always read
>> them, you do get a sense to what is going on.
>>
>> Ian Robinson
>> Salem, Ohio
>
> Doh! Please don't re-install from scratch until you report something in :)
>
> This sounds like a kernel panic, and we'll need to see if we can find
> what the error is exactly. For future reference, the way to do this is such:
>
> * Start install
> * Switch to "console" with Ctrl-Alt-F1
>
> Monitor the console for any kernel messages. When the kernel panics, it
> should give you 15 seconds to press a key to pause the auto-reboot. If
> you can, take a pic of the panic message, or send the details over by
> transcribing them. That'll let us figure out if its a driver bug, kernel
> bug, etc.
>
> --
> Kris Moore
> PC-BSD Software
> iXsystems
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 21 Jun 2010 14:57:42 -0400
> From: Ian Robinson <fitchkendall at gmail.com>
> To: testing at lists.pcbsd.org
> Subject: [PC-BSD Testing] nVidia Legacy Driver Issues
> Message-ID:
> 	<AANLkTikpXPsM1OvncGhnjVaB3rcxnNuC3uU1rS_PtbX3 at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
>  On 06/21/2010 13:55, Ian Robinson wrote:
>  > Testing PCBSD 8.1-RC1 on HP Vectra PIII, 1.0 GHz, 512 Mb RAM,
>  > nVidia GeForce4 Ti4200 64Mb AGP 4x
>  >
>  > I think these are nVidia issues but I'm reporting them anyway just in
>  > case because I did not have these issues under PCBSD 8.0.
>  >
>  > The PCBSD video installer picked the correct nVidia driver and display
>  > settings appropriate for the monitor.  The video driver is nVidia
>  > 96.43.16.  Desktop effects have been set to off.
>  >
>  > There are frequently minor pixels on the desktop that trail after a
>  > desktop icon.  They are so small and occupy so little of the screen
>  > that they are insignificant.
>  >
>  > However, the screen will occasionally leave a colored or a black
>  > rectangle the size of the closed window on the screen until a few
>  > seconds pass or until you overlay the screen with another program.
>  > On one occasion I had the entire screen go black on black for approx.
>  > 45 seconds, then miraculously return to normal.
>  >
>  > Additionally, the display dims with a light blue overcast and then
>  > lightens.  If you were to jump over to console, the letters on the
>  > screen are a pale blue against a black background.  After a while, the
>  > colors will jump back to their normal state.  On the console, that
>  > would be a pale white/very light grey against a black background.
>  >
>  >
>  > Ian Robinson
>  > Salem, Ohio
>
>  That does sound like a driver bug :(
>
>  Can you confirm by switching to "nv" and making sure you don't see any
>  corruption? If so, you'll want to give nvidia a ping about this:
>
>  http://www.nvnews.net/vbulletin/forumdisplay.php?f=47
>
>  On their forum they have instructions for submitting bug reports, with
>  the details they need.
>   --
>  Kris Moore
>
> ==============================================
> Kris --
>
> I could not install the "nv" driver or the "nouveau" driver.
>
> I went with "vesa" and have had no problems of the type described above.
>
> I sure like the 8.1 series.  Perhaps its the improved KDE 4.4, but
> things are much faster.
>
> Ian Robinson
> Salem, Ohio
>
>
> ------------------------------
>
> _______________________________________________
> Testing mailing list
> Testing at lists.pcbsd.org
> http://lists.pcbsd.org/mailman/listinfo/testing
>
>
> End of Testing Digest, Vol 41, Issue 14
> ***************************************
>


More information about the Testing mailing list