From: Greg KH <gregkh@suse.de>
To: baoyb <baoyb@avit.org.cn>
Cc: linux-kernel@vger.kernel.org, alan@linux.intel.com
Subject: Re: Kernel Oops at tty_buffer_request_room when using pppd program (2.6.37-rc4)
Date: Thu, 6 Jan 2011 14:09:17 -0800 [thread overview]
Message-ID: <20110106220917.GL30799@suse.de> (raw)
In-Reply-To: <BECB6E558F0C4305830CC2A5CF2EB439@baoyb>
On Thu, Dec 16, 2010 at 07:00:16PM +0800, baoyb wrote:
> Hi All:
> I have tested 2.6.37-rc5 and the bug still exist.
> I also tested 2.6.32.24, the oops frequency is much lower than
> 2.6.37. (Only happened 2 times in one week).
{sigh}
I really don't know what to say here. Do you have the full backtrace of
the oops with 2.6.37? Is the device disconnecting right before the oops
happens?
thanks,
greg k-h
next prev parent reply other threads:[~2011-01-06 22:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 13:55 Kernel Oops at tty_buffer_request_room when using pppd program (2.6.37-rc4) baoyb
2010-12-08 15:07 ` Greg KH
2010-12-16 11:00 ` baoyb
2011-01-06 22:09 ` Greg KH [this message]
2010-12-09 19:17 ` Maciej Rutecki
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=20110106220917.GL30799@suse.de \
--to=gregkh@suse.de \
--cc=alan@linux.intel.com \
--cc=baoyb@avit.org.cn \
--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