Your message dated Fri, 25 Jun 2010 15:24:51 +0200 with message-id <201006251524.51907.mcy@lm7.fr> and subject line Close (again) #548434 has caused the Debian Bug report #548434, regarding fdformat fails completely with current kernel 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.) -- 548434: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=548434 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: fdformat fails completely with current kernel
- From: ael <law_ence.dev@ntlworld.com>
- Date: Sat, 26 Sep 2009 12:02:50 +0100
- Message-id: <20090926110250.GA16060@exact.conquest>
Subject: fdutils: fdformat fails under current kernel(s) Package: fdutils Version: 5.5-20060227-3 Justification: renders package unusable Severity: grave *** Please type your report below this line *** fdformat fails completely on current kernels. example: (retyped by hand ,so typos possible...) # setfdprm /dev/fd0 hd # getfdprm /dev/hd0 DS HD sector=18 # fdformat /dev/fd0 Double sided, 80 tracks, 18 sector/track. Total capacity 1440 kB. Formating ... done. Verifying ... Read: : Input/Output error Problem reading cyclinder 0, expected 18432, read -1 /var/log/messages reports data CRC errors:- Sep 26 11:31:03 exact kernel: [ 108.727707] floppy0: data CRC error: track 0, head 0, sector 3, size 2 Sep 26 11:32:30 exact kernel: [ 195.912529] floppy0: data CRC error: track 0, head 0, sector 1, size 2 Sep 26 11:32:30 exact kernel: [ 196.112518] floppy0: data CRC error: track 0, head 0, sector 1, size 2 Sep 26 11:32:31 exact kernel: [ 197.010847] floppy0: data CRC error: track 0, head 0, sector 10, size 2 Sep 26 11:32:32 exact kernel: [ 197.232729] floppy0: data CRC error: track 0, head 0, sector 12, size 2 Sep 26 11:32:32 exact kernel: [ 197.854571] floppy0: data CRC error: track 0, head 0, sector 14, size 2 Sep 26 11:32:34 exact kernel: [ 199.367041] floppy0: data CRC error: track 0, head 1, sector 3, size 2 Sep 26 11:32:34 exact kernel: [ 199.567047] floppy0: data CRC error: track 0, head 1, sector 3, size 2 Sep 26 11:32:34 exact kernel: [ 200.010748] floppy0: data CRC error: track 0, head 1, sector 7, size 2 Sep 26 11:32:35 exact kernel: [ 200.243533] floppy0: data CRC error: track 0, head 1, sector 10, size 2 Sep 26 11:32:36 exact kernel: [ 201.265301] floppy0: data CRC error: track 0, head 1, sector 12, size 2 Sep 26 11:32:36 exact kernel: [ 201.476236] floppy0: data CRC error: track 0, head 1, sector 13, size 2 Sep 26 11:32:37 exact kernel: [ 203.123078] floppy0: data CRC error: track 0, head 1, sector 17, size 2 Sep 26 11:32:39 exact kernel: [ 204.232240] floppy0: data CRC error: track 1, head 0, sector 3, size 2 Sep 26 11:32:40 exact kernel: [ 205.475930] floppy0: data CRC error: track 1, head 0, sector 7, size 2 Sep 26 11:32:40 exact kernel: [ 205.686864] floppy0: data CRC error: track 1, head 0, sector 8, size 2 Sep 26 11:32:41 exact kernel: [ 207.133744] floppy0: data CRC error: track 1, head 0, sector 12, size 2 Sep 26 11:32:43 exact kernel: [ 208.344612] floppy0: data CRC error: track 1, head 0, sector 13, size 2 Sep 26 11:32:43 exact kernel: [ 208.544608] floppy0: data CRC error: track 1, head 0, sector 13, size 2 Sep 26 11:32:46 exact kernel: [ 211.588163] floppy0: data CRC error: track 1, head 1, sector 14, size 2 Sep 26 11:32:46 exact kernel: [ 211.799070] floppy0: data CRC error: track 1, head 1, sector 15, size 2 Sep 26 11:32:47 exact kernel: [ 212.399073] floppy0: data CRC error: track 1, head 1, sector 15, size 2 Sep 26 11:32:47 exact kernel: [ 212.599053] floppy0: data CRC error: track 1, head 1, sector 15, size 2 Sep 26 11:32:48 exact kernel: [ 213.577045] floppy0: data CRC error: track 2, head 0, sector 7, size 2 Sep 26 11:32:49 exact kernel: [ 214.587854] floppy0: data CRC error: track 2, head 0, sector 8, size 2 Sep 26 11:32:49 exact kernel: [ 214.787839] floppy0: data CRC error: track 2, head 0, sector 8, size 2 Sep 26 11:32:50 exact kernel: [ 215.409653] floppy0: data CRC error: track 2, head 0, sector 10, size 2 Sep 26 11:32:50 exact kernel: [ 216.009596] floppy0: data CRC error: track 2, head 0, sector 10, size 2 Sep 26 11:32:51 exact kernel: [ 216.209592] floppy0: data CRC error: track 2, head 0, sector 10, size 2 Sep 26 11:32:51 exact kernel: [ 216.943967] floppy0: data CRC error: track 2, head 1, sector 1, size 2 Sep 26 11:32:51 exact kernel: [ 217.143920] floppy0: data CRC error: track 2, head 1, sector 1, size 2 Sep 26 11:32:53 exact kernel: [ 218.242258] floppy0: data CRC error: track 2, head 1, sector 10, size 2 Sep 26 11:32:53 exact kernel: [ 218.442166] floppy0: data CRC error: track 2, head 1, sector 10, size 2 Sep 26 11:32:54 exact kernel: [ 219.809271] floppy0: data CRC error: track 3, head 0, sector 1, size 2 Sep 26 11:32:54 exact kernel: [ 220.009281] floppy0: data CRC error: track 3, head 0, sector 1, size 2 Sep 26 11:32:56 exact kernel: [ 221.274683] floppy0: data CRC error: track 3, head 0, sector 7, size 2 Sep 26 11:32:56 exact kernel: [ 221.474769] floppy0: data CRC error: track 3, head 0, sector 7, size 2 Sep 26 11:32:57 exact kernel: [ 222.998180] floppy0: data CRC error: track 3, head 0, sector 18, size 2 Sep 26 11:32:59 exact kernel: [ 224.976404] floppy0: data CRC error: track 0, head 0, sector 7, size 2 Sep 26 11:33:00 exact kernel: [ 225.198254] floppy0: data CRC error: track 0, head 0, sector 9, size 2 ---------------------------------------------------------------------------- This has been tried on two different systems with 3 different known good floppies. So different floppy drives, 3 sets of good media. On a third system running an old kernel: 2.3.37 using one of the "failed" floppies, # fdformat /dev/fd0h1440 works perfectly. So it seems that something has changed on the floppy api (?) for current kernels -------------------------------------------------------------- lsmod: Module Size Used by ppdev 6348 0 lp 8012 0 speedstep_lib 4136 0 cpufreq_conservative 6256 0 cpufreq_stats 3520 0 cpufreq_powersave 1292 0 cpufreq_userspace 2768 0 microcode 11588 0 nfsd 204900 9 exportfs 3792 1 nfsd nfs 221580 0 lockd 57972 2 nfsd,nfs fscache 34440 1 nfs nfs_acl 2640 2 nfsd,nfs auth_rpcgss 31416 2 nfsd,nfs sunrpc 163772 10 nfsd,nfs,lockd,nfs_acl,auth_rpcgss nls_utf8 1488 1 nls_cp437 5320 1 vfat 8628 1 fat 41452 1 vfat nls_base 6416 4 nls_utf8,nls_cp437,vfat,fat fuse 47752 3 dm_crypt 11092 0 dm_mod 49992 1 dm_crypt loop 13324 0 snd_intel8x0 26584 0 snd_ac97_codec 91264 1 snd_intel8x0 ac97_bus 1456 1 snd_ac97_codec snd_pcm_oss 32232 0 snd_mixer_oss 12368 1 snd_pcm_oss snd_pcm 62420 3 snd_intel8x0,snd_ac97_codec,snd_pcm_oss snd_seq_midi 5688 0 snd_rawmidi 18596 1 snd_seq_midi snd_seq_midi_event 6212 1 snd_seq_midi snd_seq 42436 2 snd_seq_midi,snd_seq_midi_event snd_timer 17436 2 snd_pcm,snd_seq snd_seq_device 6136 3 snd_seq_midi,snd_rawmidi,snd_seq snd 49060 9 snd_intel8x0,snd_ac97_codec,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_rawmidi,snd_seq,snd_timer,snd_seq_device uhci_hcd 19132 0 soundcore 6184 1 snd ehci_hcd 29680 0 snd_page_alloc 8180 2 snd_intel8x0,snd_pcm i2c_i801 8564 0 3c59x 35576 0 e100 27464 0 i2c_core 20844 1 i2c_i801 intel_agp 22900 1 mii 4664 2 3c59x,e100 psmouse 37528 0 evdev 8028 6 rng_core 3672 0 usbcore 126004 3 uhci_hcd,ehci_hcd serio_raw 4560 0 pcspkr 2104 0 agpgart 30836 1 intel_agp shpchp 26648 0 pci_hotplug 24400 1 shpchp parport_pc 22420 1 floppy 46220 0 parport 31144 3 ppdev,lp,parport_pc processor 34504 0 button 5060 0 ext3 107172 2 jbd 41036 1 ext3 mbcache 6924 1 ext3 ide_cd_mod 24484 0 cdrom 30316 1 ide_cd_mod ide_gd_mod 19852 8 thermal 12580 0 fan 4044 0 thermal_sys 13140 3 processor,thermal,fan ata_generic 4340 0 libata 150904 1 ata_generic scsi_mod 131800 1 libata ide_pci_generic 3632 0 piix 5680 6 ide_core 88100 4 ide_cd_mod,ide_gd_mod,ide_pci_generic,piix ------------------------------------------------------------------------ -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages fdutils depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii debianutils 3.2.1 Miscellaneous utilities specific t ii libc6 2.9-25 GNU C Library: Shared libraries Versions of packages fdutils recommends: ii mtools 4.0.10-1 Tools for manipulating MSDOS files fdutils suggests no packages. -- debconf information: fdutils/fdmount_setuid: false
--- End Message ---
--- Begin Message ---
- To: 548434-done@bugs.debian.org
- Subject: Close (again) #548434
- From: Matteo Cypriani <mcy@lm7.fr>
- Date: Fri, 25 Jun 2010 15:24:51 +0200
- Message-id: <201006251524.51907.mcy@lm7.fr>
- In-reply-to: <201006241851.45072.mcy@lm7.fr>
- References: <201006241851.45072.mcy@lm7.fr>
Hi, As said in my previous messages, a patch relative to this issue has been included in the kernel, therefore I'm closing it. For more information, please refer to the bug page on the BTS. Thanks for reporting, and again, feel free to reopen the bug if the issue did not disappear. Regards, Matteo -- Ma clef GPG est disponible sur keyserver.veridis.com My GPG key is available on keyserver.veridis.comAttachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---