From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "James Courtier-Dutton" <James@superbug.co.uk>
Cc: linux-kernel@vger.kernel.org, "Ingo Molnar" <mingo@redhat.com>
Subject: Re: 2.6.18-rt5 crashes with netconsole enabled. (bug#7288)
Date: Mon, 9 Oct 2006 00:40:52 +0200 [thread overview]
Message-ID: <9a8748490610081540t3d7dc7a3pce8cab496cd57340@mail.gmail.com> (raw)
In-Reply-To: <4529734B.7070707@superbug.co.uk>
On 08/10/06, James Courtier-Dutton <James@superbug.co.uk> wrote:
> Hi,
>
> Does anyone have any clues where I can find help regarding the rt kernels?
>
You could start by adding Ingo Molnar to Cc: (added) since he's the
creator of the -rt kernels.
> Please see kernel bug entry:
> http://bugzilla.kernel.org/show_bug.cgi?id=7288
> Description: 2.6.18-rt5 crashes with netconsole enabled. (bug#7288)
>
> Full console trace attached to bug report.
> Extract of console trace of crash/hang:
>
> modprobe/8459[CPU#1]: BUG in write_msg at drivers/net/netconsole.c:85
> 5/0x67
> [<c012274d>] _call_console_drivers+0x4e/0x52
> [<c0122d92>] release_console_sem+0x12a/0x1dc
> [<c0122ac7>] vprintk+0x299/0x2e1
> [<c0122b24>] printk+0x15/0x17
> [<f8991090>] init_netconsole+0x75/0x80 [netconsole]
> [<c013dbec>] sys_init_module+0x1597/0x175d
> [<c0102f99>] sysenter_past_esp+0x56/0x79
> modprobe/8459[CPU#1]: BUG in write_msg at drivers/net/netconsole.c:87
> [<c0103f92>] show_trace+0x16/0x19
> [<c0104583>] dump_stack+0x1a/0x1f
> [<c01234aa>] __WARN_ON+0x41/0x57
> [<f899112c>] write_msg+0x91/0xc9 [netconsole]
> [<c01226ed>] __call_console_drivers+0x55/0x67
> [<c012274d>] _call_console_drivers+0x4e/0x52
> [<c0122d92>] release_console_sem+0x12a/0x1dc
> [<c0122ac7>] vprintk+0x299/0x2e1
> [<c0122b24>] printk+0x15/0x17
> [<f8991090>] init_netconsole+0x75/0x80 [netconsole]
> [<c013dbec>] sys_init_module+0x1597/0x175d
> [<c0102f99>] sysenter_past_esp+0x56/0x79
> modprobe/8459[CPU#1]: BUG in write_msg at drivers/net/netconsole.c:85
> [<c0103f92>] show_trace+0x16/0x19
> [<c0104583>] dump_stack+0x1a/0x1f
> [<c01234aa>] __WARN_ON+0x41/0x57
> [<f8991102>] write_msg+0x67/0xc9 [netconsole]
> [<c01226ed>] __call_console_drivers+0x55/0x67
> [<c012274d>] _call_console_drivers+0x4e/0x52
> le+0x1597/0x175d
> [<c0102f99>] sysenter_past_esp+0x56/0x79
> modprobe/8459[CPU#1]: BUG in write_msg at drivers/net/netconsole.c:87
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
prev parent reply other threads:[~2006-10-08 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 21:53 James Courtier-Dutton
2006-10-08 22:40 ` Jesper Juhl [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=9a8748490610081540t3d7dc7a3pce8cab496cd57340@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=James@superbug.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
/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
all inboxes | Powered by JetHome®