From: Jeff Garzik <jgarzik@pobox.com>
To: syphir@syphir.sytes.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel Oops introduced in kernel-2.6.7-bk4+
Date: Tue, 22 Jun 2004 22:58:54 -0400 [thread overview]
Message-ID: <40D8F1EE.4080106@pobox.com> (raw)
In-Reply-To: <!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAA9mKu6AlYok2efOpJ3sb3O+KAAAAQAAAAMg8EaGipjkWalR4FA3PwJwEAAAAA@syphir.sytes.net>
C.Y.M. wrote:
> After installing kernel-2.6.7-bk4 and bk5, my machine fails to start (with
> an Oops) right about when Samba attempts to load from the init.d script.
> Kernel-2.6.7-bk3 works perfectly, so it must be something that was changed
> right about on June 20th.
[...]
> P.S. I would have included the actual Oops message in this email but it was
> not in any of the logs. The error is occuring before the machine can get
> started.
This doesn't help us a while lot :(
See if you can copy the oops by hand, or use a serial console to copy it
onto another computer.
Jeff
next prev parent reply other threads:[~2004-06-23 2:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-23 2:30 Kernel Oops introduced in kernel-2.6.7-bk4+ C.Y.M.
2004-06-23 2:58 ` Jeff Garzik [this message]
2004-06-23 3:57 ` C.Y.M.
2004-06-23 15:59 ` C.Y.M.
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=40D8F1EE.4080106@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=syphir@syphir.sytes.net \
/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