public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christian Kujau <evil@g-house.de>
To: LKML <linux-kernel@vger.kernel.org>
Cc: alsa-devel@lists.sourceforge.net, perex@suse.cz
Subject: Oops in 2.6.10-rc1
Date: Sun, 07 Nov 2004 02:24:41 +0100	[thread overview]
Message-ID: <418D7959.4020206@g-house.de> (raw)
In-Reply-To: <418A47BB.5010305@g-house.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

hi again,

i *think* i found the ChangeSet leading to the bug i tried to report in
 http://marc.theaimsgroup.com/?l=linux-kernel&m=109888178603516&w=2

the error is sill present here (and only here? strange...), the latest -BK
does not fix it. i had some difficulties in telling BK to do the right
thing. to summarise the error:

- - upon loading of snd_ens1371 the Oops occurs. system is still stable
then, but no sound available.
- - this occured somewhere between 2.6.9 (released 15-Oct-2004) and 2.6.9-10
(released 22-Oct-2004)

one interesting changeset was:

ChangeSet@1.2000.7.1, 2004-10-20 20:33:06+02:00, perex@suse.cz
  Merge suse.cz:/home/perex/bk/linux-sound/linux-2.5
  into suse.cz:/home/perex/bk/linux-sound/linux-sound

i tried to back it out:

$ bk clone -r1.2000.7.1 linux-2.6-BK linux-2.6-BK-test

but the said ChangeSet was still there (of course). i tried to back it out
(now for sure):

$ bk undo -a1.2010
(hm: the changesets get renumbered everytime i "do" something with the
tree) this one reverted quite a few ChangeSets but i let it happen.

compiling & booting this thing goes fine and i am now running 2,6,9-BK(?)
with working snd_ens1371.

if someone could give me a hint here what to do next or perhaps tell me
that the whole things was totally pointless - please say so.
i am somehow lost as to which is the right person to bug here.

thank you for your time,
Christian.
- --
BOFH excuse #328:

Fiber optics caused gas main leak
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBjXlZ+A7rjkF8z0wRAqaVAJ9ljiIpxi01SblgEg/ce/Vd/uYksQCfeuJ9
hRGA0/17ttZ83xRQDb8jfhs=
=DQYp
-----END PGP SIGNATURE-----

  parent reply	other threads:[~2004-11-07  1:24 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4180F026.9090302@g-house.de>
2004-10-28 13:29 ` [Alsa-devel] Oops in 2.6.10-rc1 Jaroslav Kysela
2004-10-28 14:09   ` Christian
2004-11-04 15:16     ` Christian Kujau
2004-11-05  2:35       ` Christian Kujau
2004-11-07  1:24       ` Christian Kujau [this message]
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-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 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 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
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=418D7959.4020206@g-house.de \
    --to=evil@g-house.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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