From: Ingo Molnar <mingo@elte.hu>
To: Romano Giannetti <romanol@upcomillas.es>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, Francois Romieu <romieu@fr.zoreil.com>,
Edward Hsu <edward_hsu@realtek.com.tw>,
Jeff Garzik <jeff@garzik.org>,
Stephen Hemminger <shemminger@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: 2.6.24-rc1 fails with lockup - /sbin/ifconfig / inet_ioctl() / dev_close() / rtl8169_down()
Date: Fri, 26 Oct 2007 08:37:33 +0200 [thread overview]
Message-ID: <20071026063733.GA12426@elte.hu> (raw)
In-Reply-To: <1193378269.17910.4.camel@localhost>
* Romano Giannetti <romanol@upcomillas.es> wrote:
> > Does this help?
>
> I tried this, but although I have the D-state processes, I cannot see
> any debug trace now. Results are at:
>
> http://www.dea.icai.upcomillas.es/romano/linux/info/2624rc1_3/
>
> Can I try anything more? This is quite a show-stopper for me... and
> before trying to bisect 11Mbyte of patches...
hm, from your log it appears that lockdep did not find anything, still
the hang does trigger.
it's /sbin/ifconfig and inet_ioctl() / dev_close() / rtl8169_down() that
seems to be hanging. I've extracted the relevant backtrace below. I've
Cc:-ed people who might have a better idea about what's going on.
Ingo
------------------>
ifconfig S c0476f80 0 7226 7166
cbb67df0 00000046 c02f3f97 c0476f80 cbb67dc0 c01489d5 c2b81550 c2b8168c
c1cf7b80 00000000 c30bd250 00000000 cbb67dd0 00000282 cbb67e00 c0476f80
cbb67df0 c0132618 00004232 00000000 00000282 cbb67e00 00004232 f884e000
Call Trace:
[schedule_timeout+72/192] schedule_timeout+0x48/0xc0
[schedule_timeout_interruptible+21/32] schedule_timeout_interruptible+0x15/0x20
[msleep_interruptible+39/64] msleep_interruptible+0x27/0x40
[<f88422f0>] rtl8169_down+0xb0/0xd0 [r8169]
[<f88424cf>] rtl8169_close+0x1f/0xb0 [r8169]
[dev_close+71/96] dev_close+0x47/0x60
[dev_change_flags+125/384] dev_change_flags+0x7d/0x180
[devinet_ioctl+1225/1632] devinet_ioctl+0x4c9/0x660
[inet_ioctl+107/144] inet_ioctl+0x6b/0x90
[sock_ioctl+208/544] sock_ioctl+0xd0/0x220
[do_ioctl+40/128] do_ioctl+0x28/0x80
[vfs_ioctl+87/640] vfs_ioctl+0x57/0x280
[sys_ioctl+57/96] sys_ioctl+0x39/0x60
[sysenter_past_esp+95/165] sysenter_past_esp+0x5f/0xa5
=======================
next prev parent reply other threads:[~2007-10-26 6:38 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 4:19 Linux v2.6.24-rc1 Linus Torvalds
2007-10-24 4:49 ` Willy Tarreau
2007-10-24 5:22 ` Dave Young
2007-10-24 7:23 ` Ingo Molnar
2007-10-24 7:32 ` Ohad Ben-Cohen
2007-10-24 7:33 ` Dave Young
2007-10-24 8:12 ` Jens Axboe
2007-10-24 7:44 ` kvm_main.c:220: error: implicit declaration of function 'smp_call_function_mask' Paolo Ornati
2007-10-24 7:56 ` Jeff Garzik
2007-10-24 8:04 ` Linux v2.6.24-rc1 Ingo Molnar
2007-10-24 8:04 ` Christoph Hellwig
2007-10-24 10:17 ` Linux v2.6.24-rc1, x86 arch code quality, unifications Ingo Molnar
2007-10-24 11:07 ` Linux v2.6.24-rc1 Sam Ravnborg
2007-10-24 12:12 ` Ingo Molnar
2007-10-24 12:21 ` Sam Ravnborg
2007-10-24 21:30 ` [RFC - GIT pull] first step to get rid of x86_64 and i386 dirs Sam Ravnborg
2007-10-24 22:50 ` Randy Dunlap
2007-10-25 6:14 ` Yinghai Lu
2007-10-25 10:56 ` Sam Ravnborg
2007-10-25 15:45 ` Randy Dunlap
2007-10-25 10:18 ` Ingo Molnar
2007-10-25 10:55 ` Sam Ravnborg
2007-10-24 8:10 ` [Git Patch] arch/um/drivers/ubd_kern.c: fix a building error WANG Cong
2007-10-24 11:03 ` Jens Axboe
2007-10-24 11:30 ` [git pull] x86 arch updates Ingo Molnar
2007-10-24 11:48 ` Jeff Garzik
2007-10-24 12:03 ` Ingo Molnar
2007-10-24 13:25 ` 2.6.24-rc1 fails with lockup and BUG: Romano Giannetti
2007-10-24 14:27 ` Ingo Molnar
2007-10-24 15:53 ` Romano Giannetti
2007-10-24 15:55 ` Ingo Molnar
2007-10-24 16:11 ` Peter Zijlstra
2007-10-26 5:57 ` Romano Giannetti
2007-10-26 6:37 ` Ingo Molnar [this message]
2007-10-26 16:48 ` 2.6.24-rc1 fails with lockup - /sbin/ifconfig / inet_ioctl() / dev_close() / rtl8169_down() Stephen Hemminger
2007-10-26 17:56 ` Ingo Molnar
2007-10-26 18:33 ` [PATCH] r8169: don't call napi_disable if not doing NAPI Stephen Hemminger
2007-10-26 20:17 ` Francois Romieu
2007-10-28 22:18 ` Romano Giannetti
2007-10-29 8:56 ` Romano Giannetti
2007-10-24 16:44 ` 2.6.24-rc1 fails with lockup and BUG: Joseph Fannin
2007-10-26 5:59 ` Romano Giannetti
2007-10-24 18:19 ` Linux v2.6.24-rc1 Giacomo Catenazzi
2007-12-04 10:08 ` [Bug 9246] On 2.6.24-rc1-gc9927c2b BUG: unable to handle kernel paging request at virtual address 3d15b925 Ingo Molnar
2007-12-04 16:47 ` Giacomo A. Catenazzi
2007-12-04 20:08 ` Rafael J. Wysocki
2007-12-05 9:26 ` Giacomo A. Catenazzi
2007-10-24 19:44 ` [patch] portman2x4.c: fix boot hang Ingo Molnar
2007-10-24 20:12 ` Frans Pop
2007-10-24 21:29 ` Ingo Molnar
2007-10-25 8:16 ` Takashi Iwai
2007-10-25 5:18 ` 2.6.24-rc1 doesn't build Theodore Tso
2007-10-25 5:30 ` Kamalesh Babulal
2007-10-25 12:45 ` Linux v2.6.24-rc1 edz_mania
2007-10-26 5:19 ` [PATCH] Dump filtering supports x86_64 sparsemem(Re: Linux v2.6.24-rc1) Ken'ichi Ohmichi
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=20071026063733.GA12426@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=davem@davemloft.net \
--cc=edward_hsu@realtek.com.tw \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=romanol@upcomillas.es \
--cc=romieu@fr.zoreil.com \
--cc=shemminger@linux-foundation.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