From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Chr <chunkeey@web.de>
Cc: linux-kernel@vger.kernel.org, Andi Kleen <ak@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7
Date: Sun, 30 Mar 2008 21:25:10 +0200 [thread overview]
Message-ID: <200803302125.10817.rjw@sisk.pl> (raw)
In-Reply-To: <200803302109.22219.chunkeey@web.de>
[Added some CCs]
On Sunday, 30 of March 2008, Chr wrote:
> Hi,
>
> Ever since I went to the new 2.6.25-rcX, I encountered lots of random
> system freezes after about 2 or 3 hours of uptime... but until now,
> I couldn't _catch_ them, since the system
> (AMD Athlon 4200+ X2 (Manchester) / nforce 4 SLI / x86_64) went
> straight into oblivion (nothing on the serial console or anywhere else,
> heck I couldn't even hit reset, It didn't POST anymore)
>
> So. take a look at stuck_task... that's best backtrace I could get...
> (I have other logs too. (Task-list / Lockdep / ... ) but it's too much
> and I hope the _logs_ are already enough.
>
> BTW: I noticed that the clock seems to jump forward and backwards.
> Is this because the CPU-Cores aren't syncronized? (And why are they
> out of sync?)
>
> (And yes, 2.6.24.4 is fine... even hpet works there without any
> rtc: lost 14 interrupts)
>
> cat /proc/interrupts
> CPU0 CPU1
> 0: 51 0 XT-PIC-XT timer
> 1: 43 22170 IO-APIC-edge i8042
> 4: 0 1 IO-APIC-edge
> 6: 0 5 IO-APIC-edge floppy
> 7: 1 0 IO-APIC-edge parport0
> 8: 0 199 IO-APIC-edge rtc
> 9: 0 0 IO-APIC-fasteoi acpi
> 14: 0 0 IO-APIC-edge pata_amd
> 15: 0 0 IO-APIC-edge pata_amd
> 16: 82 51311 IO-APIC-fasteoi firewire_ohci, EMU10K1
> 17: 0 50 IO-APIC-fasteoi firewire_ohci, eth1
> 18: 12 4862 IO-APIC-fasteoi nvidia
> 20: 421 304857 IO-APIC-fasteoi eth0
> 21: 57 33025 IO-APIC-fasteoi ohci_hcd:usb1
> 22: 185 12275 IO-APIC-fasteoi sata_nv
> 23: 276 83270 IO-APIC-fasteoi sata_nv, ehci_hcd:usb2
> NMI: 0 0 Non-maskable interrupts
> LOC: 339847 307599 Local timer interrupts
> RES: 126709 38837 Rescheduling interrupts
> CAL: 605 1054 function call interrupts
> TLB: 1513 3813 TLB shootdowns
> TRM: 0 0 Thermal event interrupts
> THR: 0 0 Threshold APIC interrupts
> SPU: 0 0 Spurious interrupts
> ERR: 1
>
next prev parent reply other threads:[~2008-03-30 19:25 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 [this message]
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
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=200803302125.10817.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ak@suse.de \
--cc=akpm@linux-foundation.org \
--cc=chunkeey@web.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox