[conspire] debugging

[Paul Zander]

Looks like we will have an interest CABAL this evening.

I am running a desktop with Debian Testing and did an upgrade about 2 weeks ago.  Recently I have encountered a couple of "glitches" during boot up.  I can bring the various log files to cabal to examine, but which files?

Glitch #1.   After grub, there is a message about "No Symbol Table".  I was going to manually record the exact words, but the warning timed out and proceeded.  I have successfully rebooted numerous times.

Glitch #2.   After running a week or more, I decided to re-boot.  The PC is dual-boot and there was something I couldn't do with Wine.  I made a point of closing all of the applications and windows before shutdown.  Later, during the re-boot of Debian, the boot screen froze with just three lines of text.  Lots of disk access, but several minutes on nothing on the screen.  I turned off power.  This morning I booted into Win 7 with no problem and took care of email.  Then I opened the laptop and prepared to type transcripts of the error messages from the desktop.  As mentioned above, the No symbol table warning cleared.  Then I started to copy from the screen:

/dev/sdc2: clean, 278521/6406144 files, 3916158/25600000 blocks
>A message about an unreliable temperature sensor.  This message is nothing new.  I have ignored it many many times in past.
>
>And one more line.
Before I could transcribe the 3rd line, the boot screen started scrolling lots of messages.  The boot appeared to finish normally.

I have put that computer into sleep mode.  Hopefully I will get an email advising what log files I should examine or bring copies to CABAL.

Paul