[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#600959: marked as done (boot warnings too fast to read and not saved in any file nor dmesg)

Your message dated Wed, 10 Jul 2013 20:09:13 +0200
with message-id <20130710180913.GB6890@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #561764,
regarding boot warnings too fast to read and not saved in any file nor dmesg
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
561764: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561764
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
X-debbugs-Cc: linux-kernel@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 .

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: