linux-kernel - Re: [Bug #11271] BUG: fealnx in 2.6.27-rc1

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:	Mon, 1 Sep 2008 23:18:10 +0200
From:	Francois Romieu <romieu@...zoreil.com>
To:	Jaswinder Singh <jaswinderlinux@...il.com>
Cc:	Arjan van de Ven <arjan@...radead.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>
Subject: Re: [Bug #11271] BUG: fealnx in 2.6.27-rc1

Jaswinder Singh <jaswinderlinux@...il.com> :
[...]
> may be you are right, I have never noticed it earlier. But currently
> this is soo serious that it has totally screwed up my networking when
> I use fealnx based NICs.

Could you enable CONFIG_PRINTK_TIME and give Jeff's reversal suggestion
a try ?

I do not see where the patch would break. Would a broken clock trigger
a lot of spurious tx timeout ?

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