Package: linux-2.6
Tags: patch
Since beginning of 2005 I tried different kernel/Linux-images 2.6.x
on my Alphastation 500/500:
=
cpu : Alpha
cpu model : EV56
cpu variation : 7
cpu revision: 0
cpu serial number :
system type : Alcor
system variation: Alcor
system revision : 0
system serial number:
cycle frequency [Hz]: 5
timer frequency [Hz]: 1024.00
page size [bytes] : 8192
phys. address bits : 40
max. addr. space # : 127
BogoMIPS: 994.44
kernel unaligned acc: 0 (pc=0,va=0)
user unaligned acc : 0 (pc=0,va=0)
platform string : Digital AlphaStation 500/500
cpus detected : 1
L1 Icache : 8K, 1-way, 32b line
L1 Dcache : 8K, 1-way, 32b line
L2 cache: 96K, 3-way, 64b line
L3 cache: 8192K, 1-way, 64b line
Tried kernels were 2.6.8-1, 2.6.8-2, 2.6.10, 2.6.12,... All kernels
crash on this machine with the following message (ksymoops):
ksymoops 2.4.9 on alpha 2.6.8-2-generic. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.6.8-2-generic/ (default)
-m /boot/System.map-2.6.8-2-generic (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
Error (regular_file): read_ksyms stat /proc/ksyms failed
No modules in ksyms, skipping objects
No ksyms, skipping lsmod
Trace:
[fc31a164] handle_IRQ_event+0x74/0xf0
[fc31ab50] handle_irq+0xe0/0x1c0
[fc329b04] srm_device_interrupt+0x24/0x40
[fc31b1f4] do_entInt+0xf4/0x140
[fc315260] ret_from_sys_call+0x0/0x10
[fc316e30] default_idle+0x0/0x10
[fc316e98] cpu_idel+0x58/0x80
[fc316e30] default_idle+0x0/0x10
[fc316e30] default_idle+0x0/0x10
[fc310234] rest_init+0x34/0x50
[fc31001c] __start+0x1c/0x20
Code: 243f0010 245f0020 21c10100 21a20200 a4490008 a429
b4410008 b422
Using defaults from ksymoops -t elf64-alpha -a alpha
Trace; fc31a164 handle_IRQ_event+74/f0
Trace; fc31ab50 handle_irq+e0/1c0
Trace; fc329b04 srm_device_interrupt+24/40
Trace; fc31b1f4 do_entInt+f4/140
Trace; fc315260 ret_from_sys_call+0/10
Trace; fc316e30 default_idle+0/10
Trace; fc316e98 cpu_idle+58/80
Trace; fc316e30 default_idle+0/10
Trace; fc316e30 default_idle+0/10
Trace; fc310234 rest_init+34/50
Trace; fc31001c _stext+1c/20
Code; ffe8 END_OF_CODE+39a83a8/
_PC:
Code; ffe8 END_OF_CODE+39a83a8/
0: 10 00 3f 24 ldah t0,16
Code; ffec END_OF_CODE+39a83ac/
4: 20 00 5f 24 ldah t1,32
Code; fff0 END_OF_CODE+39a83b0/
8: 00 01 c1 21 lda s5,256(t0)
Code; fff4 END_OF_CODE+39a83b4/
c: 00 02 a2 21 lda s4,512(t1)
Code; fff8 END_OF_CODE+39a83b8/
10: 08 00 49 a4 ldq t1,8(s0)
Code; fffc END_OF_CODE+39a83bc/
14: 00 00 29 a4 ldq t0,0(s0)
Code; Before first symbol
18: 08 00 41 b4 stq t1,8(t0)
Code; 0004 Before first symbol
1c: 00 00 22 b4 stq t0,0(t1)
Kernel panic: Aiee, killing interrupt handler!
=
The time of the crash depends on multiple factors. Sometimes after 3
hours, sometimes after two days, but mostly during idle time. A
device driver is not affected because the crash always occurs inside
arch/alpha/kernel/irq.c in function handle_irq_event. This could be a
problem after the call to an interrupt handler of a driver but this
also happens with changed hardware/drivers (2 different drivers for
scsi, 3 different drivers for ethernet, with/without SATA,
with/without USB). Nevertheless, here the hardware configuration:
=
:00:06.0 Ethernet controller: Digital Equipment Corporation
DECchip 21040 [Tulip] (rev 26)
Flags: bus master, medium devsel, latency 255, IRQ 29
I/O ports at 9400 [size=128]
Memory at 022dd000 (32-bit, non-prefetchable) [size=128]
:00:07.0 RAID bus controller: Silicon Image, Inc. (formerly CMD
Technology Inc) SiI 3114 [SATALink/SATARaid] Serial ATA Controller
