From: Artem Savkov <artem.savkov@gmail.com>
To: Shaun Ruffell <sruffell@digium.com>
Cc: Dave Haywood <tla@oak.selfip.net>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-net@vger.kernel.org
Subject: Re: BUG: unable to handle kernel paging request at 00010016
Date: Sun, 19 Aug 2012 12:21:17 +0400 [thread overview]
Message-ID: <20120819082117.GA4634@thinkpad.lan> (raw)
In-Reply-To: <20120819042543.GA14461@digium.com>
On Sat, Aug 18, 2012 at 11:25:43PM -0500, Shaun Ruffell wrote:
> Adding linux-net to the CC list.
>
> On Fri, Aug 17, 2012 at 11:57:56PM +0100, Dave Haywood wrote:
> > [1.] One line summary of the problem:
> > BUG: unable to handle kernel paging request at 00010016
> >
> > System boots then crashes a 5-10 or so seconds after getting to the login prompt
> > Booting without the network cable attached prevents the crash (no evidence beyond 10 minutes after boot)
> >
> > Diagnostics:
> > Captured the boot and managed a login + dmesg before the crash
> > Some of the log looks corrupted. Probably my crappy usb dongle serial flow control but left it in anyway
>
> [snip]
>
> Just a note that I see this as well. It happens reliably for me after trying to
> login to the machine via ssh.
>
> Here is the back trace I collected on the serial port.
There is a patch posted on netdev that fixes this for me:
http://patchwork.ozlabs.org/patch/178525/
--
Kind regards,
Artem
next prev parent reply other threads:[~2012-08-19 8:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-17 22:57 BUG: unable to handle kernel paging request at 00010016 Dave Haywood
2012-08-19 4:25 ` Shaun Ruffell
2012-08-19 8:21 ` Artem Savkov [this message]
2012-08-19 17:19 ` Shaun Ruffell
2012-08-21 0:05 ` Dave Haywood
2012-08-21 13:46 ` Neal Cardwell
2012-08-22 12:53 ` Dave Haywood
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=20120819082117.GA4634@thinkpad.lan \
--to=artem.savkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=sruffell@digium.com \
--cc=tla@oak.selfip.net \
/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;
as well as URLs for NNTP newsgroup(s).