Re: Oops in 2.6.10-rc1

From: Christian Kujau
Date: Sun Nov 07 2004 - 08:13:31 EST


On Sat, 6 Nov 2004 23:02:28 -0800 (PST), Linus Torvalds wrote
>
> Since you seem to be a BK user, try doing a

s/BK user/BK beginner/

>
> bk revtool sound/pci/ens1370.c
>
> and see if you can find the change that caused your problem.

hm, i already found the ChangeSet (ChangeSet@xxxxxxxxxx), but it seems
the ChangeSets get renumbered when linux makes progress. the issuer of
this changeset did not comment yet.

> 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.

yes.

>
> Also, if you enable frame pointers (under kernel debugging),
> the traceback will look a bit better. As it is, your oops

ah, ok, will do.

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

Police are examining all internet packets in the search for a
narco-net-trafficker
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/