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

Bug#521943: marked as done ([linux-image-2.6.29-1-686] system becomes unresponsive due to "soft lockup - CPU#0 stuck for 61s!")

Your message dated Sun, 13 Sep 2009 13:11:32 +0200
with message-id <20090913111132.GA12415@galadriel.inutil.org>
and subject line Re: [linux-image-2.6.29-1-686] system becomes unresponsive due to "soft lockup - CPU#0 stuck for 61s!"
has caused the Debian Bug report #521943,
regarding [linux-image-2.6.29-1-686] system becomes unresponsive due to "soft lockup - CPU#0 stuck for 61s!"
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.)


-- 
521943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521943
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6.29-1-686
Version: 2.6.29-1
Severity: important

--- Please enter the report below this line. ---
After a few hours my laptop is on, the system suddenly becomes near
totally unresponsive: the keyboard doesn't work (in particular, I can't
switch to tty1 or kill X with Ctrl-Alt-Backspace), the mouse moves, but
the clicks are processed with considerable delay (magnitude of minutes).
The GNOME interface (panels, applets) are working, so I can see that the
CPU usage is constantly to 50% (I'm on a two cores machine, so one core
totally used and the other not).

I've tried to let the computer alone and without inputs for a couple of
hours, but nothing changed when I started again trying to bring it again
to normal work.

After reboot with Alt-SysRq-B, the syslog contains lots of messages like
this:

> Mar 30 23:58:26 sieff kernel: [14450.420008] BUG: soft lockup - CPU#0 stuck for 61s! [cp:9819]
> Mar 30 23:58:26 sieff kernel: [14450.420008] Modules linked in: nls_utf8 nls_cp437 vfat fat nls_base usb_storage i915 drm i2c_algo_bit ppdev parport_pc lp parport binfmt_misc cpufreq_stats cpufreq_userspa
> ce cpufreq_powersave cpufreq_conservative tun fuse ipv6 acpi_cpufreq coretemp eeprom loop dm_crypt dm_mod snd_hda_codec_realtek joydev snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_p
> cm snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd soundcore i2c_i801 yenta_socket acer_wmi rfkill intel_agp pcspkr i2c_core serio_raw psmouse rs
> rc_nonstatic snd_page_alloc evdev rng_core wmi battery container agpgart ac video output button ext3 jbd mbcache usbhid hid sg sr_mod cdrom sd_mod crc_t10dif ide_pci_generic ide_core ata_generic ata_piix 
> libata b44 ssb scsi_mod sdhci_pci sdhci uhci_hcd mmc_core pcmcia pcmcia_core mii ehci_hcd led_class usbcore thermal processor fan thermal_sys [last unloaded: v4l1_compat]
> Mar 30 23:58:26 sieff kernel: [14450.420008] 
> Mar 30 23:58:26 sieff kernel: [14450.420008] Pid: 9819, comm: cp Not tainted (2.6.29-1-686 #1) Aspire 5610Z    
> Mar 30 23:58:26 sieff kernel: [14450.420008] EIP: 0060:[<c01ff4be>] EFLAGS: 00010246 CPU: 0
> Mar 30 23:58:26 sieff kernel: [14450.420008] EIP is at __copy_from_user_ll_nocache_nozero+0x21/0x2c
> Mar 30 23:58:26 sieff kernel: [14450.420008] EAX: f76ff000 EBX: 00001000 ECX: 00000400 EDX: 00000000
> Mar 30 23:58:26 sieff kernel: [14450.420008] ESI: 09a7b000 EDI: f76ff000 EBP: 00000000 ESP: e865ddbc
> Mar 30 23:58:26 sieff kernel: [14450.420008]  DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
> Mar 30 23:58:26 sieff kernel: [14450.420008] CR0: 8005003b CR2: f76ff000 CR3: 2bafd000 CR4: 000006d0
> Mar 30 23:58:26 sieff kernel: [14450.420008] DR0: 00000000 DR1: 00000000 DR2: 00000000 DR3: 00000000
> Mar 30 23:58:26 sieff kernel: [14450.420008] DR6: ffff0ff0 DR7: 00000400
> Mar 30 23:58:26 sieff kernel: [14450.420008] Call Trace:
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c01663ce>] iov_iter_copy_from_user_atomic+0x4d/0xa5
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c016763c>] generic_file_buffered_write+0xe1/0x270
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c0167665>] generic_file_buffered_write+0x10a/0x270
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c0167c05>] __generic_file_aio_write_nolock+0x265/0x28d
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c02e84cb>] _spin_lock+0x5/0x7
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c02e84cb>] _spin_lock+0x5/0x7
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c016845d>] generic_file_aio_write+0x5d/0xb4
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c0188652>] do_sync_write+0xc0/0x107
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c013ad95>] sched_clock_cpu+0x136/0x147
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c011e23c>] pick_next_task_fair+0x80/0x87
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c0136d6a>] autoremove_wake_function+0x0/0x2d
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c02e728b>] schedule+0x6dd/0x754
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c01d1d68>] security_file_permission+0xc/0xd
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c0188592>] do_sync_write+0x0/0x107
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c0188e78>] vfs_write+0x7e/0xd6
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c0188f68>] sys_write+0x3c/0x63
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c010343b>] sysenter_do_call+0x12/0x2f
> Mar 30 23:58:26 sieff kernel: [14450.420008]  [<c02e0000>] pci_fixup_video+0x0/0x93

I'm not able to understand what they mean. They seem to be sent out on
an average of once every one or two minutes, for the entire interval
during which the system is unresponsive.

I hope this annoying but to be fixed as soon as possible!

Thank you for your work on Debian and Linux. :-)

Regards, Giovanni.

--- System information. ---
Architecture: i386
Kernel:       Linux 2.6.29-1-686

Debian Release: squeeze/sid
  500 unstable        www.debian-multimedia.org 
  500 unstable        ftp.it.debian.org 
  500 testing         ftp.it.debian.org 
  500 stable          ftp.it.debian.org 
    1 experimental    ftp.it.debian.org 

--- Package information. ---
Depends                     (Version) | Installed
=====================================-+-=============
module-init-tools                     | 3.7-pre9-1
initramfs-tools            (>= 0.55)  | 0.93.1
 OR yaird                (>= 0.0.13)  | 
 OR linux-initramfs-tool              | 

--- Output from package bug script ---

-- 
Giovanni Mascellani <g.mascellani@gmail.com>
Pisa, Italy

Web: http://poisson.phc.unipi.it/~mascellani
Jabber: g.mascellani@jabber.org / giovanni@elabor.homelinux.org
GPG: 0x5F1FBF70 (FP: 1EB6 3D43 E201 4DDF 67BD  003F FCB0 BB5C 5F1F BF70)

Attachment: signature.asc
Description: Questa =?ISO-8859-1?Q?=E8?= una parte del messaggio firmata digitalmente


--- End Message ---
--- Begin Message --- 
Version: 2.6.30-1

Giovanni Mascellani wrote:
> Moritz Muehlenhoff ha scritto:
> >> After a few hours my laptop is on, the system suddenly becomes near
> >> totally unresponsive: the keyboard doesn't work (in particular, I can't
> >> switch to tty1 or kill X with Ctrl-Alt-Backspace), the mouse moves, but
> >> the clicks are processed with considerable delay (magnitude of minutes).
> >> The GNOME interface (panels, applets) are working, so I can see that the
> >> CPU usage is constantly to 50% (I'm on a two cores machine, so one core
> >> totally used and the other not).
> > 
> > Does this still occur with 2.6.30?
> 
> No, I'm using 2.6.30, but I don't experience this bug anymore.

Thanks, marking as closed.

Cheers,
        Moritz

--- End Message ---
Reply to: