From: Julian Wollrath <jwollrath@web.de>
To: Takashi Iwai <tiwai@suse.de>
Cc: Dylan Reid <dgreid@chromium.org>, alsa-devel@alsa-project.org
Subject: Re: Hung task with trace after resume on kernel v3.7-rc6
Date: Mon, 19 Nov 2012 14:56:45 +0100 [thread overview]
Message-ID: <20121119145645.30c681e5@ilfaris> (raw)
In-Reply-To: <s5h8v9xaha1.wl%tiwai@suse.de>
> > > Could you try the patch below instead?
> > The patch did not apply against 3.7-rc6 but the patch below applied
> > and let the trace disappear.
>
> OK, then at least it can be added as a workaround.
>
> But the spurious response still appears, right?
Yes, the spurious response still appears.
> Hm, then something screwed up the communication...
>
> At which moment do you see such a message? In other words, how to
> trigger the bug?
I suspend my system to ram or to disk. Then I resume it, everthing
comes up again and then, aprrox 4s after the resume was initiated, the
spurious response messages hit the dmesg for approx. 0.07s as you can
see in my first message. Hopefully this answer the question.
With best regards,
Julian
next prev parent reply other threads:[~2012-11-19 13:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-18 15:18 Hung task with trace after resume on kernel v3.7-rc6 Julian Wollrath
2012-11-19 5:54 ` Dylan Reid
2012-11-19 9:38 ` Takashi Iwai
2012-11-19 10:56 ` Julian Wollrath
2012-11-19 11:11 ` Julian Wollrath
2012-11-19 11:22 ` Takashi Iwai
2012-11-19 12:15 ` Julian Wollrath
2012-11-19 12:50 ` Takashi Iwai
2012-11-19 13:56 ` Julian Wollrath [this message]
2012-11-19 14:18 ` Julian Wollrath
2012-11-19 14:38 ` Takashi Iwai
2012-11-19 15:00 ` Julian Wollrath
2012-11-19 16:09 ` Julian Wollrath
2012-11-19 16:17 ` Takashi Iwai
2012-11-19 17:51 ` Julian Wollrath
2012-11-19 18:08 ` Takashi Iwai
2012-11-19 19:06 ` Takashi Iwai
2012-11-19 19:25 ` Julian Wollrath
2012-11-19 20:28 ` Takashi Iwai
2012-11-19 19:14 ` Julian Wollrath
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=20121119145645.30c681e5@ilfaris \
--to=jwollrath@web.de \
--cc=alsa-devel@alsa-project.org \
--cc=dgreid@chromium.org \
--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 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.