From: Justin Madru <jdm64@gawab.com>
To: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
Cc: "Justin P. Mattock" <justinmattock@gmail.com>,
Jesper Juhl <jj@chaosbits.net>,
lkml <linux-kernel@vger.kernel.org>,
John Stoffel <john@stoffel.org>, Ingo Molnar <mingo@elte.hu>,
"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [bisected] 2.6.29-rc1 Firefox crashing on page load
Date: Tue, 20 Jan 2009 18:39:11 -0800 [thread overview]
Message-ID: <49768ACF.5010608@gawab.com> (raw)
In-Reply-To: <49762AA3.7050402@ct.jp.nec.com>
Hiroshi Shimamoto wrote:
> Justin Madru wrote:
>
>> Hiroshi Shimamoto wrote:
>>
>>> Justin Madru wrote:
>>>
>>>
>>>> Hiroshi Shimamoto wrote:
>>>>
>>>>
>>>>> Justin Madru wrote:
>>>>>
>>>>>
>>>>>> Ok, finally bisected the bug, but the commit isn't related to networking!
>>>>>> I did: git revert 4217458dafaa57d8e26a46f5d05ab8c53cf64191
>>>>>> on current git and that fixed the bug.
>>>>>>
>>>>>> By the way, how do I undo my git revert, so I'm back to a pristine tree?
>>>>>> I want to drop my changes - the revert.
>>>>>> Also how do I find the commit that merged/pulled in this commit?
>>>>>>
>>>>>> commit 4217458dafaa57d8e26a46f5d05ab8c53cf64191
>>>>>> Author: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>>>>>> Date: Fri Dec 5 17:17:09 2008 -0800
>>>>>>
>>>>>> x86: signal: change type of paramter for sys_rt_sigreturn()
>>>>>>
>>>>>> Impact: cleanup on 32-bit
>>>>>>
>>>>>> Peter pointed this parameter can be changed.
>>>>>>
>>>>>> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>>>>>> Signed-off-by: Ingo Molnar <mingo@elte.hu>
>>>>>>
>>>>>>
>>>>> Hi,
>>>>> thanks for reporting.
>>>>>
>>>>> I'm not sure why this commit affects.
>>>>> Can you check vmlinux? size, objdump, etc.
>>>>> On my environment, the generated code looks same.
>>>>>
>>>>> Thanks,
>>>>> Hiroshi
>>>>>
>>>>>
>>>>>
>>>> I tried to do an objdump but it gave an error. How am I suppose to do an
>>>> objdump?
>>>>
>>>> $ objdump -x /boot/vmlinuz-2.6.29-rc2-git
>>>> objdump: /boot/vmlinuz-2.6.29-rc2-git: File format not recognized
>>>> $ readelf -a /boot/vmlinuz-2.6.29-rc2-git
>>>> readelf: Error: Unable to seek to 0xc031f2eb for section headers
>>>> readelf: Error: Not an ELF file - it has the wrong magic bytes at the start
>>>> $ ls -la /boot/vmlinuz-2.6.29-rc2-git
>>>> -rw-r--r-- 1 root root 2286480 2009-01-19 18:44 /boot/vmlinuz-2.6.29-rc2-git
>>>>
>>>>
>>> not vmlinuz, vmlinux.
>>> vmlinuz is a compressed kernel, it is not ELF file.
>>> Usually vmlinux is generated in top of source directory.
>>> I can see disassembled image with objdump -d vmlinux.
>>>
>>> Thanks,
>>> Hiroshi
>>>
>>>
>>>
>> Sorry, didn't know. I tried objdump -d vmlinux, but the resulting file
>> is ~50MB!
>> Is there a smaller section you're interested in, because that would be
>> hard to send.
>> Or am I doing it wrong again?
>>
>
> that's OK. No need to send the disassembled result.
> You can diff disassembled file.
> I guess your GCC generates different code when the patch is reverted.
>
> Thanks,
> Hiroshi
>
>
Ok, I tried, I really did. But no mater what I did the diff was even bigger
if not the same size as the original dump! I even tried to cut out the
first two fields with
cut -f3- dump-revert > dump-revert2
but that wouldn't shrink the diff size (100,000+ lines).
Does gcc output fluctuate this wildly with such little change?
Is there a config option that allows gcc to randomize the output?
I recompiled just to make sure, and even two recompiles of the same
source (no revert)
resulted in a different sha1 hash (didn't test the objdump diff).
The only thing I can think of is that I compile with -O3 instead of -O2.
I'm sorry, but unless you have any suggestions I've decided to just upload
the vmlinux files to my server (<40KB up speed)
http://jdserver.homelinux.org/bugreports/002/
and rapidshare
http://rapidshare.com/files/186890846/vmlinux.tar.bz2.html
http://rapidshare.com/files/186890848/data-norevert.tar.bz2.html
http://rapidshare.com/files/186890849/data-revert.tar.bz2.html
By the way Ingo has already added the revert to tip/master
http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commit;h=1d03950243904c89b8854c10516932b029c2a8fa
Justin Madru
next prev parent reply other threads:[~2009-01-21 2:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-16 20:56 Justin Madru
2009-01-17 2:28 ` Justin Madru
2009-01-17 3:27 ` John Stoffel
2009-01-17 3:27 ` Justin P. Mattock
2009-01-17 8:48 ` Justin Madru
2009-01-17 9:10 ` Justin P. Mattock
2009-01-17 20:21 ` Jesper Juhl
2009-01-17 21:07 ` Justin Madru
2009-01-17 22:51 ` Justin P. Mattock
2009-01-18 0:05 ` Justin Madru
2009-01-18 0:46 ` Justin P. Mattock
2009-01-18 2:06 ` Justin Madru
2009-01-18 2:49 ` Justin P. Mattock
2009-01-20 0:32 ` [bisected] " Justin Madru
2009-01-20 1:06 ` Justin P. Mattock
2009-01-20 1:25 ` Hiroshi Shimamoto
2009-01-20 6:19 ` Justin Madru
2009-01-20 18:28 ` Hiroshi Shimamoto
2009-01-20 19:22 ` Justin Madru
2009-01-20 19:48 ` Hiroshi Shimamoto
2009-01-21 2:39 ` Justin Madru [this message]
2009-01-21 3:04 ` Hiroshi Shimamoto
2009-01-20 1:39 ` Peter Annema
2009-01-20 7:15 ` Heiko Carstens
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=49768ACF.5010608@gawab.com \
--to=jdm64@gawab.com \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=hpa@zytor.com \
--cc=jj@chaosbits.net \
--cc=john@stoffel.org \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
Powered by JetHome