From: Nick Orlov <bugfixer@list.ru>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.17-rc1-mm2: badness in 3w_xxxx driver
Date: Sun, 09 Apr 2006 17:23:23 -0400 [thread overview]
Message-ID: <20060409212323.GA4811@nickolas.homeunix.com> (raw)
In-Reply-To: <20060409124301.44a9567c.akpm@osdl.org>
On Sun, Apr 09, 2006 at 12:43:01PM -0700, Andrew Morton wrote:
> Nick Orlov <bugfixer@list.ru> wrote:
> >
> > Confirmed, this patch solves the "badness" problem for me.
>
> yup, thanks.
>
> > I still experiencing a weird hangs though (the box just hangs, no
> > messages on console/syslog, nothing). I'll try to nail it down.
> >
> > 2.6.16-mm2 works like a charm with the same config.
> > Do you know which patches should I try to revert first?
>
> Gee, 2.6.16-mm2 was a long time ago.
>
> Tried sysrq?
>
> echo 1 > /proc/sys/kernel/sysrq
> <wait for hang>
> ALT-SYSRQ-P or ALT-SYSRQ-T
>
> Is the NMi watchdog enabled? Boot with `nmi_watchdog=1', make sure that
> the NMI counts are incrementing in /proc/interrupts.
>
> Failing all that, testing 2.6.17-rc1 would be interesting.
2.6.17-rc1 fails in the same fashion - it hangs "randomly".
Good news that I've found the pattern and solution:
it always happens when 2 applications open /dev/dsp simultaneously.
Applying the following patches published by Takashi Iwai solves the
problem:
http://marc.theaimsgroup.com/?l=linux-kernel&m=114423578508165&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=114424198614019&w=2
Not sure if the first one is enough.
I would probably recommend to put them into the hot-fixes,
since many people can be frustrated because of this.
--
With best wishes,
Nick Orlov.
prev parent reply other threads:[~2006-04-09 21:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-09 18:23 2.6.17-rc1-mm2: badness in 3w_xxxx driver Nick Orlov
2006-04-09 18:32 ` Andrew Morton
2006-04-09 19:12 ` Jeff Garzik
2006-04-09 19:21 ` Arjan van de Ven
2006-04-09 19:12 ` Nick Orlov
2006-04-09 19:43 ` Andrew Morton
2006-04-09 21:23 ` Nick Orlov [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=20060409212323.GA4811@nickolas.homeunix.com \
--to=bugfixer@list.ru \
--cc=akpm@osdl.org \
--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