From: Michael Krufky <mkrufky@m1k.net>
To: Stephen Frost <sfrost@snowman.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.15-rc3
Date: Tue, 29 Nov 2005 12:04:21 -0500 [thread overview]
Message-ID: <438C8A15.60201@m1k.net> (raw)
In-Reply-To: <20051129164946.GP6026@ns.snowman.net>
Stephen Frost wrote:
>* Linus Torvalds (torvalds@osdl.org) wrote:
>
>
>>On Tue, 29 Nov 2005, Michael Krufky wrote:
>>
>>
>>>In other words, the OOPS is the last thing to show on the screen in text mode,
>>>before the console switches into X, using debian sarge's default bootup
>>>process.
>>>
>>>
>>Ok. Whatever it is, I'm happy it is doing that, since it caused us to see
>>the oops quickly. None of _my_ boxes do that, obviously (and I tested on
>>x86, x86-64 and ppc64 exactly to get reasonable coverage of what different
>>architectures might do - but none of the boxes are debian-based).
>>
>>
>I'm pretty curious about it too, none of my debian-based boxes have
>'gdb' anywhere in /etc/init.d. The only thing I see is that the shell
>script /usr/bin/mozilla-firefox calls gdb when passed '--debugger', or
>when the DEBUG environment variable is set... Perhaps he's doing that
>during his .xsession?
>
>
I don't think that the .xsession can be involved, here..... The oops
happens BEFORE user login, and firefox definately isn't loaded before
logging in. ;-)
Anyhow, I forgot to mention that I am using the debian/testing sarge apt
repository ... Once again, I have a purely default configuration, with
the exception of the kernel. When I get home, I'll grep through my
startup scripts... I'll let you guys know what I find.
Cheers,
Mike
next prev parent reply other threads:[~2005-11-29 17:04 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-29 4:11 Linux 2.6.15-rc3 Linus Torvalds
2005-11-29 7:20 ` Michael Krufky
2005-11-29 7:43 ` Nick Piggin
2005-11-29 8:25 ` Michael Krufky
2005-11-29 15:47 ` Linus Torvalds
2005-11-29 16:10 ` Linus Torvalds
2005-11-29 16:25 ` Michael Krufky
2005-11-29 16:38 ` Linus Torvalds
2005-11-29 16:49 ` Stephen Frost
2005-11-29 17:04 ` Michael Krufky [this message]
2005-11-30 0:18 ` David S. Miller
2005-11-29 17:25 ` Chris Shoemaker
2005-11-29 17:44 ` Stephen Frost
2005-11-29 18:37 ` Linux 2.6.15-rc3 - gcc-4.0.2 compile error Byron Stanoszek
2005-11-29 18:42 ` Arjan van de Ven
2005-11-30 5:53 ` Linux 2.6.15-rc3 Michael Krufky
2005-11-29 9:29 ` Linux 2.6.15-rc3 - VIDEO_BT848_DVB config Eyal Lebedinsky
2005-11-29 13:07 ` Michael Krufky
2005-11-29 21:36 ` Linux 2.6.15-rc3 Helge Hafting
2005-11-29 21:47 ` Linus Torvalds
2005-11-30 8:59 ` Helge Hafting
2005-12-01 8:16 ` Jeff Garzik
2005-12-01 9:32 ` Helge Hafting
2005-12-01 9:37 ` Jeff Garzik
2005-12-04 0:43 ` Linux 2.6.15-rc3 problem found - scsi order changed Helge Hafting
2005-12-04 1:14 ` Linus Torvalds
2005-12-04 9:34 ` Zwane Mwaikambo
2005-12-04 15:28 ` Adrian Bunk
2005-12-04 23:50 ` Helge Hafting
2005-11-29 21:47 ` Linux 2.6.15-rc3 Rafael J. Wysocki
2005-11-29 22:42 ` Rafael J. Wysocki
2005-11-29 22:53 ` Stephen Hemminger
2005-11-29 23:37 ` Greg KH
2005-11-30 0:17 ` Stephen Hemminger
2005-11-30 0:25 ` Andrew Morton
2005-11-30 0:42 ` Stephen Hemminger
2005-11-30 1:57 ` Linus Torvalds
2005-11-30 2:09 ` Paul Mackerras
2005-11-30 2:46 ` Stephen Hemminger
2005-11-30 3:16 ` Linus Torvalds
2005-11-30 4:14 ` Greg KH
2005-11-30 1:09 ` Stephen Hemminger
2005-11-30 6:11 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=438C8A15.60201@m1k.net \
--to=mkrufky@m1k.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sfrost@snowman.net \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox