From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: linux-next: Tree for July 11 Date: Sat, 12 Jul 2008 20:51:50 +0200 Message-ID: <200807122051.50909.rjw@sisk.pl> References: <20080711182557.9b24df1f.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Cc: linux-next@vger.kernel.org, LKML , Kernel Testers List , netdev@vger.kernel.org, "Vegard Nossum" , "Pekka Enberg" To: Stephen Rothwell Return-path: In-Reply-To: <20080711182557.9b24df1f.sfr@canb.auug.org.au> Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Friday, 11 of July 2008, Stephen Rothwell wrote: > Hi all, > > Changes since next-20080710: > > New tree: voltage > > The tip-core tree lost its conflict against Linus' tree. > > The sched tree gained a conflict against Linus' tree. > > The x86 tree gained conflicts against the ftrace and driver-core trees. > > The ide tree lost its 2 conflicts against Linus' tree. > > The rr tree gained a runtime bug fix patch (which Rusty tells me will not > be needed for long). > > The firmware tree gained a conflict against the usb tree that required the > reverting of one of its commits) but also lost a conflict against Linus' > tree. > > The kmemcheck tree gained a conflict against the x86 tree. > > The ttydev tree had two patches fail to apply which I removed. > > I have also applied the following patches for known problems: > > sparc64: sysdev API change fallout > s390: fix compile error due to smp_call_function > > This patch is no longer needed: > linux-next: zero based percpu build error on s390 > > ---------------------------------------------------------------------------- With this tree I see two problems. The first one is this: ============================================= [ INFO: possible recursive locking detected ] 2.6.26-rc9-next #44 --------------------------------------------- swapper/1 is trying to acquire lock: (&queue->lock){-...}, at: [] qdisc_lock_tree+0x27/0x30 but task is already holding lock: (&queue->lock){-...}, at: [] qdisc_lock_tree+0x1f/0x30 other info that might help us debug this: 3 locks held by swapper/1: #0: (net_mutex){--..}, at: [] register_pernet_device+0x22/0x70 #1: (rtnl_mutex){--..}, at: [] rtnl_lock+0x12/0x20 #2: (&queue->lock){-...}, at: [] qdisc_lock_tree+0x1f/0x30 stack backtrace: Pid: 1, comm: swapper Not tainted 2.6.26-rc9-next #44 Call Trace: [] __lock_acquire+0xb7e/0x1280 [] lock_acquire+0x57/0x80 [] ? qdisc_lock_tree+0x27/0x30 [] _spin_lock+0x25/0x40 [] qdisc_lock_tree+0x27/0x30 [] dev_init_scheduler+0x11/0x70 [] register_netdevice+0x1fb/0x370 [] register_netdev+0x44/0x60 [] loopback_net_init+0x47/0x90 [] ? firmware_class_init+0x0/0x90 [] ? loopback_init+0x0/0x20 [] register_pernet_operations+0x18/0x20 [] register_pernet_device+0x31/0x70 [] loopback_init+0x10/0x20 [] kernel_init+0x128/0x310 [] ? trace_hardirqs_on_caller+0xbf/0x150 [] ? trace_hardirqs_on+0xd/0x10 [] ? _spin_unlock_irq+0x2b/0x40 [] ? trace_hardirqs_on_thunk+0x3a/0x3f [] ? trace_hardirqs_on_caller+0xbf/0x150 [] child_rip+0xa/0x11 [] ? restore_args+0x0/0x30 [] ? kernel_init+0x0/0x310 [] ? child_rip+0x0/0x11 and the second one is the following: WARNING: at /home/rafael/src/linux-next/include/linux/blkdev.h:447 blk_plug_device+0x9b/0xb0() Modules linked in: snd_hda_intel ohci1394 ieee1394 snd_pcm rtc_cmos sr_mod rtc_core floppy snd_timer wmi button cdrom rtc_lib serio_raw sky2 snd_page_alloc snd_hwdep snd evdev joydev sg soundcore raid456 async_xor async_memcpy async_tx xor raid0 usbhid ff_memless ehci_hcd ohci_hcd sd_mod edd raid1 ext3 jbd fan pata_marvell pata_atiixp thermal processor Pid: 2244, comm: kjournald Not tainted 2.6.26-rc9-next #44 Call Trace: [] warn_on_slowpath+0x5f/0x80 [] ? hpet_unregister_irq_handler+0x0/0x30 [] ? kmemcheck_mark_initialized+0xe/0x10 [] ? kmemcheck_slab_alloc+0x2b/0x50 [] ? kmem_cache_alloc+0xc0/0x140 [] ? mempool_alloc_slab+0x11/0x20 [] ? mempool_alloc+0x5b/0x140 [] blk_plug_device+0x9b/0xb0 [] bitmap_startwrite+0xbf/0x1b0 [] ? bio_alloc_bioset+0x54/0xb0 [] make_request+0x39a/0x810 [raid1] [] ? mempool_alloc+0x5b/0x140 [] ? mempool_alloc+0x5b/0x140 [] generic_make_request+0x17d/0x2b0 [] submit_bio+0x6c/0xf0 [] submit_bh+0xf0/0x130 [] journal_commit_transaction+0xa40/0x1000 [jbd] [] ? try_to_del_timer_sync+0x44/0x90 [] kjournald+0xe7/0x250 [jbd] [] ? autoremove_wake_function+0x0/0x40 [] ? kjournald+0x0/0x250 [jbd] [] kthread+0x4d/0x80 [] child_rip+0xa/0x11 [] ? _spin_unlock_irq+0x2b/0x40 [] ? restore_args+0x0/0x30 [] ? kthreadd+0x122/0x1a0 [] ? kthread+0x0/0x80 [] ? child_rip+0x0/0x11 ---[ end trace d63b767d1ed7d78a ]--- Full dmesg output is at: http://www.sisk.pl/kernel/debug/20080711/dmesg-1.log Thanks, Rafael