Launchpad has imported 5 comments from the remote bug at https://bugzilla.kernel.org/show_bug.cgi?id=43120.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2012-04-18T15:59:18+00:00 ticmanis wrote: The floppy disk drive's motor keeps running forever as soon as the floppy is accessed (say, by doing a "mdir a:" or a "fdformat /dev/fd0", or a "dd if=/dev/fd0 ..." ), and the floppy drive's activity LED stays lit. Only when the disk is removed from the drive, the drive stops. I'd expect the drive to stop spinning a few seconds after the access is finished. The accessing command returns normally and I can still access the drive normally by giving another command afterwards. The problem is purely the failure to deselect the drive and/or turn off the drive motor line. This is a standard IRQ6/DMA2 floppy drive connected directly to the motherboard's built in FDC with a standard 34-wire ribbon floppy cable. The bug happens both with a normal 1.44MB drive and with a 1.2MB (5.25 inch) drive. The drives do not exhibit this problem in DOS or Windows running on the same physical hardware. My motherboard is an ASUS P5B, if that is important. There was no second drive connected as my motherboard supports only one floppy. The bug first occured after upgrading my Ubuntu system to Ubuntu Precise (12.04) Beta 2, but I have tested with a mainline 3.4.0-rc3 kernel (though with Ubuntu specific configuration) which I got from here: http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc3-precise/ The specific package I tested with was called "linux- image-3.4.0-030400rc3-generic_3.4.0-030400rc3.201204152235_amd64.deb" The bug was still there in that mainline kernel. I hope this is the right subsystem for this bug, if not please feel free to move it and/or to point out where it should go. This is the first kernel bug I'm reporting upstream so please excuse me if some vital information is missing. Please just tell me what more info you need. Thanks! My original Ubuntu bug report can be found here: https://bugs.launchpad.net/bugs/983681 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/6 ------------------------------------------------------------------------ On 2012-04-18T16:02:38+00:00 ticmanis wrote: The kernel where I first noticed the bug is the Ubuntu specific 3.2.0. Currently "uname -a" gives "Linux linards 3.2.0-23-generic #36-Ubuntu SMP Tue Apr 10 20:39:51 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux". Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/7 ------------------------------------------------------------------------ On 2017-03-06T20:29:51+00:00 szg0000 wrote: Please try to reproduce this bug with latest kernel image. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/12 ------------------------------------------------------------------------ On 2019-02-14T09:29:09+00:00 corti wrote: The problem still persists. I've tried kernel 4.19.16 from Debian testing. The bug somehow lies in the logic for detecting a disk change. If I access the floppy the motor won't turn off. But if I force a disk change (ejecting and immediately inserting the floppy again) the motor turns off within about two seconds - as it should. Also, if I practically disable the disk change checks with "floppycontrol -C 2147483647" the motor turns off normally. So I suspect that frequently checking for disk changes without the floppy being changed keeps the motor in its current state. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/13 ------------------------------------------------------------------------ On 2019-02-14T10:52:18+00:00 corti wrote: Created attachment 281133 kernel messages The following kernel messages are repeated every two seconds (after which the motor should be turned off) when loading the module with floppy=debug Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/983681/comments/14 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/983681 Title: Floppy keeps running forever after every access Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Bug description: In Ubuntu Precise, the floppy disk drive's motor keeps running forever as soon as the floppy is accessed (say, by doing a "mdir a:" or a "fdformat /dev/fd0", or a "dd if=/dev/fd0 ..." ), and the floppy drive's activity LED stays lit. Only when the disk is removed from the drive, the drive stops. I'd expect the drive to stop spinning a few seconds after the access is finished. The accessing command returns normally and I can still access the drive normally by giving another command afterwards. The problem is purely the failure to deselect the drive and/or turn off the drive motor line. This is a standard IRQ6/DMA2 floppy drive connected directly to the motherboard's built in FDC with a standard 34-wire ribbon floppy cable. The bug happens both with a normal 1.44MB drive and with a 1.2MB (5.25 inch) drive. The drives do not exhibit this problem in DOS or Windows running on the same physical hardware, and I do not remember having this problem in Oneiric either. If you need more info on my system than the automatically generated attachments provide, please ask. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-image-3.2.0-23-generic 3.2.0-23.36 ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14 Uname: Linux 3.2.0-23-generic x86_64 NonfreeKernelModules: nvidia AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 2.0.1-0ubuntu4 Architecture: amd64 ArecordDevices: **** List of CAPTURE Hardware Devices **** card 0: XFi [Creative X-Fi], device 0: ctxfi [Front/WaveIn] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: linards 1855 F.... pulseaudio CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Card0.Amixer.info: Card hw:0 'XFi'/'Creative X-Fi 20K2 SB0880' Mixer name : '20K2' Components : '' Controls : 27 Simple ctrls : 10 Date: Tue Apr 17 07:40:17 2012 HibernationDevice: RESUME=UUID=e00a04d9-b055-49bd-a504-bba24c74df32 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012) IwConfig: lo no wireless extensions. teredo no wireless extensions. eth0 no wireless extensions. MachineType: System manufacturer System Product Name ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-23-generic root=UUID=efe722f2-6b46-4b17-90a8-889d655827be ro quiet gfxpayload=text nomodeset quiet gfxpayload=text nomodeset RelatedPackageVersions: linux-restricted-modules-3.2.0-23-generic N/A linux-backports-modules-3.2.0-23-generic N/A linux-firmware 1.79 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to precise on 2012-03-30 (17 days ago) dmi.bios.date: 03/09/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2104 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5B dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2104:bd03/09/2009:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5B:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/983681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
