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. > > > 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: > > fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 > fdc0: FIFO enabled, 8 bytes threshold > fd0: <1440-KB 3.5" drive> on fdc0 drive 0 > > The new kernel (6.0-CURRENT as of yesterday) reports this: > > fdc0: ic_type 90 part_id 73 > fdc0: <Enhanced floppy controller> 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: <Enhanced floppy controller> at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 > fdc1: ic_type 90 part_id 73 > > 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. > 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: <Enhanced floppy controller> 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: <Enhanced floppy controller> 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, -- Ruslan Ermilov ru_at_FreeBSD.org FreeBSD committer
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:08 UTC