From: Stian Jordet <liste@jordet.nu>
To: Florin Iucha <florin@iucha.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Re: ALSA problems: sound lockup, modules, 2.5.70
Date: 28 May 2003 16:37:26 +0200 [thread overview]
Message-ID: <1054132646.704.0.camel@chevrolet.hybel> (raw)
In-Reply-To: <20030528133940.GT3359@iucha.net>
ons, 28.05.2003 kl. 15.39 skrev Florin Iucha:
> On Wed, May 28, 2003 at 03:23:32PM +0200, Stian Jordet wrote:
> > > > This did not fix my problem. When I unload one ALSA-modules after the
> > > > other, the system hangs when I come to the "snd" module. No oops or
> > > > panic, it just freezes. Other than that, ALSA works fine for me, just
> > > > frustrating when I reboot.
> > > >
> > > > Best regards,
> > > > Stian
> > >
> > > For what it's worth, maybe as a point to start to look for differences...
> > >
> > > I am running 2.5.70-mm1, with snd-intel8x0 module. Also SMP on Xeon P4
> > > (2up), Intel chipset. I am not having any problems with unloading snd.
> > >
> > > So maybe the difference is between -mm1 and (IIRC) -bk1.
> >
> > Hmm. I will try -mm1 later today, but my problems started with
> > 2.5.68-bk18 (IIRC). This is also a SMP-system, Dual P3 (But VIA
> > chipset): But it's a pity you don't see the problem. I was hoping
> > everyone had it :) Well, I'll try to insert some printk's and stuff, and
> > see what happens. And try -mm1
>
> Try -bk2: it contains Al Viro's second fix.
Thank you, this did indeed fix it. I'm usually good at catching changes
that is relevant for me, but this one slipped through. Thanks again :)
Best regards,
Stian
next prev parent reply other threads:[~2003-05-28 14:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-28 12:55 Downing, Thomas
2003-05-28 13:23 ` Stian Jordet
2003-05-28 13:39 ` Florin Iucha
2003-05-28 14:37 ` Stian Jordet [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-27 21:22 Ivan Gyurdiev
2003-05-27 18:19 Olivier NICOLAS
2003-05-27 18:51 ` [PATCH] " viro
2003-05-27 20:07 ` Stian Jordet
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=1054132646.704.0.camel@chevrolet.hybel \
--to=liste@jordet.nu \
--cc=florin@iucha.net \
--cc=linux-kernel@vger.kernel.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: 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
all inboxes | Powered by JetHome®