From: Chris Frey <cdfrey@foursquare.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] kernel warning and hang in 3.4.47
Date: Mon, 10 Jun 2013 16:43:47 -0400 [thread overview]
Message-ID: <20130610204347.GA27111@foursquare.net> (raw)
In-Reply-To: <20130610193722.GA23009@foursquare.net>
And another error, this time a panic in the UML kernel again, using
the same versions:
EIP: 0073:[<0805f5c2>] CPU: 0 Not tainted ESP: 007b:0827227c EFLAGS: 00210206
Not tainted
EAX: 00000000 EBX: 0000000b ECX: 00000000 EDX: 0000000e
ESI: 000000a0 EDI: 0827232c EBP: 08272318 DS: 007b ES: 007b
08271dc8: [<0806fb90>] show_regs+0xc5/0xcd
08271df4: [<0805f5d3>] segv+0x59/0x242
08271e9c: [<0805f811>] segv_handler+0x55/0x60
08271ec4: [<0806b1ae>] sig_handler_common+0x6d/0x7f
Kernel panic - not syncing: Segfault with no mm
08271dc0: [<081f3adb>] dump_stack+0x1c/0x20
08271dd8: [<081f3b48>] panic+0x69/0x157
08271df0: [<0805f681>] segv+0x107/0x242
08271e9c: [<0805f811>] segv_handler+0x55/0x60
08271ec4: [<0806b1ae>] sig_handler_common+0x6d/0x7f
EIP: 0000:[<00000000>] CPU: 0 Not tainted EFLAGS: 00000000
Not tainted
EAX: 00000000 EBX: 00000000 ECX: 00000000 EDX: 00000000
ESI: 00000000 EDI: 00000000 EBP: 00000000 DS: 0000 ES: 0000
08271d34: [<0806fb90>] show_regs+0xc5/0xcd
08271d60: [<0805f920>] panic_exit+0x25/0x3b
08271d74: [<0808afed>] notifier_call_chain+0x25/0x4a
08271d9c: [<0808b029>] __atomic_notifier_call_chain+0x17/0x19
08271dac: [<0808b040>] atomic_notifier_call_chain+0x15/0x17
08271dc8: [<081f3b60>] panic+0x81/0x157
08271df0: [<0805f681>] segv+0x107/0x242
08271e9c: [<0805f811>] segv_handler+0x55/0x60
08271ec4: [<0806b1ae>] sig_handler_common+0x6d/0x7f
- Chris
On Mon, Jun 10, 2013 at 03:37:22PM -0400, Chris Frey wrote:
> Hi,
>
> I'm running a 3.4.47 UML kernel on a 3.4.47 system.
>
> Recently I got the following warning, just before the UML guest system
> became unresponsive:
>
> ------------[ cut here ]------------
> WARNING: at kernel/softirq.c:159 local_bh_enable+0x3b/0x8b()
> Modules linked in:
> 21274430: [<081f3adb>] dump_stack+0x1c/0x20
>
> This is little to go on, I'm guessing. What should I do to provide
> more data?
>
> Thanks,
> - Chris
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> User-mode-linux-devel mailing list
> User-mode-linux-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
prev parent reply other threads:[~2013-06-10 20:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-10 19:37 [uml-devel] kernel warning and hang in 3.4.47 Chris Frey
2013-06-10 20:43 ` Chris Frey [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=20130610204347.GA27111@foursquare.net \
--to=cdfrey@foursquare.net \
--cc=user-mode-linux-devel@lists.sourceforge.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