public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Ornati <ornati@fastwebnet.it>
To: Paolo Ornati <ornati@fastwebnet.it>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Unkillable process in last git -- 100% reproducible
Date: Wed, 28 Jun 2006 15:19:55 +0200	[thread overview]
Message-ID: <20060628151955.0acdb39a@localhost> (raw)
In-Reply-To: <20060628150943.78e91871@localhost>

[-- Attachment #1: Type: text/plain, Size: 2280 bytes --]

On Wed, 28 Jun 2006 15:09:43 +0200
Paolo Ornati <ornati@fastwebnet.it> wrote:

> On Wed, 28 Jun 2006 14:53:49 +0200
> Paolo Ornati <ornati@fastwebnet.it> wrote:
> 
> > > [  430.083347] localedef     R  running task       0  8577   8558  8578               (NOTLB)
> > > [  430.083352] gzip          X ffff81001e612ee0     0  8578   8577                     (L-TLB)
> > > [  430.083358] ffff81001395bef8 ffff81001fd1a310 0000000000000246 ffff81001e612ee0 
> > > [  430.083362]        ffff81001e4c0080 ffff81001e612ee0 ffff81001e4c0258 0000000000000001 
> > > [  430.083366]        0000000000000046 0000000000000046 ffff81001395bf18 0000000000000010 
> > > [  430.083370] Call Trace: <ffffffff80227f6f>{do_exit+2378} <ffffffff802628e9>{vfs_write+288}
> > > [  430.083379]        <ffffffff80228065>{sys_exit_group+0} <ffffffff80209806>{system_call+126}
> > 
> > do_exit() -- kernel/exit.c
> > 
> > 0xffffffff80227f66 <do_exit+2369>:      mov    %rax,0x18(%rbp)
> > 0xffffffff80227f6a <do_exit+2373>:      callq  0xffffffff8048b850 <schedule>
> > 0xffffffff80227f6f <do_exit+2378>:      ud2a
> > 0xffffffff80227f71 <do_exit+2380>:      pushq  $0xffffffff804b7821
> > 0xffffffff80227f76 <do_exit+2385>:      retq   $0x3ba
> > 0xffffffff80227f79 <do_exit+2388>:      jmp    0xffffffff80227f79 <do_exit+2388>
> 
> 
> that is the end of the function:
> 
> ...
>         schedule();
>         BUG();
>         /* Avoid "noreturn function does return".  */
>         for (;;) ;
> }
> 
> 
> So the questions are two:
> 
> 1) why schedule() didn't work?
> 
> 2) why the process is looping around "ud2a" (placed by BUG()) and
> presumibly throwing a lot of "invalid opcode" exceptions?

It seems that the first mail didn't hit LKML (maybe it was too big),
here it is (stripped):

------------------------------------------------------------------------
Running "localedef" triggers an infinite loop in kernel mode (or
something) --> localdef becomes unkillable.

This is dmesg after pressing ALT+SysRQ+T three times:

[CUT]

KERNEL:

--
	Paolo Ornati
	Linux 2.6.17-ga39727f2-dirty on x86_64
	                      ^^^^^^^

The -dirty is because of a fix to PS2 Keyboard auto-repeat, nothing else.
------------------------------------------------------------------------


Full config attached.

[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 8546 bytes --]

  reply	other threads:[~2006-06-28 13:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060628142918.1b2c25c3@localhost>
2006-06-28 12:53 ` Unkillable process in last git -- 100% reproducible Paolo Ornati
2006-06-28 13:09   ` Paolo Ornati
2006-06-28 13:19     ` Paolo Ornati [this message]
2006-06-28 18:38       ` Unkillable process in last git -- Bisected Paolo Ornati
2006-06-28 19:06         ` Vladimir V. Saveliev
2006-06-28 20:14           ` Paolo Ornati
2006-06-29  5:20         ` Andrew Morton
2006-06-29  6:23           ` Paolo Ornati

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=20060628151955.0acdb39a@localhost \
    --to=ornati@fastwebnet.it \
    --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