lkml.org 
[lkml]   [1999]   [Mar]   [21]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectMore SCSI modules in RAM disk
Hello module gurus,

I have been having problems including the SCSI module, scsi_mod.o,
into a boot RAM disk image.

As advised, I used the --preload keyword to Red Hat's mkinitrd to load
the scsi_mod module first.

The machine booted fine. However, the (unrelated) floppy disk would
not work anymore!

`od /dev/fd0` produces these log entries, unstoppable, and ultimately
fatal.

Mar 21 10:14:23 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:23 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:14:25 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:25 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:14:26 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:26 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:14:26 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:26 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:14:27 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:27 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:14:27 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:27 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:14:27 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:27 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:14:28 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:28 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:14:28 skunkworks kernel: floppy0: unexpected interrupt
Mar 21 10:14:28 skunkworks kernel: floppy0: sensei repl[0]=80
Mar 21 10:17:01 skunkworks init: Switching to runlevel: 6
Mar 21 10:17:09 skunkworks named[260]: named shutting down

There does not seem to be any evidence that an interrupt is being
used for the floppy. I know that there is one being used and I
know the only one that could be used because it is hardwired (IRQ6).
However, it doesn't show anywhere.


/proc/interrupts

CPU0 CPU1
0: 12569 12042 IO-APIC-edge timer
1: 844 1009 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
10: 1779 1783 IO-APIC-level aic7xxx, aic7xxx
11: 86 70 IO-APIC-level Intel EtherExpress Pro 10/100 Ethernet
13: 1 0 XT-PIC fpu
NMI: 0
ERR: 0


Also, the I/O range used by the floppy 0x3f0-0x3f7, is not shown either.

/proc/ioports

0000-001f : dma1
0020-003f : pic1
0040-005f : timer
0060-006f : keyboard
0080-008f : dma page reg
00a0-00bf : pic2
00c0-00df : dma2
00f0-00ff : fpu
02f8-02ff : serial(auto)
03c0-03df : vga+
03f8-03ff : serial(auto)
e400-e4be : aic7xxx
e800-e8be : aic7xxx
ef40-ef5f : Intel Speedo3 Ethernet

If these are now dynamic (like serial I/O), and allocated only when the
floppy is opened, I don't know why. A floppy controller will never be
hot-swappable. This sure makes debugging difficult.


Cheers,
Dick Johnson
***** FILE SYSTEM WAS MODIFIED *****
Penguin : Linux version 2.2.3 on an i686 machine (400.59 BogoMips).
Warning : It's hard to remain at the trailing edge of technology.


-
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/

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