From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: "Zhang, Yanmin" <yanmin_zhang@linux.intel.com>
Subject: Re: Oops in 2.6.19.1
Date: Thu, 28 Dec 2006 04:02:23 +0000
User-Agent: KMail/1.9.5
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>,
       Chuck Ebbert <76306.1226@compuserve.com>
References: <200612201421.03514.s0348365@sms.ed.ac.uk> <200612271235.08845.s0348365@sms.ed.ac.uk> <1167273694.15989.146.camel@ymzhang>
In-Reply-To: <1167273694.15989.146.camel@ymzhang>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200612280402.23474.s0348365@sms.ed.ac.uk>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1162
Lines: 32

On Thursday 28 December 2006 02:41, Zhang, Yanmin wrote:
[snip]
> > Here's a current decompilation of vmlinux/pipe_poll() from the running
> > kernel, the addresses have changed slightly. There's no xchg there
> > either:
>
> Could you reproduce the bug by the new kernel, so we could get the exact
> address and instruction of the bug?

It crashed again, but this time with no output (machine locked solid). To be 
honest, the disassembly looks right (it's like Chuck said, it's jumping back 
half way through an instruction):

c0156f5f:       3b 87 68 01 00 00       cmp    0x168(%edi),%eax

So c0156f60 is 87 68 01 00 00..

This is with the GCC recompile, so it's not a distro problem. It could still 
either be GCC 4.x, or a 2.6.19.1 specific bug, but it's serious. 2.6.19 with 
GCC 3.4.3 is 100% stable.

-- 
Cheers,
Alistair.

Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/