NetBSD Problem Report #37984

From tacha@tack.fukui-med.ac.jp  Sat Feb  9 07:19:12 2008
Return-Path: <tacha@tack.fukui-med.ac.jp>
Received: from mail.netbsd.org (mail.netbsd.org [204.152.190.11])
	by narn.NetBSD.org (Postfix) with ESMTP id CF9DA63B853
	for <gnats-bugs@gnats.NetBSD.org>; Sat,  9 Feb 2008 07:19:11 +0000 (UTC)
Message-Id: <20080209055920.03B0323CA0@tamp.fukui-med.ac.jp>
Date: Sat,  9 Feb 2008 14:59:19 +0900 (JST)
From: tacha@tack.fukui-med.ac.jp
Reply-To: tacha@tack.fukui-med.ac.jp
To: gnats-bugs@gnats.NetBSD.org
Subject: current ath(4) does not work properly with Atheros AR5006EX
X-Send-Pr-Version: 3.95

>Number:         37984
>Category:       kern
>Synopsis:       current ath(4) does not work properly with Atheros AR5006EX
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sat Feb 09 07:20:00 +0000 2008
>Closed-Date:    
>Last-Modified:  Thu Apr 21 03:44:25 +0000 2011
>Originator:     tacha@tack.fukui-med.ac.jp
>Release:        NetBSD 4.99.52
>Organization:
-----            : Tatoku Ogaito
   / _  _ |_  _  : Dept. Medical Informatics, University of Fukui
  / (_|(_ | )(_| : E-mail: tacha@tack.fukui-med.ac.jp tacha@NetBSD.org

  *** NetBSD: It'll be there when you're ready for it. ***
>Environment:


System: NetBSD tamp.fukui-med.ac.jp 4.99.52 NetBSD 4.99.52 (TPX61-1.28) #23: Wed Feb 6 22:53:00 JST 2008 tacha@tamp.fukui-med.ac.jp:/usr/current/src/sys/arch/i386/compile/obj.i386/TPX61 i386
Architecture: i386
Machine: i386
>Description:

My Lenovo 802.11a/b/g wireless MINI-PCI Express adotper (PN 40Y7028)
is configured as ath and ifconfig reports correct MAC address etc.
But when invoke "ifconfig ath0 up" kernel reports 

'ath0: ath_chan_set: unable to reset channel 8 (2447 MHz, flags 0x3e0 hal flags 0x140)'

and no wireless connection established. Also, "ifconfig ath0 down up" produce

'ath0: unable to reset hardware; hal status 0'

kernel message. 
Both messages are described in ath(4) as "This should not happen."

Simple google search leads the chip is Atheros AR5006EX but I don't know
that is correct or not.  Here is pcictl output .

# pcictl pci2 dump -d 0
PCI configuration registers:
  Common header:
    0x00: 0x1014168c 0x00100107 0x02000001 0x00000010

    Vendor Name: Atheros Communications (0x168c)
    Device ID: 0x1014
    Command register: 0x0107
      I/O space accesses: on
      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): on
      Fast back-to-back transactions: off
      Interrupt disable: 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: network (0x02)
    Subclass Name: ethernet (0x00)
    Interface: 0x00
    Revision ID: 0x01
    BIST: 0x00
    Header Type: 0x00 (0x00)
    Latency Timer: 0x00
    Cache Line Size: 0x10

  Type 0 ("normal" device) header:
    0x10: 0xf7f00004 0x00000000 0x00000000 0x00000000
    0x20: 0x00000000 0x00000000 0x00005001 0x058a1014
    0x30: 0x00000000 0x00000040 0x00000000 0x0000010b

    Base address register at 0x10
      type: 64-bit nonprefetchable memory
      base: 0x00000000f7f00000, 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: 0x00005001
    Subsystem vendor ID: 0x1014
    Subsystem ID: 0x058a
    Expansion ROM Base Address: 0x00000000
    Capability list pointer: 0x40
    Reserved @ 0x38: 0x00000000
    Maximum Latency: 0x00
    Minimum Grant: 0x00
    Interrupt pin: 0x01 (pin A)
    Interrupt line: 0x0b

  Capability register at 0x40
    type: 0x01 (Power Management, rev. 1.0)
  Capability register at 0x50
    type: 0x05 (MSI)
  Capability register at 0x60
    type: 0x10 (PCI Express)
  Capability register at 0x90
    type: 0x11 (MSI-X)

  PCI Express Capabilities Register
    Capability version: 1
    Device type: Legcay PCI Express Endpoint device
    Interrupt Message Number: 0
    Slot Control Register:
      Attention Indictor Control: blink
      Power Indictor Control: off
      Power Controller Control: on

  Device-dependent header:
    0x40: 0x01c25001 0x00000000 0x00000000 0x00000000
    0x50: 0x00006005 0x00000000 0x00000000 0x00000000
    0x60: 0x00119010 0x05040cc0 0x000a2010 0x00033c11
    0x70: 0x1011004b 0x00000000 0x000003c0 0x00000000
    0x80: 0x00000000 0x00000000 0x00000000 0x00000000
    0x90: 0x00000011 0x00000000 0x00000000 0x00000000
    0xa0: 0x00000004 0x00000000 0x00000000 0x00000000
    0xb0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xc0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xd0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xe0: 0x00000000 0x00000000 0x00000000 0x00000000
    0xf0: 0x00000000 0x00000000 0x00000000 0x00000000


>How-To-Repeat:

purchase Lenovo 40Y7028 and boot kernel with ath.

>Fix:


>Release-Note:

>Audit-Trail:

State-Changed-From-To: open->feedback
State-Changed-By: jmcneill@NetBSD.org
State-Changed-When: Sun, 20 Feb 2011 12:18:50 +0000
State-Changed-Why:
This chipset should be supported by NetBSD 5.1, can you confirm?


From: Tatoku Ogaito <tacha@tack.m.cii.u-fukui.ac.jp>
To: gnats-bugs@NetBSD.org, jmcneill@NetBSD.org
Cc: kern-bug-people@NetBSD.org, netbsd-bugs@NetBSD.org, gnats-admin@NetBSD.org
Subject: Re: kern/37984 (current ath(4) does not work properly with Atheros
 AR5006EX)
Date: Wed, 23 Feb 2011 00:51:04 +0900 (JST)

 Hi.

 >> In Message <20110220121850.EFBE463B100@www.NetBSD.org>
  at Sun, 20 Feb 2011 12:18:50 +0000 (UTC)
  jmcneill@NetBSD.org wrote:

  > This chipset should be supported by NetBSD 5.1, can you confirm?

 Unfortunately, the situation is almost same with -current as of 2011/01/09.

 First "ifconfig ath0 up" yields the kernel message

 "ath0: ath_chan_set: unable to reset channel 7 (2442 MHz, flags 0x3e0 hal flags 0x140)"

 and following "ifconfig ath0 down up" produces following message. 

 "ath0: unable to reset hardware; hal status 12"

 # Although I am currently happy iwn user, I am willing to check when you need.

 Tacha

State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Thu, 21 Apr 2011 03:44:25 +0000
State-Changed-Why:
Feedback received, still failing.


>Unformatted:

NetBSD Home
NetBSD PR Database Search

(Contact us) $NetBSD: query-full-pr,v 1.39 2013/11/01 18:47:49 spz Exp $
$NetBSD: gnats_config.sh,v 1.8 2006/05/07 09:23:38 tsutsui Exp $
Copyright © 1994-2007 The NetBSD Foundation, Inc. ALL RIGHTS RESERVED.