From: Michael Karcher <kernel@mkarcher.dialup.fu-berlin.de>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Udo van den Heuvel <udovdh@xs4all.nl>,
Karsten Keil <isdn@linux-pingi.de>, Greg KH <gregkh@suse.de>,
linux-kernel@vger.kernel.org, Alan Cox <alan@linux.intel.com>,
Tilman Schmidt <tilman@imap.cc>,
stable@kernel.org
Subject: Re: known vboxgetty/isdn issue in 2.6.35.3?
Date: Fri, 18 Mar 2011 15:29:25 +0100 [thread overview]
Message-ID: <1300458565.4299.301.camel@localhost> (raw)
In-Reply-To: <201103181524.33246.arnd@arndb.de>
Am Freitag, den 18.03.2011, 15:24 +0100 schrieb Arnd Bergmann:
> On Thursday 17 March 2011, Michael Karcher wrote:
> > The same issue happened on our system. Sometimes vboxgetty gets stuck in
> > state D on a debian stable system (2.6.32). I just applied your patch to
> > that kernel and hope the problem went away. Please remind me to report
> > back in one to two weeks if I didn't already report whether the hangs
> > are fixed. Is something except for a test on a productive system missing
> > to get this fix into 32-stable?
>
> Thanks for the report. You are talking about this patch, right?
>
> bc10f96757 "isdn: avoid calling tty_ldisc_flush() in atomic context"
Yes, exactly. Sorry for not mentioning it. I did not experience the BUG,
but the hung task, just as in the mail I replied to.
Regards,
Michael Karcher
prev parent reply other threads:[~2011-03-18 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-07 13:42 known vboxgetty/isdn issue in 2.6.35.3? Udo van den Heuvel
2010-09-07 19:45 ` Arnd Bergmann
2010-09-08 0:35 ` Greg KH
2010-11-06 14:04 ` Udo van den Heuvel
2010-11-09 10:15 ` Arnd Bergmann
2011-03-17 21:48 ` Michael Karcher
2011-03-18 14:24 ` Arnd Bergmann
2011-03-18 14:29 ` Michael Karcher [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=1300458565.4299.301.camel@localhost \
--to=kernel@mkarcher.dialup.fu-berlin.de \
--cc=alan@linux.intel.com \
--cc=arnd@arndb.de \
--cc=gregkh@suse.de \
--cc=isdn@linux-pingi.de \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@kernel.org \
--cc=tilman@imap.cc \
--cc=udovdh@xs4all.nl \
/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.