From owner-freebsd-current@FreeBSD.ORG Wed Aug 25 20:57:34 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2577116A4CE; Wed, 25 Aug 2004 20:57:34 +0000 (GMT) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.86.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id 74CFA43D1D; Wed, 25 Aug 2004 20:57:33 +0000 (GMT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id i7PKvVwI042279; Wed, 25 Aug 2004 22:57:32 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Ruslan Ermilov From: "Poul-Henning Kamp" In-Reply-To: Your message of "Wed, 25 Aug 2004 23:47:57 +0300." <20040825204757.GD35529@ip.net.ua> Date: Wed, 25 Aug 2004 22:57:31 +0200 Message-ID: <42278.1093467451@critter.freebsd.dk> Sender: phk@critter.freebsd.dk cc: current@FreeBSD.org Subject: Re: No more floppy drive X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 25 Aug 2004 20:57:34 -0000 Ruslan, I have my left arm in a sling and keyboard work is very painful still so this will be short: There are two current problem issues with floppy disks, one is a ACPI and possibly ISA issue about resource reservation, and the other is that I may have made the probe/attach too selective with my last commit to fdc.c. I don't know which of the two you hit here, but suspect the first because the "device_attach: fdc0 attach returned 2" doesn't look like anything I have any connection with. Please pepper the stuff with printfs and see if you can find out where it explodes, and then send email to Warner, Nate and me about what you find. Poul-Henning In message <20040825204757.GD35529@ip.net.ua>, Ruslan Ermilov writes: > >--DiL7RhKs8rK9YGuF >Content-Type: text/plain; charset=us-ascii >Content-Disposition: inline >Content-Transfer-Encoding: quoted-printable > >On Wed, Aug 25, 2004 at 01:51:46PM +0300, Ruslan Ermilov wrote: >> On Wed, Aug 25, 2004 at 12:37:58PM +0200, Poul-Henning Kamp wrote: >> > I'm not sure you can debug this with the sysctl. You'll probably have >> > to stick in some printfs to find out where that two comes from. >> >=20 >> I'll try that tonight, when I have more spare time. In the >> mean time, here's some info for consideration. The old >> kernel had this "fdc" related stuff: >>=20 >> fdc0: at port 0x3= >f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 >> fdc0: FIFO enabled, 8 bytes threshold >> fd0: <1440-KB 3.5" drive> on fdc0 drive 0 >>=20 >> The new kernel (6.0-CURRENT as of yesterday) reports this: >>=20 >> fdc0: ic_type 90 part_id 73 >> fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 = >on isa0 >> device_attach: fdc0 attach returned 2 >> fdc1: ic_type 90 part_id 73 >> fdc1: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 = >on isa0 >> fdc1: ic_type 90 part_id 73 >>=20 >> Another odd thing is that I don't have fdc1 at all. This >> is an IBM ThinkPad 600X notebook with only one floppy >> controller. My floppy drive is physically attached. >>=20 >OK, I wanted to play with the new fdc(4) a bit, to help you find >out what's wrong with it, so I took away "device fdc" from my >kernel config, recompiled, rebooted, and wanted to play with the >module. I found the following bugs: > >1. If kernel has "device fdc", then "kldload fdc" will panic > a system. > >2. If kernel doesn't have "device fdc", then "kldload fdc" > reports "fdc0: cannot allocate a port range (6 ports)". > Attempting to "kldunload fdc" results in a panic. > >3. The fdc(4) seems to find a non-existing fdc1. > >Verbose boot says the following about fdc: > >: fdc0: ic_type 90 part_id 73 >: fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 = >on isa0 >: device_attach: fdc0 attach returned 2 >: fdc1: ic_type 90 part_id 73 >: fdc1: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 = >on isa0 >: fdc1: ic_type 90 part_id 73 >: fdc1: output ready timeout >: fdc1: output ready timeout >: fdc1: output ready timeout >: fdc1: output ready timeout >: fdc1: output ready timeout >: fdc1: output ready timeout >: fdc1: output ready timeout >: fdc1: output ready timeout >: fdc1: input ready timeout >: fdc1: input ready timeout >: fdc1: output ready timeout >: fdc1: input ready timeout >: fdc1: input ready timeout >: fdc1: output ready timeout >: fdc1: input ready timeout >: fdc1: input ready timeout >: fdc1: output ready timeout >: fdc1: input ready timeout >: fdc1: input ready timeout > >Can you please fix module loading/unloading so that I can play >with fdc further, to find the main reason? I really miss my >floppy back. ;) > >Please also don't MFC it to RELENG_5 just yet. > > >Cheers, >--=20 >Ruslan Ermilov >ru@FreeBSD.org >FreeBSD committer > >--DiL7RhKs8rK9YGuF >Content-Type: application/pgp-signature >Content-Disposition: inline > >-----BEGIN PGP SIGNATURE----- >Version: GnuPG v1.2.5 (FreeBSD) > >iD8DBQFBLPr9qRfpzJluFF4RAhC3AJ0VEitXQg3C53bf+euSmQnNajaYVACeLhMz >BsZs2in/62zGsXM+GnWlOek= >=1OX9 >-----END PGP SIGNATURE----- > >--DiL7RhKs8rK9YGuF-- > -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | TCP/IP since RFC 956 FreeBSD committer | BSD since 4.3-tahoe Never attribute to malice what can adequately be explained by incompetence.