From: Linus Torvalds <torvalds@osdl.org>
To: Christian Kujau <evil@g-house.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
alsa-devel@lists.sourceforge.net, perex@suse.cz
Subject: Re: Oops in 2.6.10-rc1
Date: Sat, 6 Nov 2004 23:02:28 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0411062244150.2223@ppc970.osdl.org> (raw)
In-Reply-To: <418D7959.4020206@g-house.de>
On Sun, 7 Nov 2004, Christian Kujau wrote:
>
> 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.
Since you seem to be a BK user, try doing a
bk revtool sound/pci/ens1370.c
and see if you can find the change that caused your problem. Of course,
the real change might be somewhere else in the sound driver initialization
path, so it's not like just that one file might be the cause. Regardöess,
the more you can pinpoint when the problem started, the better.
Also, if you enable frame pointers (under kernel debugging), the traceback
will look a bit better. As it is, your oops looks looks like something has
jumped off into la-la-land by jumping through a bad pointer (the value is
still in %ecx), but it's definitely not clear _where_ that happened.
Your trace points to pci_enable_device_bars(), but that may well be just
stale stack contents.
Linus
next prev parent reply other threads:[~2004-11-07 7:02 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 [this message]
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
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.0411062244150.2223@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=alsa-devel@lists.sourceforge.net \
--cc=evil@g-house.de \
--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 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.