Bug 14174 - floppy drive not usable more than one time after reboot - kernel panic with active DVB
Summary: floppy drive not usable more than one time after reboot - kernel panic with a...
Status: RESOLVED CODE_FIX
Alias: None
Product: IO/Storage
Classification: Unclassified
Component: Other (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: Brandon Philips
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-13 15:08 UTC by Alexander Koenig
Modified: 2010-01-04 22:58 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.27.29-0.1-vanilla x86_64 SMP
Subsystem:
Regression: No
Bisected commit-id:


Attachments
kernel panic after floppy usage - longer dump (52 bytes, text/plain)
2009-09-13 15:11 UTC, Alexander Koenig
Details
kernel panic after floppy usage (mdir) (52 bytes, text/plain)
2009-09-13 15:13 UTC, Alexander Koenig
Details

Description Alexander Koenig 2009-09-13 15:08:19 UTC
This bug report is afollow-up of my report already posted in the OPENSuse bugzilla at https://bugzilla.novell.com/show_bug.cgi?id=421732
You can find detailed information of my hardware and software configuration there.

Short System description:
- CPU:             AMD Phenom X4 9550 4x2.2GHz (95W) 65nm Quad Core
- Memory:          4GB - 2x2048MB DDR2-800 CL5, Dual Channel 2x1024MB
- Motherboard:     GIGABYTE GA-MA770-DS3
- Graphics         NVidia GeForce 7300 GS, 256MB, TV-Out, DVI, PCIe
- Floppy:          1.44MB
- 1. hard disk:    500GB Seagate 7200 RPM SATA II
- 2. hard disk:    500GB Seagate 7200 RPM SATA II
- DVD-ROM:         Optiarc DDU 1615 16x/48x, IDE
- DVD-RW:          NEC AD-7200, IDE
- SCSI-Controller: Adaptec 2940 SCSI adapter,            SCSI ID: 7
- DVB controller:  Technotrend/Hauppauge DVB card rev2.1

Symptoms:
The first command to the floppy drive after re-boot seems to work, all
subsequent access to the floppy drive - with the same disk or with any other -
fail (floppy LED is on, floppy drive moves, but no positive result). See log of
a terminal session below:

alexande@asterix:~> mdir
 Volume in drive A has no label
 Volume Serial Number is 2828-50E1
Directory for A:/

autoexec bat      1142 1998-05-15  20:01  autoexec.bat
setramd  bat       881 1998-05-15  20:01  setramd.bat
findramd exe      6855 1998-05-15  20:01  findramd.exe
aspi4dos sys     14386 1998-05-15  20:01  aspi4dos.sys
aspicd   sys     29620 1998-05-15  20:01  aspicd.sys
aspi2dos sys     35330 1998-05-15  20:01  aspi2dos.sys
aspi8u2  sys     40792 1998-05-15  20:01  aspi8u2.sys
extract  exe     93242 1998-05-15  20:01  extract.exe
drvspace bin     69079 1998-05-15  20:01  drvspace.bin
himem    sys     33447 1998-05-15  20:01  himem.sys
ebd      cab    276324 1998-05-15  20:01  ebd.cab
country  sys     30742 1998-05-15  20:01  country.sys
mode     com     29815 1998-05-15  20:01  mode.com
keyb     com     20023 1998-05-15  20:01  keyb.com
ebd      sys         0 2000-01-08  10:09  ebd.sys
io       sys    222390 1998-05-15  20:01  io.sys
config   sys       860 2003-11-16   0:26  config.sys
readme   txt     16216 1998-05-15  20:01  readme.txt
ramdrive sys     12823 1998-05-15  20:01  ramdrive.sys
btcdrom  sys     21971 1998-05-15  20:01  btcdrom.sys
btdosm   sys     30955 1998-05-15  20:01  btdosm.sys
aspi8dos sys     37564 1998-05-15  20:01  aspi8dos.sys
flashpt  sys     64425 1998-05-15  20:01  flashpt.sys
fdisk    exe     64956 1998-05-15  20:01  fdisk.exe
command  com     96360 1998-05-15  20:01  command.com
oakcdrom sys     41302 1998-05-15  20:01  oakcdrom.sys
display  sys     17191 1998-05-15  20:01  display.sys
ega      cpi     58870 1998-05-15  20:01  ega.cpi
keyboard sys     34566 1998-05-15  20:01  keyboard.sys
msdos    sys         9 2000-01-08  10:09  msdos.sys
toshv224 sys     13720 2003-11-16   0:24  toshv224.sys
       31 files           1 415 856 bytes
                             33 792 bytes free

alexande@asterix:~> mdir
init A: non DOS media
Cannot initialize 'A:'
alexande@asterix:~> mdir
init A: non DOS media
Cannot initialize 'A:'
alexande@asterix:~> mount /media/floppy
mount: blockorientiertes Gerät /dev/fd0 ist schreibgeschützt, wird eingehängt
im Nur-Lese-Modus
mount: konnte Dateisystemtyp nicht feststellen, und es wurde keiner angegeben
---> floppy removed from drive <---
alexande@asterix:~> mount /media/floppy  
mount: /dev/fd0 ist kein gültiges blockorientiertes Gerät
 ---> inserted another floppy into the drive <---
alexande@asterix:~> mount /media/floppy
mount: blockorientiertes Gerät /dev/fd0 ist schreibgeschützt, wird eingehängt
im Nur-Lese-Modus
mount: konnte Dateisystemtyp nicht feststellen, und es wurde keiner angegeben
 ---> removed floppy from drive <---
alexande@asterix:~> mdir
Can't open /dev/fd0: No such device or address
Cannot initialize 'A:'
 ---> inserted floppy into drive <---
alexande@asterix:~> mdir
init A: non DOS media
Cannot initialize 'A:'
alexande@asterix:~> mdir
init A: non DOS media
Cannot initialize 'A:'
alexande@asterix:~> 

All disks used for these experiments (Windows 98 installation boot disk, SuSE
Linux 8.1 boot disk) work perfectly on a openSUSE 10.3 32bit system.

Both disks work as boot disks on my 64 bit system, the Windows boot disk boots
into DOS, where all file commands work on the floppy.


The above behavior is the same with the SUSE kernel and the vanilla kernel, if the drivers for my DVB card (Technotrend/Hauppauge DVB card rev2.1) are not active. With the SUSE kernel no obvious change with active DVB. 

With the vanilla kernel, however, 9 of 10 attempts to use the floppy (mdir command) lead to a "General protection fault" and "Kernel panic" if DVB is active (see attachments).
Comment 1 Alexander Koenig 2009-09-13 15:11:48 UTC
Created attachment 23088 [details]
kernel panic after floppy usage - longer dump
Comment 2 Alexander Koenig 2009-09-13 15:13:26 UTC
Created attachment 23089 [details]
kernel panic after floppy usage (mdir)
Comment 3 Andrew Morton 2009-09-14 22:14:02 UTC
(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Sun, 13 Sep 2009 15:08:21 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:

> http://bugzilla.kernel.org/show_bug.cgi?id=14174
> 
>            Summary: floppy drive not usable more than one time after
>                     reboot - kernel panic with active DVB
>            Product: IO/Storage
>            Version: 2.5
>     Kernel Version: 2.6.27.29-0.1-vanilla x86_64 SMP
>           Platform: All
>         OS/Version: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: Other
>         AssignedTo: io_other@kernel-bugs.osdl.org
>         ReportedBy: alexander.koenig@koenig-a.de
>         Regression: No
> 
> 
> This bug report is afollow-up of my report already posted in the OPENSuse
> bugzilla at https://bugzilla.novell.com/show_bug.cgi?id=421732
> You can find detailed information of my hardware and software configuration
> there.
> 
> Short System description:
> - CPU:             AMD Phenom X4 9550 4x2.2GHz (95W) 65nm Quad Core
> - Memory:          4GB - 2x2048MB DDR2-800 CL5, Dual Channel 2x1024MB
> - Motherboard:     GIGABYTE GA-MA770-DS3
> - Graphics         NVidia GeForce 7300 GS, 256MB, TV-Out, DVI, PCIe
> - Floppy:          1.44MB
> - 1. hard disk:    500GB Seagate 7200 RPM SATA II
> - 2. hard disk:    500GB Seagate 7200 RPM SATA II
> - DVD-ROM:         Optiarc DDU 1615 16x/48x, IDE
> - DVD-RW:          NEC AD-7200, IDE
> - SCSI-Controller: Adaptec 2940 SCSI adapter,            SCSI ID: 7
> - DVB controller:  Technotrend/Hauppauge DVB card rev2.1
> 
> Symptoms:
> The first command to the floppy drive after re-boot seems to work, all
> subsequent access to the floppy drive - with the same disk or with any other
> -
> fail (floppy LED is on, floppy drive moves, but no positive result). See log
> of
> a terminal session below:
> 
> alexande@asterix:~> mdir
>  Volume in drive A has no label
>  Volume Serial Number is 2828-50E1
> Directory for A:/
> 
> autoexec bat      1142 1998-05-15  20:01  autoexec.bat
> setramd  bat       881 1998-05-15  20:01  setramd.bat
> findramd exe      6855 1998-05-15  20:01  findramd.exe
> aspi4dos sys     14386 1998-05-15  20:01  aspi4dos.sys
> aspicd   sys     29620 1998-05-15  20:01  aspicd.sys
> aspi2dos sys     35330 1998-05-15  20:01  aspi2dos.sys
> aspi8u2  sys     40792 1998-05-15  20:01  aspi8u2.sys
> extract  exe     93242 1998-05-15  20:01  extract.exe
> drvspace bin     69079 1998-05-15  20:01  drvspace.bin
> himem    sys     33447 1998-05-15  20:01  himem.sys
> ebd      cab    276324 1998-05-15  20:01  ebd.cab
> country  sys     30742 1998-05-15  20:01  country.sys
> mode     com     29815 1998-05-15  20:01  mode.com
> keyb     com     20023 1998-05-15  20:01  keyb.com
> ebd      sys         0 2000-01-08  10:09  ebd.sys
> io       sys    222390 1998-05-15  20:01  io.sys
> config   sys       860 2003-11-16   0:26  config.sys
> readme   txt     16216 1998-05-15  20:01  readme.txt
> ramdrive sys     12823 1998-05-15  20:01  ramdrive.sys
> btcdrom  sys     21971 1998-05-15  20:01  btcdrom.sys
> btdosm   sys     30955 1998-05-15  20:01  btdosm.sys
> aspi8dos sys     37564 1998-05-15  20:01  aspi8dos.sys
> flashpt  sys     64425 1998-05-15  20:01  flashpt.sys
> fdisk    exe     64956 1998-05-15  20:01  fdisk.exe
> command  com     96360 1998-05-15  20:01  command.com
> oakcdrom sys     41302 1998-05-15  20:01  oakcdrom.sys
> display  sys     17191 1998-05-15  20:01  display.sys
> ega      cpi     58870 1998-05-15  20:01  ega.cpi
> keyboard sys     34566 1998-05-15  20:01  keyboard.sys
> msdos    sys         9 2000-01-08  10:09  msdos.sys
> toshv224 sys     13720 2003-11-16   0:24  toshv224.sys
>        31 files           1 415 856 bytes
>                              33 792 bytes free
> 
> alexande@asterix:~> mdir
> init A: non DOS media
> Cannot initialize 'A:'
> alexande@asterix:~> mdir
> init A: non DOS media
> Cannot initialize 'A:'
> alexande@asterix:~> mount /media/floppy
> mount: blockorientiertes Ger__t /dev/fd0 ist schreibgesch__tzt, wird
> eingeh__ngt
> im Nur-Lese-Modus
> mount: konnte Dateisystemtyp nicht feststellen, und es wurde keiner angegeben
> ---> floppy removed from drive <---
> alexande@asterix:~> mount /media/floppy  
> mount: /dev/fd0 ist kein g__ltiges blockorientiertes Ger__t
>  ---> inserted another floppy into the drive <---
> alexande@asterix:~> mount /media/floppy
> mount: blockorientiertes Ger__t /dev/fd0 ist schreibgesch__tzt, wird
> eingeh__ngt
> im Nur-Lese-Modus
> mount: konnte Dateisystemtyp nicht feststellen, und es wurde keiner angegeben
>  ---> removed floppy from drive <---
> alexande@asterix:~> mdir
> Can't open /dev/fd0: No such device or address
> Cannot initialize 'A:'
>  ---> inserted floppy into drive <---
> alexande@asterix:~> mdir
> init A: non DOS media
> Cannot initialize 'A:'
> alexande@asterix:~> mdir
> init A: non DOS media
> Cannot initialize 'A:'
> alexande@asterix:~> 
> 
> All disks used for these experiments (Windows 98 installation boot disk, SuSE
> Linux 8.1 boot disk) work perfectly on a openSUSE 10.3 32bit system.
> 
> Both disks work as boot disks on my 64 bit system, the Windows boot disk
> boots
> into DOS, where all file commands work on the floppy.
> 
> 
> The above behavior is the same with the SUSE kernel and the vanilla kernel,
> if
> the drivers for my DVB card (Technotrend/Hauppauge DVB card rev2.1) are not
> active. With the SUSE kernel no obvious change with active DVB. 
> 
> With the vanilla kernel, however, 9 of 10 attempts to use the floppy (mdir
> command) lead to a "General protection fault" and "Kernel panic" if DVB is
> active (see attachments).
> 

hm, hard.

Dunno about the floppy problem but this photo you took:
https://bugzillafiles.novell.org/attachment.cgi?id=318005
shows a good solid oops in dvb_dmx_memcopy().

However that's just a memcpy(), and we have no info about who called it.
Comment 4 Mauro Carvalho Chehab 2009-09-14 23:24:05 UTC
Em Mon, 14 Sep 2009 15:13:40 -0700
Andrew Morton <akpm@linux-foundation.org> escreveu:

> Dunno about the floppy problem but this photo you took:
> https://bugzillafiles.novell.org/attachment.cgi?id=318005
> shows a good solid oops in dvb_dmx_memcopy().

I suspect that this is a bug caused by the lack of a memory barrier,
already corrected by dda06a8e4610757def753ee3a541a0b1a1feb36b.
Comment 5 Alexander Koenig 2009-12-31 16:59:22 UTC
The problem is no longer reproducible after I installed openSUSE 11.2:
uname -a
Linux asterix 2.6.31.5-0.1-desktop #1 SMP PREEMPT 2009-10-26 15:49:03 +0100 x86_64 x86_64 x86_64 GNU/Linux

I also tried with the latest 2.6.32 vanilla kernel - problem has  disappeared as well.
Comment 6 Brandon Philips 2010-01-04 22:58:46 UTC
Fixed.

Note You need to log in before you can comment on or make changes to this bug.