All of lore.kernel.org
 help / color / mirror / Atom feed
From: augustus@linuxhardware.org
To: Jeff Garzik <jgarzik@pobox.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Via Velocity Concerns
Date: Thu, 15 Jul 2004 08:10:18 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0407150807200.7017@penguin.linuxhardware.org> (raw)
In-Reply-To: <40F621B9.7020407@pobox.com>

I just tried his 2.6.8-rc1-mm1 and it doesn't fix it.  In fact, EHCI USB 
support seems to hang.  I disabled it and it booted to the same point as 
before and kernel paniced.  FYI, the driver also didn't compile cleanly.  
I had to add a member to a struct to get it to compile correctly.  I'll 
get you specifics on that if needed but it's very easy to spot if you 
attempt to compile the driver.  Where should I go from here?  I can work 
on getting the info from the panic but since the system is almost dead at 
that point cutting and pasting is not an option.

Thanks,
Kris Kersey (Augustus)
LinuxHardware.org Site Manager
augustus@linuxhardware.org
Gentoo Linux AMD64 Developer
augustus@gentoo.org

On Thu, 15 Jul 2004, Jeff Garzik wrote:

> augustus@linuxhardware.org wrote:
> > I am testing the via velocity gigabit ethernet drivers in the 2.6.8-rc1 
> > kernel.  It seems to work fine unless it is compiled into the kernel.  If 
> > it is compiled in then it kernel panics as soon as it tries to bring up 
> > the device with dhcpcd.  If you load the driver as a module though, all is 
> > fine.
> 
> Try the updated velocity driver in Andrew's -mm tree.
> 
> 	Jeff
> 
> 
> 

      reply	other threads:[~2004-07-15 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-15  3:40 Via Velocity Concerns augustus
2004-07-15  6:18 ` Jeff Garzik
2004-07-15 12:10   ` augustus [this message]

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=Pine.LNX.4.58.0407150807200.7017@penguin.linuxhardware.org \
    --to=augustus@linuxhardware.org \
    --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 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.