[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#327115: marked as done (Floppy unexpected interrupt)

Your message dated Sat, 25 Jul 2009 11:32:12 +0200
with message-id <20090725093212.GA14160@galadriel.inutil.org>
and subject line Re: Bug#327115: Floppy unexpected interrupt
has caused the Debian Bug report #327115,
regarding Floppy unexpected interrupt
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
327115: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=327115
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: Kernel
Version: any

Dear Sirs,
I tried out your distro on a laptop PC (Pentium III 900MHz); it is not a brand PC, it is a Nev@ada PC, thus it is quite easy for me to have trouble installing GNU/Linux on it, so that till now the only distro that has been acceptable has been Slackware (both 9.1 and 10.1). Recently, I decided to try also Debian because it appeared very impressive (in the positive sense) to me, but I had a bad surprise which I didn't find with Slackware instead: when I mount the floppy drive I continuously receive the message: "Floppy unexpected interrupt" together with some other strange indication like "sensei repl[80]". To try to solve this problem I put the parameter "floppy=thinkpad" (even if it is not a thinkpad) in the kernel options in GRUB, but without any success; after that I tried the kernel parameter "floppy=no_unexpected_interrupts" and even then I had no result at all. Please, can you suggest to me a solution of any kind to this problem? Take note that the kernel installed is the one obtained specifying linux26 at the installation boot prompt; the problem arised also with linux24 choosen at boot time at the beginning of the installation. 

Thank you a lot and many congratulation: Debian is really great!

Luca "Killer Fish" PERSICO

--- End Message ---
--- Begin Message --- 
On Fri, Dec 26, 2008 at 08:52:26PM +0100, Moritz Muehlenhoff wrote:
> reassign 327115 linux-2.6
> thanks
> 
> 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?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz

--- End Message ---
Reply to: