linux-kernel - sungem lockup on 2.6.26.2 on sparc64

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-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.1.10.0808071138160.3804@squeaker.ratbox.org>
Date:	Thu, 7 Aug 2008 11:39:55 -0400 (EDT)
From:	Aaron Sethman <androsyn@...box.org>
To:	linux-kernel@...r.kernel.org
Subject: sungem lockup on 2.6.26.2 on sparc64

Got this on 2.6.26.2 on sparc64

eth1: Pause is disabled
BUG: soft lockup - CPU#0 stuck for 61s! [ifconfig:1297]
TSTATE: 0000000080009600 TPC: 00000000005ed080 TNPC: 00000000005ed084 Y: 
00000000    Not tainted
g0: 0000000000000000 g1: fffff80047beef90 g2: fffff80047beef90 g3: 
fffff80065670560
g4: fffff80066193060 g5: 0000006574683100 g6: fffff80047bec000 g7: 
00000000007db630
o0: fffff80065670000 o1: fffff80047bec400 o2: 0000000000460f24 o3: 
0000000000000100
o4: fffff80066096000 o5: fffff80066096000 sp: fffff80047bee6e1 ret_pc: 
00000000004610b4
l0: 00000000007da780 l1: 0000000000000100 l2: fffff80047beef90 l3: 
00000000005ed080
l4: 0000000000715758 l5: 00000000007db790 l6: 00000000007dbb90 l7: 
ff2002ffff2002ff
i0: 00000000007da320 i1: fffff80066096650 i2: 0000000000000001 i3: 
0000000000000000
i4: 00000000007dc390 i5: 00000000007dbf90 i6: fffff80047bee7b1 i7: 
000000000045bf10


The output of ksymoops on this is as follows:

Reading Oops report from the terminal
TSTATE: 0000000080009600 TPC: 00000000005ed080 TNPC: 00000000005ed084 Y: 
00000000    Not tainted
Using defaults from ksymoops -a sparc
g0: 0000000000000000 g1: fffff80047beef90 g2: fffff80047beef90 g3: 
fffff80065670560
g4: fffff80066193060 g5: 0000006574683100 g6: fffff80047bec000 g7: 
00000000007db630
o0: fffff80065670000 o1: fffff80047bec400 o2: 0000000000460f24 o3: 
0000000000000100
o4: fffff80066096000 o5: fffff80066096000 sp: fffff80047bee6e1 ret_pc: 
00000000004610b4
l0: 00000000007da780 l1: 0000000000000100 l2: fffff80047beef90 l3: 
00000000005ed080
l4: 0000000000715758 l5: 00000000007db790 l6: 00000000007dbb90 l7: 
ff2002ffff2002ff
i0: 00000000007da320 i1: fffff80066096650 i2: 0000000000000001 i3: 
0000000000000000
i4: 00000000007dc390 i5: 00000000007dbf90 i6: fffff80047bee7b1 i7: 
000000000045bf10


>>TPC; 005ed080 <sym53c8xx_timer+0/40>   <=====

>>g7; 007db630 <boot_tvec_bases+eb0/2040>
>>o2; 00460f24 <run_timer_softirq+4/200>
>>ret_pc; 004610b4 <run_timer_softirq+194/200>
>>l0; 007da780 <boot_tvec_bases+0/2040>
>>l3; 005ed080 <sym53c8xx_timer+0/40>
>>l4; 00715758 <jiffies+0/0>
>>l5; 007db790 <boot_tvec_bases+1010/2040>
>>l6; 007dbb90 <boot_tvec_bases+1410/2040>
>>i0; 007da320 <softirq_vec+10/200>
>>i4; 007dc390 <boot_tvec_bases+1c10/2040>
>>i5; 007dbf90 <boot_tvec_bases+1810/2040>
>>i7; 0045bf10 <__do_softirq+70/100>


Any ideas or clues?

-Aaron
--
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/