Once again I'm back with my mysterious oopses. It's still the
same Hardware: Gigabyte GA-586ATE (Triton), Adaptec AHA-2940UW
(Bios 1.34.3), Pentium 133, ...
In my earlier post I assumed that this coud be the aic7xxx
driver's fault. Doug Ledford suggested fiddling with my DRAM
timings and cache settings but this didn't help. Maybe somebody
could recommend me a RAM testing program so I could check this
probability. Util then I attach my newest oops from 2.2.1-ac1.
Regards
Martin
-- "Absolutely nothing should be concluded from these figures except that no conclusion can be drawn from them." (By Joseph L. Brothers, Linux/PowerPC Project)--6c2NcOVqGQ03X4Wi Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="ksymoops-2.2.1-ac1"
Options used: -V (default) -o /lib/modules/2.2.1-ac1/ (default) -k /proc/ksyms (default) -l /proc/modules (default) -m /usr/src/linux/System.map (default) -c 1 (default)
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.
n 29 18:24:36 nexus kernel: Unable to handle kernel NULL pointer dereference at virtual address 00000400 Jan 29 18:24:36 nexus kernel: current->tss.cr3 = 01943000, `r3 = 01943000 Jan 29 18:24:36 nexus kernel: *pde = 00000000 Jan 29 18:24:36 nexus kernel: Oops: 0000 Jan 29 18:24:36 nexus kernel: CPU: 0 Jan 29 18:24:36 nexus kernel: EIP: 0010:[<c0123efa>] Jan 29 18:24:36 nexus kernel: EFLAGS: 00010206 Jan 29 18:24:36 nexus kernel: eax: 00000400 ebx: 000144fa ecx: 00000b02 edx: 00000400 Jan 29 18:24:36 nexus kernel: esi: 00000800 edi: 000144fa ebp: c1940b02 esp: c1947cfc Jan 29 18:24:36 nexus kernel: ds: 0018 es: 0018 ss: 0018 Jan 29 18:24:36 nexus kernel: Process dd (pid: 660, process nr: 83, stackpage=c1947000) Jan 29 18:24:36 nexus kernel: Stack: c0123f29 00000b02 000144fa 00000800 c0124187 00000b02 000144fa 00000800 Jan 29 18:24:36 nexus kernel: 00000001 00000000 c1947e90 c1947e94 00000002 c0127371 00000b02 000144fa Jan 29 18:24:36 nexus kernel: 00000800 c1a53aa0 0804c3da 0804c3da 00000800 08048000 c160b900 08040008 Jan 29 18:24:36 nexus kernel: Call Trace: [<c0123f29>] [<c0124187>] [<c0127371>] [<c480cb53>] [<c4800002>] [<c480cadb>] [<c480cb53>] Jan 29 18:24:36 nexus kernel: [<c018ea79>] [<c480c17e>] [<c010ef27>] [<c018c731>] [<c010ef27>] [<c0192bab>] [<c0193b5a>] [<c0108b95>] Jan 29 18:24:36 nexus kernel: [<c018ada7>] [<c0122aa6>] [<c0107b0c>] Jan 29 18:24:36 nexus kernel: Code: 8b 12 39 58 04 75 f3 39 70 08 75 ee 66 39 48 0c 75 e8 89 c2
>>EIP: c0123efa <find_buffer+2a/44> Trace: c0123f29 <get_hash_table+15/20> Trace: c0124187 <getblk+1f/21c> Trace: c0127371 <block_read+30d/524> Trace: c480cb53 <requeue_sd_request+2b/ddc> Trace: c4800002 <_end+460cefa/460ef44> Trace: c480cadb <do_sd_request+177/1c4> Trace: c480cb53 <requeue_sd_request+2b/ddc> Trace: c018ea79 <add_blkdev_randomness+45/4c> Trace: c018ada7 <flush_to_ldisc+cf/d8> Code: c0123efa <find_buffer+2a/44> 00000000 <_EIP>: Code: c0123efa <find_buffer+2a/44> 0: 8b 12 movl (%edx),%edx Code: c0123efc <find_buffer+2c/44> 2: 39 58 04 cmpl %ebx,0x4(%eax) Code: c0123eff <find_buffer+2f/44> 5: 75 f3 jne fffffffa <_EIP+0xfffffffa> c0123ef4 <find_buffer+24/44> Code: c0123f01 <find_buffer+31/44> 7: 39 70 08 cmpl %esi,0x8(%eax) Code: c0123f04 <find_buffer+34/44> a: 75 ee jne fffffffa <_EIP+0xfffffffa> c0123ef4 <find_buffer+24/44> Code: c0123f06 <find_buffer+36/44> c: 66 39 48 0c cmpw %cx,0xc(%eax) Code: c0123f0a <find_buffer+3a/44> 10: 75 e8 jne fffffffa <_EIP+0xfffffffa> c0123ef4 <find_buffer+24/44> Code: c0123f0c <find_buffer+3c/44> 12: 89 c2 movl %eax,%edx
4 warnings issued. Results may not be reliable.
--6c2NcOVqGQ03X4Wi--
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/