linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-dev@ozlabs.org
Subject: Re: AMCC yosemite 440ep PCI slot doesn't work.
Date: Mon, 24 Sep 2007 13:14:17 +0200	[thread overview]
Message-ID: <200709241314.18123.sr@denx.de> (raw)
In-Reply-To: <46F784B0.1040600@windriver.com>

On Monday 24 September 2007, Andrew Liu wrote:
> By default, it is IRQ_SENSE_LEVEL | IRQ_POLARITY_NEGATIVE

And that should be correct for PCI interrupts.

>  I change it to IRQ_SENSE_EDGE | IRQ_POLARITY_NEGATIVE  or
> IRQ_SENSE_EDGE | IRQ_POLARITY_POSITIVE.
> It  displays:
> eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
> eth2: no IPv6 routers present
> NETDEV WATCHDOG: eth2: transmit timed out
> eth2: Transmit timeout, status 0c 0005 c07f media 10.
> eth2: Tx queue start entry 4  dirty entry 0.
> eth2:  Tx descriptor 0 is 0008a05a. (queue head)
> eth2:  Tx descriptor 1 is 0008a04e.
> eth2:  Tx descriptor 2 is 0008a046.
> eth2:  Tx descriptor 3 is 0008a05a.
> eth2: link up, 100Mbps, full-duplex, lpa 0x45E1
>
> and
> root@localhost:/root> ifconfig  eth2
> eth2      Link encap:Ethernet  HWaddr 00:0E:2E:7E:F5:E6
>           inet addr:128.224.149.13  Bcast:128.224.255.255  Mask:255.255.0.0
>           inet6 addr: fe80::20e:2eff:fe7e:f5e6/64 Scope:Link
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>           Interrupt:25 Base address:0x6f00
>
>
> and
> root@localhost:/root> cat /proc/interrupts
>            CPU0
>   2:          0  UIC0 Edge      IBM IIC
>   7:          0  UIC0 Edge      IBM IIC
>  10:      11961  UIC0 Edge      MAL TX EOB
>  11:      18471  UIC0 Edge      MAL RX EOB
>  25:          0  UIC0 Edge      eth2
>  32:          0  UIC1 Edge      MAL SERR
>  33:          0  UIC1 Edge      MAL TX DE
>  34:          0  UIC1 Edge      MAL RX DE
>  40:         32  UIC1 Edge      ohci_hcd:usb1
>  60:          0  UIC1 Edge      EMAC
> BAD:          0
>
>
> Can PCI slot use level trigger?
>
> give me some advice.

Hmmm. Did you try an earlier Linux version too? For example 2.6.22 or even 
earlier? Please give it a try and let us know if the same problem occurs.

Best regards,
Stefan

=====================================================================
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80  Email: office@denx.de
=====================================================================

  reply	other threads:[~2007-09-24 11:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-21 10:53 AMCC yosemite 440ep PCI slot doesn't work Andrew Liu
2007-09-21 15:14 ` Valentine Barshak
2007-09-24  9:34   ` Andrew Liu
2007-09-24 11:14     ` Stefan Roese [this message]
2007-09-24 11:20       ` Valentine Barshak
2007-09-25  2:05         ` Andrew Liu
2007-09-25  2:02       ` Andrew Liu
2007-09-25  5:18         ` Stefan Roese
2007-09-25 13:21           ` Stefan Roese

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200709241314.18123.sr@denx.de \
    --to=sr@denx.de \
    --cc=linuxppc-dev@ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).