From: Ingo Molnar <mingo@elte•hu>
To: Thomas Gleixner <tglx@linutronix•de>
Cc: Andrew Morton <akpm@linux-foundation•org>,
torvalds@linux-foundation•org, sfr@canb•auug.org.au,
linux-next@vger•kernel.org, linux-kernel@vger•kernel.org,
yhlu.kernel@gmail•com, ink@jurassic•park.msu.ru,
jbarnes@virtuousgeek•org, netdev@vger•kernel.org,
viro@zeniv•linux.org.uk, ebiederm@xmission•com,
dwmw2@infradead•org, sam@ravnborg•org, johnstul@us•ibm.com
Subject: Re: linux-next: Tree for September 3
Date: Fri, 5 Sep 2008 13:04:11 +0200 [thread overview]
Message-ID: <20080905110411.GA26846@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.10.0809050121440.3243@apollo.tec.linutronix.de>
* Thomas Gleixner <tglx@linutronix•de> wrote:
> On Thu, 4 Sep 2008, Andrew Morton wrote:
> > >
> > > Cute, NULL pointer in the timer check code. Can you please addr2line
> > > the exact code line or upload the vmlinux somewhere ?
> > >
> >
> > erm, I might have lost that binary, and it only happened the once. It
> > happened shortly after the machine had fully booted, during
> > establishment of the first sshd session.
> >
> > It nuked the machine really well, too. I had to pull the battery to
> > get it back.
>
> Known problem on Sonys. :(
>
> > fwiw:
> >
> > (gdb) l *0xc0126e7f
> > 0xc0126e7f is in get_next_timer_interrupt (kernel/timer.c:863).
> > warning: Source file is more recent than executable.
> > 858 for (array = 0; array < 4; array++) {
> > 859 struct tvec *varp = varray[array];
> > 860
> > 861 index = slot = timer_jiffies & TVN_MASK;
> > 862 do {
> > 863 list_for_each_entry(nte, varp->vec + slot, entry) {
> > 864 found = 1;
> > 865 if (time_before(nte->expires, expires))
> > 866 expires = nte->expires;
> > 867 }
> >
> > which looks reasonable.
>
> Yeah, as Linus decoded it's that loop. So we look at some corrupted
> entry here.
>
> CONFIG_DEBUG_OBJECTS (add debug_objects to the command line as well)
> should catch it when this is a timer being discarded, freed or
> reinitialized.
>
> Otherwise, when it is just random corruption it wont help much.
i guess CONFIG_DEBUG_OBJECTS_TIMERS=y is practical, and
CONFIG_DEBUG_LIST=y would be nice as well - it can catch memory
corruptions rather early and is relatively light-weight.
[ and if there's any reproducability of the corruption and if it happens
at a stable kernel address then a small custom hack in ftrace can
catch it the moment it happens. ]
Ingo
next prev parent reply other threads:[~2008-09-05 11:05 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 9:16 linux-next: Tree for September 3 Stephen Rothwell
2008-09-04 2:32 ` [PATCH] hid: fix gyration build error Randy Dunlap
2008-09-04 6:52 ` Jiri Slaby
2008-09-04 8:06 ` Jiri Kosina
2008-09-04 4:42 ` linux-next: Tree for September 3 Andrew Morton
2008-09-04 4:46 ` Andrew Morton
2008-09-04 4:54 ` Andrew Morton
2008-09-04 4:57 ` Stephen Rothwell
2008-09-04 5:05 ` Andrew Morton
2008-09-04 5:20 ` Stephen Rothwell
2008-09-04 6:01 ` Andrew Morton
2008-09-04 7:15 ` Andrew Morton
2008-09-04 7:48 ` Stephen Rothwell
2008-09-04 9:19 ` Alan Cox
2008-09-04 9:21 ` Alan Cox
2008-09-04 11:01 ` Alan Cox
2008-09-04 14:35 ` Alan Cox
2008-09-04 5:26 ` Linus Torvalds
2008-09-04 5:42 ` Andrew Morton
2008-09-04 5:00 ` Stephen Rothwell
2008-09-04 5:21 ` Linus Torvalds
2008-09-04 5:33 ` Andrew Morton
2008-09-04 7:14 ` Yinghai Lu
2008-09-04 8:00 ` Andrew Morton
2008-09-04 8:23 ` Linus Torvalds
2008-09-04 8:02 ` Linus Torvalds
2008-09-04 8:25 ` Andrew Morton
2008-09-04 8:37 ` Andrew Morton
2008-09-04 9:03 ` Linus Torvalds
2008-09-04 8:50 ` Linus Torvalds
2008-09-04 8:57 ` Andrew Morton
2008-09-04 9:07 ` Linus Torvalds
2008-09-04 17:45 ` Andrew Morton
2008-09-04 18:05 ` Linus Torvalds
2008-09-04 18:34 ` Andrew Morton
2008-09-04 20:31 ` Eric W. Biederman
2008-09-04 20:41 ` Andrew Morton
2008-09-04 21:03 ` Eric W. Biederman
2008-09-04 22:22 ` Andrew Morton
2008-09-04 22:45 ` Thomas Gleixner
2008-09-04 23:17 ` Linus Torvalds
2008-09-05 5:39 ` Arjan van de Ven
2008-09-04 23:17 ` Andrew Morton
2008-09-04 23:25 ` Linus Torvalds
2008-09-04 23:27 ` Thomas Gleixner
2008-09-05 11:04 ` Ingo Molnar [this message]
2008-09-05 17:49 ` Andrew Morton
2008-09-09 4:39 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2009-09-03 11:59 Stephen Rothwell
2010-09-03 3:52 Stephen Rothwell
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=20080905110411.GA26846@elte.hu \
--to=mingo@elte$(echo .)hu \
--cc=akpm@linux-foundation$(echo .)org \
--cc=dwmw2@infradead$(echo .)org \
--cc=ebiederm@xmission$(echo .)com \
--cc=ink@jurassic$(echo .)park.msu.ru \
--cc=jbarnes@virtuousgeek$(echo .)org \
--cc=johnstul@us$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sam@ravnborg$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=tglx@linutronix$(echo .)de \
--cc=torvalds@linux-foundation$(echo .)org \
--cc=viro@zeniv$(echo .)linux.org.uk \
--cc=yhlu.kernel@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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