From: Alex Romosan <romosan@sycorax.lbl.gov>
To: Jiri Slaby <jirislaby@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: linux 2.6.20-rc1: kernel BUG at fs/buffer.c:1235!
Date: Sun, 24 Dec 2006 08:29:49 -0800 [thread overview]
Message-ID: <871wmpgsua.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <458E84C6.7040100@gmail.com> (message from Jiri Slaby on Sun, 24 Dec 2006 14:46:23 +0059)
Jiri Slaby <jirislaby@gmail.com> writes:
> Alex Romosan wrote:
>> this is on a thinkpad t40, not sure if it means anything, but here it goes:
>>
>> kernel: kernel BUG at fs/buffer.c:1235!
>> kernel: invalid opcode: 0000 [#1]
>> kernel: PREEMPT
>> kernel: Modules linked in: radeon drm binfmt_misc nfs sd_mod scsi_mod nfsd exportfs lockd sunrpc autofs4 pcmcia firmware_class joydev irtty_sir sir_dev nsc_ircc irda crc_ccitt parport_pc parport ehci_hcd uhci_hcd usbcore aes_i586 airo nls_iso8859_1 ntfs yenta_socket rsrc_nonstatic pcmcia_core
>> kernel: CPU: 0
>> kernel: EIP: 0060:[<c016ad06>] Not tainted VLI
>> kernel: EFLAGS: 00010046 (2.6.20-rc1 #215)
>
> Could you test 2.6.20-rc2? It's probably fixed there.
i switched to 2.6.20-rc2 last night. we'll see if it happens again.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
prev parent reply other threads:[~2006-12-24 16:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-24 1:03 Alex Romosan
2006-12-24 13:47 ` Jiri Slaby
2006-12-24 16:29 ` Alex Romosan [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=871wmpgsua.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=jirislaby@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®