Development of Linux for the HP PA-RISC platform

Unknown device 0x0005f

On Tue, Sep 04, 2007 at 11:44:29PM +0200, Helge Deller wrote:
> Additionally, does someone knows what this device is ?
> > 12. unknown device at 0xf190c000 [10/4/12] { 2, 0x0, 0x004, 0x0005f }

I don't.  We don't have anything with the 0x0005f programming model in
the database.  We have:

        {HPHW_A_DMA, 0x004, 0x00050, 0x80, "Lanbrusca 802.3 (36967A)"}, 
        {HPHW_B_DMA, 0x008, 0x00051, 0x80, "HP-PB Transit 802.3"}, 
        {HPHW_B_DMA, 0x004, 0x00052, 0x80, "Miura LAN/Console (J2146A)"}, 
        {HPHW_A_DMA, 0x004, 0x00056, 0x80, "HP-PB LoQuix FDDI"}, 
        {HPHW_A_DMA, 0x004, 0x00057, 0x80, "HP-PB LoQuix FDDI (28670A)"}, 
        {HPHW_B_DMA, 0x008, 0x00058, 0x80, "HP-PB Transit 802.4"}, 
        {HPHW_A_DMA, 0x004, 0x0005E, 0x00, "Gecko Add-on Token Ring"}, 

The owner could probably help us out by taking a look at the card in
slot 10/4/12 and seeing what chips are on it, and what connectors it has.

--

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

headers

Rob Sciuk | 5 Sep 01:56

Re: Unknown device 0x0005f

On Tue, 4 Sep 2007, Matthew Wilcox wrote:

> Date: Tue, 4 Sep 2007 16:15:37 -0600
> From: Matthew Wilcox <matthew <at> wil.cx>
> To: Helge Deller <deller <at> gmx.de>
> Cc: rob <at> controlq.com, parisc-linux <at> lists.parisc-linux.org,
>     debian-hppa <at> lists.debian.org
> Subject: Unknown device 0x0005f
> 
> On Tue, Sep 04, 2007 at 11:44:29PM +0200, Helge Deller wrote:
>> Additionally, does someone knows what this device is ?
>>> 12. unknown device at 0xf190c000 [10/4/12] { 2, 0x0, 0x004, 0x0005f }
>
> I don't.  We don't have anything with the 0x0005f programming model in
> the database.  We have:
>
>        {HPHW_A_DMA, 0x004, 0x00050, 0x80, "Lanbrusca 802.3 (36967A)"},
>        {HPHW_B_DMA, 0x008, 0x00051, 0x80, "HP-PB Transit 802.3"},
>        {HPHW_B_DMA, 0x004, 0x00052, 0x80, "Miura LAN/Console (J2146A)"},
>        {HPHW_A_DMA, 0x004, 0x00056, 0x80, "HP-PB LoQuix FDDI"},
>        {HPHW_A_DMA, 0x004, 0x00057, 0x80, "HP-PB LoQuix FDDI (28670A)"},
>        {HPHW_B_DMA, 0x008, 0x00058, 0x80, "HP-PB Transit 802.4"},
>        {HPHW_A_DMA, 0x004, 0x0005E, 0x00, "Gecko Add-on Token Ring"},
>
> The owner could probably help us out by taking a look at the card in
> slot 10/4/12 and seeing what chips are on it, and what connectors it has.

I can photograph it, if you like, how does one determine where slot 
10/4/12 is??  I know that there are a couple of mux boards on the back, 
but frankly I haven't opened up the box as of yet.  Pointers?

(Continue reading)

headers

Matthew Wilcox | 5 Sep 03:55

Re: Unknown device 0x0005f

On Tue, Sep 04, 2007 at 07:56:23PM -0400, Rob Sciuk wrote:
> >The owner could probably help us out by taking a look at the card in
> >slot 10/4/12 and seeing what chips are on it, and what connectors it has.
> 
> I can photograph it, if you like, how does one determine where slot 
> 10/4/12 is??  I know that there are a couple of mux boards on the back, 
> but frankly I haven't opened up the box as of yet.  Pointers?

It's been a few years since I looked at the back of a K-class, but I
believe the path '10/4/12' is silk-screened onto the outside of the case
below the slot in question.

--

-- 
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours.  We can't possibly take such
a retrograde step."

headers

Rob Sciuk | 5 Sep 17:01

Re: Unknown device 0x0005f

On Tue, 4 Sep 2007, Matthew Wilcox wrote:

> 
> On Tue, Sep 04, 2007 at 07:56:23PM -0400, Rob Sciuk wrote:
>>> The owner could probably help us out by taking a look at the card in
>>> slot 10/4/12 and seeing what chips are on it, and what connectors it has.
>>
>> I can photograph it, if you like, how does one determine where slot
>> 10/4/12 is??  I know that there are a couple of mux boards on the back,
>> but frankly I haven't opened up the box as of yet.  Pointers?
>
> It's been a few years since I looked at the back of a K-class, but I
> believe the path '10/4/12' is silk-screened onto the outside of the case
> below the slot in question.

The roadmap on the back of the K200 points to the I/O panel, and indeed, 
the 10/4/12 device appears to be a BNC connecter to the AUI for 10Base2 
network adapter (yes, I know, it is ancient -- but it was handy.  I'll 
make up a 10BT cable which can reach the box, and replace the "unknown 
device" with 10BT).  At this point, this unknown device is a red herring 
IMHO.

The problem persists, however, and it seems unrelated to the unknown 
device, which is now lying pathetic, and abandoned on the floor of my 
machine room -- cast into the dust!) and no longer is mentioned in the 
boot log -- the panic occurs at the same spot, after freeing memory.

Rob.

(Continue reading)