linux-kernel - Re: The never ending BEEEEP/__smp_call_function

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <200803302125.10817.rjw@sisk.pl>
Date:	Sun, 30 Mar 2008 21:25:10 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Chr <chunkeey@....de>
Cc:	linux-kernel@...r.kernel.org, Andi Kleen <ak@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: The never ending BEEEEP/__smp_call_function_mask with 2.6.25-rc7

[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
> 
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/