lkml.org 
[lkml]   [1998]   [Jan]   [27]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectScheduling in interrupt in 2.1.8x
  Hi, all. I've found that 2.1.8x sometimes gives "Scheduling in
interrupt" messages. I have two similar machines (dual PPro/180).

Machine A: one IDE drive and two WIDE SCSI drives. On this machine I
get "Scheduling in interrupt" messages for 2.1.81-SMP and 2.1.82-SMP,
always in the same place. However, 2.1.82-UP works OK.

Machine B: 4 narrow SCSI drives. This has no problems with
2.1.81-SMP.

Although I can't show kernel logs for the failure mode (since the root
FS is not even mounted, let alone syslogd running), I can show you the
kernel logs for 2.1.82-UP around the place the failure happens:

Console: 8 point font, 400 scans
Console: colour VGA+ 80x50, 1 virtual console (max 63)
PCI: BIOS32 Service Directory structure at 0xc00fdb70
PCI: BIOS32 Service Directory entry at 0xfdb80
PCI: PCI BIOS revision 2.10 entry at 0xfdba1
Probing PCI hardware.
Calibrating delay loop... 179.40 BogoMIPS
Memory: 192976k/196608k available (688k kernel code, 392k reserved, 2508k data, 44k init)
Swansea University Computer Society NET3.039 for Linux 2.1
NET3: Unix domain sockets 0.16 for Linux NET3.038.
Swansea University Computer Society TCP/IP for NET3.037
IP Protocols: ICMP, UDP, TCP
CPU: Intel Pentium Pro stepping 07
Checking 386/387 coupling... Ok, fpu using exception 16 error reporting.
Checking 'hlt' instruction... Ok.
POSIX conformance testing by UNIFIX
Starting kswapd v 1.23
Serial driver version 4.24 with SHARE_IRQ enabled
ttyS00 at 0x03f8 (irq = 4) is a 16550A
ttyS02 at 0x03e8 (irq = 4) is a 16550A
Real Time Clock Driver v1.07
Ramdisk driver initialized : 16 ramdisks of 4096K size
PIIX3: IDE controller on PCI bus 0 function 57
PIIX3: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xffa0-0xffa7, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xffa8-0xffaf, BIOS settings: hdc:pio, hdd:pio
hda: FUJITSU M1636TAU, ATA DISK drive
ide2: ports already in use, skipping probe
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
hda: FUJITSU M1636TAU, 1226MB w/128kB Cache, CHS=622/64/63, DMA
ncr53c8xx: at PCI bus 0, device 20, function 0
ncr53c8xx: 53c875 detected
ncr53c875-0: rev=0x03, base=0xfebfff00, io_port=0xec00, irq=10
ncr53c875-0: NCR clock is 40218KHz, 40037KHz
ncr53c875-0: ID 7, Fast-20, Parity Checking
ncr53c875-0: on-board RAM at 0xfebfe000
ncr53c875-0: restart (scsi reset).
ncr53c875-0: copying script fragments into the on-board RAM ...
scsi0 : ncr53c8xx - revision 2.5f
scsi : 1 host.
Scheduling in interrupt
ncr53c875-0-<0,0>: using tagged command queueing, up to 4 cmds/lun

Yes, that's right, I get one more line of output after the "Scheduling
in interrupt" message before the system freezes. If everything was
working properly, the following boot messages would appear:

Vendor: SEAGATE Model: ST32171W Rev: 0338
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk c0b0t0u0 at scsi0, channel 0, id 0, lun 0
ncr53c875-0-<1,0>: using tagged command queueing, up to 4 cmds/lun
Vendor: SEAGATE Model: ST32171W Rev: 0338
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk c0b0t1u0 at scsi0, channel 0, id 1, lun 0
scsi : detected 2 SCSI disks total.
ncr53c875-0-<0,0>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
SCSI device sda: hdwr sector= 512 bytes. Sectors= 4222640 [2061 MB] [2.1 GB]
ncr53c875-0-<1,0>: FAST-20 WIDE SCSI 40.0 MB/s (50 ns, offset 15)
SCSI device sdb: hdwr sector= 512 bytes. Sectors= 4222640 [2061 MB] [2.1 GB]
Partition check:

and so on. So, anyone have any ideas? Patches to try?

Regards,

Richard....

\
 
 \ /
  Last update: 2005-03-22 13:41    [W:0.029 / U:0.444 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site