I see people on this list are using gcc-3 snapshots, so I thought I'd ask
advice here to narrow the problem down, before posting a gcc bug report.
I've been sitting on this for a couple of days without getting anywhere.
If I use a recent gcc snapshot (example : 4th June), I get an oops if I
try to use "df". The following output from ksymoops relates to a recent
example. No modules were loaded at the time, so the modules file was
empty.
Can people on this list using x86 gcc-3 snapshots let me know if
"df" works for them, and if so a summary of their hardware / .config .
"df" only gets as far as printing the column titles before the oops occurs.
As far as I can tell, the only things at all out of the ordinary are that
I have an AMD K6-2/500 and one of my partitions uses reiserfs (which was
why I tried -ac6).
The oops follows, I wasn't using any modules at the time.
ksymoops 2.4.1 on i586 2.4.5-ac6. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.5-ac6/ (default)
-m /boot/System.map-2.4.5-ac6 (specified)
No modules in ksyms, skipping objects
Warning (read_lsmod): no symbols in lsmod, is /proc/modules a valid lsmod file?
Jun 6 11:42:27 reg_kipling kernel: Unable to handle kernel paging request at virtual address a2fcc113
Jun 6 11:42:27 reg_kipling kernel: c11ec8fd
Jun 6 11:42:27 reg_kipling kernel: *pde = 00000000
Jun 6 11:42:27 reg_kipling kernel: Oops: 0002
Jun 6 11:42:27 reg_kipling kernel: CPU: 0
Jun 6 11:42:27 reg_kipling kernel: EIP: 0010:[<c11ec8fd>]
Using defaults from ksymoops -t elf32-i386 -a i386
Jun 6 11:42:27 reg_kipling kernel: EFLAGS: 00010286
Jun 6 11:42:27 reg_kipling kernel: eax: c2cd1f90 ebx: 00000000 ecx: 00000000 edx: c11ec8fc
Jun 6 11:42:27 reg_kipling kernel: esi: 00000000 edi: 00000000 ebp: c113a2fc esp: c2cd1f98
Jun 6 11:42:27 reg_kipling kernel: ds: 0018 es: 0018 ss: 0018
Jun 6 11:42:27 reg_kipling kernel: Process df (pid: 521, stackpage=c2cd1000)
Jun 6 11:42:27 reg_kipling kernel: Stack: ffffffe7 bffff150 c11c9e94 00000009 00000001 00000004 c2cd0000 08051ea0
Jun 6 11:42:27 reg_kipling kernel: bffff8e0 bffff848 c0107277 08051ea0 bffff7f0 401420e0 08051ea0 bffff8e0
Jun 6 11:42:27 reg_kipling kernel: bffff848 00000063 0000002b 0000002b 00000063 400efd61 00000023 00000246
Jun 6 11:42:27 reg_kipling kernel: Call Trace: [system_call+55/64]
Jun 6 11:42:27 reg_kipling kernel: Code: a2 13 c1 fc a2 13 c1 fc c8 1e c1 6c 8c 16 c1 6c 8c 16 c1 10
>>EIP; c11ec8fd <END_OF_CODE+e89149/????> <=====
Code; c11ec8fd <END_OF_CODE+e89149/????>
00000000 <_EIP>:
Code; c11ec8fd <END_OF_CODE+e89149/????> <=====
0: a2 13 c1 fc a2 mov %al,0xa2fcc113 <=====
Code; c11ec902 <END_OF_CODE+e8914e/????>
5: 13 c1 adc %ecx,%eax
Code; c11ec904 <END_OF_CODE+e89150/????>
7: fc cld
Code; c11ec905 <END_OF_CODE+e89151/????>
8: c8 1e c1 6c enter $0xc11e,$0x6c
Code; c11ec909 <END_OF_CODE+e89155/????>
c: 8c 16 movl %ss,(%esi)
Code; c11ec90b <END_OF_CODE+e89157/????>
e: c1 6c 8c 16 c1 shrl $0xc1,0x16(%esp,%ecx,4)
Code; c11ec910 <END_OF_CODE+e8915c/????>
13: 10 00 adc %al,(%eax)
1 warning issued. Results may not be reliable.
For what it's worth, I also get the "probable hardware bug. clock timer"
message from this kernel with the gcc-3 snapshot. The mobo is a Jetway
542C, with an ALi chipset.
Needless to say, everything works fine with gcc-2.96. .config and dmesg
output attached.
Cheers.
Ken
-- That's it, six times nine, forty-two.Home page : http://www.kenmoffat.uklinux.net
This archive was generated by hypermail 2b29 : Fri Jun 15 2001 - 21:00:12 EST