[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#432312: marked as done (BUG: soft lockup detected on CPU#1)



Your message dated Mon, 15 Feb 2010 02:40:31 +0100
with message-id <20100215014031.GA23254@galadriel.inutil.org>
and subject line Re: Bug#432312: BUG: soft lockup detected on CPU#1
has caused the Debian Bug report #432312,
regarding BUG: soft lockup detected on CPU#1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
432312: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=432312
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: quota
Version: 3.14-8

When activating quota on my server I get kernelpanics:
Jul  8 18:25:44 server kernel: BUG: soft lockup detected on CPU#0!
Jul  8 18:25:44 server kernel:  [softlockup_tick+166/180] softlockup_tick+0xa6/0xb4
Jul  8 18:25:44 server kernel:  [update_process_times+59/94] update_process_times+0x3b/0x5e
Jul  8 18:25:44 server kernel:  [tick_periodic+96/106] tick_periodic+0x60/0x6a
Jul  8 18:25:44 server kernel:  [tick_handle_periodic+23/104] tick_handle_periodic+0x17/0x68
Jul  8 18:25:44 server kernel:  [smp_apic_timer_interrupt+108/125] smp_apic_timer_interrupt+0x6c/0x7d
Jul  8 18:25:44 server kernel:  [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
Jul  8 18:25:44 server kernel:  [vfs_quota_on_inode+642/934] vfs_quota_on_inode+0x282/0x3a6
Jul  8 18:25:44 server kernel:  [vfs_quota_on+82/101] vfs_quota_on+0x52/0x65
Jul  8 18:25:44 server kernel:  [getname+89/143] getname+0x59/0x8f
Jul  8 18:25:44 server kernel:  [pg0+945238007/1069745152] ext3_quota_on+0xad/0xb5 [ext3]
Jul  8 18:25:44 server kernel:  [lookup_bdev+95/113] lookup_bdev+0x5f/0x71
Jul  8 18:25:44 server kernel:  [find_get_page+24/65] find_get_page+0x18/0x41
Jul  8 18:25:44 server kernel:  [getname+89/143] getname+0x59/0x8f
Jul  8 18:25:44 server kernel:  [sys_quotactl+904/1594] sys_quotactl+0x388/0x63a
Jul  8 18:25:44 server kernel:  [do_page_fault+652/1317] do_page_fault+0x28c/0x525
Jul  8 18:25:44 server kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Jul  8 18:25:44 server kernel:  =======================

or this:
Jul  9 12:39:17 server kernel: BUG: soft lockup detected on CPU#1!
Jul  9 12:39:17 server kernel:  [softlockup_tick+166/180] softlockup_tick+0xa6/0xb4
Jul  9 12:39:17 server kernel:  [update_process_times+59/94] update_process_times+0x3b/0x5e
Jul  9 12:39:17 server kernel:  [tick_sched_timer+119/186] tick_sched_timer+0x77/0xba
Jul  9 12:39:17 server kernel:  [hrtimer_interrupt+317/457] hrtimer_interrupt+0x13d/0x1c9
Jul  9 12:39:17 server kernel:  [tick_sched_timer+0/186] tick_sched_timer+0x0/0xba
Jul  9 12:39:17 server kernel:  [smp_apic_timer_interrupt+108/125] smp_apic_timer_interrupt+0x6c/0x7d
Jul  9 12:39:17 server kernel:  [dqget+499/563] dqget+0x1f3/0x233
Jul  9 12:39:17 server kernel:  [apic_timer_interrupt+40/48] apic_timer_interrupt+0x28/0x30
Jul  9 12:39:17 server kernel:  [vfs_quota_on_inode+642/934] vfs_quota_on_inode+0x282/0x3a6
Jul  9 12:39:17 server kernel:  [vfs_quota_on+82/101] vfs_quota_on+0x52/0x65
Jul  9 12:39:18 server kernel:  [getname+89/143] getname+0x59/0x8f
Jul  9 12:39:18 server kernel:  [pg0+945430519/1069745152] ext3_quota_on+0xad/0xb5 [ext3]
Jul  9 12:39:18 server kernel:  [lookup_bdev+95/113] lookup_bdev+0x5f/0x71
Jul  9 12:39:19 server kernel:  [getname+89/143] getname+0x59/0x8f
Jul  9 12:39:20 server kernel:  [sys_quotactl+904/1594] sys_quotactl+0x388/0x63a
Jul  9 12:39:20 server kernel:  [_atomic_dec_and_lock+42/68] _atomic_dec_and_lock+0x2a/0x44
Jul  9 12:39:22 server kernel:  [dput+40/275] dput+0x28/0x113
Jul  9 12:39:24 server kernel:  [__fput+288/330] __fput+0x120/0x14a
Jul  9 12:39:24 server kernel:  [mntput_no_expire+17/104] mntput_no_expire+0x11/0x68
Jul  9 12:39:25 server kernel:  [filp_close+81/88] filp_close+0x51/0x58
Jul  9 12:39:25 server kernel:  [syscall_call+7/11] syscall_call+0x7/0xb
Jul  9 12:39:25 server kernel:  =======================

When I remove quota package from server all is working fine.
I get also such messages in dmesg when I run:
quotacheck -cugvmf -F vfsv0 /
or equal.

I also updated kernel to latest version:
Linux server 2.6.21-2-k7 #1 SMP Mon Jun 25 21:37:29 UTC 2007 i686 GNU/Linux

I can reproduce this error at any time I activate quota.
I run also several fsck´s on / without any success.

Does have anyone any idea?
Or is it no quota problem?

Gruss,
Peter
-- 
www: http://peter.tux.hm
www: http://tux.hm - Linux- und BSD-UserGroup im Weserbergland
www: http://ha-forum.org - HA Cluster Forums
icq: 540954



--- End Message ---
--- Begin Message ---
On Mon, Dec 29, 2008 at 09:18:18PM +0100, Moritz Muehlenhoff wrote:
> On Wed, Jul 11, 2007 at 11:26:25AM +0200, Michael Meskes wrote:
> > reassign 432312 linux-image-2.6.21-2-k7
> > thanks
> > 
> > On Mon, Jul 09, 2007 at 01:07:46PM +0200, Peter wrote:
> > > Package: quota
> > > Version: 3.14-8
> > > 
> > > When activating quota on my server I get kernelpanics:
> > > ...
> > 
> > User space utilities shouldn't create kernel panics by just calling a
> > function. Thus I would think it's a kernel problem. The quota package
> > only contains the user space utilities, but not the kernel code. 
> 
> Peter, does this error still occur with more recent kernel versions?

No further feedback, closing the bug.

If anyone reencounters the problem, please reopen this bug.

Cheers,
        Moritz


--- End Message ---

Reply to: