lkml.org 
[lkml]   [2000]   [Aug]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Lockup in 2.4.0-test7
This is probably unrelated, but I have an SMP system here as well with an
Adaptec card using the aic7xxx driver. Awhile back, I had this driver
compiled as a module (primary drives are IDE - right now, the SCSI card is
there for a cd burner). ~50% of the time when I loaded the module (the
longer I waited after boot the more likely it was to happen), the system
would completely lock up.

The card was pulled out of a single cpu system - it worked great there.

This problem *appears* to have gone away with the driver compiled into the
kernel - haven't tried making it a module again recently. I think the
last time I tried this was at 2.2.14.

As I said, it's probably unrelated, but I thought it interesting that you
were experiencing lockups on a SMP box with that driver loaded...


On Sat, 26 Aug 2000, Roland Orre wrote:

> Since I tried to upgrade to 2.2.17 (pre6) from the rock stable 2.2.12
> on two of my SMP systems (ASUS PL97DS and P2B-DS, both PII 512Mb,Scsi)
> I've got lockup problems, which have made 2.2.17 unusable for me so
> I continued to run 2.2.12 for work. I've not yet checked the kernels
> in between but tried with the later 2.4.0-test kernels instead.
> I had problems catching these rare lockups in 2.2.17 (about once a
> normal work day) but now in the later test kernels they show up much
> quicker and are also very much easier to catch thanks to the NMI watchdog
> in comb with a serial console. The problem is also very easy reproducable
> in the later 2.4.0-test kernels. All I have to do is to boot the system
> and move the mouse (PS2, alone on irq 12) quickly back and forth a couple
> of times. I don't need to start X. Of course I can't be sure that the
> lockup problem is the same in 2.2.17pre6 and 2.4.0-test* but each time
> I've got the lockup in 2.2.17 it has been after a mouse move.
>
> I provide the kernel message (looks almost identical each time)
> together with it's decoding by ksymoops. I also provide /proc/interrupts.
>
> As I'm not sure if this problem is related to SMP or not I CC this
> message to linux-smp too. I've got one similar lockup, after mouse move,
> with 2.2.17pre6 on my laptop too but I've not been able to install
> 2.4.0-test* there due to not being able to compile the pcmcia package
> (3.1.19) in the 2.4.0-test* environment.
>
> suggestion:
> I think it would be nice if it was possible to add an automatic
> disk sync, in cases it is still possible, after the console message
> from the nmi-watchdog. It's very annoying with these lengthy disk
> checks after each reboot on large hard disks.
>
> Best regards
> Roland Orre
>
>
> ksymoops 2.3.4 on i686 2.4.0-test7. Options used
> -V (default)
> -k /proc/ksyms (default)
> -l /proc/modules (default)
> -o /lib/modules/2.4.0-test7/ (default)
> -m /boot/System.map-2.4.0-test7 (default)
>
> Reading Oops report from the terminal
>
> NMI Watchdog detected LOCKUP on CPU1, registers:
> CPU: 1
> EIP: 0010:[<c02205a3>]
> EFLAGS: 00000086
> NMI Watchdog detected LOCKUP on CPU1, registers:
> CPU: 1
> EIP: 0010:[<c02205a3>]
> Using defaults from ksymoops -t elf32-i386 -a i386
> eax: c1833000 ebx: 00000046 ecx: dfff60aa edx: dfff7f80
> esi: 00002710 edi: 0000000c ebp: 00000001 esp: dfff7f14
> ds: 0018 es: 0018 ss: 0018
> Process swapper (pid: 0, stackpage=dfff7000)
> Stack: 00000235 c019a845 000000f4 00000202 04000001 00000001 c019a977 df2cb7c0
> c010a88f 0000000c c1833000 dfff7f80 c02b2980 df2cb7c0 00000180 dfff7f78
> c010aaa9 0000000c dfff7f80 df2cb7c0 c01071ac dfff6000 00000000 0000000c
> Call Trace: [<c019a845>] [<c019a977>] [<c010a88f>] [<c010aaa9>] [<c01071ac>] [<c0109084>] [<c01071ac>]
> [<c01071d9>] [<c0107241>] [<c010aaf2>] [<c0109084>]
> Code: f3 90 7e f5 e9 64 a5 f7 ff 80 3d 9c 79 27 c0 00 f3 90 7e f5
> console shuts up ...
> EFLAGS: 00000086
> eax: c1833000 ebx: 00000046 ecx: dfff60aa edx: dfff7f80
> esi: 00002710 edi: 0000000c ebp: 00000001 esp: dfff7f14
> ds: 0018 es: 0018 ss: 0018
> Process swapper (pid: 0, stackpage=dfff7000)
> Stack: 00000235 c019a845 000000f4 00000202 04000001 00000001 c019a977 df2cb7c0
> c010a88f 0000000c c1833000 dfff7f80 c02b2980 df2cb7c0 00000180 dfff7f78
> c010aaa9 0000000c dfff7f80 df2cb7c0 c01071ac dfff6000 00000000 0000000c
> Call Trace: [<c019a845>] [<c019a977>] [<c010a88f>] [<c010aaa9>] [<c01071ac>] [<c0109084>] [<c01071ac>]
> [<c01071d9>] [<c0107241>] [<c010aaf2>] [<c0109084>]
> Code: f3 90 7e f5 e9 64 a5 f7 ff 80 3d 9c 79 27 c0 00 f3 90 7e f5
>
> >>EIP; c02205a3 <stext_lock+3c13/7a48> <=====
> Trace; c019a845 <handle_kbd_event+75/188>
> Trace; c019a977 <keyboard_interrupt+1f/2c>
> Trace; c010a88f <handle_IRQ_event+4b/7c>
> Trace; c010aaa9 <do_IRQ+89/e0>
> Trace; c01071ac <default_idle+0/34>
> Trace; c0109084 <ret_from_intr+0/20>
> Trace; c01071ac <default_idle+0/34>
> Trace; c01071d9 <default_idle+2d/34>
> Trace; c0107241 <cpu_idle+3d/4c>
> Trace; c010aaf2 <do_IRQ+d2/e0>
> Trace; c0109084 <ret_from_intr+0/20>
> Code; c02205a3 <stext_lock+3c13/7a48>
> 00000000 <_EIP>:
> Code; c02205a3 <stext_lock+3c13/7a48> <=====
> 0: f3 90 repz nop <=====
> Code; c02205a5 <stext_lock+3c15/7a48>
> 2: 7e f5 jle fffffff9 <_EIP+0xfffffff9> c022059c <stext_lock+3c0c/7a48>
> Code; c02205a7 <stext_lock+3c17/7a48>
> 4: e9 64 a5 f7 ff jmp fff7a56d <_EIP+0xfff7a56d> c019ab10 <aux_write_ack+4/3c>
> Code; c02205ac <stext_lock+3c1c/7a48>
> 9: 80 3d 9c 79 27 c0 00 cmpb $0x0,0xc027799c
> Code; c02205b3 <stext_lock+3c23/7a48>
> 10: f3 90 repz nop
> Code; c02205b5 <stext_lock+3c25/7a48>
> 12: 7e f5 jle 9 <_EIP+0x9> c02205ac <stext_lock+3c1c/7a48>
>
>
> Output from /proc/interrupts (no sound playing)
>
> CPU0 CPU1
> 0: 49913 43540 IO-APIC-edge timer
> 1: 24 11 IO-APIC-edge keyboard
> 2: 0 0 XT-PIC cascade
> 5: 86612 86954 IO-APIC-level aic7xxx, EMU10K1
> 10: 1389 1345 IO-APIC-level eth0
> 12: 0 0 IO-APIC-edge PS/2 Mouse
> 13: 1 0 XT-PIC fpu
> NMI: 93280 93280
> LOC: 92973 93182
> ERR: 0
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:38    [W:0.027 / U:15.032 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site