From: Christian Kujau <evil@g-house.de>
To: Pekka Enberg <penberg@gmail.com>
Cc: Greg KH <greg@kroah.com>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>,
alsa-devel@lists.sourceforge.net, linux-sound@vger.kernel.org
Subject: Re: Oops in 2.6.10-rc1
Date: Mon, 08 Nov 2004 20:31:57 +0000 [thread overview]
Message-ID: <418FD7BD.2060403@g-house.de> (raw)
In-Reply-To: <84144f02041108111816dc0b3a@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Pekka Enberg schrieb:
> Hi,
>
> 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...
i could use the -bk snapshots too, but since i am using bk myself (i try),
i think we can narrow it down a bit more.
>
> No, -bk14 is just the kernel I am running right now (I haven't tried
> -bk15) and I haven't had the problem. I cannot reproduce the oops _at
> all_ which is why I suspect it's his hardware. I included my lspci and
> dmesg output because we have similar (but not exactly the same)
> setups.
i've put an lspci output here:
http://www.nerdbynature.de/bits/prinz/2.6.10-rc1/lspci-v.txt
http://www.nerdbynature.de/bits/prinz/2.6.10-rc1/lspci-vv.txt
i do not suspect hw problems *yet*, because kernel up to 2.6.9 (tracking
bk) do not show this behaviour.
> FWIW, I've asked Christian for an obdump of the kernel to see if I can
will show up in a couple of minutes here:
http://www.nerdbynature.de/bits/prinz/2.6.10-rc1/objdump-d_a1.2463.txt.bz2
this is from the vmlinux from a "bk undo -a1.2463" kernel, IOW it still
contains:
ChangeSet@1.2463, 2004-11-04 17:07:16-08:00, torvalds@ppc970.osdl.org
Merge bk://kernel.bkbits.net/gregkh/linux/driver-2.6
into ppc970.osdl.org:/home/torvalds/v2.6/linux
thank you for the hints,
Christian.
PS: should we i un'CC linux-sound and alsa-devel, now we are sure it's a
pci thing?
- --
BOFH excuse #228:
That function is not currently supported, but Bill Gates assures us it
will be featured in the next upgrade.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBj9e9+A7rjkF8z0wRAregAJ9TyK5Mt00CFmCcgA1pOKmzvIxv2QCg0OBi
/9eNZ41Kp2GAOg4J5l0QR8E=OkFI
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2004-11-08 20:31 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
2004-11-08 20:31 ` 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=418FD7BD.2060403@g-house.de \
--to=evil@g-house.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=penberg@gmail.com \
--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