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]
Date:	Sun, 09 Feb 2014 19:44:27 +0100
From:	Bastien Traverse <bastien.traverse@...il.com>
To:	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	Peter Wu <lekensteyn@...il.com>
CC:	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 07/02/2014 02:19, Rafael J. Wysocki a écrit :
> Please send the output of lspci -vv right before suspend and right after
> the subsequent resume as attachments.

You'll find them attached, but I got a strange error when I wanted to
run it as root:
$ sudo lspci -vv > lspci_vv_before
pcilib: sysfs_read_vpd: read failed: Connection timed out
$ sudo -i
# lspci -vv
pcilib: sysfs_read_vpd: read failed: Connection timed out

So I only got the unpriviledge output.

Some complementary lines from my journal:

kernel: r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
kernel: r8169 0000:03:00.2: can't disable ASPM; OS doesn't have ASPM control
kernel: pcieport 0000:00:1c.3: driver skip pci_set_master, fix it!
kernel: r8169 0000:03:00.2: irq 44 for MSI/MSI-X
kernel: r8169 0000:03:00.2 eth0: RTL8411 at 0xffffc90016ed4000,
00:90:f5:d7:34:53, XID 08800800 IRQ 44
kernel: r8169 0000:03:00.2 eth0: jumbo features [frames: 9200 bytes, tx
checksumming: ko]
kernel: rtsx_pci 0000:03:00.0: irq 45 for MSI/MSI-X
kernel: rtsx_pci 0000:03:00.0: rtsx_pci_acquire_irq: pcr->msi_en = 1,
pci->irq = 45
...

And one I thought of interest:

kernel: rtsx_pci 0000:03:00.0: vpd r/w failed.  This is likely a
firmware bug on this device.  Contact the card vendor for a firmware update.

That came three times before suspend.

Only two lines about hotplug, none special.

Stripped journal attached for the suspend cycle.


Le 07/02/2014 08:29, Francis Moreau a écrit :
> yeah, but calling this "fast resolution" is quite incorrect.
>
> I don't blame anyone for this and I'm quite happy that a workaround has
> been found at last but calling this "fast resolution" is a bit funny
> compare to the PITA it was to debug this.

Sorry, I didn't mean to underestimate the amount of work you put in that
bug resolution (actually it was the first time I heard of kernel
bisection and was pretty impressed by how you led it).
What made me say it had been a fast resolution is that its fix was
included right in the next kernel revision, which I found to be quite
diligent. But the actual work to find it, the kernel bisection, that
must have been a real sweat.


Thanks

View attachment "lspci_vv_before" of type "text/plain" (10912 bytes)

View attachment "lspci_vv_after" of type "text/plain" (9641 bytes)

View attachment "journalctl_-b_suspend_cycle" of type "text/plain" (20496 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ