* [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
@ 2001-08-19 4:47 Paul
2001-08-19 5:09 ` Jeff Chua
` (2 more replies)
0 siblings, 3 replies; 18+ messages in thread
From: Paul @ 2001-08-19 4:47 UTC (permalink / raw)
To: linux-kernel
* Kernel oops, and locks up when I run xdos (dosemu)
* Occuring in both 2.4.7-ac6 and 2.4.8-ac7. Run 'xdos' in X, and
machine locks hard, only output to console is oops. (no sysrq)
Tried once with strace, but no oops. (didnt wait long, though)
Some oops before window is placed, some a little while after.
(mouse movement?) Repeatable.
* Kernels are virgin linus patched with ac. AMD-K6(tm) 3D
processor
* If anyone wants any more info or for me to do anything, just
ask.
Paul
set@pobox.com
(2.4.7-ac6 -- two captured, identitcal, first shown)
ksymoops 2.4.1 on i586 2.4.7-ac6. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.7-ac6/ (default)
-m /boot/System.map-2.4.7-ac6 (specified)
CPU: 0
EIP: 0010:[<c0180a18>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010002
eax: 00001000 ebx: c4562368 ecx: 00000000 edx: 00000001
esi: c4562368 edi: c4a954d4 ebp: 00000001 esp: c6887d88
ds: 008 es: 0000 ss: 0018
Process xdos (pid: 28039, stackpage=c6887000)
Stack: c4562768 c4562368 00000001 00000000 c4562000 c4a954d4 00000202 00000001
00000001 c0181815 c4562000 c4562568 c4562168 00000001 00000000 0000000e
00000001 00000202 00000000 00000282 0000000e c0117554 0000000e 00000001
Call Trace: [<c0181815>] [<c0117554>] [<c01173cc>] [<c01174ac>] [<c017fc3f>]
[<c0113e24>] [<c01163f6>] [<c0113d7e>] [<c0113c61>] [<c01139fb>] [<c0107ece>]
[<c010760c>] [<c0109cfe>] [<c010760c>] [<c0106bed>] [<c0106ad3>]
Code: a4 8b 7c 24 1c 8b 8c 24 b0 00 00 00 01 d3 29 d5 ba 00 10 00
>>EIP; c0180a18 <n_tty_receive_buf+a4/edc> <=====
Trace; c0181815 <n_tty_receive_buf+ea1/edc>
Trace; c0117554 <send_sig_info+74/98>
Trace; c01173cc <send_signal+2c/f0>
Trace; c01174ac <deliver_signal+1c/50>
Trace; c017fc3f <flush_to_ldisc+db/e4>
Trace; c0113e24 <__run_task_queue+4c/60>
Trace; c01163f6 <tqueue_bh+16/1c>
Trace; c0113d7e <bh_action+1a/30>
Trace; c0113c61 <tasklet_hi_action+51/b4>
Trace; c01139fb <do_softirq+5b/ac>
Trace; c0107ece <do_IRQ+9e/b0>
Trace; c010760c <do_general_protection+0/6c>
Trace; c0109cfe <call_do_IRQ+5/17>
Trace; c010760c <do_general_protection+0/6c>
Trace; c0106bed <error_code+2d/40>
Trace; c0106ad3 <system_call+33/40>
Code; c0180a18 <n_tty_receive_buf+a4/edc>
00000000 <_EIP>:
Code; c0180a18 <n_tty_receive_buf+a4/edc> <=====
0: a4 movsb %ds:(%esi),%es:(%edi) <=====
Code; c0180a19 <n_tty_receive_buf+a5/edc>
1: 8b 7c 24 1c mov 0x1c(%esp,1),%edi
Code; c0180a1d <n_tty_receive_buf+a9/edc>
5: 8b 8c 24 b0 00 00 00 mov 0xb0(%esp,1),%ecx
Code; c0180a24 <n_tty_receive_buf+b0/edc>
c: 01 d3 add %edx,%ebx
Code; c0180a26 <n_tty_receive_buf+b2/edc>
e: 29 d5 sub %edx,%ebp
Code; c0180a28 <n_tty_receive_buf+b4/edc>
10: ba 00 10 00 00 mov $0x1000,%edx
<0>Kernel panic: Aiee, killing interrupt handler!
===================================================================
(2.4.8-ac7)
ksymoops 2.4.1 on i586 2.4.8-ac7. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.8-ac7/ (default)
-m /boot/System.map-2.4.8-ac7 (specified)
CPU: 0
EIP: 0010:[<c0180ab8>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010002
eax: 00001000 ebx: c77dc168 ecx: 00000000 edx: 00000001
esi: c77dc168 edi: c524c1aa ebp: 00000001 esp: c7195d88
ds: 0018 es: 0000 ss: 0018
Process xdos (pid: 252, stackpage=c7195000)
Stack: c77dc568 c77dc168 00000000 00000000 00000046 c7195dbc 00000202 00000001
007dc000 c524c1aa c77dc984 00000282 00000001 c01818b5 c77dc000 c77dc768
c77dc368 00000000 00000000 00000286 0000000e 00000202 00000000 00000001
Call Trace: [<c01818b5>] [<c0112fe4>] [<c011735c>] [<c011743c>] [<c017fcdf>]
[<c0113d94>] [<c0116366>] [<c0113cde>] [<c0113c12>] [<c0113a3b>] [<c0107eee>]
[<c010762c>] [<c0109d1e>] [<c010762c>] [<c0106c0d>] [<c0106af3>]
Code: a4 8b 7c 24 1c 8b 8c 24 b0 00 00 00 01 d3 29 d5 ba 00 10 00
>>EIP; c0180ab8 <n_tty_receive_buf+a4/edc> <=====
Trace; c01818b5 <n_tty_receive_buf+ea1/edc>
Trace; c0112fe4 <it_real_fn+0/44>
Trace; c011735c <send_signal+2c/f0>
Trace; c011743c <deliver_signal+1c/50>
Trace; c017fcdf <flush_to_ldisc+db/e4>
Trace; c0113d94 <__run_task_queue+4c/60>
Trace; c0116366 <tqueue_bh+16/1c>
Trace; c0113cde <bh_action+1a/40>
Trace; c0113c12 <tasklet_hi_action+42/64>
Trace; c0113a3b <do_softirq+5b/ac>
Trace; c0107eee <do_IRQ+9e/b0>
Trace; c010762c <do_general_protection+0/6c>
Trace; c0109d1e <call_do_IRQ+5/17>
Trace; c010762c <do_general_protection+0/6c>
Trace; c0106c0d <error_code+2d/40>
Trace; c0106af3 <system_call+33/40>
Code; c0180ab8 <n_tty_receive_buf+a4/edc>
00000000 <_EIP>:
Code; c0180ab8 <n_tty_receive_buf+a4/edc> <=====
0: a4 movsb %ds:(%esi),%es:(%edi) <=====
Code; c0180ab9 <n_tty_receive_buf+a5/edc>
1: 8b 7c 24 1c mov 0x1c(%esp,1),%edi
Code; c0180abd <n_tty_receive_buf+a9/edc>
5: 8b 8c 24 b0 00 00 00 mov 0xb0(%esp,1),%ecx
Code; c0180ac4 <n_tty_receive_buf+b0/edc>
c: 01 d3 add %edx,%ebx
Code; c0180ac6 <n_tty_receive_buf+b2/edc>
e: 29 d5 sub %edx,%ebp
Code; c0180ac8 <n_tty_receive_buf+b4/edc>
10: ba 00 10 00 00 mov $0x1000,%edx
<0>Kernel panic: Aiee, killing interrupt handler!
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
2001-08-19 4:47 [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos Paul
@ 2001-08-19 5:09 ` Jeff Chua
2001-08-19 5:40 ` Paul
2001-08-19 5:10 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 " Jeff Chua
2001-08-22 2:45 ` Brian Gerst
2 siblings, 1 reply; 18+ messages in thread
From: Jeff Chua @ 2001-08-19 5:09 UTC (permalink / raw)
To: Paul; +Cc: linux-kernel
xdos runs fine for me for all of 2.4.x. Mine is P3.
Thanks,
Jeff
[ jchua@fedex.com ]
On Sun, 19 Aug 2001, Paul wrote:
> * Kernel oops, and locks up when I run xdos (dosemu)
>
> * Occuring in both 2.4.7-ac6 and 2.4.8-ac7. Run 'xdos' in X, and
> machine locks hard, only output to console is oops. (no sysrq)
> Tried once with strace, but no oops. (didnt wait long, though)
> Some oops before window is placed, some a little while after.
> (mouse movement?) Repeatable.
>
> * Kernels are virgin linus patched with ac. AMD-K6(tm) 3D
> processor
>
> * If anyone wants any more info or for me to do anything, just
> ask.
>
> Paul
> set@pobox.com
>
> (2.4.7-ac6 -- two captured, identitcal, first shown)
>
> ksymoops 2.4.1 on i586 2.4.7-ac6. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.7-ac6/ (default)
> -m /boot/System.map-2.4.7-ac6 (specified)
>
> CPU: 0
> EIP: 0010:[<c0180a18>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010002
> eax: 00001000 ebx: c4562368 ecx: 00000000 edx: 00000001
> esi: c4562368 edi: c4a954d4 ebp: 00000001 esp: c6887d88
> ds: 008 es: 0000 ss: 0018
> Process xdos (pid: 28039, stackpage=c6887000)
> Stack: c4562768 c4562368 00000001 00000000 c4562000 c4a954d4 00000202 00000001
> 00000001 c0181815 c4562000 c4562568 c4562168 00000001 00000000 0000000e
> 00000001 00000202 00000000 00000282 0000000e c0117554 0000000e 00000001
> Call Trace: [<c0181815>] [<c0117554>] [<c01173cc>] [<c01174ac>] [<c017fc3f>]
> [<c0113e24>] [<c01163f6>] [<c0113d7e>] [<c0113c61>] [<c01139fb>] [<c0107ece>]
> [<c010760c>] [<c0109cfe>] [<c010760c>] [<c0106bed>] [<c0106ad3>]
> Code: a4 8b 7c 24 1c 8b 8c 24 b0 00 00 00 01 d3 29 d5 ba 00 10 00
>
> >>EIP; c0180a18 <n_tty_receive_buf+a4/edc> <=====
> Trace; c0181815 <n_tty_receive_buf+ea1/edc>
> Trace; c0117554 <send_sig_info+74/98>
> Trace; c01173cc <send_signal+2c/f0>
> Trace; c01174ac <deliver_signal+1c/50>
> Trace; c017fc3f <flush_to_ldisc+db/e4>
> Trace; c0113e24 <__run_task_queue+4c/60>
> Trace; c01163f6 <tqueue_bh+16/1c>
> Trace; c0113d7e <bh_action+1a/30>
> Trace; c0113c61 <tasklet_hi_action+51/b4>
> Trace; c01139fb <do_softirq+5b/ac>
> Trace; c0107ece <do_IRQ+9e/b0>
> Trace; c010760c <do_general_protection+0/6c>
> Trace; c0109cfe <call_do_IRQ+5/17>
> Trace; c010760c <do_general_protection+0/6c>
> Trace; c0106bed <error_code+2d/40>
> Trace; c0106ad3 <system_call+33/40>
> Code; c0180a18 <n_tty_receive_buf+a4/edc>
> 00000000 <_EIP>:
> Code; c0180a18 <n_tty_receive_buf+a4/edc> <=====
> 0: a4 movsb %ds:(%esi),%es:(%edi) <=====
> Code; c0180a19 <n_tty_receive_buf+a5/edc>
> 1: 8b 7c 24 1c mov 0x1c(%esp,1),%edi
> Code; c0180a1d <n_tty_receive_buf+a9/edc>
> 5: 8b 8c 24 b0 00 00 00 mov 0xb0(%esp,1),%ecx
> Code; c0180a24 <n_tty_receive_buf+b0/edc>
> c: 01 d3 add %edx,%ebx
> Code; c0180a26 <n_tty_receive_buf+b2/edc>
> e: 29 d5 sub %edx,%ebp
> Code; c0180a28 <n_tty_receive_buf+b4/edc>
> 10: ba 00 10 00 00 mov $0x1000,%edx
>
> <0>Kernel panic: Aiee, killing interrupt handler!
>
> ===================================================================
>
> (2.4.8-ac7)
>
> ksymoops 2.4.1 on i586 2.4.8-ac7. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.8-ac7/ (default)
> -m /boot/System.map-2.4.8-ac7 (specified)
>
> CPU: 0
> EIP: 0010:[<c0180ab8>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010002
> eax: 00001000 ebx: c77dc168 ecx: 00000000 edx: 00000001
> esi: c77dc168 edi: c524c1aa ebp: 00000001 esp: c7195d88
> ds: 0018 es: 0000 ss: 0018
> Process xdos (pid: 252, stackpage=c7195000)
> Stack: c77dc568 c77dc168 00000000 00000000 00000046 c7195dbc 00000202 00000001
> 007dc000 c524c1aa c77dc984 00000282 00000001 c01818b5 c77dc000 c77dc768
> c77dc368 00000000 00000000 00000286 0000000e 00000202 00000000 00000001
> Call Trace: [<c01818b5>] [<c0112fe4>] [<c011735c>] [<c011743c>] [<c017fcdf>]
> [<c0113d94>] [<c0116366>] [<c0113cde>] [<c0113c12>] [<c0113a3b>] [<c0107eee>]
> [<c010762c>] [<c0109d1e>] [<c010762c>] [<c0106c0d>] [<c0106af3>]
> Code: a4 8b 7c 24 1c 8b 8c 24 b0 00 00 00 01 d3 29 d5 ba 00 10 00
>
> >>EIP; c0180ab8 <n_tty_receive_buf+a4/edc> <=====
> Trace; c01818b5 <n_tty_receive_buf+ea1/edc>
> Trace; c0112fe4 <it_real_fn+0/44>
> Trace; c011735c <send_signal+2c/f0>
> Trace; c011743c <deliver_signal+1c/50>
> Trace; c017fcdf <flush_to_ldisc+db/e4>
> Trace; c0113d94 <__run_task_queue+4c/60>
> Trace; c0116366 <tqueue_bh+16/1c>
> Trace; c0113cde <bh_action+1a/40>
> Trace; c0113c12 <tasklet_hi_action+42/64>
> Trace; c0113a3b <do_softirq+5b/ac>
> Trace; c0107eee <do_IRQ+9e/b0>
> Trace; c010762c <do_general_protection+0/6c>
> Trace; c0109d1e <call_do_IRQ+5/17>
> Trace; c010762c <do_general_protection+0/6c>
> Trace; c0106c0d <error_code+2d/40>
> Trace; c0106af3 <system_call+33/40>
> Code; c0180ab8 <n_tty_receive_buf+a4/edc>
> 00000000 <_EIP>:
> Code; c0180ab8 <n_tty_receive_buf+a4/edc> <=====
> 0: a4 movsb %ds:(%esi),%es:(%edi) <=====
> Code; c0180ab9 <n_tty_receive_buf+a5/edc>
> 1: 8b 7c 24 1c mov 0x1c(%esp,1),%edi
> Code; c0180abd <n_tty_receive_buf+a9/edc>
> 5: 8b 8c 24 b0 00 00 00 mov 0xb0(%esp,1),%ecx
> Code; c0180ac4 <n_tty_receive_buf+b0/edc>
> c: 01 d3 add %edx,%ebx
> Code; c0180ac6 <n_tty_receive_buf+b2/edc>
> e: 29 d5 sub %edx,%ebp
> Code; c0180ac8 <n_tty_receive_buf+b4/edc>
> 10: ba 00 10 00 00 mov $0x1000,%edx
>
> <0>Kernel panic: Aiee, killing interrupt handler!
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
2001-08-19 4:47 [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos Paul
2001-08-19 5:09 ` Jeff Chua
@ 2001-08-19 5:10 ` Jeff Chua
2001-08-22 2:45 ` Brian Gerst
2 siblings, 0 replies; 18+ messages in thread
From: Jeff Chua @ 2001-08-19 5:10 UTC (permalink / raw)
To: Paul; +Cc: linux-kernel
Xdos runs fine for me for all of 2.4.x. Mine is P3.
Thanks,
Jeff
[ jchua@fedex.com ]
On Sun, 19 Aug 2001, Paul wrote:
> * Kernel oops, and locks up when I run xdos (dosemu)
>
> * Occuring in both 2.4.7-ac6 and 2.4.8-ac7. Run 'xdos' in X, and
> machine locks hard, only output to console is oops. (no sysrq)
> Tried once with strace, but no oops. (didnt wait long, though)
> Some oops before window is placed, some a little while after.
> (mouse movement?) Repeatable.
>
> * Kernels are virgin linus patched with ac. AMD-K6(tm) 3D
> processor
>
> * If anyone wants any more info or for me to do anything, just
> ask.
>
> Paul
> set@pobox.com
>
> (2.4.7-ac6 -- two captured, identitcal, first shown)
>
> ksymoops 2.4.1 on i586 2.4.7-ac6. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.7-ac6/ (default)
> -m /boot/System.map-2.4.7-ac6 (specified)
>
> CPU: 0
> EIP: 0010:[<c0180a18>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010002
> eax: 00001000 ebx: c4562368 ecx: 00000000 edx: 00000001
> esi: c4562368 edi: c4a954d4 ebp: 00000001 esp: c6887d88
> ds: 008 es: 0000 ss: 0018
> Process xdos (pid: 28039, stackpage=c6887000)
> Stack: c4562768 c4562368 00000001 00000000 c4562000 c4a954d4 00000202 00000001
> 00000001 c0181815 c4562000 c4562568 c4562168 00000001 00000000 0000000e
> 00000001 00000202 00000000 00000282 0000000e c0117554 0000000e 00000001
> Call Trace: [<c0181815>] [<c0117554>] [<c01173cc>] [<c01174ac>] [<c017fc3f>]
> [<c0113e24>] [<c01163f6>] [<c0113d7e>] [<c0113c61>] [<c01139fb>] [<c0107ece>]
> [<c010760c>] [<c0109cfe>] [<c010760c>] [<c0106bed>] [<c0106ad3>]
> Code: a4 8b 7c 24 1c 8b 8c 24 b0 00 00 00 01 d3 29 d5 ba 00 10 00
>
> >>EIP; c0180a18 <n_tty_receive_buf+a4/edc> <=====
> Trace; c0181815 <n_tty_receive_buf+ea1/edc>
> Trace; c0117554 <send_sig_info+74/98>
> Trace; c01173cc <send_signal+2c/f0>
> Trace; c01174ac <deliver_signal+1c/50>
> Trace; c017fc3f <flush_to_ldisc+db/e4>
> Trace; c0113e24 <__run_task_queue+4c/60>
> Trace; c01163f6 <tqueue_bh+16/1c>
> Trace; c0113d7e <bh_action+1a/30>
> Trace; c0113c61 <tasklet_hi_action+51/b4>
> Trace; c01139fb <do_softirq+5b/ac>
> Trace; c0107ece <do_IRQ+9e/b0>
> Trace; c010760c <do_general_protection+0/6c>
> Trace; c0109cfe <call_do_IRQ+5/17>
> Trace; c010760c <do_general_protection+0/6c>
> Trace; c0106bed <error_code+2d/40>
> Trace; c0106ad3 <system_call+33/40>
> Code; c0180a18 <n_tty_receive_buf+a4/edc>
> 00000000 <_EIP>:
> Code; c0180a18 <n_tty_receive_buf+a4/edc> <=====
> 0: a4 movsb %ds:(%esi),%es:(%edi) <=====
> Code; c0180a19 <n_tty_receive_buf+a5/edc>
> 1: 8b 7c 24 1c mov 0x1c(%esp,1),%edi
> Code; c0180a1d <n_tty_receive_buf+a9/edc>
> 5: 8b 8c 24 b0 00 00 00 mov 0xb0(%esp,1),%ecx
> Code; c0180a24 <n_tty_receive_buf+b0/edc>
> c: 01 d3 add %edx,%ebx
> Code; c0180a26 <n_tty_receive_buf+b2/edc>
> e: 29 d5 sub %edx,%ebp
> Code; c0180a28 <n_tty_receive_buf+b4/edc>
> 10: ba 00 10 00 00 mov $0x1000,%edx
>
> <0>Kernel panic: Aiee, killing interrupt handler!
>
> ===================================================================
>
> (2.4.8-ac7)
>
> ksymoops 2.4.1 on i586 2.4.8-ac7. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.8-ac7/ (default)
> -m /boot/System.map-2.4.8-ac7 (specified)
>
> CPU: 0
> EIP: 0010:[<c0180ab8>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010002
> eax: 00001000 ebx: c77dc168 ecx: 00000000 edx: 00000001
> esi: c77dc168 edi: c524c1aa ebp: 00000001 esp: c7195d88
> ds: 0018 es: 0000 ss: 0018
> Process xdos (pid: 252, stackpage=c7195000)
> Stack: c77dc568 c77dc168 00000000 00000000 00000046 c7195dbc 00000202 00000001
> 007dc000 c524c1aa c77dc984 00000282 00000001 c01818b5 c77dc000 c77dc768
> c77dc368 00000000 00000000 00000286 0000000e 00000202 00000000 00000001
> Call Trace: [<c01818b5>] [<c0112fe4>] [<c011735c>] [<c011743c>] [<c017fcdf>]
> [<c0113d94>] [<c0116366>] [<c0113cde>] [<c0113c12>] [<c0113a3b>] [<c0107eee>]
> [<c010762c>] [<c0109d1e>] [<c010762c>] [<c0106c0d>] [<c0106af3>]
> Code: a4 8b 7c 24 1c 8b 8c 24 b0 00 00 00 01 d3 29 d5 ba 00 10 00
>
> >>EIP; c0180ab8 <n_tty_receive_buf+a4/edc> <=====
> Trace; c01818b5 <n_tty_receive_buf+ea1/edc>
> Trace; c0112fe4 <it_real_fn+0/44>
> Trace; c011735c <send_signal+2c/f0>
> Trace; c011743c <deliver_signal+1c/50>
> Trace; c017fcdf <flush_to_ldisc+db/e4>
> Trace; c0113d94 <__run_task_queue+4c/60>
> Trace; c0116366 <tqueue_bh+16/1c>
> Trace; c0113cde <bh_action+1a/40>
> Trace; c0113c12 <tasklet_hi_action+42/64>
> Trace; c0113a3b <do_softirq+5b/ac>
> Trace; c0107eee <do_IRQ+9e/b0>
> Trace; c010762c <do_general_protection+0/6c>
> Trace; c0109d1e <call_do_IRQ+5/17>
> Trace; c010762c <do_general_protection+0/6c>
> Trace; c0106c0d <error_code+2d/40>
> Trace; c0106af3 <system_call+33/40>
> Code; c0180ab8 <n_tty_receive_buf+a4/edc>
> 00000000 <_EIP>:
> Code; c0180ab8 <n_tty_receive_buf+a4/edc> <=====
> 0: a4 movsb %ds:(%esi),%es:(%edi) <=====
> Code; c0180ab9 <n_tty_receive_buf+a5/edc>
> 1: 8b 7c 24 1c mov 0x1c(%esp,1),%edi
> Code; c0180abd <n_tty_receive_buf+a9/edc>
> 5: 8b 8c 24 b0 00 00 00 mov 0xb0(%esp,1),%ecx
> Code; c0180ac4 <n_tty_receive_buf+b0/edc>
> c: 01 d3 add %edx,%ebx
> Code; c0180ac6 <n_tty_receive_buf+b2/edc>
> e: 29 d5 sub %edx,%ebp
> Code; c0180ac8 <n_tty_receive_buf+b4/edc>
> 10: ba 00 10 00 00 mov $0x1000,%edx
>
> <0>Kernel panic: Aiee, killing interrupt handler!
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
2001-08-19 5:09 ` Jeff Chua
@ 2001-08-19 5:40 ` Paul
2001-08-19 8:04 ` Jeff Chua
0 siblings, 1 reply; 18+ messages in thread
From: Paul @ 2001-08-19 5:40 UTC (permalink / raw)
To: Jeff Chua; +Cc: linux-kernel
Jeff Chua <jchua@fedex.com>, on Sun Aug 19, 2001 [01:09:26 PM] said:
> xdos runs fine for me for all of 2.4.x. Mine is P3.
>
> Thanks,
> Jeff
> [ jchua@fedex.com ]
>
Actually, it works fine for me too, _if_ I use DOS 5 as
the boot image, but I changed to DOS 6.22, and its has oops'd
every time Ive tried it that way. Its just a trigger for whatever
the real problem is.
Paul
set@pobox.com
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
2001-08-19 5:40 ` Paul
@ 2001-08-19 8:04 ` Jeff Chua
2001-08-19 20:30 ` Eric W. Biederman
0 siblings, 1 reply; 18+ messages in thread
From: Jeff Chua @ 2001-08-19 8:04 UTC (permalink / raw)
To: Paul; +Cc: Jeff Chua, Linux Kernel
On Sun, 19 Aug 2001, Paul wrote:
> Actually, it works fine for me too, _if_ I use DOS 5 as
> the boot image, but I changed to DOS 6.22, and its has oops'd
> every time Ive tried it that way. Its just a trigger for whatever
> the real problem is.
>
> Paul
> set@pobox.com
I'm using dosemu-1.1.1.tgz with Windows 98 [Version 4.10.2222]
Does "dos" command works for you instead of "xdos" ?
Did you check your shmmax?
Try ...
echo 1000000000 >/proc/sys/kernel/shmmax
Jeff
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
2001-08-19 8:04 ` Jeff Chua
@ 2001-08-19 20:30 ` Eric W. Biederman
2001-08-20 1:43 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] " Paul
0 siblings, 1 reply; 18+ messages in thread
From: Eric W. Biederman @ 2001-08-19 20:30 UTC (permalink / raw)
To: Jeff Chua; +Cc: Paul, Jeff Chua, Linux Kernel
Jeff Chua <jeffchua@silk.corp.fedex.com> writes:
> On Sun, 19 Aug 2001, Paul wrote:
> > Actually, it works fine for me too, _if_ I use DOS 5 as
> > the boot image, but I changed to DOS 6.22, and its has oops'd
> > every time Ive tried it that way. Its just a trigger for whatever
> > the real problem is.
> >
> > Paul
> > set@pobox.com
>
> I'm using dosemu-1.1.1.tgz with Windows 98 [Version 4.10.2222]
>
> Does "dos" command works for you instead of "xdos" ?
>
> Did you check your shmmax?
>
> Try ...
> echo 1000000000 >/proc/sys/kernel/shmmax
This should be totally irrelevant. You shouldn't be able to
crash linux with dosemu unless you are doing direct hardware access.
There are a number of cases, where dosemu is different enough it has
been known to cause code to go down buggy non-common paths and cause
things to fail. This has happened with both X and the kernel.
I suspect that is what is happening here.
Paul is dosemu configured to do any direct hardware access?
Also of interest is that this crash is not even directly triggered by
the dosemu process. Instead an interrupt handler is doing something
bad.
Paul If you can verify that dosemu isn't doing any direct hardware
access. i.e. Dosemu isn't suid root, and you have no ports lines
you should be fine.
Eric
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-19 20:30 ` Eric W. Biederman
@ 2001-08-20 1:43 ` Paul
2001-08-20 6:09 ` Eric W. Biederman
0 siblings, 1 reply; 18+ messages in thread
From: Paul @ 2001-08-20 1:43 UTC (permalink / raw)
To: Eric W. Biederman; +Cc: Linux Kernel
"Eric W. Biederman" <ebiederm@xmission.com>, on Sun Aug 19, 2001 [02:30:29 PM] said:
[...]
> There are a number of cases, where dosemu is different enough it has
> been known to cause code to go down buggy non-common paths and cause
> things to fail. This has happened with both X and the kernel.
> I suspect that is what is happening here.
>
> Paul is dosemu configured to do any direct hardware access?
>
> Also of interest is that this crash is not even directly triggered by
> the dosemu process. Instead an interrupt handler is doing something
> bad.
>
> Paul If you can verify that dosemu isn't doing any direct hardware
> access. i.e. Dosemu isn't suid root, and you have no ports lines
> you should be fine.
>
> Eric
>
Dear Eric;
No, the program isnt setuid, nor run by root, and no
ports specified in the config. Let me know if there is anything
further I can do.
Paul
set@pobox.com
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-20 1:43 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] " Paul
@ 2001-08-20 6:09 ` Eric W. Biederman
2001-08-21 1:14 ` Paul
0 siblings, 1 reply; 18+ messages in thread
From: Eric W. Biederman @ 2001-08-20 6:09 UTC (permalink / raw)
To: Paul; +Cc: Linux Kernel
Paul <set@pobox.com> writes:
> Dear Eric;
>
> No, the program isnt setuid, nor run by root, and no
> ports specified in the config. Let me know if there is anything
> further I can do.
O.k. Then it is most definentily not dosemu, but a kernel or an X bug.
Running dosemu as just dos so it runs in a terminal window will rule
out X.
If you can rule out X stracing dosemu might be of some help. The
challenge now is to track down what dosemu is doing that is triggering
the problem.
As an interrupt handler is where the oops is occuring. Finding an
immediate cause and effect could be tricky.
Eric
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-20 6:09 ` Eric W. Biederman
@ 2001-08-21 1:14 ` Paul
2001-08-21 6:08 ` Eric W. Biederman
0 siblings, 1 reply; 18+ messages in thread
From: Paul @ 2001-08-21 1:14 UTC (permalink / raw)
To: Eric W. Biederman; +Cc: Linux Kernel
"Eric W. Biederman" <ebiederm@xmission.com>, on Mon Aug 20, 2001 [12:09:27 AM] said:
> If you can rule out X stracing dosemu might be of some help. The
> challenge now is to track down what dosemu is doing that is triggering
> the problem.
>
> As an interrupt handler is where the oops is occuring. Finding an
> immediate cause and effect could be tricky.
>
> Eric
Dear Eric;
Ok. I oopsed/locked the machine running 'dos' in a vt,
without X in single user mode. Then I did it again, stracing the
session. Unfortunately, the fs was left in such a state, that
fsck completely chucked the logfile out. Then I booted 2.2.18, and
tried. I could not make it oops.
I need to setup a test machine to persue this farther, as
locking and fscking my main box is no fun:) Ill try to get that
strace...
Paul
set@pobox.com
Here are the oopsen, even though I suspect they dont shed any
light:
ksymoops 2.4.1 on i586 2.4.8-ac7. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.8-ac7/ (default)
-m /boot/System.map-2.4.8-ac7 (specified)
CPU: 0
EIP: 0010:[<c89a0417>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: 00000000 ecx: ffffffff edx: 00000010
esi: c269f800 edi: c1e910e6 ebp: c1e910c0 esp: c7a93c74
ds: 0018 es: 0000 ss: 0018
Process dos (pid: 11215, stackpage=c7a93000)
Stack: 00000000 c1e910c0 00000e29 0000006e c1e910e6 006e0028 00690e29 c89a0b2e
c1e910c0 c269f800 c269fa9c 00000000 00000e29 0000006e 00000000 c7a93d98
00000001 c7a93d2a 00000004 00000000 00000000 00000003 00000007 000bdd7c
Call Trace: [<c89a0b2e>] [<c89a1b92>] [<c899c1d4>] [<c89a2e28>] [<c01d8d5c>]
[<c01d0f48>] [<c01d8d5c>] [<c01d8d5c>] [<c01d11fd>] [<c01d8d5c>] [<c89a2778>]
[<c01d7a32>] [<c01d8d5c>] [<c01d7dd8>] [<c01e9bc6>] [<c01e52b9>] [<c01e5362>]
[<c01e7712>] [<c01e7fc5>] [<c01e7e88>] [<c0116a42>] [<c0116abb>] [<c010aa4a>]
[<c010762c>] [<c0106c0d>] [<c0106af3>]
Code: f2 ae f7 d1 49 8b 7c 24 10 49 78 08 ac ae 75 08 84 c0 75 f5
>>EIP; c89a0417 <[ipchains]ip_rule_match+a7/244> <=====
Trace; c89a0b2e <[ipchains]ip_fw_check+21e/488>
Trace; c89a1b92 <[ipchains]ipfw_output_check+5a/60>
Trace; c899c1d4 <[ipchains]fw_in+118/254>
Trace; c89a2e28 <[ipchains]ipfw_ops+0/17>
Trace; c01d8d5c <ip_finish_output2+0/c8>
Trace; c01d0f48 <nf_iterate+30/84>
Trace; c01d8d5c <ip_finish_output2+0/c8>
Trace; c01d8d5c <ip_finish_output2+0/c8>
Trace; c01d11fd <nf_hook_slow+b1/140>
Trace; c01d8d5c <ip_finish_output2+0/c8>
Trace; c89a2778 <[ipchains]postroute_ops+0/18>
Trace; c01d7a32 <ip_output+10a/110>
Trace; c01d8d5c <ip_finish_output2+0/c8>
Trace; c01d7dd8 <ip_queue_xmit+3a0/4f0>
Trace; c01e9bc6 <tcp_v4_send_check+6a/a8>
Trace; c01e52b9 <tcp_transmit_skb+3a9/4f0>
Trace; c01e5362 <tcp_transmit_skb+452/4f0>
Trace; c01e7712 <tcp_send_ack+c2/c8>
Trace; c01e7fc5 <tcp_delack_timer+13d/180>
Trace; c01e7e88 <tcp_delack_timer+0/180>
Trace; c0116a42 <timer_bh+212/24c>
Trace; c0116abb <do_timer+3f/70>
Trace; c010aa4a <timer_interrupt+ba/174>
Trace; c010762c <do_general_protection+0/6c>
Trace; c0106c0d <error_code+2d/40>
Trace; c0106af3 <system_call+33/40>
Code; c89a0417 <[ipchains]ip_rule_match+a7/244>
00000000 <_EIP>:
Code; c89a0417 <[ipchains]ip_rule_match+a7/244> <=====
0: f2 ae repnz scas %es:(%edi),%al <=====
Code; c89a0419 <[ipchains]ip_rule_match+a9/244>
2: f7 d1 not %ecx
Code; c89a041b <[ipchains]ip_rule_match+ab/244>
4: 49 dec %ecx
Code; c89a041c <[ipchains]ip_rule_match+ac/244>
5: 8b 7c 24 10 mov 0x10(%esp,1),%edi
Code; c89a0420 <[ipchains]ip_rule_match+b0/244>
9: 49 dec %ecx
Code; c89a0421 <[ipchains]ip_rule_match+b1/244>
a: 78 08 js 14 <_EIP+0x14> c89a042b <[ipchains]ip_rule_match+bb/244>
Code; c89a0423 <[ipchains]ip_rule_match+b3/244>
c: ac lods %ds:(%esi),%al
Code; c89a0424 <[ipchains]ip_rule_match+b4/244>
d: ae scas %es:(%edi),%al
Code; c89a0425 <[ipchains]ip_rule_match+b5/244>
e: 75 08 jne 18 <_EIP+0x18> c89a042f <[ipchains]ip_rule_match+bf/244>
Code; c89a0427 <[ipchains]ip_rule_match+b7/244>
10: 84 c0 test %al,%al
Code; c89a0429 <[ipchains]ip_rule_match+b9/244>
12: 75 f5 jne 9 <_EIP+0x9> c89a0420 <[ipchains]ip_rule_match+b0/244>
>Kernel panic: Aiee, killing interrupt handler!
ksymoops 2.4.1 on i586 2.4.8-ac7. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.8-ac7/ (default)
-m /boot/System.map-2.4.8-ac7 (specified)
CPU: 0
EIP: 0010:[<c01a4bf0>]
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: 00000000 ebx: 00000000 ecx: 00000003 edx: c251cbc0
esi: 00001000 edi: c7f9b000 ebp: c1df8000 esp: c19cfd7c
ds: 0018 es: 0000 ss: 0018
Process dos (pid: 271, stackpage=c19cf000)
Stack: c7f9c000 00000001 c02a5e80 00000000 00000000 c7f9b000 00000001 c7f9b000
c01a4c4d c02a5e40 c7f92140 0000d000 00000001 c02a5e80 c02a5e40 c01a4a8f
c01a5140 c02a5e80 00000001 000001f6 c02a5e40 c7f92140 c02a5e80 0032a000
Call Trace: [<c01a4c4d>] [<c01a4a8f>] [<c01a5140>] [<c01a4a8f>] [<c01a85e0>]
[<c01a07ca>] [<c01a0825>] [<c01a0b76>] [<c01a100b>] [<c01a4aa0>] [<c0107d5c>]
[<c0107ebe>] [<c010762c>] [<c0109d1e>] [<c010762c>] [<c0106c0d>] [<c0106b7f>]
Code: f3 ab 8b 44 24 14 89 28 8b 4c 24 10 8b 7c 24 1c 89 74 0f 08
>>EIP; c01a4bf0 <ide_build_sglist+a8/e0> <=====
Trace; c01a4c4d <ide_build_dmatable+25/148>
Trace; c01a4a8f <ali15x3_dmaproc+3f/50>
Trace; c01a5140 <ide_dmaproc+e8/210>
Trace; c01a4a8f <ali15x3_dmaproc+3f/50>
Trace; c01a85e0 <do_rw_disk+184/308>
Trace; c01a07ca <start_request+12e/204>
Trace; c01a0825 <start_request+189/204>
Trace; c01a0b76 <ide_do_request+27e/2c4>
Trace; c01a100b <ide_intr+12b/14c>
Trace; c01a4aa0 <ide_dma_intr+0/a8>
Trace; c0107d5c <handle_IRQ_event+30/5c>
Trace; c0107ebe <do_IRQ+6e/b0>
Trace; c010762c <do_general_protection+0/6c>
Trace; c0109d1e <call_do_IRQ+5/17>
Trace; c010762c <do_general_protection+0/6c>
Trace; c0106c0d <error_code+2d/40>
Trace; c0106b7f <tracesys+1f/23>
Code; c01a4bf0 <ide_build_sglist+a8/e0>
00000000 <_EIP>:
Code; c01a4bf0 <ide_build_sglist+a8/e0> <=====
0: f3 ab repz stos %eax,%es:(%edi) <=====
Code; c01a4bf2 <ide_build_sglist+aa/e0>
2: 8b 44 24 14 mov 0x14(%esp,1),%eax
Code; c01a4bf6 <ide_build_sglist+ae/e0>
6: 89 28 mov %ebp,(%eax)
Code; c01a4bf8 <ide_build_sglist+b0/e0>
8: 8b 4c 24 10 mov 0x10(%esp,1),%ecx
Code; c01a4bfc <ide_build_sglist+b4/e0>
c: 8b 7c 24 1c mov 0x1c(%esp,1),%edi
Code; c01a4c00 <ide_build_sglist+b8/e0>
10: 89 74 0f 08 mov %esi,0x8(%edi,%ecx,1)
<0>Kernel panic: Aiee, killing interrupt handler!
13 warnings issued. Results may not be reliable.
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-21 1:14 ` Paul
@ 2001-08-21 6:08 ` Eric W. Biederman
2001-08-21 16:14 ` Wilfried Weissmann
` (2 more replies)
0 siblings, 3 replies; 18+ messages in thread
From: Eric W. Biederman @ 2001-08-21 6:08 UTC (permalink / raw)
To: Paul; +Cc: Linux Kernel
Paul <set@pobox.com> writes:
> "Eric W. Biederman" <ebiederm@xmission.com>, on Mon Aug 20, 2001 [12:09:27 AM]
> said:
>
>
> > If you can rule out X stracing dosemu might be of some help. The
> > challenge now is to track down what dosemu is doing that is triggering
> > the problem.
> >
> > As an interrupt handler is where the oops is occuring. Finding an
> > immediate cause and effect could be tricky.
> >
> > Eric
>
> Dear Eric;
>
> Ok. I oopsed/locked the machine running 'dos' in a vt,
> without X in single user mode. Then I did it again, stracing the
> session. Unfortunately, the fs was left in such a state, that
> fsck completely chucked the logfile out. Then I booted 2.2.18, and
> tried. I could not make it oops.
> I need to setup a test machine to persue this farther, as
> locking and fscking my main box is no fun:) Ill try to get that
> strace...
O.k. That rules out all kinds of things. What is interesting at first
glance is that a) Every oops has been in an interrupt handler. and
b) It is never remotely at the same location.
I'm beginning to suspect there is some kind of hardware problem. But it
is very weird. I wonder if dos 6.2 somehow tickles a bug in the media GX
processor. Though my top canidate is probably the lazy state switching
introduced in 2.4. I know there were some problems with the ldt that were
fixed, and there might be another case out there. But I'm just guessing
in the dark.
If you can reproduce this on a second machine that would definentily help.
Eric
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-21 6:08 ` Eric W. Biederman
@ 2001-08-21 16:14 ` Wilfried Weissmann
[not found] ` <3B828898.BD98D4C4@gmx.at>
2001-08-22 1:42 ` Paul
2 siblings, 0 replies; 18+ messages in thread
From: Wilfried Weissmann @ 2001-08-21 16:14 UTC (permalink / raw)
To: Kernel Mailing List
"Eric W. Biederman" wrote:
>
> Paul <set@pobox.com> writes:
>
> > "Eric W. Biederman" <ebiederm@xmission.com>, on Mon Aug 20, 2001 [12:09:27 AM]
> > said:
> >
> >
> > > If you can rule out X stracing dosemu might be of some help. The
> > > challenge now is to track down what dosemu is doing that is triggering
> > > the problem.
> > >
> > > As an interrupt handler is where the oops is occuring. Finding an
> > > immediate cause and effect could be tricky.
> > >
> > > Eric
> >
> > Dear Eric;
> >
> > Ok. I oopsed/locked the machine running 'dos' in a vt,
> > without X in single user mode. Then I did it again, stracing the
> > session. Unfortunately, the fs was left in such a state, that
> > fsck completely chucked the logfile out. Then I booted 2.2.18, and
> > tried. I could not make it oops.
> > I need to setup a test machine to persue this farther, as
> > locking and fscking my main box is no fun:) Ill try to get that
> > strace...
>
> O.k. That rules out all kinds of things. What is interesting at first
> glance is that a) Every oops has been in an interrupt handler. and
> b) It is never remotely at the same location.
>
> I'm beginning to suspect there is some kind of hardware problem. But it
> is very weird. I wonder if dos 6.2 somehow tickles a bug in the media GX
> processor. Though my top canidate is probably the lazy state switching
> introduced in 2.4. I know there were some problems with the ldt that were
> fixed, and there might be another case out there. But I'm just guessing
> in the dark.
>
> If you can reproduce this on a second machine that would definentily help.
>
> Eric
I have the same problem on a K7-800. My kernel is 2.4.7-ac3 (with K7
optimization!). Everything else seems to work fine, but dosemu locks up
the computer when running certain games.
Sometimes I can play for quite some time (1/2 hour or more) without
problems. Eventually it will freeze. It feels like it is triggered by
mouse activity.
Wilfried
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
[not found] ` <3B828898.BD98D4C4@gmx.at>
@ 2001-08-21 16:20 ` Eric W. Biederman
2001-08-21 18:49 ` Wilfried Weissmann
0 siblings, 1 reply; 18+ messages in thread
From: Eric W. Biederman @ 2001-08-21 16:20 UTC (permalink / raw)
To: Wilfried Weissmann; +Cc: linux-kernel
Wilfried Weissmann <Wilfried.Weissmann@gmx.at> writes:
>
> I have the same problem on a K7-800. My kernel is 2.4.7-ac3 (with K7
> optimization!). Everything else seems to work fine, but dosemu locks up
> the computer when running certain games.
> Sometimes I can play for quite some time (1/2 hour or more) without
> problems. Eventually it will freeze. It feels like it is triggered by
> mouse activity.
Hmm. There are some similiar conditions. And it may be the same bug.
Is your dosemu not suid root? And running in X when you are playing those
games? You don't have any ports lines in your dosemu.conf?
It is very important to rule out dosemu doing direct hardware access, before investigating
something else like the kernel.
Eric
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-21 16:20 ` Eric W. Biederman
@ 2001-08-21 18:49 ` Wilfried Weissmann
2001-08-21 21:50 ` Wilfried Weissmann
0 siblings, 1 reply; 18+ messages in thread
From: Wilfried Weissmann @ 2001-08-21 18:49 UTC (permalink / raw)
To: Eric W. Biederman; +Cc: linux-kernel
"Eric W. Biederman" wrote:
>
> Wilfried Weissmann <Wilfried.Weissmann@gmx.at> writes:
> >
> > I have the same problem on a K7-800. My kernel is 2.4.7-ac3 (with K7
> > optimization!). Everything else seems to work fine, but dosemu locks up
> > the computer when running certain games.
> > Sometimes I can play for quite some time (1/2 hour or more) without
> > problems. Eventually it will freeze. It feels like it is triggered by
> > mouse activity.
>
> Hmm. There are some similiar conditions. And it may be the same bug.
>
> Is your dosemu not suid root? And running in X when you are playing those
> games? You don't have any ports lines in your dosemu.conf?
>
> It is very important to rule out dosemu doing direct hardware access, before investigating
> something else like the kernel.
I set $_videoportaccess = (0)
This should not change anything since $_graphics=(0) too. However I
experienced no more crashes. (???)
>
> Eric
thanks,
Wilfried
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-21 18:49 ` Wilfried Weissmann
@ 2001-08-21 21:50 ` Wilfried Weissmann
0 siblings, 0 replies; 18+ messages in thread
From: Wilfried Weissmann @ 2001-08-21 21:50 UTC (permalink / raw)
To: Eric W. Biederman, linux-kernel
Wilfried Weissmann wrote:
>
> "Eric W. Biederman" wrote:
> >
> > Wilfried Weissmann <Wilfried.Weissmann@gmx.at> writes:
> > >
> > > I have the same problem on a K7-800. My kernel is 2.4.7-ac3 (with K7
> > > optimization!). Everything else seems to work fine, but dosemu locks up
> > > the computer when running certain games.
> > > Sometimes I can play for quite some time (1/2 hour or more) without
> > > problems. Eventually it will freeze. It feels like it is triggered by
> > > mouse activity.
> >
> > Hmm. There are some similiar conditions. And it may be the same bug.
> >
> > Is your dosemu not suid root? And running in X when you are playing those
> > games? You don't have any ports lines in your dosemu.conf?
> >
> > It is very important to rule out dosemu doing direct hardware access, before investigating
> > something else like the kernel.
>
> I set $_videoportaccess = (0)
> This should not change anything since $_graphics=(0) too. However I
> experienced no more crashes. (???)
argh! I take it back. It just crashed again. There are no port entries
and the setuid bit of the executable is not set.
It is quite hard to reproduce. ... takes some hours of intense testing
;)
Wilfried
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-21 6:08 ` Eric W. Biederman
2001-08-21 16:14 ` Wilfried Weissmann
[not found] ` <3B828898.BD98D4C4@gmx.at>
@ 2001-08-22 1:42 ` Paul
2001-08-22 7:56 ` Eric W. Biederman
2 siblings, 1 reply; 18+ messages in thread
From: Paul @ 2001-08-22 1:42 UTC (permalink / raw)
To: Eric W. Biederman; +Cc: Linux Kernel
"Eric W. Biederman" <ebiederm@xmission.com>, on Tue Aug 21, 2001 [12:08:09 AM] said:
> Paul <set@pobox.com> writes:
>
> > I need to setup a test machine to persue this farther, as
> > locking and fscking my main box is no fun:) Ill try to get that
> > strace...
>
> O.k. That rules out all kinds of things. What is interesting at first
> glance is that a) Every oops has been in an interrupt handler. and
> b) It is never remotely at the same location.
>
> I'm beginning to suspect there is some kind of hardware problem. But it
> is very weird. I wonder if dos 6.2 somehow tickles a bug in the media GX
> processor. Though my top canidate is probably the lazy state switching
> introduced in 2.4. I know there were some problems with the ldt that were
> fixed, and there might be another case out there. But I'm just guessing
> in the dark.
>
> If you can reproduce this on a second machine that would definentily help.
>
> Eric
Dear Eric;
Oops'd twice on intel pentium 90 box. Same dosemu 1.0.0
binary and config files, 2.4.8-ac7 kernel. Behaviour was same as
my k6 box-- I did not decode oops, as that box didnt have a
serial console, and it didnt seem worth transcribing...
(was unable to oops it running 2.2.18pre21 on p90 box) Here
is the tail end of an strace. (the last bit that made it across
the wire during the telnet session-- I logged with fs mounted
sync, but the end of the log was garbage)
Paul
set@pobox.com
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
write(3,
"8\1\4\0\n\0\0\4\10\0\0\0\250\0\0\0L\1\5\0\2\0\0\4\n\0\0"..., 76)
= 76
write(3,
"L\"\r\0\2\0\0\4\n\0\0\4\0\0\34\0\332\304\304\304\304\304"...,
592) = 592
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4 <unfinished ...>
--- SIGALRM (Alarm clock) ---
<... vm86 resumed> ) = -1 ENOSYS (Function not
implemented)
ioctl(3, FIONREAD, [0]) = 0
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = ? ERESTARTNOHAND (To be
restarted)
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4 <unfinished ...>
--- SIGALRM (Alarm clock) ---
<... vm86 resumed> ) = -1 ENOSYS (Function not
implemented)
ioctl(3, FIONREAD, [0]) = 0
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4 <unfinished ...>
--- SIGALRM (Alarm clock) ---
<... vm86 resumed> ) = -1 ENOSYS (Function not
implemented)
ioctl(3, FIONREAD, [0]) = 0
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
write(3,
"L\1\5\0\2\0\0\4\n\0\0\4\0\0|\1\263\304\304\3048\304\5\0"...,
552) = 552
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
--- SIGALRM (Alarm clock) ---
sigreturn() = ? (mask now [])
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4) = -1 ENOSYS
(Function not implemented)
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
select(10, [9], NULL, NULL, {0, 0}) = 0 (Timeout)
vm86(0x1, 0x811e740, 0xa6, 0xfff8fff1, 0x81d66a4 <unfinished ...>
--- SIGALRM (Alarm clock) ---
<... vm86 resumed> ) = -1 ENOSYS (Function not
implemented)
ioctl(3, FIONREAD, [0]) = 0
select(0, [], NULL, NULL, {0, 0}) = 0 (Timeout)
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos
2001-08-19 4:47 [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos Paul
2001-08-19 5:09 ` Jeff Chua
2001-08-19 5:10 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 " Jeff Chua
@ 2001-08-22 2:45 ` Brian Gerst
[not found] ` <20010821232557.G218@squish.home.loc>
2 siblings, 1 reply; 18+ messages in thread
From: Brian Gerst @ 2001-08-22 2:45 UTC (permalink / raw)
To: Paul, Alan Cox; +Cc: linux-kernel
Paul wrote:
>
> * Kernel oops, and locks up when I run xdos (dosemu)
>
> * Occuring in both 2.4.7-ac6 and 2.4.8-ac7. Run 'xdos' in X, and
> machine locks hard, only output to console is oops. (no sysrq)
> Tried once with strace, but no oops. (didnt wait long, though)
> Some oops before window is placed, some a little while after.
> (mouse movement?) Repeatable.
>
> * Kernels are virgin linus patched with ac. AMD-K6(tm) 3D
> processor
>
> * If anyone wants any more info or for me to do anything, just
> ask.
>
> Paul
> set@pobox.com
>
> (2.4.7-ac6 -- two captured, identitcal, first shown)
>
> ksymoops 2.4.1 on i586 2.4.7-ac6. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.7-ac6/ (default)
> -m /boot/System.map-2.4.7-ac6 (specified)
>
> CPU: 0
> EIP: 0010:[<c0180a18>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> EFLAGS: 00010002
> eax: 00001000 ebx: c4562368 ecx: 00000000 edx: 00000001
> esi: c4562368 edi: c4a954d4 ebp: 00000001 esp: c6887d88
> ds: 008 es: 0000 ss: 0018
^^^^
Here is your problem. %es is set to the null segment. I had my
suspicions about the segment reload optimisation in the -ac kernels, and
this proves it. Try backing out the changes to arch/i386/kernel/entry.S
and include/asm-i386/hw_irq.h and see if that fixes the problem.
--
Brian Gerst
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] [resolution]
[not found] ` <3B832904.491AFE0E@didntduck.org>
@ 2001-08-22 4:43 ` Paul
0 siblings, 0 replies; 18+ messages in thread
From: Paul @ 2001-08-22 4:43 UTC (permalink / raw)
To: Brian Gerst; +Cc: linux-kernel
Brian Gerst <bgerst@didntduck.org>, on Tue Aug 21, 2001 [11:37:40 PM] said:
> Paul wrote:
> >
> > Brian Gerst <bgerst@didntduck.org>, on Tue Aug 21, 2001 [10:45:51 PM] said:
> > > > CPU: 0
> > > > EIP: 0010:[<c0180a18>]
> > > > Using defaults from ksymoops -t elf32-i386 -a i386
> > > > EFLAGS: 00010002
> > > > eax: 00001000 ebx: c4562368 ecx: 00000000 edx: 00000001
> > > > esi: c4562368 edi: c4a954d4 ebp: 00000001 esp: c6887d88
> > > > ds: 008 es: 0000 ss: 0018
> > > ^^^^
> > > Here is your problem. %es is set to the null segment. I had my
> > > suspicions about the segment reload optimisation in the -ac kernels, and
> > > this proves it. Try backing out the changes to arch/i386/kernel/entry.S
> > > and include/asm-i386/hw_irq.h and see if that fixes the problem.
> > >
[....]
> Try the attached diff.
>
Dear Brian;
Well, with this backed out, I cannot get an oops anymore.
Thanks.
Paul
set@pobox.com
> --
> Brian Gerst
> --- linux-2.4.8-ac7/arch/i386/kernel/entry.S Mon Aug 20 19:21:49 2001
> +++ linux-2.4.8/arch/i386/kernel/entry.S Sat Jul 7 13:55:12 2001
> @@ -106,14 +106,10 @@
> popl %edi; \
> popl %ebp; \
> popl %eax; \
> - cmpl $__KERNEL_DS,(%esp); \
> - je 4f ; \
> 1: popl %ds; \
> 2: popl %es; \
> addl $4,%esp; \
> 3: iret; \
> -4: addl $12,%esp; \
> - iret; \
> .section .fixup,"ax"; \
> 4: movl $0,(%esp); \
> jmp 1b; \
> @@ -289,11 +285,9 @@
> pushl %esi # push the error code
> pushl %edx # push the pt_regs pointer
> movl $(__KERNEL_DS),%edx
> - cmpl %edx,%ecx
> - jz 1f
> movl %edx,%ds
> movl %edx,%es
> -1: GET_CURRENT(%ebx)
> + GET_CURRENT(%ebx)
> call *%edi
> addl $8,%esp
> jmp ret_from_exception
> --- linux-2.4.8-ac7/include/asm-i386/hw_irq.h Mon Aug 20 19:22:19 2001
> +++ linux-2.4.8/include/asm-i386/hw_irq.h Sat Jul 7 13:55:40 2001
> @@ -95,10 +95,6 @@
> #define __STR(x) #x
> #define STR(x) __STR(x)
>
> -/*
> - * A segment register reload is rather expensive. Try to avoid it
> - * if possible.
> - */
> #define SAVE_ALL \
> "cld\n\t" \
> "pushl %es\n\t" \
> @@ -110,12 +106,9 @@
> "pushl %edx\n\t" \
> "pushl %ecx\n\t" \
> "pushl %ebx\n\t" \
> - "movl $" STR(__KERNEL_DS) ",%eax\n\t" \
> - "cmpl %eax,7*4(%esp)\n\t" \
> - "je 1f\n\t" \
> - "movl %eax,%ds\n\t" \
> - "movl %eax,%es\n\t" \
> - "1:\n\t"
> + "movl $" STR(__KERNEL_DS) ",%edx\n\t" \
> + "movl %edx,%ds\n\t" \
> + "movl %edx,%es\n\t"
>
> #define IRQ_NAME2(nr) nr##_interrupt(void)
> #define IRQ_NAME(nr) IRQ_NAME2(IRQ##nr)
^ permalink raw reply [flat|nested] 18+ messages in thread
* Re: [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] just run xdos
2001-08-22 1:42 ` Paul
@ 2001-08-22 7:56 ` Eric W. Biederman
0 siblings, 0 replies; 18+ messages in thread
From: Eric W. Biederman @ 2001-08-22 7:56 UTC (permalink / raw)
To: Paul; +Cc: Linux Kernel
Paul <set@pobox.com> writes:
> Dear Eric;
>
> Oops'd twice on intel pentium 90 box. Same dosemu 1.0.0
> binary and config files, 2.4.8-ac7 kernel. Behaviour was same as
> my k6 box-- I did not decode oops, as that box didnt have a
> serial console, and it didnt seem worth transcribing...
> (was unable to oops it running 2.2.18pre21 on p90 box) Here
> is the tail end of an strace. (the last bit that made it across
> the wire during the telnet session-- I logged with fs mounted
> sync, but the end of the log was garbage)
O.k. Then there is definentily something going on. From the log
it didn't look like you were doing anything in dosemu. Just what were
you doing in dosemu. Starting dos 6.2 and idling or something else.
A feel for what is going on would help.
Eric
^ permalink raw reply [flat|nested] 18+ messages in thread
end of thread, other threads:[~2001-08-22 8:04 UTC | newest]
Thread overview: 18+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-08-19 4:47 [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 just run xdos Paul
2001-08-19 5:09 ` Jeff Chua
2001-08-19 5:40 ` Paul
2001-08-19 8:04 ` Jeff Chua
2001-08-19 20:30 ` Eric W. Biederman
2001-08-20 1:43 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 [I] " Paul
2001-08-20 6:09 ` Eric W. Biederman
2001-08-21 1:14 ` Paul
2001-08-21 6:08 ` Eric W. Biederman
2001-08-21 16:14 ` Wilfried Weissmann
[not found] ` <3B828898.BD98D4C4@gmx.at>
2001-08-21 16:20 ` Eric W. Biederman
2001-08-21 18:49 ` Wilfried Weissmann
2001-08-21 21:50 ` Wilfried Weissmann
2001-08-22 1:42 ` Paul
2001-08-22 7:56 ` Eric W. Biederman
2001-08-19 5:10 ` [OOPS] repeatable 2.4.8-ac7, 2.4.7-ac6 " Jeff Chua
2001-08-22 2:45 ` Brian Gerst
[not found] ` <20010821232557.G218@squish.home.loc>
[not found] ` <3B832904.491AFE0E@didntduck.org>
2001-08-22 4:43 ` [OOPS] [resolution] Paul
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).