From: Alistair John Strachan <alistair@devzero.co.uk>
To: Vadim Dyadkin <dyadkin@lns.pnpi.spb.ru>
Cc: Robert Hancock <hancockr@shaw.ca>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: troubles with r8169
Date: Sun, 12 Aug 2007 21:38:58 +0100 [thread overview]
Message-ID: <200708122138.58405.alistair@devzero.co.uk> (raw)
In-Reply-To: <46BF6853.4020800@lns.pnpi.spb.ru>
On Sunday 12 August 2007 21:06:43 Vadim Dyadkin wrote:
> Robert Hancock пишет:
> > 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.
>
> Thank for your answer. This problem never shows up if I use only nvidia
> driver (the work without network), or if I use only r8169 (without
> x.org). If I use both of them I have the hang. Usually the hang appears
> if OpenGL is used or network rate is maximal. I tested this regimes many
> times before.
If you haven't already, I'd drop linux-bugs@nvidia.com an email to see if they
have any insight. Not that this can't be a kernel bug, just that it's a bit
difficult for kernel developers to debug when you're using a driver for which
we don't have the sources.
As for changing the IRQ assignments, I don't have any immediate suggestions. I
notice that this laptop has a dual core processor, so I'm guessing disabling
APIC isn't an option. Have you tried that anyway, just to see if the IRQ
assignment differs?
--
Cheers,
Alistair.
137/1 Warrender Park Road, Edinburgh, UK.
next prev parent reply other threads:[~2007-08-12 20: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 ` troubles with r8169 Robert Hancock
2007-08-12 20:06 ` Vadim Dyadkin
2007-08-12 20:38 ` Alistair John Strachan [this message]
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=200708122138.58405.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=dyadkin@lns.pnpi.spb.ru \
--cc=hancockr@shaw.ca \
--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.