From: Thomas Gleixner <tglx@linutronix.de>
To: "Renato S. Yamane" <renatoyamane@mandic.com.br>
Cc: linux-kernel@vger.kernel.org, alan-jenkins@tuffmail.co.uk,
devzero@web.de, mingo@elte.hu
Subject: Re: Kernel Linux 2.6.23.16 hangs when run updatedb
Date: Tue, 11 Mar 2008 09:11:32 +0100 (CET) [thread overview]
Message-ID: <alpine.LFD.1.00.0803110803280.3781@apollo.tec.linutronix.de> (raw)
In-Reply-To: <47D54A8B.2020303@mandic.com.br>
On Mon, 10 Mar 2008, Renato S. Yamane wrote:
> > > How can I fix this? Is safe run reiserfsck?
> >
> >
> > I think he's wrong.
> >
> > Looking at the call trace, the BUG happens during an interrupt. It
> > could be a coincidence that the interrupt happened during this
> > particular system call.
> >
> > It looks like a timer callback has been corrupted / set to an invalid
> > value. The BUG is due to accessing the invalid address 61060fe0
> > within enqueue_hrtimer, and the EIP (instruction pointer) is also
> > equal to 61060fe0. This would be consistent with the source code of
> > enqueue_hrtimer. It's not an obvious reiserfs issue.
It's pretty inconsistent with the source code of enqueue_hrtimer().
The only possibility to have a callback from enqueue_hrtimer() is in
hrtimer_enqueue_reprogram() in the HRTIMER_CB_IRQSAFE_NO_RESTART
case. Such timers can not be requeued in interrupt context, hence the
name HRTIMER_CB_IRQSAFE_NO_RESTART :)
Also in hrtimer_interrupt context, hrtimer_enqueue() is called with
reprogram = 0, which ensures that we do not call
hrtimer_enqueue_reprogram().
> > I don't know how to find out where this corruption is happening, but
> > it's worth asking the hrtimers people.
Let's gather some more information.
Renato, some questions:
1) is this fully reproducible with updatedb ?
2) are you sure that this is the first stacktrace you captured, there
might be some BUG before that which scrolled out of sight. Any chance
to use a serial console ?
3) Can you please recompile the kernel with CONFIF_DEBUG_INFO set
and then run the following addresses from the backtrace through
addr2line with the new vmlinux:
# addr2line -e vmlinux 0xc013dad9 0xc0107c3b
Please provide the output.
4) Looking at your .config it seems you have some more patches applied
aside of the .16 stable. Can you please upload a full patch queue
somewhere ?
Thanks,
tglx
next prev parent reply other threads:[~2008-03-11 8:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 14:49 Renato S. Yamane
2008-03-11 8:11 ` Thomas Gleixner [this message]
2008-03-11 14:33 ` Renato S. Yamane
2008-03-11 15:03 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2008-03-07 20:44 devzero
2008-03-10 11:22 ` Kernel " Renato S. Yamane
2008-03-07 16:04 Renato S. Yamane
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=alpine.LFD.1.00.0803110803280.3781@apollo.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=devzero@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=renatoyamane@mandic.com.br \
/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®