mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jiri Kosina <jkosina@suse.cz>
To: "Brandeburg, Jesse" <jesse.brandeburg@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	agospoda@redhat.com, "Ronciak, John" <john.ronciak@intel.com>,
	"Allan, Bruce W" <bruce.w.allan@intel.com>,
	"Graham, David" <david.graham@intel.com>,
	kkiel@suse.de, Thomas Gleixner <tglx@linutronix.de>,
	chris.jones@canonical.com, arjan@linux.jf.intel.com
Subject: Re: e1000e NVM corruption issue status
Date: Mon, 29 Sep 2008 18:20:50 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.1.10.0809291817130.4022@jikos.suse.cz> (raw)
In-Reply-To: <alpine.LNX.1.10.0809291740140.4022@jikos.suse.cz>

On Mon, 29 Sep 2008, Jiri Kosina wrote:

> > in case your mailer hoses something apply in this order:
> > # This series applies on GIT commit 011fcfcb75311c7368f13170b9e68adcf146a557
> > 01-e-mem.patch
> > 02-e_flash.patch
> > 03-e1000e-release-lock-in-reset.patch
> > 04-e1000e-dont-sleep.patch
> > 05-e1000e-no-deeplocks.patch
> > 06-e1000e-drop-stats-lock.patch
> > 07-subject-e1000e-debug-patch.patch
> > 08-e1000e-version.patch
> > 09-e1000e-allow-bad-checksum.patch
> > 10-e1000e-dump-eeprom-to-dmesg.txt
> When using this patchset (plus patch that adds check for address range in 
> pci_mmap_resource() by Jesse Barnes), the machine (that already has 
> corrupted (but not completely erased)) hangs after dumping eeprom 
> contents:
> 0000:00:19.0: 0000:00:19.0: The NVM Checksum Is Not Valid
> /*********************/
> Current EEPROM Checksum : 0x2259
> Calculated              : 0xa259
> Offset    Values
> ========  ======
> 00000000: 00 15 58 c6 4a ff 00 08 ff ff 30 00 ff ff ff ff
> 00000010: ff ff ff ff c7 10 b9 20 aa 17 49 10 86 80 00 00
> 00000020: 01 0d 00 00 00 00 05 16 20 50 00 38 00 00 8b 0d
> 00000030: 02 06 c1 01 03 08 00 00 00 00 00 00 00 00 00 00
> 00000040: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00000050: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 00000060: 00 01 00 40 28 12 07 40 ff ff ff ff ff ff ff ff
> 00000070: ff ff ff ff ff ff ff ff ff ff ff ff ff ff 59 22
> /*********************/
> after this, alt-sysrq-p indicates that it's somehow running in the loops 
> around r1000_read_nvm_ich8lan and e1000_release_swflag_uch8lan. Below 
> there are several subsequent alt-sysrq-p outputs on this frozen system

And I believe that this is because of this code in 
09-e1000e-allow-bad-checksum.patch:

        for (i = 0;; i++) {
                if (e1000_validate_nvm_checksum(hw) >= 0) {
                        /* copy the MAC address out of the NVM */
                        if (e1000e_read_mac_addr(&adapter->hw))
                                e_err("NVM Read Error reading MAC address\n");
                        break;
                }
                if (i == 2) {
                        e_err("The NVM Checksum Is Not Valid\n");
                        e1000e_dump_eeprom(adapter);
                        /*
                         * set MAC address to all zeroes to invalidate and
                         * temporary disable this device for the user. This
                         * blocks regular traffic while still permitting
                         * ethtool ioctls from reaching the hardware as well as
                         * allowing the user to run the interface after
                         * manually setting a hw addr using
                         * `ip link set address`
                         */
                        memset(hw->mac.addr, 0, netdev->addr_len);
                }
        }

We are missing 'break;' after the memset, and that is where the hanging 
machine comes from (the loop keeps spinning forever), right? I will verify 
this right away.

-- 
Jiri Kosina
SUSE Labs

  reply	other threads:[~2008-09-29 16:21 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <987CEB09A2567F4A963E1E226364E2D33A685B4B@orsmsx418.amr.corp.intel.com>
2008-09-26  1:50 ` Brandeburg, Jesse
2008-09-26  1:58   ` Chris Snook
2008-09-26  2:04     ` Brandeburg, Jesse
2008-09-26  2:01   ` Brandeburg, Jesse
2008-09-26  2:09     ` Brandeburg, Jesse
2008-09-26  7:12       ` Ingo Molnar
2008-09-26  2:09     ` Brandeburg, Jesse
2008-09-26  2:10     ` Brandeburg, Jesse
2008-09-26  2:10     ` Brandeburg, Jesse
2008-09-26  2:10     ` Brandeburg, Jesse
2008-09-26  2:11     ` Brandeburg, Jesse
2008-09-26  2:11     ` Brandeburg, Jesse
2008-09-26  2:12     ` Brandeburg, Jesse
2008-09-26  2:12     ` Brandeburg, Jesse
2008-09-26  2:13     ` Brandeburg, Jesse
2008-09-26  2:13     ` Brandeburg, Jesse
2008-09-29 15:52       ` Jiri Kosina
2008-09-29 16:20         ` Jiri Kosina [this message]
2008-09-29 16:24           ` Brandeburg, Jesse
2008-09-29 17:18             ` Jiri Kosina
2008-09-29 17:36               ` Jiri Kosina
2008-09-29 22:43                 ` Jiri Kosina
2008-09-26  6:13     ` Jiri Kosina
2008-09-26 11:49       ` Arjan van de Ven
2008-09-26 17:52         ` Jesse Barnes
2008-09-26 18:23           ` Jesse Barnes
2008-09-26 18:39             ` Jesse Barnes
2008-09-26 18:43               ` Jesse Barnes
2008-09-26 18:53             ` Tim Gardner
2008-09-26 22:04               ` Krzysztof Halasa
2008-09-26 22:23                 ` Brandeburg, Jesse
2008-09-27 18:45                   ` Krzysztof Halasa
2008-09-27  0:05               ` Brandeburg, Jesse
2008-09-27  4:20                 ` Tim Gardner
2008-09-26 14:23     ` Karsten Keil
2008-09-26  5:44   ` Jesse Brandeburg
2008-09-26  7:19   ` Karsten Keil
2008-10-18 19:13   ` James Courtier-Dutton
2008-10-18 22:49     ` Jiri Kosina

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=alpine.LNX.1.10.0809291817130.4022@jikos.suse.cz \
    --to=jkosina@suse.cz \
    --cc=agospoda@redhat.com \
    --cc=arjan@linux.jf.intel.com \
    --cc=bruce.w.allan@intel.com \
    --cc=chris.jones@canonical.com \
    --cc=david.graham@intel.com \
    --cc=jesse.brandeburg@intel.com \
    --cc=john.ronciak@intel.com \
    --cc=kkiel@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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

all inboxes | Powered by JetHome®