From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Andrej Hocevar" <and.hocevar@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: possible kernel bug
Date: Sat, 12 May 2007 20:40:28 +0200 [thread overview]
Message-ID: <6bffcb0e0705121140i2f96f94eq4f48fd734e72b6b6@mail.gmail.com> (raw)
In-Reply-To: <20070512181019.GA5868@stoa>
Hi Andrej,
On 12/05/07, Andrej Hocevar <and.hocevar@gmail.com> wrote:
> as i've lately been forced to see the following message, i decided to
> report this. i hope it's the right place to do it.
>
> kernel: ------------[ cut here ]------------
> kernel: Kernel BUG at [verbose debug info unavailable]
> [...]
>
> here is the latest bug message:
>
> ===================
>
> May 12 19:52:52 stoa kernel: ------------[ cut here ]------------
> May 12 19:52:55 stoa kernel: Kernel BUG at [verbose debug info
> unavailable]
> May 12 19:52:55 stoa kernel: invalid opcode: 0000 [#1]
> May 12 19:52:55 stoa kernel: PREEMPT
> May 12 19:52:55 stoa kernel: Modules linked in: psmouse nls_cp437 nfs
> lockd sunrpc loop ppdev lp af_packet sr_mod sbp2 scsi_mod snd_intel8x0
> snd_ac97_codec snd_ac97_bus snd_pcm_oss ieee80211 snd_mixer_oss
> ieee80211_crypt irda parport_pc parport snd_pcm snd_timer crc_ccitt
> pcspkr rtc snd_page_alloc eth1394 e100 mii ohci1394 ieee1394 ehci_hcd
> uhci_hcd usbcore unix
> May 12 19:52:55 stoa kernel: CPU: 0
> May 12 19:52:55 stoa kernel: EIP: 0060:[<c01544a9>] Tainted: GF
> VLI
You are using tainted kernel.
" 2: 'F' if any module was force loaded by "insmod -f", ' ' if all
modules were loaded normally."
Documentation/oops-tracing.txt
Please try to reproduce this bug on non-tainted kernel.
Regards,
Michal
--
Michal K. K. Piotrowski
Kernel Monkeys
(http://kernel.wikidot.com/start)
prev parent reply other threads:[~2007-05-12 18:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 18:10 Andrej Hocevar
2007-05-12 18:40 ` Michal Piotrowski [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=6bffcb0e0705121140i2f96f94eq4f48fd734e72b6b6@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=and.hocevar@gmail.com \
--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
all inboxes | Powered by JetHome®