From: Andrew Morton <akpm@osdl.org>
To: David Miller <davem@davemloft.net>
Cc: preining@logic.at, linux-kernel@vger.kernel.org,
Michael Chan <mchan@broadcom.com>,
netdev@vger.kernel.org
Subject: Re: tg3 kernel bug in 2.6.18-mm3 and 2.6.19-rc2-mm2
Date: Sat, 21 Oct 2006 23:36:10 -0700 [thread overview]
Message-ID: <20061021233610.f190e0a8.akpm@osdl.org> (raw)
In-Reply-To: <20061021.123814.106436476.davem@davemloft.net>
On Sat, 21 Oct 2006 12:38:14 -0700 (PDT)
David Miller <davem@davemloft.net> wrote:
> From: Norbert Preining <preining@logic.at>
> Date: Sat, 21 Oct 2006 15:22:39 +0200
>
> > [<c010469d>] dump_stack+0x12/0x14
> > [<c0141cb3>] softlockup_tick+0xaa/0xc1
> > [<c0129bad>] update_process_times+0x3b/0x5e
> > [<c01362a1>] handle_update_profile+0x14/0x1e
> > [<c0115956>] smp_apic_timer_interrupt+0x49/0x5b
> > [<c0103998>] apic_timer_interrupt+0x28/0x30
> > DWARF2 unwinder stuck at apic_timer_interrupt+0x28/0x30
> > Leftover inexact backtrace:
> > [<c01d03af>] delay_tsc+0xb/0x13
> > [<c01d03e0>] __delay+0x6/0x7
>
> It's OOPS'ing by softlockup'ing in udelay() and then we get a corrupt
> backtrace.
The unwinder-based backtrace is screwed up (yet again) but the old-style
backtrace is there, in all its messy glory.
Weeding out the crap, I think it's this:
[<c01d03af>] delay_tsc+0xb/0x13
[<c01d03e0>] __delay+0x6/0x7
[<c022c240>] _tw32_flush+0x3f/0x51
[<c022da97>] tg3_switch_clocks+0x8f/0x93
<I assume tg3_init_hw() got inlined>
[<c0237673>] tg3_open+0x250/0x520
[<c02d3263>] dev_open+0x2b/0x62
[<c02d1dd8>] dev_change_flags+0x47/0xe4
[<c0307fcc>] devinet_ioctl+0x252/0x556
[<c02d2e5a>] dev_ifsioc+0x113/0x38d
[<c02d29c4>] dev_load+0x24/0x4b
[<c02c9265>] sock_ioctl+0x19e/0x1c2
It's strange that the post-2.6.19-rc2 changes triggered this - that code
won't have run yet.
Norbert, are you really sure?
prev parent reply other threads:[~2006-10-22 6:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-21 13:22 Norbert Preining
2006-10-21 17:02 ` Andrew Morton
2006-10-21 17:18 ` Rafael J. Wysocki
2006-10-21 23:41 ` Norbert Preining
2006-10-22 5:47 ` Michael Chan
2006-10-22 16:22 ` Norbert Preining
2006-10-22 18:13 ` Norbert Preining
2006-10-21 19:38 ` David Miller
2006-10-22 6:36 ` Andrew Morton [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=20061021233610.f190e0a8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=preining@logic.at \
/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®