Bug#600959: boot warnings too fast to read and not saved in any file nor dmesg

2010-10-21 Thread jidanni
> "BH" == Ben Hutchings  writes:

BH> This looks the same as #561764, reported by... you.

I see. Anyways here's a little discovery I made. If it is not
technologically possible to put such messages in files like dmesg, then
at least they could be left on the screen:

On one of my computers, the desktop with the detached terminal, the
messages are still visible with ShiftPgUp. (In contrast to the laptops,
where the farthest as ShiftPgUp reaches is the swap message. I.e., the
first few items from /sbin/init to before /etc/rcS.d/S08checkroot.sh are
not in any logs nor left on the console still.)

Using a pencil from the desktop, I see they were roughly:
INIT: version 2.88 starting
Using Makefile ... runlevels
Starting hotplug...
Synthesizing hotplug...
Waiting for /dev ... fully pop...
And then the swap message, which is the first to be left on the top of
other consoles too.



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87eibi7nuo@jidanni.org



Processed: Re: Bug#600959: boot warnings too fast to read and not saved in any file nor dmesg

2010-10-21 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> merge 600959 561764
Bug#561764: boot warnings fly off screen and are not logged to any file
Bug#600959: boot warnings too fast to read and not saved in any file nor dmesg
Merged 561764 600959.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
561764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561764
600959: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600959
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/handler.s.c.12876980597390.transcr...@bugs.debian.org



Bug#561764: Bug#600959: boot warnings too fast to read and not saved in any file nor dmesg

2010-10-21 Thread Holger Levsen
merge 600959 561764
thanks

On Donnerstag, 21. Oktober 2010, Ben Hutchings wrote:
> This looks the same as #561764, reported by... you.


signature.asc
Description: This is a digitally signed message part.


Bug#600959: boot warnings too fast to read and not saved in any file nor dmesg

2010-10-21 Thread Ben Hutchings
On Fri, 2010-10-22 at 04:18 +0800, jida...@jidanni.org wrote:
> X-debbugs-Cc: linux-ker...@vger.kernel.org
> Package: linux-2.6
> Version: 2.6.32-26
> 
> I'm quite distressed that again I am seeing warnings at boot that fly
> off the screen and cannot be found in any log files.

This looks the same as #561764, reported by... you.

Ben.

-- 
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.


signature.asc
Description: This is a digitally signed message part


Bug#600959: boot warnings too fast to read and not saved in any file nor dmesg

2010-10-21 Thread jidanni
X-debbugs-Cc: linux-ker...@vger.kernel.org
Package: linux-2.6
Version: 2.6.32-26

I'm quite distressed that again I am seeing warnings at boot that fly
off the screen and cannot be found in any log files.

I believe the message was similar to
udevd[263]: GOTO 'acl_end' has no matching label in: 
'/lib/udev/rules.d/70-acl.rules'

But that is not important. What is important is that it is not saved in
dmesg, or anywhere else.

How can an administrator deal with warnings that fly past too fast and
are not even in the record that one can ShiftPgUp to on the console, as
that gets truncated during some kind of screen reset upon boot.

You might think that the messages were saved in /var/log/boot, however
the top of that starts only at "Activating swap...done"

One might think that running "Debian GNU/Linux, with Linux 2.6.32-5-686
(recovery mode)" might show more, but same problem: boot messages
truncated... can't see them in any file. And with recovery mode, one
will not notice any problem, as there are too many messages to be able
to notice the error messages anyway.

See also http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=272428 .



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/87y69r1er9@jidanni.org