From: "Bill Adair" <adair@gotadsl.co.uk>
To: "alsa-devel@lists.sourceforge.net" <alsa-devel@lists.sourceforge.net>
Subject: Re: Linux 2.6.10 OOPS
Date: Fri, 21 Jan 2005 10:25:00 -0000 [thread overview]
Message-ID: <opskx67ys8n0kn27@biotracedesign.com> (raw)
In-Reply-To: <s5hu0pla6u6.wl@alsa2.suse.de>
I'm suffering from a hard lockup as well but on an earlier kernel build
2.6.5 with SuSE patches. I've compiled down the kernel when spinlock
debugging
and debug code AND set nmi_watchdog but my SMP system still locks up. To
get
ALSA to run with this set up I had to remove a lot of lines checking for
current->fs->root which cause a system crash as the process I seem to be
running in _DOES NOT_ have fs set. I can't quite see the point of the lines
which occur before calls to request->module.
Bill
On Thu, 13 Jan 2005 12:47:45 +0100, Takashi Iwai <tiwai@suse.de> wrote:
> At Thu, 13 Jan 2005 11:57:43 +0100,
> Gregor Jasny wrote:
>>
>> Takashi Iwai wrote:
>> >>After removing an USB webcam with a built-in microphone
>> (snd-usb-audio)
>> >>the kernel oopsed and the PS/2 keyboard wasn't working anymore.
>> >
>> > Yeah this is a known problem. This seems to be introduced recently.
>> > IIRC, it didn't happen with the USB stack on 2.6.9.
>>
>> At least on Fedora Core 3 with 2.6.9-1.667 it is happening, too.
>> From a posting on the PWC mailing list:
>>
>> > I'm using FC3 with kernel version 2.6.9-1.667 and no other
>> > usb devices (in fact no other external devices) on a an
>> > ibm thinkpad t42 laptop.
>
> Hmm, was 2.6.8 OK?
>
>
> Takashi
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by: Beat the post-holiday blues
> Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
> It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/alsa-devel
--
Ty Rhos Barn
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
prev parent reply other threads:[~2005-01-21 10:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 9:08 Linux 2.6.10 OOPS Gregor Jasny
2005-01-13 10:49 ` Takashi Iwai
2005-01-13 10:49 ` [Alsa-devel] " Takashi Iwai
2005-01-13 10:57 ` Gregor Jasny
2005-01-13 10:57 ` [Alsa-devel] " Gregor Jasny
2005-01-13 11:47 ` Takashi Iwai
2005-01-13 11:47 ` [Alsa-devel] " Takashi Iwai
2005-01-21 10:25 ` Bill Adair [this message]
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=opskx67ys8n0kn27@biotracedesign.com \
--to=adair@gotadsl.co.uk \
--cc=alsa-devel@lists.sourceforge.net \
/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.