linux-kernel - Re: 2.6.32.2 SATA link detect failed, 2.6.32.1 works fine

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]

Date:	Thu, 24 Dec 2009 09:21:29 +0800 (CST)
From:	fengxiangjun <fengxiangjun@...soft.com>
To:	Bjarke Istrup Pedersen <gurligebis@...il.com>
Cc:	Tejun Heo <tj@...nel.org>, Robert Hancock <hancockrwd@...il.com>,
	linux-kernel@...r.kernel.org, linux-ide@...r.kernel.org
Subject: Re: 2.6.32.2 SATA link detect failed, 2.6.32.1 works fine


Hi, it's timing related.

I just tried booting with an initrd, and i want to capture the full error 
message, but with initrd, the problem went away.

The only difference between the two config is:

--- .config.old	2009-12-24 09:16:31.000000000 +0800
+++ .config	2009-12-23 19:05:17.000000000 +0800
@@ -1,7 +1,7 @@
 #
 # Automatically generated make config: don't edit
 # Linux kernel version: 2.6.32.2
-# Mon Dec 21 18:42:50 2009
+# Wed Dec 23 19:05:17 2009
 #
 CONFIG_64BIT=y
 # CONFIG_X86_32 is not set
@@ -100,7 +100,11 @@
 # CONFIG_USER_NS is not set
 # CONFIG_PID_NS is not set
 # CONFIG_NET_NS is not set
-# CONFIG_BLK_DEV_INITRD is not set
+CONFIG_BLK_DEV_INITRD=y
+CONFIG_INITRAMFS_SOURCE=""
+CONFIG_RD_GZIP=y
+CONFIG_RD_BZIP2=y
+CONFIG_RD_LZMA=y
 CONFIG_CC_OPTIMIZE_FOR_SIZE=y
 CONFIG_SYSCTL=y
 CONFIG_ANON_INODES=y
@@ -1710,8 +1714,11 @@
 CONFIG_CRC32=y
 # CONFIG_CRC7 is not set
 # CONFIG_LIBCRC32C is not set
-CONFIG_ZLIB_INFLATE=m
+CONFIG_ZLIB_INFLATE=y
 CONFIG_ZLIB_DEFLATE=m
+CONFIG_DECOMPRESS_GZIP=y
+CONFIG_DECOMPRESS_BZIP2=y
+CONFIG_DECOMPRESS_LZMA=y
 CONFIG_HAS_IOMEM=y
 CONFIG_HAS_IOPORT=y
 CONFIG_HAS_DMA=y

Right now, I can reproduce this problem only when I
running 2.6.32.2 with a specific kernel config.

If I attach a serial console or use initrd to capture
the fail boot log, the problem disapeared. Even running
2.6.31.1 with the exactly same config, no problem. 

So I will say that it's very hard to reproduce this, it's very
subtly timing related. 

I remember when running 2.6.32-rc8 and 2.6.32, the same
problem happened twice, I just can't reproduce it.
And with 2.6.31.x, never running into this.

Oh well. 

On Wed, 23 Dec 2009, Bjarke Istrup Pedersen wrote:

> Hey,
> 
> Could it be an idea to do a bisect for the patch that makes it break? :)
> 
> /Bjarke
> 
---------------------------------------------------------------------------------------------------
Confidentiality Notice: The information contained in this e-mail and any accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, disclosure or copying 
is strictly prohibited, and may be unlawful.If you have received this communication in error,please 
immediately notify the sender by return e-mail, and delete the original message and all copies from 
your system. Thank you. 
---------------------------------------------------------------------------------------------------

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