linux-kernel - Re: 3.12: ethernet controller missing after resuming from suspend to RAM

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <52FA6881.4030602@gmail.com>
Date:	Tue, 11 Feb 2014 19:14:25 +0100
From:	Bastien Traverse <bastien.traverse@...il.com>
To:	Peter Wu <lekensteyn@...il.com>
CC:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	linux-kernel@...r.kernel.org, francis.moro@...il.com,
	Linux PM list <linux-pm@...r.kernel.org>
Subject: Re: 3.12: ethernet controller missing after resuming from suspend
 to RAM

Le 09/02/2014 23:07, Peter Wu a écrit :
> I think this is relevant. See also my test with 3.13.2 and different
> kernel configs[1]. A workaround that triggers a scan was also posted[2].
> 
> Peter
> 
>  [1]: http://lkml.org/lkml/2014/2/8/264
>  [2]: http://lkml.org/lkml/2014/2/7/809

Thanks, I can confirm that triggering a rescan by issuing

  sudo tee /sys/devices/pci0000:00/0000:00:1c.1/rescan <<<1

made the device reappear on my system (of course I had to adapt the
command to match PCI Bridge number). That's a handy workaround, it
avoids restarting each time.

As I've never compiled a kernel so far I think I'll leave the
configuration tweaks for another time :)

Cheers
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/