NetBSD Problem Report #36672

From diro@nixsyspaus.org  Sat Jul 21 06:20:18 2007
Return-Path: <diro@nixsyspaus.org>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id 9CEB663B93E
	for <gnats-bugs@gnats.netbsd.org>; Sat, 21 Jul 2007 06:20:18 +0000 (UTC)
Message-Id: <20070721062012.0A55F75790@asche.nixsyspaus.org>
Date: Sat, 21 Jul 2007 06:20:11 +0000 (UTC)
From: diro@nixsyspaus.org
Reply-To: diro@nixsyspaus.org
To: gnats-bugs@NetBSD.org
Subject:
X-Send-Pr-Version: 3.95

>Number:         36672
>Category:       kern
>Synopsis:       azalia can not map 64-bit bar on 32-bit platform
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    kern-bug-people
>State:          closed
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Jul 21 06:25:00 +0000 2007
>Closed-Date:    Mon May 27 22:14:50 +0000 2019
>Last-Modified:  Mon May 27 22:14:50 +0000 2019
>Originator:     diro@nixsyspaus.org
>Release:        NetBSD 3.1
>Organization:
>Environment:
System: NetBSD themobe 3.1 NetBSD 3.1 (THEMOBE) #9: Sat Jul 7 22:43:26 EDT 2007 root@themobe:/usr/src/sys/arch/i386/compile/THEMOBE i386
Architecture: i386
Machine: i386
>Description:

Unable to get audio to work either with native driver or with OSS Audio. I've had private communications from a NetBSD user using a very similar high definition audio controller from Intel with no problems. He suggested i test -current, which did not help.

If no one has time to handle this or pull a fix into 3.x and / or 4.x, if someone could point me at the right resources, i'd be willing to spend some time on it. I don't currently have time to find those resources and if someone knows, i'd appreciate the links.

from dmesg:

azalia0 at pci0 dev 27 function 0: Generic High Definition Audio Controller
pci_mem_find: 64-bit memory map which is inaccessible on a 32-bit platform
azalia0: can't map device i/o space

% lspci
[...]
00:1b.0 Class 0403: Intel Corp.: Unknown device 2668 (rev 04)
[...]

% pcictl pci0 list
[...]
000:27:0: Intel 82801FB/FR High Definition Audio Controller (multimedia subclass 0x03, revision 0x04)
[...]

 % pcictl pci0 dump -d 27
 PCI configuration registers:
   Common header:
     0x00: 0x26688086 0x00100006 0x04030004 0x00000008

     Vendor Name: Intel (0x8086)
     Device Name: 82801FB/FR High Definition Audio Controller (0x2668)
     Command register: 0x0006
       I/O space accesses: off
       Memory space accesses: on
       Bus mastering: on
       Special cycles: off
       MWI transactions: off
       Palette snooping: off
       Parity error checking: off
       Address/data stepping: off
       System error (SERR): off
       Fast back-to-back transactions: off
     Status register: 0x0010
       Capability List support: on
       66 MHz capable: off
       User Definable Features (UDF) support: off
       Fast back-to-back capable: off
       Data parity error detected: off
       DEVSEL timing: fast (0x0)
       Slave signaled Target Abort: off
       Master received Target Abort: off
       Master received Master Abort: off
       Asserted System Error (SERR): off
       Parity error detected: off
     Class Name: multimedia (0x04)
     Subclass ID: 0x03
     Interface: 0x00
     Revision ID: 0x04
     BIST: 0x00
     Header Type: 0x00 (0x00)
     Latency Timer: 0x00
     Cache Line Size: 0x08

   Type 0 ("normal" device) header:
     0x10: 0xffffc004 0x0000000f 0x00000000 0x00000000
     0x20: 0x00000000 0x00000000 0x00000000 0x041b14ff
     0x30: 0x00000000 0x00000050 0x00000000 0x0000010a

     Base address register at 0x10
       type: 64-bit nonprefetchable memory
       base: 0x0000000fffffc000, not sized
     Base address register at 0x18
       not implemented(?)
     Base address register at 0x1c
       not implemented(?)
     Base address register at 0x20
       not implemented(?)
     Base address register at 0x24
       not implemented(?)
     Cardbus CIS Pointer: 0x00000000
     Subsystem vendor ID: 0x14ff
     Subsystem ID: 0x041b
     Expansion ROM Base Address: 0x00000000
     Capability list pointer: 0x50
     Reserved @ 0x38: 0x00000000
     Maximum Latency: 0x00
     Minimum Grant: 0x00
     Interrupt pin: 0x01 (pin A)
     Interrupt line: 0x0a

   Capability register at 0x50
     type: 0x01 (Power Management, rev. 1.0)
   Capability register at 0x60
     type: 0x05 (MSI)
   Capability register at 0x70
     type: 0x10 (PCI Express)

   Device-dependent header:
     0x40: 0x00000003 0x00000007 0x00000000 0x00000000
     0x50: 0xc8426001 0x00000000 0x00000000 0x00000000
     0x60: 0x00807005 0x00000000 0x00000000 0x00000000
     0x70: 0x00910010 0x00000000 0x00100800 0x00000000
     0x80: 0x00000000 0x00000000 0x00000000 0x00000000
     0x90: 0x00000000 0x00000000 0x00000000 0x00000000
     0xa0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xc0: 0x01000000 0x00000000 0x00000000 0x00000000
     0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
     0xf0: 0x00000000 0x00000000 0x00040f80 0x00000000

>How-To-Repeat:

>Fix:


>Release-Note:

>Audit-Trail:
From: diro@nixsyspaus.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/36672: azalia can not map i/o space
Date: Sat, 21 Jul 2007 02:35:23 -0400

 Subject: azalia can not map i/o space

State-Changed-From-To: open->feedback
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Mon, 07 Sep 2009 17:08:44 +0000
State-Changed-Why:
Is this still an issue with NetBSD 5.0 for you?


From: Timothy Lee Roden <diro@nixsyspaus.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/36672 (azalia can not map 64-bit bar on 32-bit platform)
Date: Mon, 7 Sep 2009 13:34:39 -0400

 On Mon, Sep 07, 2009 at 05:08:46PM +0000, jmcneill@NetBSD.org wrote:
 > Synopsis: azalia can not map 64-bit bar on 32-bit platform
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: jmcneill@NetBSD.org
 > State-Changed-When: Mon, 07 Sep 2009 17:08:44 +0000
 > State-Changed-Why:
 > Is this still an issue with NetBSD 5.0 for you?


 Indeed, but i haven't tried 5.0.1 yet. Since 5.0, i've been getting these now:

 pad0: outputs: 44100Hz, 16-bit, stereo
 audio1 at pad0: half duplex

 which don't seem to do anything. Let me know if i can help test anything.

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/36672 (azalia can not map 64-bit bar on 32-bit platform)
Date: Mon, 7 Sep 2009 19:52:13 +0000

 On Mon, Sep 07, 2009 at 06:55:02PM +0000, Timothy Lee Roden wrote:
  >  > Is this still an issue with NetBSD 5.0 for you?
  >   
  >  Indeed, but i haven't tried 5.0.1 yet.

 If you feel brave, try the new hdaudio(4) in -current; there's talk of
 getting it into 5.1.

  > Since 5.0, i've been getting these now:
  >  
  >  pad0: outputs: 44100Hz, 16-bit, stereo
  >  audio1 at pad0: half duplex
  >  
  >  which don't seem to do anything.

 That's the audio equivalent of a pty, and not related.

 -- 
 David A. Holland
 dholland@netbsd.org

From: diro@nixsyspaus.org
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/36672 (azalia can not map 64-bit bar on 32-bit platform)
Date: Mon, 7 Sep 2009 17:25:37 -0400

 On Mon, Sep 07, 2009 at 07:55:02PM +0000, David Holland wrote:
 > The following reply was made to PR kern/36672; it has been noted by GNATS.
 > 
 > From: David Holland <dholland-bugs@netbsd.org>
 > To: gnats-bugs@NetBSD.org
 > Cc: 
 > Subject: Re: kern/36672 (azalia can not map 64-bit bar on 32-bit platform)
 > Date: Mon, 7 Sep 2009 19:52:13 +0000
 > 
 >  On Mon, Sep 07, 2009 at 06:55:02PM +0000, Timothy Lee Roden wrote:
 >   >  > Is this still an issue with NetBSD 5.0 for you?
 >   >   
 >   >  Indeed, but i haven't tried 5.0.1 yet.
 >  
 >  If you feel brave, try the new hdaudio(4) in -current; there's talk of
 >  getting it into 5.1.

 I booted the lastest kernel i found on releng, but cgd still isn't enabled in
 the GENERIC kernels. This is an enormous PITA by the way, and i was told some
 time ago that it was to be the default in 5.0 but wasn't.

From: diro@nixsyspaus.org
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/36672 (azalia can not map 64-bit bar on 32-bit platform)
Date: Thu, 28 Jan 2010 09:59:12 -0500

 # uname -a
 NetBSD themobe.lan 5.99.24 NetBSD 5.99.24 (MONOLITHIC) #0: Wed Jan 27 03:45:47
 UTC 2010
 builds@b7.netbsd.org:/home/builds/ab/HEAD/i386/201001270000Z-obj/home/builds/ab/HEAD/src/sys/arch/i386/compile/MONOLITHIC
 i386

 hdaudio0 at pci0 dev 27 function 0: HD Audio Controller
 hdaudio0: interrupting at ioapic0 pin 16
 hdaudio0: timeout leaving reset state
 hdaudio0: device driver failed to attach

 Getting closer...

 Anything i can to here to help/test?

State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Sat, 30 Jan 2010 18:10:47 +0000
State-Changed-Why:
hdaudio in -current does not work.


From: coypu@sdf.org
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: kern/36672 (azalia can not map 64-bit bar on 32-bit platform)
Date: Mon, 27 May 2019 13:40:09 +0000

 Is this the same issue as
 hdaudio_pci.c v1.9
 use pci_mapreg_type() instead of assuming PCI_MAPREG_TYPE_MEM.
 suggested by riastradh@.

 fixes hdaudio on thinkpad P51 where the registers are mapped
 over 4GB range. probably fixes intel X10-based systems that
 map hdaudio high as well, but i was able to work around that
 in the BIOS. not so for the P51.

 XXX: pullup-7, pullup-8.
 ?

State-Changed-From-To: open->closed
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Mon, 27 May 2019 22:14:50 +0000
State-Changed-Why:
 > Is this the same issue as [...]
Probably; if not that, there was, as I recall, another catastrophic
64-bit bar problem fixed a couple years ago.

Anyway, there's been a ton of water under the bridge so no real point holding
this open.l


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.43 2018/01/16 07:36:43 maya Exp $
$NetBSD: gnats_config.sh,v 1.9 2014/08/02 14:16:04 spz Exp $
Copyright © 1994-2017 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.