NetBSD Problem Report #18094

Received: (qmail 23350 invoked by uid 605); 28 Aug 2002 07:17:33 -0000
Message-Id: <20020828071731.EDC9D11122@narn.netbsd.org>
Date: Wed, 28 Aug 2002 00:17:31 -0700 (PDT)
From: jarkko.teppo@er-grp.com
Sender: gnats-bugs-owner@netbsd.org
Reply-To: jarkko.teppo@er-grp.com
To: gnats-bugs@gnats.netbsd.org
Subject: Kernel panic with homepna card on Alpha 500/500
X-Send-Pr-Version: www-1.0

>Number:         18094
>Category:       kern
>Synopsis:       Kernel panic with homepna card on Alpha 500/500
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    kern-bug-people
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Aug 28 07:18:00 +0000 2002
>Closed-Date:    
>Last-Modified:  Fri Apr 09 15:10:03 +0000 2010
>Originator:     Jarkko Teppo
>Release:        1.6RC1
>Organization:
none
>Environment:
>Description:
I have a noname homepna-card on a 500/500 (1.6RC1, 1.6F) and it's
causing me some headache.
After enabling vr* and adding all the available PHYs and

 pnaphy* at mii? phy ?

I got this: (the short version, due to 4k dmesg)
..
..
..
Digital Equipment DECchip 21030 ("TGA") (miscellaneous display, revision
0x03) a
t ? dev 7 function 0 (intrswiz 0, intrpin 0x1, i/o on, mem on, no quirks):
DC210
30 step C, board type T8-02
tga0: 1280 x 1024, 8bpp, Bt485 RAMDAC
tga0: interrupting at kn20aa irq 8
wsdisplay0 at tga0 kbdmux 1: console (std, vt100 emulation)
wsmux1: connecting to wsdisplay0
vr0 at pci0 dev 8 function 0: PCI configuration registers:
  Common header:
    0x00: 0x30651106 0x02100047 0x02000042 0x0000f800

    Vendor Name: VIA Technologies (0x1106)
    Device Name: VT6102 (Rhine II) 10/100 Ethernet (0x3065)
    Command register: 0x0047
      I/O space accesses: on
      Memory space accesses: on
      Bus mastering: on
      Special cycles: off
      MWI transactions: off
      Palette snooping: off
      Parity error checking: on
      Address/data stepping: off
      System error (SERR): off
      Fast back-to-back transactions: off
    Status register: 0x0210
      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: medium (0x1)
      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: 0x42
    BIST: 0x00 
    Header Type: 0x00 (0x00)
    Latency Timer: 0xf8
    Cache Line Size: 0x00

  Type 0 ("normal" device) header:
    0x10: 0x00010301 0x80071000 0x00000000 0x00000000
    0x20: 0x00000000 0x00000000 0x00000000 0xab2113d1
    0x30: 0x00000000 0x00000040 0x00000000 0x080301a0

    Base address register at 0x10 
      type: 32-bit i/o
      base: 0x00010300, size: 0x00000100
    Base address register at 0x14
      type: 32-bit nonprefetchable memory
      base: 0x80071000, size: 0x00000100
    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: 0x13d1
Subsystem ID: 0xab21 
    Expansion ROM Base Address: 0x00000000
    Capability list pointer: 0x40
    Reserved @ 0x38: 0x00000000
    Maximum Latency: 0x08
    Minimum Grant: 0x03
    Interrupt pin: 0x01 (pin A)
    Interrupt line: 0xa0
    Capability register at 0x40
      type: 0x01 (Power Management, rev. 1.0)

  Device-dependent header:
    0x40: 0x7e020001 0x00000000 0x00000000 0x00000000
    0x50: 0x00000000 0x00000000 0x00000000 0x00000000
    0x60: 0x00000000 0x00000000 0x00000000 0x00000000
    0x70: 0x00000000 0x00000000 0x00000000 0x00000000
    0x80: 0x00000000 0x00000000 0x00000000 0x00000000
    0x90: 0x00000000 0x00000000 0x00000000 0x00000000
    0xa0: 0x00000000 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

    Don't know how to pretty-print device-dependent header.

VIA Technologies VT6102 (Rhine II) 10/100 Ethernet (ethernet network,
revision 0
x42) at ? dev 8 function 0 (intrswiz 0, intrpin 0x1, i/o on, mem on, no
quirks):
 VIA VT6102 (Rhine II) 10/100 Ethernet
vr0: interrupting at kn20aa irq 16
vr0: Ethernet address: 00:e0:98:9d:e2:1c
pnaphy0 at vr0 phy 2: Am79C901 HomePNA 1.0 interface, rev. 4
pnaphy0: 10baseT
OUI 0x000058 model 0x0037 rev 1 at vr0 phy 3 not configured
ifmedia_set: no match for 0x20/0xffffffff
panic: ifmedia_set 
halted.

cpu_Debugger()
panic()
ifmedia_set()
vr_attach()
config_attach()
config_found_sm()
pci_probe_device()
..  
..  
..

Please note that ukphy was not enabled as it paniced with it as well.

I found another similar problem on the mailing-lists:
http://mail-index.netbsd.org/tech-kern/2002/04/25/0003.html

>How-To-Repeat:
Try a similar noname card.
>Fix:

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Tue, 12 Jan 2010 06:25:26 +0000
State-Changed-Why:
Does this still happen? Quite a lot has changed since 2002.


State-Changed-From-To: feedback->open
State-Changed-By: dholland@NetBSD.org
State-Changed-When: Fri, 09 Apr 2010 06:41:06 +0000
State-Changed-Why:
feedback mail is bouncing. does anyone have vr(4) and an alpha to look into
this?


From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
To: gnats-bugs@NetBSD.org
Cc: kern-bug-people@NetBSD.org, netbsd-bugs@NetBSD.org, gnats-admin@NetBSD.org,
        dholland@NetBSD.org, jarkko.teppo@er-grp.com, tsutsui@ceres.dti.ne.jp
Subject: Re: kern/18094 (Kernel panic with homepna card on Alpha 500/500)
Date: Fri, 9 Apr 2010 18:24:59 +0900

 > Synopsis: Kernel panic with homepna card on Alpha 500/500

 It looks submitter didn't enable ukphy(4) and that was the problem.

 ---
 Izumi Tsutsui

From: David Holland <dholland-bugs@netbsd.org>
To: gnats-bugs@NetBSD.org
Cc: 
Subject: Re: kern/18094 (Kernel panic with homepna card on Alpha 500/500)
Date: Fri, 9 Apr 2010 15:05:54 +0000

 On Fri, Apr 09, 2010 at 09:30:05AM +0000, Izumi Tsutsui wrote:
  >  > Synopsis: Kernel panic with homepna card on Alpha 500/500
  >  
  >  It looks submitter didn't enable ukphy(4) and that was the problem.

 Well, the submitter said

  : Please note that ukphy was not enabled as it paniced with it as well.

 so that wasn't the only problem.

 -- 
 David A. Holland
 dholland@netbsd.org

>Unformatted:

Home	PR Database Search