LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Auke Kok <auke-jan.h.kok@intel.com> To: Roger Heflin <rheflin@atipa.com> Cc: NetDev <netdev@vger.kernel.org>, e1000-devel@lists.sourceforge.net, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: Nvidia MCP55 Machine reboots on ixgb driver load Date: Wed, 24 Jan 2007 14:07:11 -0800 [thread overview] Message-ID: <45B7D88F.30703@intel.com> (raw) In-Reply-To: <45B7CA3D.9020601@atipa.com> [added netdev to CC] Roger Heflin wrote: > I have a machine (actually 2 machines) that upon loading > the intel 10GBe driver (ixgb) the machine reboots, I am > using a RHAS4.4 based distribution with Vanilla 2.6.19.2 > (the RHAS 4.4.03 kernel also reboots with the ixgb load), > I don't see any messages on the machine before it reboots, > loading the driver with debug does not appear to produce > any extra messages. The basic steps are the I load > the driver, the machine locks up, and then in a second > or 2 it starts to post. some suggestions immediately come to mind: * have you tried the latest driver from http://e1000.sf.net/ ? * what happens when you unplug the card and modprobe the ixgb module? * have you tried capturing a trace with netconsole or serial console? probing the ixgb driver produces at least 1 syslog line that should show up. If nothing shows up on serial or netconsole, the issue may be way outside the ixgb driver. > I have tried the default ixgb driver in 2.6.19.2, and I > have tried the open source intel driver on RH4.4, both cause > the same reboot. I also tried the linux firmware > development kit, and booting fc6 causes the same reboot > upon the network driver load. just for completeness, which driver versions were this? and when you say "booting fc6" I assume you mean that fc6 boots OK until you modprobe the ixgb driver? > I have tried pci=nomsi try compiling your kernel without MSI support alltogether. There have been serious issues found with MSI on certain configurations, and in your case this might be the cause. Allthough passing pci=nomsi should be the same as compiling it out, it can't hurt to try. > Also note that the linux.nics@intel.com address is apparently > unused and returns an email telling you to use a web page, > and so far after using the web page I have not got any response > indicating that anything got to anyone. I've taken action to get that straightened out. You're always welcome to mail netdev, the e1000 devel list or even lkml which we will all pick up on. I can't think of a specific reason for the issue right now, other than attempting to get a serial/netconsole attached and trying without any msi support in the kernel. Please give that a try and let us know. Auke
next prev parent reply other threads:[~2007-01-24 22:07 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-24 21:06 Nvidia MCP55 Machine reboots on ixgb driver load Roger Heflin 2007-01-24 22:07 ` Auke Kok [this message] 2007-01-24 23:30 ` Roger Heflin 2007-01-24 22:40 ` Jeff V. Merkey 2007-01-24 23:24 ` Roger Heflin
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=45B7D88F.30703@intel.com \ --to=auke-jan.h.kok@intel.com \ --cc=e1000-devel@lists.sourceforge.net \ --cc=linux-kernel@vger.kernel.org \ --cc=netdev@vger.kernel.org \ --cc=rheflin@atipa.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: linkBe 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).