netdev - Re: i217-LM boot wreckage

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.DEB.2.02.1403201431580.18573@ionos.tec.linutronix.de>
Date:	Thu, 20 Mar 2014 14:45:19 +0100 (CET)
From:	Thomas Gleixner <tglx@...utronix.de>
To:	netdev@...r.kernel.org
cc:	todd.fujinaka@...el.com, e1000-devel@...ts.sourceforge.net
Subject: Re: i217-LM boot wreckage

On Thu, 20 Mar 2014, Thomas Gleixner wrote:
> So it looks like the BIOS is setting something up, when the cable is
> plugged at power on time, which is not visible through our debug
> output.

Some more info:

I prevented e1000e from being autoloaded and booted with the cable
unplugged.

T1:
  Plug cable 
  modprobe e1000e	-> Works

T2:
  modprobe e1000e
  plug cable		-> Works not

  rmmod e1000e
  modprobe e1000e	-> works not

  unplug cable
  rmmod e1000e
  modprobe e1000e	-> works

  rmmod e1000e
  unplug cable     
  modprobe e1000e
  plug cable		-> Works not

  rmmod e1000e
  unplug cable     
  plug cable
  modprobe e1000e	-> Works not

So if the module is loaded w/o the cable plugged it does not work. If
I unplug before unloading the module and then plug in before loading
the module again it works again.

Thanks,

	tglx

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html