[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <1300458565.4299.301.camel@localhost>
Date: Fri, 18 Mar 2011 15:29:25 +0100
From: Michael Karcher <kernel@...rcher.dialup.fu-berlin.de>
To: Arnd Bergmann <arnd@...db.de>
Cc: Udo van den Heuvel <udovdh@...all.nl>,
Karsten Keil <isdn@...ux-pingi.de>, Greg KH <gregkh@...e.de>,
linux-kernel@...r.kernel.org, Alan Cox <alan@...ux.intel.com>,
Tilman Schmidt <tilman@...p.cc>, stable@...nel.org
Subject: Re: known vboxgetty/isdn issue in 2.6.35.3?
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists