FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.

» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Kernel

LinkBack Thread Tools
Old 12-26-2008, 06:52 PM
Moritz Muehlenhoff
Default Bug#327115: Floppy unexpected interrupt

reassign 327115 linux-2.6

On Sat, Sep 17, 2005 at 09:41:46PM +0200, Luca PERSICO wrote:
> Hi Maks!
> I am back to you with some news, but first of all many thanks for your
> attention.
> As I told you, my laptop is a Nev@da, more precisely a CLEVO 2700S with
> a BIOS SystemSoft MobilePRO Version 1.01 - R1.14 and a Pentium III
> Coppermine at 900MHz; it is not a recent one, but I do not think this
> should be a problem.
> I receive the error message only when the floppy is mounted, the text of
> the message is always the same:
> floppy0: unexpected interrupt
> floppy0: sensei repl[0]=80
> The message arises from now to then, sometimes very often, sometimes
> less often, apparently without a specific reason or cause. Please would
> you note also that I had the same behaviour on that PC even when I
> installed Red HAT from 7.3 on and Fedora Core 1 and 3.
> I have also some news about Slackware. I went back to Slack 9.1 on that
> PC, so the trials I made have been carried out with that distribution.
> Even if I did not specify any kernel parameter for the floppy on the
> kernel line for the boot, I am able to use it without any problem at
> all. Nevertheless, having decided to give you also the results from
> dmesg in Slackware, I have seen something that could be interesting for
> you; if I give dmesg command before I mount the floppy the result is the
> one you may see in dmesgSlackNoFD text file, if I give the same command
> after the floppy has been mounted I obtain the textfile dmesgSlack; the
> interesting part is the last one in this file, where it is possible to
> see the same error message about floppy, even if this error does not
> arise at all during the use of the PC, I mean that the only moment when
> it arises is the execution of dmesg command; the other strange thing is
> that if I repeat the dmesg command after I have unmounted the floppy,
> the dmesg command continues to report the same lines with those errors.
> Attached to this mail you may find four files: dmesg2.4 and dmesg2.6
> have been made with Debian and kernel 2.4 and 2.6 respectively;
> dmesgSlack and dmesgSlackNoFD have been made with Slackware 9.1 after
> and before the mounting of the floppy, respectively.
> Many Many thanks again for your attention and for your great work! Good
> Luck!

Does this error still occur with more recent kernel versions?


To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

Thread Tools

All times are GMT. The time now is 07:40 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org