netdev - PROBLEM: freeze when 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-next>] [day] [month] [year] [list]

Date:	Sun, 11 Nov 2012 20:47:45 +0100
From:	medhefgo@....de
To:	venza@...wnhat.org
Cc:	netdev@...r.kernel.org
Subject: PROBLEM: freeze when resuming from suspend-to-ram

Hello, 

When resuming from suspend-to-ram the kernel freezes. Git bisect output below. 
When removing the sis900 module or if eth0 hasn't yet been brought up with "ip 
link set eth0 up", resuming works fine.

This is happening on a up-to-date Arch installation with kernel 3.6.6 and is 
still present in 3.7-rc5. Reverting the patch is possible and fixes the 
freezing.

Please let me know if more info is requried to fix this.

Thanks,
Jan

57d6d456cfb89264f87d24f52640ede23fdf12bd is the first bad commit
commit 57d6d456cfb89264f87d24f52640ede23fdf12bd
Author: Francois Romieu <romieu@...zoreil.com>
Date:   Tue Mar 13 11:14:17 2012 +0100

    sis900: stop using net_device.{base_addr, irq} and convert to __iomem.
    
    - pci_resource_start() can be removed from sis900_get_mac_addr() because
      the IO range is maped and stored into the device private struct early
      in the device probe function.
    - the driver contains a few direct accesses to low IO ports that forbid
      to re(#)define the usual out{l, w, b} macros.
    
    Signed-off-by: Francois Romieu <romieu@...zoreil.com>
    Cc: Daniele Venzano <venza@...wnhat.org>

:040000 040000 f328a3383c1ff9b9ed16de7272b4c8a302ae2812 
44c07bfe1bd23b381fd407dfaa9591ed26165afd M      drivers
--
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