Bug 544112 - multiple unexpected system hangs
Summary: multiple unexpected system hangs
Keywords:
Status: CLOSED DUPLICATE of bug 537981
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-03 22:50 UTC by SergSmirnov
Modified: 2010-05-10 03:00 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-05-10 03:00:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
syslog_messages (22.08 KB, text/plain)
2009-12-03 22:50 UTC, SergSmirnov
no flags Details

Description SergSmirnov 2009-12-03 22:50:37 UTC
Created attachment 375947 [details]
syslog_messages

Description of problem:

System hangs after a few days of normal operation.

Version-Release number of selected component (if applicable):
kernel 2.6.31.5-127.fc12.i686

How reproducible:
Boot the system and wait

Steps to Reproduce:
1. Boot up the system
2. Work as usual, in a normal running condition
3. Wait and get crash

syslog messages:
...
------------[ cut here ]------------
WARNING: at lib/list_debug.c:30 __list_add+0x44/0x5c() (Not tainted)
Hardware name:         
list_add corruption. prev->next should be next (f6c3f8e0), but was f2063fb0. (prev=f2063fb0).
Modules linked in: fuse ipv6 p4_clockmod dm_multipath uinput snd_intel8x0 snd_ac97_codec ac97_bus snd_seq snd_seq_device snd_pcm snd_timer snd ppdev parport_pc soundcore parport snd_page_alloc 3c59x iTCO_wdt iTCO_vendor_support mii i2c_i801 intel_rng floppy radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Pid: 1019, comm: Xorg Not tainted 2.6.31.5-127.fc12.i686 #1
Call Trace:
 [<c0436d93>] warn_slowpath_common+0x70/0x87
 [<c059da88>] ? __list_add+0x44/0x5c
 [<c0436de8>] warn_slowpath_fmt+0x29/0x2c
 [<c059da88>] __list_add+0x44/0x5c
 [<f7d6e857>] radeon_object_create+0x16f/0x17c [radeon]
 [<f7d781e8>] radeon_gem_object_create+0x6b/0xc7 [radeon]
 [<f7d78298>] radeon_gem_create_ioctl+0x54/0xcc [radeon]
 [<f7c7f941>] drm_ioctl+0x205/0x2a8 [drm]
 [<f7d78244>] ? radeon_gem_create_ioctl+0x0/0xcc [radeon]
 [<c0564721>] ? inode_has_perm+0x69/0x84
 [<c05647c5>] ? file_has_perm+0x89/0xa3
 [<c04cad2a>] vfs_ioctl+0x5c/0x76
 [<c04cb28a>] do_vfs_ioctl+0x498/0x4d6
 [<c0564a69>] ? selinux_file_ioctl+0x43/0x46
 [<c04cb30e>] sys_ioctl+0x46/0x66
 [<c040363c>] syscall_call+0x7/0xb
---[ end trace b29dc7970ea76ed5 ]---

...

Comment 1 SergSmirnov 2009-12-04 01:28:37 UTC
I've just updated entire system to the latest packages.
The new kernel - 2.6.31.6-145.fc12.i686

waiting for a new crashes.. :)

Comment 2 SergSmirnov 2009-12-08 02:42:01 UTC
still get the crashes.
updates didn't solve the problem :(

==
Dec  8 03:15:26 chupacabra kernel: ------------[ cut here ]------------
Dec  8 03:15:26 chupacabra kernel: WARNING: at lib/list_debug.c:30 __list_add+0x44/0x5c() (Not tainted)
Dec  8 03:15:26 chupacabra kernel: Hardware name:
Dec  8 03:15:26 chupacabra kernel: list_add corruption. prev->next should be next (f656c8e0), but was c96405b0. (prev=c96405b0).
Dec  8 03:15:26 chupacabra kernel: Modules linked in: vfat fat usb_storage fuse ipv6 p4_clockmod dm_multipath uinput snd_intel8x0 snd_ac97_codec ac97_bus snd
_seq snd_seq_device snd_pcm snd_timer ppdev parport_pc parport 3c59x iTCO_wdt mii iTCO_vendor_support snd soundcore i2c_i801 snd_page_alloc intel_rng floppy
radeon ttm drm_kms_helper drm i2c_algo_bit i2c_core [last unloaded: scsi_wait_scan]
Dec  8 03:15:26 chupacabra kernel: Pid: 1039, comm: Xorg Not tainted 2.6.31.6-145.fc12.i686 #1
Dec  8 03:15:26 chupacabra kernel: Call Trace:
Dec  8 03:15:26 chupacabra kernel: [<c0436d8b>] warn_slowpath_common+0x70/0x87
Dec  8 03:15:26 chupacabra kernel: [<c059db38>] ? __list_add+0x44/0x5c
Dec  8 03:15:26 chupacabra kernel: [<c0436de0>] warn_slowpath_fmt+0x29/0x2c
Dec  8 03:15:26 chupacabra kernel: [<c059db38>] __list_add+0x44/0x5c
Dec  8 03:15:26 chupacabra kernel: [<f7d7115f>] radeon_object_create+0x16f/0x17c [radeon]
Dec  8 03:15:26 chupacabra kernel: [<f7d7af29>] radeon_gem_object_create+0x6b/0xc7 [radeon]
Dec  8 03:15:26 chupacabra kernel: [<f7d7afd9>] radeon_gem_create_ioctl+0x54/0xcc [radeon]
Dec  8 03:15:26 chupacabra kernel: [<f7c7f941>] drm_ioctl+0x205/0x2a8 [drm]
Dec  8 03:15:26 chupacabra kernel: [<f7d7af85>] ? radeon_gem_create_ioctl+0x0/0xcc [radeon]
Dec  8 03:15:26 chupacabra kernel: [<c05647d1>] ? inode_has_perm+0x69/0x84
Dec  8 03:15:26 chupacabra kernel: [<c0564875>] ? file_has_perm+0x89/0xa3
Dec  8 03:15:26 chupacabra kernel: [<c04cadda>] vfs_ioctl+0x5c/0x76
Dec  8 03:15:26 chupacabra kernel: [<c04cb33a>] do_vfs_ioctl+0x498/0x4d6
Dec  8 03:15:26 chupacabra kernel: [<c0564b19>] ? selinux_file_ioctl+0x43/0x46
Dec  8 03:15:26 chupacabra kernel: [<c04cb3be>] sys_ioctl+0x46/0x66
Dec  8 03:15:26 chupacabra kernel: [<c040363c>] syscall_call+0x7/0xb
Dec  8 03:15:26 chupacabra kernel: ---[ end trace c8f64931fd952273 ]---
==

When I used a fc7 before for a long time I haven't had such problems.

And I've found a few lines before crash like this:
--
kernel: BUG: unable to handle kernel NULL pointer dereference at (null)
kernel: BUG: unable to handle kernel NULL pointer dereference at 00000010
--
any thoughts?

Comment 3 Thomas Lake 2009-12-10 08:30:19 UTC
2.6.31.6-162.fc12.i686.PAE

Getting frequent ABRT notifications about this oops

http://kerneloops.org/oops.php?number=664510 refers to this bugzilla entry, with a few hundred reported oopses against it

Comment 4 Jeff Raber 2010-05-05 07:55:52 UTC
Is this a dup of Bug 537981?

Reporter, could you check if this issue has is fixed in
kernel-2.6.32.8-58.fc12.x86_64 ???


-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

Comment 5 SergSmirnov 2010-05-05 08:25:04 UTC
hi Jeff.

now I'm running -

~$ uname -r
2.6.32.9-70.fc12.i686.PAE

and the system still up - 

~$ w
 12:13:36 up 21 days, 16:03,  2 users,  load average: 1.06, 1.02, 1.00

I will watch and get back if it will crash again, yup?

Comment 6 Jeff Raber 2010-05-10 03:00:04 UTC
Closing as a dup of 537981 as I believe they are the same issue (based on the backtrace).

-- 
Fedora Bugzappers volunteer triage team
https://fedoraproject.org/wiki/BugZappers

*** This bug has been marked as a duplicate of bug 537981 ***


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