Bug 60817
| Summary: | FBSD-5.1/5.2-RC1 "fdc0: cmd 3 failed at out byte 1 of 3" | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | none <nospam> | ||||||
| Component: | i386 | Assignee: | freebsd-acpi (Nobody) <acpi> | ||||||
| Status: | Closed FIXED | ||||||||
| Severity: | Affects Only Me | ||||||||
| Priority: | Normal | ||||||||
| Version: | 5.1-CURRENT | ||||||||
| Hardware: | Any | ||||||||
| OS: | Any | ||||||||
| Attachments: |
|
||||||||
|
Description
none
2004-01-02 08:00:35 UTC
Hello, same problem here. With ACPI enabled, fdc0 fails with: fdc0: cmd 3 failed at out byte 1 of 3 fdc0: cannot reserve I/O port range (6 ports) devinfo -u says: 0x3f0-0x3f1 (acpi_sysresource0) 0x3f2-0x3f5 ---- Boards testet so far: - MSI 845PE Max3 - MSI 845PE Neo Without ACPI enabled: 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 drive0 Debug dmesg or any other verbose information on request. Gruss Dierk -- |----+----|----+----|----+----|----+----|----+----|----+----|----+----|--< GPG Fingerprint: D14C 12BB 37A6 6745 7F4F F420 9E59 D79E A492 2A96 GPG KeyID : A4922A96 +------------------------------------------------------------------------+ Still unable to get my floppy disk to work under 5.2-RC2. Have tried the following with no noticeable affect: 1) disable BIOS for MS6758 (875P Neo) setting for "APIC ACPI SCI IRQ", the only BIOS setting specifically related to ACPI BIOS is at latest version as of 12/2003 2) inserted two lines into /boot/loader.conf which did not display any more boot information, so I obviously have these placed incorrectly debug.acpi.layer="ACPI_HARDWARE ACPI_BUS" debug.acpi.level="ACPI_LV_ALLOCATIONS ACPI_LV_INFO" 3) added the following line in /boot/device.hints to attempt to disable runtime ACPI, which apparently did not work, or at least - had no apparent affect with regards to FDC0: hint.acpi.0.disable="1" 4) rebuilt and installed kernel withOUT "SMP" and "APIC" options no change in FDC failure or APIC error messages system hangs at mounting root device 5) sent e-mail to MSI and they suggested "disabling APIC and seeing if the system would (continue) to boot", which as shown above, has no affect on the problem 6) I have done a cursory examination of attempting to understand and recompile the ADST (?), but do not have enough information nor experience with such to be able to effectively do anything Attached are the boot messages displayed for both FBSD-5.1-RC2 and FBSD-4.9, using the same base system, but different SCSI harddrives. The installed floppy drive works under FBSD-4.x. The kernel that I use has only a few differences from the distributed GENERIC, in both FBSD V4/V5 "systems": only i686 is defined kernel name is changed all NFS options are commented out IPFILTER options are added Zitiere supraexpress@globaleyes.net vom Sat, Jan 24, 2004 at 09:24:01AM -0600: > 3) added the following line in /boot/device.hints to attempt to disable > runtime ACPI, which apparently did not work, or at least - had no > apparent affect with regards to FDC0: > > hint.acpi.0.disable="1" Argl. Mea culpa. A Typo. It has to be hint.acpi.0.disabled="1" Meanwhile I digged deeper into the issue and it turns out, that the isa code fails to allocate the resource in fdc_alloc_resources /usr/src/sys/isa/fd.c: line 702: fdc->res_ioport = bus_alloc_resource([...] The resulting error is not bogus, as I thought in the first. I think, the resource is either allocated to acpi_sysresource in error or is not allocated to anything at all in acpi_sysresource_attach /usr/src/sys/dev/acpica: line 583ff The cause seems to be a wrong or missing resource claim in the bios of those MSI boards. My next step will be to find out, which one of the lines (devinfo -u): ... 0x3f0-0x3f1 (acpi_sysresource0) 0x3f2-0x3f5 ---- ... is the wrong one. Either 0x3f0-9x3f1 shouldn't be claimed by acpi_sysresource0 _or_ the strange "----" indicates $I_DONT_KNOW_THE_HECK_WHAT_IT_INDICATES. Maybe it should also be claimed by acpi_sysresource0 (and this may be the missing part in the BIOS DSTD or wherever the acpi knows about whats a sysresource). If we make it to the statement thats missing or wrong, we may be able to force things via a hard coded hack for our broken boards until we are able to beg MSI to release a bios update or fix the DSDT ourselves. On the other hand 0x3f7 is claimed by root0 and to my understanding of acpi this might be the right assignment. So maybe the whole range of 0x3f0-0x3f5 (0x3f6 is the stupid ata controller that makes this breakage necessary in the first place) should be claimed by root0 too. But I'm just guessing. "Ich glotz da rein wie die Sau ins Uhrwerk"[1], as we say in german. So we are in heavy need of some bsd acpi insider to help us out with at least some hints, where to dig further. Gruss Dierk [1] sort of "I really have no idea, what I'm doing here." -- |----+----|----+----|----+----|----+----|----+----|----+----|----+----|--< GPG Fingerprint: D14C 12BB 37A6 6745 7F4F F420 9E59 D79E A492 2A96 GPG KeyID : A4922A96 +------------------------------------------------------------------------+ Finally getting ACPI disabled on my 5.2-RC2 system DOES now allow fdc0
to be "found/allocated/skinned from the Twilight Zone" as shown in the
following RC2 dmesg output, though now there are a bunch of 'unknown:
<PNP0303> can't assign resources (port)' messages. FWIW the MS6758 (875P
Neo) BIOS uses an MP table of V1.4.
This begs the question of: what are "we" loosing or gaining with or
without ACPI, other than the floppy drive?
Copyright (c) 1992-2003 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD 5.2-RC2 #0: Sat Jan 24 08:33:26 CST 2004
root@freebsd2.localnet10:/usr/src/sys/i386/compile/5.2_RC2
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0baf000.
Preloaded elf module "/boot/kernel/linux.ko" at 0xc0baf244.
Preloaded elf module "/boot/kernel/snd_emu10k1.ko" at 0xc0baf2f0.
Preloaded elf module "/boot/kernel/snd_pcm.ko" at 0xc0baf3a0.
Preloaded elf module "/boot/kernel/snd_ich.ko" at 0xc0baf44c.
Preloaded elf module "/boot/kernel/nvidia.ko" at 0xc0baf4f8.
MPTable: <INTEL I875 >
Timecounter "i8254" frequency 1193182 Hz quality 0
CPU: Intel(R) Pentium(R) 4 CPU 3.20GHz (3245.47-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0xf29 Stepping = 9
Features=0xbfebfbff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CLFLUSH,DTS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE>
Hyperthreading: 2 logical CPUs
real memory = 1073676288 (1023 MB)
avail memory = 1033498624 (985 MB)
ioapic0: Assuming intbase of 0
ioapic0 <Version 2.0> irqs 0-23 on motherboard
Pentium Pro MTRR support enabled
npx0: [FAST]
npx0: <math processor> on motherboard
npx0: INT 16 interface
pcibios: BIOS version 2.10
Using $PIR table, 12 entries at 0xc00f7c30
pcib0: <MPTable Host-PCI bridge> at pcibus 0 on motherboard
pci0: <PCI bus> on pcib0
pcib0: slot 29 INTA routed to irq 16
pcib0: slot 29 INTB routed to irq 19
pcib0: slot 29 INTC routed to irq 18
pcib0: slot 29 INTA routed to irq 16
pcib0: slot 29 INTD routed to irq 23
pcib0: slot 31 INTB routed to irq 17
pcib0: slot 31 INTB routed to irq 17
agp0: <Intel 82875P host to AGP bridge> mem 0xfc000000-0xfdffffff at device 0.0 on pci0
pcib1: <MPTable PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pcib1: slot 0 INTA routed to irq 16
nvidia0: <GeForce4 Ti 4600> mem 0xf9a80000-0xf9afffff,0xf0000000-0xf7ffffff,0xfa000000-0xfaffffff irq 16 at device 0.0 on pci1
pci0: <base peripheral> at device 6.0 (no driver attached)
uhci0: <Intel 82801EB (ICH5) USB controller USB-A> port 0xe000-0xe01f irq 16 at device 29.0 on pci0
usb0: <Intel 82801EB (ICH5) USB controller USB-A> on uhci0
usb0: USB revision 1.0
uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
uhci1: <Intel 82801EB (ICH5) USB controller USB-B> port 0xe400-0xe41f irq 19 at device 29.1 on pci0
usb1: <Intel 82801EB (ICH5) USB controller USB-B> on uhci1
usb1: USB revision 1.0
uhub1: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhci2: <Intel 82801EB (ICH5) USB controller USB-C> port 0xe800-0xe81f irq 18 at device 29.2 on pci0
usb2: <Intel 82801EB (ICH5) USB controller USB-C> on uhci2
usb2: USB revision 1.0
uhub2: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub2: 2 ports with 2 removable, self powered
ugen0: APC Back-UPS ES 725 FW:802.n2.D USB FW:n2, rev 1.10/1.06, addr 2
uhci3: <Intel 82801EB (ICH5) USB controller USB-D> port 0xec00-0xec1f irq 16 at device 29.3 on pci0
usb3: <Intel 82801EB (ICH5) USB controller USB-D> on uhci3
usb3: USB revision 1.0
uhub3: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub3: 2 ports with 2 removable, self powered
pci0: <serial bus, USB> at device 29.7 (no driver attached)
pcib2: <MPTable PCI-PCI bridge> at device 30.0 on pci0
pci2: <PCI bus> on pcib2
pcib2: slot 1 INTA routed to irq 17
pcib2: slot 2 INTA routed to irq 18
pcib2: slot 3 INTA routed to irq 19
pcib2: slot 8 INTA routed to irq 20
pcm0: <Creative EMU10K1> port 0xc400-0xc41f irq 17 at device 1.0 on pci2
pcm0: <SigmaTel STAC9708/11 AC97 Codec>
ahc0: <Adaptec 29160N Ultra160 SCSI adapter> port 0xc800-0xc8ff mem 0xfbeff000-0xfbefffff irq 18 at device 2.0 on pci2
aic7892: Ultra160 Wide Channel A, SCSI Id=7, 32/253 SCBs
sis0: <NatSemi DP8381[56] 10/100BaseTX> port 0xc000-0xc0ff mem 0xfbefe000-0xfbefefff irq 19 at device 3.0 on pci2
sis0: Silicon Revision: DP83815D
sis0: Ethernet address: 00:09:5b:1e:62:ec
miibus0: <MII bus> on sis0
ukphy0: <Generic IEEE 802.3u media interface> on miibus0
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
fxp0: <Intel 82801BA (D865) Pro/100 VE Ethernet> port 0xbc00-0xbc3f mem 0xfbefd000-0xfbefdfff irq 20 at device 8.0 on pci2
fxp0: Ethernet address 00:0c:76:26:da:ea
miibus1: <MII bus> on fxp0
inphy0: <i82562ET 10/100 media interface> on miibus1
inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci0: <Intel ICH5 UDMA100 controller> port 0xfc00-0xfc0f,0-0x3,0-0x7,0-0x3,0-0x7 at device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
pci0: <serial bus, SMBus> at device 31.3 (no driver attached)
pcm1: <Intel ICH5 (82801EB)> port 0xd800-0xd83f,0xdc00-0xdcff mem 0xfbfff900-0xfbfff9ff,0xfbfffa00-0xfbfffbff irq 17 at device 31.5 on pci0
pcm1: <Analog Devices AD1980 AC97 Codec>
orm0: <Option ROMs> at iomem 0xe0000-0xe0fff,0xc0000-0xce7ff on isa0
pmtimer0 on isa0
atkbdc0: <Keyboard controller (i8042)> at port 0x64,0x60 on isa0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse, device ID 3
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
ppc0: <Parallel port> at port 0x378-0x37f irq 7 on isa0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/9 bytes threshold
ppbus0: <Parallel port bus> on ppc0
plip0: <PLIP network interface> on ppbus0
lpt0: <Printer> on ppbus0
lpt0: Interrupt-driven port
ppi0: <Parallel I/O> on ppbus0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0
sio0: type 16550A
sio1 at port 0x2f8-0x2ff irq 3 on isa0
sio1: type 16550A
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
unknown: <PNP0303> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0501> can't assign resources (port)
unknown: <PNP0401> can't assign resources (port)
unknown: <PNP0700> can't assign resources (port)
unknown: <PNP0f13> can't assign resources (irq)
Timecounter "TSC" frequency 3245470592 Hz quality 800
Timecounters tick every 10.000 msec
IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled
acd0: CDRW <SAMSUNG CDRW/DVD SM-348B> at ata0-master PIO4
GEOM: create disk ad2 dp=0xc6b62b60
ad2: 38196MB <SAMSUNG SV4002H> [77605/16/63] at ata1-master UDMA100
Waiting 15 seconds for SCSI devices to settle
GEOM: create disk da0 dp=0xc6b6a850
GEOM: create disk da1 dp=0xc6b69c50
GEOM: create disk da2 dp=0xc6b75850
sa0 at ahc0 bus 0 target 2 lun 0
sa0: <ECRIX VXA-1 2C8C> Removable Sequential Access SCSI-2 device
sa0: 80.000MB/s transfers (40.000MHz, offset 32, 16bit)
da0 at ahc0 bus 0 target 0 lun 0
da0: <SEAGATE ST336752LW 0004> Fixed Direct Access SCSI-3 device
da0: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da0: 35003MB (71687369 512 byte sectors: 255H 63S/T 4462C)
da1 at ahc0 bus 0 target 4 lun 0
da1: <SEAGATE ST34501N 0015> Fixed Direct Access SCSI-2 device
da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled
da1: 4339MB (8887200 512 byte sectors: 255H 63S/T 553C)
da2 at ahc0 bus 0 target 6 lun 0
da2: < S7Z0> Fixed Direct Access SCSI-3 device
da2: 160.000MB/s transfers (80.000MHz, offset 63, 16bit), Tagged Queueing Enabled
da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C)
Mounting root from ufs:/dev/da1s1a
Hi,
After a valuable mailing from Nate Lawson on -current I've been
finally able to fix my DSDT. I have now a working fdc with acpi.
The attached patch is for my MSI 845PE Max3. It should tell you, what to
do (find the sysressource, remove it, fix FDC resource allocation, fix
it, never forget to adjust the buffers length )
WARNING: I'm not shure about the removed sysresource. That part was just
trial and error. It may destroy your box or whatever. Don't blame me if
you try this.
The PR should also be closed, because a broken DSDT is not a problem of
freebsd.
Gruss
Dierk
--- DSDT.dsl.orig Mon Feb 16 04:13:31 2004
+++ DSDT.dsl Mon Feb 16 04:13:22 2004
@@ -1501,7 +1501,7 @@
Return (0x0F)
}
- Name (IORG, Buffer (0x56)
+ Name (IORG, Buffer (0x4e)
{
0x4B, 0x10, 0x00, 0x10, 0x4B, 0x20, 0x00, 0x20,
0x4B, 0x44, 0x00, 0x1C, 0x4B, 0x62, 0x00, 0x02,
@@ -1510,12 +1510,11 @@
0x4B, 0x88, 0x00, 0x01, 0x4B, 0x8C, 0x00, 0x03,
0x4B, 0x90, 0x00, 0x10, 0x4B, 0xA0, 0x00, 0x20,
0x4B, 0xE0, 0x00, 0x10, 0x4B, 0x90, 0x02, 0x08,
- 0x47, 0x01, 0xF0, 0x03, 0xF0, 0x03, 0x00, 0x02,
0x47, 0x01, 0xD0, 0x04, 0xD0, 0x04, 0x00, 0x02,
0x86, 0x09, 0x00, 0x00, 0x00, 0x00, 0xE0, 0xFE,
0x00, 0x00, 0x10, 0x00, 0x79, 0x00
})
- Name (IO98, Buffer (0x5A)
+ Name (IO98, Buffer (0x52)
{
0x4B, 0x10, 0x00, 0x10, 0x4B, 0x22, 0x00, 0x1E,
0x4B, 0x44, 0x00, 0x1C, 0x4B, 0x62, 0x00, 0x02,
@@ -1524,7 +1523,6 @@
0x4B, 0x88, 0x00, 0x01, 0x4B, 0x8C, 0x00, 0x03,
0x4B, 0x90, 0x00, 0x10, 0x4B, 0xA2, 0x00, 0x1E,
0x4B, 0xE0, 0x00, 0x10, 0x4B, 0x90, 0x02, 0x08,
- 0x47, 0x01, 0xF0, 0x03, 0xF0, 0x03, 0x00, 0x02,
0x47, 0x01, 0xD0, 0x04, 0xD0, 0x04, 0x00, 0x02,
0x47, 0x01, 0x00, 0x04, 0x00, 0x04, 0x00, 0x40,
0x47, 0x01, 0x00, 0x08, 0x00, 0x08, 0x00, 0x80,
@@ -2736,10 +2734,9 @@
}
}
- Name (FCRS, Buffer (0x20)
+ Name (FCRS, Buffer (0x18)
{
- 0x47, 0x01, 0xF2, 0x03, 0xF2, 0x03, 0x01, 0x02,
- 0x47, 0x01, 0xF4, 0x03, 0xF4, 0x03, 0x01, 0x02,
+ 0x47, 0x01, 0xF0, 0x03, 0xF0, 0x03, 0x01, 0x06,
0x47, 0x01, 0xF7, 0x03, 0xF7, 0x03, 0x01, 0x01,
0x22, 0x40, 0x00, 0x2A, 0x04, 0x00, 0x79, 0x00
})
--
|----+----|----+----|----+----|----+----|----+----|----+----|----+----|--<
GPG Fingerprint: D14C 12BB 37A6 6745 7F4F F420 9E59 D79E A492 2A96
GPG KeyID : A4922A96
+------------------------------------------------------------------------+
The suggested patch failed to alleviate the FDC0 failure for my MSI-6758, 875P Neo motherboard. It also doesn't exactly "fit" as the DSDT for the 875P is slightly different from that in the suggestion (for an MSI 845PE) which I cannot expound upon right at the moment as this update is coming from FBSD-4.9 instead of FBSD-5.2. Responsible Changed From-To: freebsd-i386->freebsd-acpi This looks like an ACPI problem State Changed From-To: open->feedback Please try a recent (2004/8/23 or newer) snapshot from snapshots.jp.freebsd.org or cvsup to -current. I think this issue may be addressed. MSI MS-6758 875P Neo + ACPI with FBSD-5.3-Beta3 SESNAP 09/04/2004 and FBSD-6.0-CURRENT SESNAP 09/04/2004 is still unable to use FDC0 with ACPI enabled: fdc0: <floppy disk controller> port 0x3f7, 0x3f4-0x3f5, 0x3fs-0x3f3 irq 6 drq 2 on acpi0 [FBSD-6.0] fdc0: does not respond [FBSD-5.3] fdc0: cmd 3 failed at out byte 1 of 3 device_attach: fdc0 attach returned 6 Disabling ACPI allows the floppy controller to be "properly" determined and set up. Running without ACPI is not a problem for me since I don't have a laptop and have no need for "power controls". No modifications to DSDT were made. > From: User1001 <supraexpress@globaleyes.net> > > fdc0: <floppy disk controller> port 0x3f7, 0x3f4-0x3f5, 0x3fs-0x3f3 irq > 6 drq 2 on acpi0 > [FBSD-6.0] fdc0: does not respond > [FBSD-5.3] fdc0: cmd 3 failed at out byte 1 of 3 > device_attach: fdc0 attach returned 6 > > Disabling ACPI allows the floppy controller to be "properly" determined > and set up. > Running without ACPI is not a problem for me since I don't have a laptop > and have no > need for "power controls". No modifications to DSDT were made. The problem is the resource going from 0x3f2-0x3f5. Warner is working on this and hopefully we'll have it fixed before 5.3. Linux had a similar problem about a year ago. -- Nate FBSD-5.3-Beta5 has FIXED the problem with my floppy drive. I have tested it and it appears to work just fine under ACPI. THANK YOU! You may close out PR#60817. On 5 Sep, To: freebsd-gnats-submit@FreeBSD.org wrote: > MSI MS-6758 875P Neo + ACPI with FBSD-5.3-Beta3 SESNAP 09/04/2004 and > FBSD-6.0-CURRENT SESNAP 09/04/2004 is still unable to use FDC0 with ACPI > enabled: > > fdc0: <floppy disk controller> port 0x3f7, 0x3f4-0x3f5, 0x3fs-0x3f3 irq > 6 drq 2 on acpi0 > [FBSD-6.0] fdc0: does not respond > [FBSD-5.3] fdc0: cmd 3 failed at out byte 1 of 3 > device_attach: fdc0 attach returned 6 > > Disabling ACPI allows the floppy controller to be "properly" determined > and set up. > Running without ACPI is not a problem for me since I don't have a laptop > and have no > need for "power controls". No modifications to DSDT were made. > State Changed From-To: feedback->closed Closed! Fixed in head and releng_5, nothing else matters. |
