From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: Oops in 2.6.19.1
Date: Sun, 31 Dec 2006 22:16:58 +0000 [thread overview]
Message-ID: <200612312216.58541.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <200612311646_MC3-1-D6DD-9566@compuserve.com>
On Sunday 31 December 2006 21:43, Chuck Ebbert wrote:
> In-Reply-To: <200612301829.15980.s0348365@sms.ed.ac.uk>
>
> On Sat, 30 Dec 2006 18:29:15 +0000, Alistair John Strachan wrote:
> > > Can you post disassembly of pipe_poll() for both the one that crashes
> > > and the one that doesn't? Use 'objdump -D -r fs/pipe.o' so we get the
> > > relocation info and post just the one function from each for now.
> >
> > Sure, no problem:
> >
> > http://devzero.co.uk/~alistair/2.6.19-via-c3-pipe_poll/
> >
> > Both use identical configs, neither are optimised for size. The config is
> > available from the same location.
>
> Those were compiled without frame pointers. Can you post them compiled
> with frame pointers so they match your original bug report? And confirm
> that pipe_poll() is still at 0xc0156ec0 in vmlinux?
c0156ec0 <pipe_poll>:
I used the config I original sent you to rebuild it again. This time I've put
up the whole vmlinux for both kernels, the config is replaced, the
decompilation is re-done, I've confirmed the offset in the GCC 4.1.1 kernel
is identical. Sorry for the confusion.
The reason I changed the configs was to experiment with enabling and disabling
debugging (and other such) options that might have shaken out compiler bugs.
However none of these kernels have ever crashed gracefully again, most of them
hang the machine (no nmi watchdog though) so I've not been able to look at
the oops. It's the same root cause, however, as GCC 3.4.6 kernels do not
crash.
http://devzero.co.uk/~alistair/2.6.19-via-c3-pipe_poll/
Happy new year, btw.
--
Cheers,
Alistair.
Final year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-12-31 22:16 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-31 21:43 Chuck Ebbert
2006-12-31 22:16 ` Alistair John Strachan [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-30 17:21 Chuck Ebbert
2006-12-30 18:29 ` Alistair John Strachan
2006-12-31 16:28 ` Adrian Bunk
2006-12-31 16:48 ` Alistair John Strachan
2007-01-02 21:12 ` Adrian Bunk
[not found] <200612232325_MC3-1-D634-10E4@compuserve.com>
2006-12-24 14:40 ` Alistair John Strachan
2006-12-24 14:51 ` Alistair John Strachan
2006-12-21 8:05 Chuck Ebbert
2006-12-21 14:22 ` Alistair John Strachan
2006-12-20 20:48 Chuck Ebbert
2006-12-20 22:15 ` Alistair John Strachan
2006-12-21 15:31 ` Valdis.Kletnieks
2006-12-30 18:06 ` James Courtier-Dutton
2006-12-30 18:32 ` Alistair John Strachan
2006-12-20 14:21 Alistair John Strachan
2006-12-20 16:30 ` Greg KH
2006-12-20 16:44 ` Alistair John Strachan
2006-12-23 15:40 ` Alistair John Strachan
2006-12-27 2:07 ` Zhang, Yanmin
2006-12-27 12:35 ` Alistair John Strachan
2006-12-28 2:41 ` Zhang, Yanmin
2006-12-28 4:02 ` Alistair John Strachan
2006-12-28 4:14 ` Alistair John Strachan
2006-12-30 16:59 ` Alistair John Strachan
2006-12-31 13:47 ` Alistair John Strachan
2006-12-31 16:27 ` Adrian Bunk
2006-12-31 16:55 ` Alistair John Strachan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200612312216.58541.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=76306.1226@compuserve.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®