netdev - Re: r8169 delay / segfault

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: <20121012210503.GA2054@electric-eye.fr.zoreil.com>
Date:	Fri, 12 Oct 2012 23:05:03 +0200
From:	Francois Romieu <romieu@...zoreil.com>
To:	Roland Stigge <stigge@...com.de>
Cc:	nic_swsd@...ltek.com, netdev@...r.kernel.org,
	hayeswang <hayeswang@...ltek.com>
Subject: Re: r8169 delay / segfault

Roland Stigge <stigge@...com.de> :
[...]
> on a Samsung laptop (x86_64, kernel 3.6.0), I get the following messages in the kernel
> log after a suspend/resume cycle (doesn't happen after every suspend/resume but sometimes):
> 
> Oct 12 21:02:27 darwin kernel: [ 4289.829755] r8169 0000:02:00.0: wake-up capability disabled by ACPI
> Oct 12 21:02:27 darwin kernel: [ 4289.830351] r8169 0000:02:00.0: eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
[...]
> Oct 12 21:02:27 darwin kernel: [ 4289.858920] r8169 0000:02:00.0: eth0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
[...]
> Oct 12 21:04:56 darwin kernel: [ 4441.330385] r8169 0000:02:00.0: eth0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
> Oct 12 21:04:56 darwin kernel: [ 4441.331592] r8169 0000:02:00.0: eth0: rtl_csiar_cond == 1 (loop: 100, delay: 10).
> Oct 12 21:04:56 darwin kernel: [ 4441.332727] r8169 0000:02:00.0: eth0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
[...]
> Oct 12 21:04:56 darwin kernel: [ 4441.343912] r8169 0000:02:00.0: eth0: rtl_eriar_cond == 1 (loop: 100, delay: 100).

The device seems completely unresponsive :o/

> Oct 12 21:04:56 darwin kernel: [ 4441.454689] r8169 0000:02:00.0: eth0: link up
> 
> I copied a bigger part of the kernel log at http://antcom.de/kernel/dmesg.
> 
> Please tell me how I can help debugging or what else information you need.

The device does not recover despite the "link up" message, right ?

Can you send the XID line from the r8169 driver ? It should be in the
upper part of the dmesg log.

Which kernel version did you previously use ?

-- 
Ueimor
--
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