From: Robert Hancock <hancockr@shaw.ca>
To: Vadim Dyadkin <dyadkin@lns.pnpi.spb.ru>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: troubles with r8169
Date: Sun, 12 Aug 2007 13:38:19 -0600 [thread overview]
Message-ID: <46BF61AB.5060400@shaw.ca> (raw)
In-Reply-To: <fa.BZqd/vLw75Xm+ORj+HLjUzU1hSw@ifi.uio.no>
Vadim Dyadkin wrote:
> Hi!
>
> I need help from developers, may be, because I have some troubles with
> r8169 card.
> I use laptop ASUS a6tc. The network card in this laptop is r8169. Video
> is GeForce Go 7300. When I load linux (I use linux almost always), the
> network and video cards take the same IRQ every time.
> ************************
> # cat /proc/interrupts
> CPU0 CPU1
> 0: 3530622 177152 XT-PIC-XT timer
> 1: 1910 9 IO-APIC-edge i8042
> 8: 1 1 IO-APIC-edge rtc
> 9: 41627 115 IO-APIC-fasteoi acpi
> 12: 122 10 IO-APIC-edge i8042
> 14: 38 12 IO-APIC-edge ide0
> 15: 53721 8 IO-APIC-edge ide1
> 16: 0 0 IO-APIC-fasteoi yenta
> 17: 34909 1 IO-APIC-fasteoi ohci_hcd:usb1
> 18: 13 1 IO-APIC-fasteoi ehci_hcd:usb2
> 19: 332826 1 IO-APIC-fasteoi nvidia, eth0
> 20: 0 0 IO-APIC-fasteoi sdhci:slot0
> 21: 26981 1 IO-APIC-fasteoi HDA Intel
> NMI: 0 0
> LOC: 177152 3530365
> ERR: 1
> MIS: 0
> **************************
> You can see, now it's 19, sometimes it's 17 or 21, but every time it is
> the same.
> Often, the computer hangs, only the reboot can help. In /var/log/messages:
> ************************
> Jul 14 19:15:29 satah NETDEV WATCHDOG: eth0: transmit timed out
> Jul 14 19:15:32 satah NVRM: Xid (0002:00): 16, Head 00000000 Count 00cfda2c
> Jul 14 19:15:40 satah NVRM: Xid (0002:00): 16, Head 00000000 Count 00cfda2d
> Jul 14 19:15:48 satah NVRM: Xid (0002:00): 16, Head 00000000 Count 00cfda2e
> Jul 14 19:15:56 satah NVRM: Xid (0002:00): 16, Head 00000000 Count 00cfda2f
> Jul 14 19:16:04 satah NVRM: Xid (0002:00): 16, Head 00000000 Count 00cfda30
> Jul 14 19:16:12 satah NVRM: Xid (0002:00): 16, Head 00000000 Count 00cfda31
> Jul 14 19:16:17 satah NETDEV WATCHDOG: eth0: transmit timed out
> Jul 14 19:16:20 satah NVRM: Xid (0002:00): 16, Head 00000000 Count 00cfda32
> Jul 14 19:16:35 satah NETDEV WATCHDOG: eth0: transmit timed out
> Jul 14 19:16:53 satah NETDEV WATCHDOG: eth0: transmit timed out
> ****************************
> There's no such problem in windows. Could you help me with it?
This could well be a problem with the nvidia driver as it shares the
same IRQ. The first step would be to see if the problem still shows up
without the nvidia binary module loaded.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-08-12 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.BZqd/vLw75Xm+ORj+HLjUzU1hSw@ifi.uio.no>
2007-08-12 19:38 ` Robert Hancock [this message]
2007-08-12 20:06 ` troubles with r8169 Vadim Dyadkin
2007-08-12 20:38 ` Alistair John Strachan
2007-08-12 20:58 ` Vadim Dyadkin
2007-08-12 18:37 Vadim Dyadkin
2007-08-12 22:32 ` Francois Romieu
2007-08-13 6:23 ` Vadim Dyadkin
2008-03-31 21:58 ` Yinghai Lu
2008-03-31 21:58 ` Yinghai Lu
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=46BF61AB.5060400@shaw.ca \
--to=hancockr@shaw.ca \
--cc=dyadkin@lns.pnpi.spb.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.