From: Linus Torvalds <torvalds@osdl.org> To: Christian Kujau <evil@g-house.de> Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>, alsa-devel@lists.sourceforge.net, linux-sound@vger.kernel.org, Greg KH <greg@kroah.com> Subject: Re: Oops in 2.6.10-rc1 Date: Sun, 7 Nov 2004 17:16:43 -0800 (PST) [thread overview] Message-ID: <Pine.LNX.4.58.0411071653480.24286@ppc970.osdl.org> (raw) In-Reply-To: <418EB3AA.8050203@g-house.de> On Mon, 8 Nov 2004, Christian Kujau wrote: > > what i did not expect is that this ChangeSet is now *not* the culprit, > because there is no oops. am i right? [1] Yes. So now I'd like to know _where_ the culprit is, since it turned out to be not the ALSA code. > i did another thing: i enabled the (deprecated) OSS driver (es1371.ko) > tried to load this thing: > > http://www.nerdbynature.de/bits/prinz/2.6.10-rc1/dmesg-debug_oops-OSS.txt > > it oopses. > - you said it's not a b0rken pci thingy > - i have to assume now that it's not an ALSA issue (since oss oopses too) > - it is OSS? the driver? i've CC'ed linux-sound... Sounds like something else changed, and likely the ALSA _and_ the OSS driver both broke. Which is not all that unlikely, since I suspect they share a lot of history. > yes, like Documentation/BUG-HUNTING says. but i seem to have difficulties > in using my tools (bk). sorry for that. Not your fault. Think of this as a learning experience ;) Anyway, now that the _other_ driver also oopses, and with a very similar oops too, so it looks like they both depended on some undocumented (or changed) detail in the PCI layer. Next step would be to see if the thing that breaks is this merge: 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 which merges Greg's PCI/driver model changes. It's all the same steps you took with the ALSA merge, you're a professional by now ;) Greg, have you followed this thread? > (whose only wish these days is to get over this strange thing and not > wasting peoples precious time with a "sound driver". hey, at least the > box is booting...) Hey, sound is important. And especially if you somehow found something non-sound that just broke sound by mistake, all the more important to fix it. Linus
WARNING: multiple messages have this Message-ID (diff)
From: Linus Torvalds <torvalds@osdl.org> To: Christian Kujau <evil@g-house.de> Cc: Kernel Mailing List <linux-kernel@vger.kernel.org>, alsa-devel@lists.sourceforge.net, linux-sound@vger.kernel.org, Greg KH <greg@kroah.com> Subject: Re: Oops in 2.6.10-rc1 Date: Mon, 08 Nov 2004 01:16:43 +0000 [thread overview] Message-ID: <Pine.LNX.4.58.0411071653480.24286@ppc970.osdl.org> (raw) In-Reply-To: <418EB3AA.8050203@g-house.de> On Mon, 8 Nov 2004, Christian Kujau wrote: > > what i did not expect is that this ChangeSet is now *not* the culprit, > because there is no oops. am i right? [1] Yes. So now I'd like to know _where_ the culprit is, since it turned out to be not the ALSA code. > i did another thing: i enabled the (deprecated) OSS driver (es1371.ko) > tried to load this thing: > > http://www.nerdbynature.de/bits/prinz/2.6.10-rc1/dmesg-debug_oops-OSS.txt > > it oopses. > - you said it's not a b0rken pci thingy > - i have to assume now that it's not an ALSA issue (since oss oopses too) > - it is OSS? the driver? i've CC'ed linux-sound... Sounds like something else changed, and likely the ALSA _and_ the OSS driver both broke. Which is not all that unlikely, since I suspect they share a lot of history. > yes, like Documentation/BUG-HUNTING says. but i seem to have difficulties > in using my tools (bk). sorry for that. Not your fault. Think of this as a learning experience ;) Anyway, now that the _other_ driver also oopses, and with a very similar oops too, so it looks like they both depended on some undocumented (or changed) detail in the PCI layer. Next step would be to see if the thing that breaks is this merge: 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 which merges Greg's PCI/driver model changes. It's all the same steps you took with the ALSA merge, you're a professional by now ;) Greg, have you followed this thread? > (whose only wish these days is to get over this strange thing and not > wasting peoples precious time with a "sound driver". hey, at least the > box is booting...) Hey, sound is important. And especially if you somehow found something non-sound that just broke sound by mistake, all the more important to fix it. Linus
next prev parent reply other threads:[~2004-11-08 1:17 UTC|newest] Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-10-28 13:12 Oops in 2.6.10-rc1 Christian 2004-10-28 13:29 ` [Alsa-devel] " Jaroslav Kysela 2004-10-28 14:09 ` Christian 2004-11-04 15:16 ` Christian Kujau 2004-11-05 2:35 ` Christian Kujau 2004-11-05 11:40 ` holborn 2004-11-07 1:24 ` Christian Kujau 2004-11-07 7:02 ` Linus Torvalds 2004-11-07 13:10 ` Christian Kujau 2004-11-07 16:02 ` Christian Kujau 2004-11-07 16:57 ` Linus Torvalds 2004-11-07 18:31 ` Christian Kujau 2004-11-07 18:44 ` Linus Torvalds 2004-11-07 23:45 ` Christian Kujau 2004-11-07 23:45 ` Christian Kujau 2004-11-08 1:16 ` Linus Torvalds [this message] 2004-11-08 1:16 ` Linus Torvalds 2004-11-08 13:01 ` Christian Kujau 2004-11-08 13:01 ` Christian Kujau 2004-11-08 18:13 ` Linus Torvalds 2004-11-08 18:13 ` Linus Torvalds 2004-11-08 20:59 ` Christian Kujau 2004-11-08 20:59 ` Christian Kujau 2004-11-08 23:49 ` Christian Kujau 2004-11-09 1:05 ` Linus Torvalds 2004-11-09 1:41 ` Christian Kujau 2004-11-09 1:31 ` Christian Kujau 2004-11-09 7:40 ` Pekka Enberg 2004-11-09 12:33 ` Christian Kujau 2004-11-09 17:26 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau 2004-11-09 18:53 ` Linus Torvalds 2004-11-09 19:04 ` [PATCH] kobject: fix double kobject_put() in error path of kobject_add() Greg KH 2004-11-09 19:08 ` Greg KH 2004-11-09 20:19 ` Pekka Enberg 2004-11-09 21:21 ` Christian Kujau 2004-11-09 21:31 ` Christian Kujau 2004-11-09 19:09 ` Linus Torvalds 2004-11-09 22:06 ` Christian Kujau 2004-11-09 23:30 ` Oops in 2.6.10-rc1 (almost solved) Christian Kujau 2004-11-09 23:40 ` Matt Domsch 2004-11-10 0:21 ` Christian Kujau 2004-11-10 1:01 ` Linus Torvalds 2004-11-11 22:43 ` Matt Domsch 2004-11-11 22:53 ` Linus Torvalds 2004-11-11 22:55 ` Matt Domsch 2004-11-12 0:27 ` Christian Kujau 2004-11-12 0:49 ` Linus Torvalds 2004-11-12 1:27 ` Christian Kujau 2004-11-10 0:12 ` Oops in 2.6.10-rc1 Christian Kujau 2004-11-10 0:23 ` Linus Torvalds 2004-11-08 18:44 ` Pekka Enberg 2004-11-08 18:44 ` Pekka Enberg 2004-11-08 19:00 ` Greg KH 2004-11-08 19:00 ` Greg KH 2004-11-08 19:18 ` Pekka Enberg 2004-11-08 19:18 ` Pekka Enberg 2004-11-08 19:30 ` Pekka Enberg 2004-11-08 19:30 ` Pekka Enberg 2004-11-08 20:31 ` Christian Kujau 2004-11-08 20:31 ` Christian Kujau 2004-11-07 13:05 ` Pekka Enberg 2004-11-07 13:43 ` 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=Pine.LNX.4.58.0411071653480.24286@ppc970.osdl.org \ --to=torvalds@osdl.org \ --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 \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.