Bug 689749

Summary: [abrt] kernel: WARNING: at fs/proc/generic.c:590 proc_register+0x129/0x220() (Not tainted)
Product: [Fedora] Fedora Reporter: Red Hat Case Diagnostics <case-diagnostics>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NEXTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: medium    
Version: 14CC: gansalmon, itamar, jonathan, jwest, kernel-maint, madhu.chinakonda, michal, west, ychavan
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:1336648850
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-07 14:13:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
dmesg from kernel-2.6.35.14-96.fc14.x86_64 with the same problem none

Description Red Hat Case Diagnostics 2011-03-22 11:12:02 UTC
This description generated by Andreas from an ABRT report
architecture: x86_64
cmdline: not_applicable
component: kernel
executable: kernel
kernel: 2.6.32-71.el6.x86_64
package: kernel
reason: WARNING: at fs/proc/generic.c:590 proc_register+0x129/0x220() (Not tainted)
release: Red Hat Enterprise Linux Server release 6.0 (Santiago)
time: 1300817465
uid: 0
backtrace: WARNING: at fs/proc/generic.c:590 proc_register+0x129/0x220() (Not tainted)
Hardware name: K42Jc
proc_dir_entry 'video/GFX0' already registered
Modules linked in: i915(+) drm_kms_helper drm i2c_algo_bit i2c_core video output dm_mod
Pid: 114, comm: modprobe Not tainted 2.6.32-71.el6.x86_64 #1
Call Trace:
 [<ffffffff8106b857>] warn_slowpath_common+0x87/0xc0
 [<ffffffff8106b946>] warn_slowpath_fmt+0x46/0x50
 [<ffffffff811d5089>] proc_register+0x129/0x220
 [<ffffffff811d5832>] proc_mkdir_mode+0x42/0x60
 [<ffffffff811d5866>] proc_mkdir+0x16/0x20
 [<ffffffffa0025ccb>] acpi_video_bus_add+0x239/0x1003 [video]
 [<ffffffff811e132c>] ? sysfs_add_one+0x2c/0x130
 [<ffffffff811e1858>] ? sysfs_do_create_link+0xd8/0x170
 [<ffffffff812b3c14>] acpi_device_probe+0x50/0x122
 [<ffffffff8132edf0>] driver_probe_device+0xa0/0x2a0
 [<ffffffff8132eff0>] ? __driver_attach+0x0/0xb0
 [<ffffffff8132f09b>] __driver_attach+0xab/0xb0
 [<ffffffff8132eff0>] ? __driver_attach+0x0/0xb0
 [<ffffffff8132e054>] bus_for_each_dev+0x64/0x90
 [<ffffffff8132eb8e>] driver_attach+0x1e/0x20
 [<ffffffff8132e490>] bus_add_driver+0x200/0x300
 [<ffffffff8132f3c6>] driver_register+0x76/0x140
 [<ffffffff811d5832>] ? proc_mkdir_mode+0x42/0x60
 [<ffffffff812b5314>] acpi_bus_register_driver+0x43/0x47
 [<ffffffffa0026adc>] acpi_video_register+0x47/0x73 [video]
 [<ffffffffa00d1135>] intel_opregion_init+0x165/0x4c0 [i915]
 [<ffffffffa00a2302>] i915_driver_load+0x792/0x1120 [i915]
 [<ffffffffa00549cc>] ? drm_sysfs_device_add+0x8c/0xc0 [drm]
 [<ffffffffa0051f53>] ? drm_get_minor+0x1d3/0x310 [drm]
 [<ffffffffa00524b8>] drm_get_dev+0x328/0x550 [drm]
 [<ffffffffa00d1a54>] i915_pci_probe+0x15/0x13b [i915]
 [<ffffffff812765d7>] local_pci_probe+0x17/0x20
 [<ffffffff812777c1>] pci_device_probe+0x101/0x120
 [<ffffffff8132ec52>] ? driver_sysfs_add+0x62/0x90
 [<ffffffff8132edf0>] driver_probe_device+0xa0/0x2a0
 [<ffffffff8132f09b>] __driver_attach+0xab/0xb0
 [<ffffffff8132eff0>] ? __driver_attach+0x0/0xb0
 [<ffffffff8132e054>] bus_for_each_dev+0x64/0x90
 [<ffffffff8132eb8e>] driver_attach+0x1e/0x20
 [<ffffffff8132e490>] bus_add_driver+0x200/0x300
 [<ffffffff8132f3c6>] driver_register+0x76/0x140
 [<ffffffff810e1dec>] ? tracepoint_update_probe_range+0xfc/0x130
 [<ffffffff81277a26>] __pci_register_driver+0x56/0xd0
 [<ffffffff814cd7a5>] ? notifier_call_chain+0x55/0x80
 [<ffffffffa004c731>] drm_init+0x111/0x120 [drm]
 [<ffffffff81123f38>] ? register_shrinker+0x48/0x50
 [<ffffffffa00f2000>] ? i915_init+0x0/0x96 [i915]
 [<ffffffffa00f2094>] i915_init+0x94/0x96 [i915]
 [<ffffffff8100a04c>] do_one_initcall+0x3c/0x1d0
 [<ffffffff810af5ef>] sys_init_module+0xdf/0x250
 [<ffffffff81013172>] system_call_fastpath+0x16/0x1b

Comment 1 Red Hat Case Diagnostics 2011-03-22 11:12:25 UTC
Created attachment 486773 [details]
File: backtrace

Comment 4 RHEL Program Management 2011-04-04 02:37:39 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.

Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.

Comment 5 Michal Jaegermann 2011-04-15 00:55:44 UTC
FWTIW I am seeing the same with Fedora 14 2.6.35.12-88.fc14.x86_64 kernel.  To wit:

[    3.346707] ACPI Warning: _BQC returned an invalid level (20100428/video-640)
[    3.347800] acpi device:03: registered as cooling_device2
[    3.348171] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/d
evice:00/LNXVIDEO:00/input/input6
[    3.348227] ACPI: Video Device [GFX0] (multi-head: yes  rom: yes  post: no)
[    3.348319] ------------[ cut here ]------------
[    3.348326] WARNING: at fs/proc/generic.c:583 proc_register+0x158/0x195()
[    3.348329] Hardware name: K52Jc
[    3.348330] proc_dir_entry 'video/GFX0' already registered
....
and so on really like the above.  On every boot. This time this is Asus K52Jc laptop instead of K42Jc.  I just got it so I cannot tell how this was "earlier".

Should I file a separate bug for F14?

Comment 6 Jeremy West 2011-10-05 21:57:26 UTC
Hi Michael.  Actually what I'm going to do is flip this bug over to the Fedora product since the original filer has closed their case and is no longer able to provide data or communicate on a fix.  Let's try to get this fixed in Fedora.

Comment 7 Josh Boyer 2011-10-05 23:19:41 UTC
Michal, are you still using F14 or have you moved on to F15/F16 at this point?

Comment 8 Michal Jaegermann 2011-10-06 00:08:03 UTC
(In reply to comment #6)
> Let's try to get this fixed in Fedora.

Yes, this is consistent.  Nothing really changed in 
2.6.35.14-96.fc14.  As somebody is going to look at this I attach the current complete dmesg.

I am not sure if in my case there are really any serious adverse effects beyond complaints on every boot.

Comment 9 Michal Jaegermann 2011-10-06 00:13:09 UTC
Created attachment 526595 [details]
dmesg from kernel-2.6.35.14-96.fc14.x86_64 with the same problem

Comment 10 Josh Boyer 2011-10-06 13:54:00 UTC
*** Bug 700835 has been marked as a duplicate of this bug. ***

Comment 11 Josh Boyer 2011-10-07 14:13:54 UTC
This entire interface was removed in 2.6.37 with commit 
39fe394d05be43481ceac8b3db19dfd5189097f6.

That is obviously too large of a backport for F14, and there's little point in fixing code that was removed upstream.  Due to the short lifetime remaining on F14, we're not going to fix this bug as it shouldn't be present in F15 or newer.

Thank you for reporting.