From: Sukadev Bhattiprolu <sukadev@us.ibm.com>
To: Auke Kok <auke-jan.h.kok@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [BUG] 2.6.20-rc4-mm1: Panic in e1000_write_vfta_82543()
Date: Thu, 18 Jan 2007 18:21:24 -0800 [thread overview]
Message-ID: <20070119022124.GA8087@us.ibm.com> (raw)
In-Reply-To: <45B02510.7050604@intel.com>
Auke Kok [auke-jan.h.kok@intel.com] wrote:
| Sukadev Bhattiprolu wrote:
| >I get following panic on 2.6.20-rc4-mm1 on a 2-cpu AMD Opteron system.
| >
| >Same basic config file seems to work with 2.6.20-rc2-mm1 on this same
| >system. Have not tried -rc3-mm1 yet.
| >
| >Attached are config file and "lspci -vv" output. Let me know if you need
| >more info.
| >
| >Suka
| >
| >---
| >
| >[ 168.925840] Freeing unused kernel memory: 320k freed
| > * INIT: version 2.86 booting
| > * Starting basic networking... [
| > ok ]
| > * Starting kernel event manager... [
| > ok ]
| > * Loading hardware drivers... [
| > ok ]
| > * Starting PCMCIA services... * PCMCIA not present
| > * Loading manual drivers... [
| > ok ]
| >[ 171.575122] Unable to handle kernel paging request at ffffc20100ec55fc
| >RIP:
| >[ 171.584632] [<ffffffff804a9858>] e1000_write_vfta_82543+0x58/0xd0
...
| >[ 171.698208] Call Trace:
| >[ 171.698216] [<ffffffff804c103d>] e1000_vlan_rx_register+0x1dd/0x210
| >[ 171.698219] [<ffffffff804c3195>] e1000_up+0x35/0x4b0
| >[ 171.698222] [<ffffffff804c3724>] e1000_open+0x74/0x100
| >[ 171.698227] [<ffffffff805626fe>] dev_open+0x3e/0xa0
| >[ 171.698230] [<ffffffff8056184f>] dev_change_flags+0x6f/0x160
| >[ 171.698234] [<ffffffff805a5174>] devinet_ioctl+0x2d4/0x6e0
| >[ 171.698238] [<ffffffff803f7e01>] __up_read+0x21/0xb0
| >[ 171.698243] [<ffffffff8055664c>] sock_ioctl+0x1fc/0x230
| >[ 171.698247] [<ffffffff8029dc0f>] do_ioctl+0x2f/0xa0
| >[ 171.698249] [<ffffffff8029df3b>] vfs_ioctl+0x2bb/0x2f0
| >[ 171.698252] [<ffffffff8029dfb9>] sys_ioctl+0x49/0x80
| >[ 171.698256] [<ffffffff805e375d>] error_exit+0x0/0x84
| >[ 171.698259] [<ffffffff802098be>] system_call+0x7e/0x83
| >[ 171.698261]
| >[ 171.698262]
| >[ 171.698262] Code: 44 8b 20 e8 30 7e 00 00 83 bb 94 01 00 00 03 75 3c 83
| >e5 01
| >[ 171.698268] RIP [<ffffffff804a9858>] e1000_write_vfta_82543+0x58/0xd0
| >[ 171.698273] RSP <ffff81007dfc5cf8>
| >[ 171.698274] CR2: ffffc20100ec55fc
| >[ 171.698276] <6>EXT3 FS on sda1, internal journal
|
| Hi,
|
| I believe this is one of the bugs that is fixed in the patch that I sent
| monday. Please
| try again with the patch applied to your tree and re-test. Thanks. I didn't
| see Andrew
| merge the patch yet.
|
| see: http://lkml.org/lkml/2007/1/16/226
|
| I can mail the patch if you can't find it. Just ping me privately.
Yep. Seems to fix the crash. Thanks !
Suka
|
| Cheers,
|
| Auke
prev parent reply other threads:[~2007-01-19 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-19 1:17 [BUG] 2.6.20-rc4-mm1: Panic in e1000_write_vfta_82543() Sukadev Bhattiprolu
2007-01-19 1:55 ` Auke Kok
2007-01-19 2:21 ` Sukadev Bhattiprolu [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=20070119022124.GA8087@us.ibm.com \
--to=sukadev@us.ibm.com \
--cc=akpm@osdl.org \
--cc=auke-jan.h.kok@intel.com \
--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 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).