From: Christian Kujau <lists@nerdbynature.de>
To: linuxppc-dev@ozlabs.org
Cc: Nathan Lynch <ntl@pobox.com>, linux-kernel@vger.kernel.org
Subject: Re: Weird oopses with 2.6.22-rc7 [SOLVED]
Date: Fri, 13 Jul 2007 22:23:20 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.0.99.0707132221320.18512@sheep.housecafe.de> (raw)
In-Reply-To: <alpine.DEB.0.99.0707130840470.18512@sheep.housecafe.de>
On Fri, 13 Jul 2007, Christian Kujau wrote:
> Ah, this seem to have fixed http://lkml.org/lkml/2007/7/8/21 and really
> looks promising, I'll try 2.6.22-git2 now.
for the record: running 2.6.22-git3 now and the Oopses went away ;)
thanks,
Christian.
--
BOFH excuse #352:
The cables are not the same length.
prev parent reply other threads:[~2007-07-13 20:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 22:37 Weird oopses with 2.6.22-rc7 Christian Kujau
2007-07-12 23:37 ` Nathan Lynch
2007-07-13 6:43 ` Christian Kujau
2007-07-13 20:23 ` Christian Kujau [this message]
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=alpine.DEB.0.99.0707132221320.18512@sheep.housecafe.de \
--to=lists@nerdbynature.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=ntl@pobox.com \
/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