From: Ben Duncan <ben@versaccounting.com>
To: linux-kernel@vger.kernel.org
Subject: Re: EIP Errors kernel 2.6.18 .AND hard lockup ...
Date: Tue, 26 Sep 2006 12:39:49 -0500 [thread overview]
Message-ID: <451965E5.1080600@versaccounting.com> (raw)
In-Reply-To: <6bffcb0e0609260851q5d97f784i47d43f2076843600@mail.gmail.com>
Ok, first IANAKP (I am not a kernel programmer ) ;-> ...
But, just got another hard lockup and EIP code ...
I am not sure why this should got to nVidia (Please, I
personally know the Head of nVidias' Linux driver development,
so if it is a nVidia problem, I can help there).
Anway,
EIP shows :
desktop kernel: CPU: 0
desktop kernel: EIP: 0060:[<c01ba714>] Tainted: P VLI
EFLAGS: 00010046 (2.6.18 #1)
desktop kernel: EIP is at radix_tree_tag_set+0x6a/0xa2
desktop kernel: eax: 00000001 ebx: 00000001 ecx: 00000001 edx: 00000001
desktop kernel: esi: 00000000 edi: 00000000 ebp: f7cf3d70 esp: f7cf3d54
desktop kernel: ds: 007b es: 007b ss: 0068
desktop kernel: Process pdflush (pid: 181, ti=f7cf2000 task=f7cd6a90 task.ti=f7cf2000)
desktop kernel: Stack: 00000001 00000001 00050001 f71a2f4c c1061be0 f71a2f48 00000000
f7cf3d88c01ba3cc t radix_tree_node_alloc
c01ba416 T radix_tree_preload
c01ba475 t radix_tree_extend
c01ba4ff T radix_tree_insert
c01ba5fc T radix_tree_lookup_slot
c01ba651 T radix_tree_lookup
c01ba6aa T radix_tree_tag_set
c01ba74c T radix_tree_tag_clear
c01ba81a t __lookup
c01ba906 T radix_tree_gang_lookup
desktop kernel: c013579e 00000286 f57d5f68 c1061be0 00050002 f7cf3db8 c014ccc8 00000000
desktop kernel: 00001000 f57d5f68 000773b0 00000000 c0150760 f71a2e70 00000000 c1061be0
With current system map showing:
c01ba3cc t radix_tree_node_alloc
c01ba416 T radix_tree_preload
c01ba475 t radix_tree_extend
c01ba4ff T radix_tree_insert
c01ba5fc T radix_tree_lookup_slot
c01ba651 T radix_tree_lookup
c01ba6aa T radix_tree_tag_set
c01ba74c T radix_tree_tag_clear
c01ba81a t __lookup
c01ba906 T radix_tree_gang_lookup
The "radix lookup" seems to be occuring inside of the radix_tree_tag_set
and in particular the pdflush routine.
fgrep'ing kernel shows this is in the lib/radix-tree routine ..
To me seems to be a PDFLUSH eip and the nvidia stuff is just
a by product of loaded modules, no?
Thnaks ..
Michal Piotrowski wrote:
> Hi,
>
<SNIP>
>
> "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
>
--
Ben Duncan - Business Network Solutions, Inc. 336 Elton Road Jackson MS, 39212
"Never attribute to malice, that which can be adequately explained by stupidity"
- Hanlon's Razor
next prev parent reply other threads:[~2006-09-26 17:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-26 15:34 EIP Errors kernel 2.6.18 Ben Duncan
2006-09-26 15:51 ` Michal Piotrowski
2006-09-26 17:39 ` Ben Duncan [this message]
2006-09-26 18:00 ` EIP Errors kernel 2.6.18 .AND hard lockup 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=451965E5.1080600@versaccounting.com \
--to=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