From: Pekka Enberg <penberg@gmail.com>
To: Greg KH <greg@kroah.com>
Cc: Christian Kujau <evil@g-house.de>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
alsa-devel@lists.sourceforge.net, linux-sound@vger.kernel.org,
penberg@cs.helsinki.fi
Subject: Re: Oops in 2.6.10-rc1
Date: Mon, 08 Nov 2004 19:30:43 +0000 [thread overview]
Message-ID: <84144f0204110811307ef1be50@mail.gmail.com> (raw)
In-Reply-To: <84144f02041108111816dc0b3a@mail.gmail.com>
On Mon, 8 Nov 2004 11:00:40 -0800, Greg KH <greg@kroah.com> wrote:
> > But 2.6.10-rc1-bk15 does have the problem?
> >
> > Trying to figure out where the issue is...
On Mon, 8 Nov 2004 21:18:09 +0200, Pekka Enberg <penberg@gmail.com> wrote:
> No, -bk14 is just the kernel I am running right now (I haven't tried
> -bk15) and I haven't had the problem.
Sorry for not being clear, any kernel after 2.6.10-rc1 oopses
according to Christian which is why I haven't bothered to test
anything else except -bk14.
Pekka
next prev parent reply other threads:[~2004-11-08 19:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4180F026.9090302@g-house.de>
[not found] ` <Pine.LNX.4.58.0410281526260.31240@pnote.perex-int.cz>
[not found] ` <4180FDB3.8080305@g-house.de>
[not found] ` <418A47BB.5010305@g-house.de>
[not found] ` <418D7959.4020206@g-house.de>
[not found] ` <Pine.LNX.4.58.0411062244150.2223@ppc970.osdl.org>
[not found] ` <20041107130553.M49691@g-house.de>
[not found] ` <418E4705.5020001@g-house.de>
[not found] ` <Pine.LNX.4.58.0411070831200.2223@ppc970.osdl.org>
[not found] ` <20041107182155.M43317@g-house.de>
2004-11-07 23:45 ` Oops in 2.6.10-rc1 Christian Kujau
2004-11-08 1:16 ` Linus Torvalds
2004-11-08 13:01 ` Christian Kujau
2004-11-08 18:13 ` Linus Torvalds
2004-11-08 20:59 ` Christian Kujau
2004-11-08 18:44 ` Pekka Enberg
2004-11-08 19:00 ` Greg KH
2004-11-08 19:18 ` Pekka Enberg
2004-11-08 19:30 ` Pekka Enberg [this message]
2004-11-08 20:31 ` Christian Kujau
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=84144f0204110811307ef1be50@mail.gmail.com \
--to=penberg@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=evil@g-house.de \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--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