From: "Michal Piotrowski" <michal.k.k.piotrowski@gmail.com>
To: "Ben Duncan" <ben@versaccounting.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: EIP Errors kernel 2.6.18 ...
Date: Tue, 26 Sep 2006 17:51:59 +0200 [thread overview]
Message-ID: <6bffcb0e0609260851q5d97f784i47d43f2076843600@mail.gmail.com> (raw)
In-Reply-To: <45194883.3080700@versaccounting.com>
Hi,
On 26/09/06, Ben Duncan <ben@versaccounting.com> wrote:
> Getting EIP erros with 2.6.18 ...
> following from Syslog ..
>
> Any Ideas what is going on?
> Thanks ...
>
> Sep 26 04:46:23 desktop kernel: ------------[ cut here ]------------
> Sep 26 04:46:23 desktop kernel: kernel BUG at lib/radix-tree.c:404!
> Sep 26 04:46:23 desktop kernel: invalid opcode: 0000 [#1]
> Sep 26 04:46:23 desktop kernel: DEBUG_PAGEALLOC
> Sep 26 04:46:23 desktop kernel: Modules linked in: sr_mod nvidia uhci_hcd nvidia_agp
> i2c_nforce2 sata_nv sd_mod ide_scsi agpgart sata_sil libata genrtc
> Sep 26 04:46:23 desktop kernel: CPU: 0
> Sep 26 04:46:23 desktop kernel: EIP: 0060:[<c01ba714>] Tainted: P VLI
"When emailing linux-bugs@nvidia.com, please attach an
nvidia-bug-report.log, which is generated by running
"nvidia-bug-report.sh". "
http://www.nvidia.com/object/linux_display_ia32_1.0-8774.html
Please send this report to Nvidia.
Regards,
Michal
--
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/)
next prev parent reply other threads:[~2006-09-26 15:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 15:34 Ben Duncan
2006-09-26 15:51 ` Michal Piotrowski [this message]
2006-09-26 17:39 ` EIP Errors kernel 2.6.18 .AND hard lockup Ben Duncan
2006-09-26 18:00 ` Valdis.Kletnieks
2006-09-26 18:09 ` Ben Duncan
2006-10-25 13:56 ` EIP Errors kernel 2.6.18 .AND hard lockup ... Revisted Ben Duncan
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=6bffcb0e0609260851q5d97f784i47d43f2076843600@mail.gmail.com \
--to=michal.k.k.piotrowski@gmail.com \
--cc=ben@versaccounting.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®