public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
To: Ingo Molnar <mingo@elte.hu>, Mike Galbraith <efault@gmx.de>,
	Jaswinder Singh Rajput <jaswinder@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86-tip: xine bustage bisection fingers commit	97286a2b64725aac2d584ddd1f94871f9991d5a1
Date: Mon, 02 Mar 2009 10:15:55 -0800	[thread overview]
Message-ID: <49AC225B.9080105@ct.jp.nec.com> (raw)
In-Reply-To: <20090302093319.GB20897@elte.hu>

Ingo Molnar wrote:
> * Mike Galbraith <efault@gmx.de> wrote:
> 
>> Greetings and Salutations,
>>
>> $subject, box is Q6600 X86_64 running v2.6.29-rc6-2261-g0fdaeee
>>
>> marge:/root # xine
>> This is xine (X11 gui) - a free video player v0.99.6cvs.
>> (c) 2000-2007 The xine Team.
>> Floating point exception
>>
>> [pid  6230] 06:59:50.524473 set_robust_list(0x40e239f0, 0x18 <unfinished ...>
>> [pid  6230] 06:59:50.524553 <... set_robust_list resumed> ) = 0 <0.000027>
>> [pid  6230] 06:59:50.524648 select(0, NULL, NULL, NULL, {0, 500000} <unfinished ...>
>> [pid  6230] 06:59:50.763988 <... select resumed> ) = ? ERESTARTNOHAND (To be restarted) <0.239321>
>> [pid  6230] 06:59:50.764012 --- SIGRT_1 (Unknown signal 33) @ 0 (0) ---
>> [pid  6230] 06:59:50.764074 setuid(0)   = 0 <0.000014>
>> [pid  6230] 06:59:50.764151 futex(0x7fff2745e7a0, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
>> [pid  6230] 06:59:50.764213 <... futex resumed> ) = 0 <0.000051>
>> [pid  6230] 06:59:50.764255 futex(0x40e23d2c, FUTEX_WAKE_PRIVATE, 1 <unfinished ...>
>> [pid  6230] 06:59:50.764298 <... futex resumed> ) = 0 <0.000028>
>> [pid  6230] 06:59:50.764346 rt_sigreturn(0x40e23d2c <unfinished ...>
>> [pid  6230] 06:59:50.778497 <... rt_sigreturn resumed> ) = 0 <0.014136>
>> [pid  6230] 06:59:50.778524 --- SIGSEGV (Segmentation fault) @ 0 (0) ---
>>
>> [ 1303.345419] xine[6230] bad frame in rt_sigreturn frame:0000000040e22c28 ip:7f051ca28622 sp:40e23070 orax:ffffffffffffffff in libc-2.8.so[7f051c95c000+14f000]
>> 
>> 97286a2b64725aac2d584ddd1f94871f9991d5a1 is first bad commit
>> commit 97286a2b64725aac2d584ddd1f94871f9991d5a1
>> Author: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>
>> Date:   Fri Feb 27 10:28:48 2009 -0800
>>
>>     x86: signal: intrroduce get_sigframe() and replace get_sigstack()
>>     
>>     Impact: cleanup

Thanks for reporting and bisecting.
Apparently I did something wrong in this cleanup series.

> 
> ok, that's the same area Jaswinder Singh Rajput bisected a 
> breakage back to. I've excluded these commits from tip:master 
> for now and pushed out an updated tip:master tree.
> 
> Hiroshi-san, mind having a look at this problem?

OK, I'll look at this.

Thanks,
Hiroshi


  reply	other threads:[~2009-03-02 18:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-02  9:04 x86-tip: xine bustage bisection fingers commit 97286a2b64725aac2d584ddd1f94871f9991d5a1 Mike Galbraith
2009-03-02  9:33 ` Ingo Molnar
2009-03-02 18:15   ` Hiroshi Shimamoto [this message]
2009-03-03  1:20   ` Hiroshi Shimamoto
2009-03-03  6:04     ` Mike Galbraith
2009-03-03  8:03       ` Ingo Molnar
2009-03-03  8:06     ` [tip:x86/signal] x86, signals: fix xine & firefox bustage Hiroshi Shimamoto

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=49AC225B.9080105@ct.jp.nec.com \
    --to=h-shimamoto@ct.jp.nec.com \
    --cc=efault@gmx.de \
    --cc=jaswinder@kernel.org \
    --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