From: Chr <chunkeey@web.de>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-kernel@vger.kernel.org,
Andi Kleen <andi-suse@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Date: Mon, 31 Mar 2008 00:19:44 +0200 [thread overview]
Message-ID: <200803310019.45219.chunkeey@web.de> (raw)
In-Reply-To: <alpine.LFD.1.10.0803302315270.3219@apollo.tec.linutronix.de>
On Sunday 30 March 2008 23:36:40 Thomas Gleixner wrote:
> On Sun, 30 Mar 2008, Chr wrote:
> > > > it's "hpet" (in both cases...)
> > >
> > > Hmm. That should be stable. Which clock is jumping back and forth ?
> > > The one in the logs or the system clock ?
> >
> > The one in the logs... (but it's because of the TSC, right?)
>
> Yes. I thought this was fixed already in Linus tree, but I might be
> wrong as usual.
>
> Anyway, that's not the real problem; I read your original post in
> meantime :)
>
> > Ever since I went to the new 2.6.25-rcX ...
>
> Did this problem start with 25-rc1 ? What is the latest version you
> tried ?
I had other problems with 25-rc1 as well.. but this one is now gone with
the dm-crypto update. I'll try rc1 tomorrow...
>
> > [ 5215.101875] [<ffffffff80217d8f>] __smp_call_function_mask+0x90/0xc5
> > [ 5215.108493] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> > [ 5215.114422] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> > [ 5215.120348] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> > [ 5215.126276] [<ffffffff80217e0d>] smp_call_function_mask+0x49/0x61
> > [ 5215.132723] [<ffffffff8029b433>] invalidate_bh_lru+0x0/0x42
> > [ 5215.138649] [<ffffffff802339a3>] on_each_cpu+0x10/0x2c
> > [ 5215.144135] [<ffffffff8029fb4b>] kill_bdev+0x1e/0x33
> > [ 5215.149456] [<ffffffff802a01da>] __blkdev_put+0x4f/0x128
> > [ 5215.155124] [<ffffffff8027dd93>] __fput+0xa1/0x164
> > [ 5215.160272] [<ffffffff8027b67d>] filp_close+0x5d/0x65
> > [ 5215.165679] [<ffffffff80231072>] put_files_struct+0x66/0xc4
> > [ 5215.171607] [<ffffffff802323ea>] do_exit+0x245/0x64c
> > [ 5215.176925] [<ffffffff80238b94>] __dequeue_signal+0xff/0x159
> > [ 5215.182941] [<ffffffff80232867>] do_group_exit+0x76/0x93
> > [ 5215.188606] [<ffffffff8023a0fd>] get_signal_to_deliver+0x2b9/0x2e5
> > [ 5215.195141] [<ffffffff8020a466>] do_notify_resume+0xaf/0x7e0
> > [ 5215.201155] [<ffffffff80291414>] mntput_no_expire+0x1f/0x86
> > [ 5215.201155] [<ffffffff80291414>] mntput_no_expire+0x1f/0x86
>
> You mentioned that you have tons of other logs. Can you please
> upload those to some place? If you don't have a possiblity, please
> contact me private and I'll provide you one.
>
http://www.file-upload.net/download-758265/logs.tar.bz2.html
and hit Download. ;-)
(BTW, the you can ignore some logs like freeze7, ... I tried
nolapic, but that doesn't play well with SATA?!)
Regards,
Chr
next prev parent reply other threads:[~2008-03-30 22:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-30 19:09 The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Chr
2008-03-30 19:25 ` Rafael J. Wysocki
2008-03-30 19:59 ` Thomas Gleixner
2008-03-30 20:18 ` Chr
2008-03-30 20:37 ` Thomas Gleixner
2008-03-30 21:09 ` Chr
2008-03-30 21:36 ` Thomas Gleixner
2008-03-30 22:19 ` Chr [this message]
2008-03-31 12:56 ` Adrian Bunk
2008-03-31 13:23 ` Chr
2008-03-31 22:01 ` Chr
2008-03-31 23:14 ` Rafael J. Wysocki
2008-03-31 23:30 ` Chr
2008-04-01 21:16 ` Rafael J. Wysocki
2008-04-01 22:27 ` Chr
2008-04-02 12:45 ` Chr
2008-04-01 16:27 ` Thomas Gleixner
2008-04-01 18:57 ` Chr
2008-04-01 22:29 ` Chr
2008-04-02 7:08 ` Thomas Gleixner
2008-04-02 9:34 ` Chr
2008-03-31 7:10 ` Andi Kleen
2008-03-31 12:51 ` Chr
-- strict thread matches above, loose matches on Subject: below --
2008-04-03 22:49 2.6.25-rc8-git2: Reported regressions from 2.6.24 Rafael J. Wysocki
2008-04-03 23:22 ` The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7 Rafael J. Wysocki
2008-04-04 1:49 ` Chr
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=200803310019.45219.chunkeey@web.de \
--to=chunkeey@web.de \
--cc=akpm@linux-foundation.org \
--cc=andi-suse@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
--cc=tglx@linutronix.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.