| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sat, 24 May 2008 11:28:38 +0200 From: Stefan Richter <stefanr@...6.in-berlin.de> To: Gene Heskett <gene.heskett@...il.com> CC: linux-kernel@...r.kernel.org, Jens Axboe <axboe@...nel.dk> Subject: Re: floppy question of the hour (Adding Cc: block layer maintainer for no solid reason...) Gene Heskett wrote: > Who is the maintainer of drivers/block/floppy.c and associated files? > > I ask because there are a few of us still using it, in particular with what some > may call oddball disk formats & I'm up to here with doing such as this: > > [root@...ote coco3]# setfdprm /dev/fd0 COCO7203.5 > [root@...ote coco3]# getfdprm /dev/fd0 > get geometry parameters: No such device > > Or: Assuming the above took, > [root@...ote coco3]# dd if=/dev/fd0 of=test.dsk > dd: reading `/dev/fd0': Input/output error > 0+0 records in > 0+0 records out > 0 bytes (0 B) copied, 25.5495 s, 0.0 kB/s > > /var/log/messages is full of these now: > May 23 21:02:07 coyote kernel: [20603.055178] floppy0: probe failed... > May 23 21:02:07 coyote kernel: [20603.455755] floppy0: unexpected interrupt > May 23 21:02:07 coyote kernel: [20603.455827] floppy0: sensei repl[0]=80 > May 23 21:02:07 coyote kernel: [20603.456135] floppy0: -- FDC reply > errorfloppy0: probe failed... [...] > The drive led is on and the disk is turning during that 25 seconds. > This is booted to 2.6.26-rc2, with the floppy driver built in. There was only a single change to drivers/block/floppy.c after 2.6.25: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=7afea3bcb1f87f3ddf34b38f202ad0d03f29e120 This looks OK to me; I suppose the problem comes from somewhere else. > 2.6.26-rc1 worked flawlessly yesterday, for both writing, then reading back for > a cmp session, twice each way, until it(2.6.26-rc1) went away after about 3 > hours uptime, the 5th time -rc1 had done this to me without a single footprint > in the logs. -rc2 is doing better, uptime is 5:45 so far. [...] By "until it(2.6.26-rc1) went away" you mean a crash during writing to or reading from the FDD, or during general usage? -- Stefan Richter -=====-==--- -=-= ==--- http://arcgraph.de/sr/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists