From: Christian Kujau <evil@g-house.de> To: linux-kernel@vger.kernel.org Cc: 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 00:45:46 +0100 [thread overview] Message-ID: <418EB3AA.8050203@g-house.de> (raw) In-Reply-To: <20041107182155.M43317@g-house.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Kujau schrieb: > On Sun, 7 Nov 2004 08:57:40 -0800 (PST), Linus Torvalds wrote > >> bk undo -a1.2000.7.2 >> >>which should give you a tree without any of "my" stuff, ie it >>was what Jaroslav was working on before he merged it into the >>standard tree. i did so from a current tree (bk pull, undo, -r get) and it's working fine (url wraps): http://www.nerdbynature.de/bits/prinz/2.6.10-rc1/dmesg-no-oops-2.6.9_a1.2000.7.2.txt so i can see with "bk changes" that the ChangeSet is still there. this is what i expected, because -a says: - -a<rev> Remove all changesets which occurred after <rev>. what i did not expect is that this ChangeSet is now *not* the culprit, because there is no oops. am i right? [1] >>Yes, that makes me suspicious, and is one reason why I wonder >>if it's just your tree not being built right. > > i'll build a -bk snapshot from a tar.bz2 later on and see what it gives. i've build from linux-2.6.10-rc1.tar.bz2 with patch-2.6.10-rc1-bk17.bz2 from kernel.org with the same .config and "modprobe snd-ens1371" oopses as expected :( > Hmm.. That may well have worked fine, but it sounds in that post like > you tried to undo the ALSA stuff, and what I suggested was really to > do the reverse: take _only_ the ALSA changes, and then if it still yes, i wanted to undo the alsa changes because i suspected the alsa framework (sorry guys) and wanted to see if it still oopses when the latest alsa patch was not appied. 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... > fails, at least you have now pinpointed it a bit more (admittedly to > the _likely_ source, but that's as it should be: you narrow down the > "known bad" source base until you've narrowed it down to the smallest > change you can find that causes the problem). yes, like Documentation/BUG-HUNTING says. but i seem to have difficulties in using my tools (bk). sorry for that. > Sounds like you're doing everything right, but hey, it can't hurt to > double-check. yes, i really hope that it's not just a user error (on my side). building kernels since 2.0...but you never know... thanks again for help, Christian (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...) - -- BOFH excuse #224: Jan 9 16:41:27 huber su: 'su root' succeeded for .... on /dev/pts/1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBjrOp+A7rjkF8z0wRAl59AKCEbRRzsGujcOlLUA74taFZJb8H0ACfUUxQ nVQHjBXRBBn9BgSs7cLhTlY= =wb90 -----END PGP SIGNATURE-----
WARNING: multiple messages have this Message-ID (diff)
From: Christian Kujau <evil@g-house.de> To: linux-kernel@vger.kernel.org Cc: Linus Torvalds <torvalds@osdl.org>, alsa-devel@lists.sourceforge.net, linux-sound@vger.kernel.org Subject: Re: Oops in 2.6.10-rc1 Date: Sun, 07 Nov 2004 23:45:46 +0000 [thread overview] Message-ID: <418EB3AA.8050203@g-house.de> (raw) In-Reply-To: <20041107182155.M43317@g-house.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Christian Kujau schrieb: > On Sun, 7 Nov 2004 08:57:40 -0800 (PST), Linus Torvalds wrote > >> bk undo -a1.2000.7.2 >> >>which should give you a tree without any of "my" stuff, ie it >>was what Jaroslav was working on before he merged it into the >>standard tree. i did so from a current tree (bk pull, undo, -r get) and it's working fine (url wraps): http://www.nerdbynature.de/bits/prinz/2.6.10-rc1/dmesg-no-oops-2.6.9_a1.2000.7.2.txt so i can see with "bk changes" that the ChangeSet is still there. this is what i expected, because -a says: - -a<rev> Remove all changesets which occurred after <rev>. what i did not expect is that this ChangeSet is now *not* the culprit, because there is no oops. am i right? [1] >>Yes, that makes me suspicious, and is one reason why I wonder >>if it's just your tree not being built right. > > i'll build a -bk snapshot from a tar.bz2 later on and see what it gives. i've build from linux-2.6.10-rc1.tar.bz2 with patch-2.6.10-rc1-bk17.bz2 from kernel.org with the same .config and "modprobe snd-ens1371" oopses as expected :( > Hmm.. That may well have worked fine, but it sounds in that post like > you tried to undo the ALSA stuff, and what I suggested was really to > do the reverse: take _only_ the ALSA changes, and then if it still yes, i wanted to undo the alsa changes because i suspected the alsa framework (sorry guys) and wanted to see if it still oopses when the latest alsa patch was not appied. 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... > fails, at least you have now pinpointed it a bit more (admittedly to > the _likely_ source, but that's as it should be: you narrow down the > "known bad" source base until you've narrowed it down to the smallest > change you can find that causes the problem). yes, like Documentation/BUG-HUNTING says. but i seem to have difficulties in using my tools (bk). sorry for that. > Sounds like you're doing everything right, but hey, it can't hurt to > double-check. yes, i really hope that it's not just a user error (on my side). building kernels since 2.0...but you never know... thanks again for help, Christian (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...) - -- BOFH excuse #224: Jan 9 16:41:27 huber su: 'su root' succeeded for .... on /dev/pts/1 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFBjrOp+A7rjkF8z0wRAl59AKCEbRRzsGujcOlLUA74taFZJb8H0ACfUUxQ nVQHjBXRBBn9BgSs7cLhTlY=wb90 -----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-11-07 23:46 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 [this message] 2004-11-07 23:45 ` Christian Kujau 2004-11-08 1:16 ` Linus Torvalds 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=418EB3AA.8050203@g-house.de \ --to=evil@g-house.de \ --cc=alsa-devel@lists.sourceforge.net \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-sound@vger.kernel.org \ --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: 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.