From shizukakudo_99@yahoo.com  Mon Aug 11 09:49:24 2003
Return-Path: <shizukakudo_99@yahoo.com>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B40FC37B401
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 11 Aug 2003 09:49:24 -0700 (PDT)
Received: from web11408.mail.yahoo.com (web11408.mail.yahoo.com [216.136.131.238])
	by mx1.FreeBSD.org (Postfix) with SMTP id BD7B343F75
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 11 Aug 2003 09:49:23 -0700 (PDT)
	(envelope-from shizukakudo_99@yahoo.com)
Received: from [219.76.96.5] by web11408.mail.yahoo.com via HTTP; Mon, 11 Aug 2003 09:49:23 PDT
Message-Id: <20030811164923.76649.qmail@web11408.mail.yahoo.com>
Date: Mon, 11 Aug 2003 09:49:23 -0700 (PDT)
From: Shizuka Kudo <shizukakudo_99@yahoo.com>
To: FreeBSD-gnats-submit@freebsd.org
Subject: Mouse broken for some AWARD bios with ACPI

>Number:         55473
>Category:       i386
>Synopsis:       Mouse broken on some AWARD BIOS with ACPI enabled
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    njl
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Mon Aug 11 09:50:11 PDT 2003
>Closed-Date:    Wed Aug 11 16:36:58 GMT 2004
>Last-Modified:  Sun Aug 15 16:30:24 GMT 2004
>Originator:     Shizuka Kudo
>Release:        FreeBSD 5.1-CURRENT i386
>Organization:
>Environment:
System: FreeBSD shizuka.com 5.1-CURRENT FreeBSD 5.1-CURRENT #20030809: Sat Aug 9 01:19:04 GMT 2003
root@shizuka.com:/usr/obj/usr/src/sys/SHIZUKA i386

        i386, FreeBSD-current
>Description:
        The symptoms are that when the mouse is moved, the cursor is only updated about once a
second. Disabling acpi makes the mouse working again.
>How-To-Repeat:
        Boot the kernel on the machine with problem.
>Fix:

   Revert a previous commit on sys/dev/acpica/acpi_pci_link.c made the mouse work again. The
commit check for ACPI_PRESENT | ACPI_FUNCTIONAL instead of ACPI_ENABLE.  Some motherboard actually
need to check against ACPI_ENABLE. Here's the relevant commit that create the problem:

> Revision 1.3 / (download) - annotate - [select for diffs], Thu Oct 31 20:43:02 2002 UTC (9 
> months, 1 week ago) by iwasaki 
> Branch: MAIN 
> Changes since 1.2: +4 -5 lines
> Diff to previous 1.2 (colored) 
> 
> Don't examine ACPI_STA_ENABLE bit of device's_STA object on initial
> state.  Instead, use ACPI_STA_PRESENT and ACPI_STA_FUNCTIONAL for it.
> In some ACPI BIOS implementations, boot disabled devices don't have
> ACPI_STA_ENABLE bit in _STA object.
> Also it is not fatal if getting current IRQ of boot disabled devices
> is failed in initial state.
>
> And minor fixes.

Here's the dmesg with a status to show STA returned.

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.1-CURRENT #20030811: Mon Aug 11 21:17:44 HKT 2003
    root@shizuka.com:/usr/obj/usr/src/sys/SHIZUKA
Preloaded elf kernel "/boot/kernel/kernel" at 0xc059d000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc059d1f4.
Timecounter "i8254"  frequency 1193182 Hz
CPU: Intel(R) Celeron(TM) CPU                1000MHz (1339.05-MHz 686-class CPU)
  Origin = "GenuineIntel"  Id = 0x6b1  Stepping = 1
 
Features=0x383f9ff<FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,MMX,FXSR,SSE>
real memory  = 536805376 (511 MB)
avail memory = 515264512 (491 MB)
Pentium Pro MTRR support enabled
npx0: <math processor> on motherboard
npx0: INT 16 interface
acpi0: <IntelR AWRDACPI> on motherboard
pcibios: BIOS version 2.10
Using $PIR table, 10 entries at 0xc00fded0
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-fast"  frequency 3579545 Hz
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x4008-0x400b on acpi0
acpi_cpu0: <CPU> port 0x530-0x537 on acpi0
acpi_tz0: <thermal zone> port 0x530-0x537 on acpi0
acpi_button0: <Power Button> on acpi0
pcib0: <ACPI Host-PCI bridge> port 0x4000-0x40f7,0xcf8-0xcff on acpi0
pcib0: PCI status - \\_SB_.PCI0.LNKA: b
pcib0: PCI status - \\_SB_.PCI0.LNKB: b
pcib0: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib0: PCI status - \\_SB_.PCI0.LNKD: b
pcib0: PCI status - \\_SB_.PCI0.LNKA: b
pcib0: PCI status - \\_SB_.PCI0.LNKB: b
pcib0: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib0: PCI status - \\_SB_.PCI0.LNKD: b
pcib0: PCI status - \\_SB_.PCI0.LNKA: b
pcib0: PCI status - \\_SB_.PCI0.LNKB: b
pcib0: PCI status - \\_SB_.PCI0.LNK1: b
pcib0: PCI status - \\_SB_.PCI0.LNKD: b
pcib0: PCI status - \\_SB_.PCI0.LNKA: b
pcib0: PCI status - \\_SB_.PCI0.LNKB: b
pcib0: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib0: PCI status - \\_SB_.PCI0.LNKD: b
pci0: <ACPI PCI bus> on pcib0
pcib0: slot 31 INTD is routed to irq 11
pcib0: slot 31 INTC is routed to irq 9
pcib0: slot 31 INTB is routed to irq 10
agp0: <Intel 82815 (i815 GMCH) host to PCI bridge> mem 0xd8000000-0xdbffffff at device 0.0 on pci0
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pcib0: slot 1 INTA is routed to irq 5
pcib1: slot 0 INTA is routed to irq 5
pci1: <display, VGA> at device 0.0 (no driver attached)
pcib2: <ACPI PCI-PCI bridge> at device 30.0 on pci0
pcib2: PCI status - \\_SB_.PCI0.LNKE: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNKF: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNK0: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNK1: b
pcib2: PCI status - \\_SB_.PCI0.LNKB: b
pcib2: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNKD: b
pcib2: PCI status - \\_SB_.PCI0.LNKA: b
pcib2: PCI status - \\_SB_.PCI0.LNKA: b
pcib2: PCI status - \\_SB_.PCI0.LNKB: b
pcib2: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNKD: b
pcib2: PCI status - \\_SB_.PCI0.LNKD: b
pcib2: PCI status - \\_SB_.PCI0.LNKA: b
pcib2: PCI status - \\_SB_.PCI0.LNKB: b
pcib2: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNKD: b
pcib2: PCI status - \\_SB_.PCI0.LNKA: b
pcib2: PCI status - \\_SB_.PCI0.LNKB: b
pcib2: PCI status - \\_SB_.PCI0.LNKA: b
pcib2: PCI status - \\_SB_.PCI0.LNKB: b
pcib2: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNKD: b
pcib2: PCI status - \\_SB_.PCI0.LNKB: b
pcib2: PCI status - \\_SB_.PCI0.LNKC: 9
   ^---------- The patch failed to detect this scenario
pcib2: PCI status - \\_SB_.PCI0.LNKD: b
pcib2: PCI status - \\_SB_.PCI0.LNKA: b
pci2: <ACPI PCI bus> on pcib2
pcib2: slot 0 INTA is routed to irq 5
pcib2: slot 0 INTA is routed to irq 5
pcib2: slot 3 INTA is routed to irq 11
pcib2: slot 5 INTA is routed to irq 10
cbb0: <TI1225 PCI-CardBus Bridge> mem 0xdf009000-0xdf009fff irq 5 at device 0.0 on pci2
cardbus0: <CardBus bus> on cbb0
pccard0: <16-bit PCCard bus> on cbb0
cbb1: <TI1225 PCI-CardBus Bridge> mem 0xdf004000-0xdf004fff irq 5 at device 0.1 on pci2
cardbus1: <CardBus bus> on cbb1
pccard1: <16-bit PCCard bus> on cbb1
atapci0: <HighPoint HPT370 UDMA100 controller> port
0xc000-0xc0ff,0xbc00-0xbc03,0xb800-0xb807,0xb400-0xb403,0xb000-0xb007 irq 11 at device 3.0 on pci2
ata2: at 0xb000 on atapci0
ata3: at 0xb800 on atapci0
xl0: <3Com 3c905-TX Fast Etherlink XL> port 0xc400-0xc43f irq 10 at device 5.0 on pci2
xl0: Ethernet address: 00:60:97:93:6a:7c
miibus0: <MII bus> on xl0
nsphy0: <DP83840 10/100 media interface> on miibus0
nsphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
isab0: <PCI-ISA bridge> at device 31.0 on pci0
isa0: <ISA bus> on isab0
atapci1: <Intel ICH2 UDMA100 controller> port 0xf000-0xf00f at device 31.1 on pci0
ata0: at 0x1f0 irq 14 on atapci1
ata1: at 0x170 irq 15 on atapci1
uhci0: <Intel 82801BA/BAM (ICH2) USB controller USB-A> port 0xd000-0xd01f irq 11 at device 31.2 on
pci0
usb0: <Intel 82801BA/BAM (ICH2) 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
ichsmb0: <Intel 82801BA (ICH2) SMBus controller> port 0x5000-0x500f at device 31.3 on pci0
pcib0: slot 31 INTB is routed to irq 10
smbus0: <System Management Bus> on ichsmb0
smb0: <SMBus generic I/O> on smbus0
uhci1: <Intel 82801BA/BAM (ICH2) USB controller USB-B> port 0xd400-0xd41f irq 9 at device 31.4 on
pci0
usb1: <Intel 82801BA/BAM (ICH2) 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
pcm0: <Intel ICH2 (82801BA)> port 0xdc00-0xdc3f,0xd800-0xd8ff irq 10 at device 31.5 on pci0
pcm0: <Avance Logic ALC200 AC97 Codec>
fdc0: <Enhanced floppy controller (i82077, NE72065 or clone)> port 0x3f7,0x3f0-0x3f5 irq 6 drq 2
on acpi0
fdc0: FIFO enabled, 8 bytes threshold
fd0: <1440-KB 3.5" drive> on fdc0 drive 0
sio0 port 0x3f8-0x3ff irq 4 on acpi0
sio0: type 16550A
sio1 port 0x2f8-0x2ff irq 3 on acpi0
sio1: type 16550A
ppc0 port 0xf78-0xf7b,0xb78-0xb7b,0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0
ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
ppc0: FIFO with 16/16/16 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
atkbdc0: <Keyboard controller (i8042)> port 0x64,0x60 irq 1 on acpi0
atkbd0: <AT Keyboard> flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: <PS/2 Mouse> irq 12 on atkbdc0
psm0: model IntelliMouse Explorer, device ID 4
pmtimer0 on isa0
sc0: <System console> at flags 0x100 on isa0
sc0: VGA <16 virtual consoles, flags=0x300>
vga0: <Generic ISA VGA> at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Timecounter "TSC"  frequency 1339053145 Hz
Timecounters tick every 10.000 msec
acpi_cpu: throttling enabled, 2 steps (100% to 50.0%), currently 100.0%
wi0: <Lucent Technologies WaveLAN/IEEE> at port 0x100-0x13f irq 5 function 0 config 1 on pccard0
wi0: 802.11 address: 00:60:1d:f2:38:c0
wi0: using Lucent Technologies, WaveLAN/IEEE
wi0: Lucent Firmware: Station (8.72.1)
wi0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps
cbb1: ready never happened, status = 0c
pccard1: Card has no functions!
cbb1: PC Card card activation failed
ad4: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata2-master UDMA100
ad6: 29314MB <IBM-DTLA-307030> [59560/16/63] at ata3-master UDMA100
ata0-master: DMA limited to UDMA33, non-ATA66 cable or device
acd0: DVD-ROM <JLMS DVD-ROM LTD-166S> at ata0-master UDMA33
acd1: CD-RW <SONY CD-RW CRX120E> at ata0-slave WDMA2
ar0: 29314MB <ATA RAID1 array> [3737/255/63] status: READY subdisks:
 disk0 READY on ad4 at ata2-master
 disk1 READY on ad6 at ata3-master
Opened disk ad4 -> 1
Opened disk ad4 -> 1
Opened disk ad4 -> 1
Opened disk ad4 -> 1
Opened disk ad6 -> 1
Opened disk ad6 -> 1
Mounting root from ufs:/dev/ar0s1a


__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
>Release-Note:
>Audit-Trail:

From: Dan Strick <strick@covad.net>
To: freebsd-gnats-submit@FreeBSD.org, shizukakudo_99@yahoo.com,
	strick@covad.net
Cc:  
Subject: Re: i386/55473: Mouse broken on some AWARD BIOS with ACPI enabled
Date: Mon, 20 Oct 2003 19:30:48 -0700

 This bug (or "glitch", depending on your point of view) report, 
 i386/55473, was submitted with
 a non-critical Severity level parameter and a medium Priority level.  I 
 think this bug report should
 be taken much more seriously by the FreeBSD person who eventually 
 processes this bug report.
 
 A workstation is essentially useless without a working mouse.  I happen 
 to be one of the unlucky
 people with an AWARD BIOS that is subject to this bug.  The misbehavior 
 came and went with
 the phases of the moon.  I became immensely frustrated and more than a 
 little depressed.
 If I had not found this problem report and hacked acpi_pci_link.c to 
 make the problem go away,
 I would have had to abandon FreeBSD release 5.1 and would not have been 
 able to use my new
 PC for many months.  (I am quite grateful to Shizuka Kudo for submitting 
 this problem report.)
 
 Please make sure this nasty bug gets noticed and fixed in the FreeBSD 
 CURRENT
 development branch.
 
 Thanks,
 
 Dan Strick
 strick@covad.net
 

From: Shizuka Kudo <shizukakudo_99@yahoo.com>
To: Dan Strick <strick@covad.net>, freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/55473: Mouse broken on some AWARD BIOS with ACPI enabled
Date: Wed, 5 Nov 2003 22:37:26 -0800 (PST)

 --- Dan Strick <strick@covad.net> wrote:
 > This bug (or "glitch", depending on your point of view) report, 
 > i386/55473, was submitted with
 > a non-critical Severity level parameter and a medium Priority level.  I 
 > think this bug report should
 > be taken much more seriously by the FreeBSD person who eventually 
 > processes this bug report.
 
 I tend to agree on your point now as I found out that the LPT port is also 
 affected by this problem.
 When sending data to the printer, it just stucks there until the printer
 timeout and then part of the page will be printed.  If you can confirm 
 with me that this also happen to you, I'll close the PR and submit a new one.
 If you have a serial device that you can check, I also suspect that COM1 / 
 COM2 may have problem as well.
 
 This problem is here for more than a year now, and I haven't gotten any
 attention to this even I sent message to the acpi-jp list several times.
 
 > 
 > A workstation is essentially useless without a working mouse.  I happen 
 > to be one of the unlucky
 > people with an AWARD BIOS that is subject to this bug.  The misbehavior 
 > came and went with
 > the phases of the moon.  I became immensely frustrated and more than a 
 > little depressed.
 > If I had not found this problem report and hacked acpi_pci_link.c to 
 > make the problem go away,
 > I would have had to abandon FreeBSD release 5.1 and would not have been 
 > able to use my new
 > PC for many months.  (I am quite grateful to Shizuka Kudo for submitting 
 > this problem report.)
 > 
 > Please make sure this nasty bug gets noticed and fixed in the FreeBSD 
 > CURRENT
 > development branch.
 > 
 > Thanks,
 > 
 > Dan Strick
 > strick@covad.net
 > 
 
 
 __________________________________
 Do you Yahoo!?
 Protect your identity with Yahoo! Mail AddressGuard
 http://antispam.yahoo.com/whatsnewfree
Responsible-Changed-From-To: freebsd-i386->freebsd-acpi 
Responsible-Changed-By: arved 
Responsible-Changed-When: Thu May 20 05:36:49 PDT 2004 
Responsible-Changed-Why:  
Over to ACPI Mailinglist for evaluation 

http://www.freebsd.org/cgi/query-pr.cgi?pr=55473 
State-Changed-From-To: open->closed 
State-Changed-By: njl 
State-Changed-When: Wed Aug 11 16:35:48 GMT 2004 
State-Changed-Why:  
The irq routing code has been completely revamped and it fixes the problem 
for revealed here, namely that link devices' _STA methods are not reliable. 


Responsible-Changed-From-To: freebsd-acpi->njl 
Responsible-Changed-By: njl 
Responsible-Changed-When: Wed Aug 11 16:35:48 GMT 2004 
Responsible-Changed-Why:  
Mark myself as responsible since I rewrote the irq code. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=55473 

From: Nate Lawson <nate@root.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: i386/55473
Date: Sun, 15 Aug 2004 09:20:40 -0700

 Shizuka Kudo >shizukakudo_99.at.yahoo.com> reports:
 
 It works! Thanks a lot. Just cvsup at around Aug 13 16:00 GMT and now 
 mouse works.
>Unformatted:
