All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: netdev@oss.sgi.com, linuxppc-dev@ozlabs.org
Subject: kernel crash with G5 Xserve and sungem driver
Date: Fri, 01 Oct 2004 10:35:52 -0600	[thread overview]
Message-ID: <415D8768.8080808@nortelnetworks.com> (raw)


I have patched 2.6.9-rc2 to run in 32-bit mode on the G5 Xserve.

When I compile a kernel with the tigon driver and the sungem driver both 
built-in, the kernel crashes.  Removing the sungem driver fixes the problem.

Is there a known incompatibility between the sungem driver and the Xserve?

I don't have crash output at the moment, but I can probably get it eventually.

Chris

WARNING: multiple messages have this Message-ID (diff)
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: netdev@oss.sgi.com, linuxppc-dev@ozlabs.org
Subject: kernel crash with G5 Xserve and sungem driver
Date: Fri, 01 Oct 2004 10:35:52 -0600	[thread overview]
Message-ID: <415D8768.8080808@nortelnetworks.com> (raw)


I have patched 2.6.9-rc2 to run in 32-bit mode on the G5 Xserve.

When I compile a kernel with the tigon driver and the sungem driver both 
built-in, the kernel crashes.  Removing the sungem driver fixes the problem.

Is there a known incompatibility between the sungem driver and the Xserve?

I don't have crash output at the moment, but I can probably get it eventually.

Chris

             reply	other threads:[~2004-10-01 16:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-01 16:35 Chris Friesen [this message]
2004-10-01 16:35 ` kernel crash with G5 Xserve and sungem driver Chris Friesen
2004-10-01 19:31 ` Harald Welte
2004-10-01 19:42   ` Chris Friesen
2004-10-01 19:46     ` Harald Welte
2004-10-02 11:50       ` Benjamin Herrenschmidt
2004-10-02 11:50         ` Benjamin Herrenschmidt

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=415D8768.8080808@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=netdev@oss.sgi.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 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.