public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: BUG: soft lockup during suspend
Date: Tue, 20 Mar 2007 12:32:50 -0400	[thread overview]
Message-ID: <46000CB2.9090700@redhat.com> (raw)
In-Reply-To: <s5hzm67c2d9.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Tue, 20 Mar 2007 17:08:48 +0100,
> I wrote:
>> At Tue, 20 Mar 2007 12:05:07 -0400,
>> Chuck Ebbert wrote:
>>> Takashi Iwai wrote:
>>>> X60/T60 is known to be often broken regarding the communication
>>>> between the controller and the codec chip.  When this kind of thing
>>>> happens, the driver tries to switch to a single-shot I/O without using
>>>> ring-buffers and IRQs, and even in such a mode, the communication gets
>>>> broken.  FWIW, it doesn't happen on other machines with HD-audio, so
>>>> it's fairly specific to X60/T60.  No idea why.
>>> What about Acer Aspire 5102?
>>>
>>> http://lkml.org/lkml/2006/12/3/9
>> This is a different problem.
>> A known workaround is to provide probe_mask=1 module option.
> 
> BTW, does this happen on the latest linus git tree?  (rc4 may work,
> though)
> 
> If yes, could you try the patch below?
> 

I can't easily test 2.6.21-rc, but "probe_mask=1" works on 2.6.20.4, which spews
errors without that. Should I try your patch on 2.6.20?

  reply	other threads:[~2007-03-20 16:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-20 12:32 BUG: soft lockup during suspend Pavel Machek
2007-03-20 12:37 ` Takashi Iwai
2007-03-20 13:22   ` Pavel Machek
2007-03-20 13:39     ` Takashi Iwai
2007-03-20 16:05   ` Chuck Ebbert
2007-03-20 16:08     ` Takashi Iwai
2007-03-20 16:21       ` Takashi Iwai
2007-03-20 16:32         ` Chuck Ebbert [this message]
2007-03-20 21:00           ` Takashi Iwai
2007-03-23 19:22         ` Chuck Ebbert
2007-03-26  9:50           ` Takashi Iwai

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=46000CB2.9090700@redhat.com \
    --to=cebbert@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=pavel@ucw.cz \
    --cc=tiwai@suse.de \
    /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