public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dirk Behme <dirk.behme@de.bosch.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Ethernet issue in most recent git?
Date: Thu, 19 Jan 2006 10:12:07 -0800	[thread overview]
Message-ID: <20060119181207.GI4425@atomide.com> (raw)
In-Reply-To: <43CFD135.4090604@de.bosch.com>

Hi,

* Dirk Behme <dirk.behme@de.bosch.com> [060119 09:55]:
> Hi,
> 
> has anybody else problems with ethernet with 2.6.16-rc1-omap1 on OSK?
> 
> # mount -t nfs -o nolock 192.0.0.1:/home/omap_linux/nfs /mnt/nfs
> NETDEV WATCHDOG: eth0: transmit timed out
> mount: RPC: Unable to receive; errno = No route to host
> mount: nfsmount failed: Bad file descriptor
> mount: Mounting 192.0.0.1:/home/omap_linux/nfs on /mnt/nfs failed: 
> Invalid argument
> # ifconfig
> eth0      Link encap:Ethernet  HWaddr 00:0E:99:02:02:42
>           inet addr:192.0.0.2  Bcast:192.0.0.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:0 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:20 errors:1 dropped:0 overruns:0 carrier:1
>           collisions:0 txqueuelen:1000
>           RX bytes:0 (0.0 B)  TX bytes:840 (840.0 B)
>           Interrupt:160 Base address:0x1300 DMA chan:ff
> # cat /proc/interrupts
>            CPU0
> ...
> 160:          1   eth0
> ...
> Err:          0
> 
> Telnet and ping don't work as well. I imagine that I doesn't change any 
> configuration, only kernel update form git. UBoots tftpboot works quite 
> well.

Same problem here. I'd assume it's the recent "IRQ type flags" patch
that does not work properly for omap gpio interrupts.

Tony

  parent reply	other threads:[~2006-01-19 18:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-19 17:49 Ethernet issue in most recent git? Dirk Behme
2006-01-19 18:11 ` Anderson Briglia
2006-01-19 19:48   ` Tony Lindgren
2006-01-19 18:12 ` Tony Lindgren [this message]
2006-01-19 20:12   ` Dirk Behme
2006-01-19 21:58     ` Tony Lindgren
2006-01-19 23:21       ` Tony Lindgren

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=20060119181207.GI4425@atomide.com \
    --to=tony@atomide.com \
    --cc=dirk.behme@de.bosch.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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