All of lore.kernel.org
 help / color / mirror / Atom feed
From: Evgeniy Polyakov <johnpol@2ka.mipt.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: netdev@vger.kernel.org, Simon Horman <horms@verge.net.au>,
	ja@ssi.bg, bugme-daemon@bugzilla.kernel.org,
	l0op8ack@hotmail.com
Subject: Re: [Bugme-new] [Bug 10556] New: IPVS sync_backup oops
Date: Sat, 26 Apr 2008 20:31:30 +0400	[thread overview]
Message-ID: <20080426163130.GA4499@2ka.mipt.ru> (raw)
In-Reply-To: <20080426040452.4fcbc962.akpm@linux-foundation.org>

Hi.

On Sat, Apr 26, 2008 at 04:04:52AM -0700, Andrew Morton (akpm@linux-foundation.org) wrote:
>  [<c011c53a>] default_wake_function+0x0/0x8
>  [<c0305c85>] sync_thread+0x0/0xa3c
>  [<c0104aa7>] kernel_thread_helper+0x7/0x10
>  =======================
> Code: a1 20 64 3e c0 89 43 54 8b 54 24 34 0f b7 42 16 66 c1 c0 08 0f b7 c0 66
> 89 43 42 0f b6 42 01 e8 90 06 00 00 0f b7 53 42 0f b7 d2 <8b> 40 14 8b 04 90 89
> 43 38 89 d8 e8 8a 8e ff ff 8b 44 24 28 03 
> EIP: [<c030659e>] sync_thread+0x919/0xa3c SS:ESP 0068:f699bf54
> Kernel panic - not syncing: Fatal exception in interrupt

Any chance to run

gdb ./vmlinux
$ l *(sync_thread+0x919)

for that kernel, and if it was not compiled with debug info try to do
that and get bug with it?
 
> Which will be a bit hard to track down because it seems that pretty much
> the whole world got inlined into sync_thread().

I'm not ipvs guru, but that will give us at least some hint...

-- 
	Evgeniy Polyakov

  reply	other threads:[~2008-04-26 16:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-10556-10286@http.bugzilla.kernel.org/>
2008-04-26 11:04 ` [Bugme-new] [Bug 10556] New: IPVS sync_backup oops Andrew Morton
2008-04-26 16:31   ` Evgeniy Polyakov [this message]
2008-04-26 17:48   ` Julian Anastasov
2008-04-27 15:33     ` Julian Anastasov
2008-04-27 23:40     ` David Miller
2008-05-06 20:10       ` Andrew Morton
2008-05-06 20:31         ` David Miller
2008-04-27  8:22   ` Julian Anastasov

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=20080426163130.GA4499@2ka.mipt.ru \
    --to=johnpol@2ka.mipt.ru \
    --cc=akpm@linux-foundation.org \
    --cc=bugme-daemon@bugzilla.kernel.org \
    --cc=horms@verge.net.au \
    --cc=ja@ssi.bg \
    --cc=l0op8ack@hotmail.com \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.