Ronald,
You missed out the most important detail : kernel version.
Anyway, I wouldnt know the answer to your question. But I seem to
recall that a bug in the interrupt handling code had been found and fixed
recently. Try looking through the archives of the linux-kernel mailing
list at http://www.tux.org (there is a link to the archives on that page).
As regards your dmesg problem, a simple solution is <Shift+PgUp>
and <Shift+PgDn>.
Regards,
Kenneth
There is no such thing as luck. 'Luck' is nothing but an absence of bad luck.
On Sat, 2 Jan 1999, Ronald V. Vazquez wrote:
> Hello everybody:
>
> My box have been dead for two days and just got it up today. This has
> been a little of a battle! Just when I configured my network, my
> printer was spitting pages with text on them, I decided to setup my
> external Zip (with Zip Zoom card) drive again. Well, startup would go
> fine and after mounting the hard drive I would get this message:
>
> Aiee: scheduling in interrupt 00127811
> Aiee: scheduling in interrupt 00127811
> Aiee: scheduling in interrupt 00127811
> etc...
>
> This would just keep going indefinitely until I turned off the machine.
> Has anybody seen this? It only happens when I make the Zip drive entry
> on the fstab.
>
> My specs:
>
> Asus SP97-V
> AMD 200 MHz
> WD 5.1 GIG
> 64 MB EDO RAM
> 24X CD ROM
> Diamond Viper 330
> Sound Blaster AWE 64 Value
> Lynksys EtherFast 100
> Zip Zoom Card
> External SCSI Zip
> Pro View 900 (19")
> DeskJet 500
>
> Is there a way to capture a screen dump into a file? When I dmesg I
> can't read the screen fast enough. Where does everything goes? Thanks
> a lot, Ronald.
>
>
