Bug 2442 - system crashes from time to time
Summary: system crashes from time to time
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2011-08-17 11:01 CEST by sagi yosef
Modified: 2012-05-01 17:41 CEST (History)
1 user (show)

See Also:
Source RPM: kernel-tmb-laptop
CVE:
Status comment:


Attachments

Description sagi yosef 2011-08-17 11:01:42 CEST
Description of problem:

Occasionally (once in a few hours), the desktop becomes garbaged (I use ATI based T60 thinkpad) and only after alt-backspace I recover.

The installation uses the radeon driver and at first it seemed as if something wrong with it.  However, looking at the system logs I got the following, which may indicate of a file-system caching problems in the kernel:

Aug 17 11:03:20 wseal kernel: ------------[ cut here ]------------
Aug 17 11:03:20 wseal kernel: kernel BUG at fs/dcache.c:947!
Aug 17 11:03:20 wseal kernel: invalid opcode: 0000 [#1] SMP 
Aug 17 11:03:20 wseal kernel: last sysfs file: /sys/devices/system/cpu/cpu1/cache/index2/shared_cpu_map
Aug 17 11:03:20 wseal kernel: Modules linked in: iptable_filter ip_tables x_tables af_packet sit tunnel4 nls_iso8859_1 nls_c
p437 vfat fat uas usb_storage nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc autofs4 ipv6 vboxnetadp vboxnetflt 
vboxdrv rfcomm sco bnep arc4 l2cap btusb ecb iwl3945 snd_hda_codec_analog iwlcore bluetooth e1000e iTCO_wdt iTCO_vendor_supp
ort sr_mod sg mac80211 rng_core snd_hda_intel cfg80211 snd_hda_codec i2c_i801 snd_hwdep binfmt_misc fuse ext3 jbd pcmcia yen
ta_socket pcmcia_rsrc pcmcia_core cpufreq_ondemand cpufreq_conservative cpufreq_powersave acpi_cpufreq freq_table mperf hdap
s input_polldev dm_mod thinkpad_acpi rfkill snd_seq_dummy irda snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm
_oss snd_pcm snd_timer snd_page_alloc snd_mixer_oss crc_ccitt joydev battery ac button snd soundcore video tpm_tis tpm nvram tpm_bios rtc_cmos processor thermal evdev ide_pci_generic ide_gd_mod ide_core pata_acpi ata_generic ahci libahci ata_piix libata sd_mod scsi_mod crc_t10dif e
Aug 17 11:03:20 wseal kernel: xt4 jbd2 crc16 uhci_hcd ohci_hcd ehci_hcd usbhid hid usbcore radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core
Aug 17 11:03:20 wseal kernel: 
Aug 17 11:03:20 wseal kernel: Pid: 10199, comm: automount Not tainted 2.6.38.7-tmb-laptop-1.mga #1 LENOVO 2007F4G/2007F4G
Aug 17 11:03:20 wseal kernel: EIP: 0060:[<c01e4149>] EFLAGS: 00010282 CPU: 0
Aug 17 11:03:20 wseal kernel: EIP is at shrink_dcache_for_umount_subtree+0x199/0x1a0
Aug 17 11:03:20 wseal kernel: EAX: 00000055 EBX: d5454400 ECX: c055a31c EDX: ffffffae
Aug 17 11:03:20 wseal kernel: ESI: f52794c8 EDI: e6bae758 EBP: dd18fed0 ESP: dd18fea4
Aug 17 11:03:20 wseal kernel: DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068
Aug 17 11:03:20 wseal kernel: Process automount (pid: 10199, ti=dd18e000 task=f1068b10 task.ti=dd18e000)
Aug 17 11:03:20 wseal kernel: Stack:
Aug 17 11:03:20 wseal kernel: c04d80b4 d5454400 001e3284 d5454424 00000001 f52794c8 e6bae758 d5454424
Aug 17 11:03:20 wseal kernel: e6bae600 d5454400 f5279080 dd18fee0 c01e4424 e6bae600 e9d9c580 dd18fefc
Aug 17 11:03:20 wseal kernel: c01d2ea0 d545444c 0019f04e 0000001a e9d9c580 c05dd508 dd18ff08 c01d2fcc
Aug 17 11:03:20 wseal kernel: Call Trace:
Aug 17 11:03:20 wseal kernel: [<c01e4424>] shrink_dcache_for_umount+0x34/0x60
Aug 17 11:03:20 wseal kernel: [<c01d2ea0>] generic_shutdown_super+0x20/0xd0
Aug 17 11:03:20 wseal kernel: [<c01d2fcc>] kill_anon_super+0xc/0x40
Aug 17 11:03:20 wseal kernel: [<c01d3019>] kill_litter_super+0x19/0x20
Aug 17 11:03:20 wseal kernel: [<f5275248>] autofs4_kill_sb+0x38/0x50 [autofs4]
Aug 17 11:03:20 wseal kernel: [<c01d3205>] deactivate_locked_super+0x35/0x60
Aug 17 11:03:20 wseal kernel: [<c01d3aa3>] deactivate_super+0x43/0x60
Aug 17 11:03:20 wseal kernel: [<c01e9344>] mntput_no_expire+0xa4/0xf0
Aug 17 11:03:20 wseal kernel: [<c01e9c10>] sys_umount+0x60/0x320
Aug 17 11:03:20 wseal kernel: [<c01e9ee9>] sys_oldumount+0x19/0x20
Aug 17 11:03:20 wseal kernel: [<c0102ecc>] sysenter_do_call+0x12/0x22
Aug 17 11:03:20 wseal kernel: [<c0189375>] ? alloc_chunk+0x15/0x70
Aug 17 11:03:20 wseal kernel: Code: 03 8b 51 60 89 44 24 10 8b 45 f0 89 7c 24 18 89 74 24 14 89 54 24 08 89 5c 24 04 89 44 24 0c c7 04 24 b4 80 4d c0 e8 e8 61 20 00 <0f> 0b 0f 0b 8d 76 00 55 89 e5 57 56 53 83 ec 08 89 45 f0 83 c0 
Aug 17 11:03:20 wseal kernel: EIP: [<c01e4149>] shrink_dcache_for_umount_subtree+0x199/0x1a0 SS:ESP 0068:dd18fea4
Aug 17 11:03:20 wseal kernel: ---[ end trace 5fd4888182a2ec34 ]---


Version-Release number of selected component (if applicable):

kernel-tmb-laptop-2.6.38.7-1.mga and autofs-5.0.5-4.mga1.src.rpm

How reproducible:

Don't know.
Manuel Hiebel 2011-09-03 22:42:27 CEST

Assignee: bugsquad => tmb
Source RPM: kernel-tmb-laptop-2.6.38.7-1.mga, autofs-5.0.5-4.mga1.src.rpm => kernel-tmb-laptop

Comment 1 Marja Van Waes 2011-12-29 20:38:16 CET
pinging because this  bug had no activity since almost 4 months ago, but still has the status NEW


@ Thomas
Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead.

CC: (none) => marja11

Comment 2 Manuel Hiebel 2012-03-22 16:46:10 CET
Is this bug still valid ?

Keywords: (none) => NEEDINFO

Comment 3 Marja Van Waes 2012-04-14 23:14:43 CEST
@ sagi yosef

That question (in comment 2) was for you.

Do you still suffer from this bug?
Comment 4 sagi yosef 2012-04-17 05:19:58 CEST
I've uninstalled the system since, so I really don't know, but I'm planning to try again with the new release, so I'll update the status when it's relevant.

Sagi.
Comment 5 Marja Van Waes 2012-04-17 07:07:23 CEST
(In reply to comment #4)
> I've uninstalled the system since, so I really don't know, but I'm planning to
> try again with the new release, so I'll update the status when it's relevant.
> 
> Sagi.

Thanks, Sagi

By new release you mean Mageia 2 stable, or do you mean beta 3?
Comment 6 sagi yosef 2012-04-17 22:37:42 CEST
Hopefully Beta 3.
Comment 7 Marja Van Waes 2012-04-18 20:11:05 CEST
(In reply to comment #5)
> (In reply to comment #4)
> > I've uninstalled the system since, so I really don't know, but I'm planning to
> > try again with the new release, so I'll update the status when it's relevant.
> > 
> > Sagi.
> 
> Thanks, Sagi
> 
> By new release you mean Mageia 2 stable, or do you mean beta 3?

(In reply to comment #6)
> Hopefully Beta 3.

Great :)

Please give a comment then whatever you find, so even if nothing changed.
Comment 8 sagi yosef 2012-05-01 05:02:42 CEST
Hi.

I've been working with Mageia 2 Beta 3 for a few days now and I'm happy to say that the system is stable and the problem I reported disappeared.

Thanks for your great efforts and hard work!
Comment 9 Marja Van Waes 2012-05-01 17:41:42 CEST
(In reply to comment #8)
> Hi.
> 
> I've been working with Mageia 2 Beta 3 for a few days now and I'm happy to say
> that the system is stable and the problem I reported disappeared.
> 
> Thanks for your great efforts and hard work!

Thanks for the feedback :)

Closing

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.