From: "Hassard, Stephen" <SHassard@angio.com>
To: "'Jeff Garzik'" <jgarzik@pobox.com>
Cc: "'linux-kernel@vger.kernel.org'" <linux-kernel@vger.kernel.org>
Subject: RE: Communication problem with via-rhine in kernel-2.6.0-test3-bk 3+
Date: Mon, 18 Aug 2003 08:47:23 -0700 [thread overview]
Message-ID: <E2B3FD6B3FF2804CB276D9ED037268354FF6FB@mail4.angio.com> (raw)
Hi Jeff,
"acpi=off" seems to fix it. I guess a change in the ACPI code betweek
2.6.0-test3-bk2 and bk3 broke ACPI on my machine ..
Thanks,
Steve
> -----Original Message-----
> From: Jeff Garzik [mailto:jgarzik@pobox.com]
> Sent: Monday, August 18, 2003 8:40 AM
> To: Hassard, Stephen
> Cc: 'linux-kernel@vger.kernel.org'
> Subject: Re: Communication problem with via-rhine in
> kernel-2.6.0-test3-bk3+
>
>
> On Mon, Aug 18, 2003 at 08:28:24AM -0700, Hassard, Stephen wrote:
> > Hi all,
> >
> > I've been happily using the Rhine-II NIC on my VIA Epia-800 with
> > 2.6.0-test3, but ever since bk3 via-rhine seems to be broken.
> > 2.6.0-test3-bk2 works without problems.
> >
> > I've contacted the driver maintainer, Roger Luethi, and he
> mentioned that if
> > it was a problem since 2.6.0-test3, I should contact the
> kernel mailing
> > list.
> >
> > The interface is detected properly, but no data is
> transmitted. DHCP doesn't
> > work. When I manually configure the interface and try to
> send data, I get
> > the following error, which repeats:
> > >>
> > eth0: Transmit timed out, status 1003, PHY status 786d, resetting...
> > eth0: Setting full-duplex based on MII #1 link partner
> capability of 45e1.
> > <<
>
> Does booting with "pci=noapic" or "acpi=off" or "noapic" help?
>
> Jeff
>
>
>
reply other threads:[~2003-08-18 15:49 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E2B3FD6B3FF2804CB276D9ED037268354FF6FB@mail4.angio.com \
--to=shassard@angio.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@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 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).