Bug 664852

Summary:	WARNING: at fs/proc/generic.c:317 __xlate_proc_name+0xbb/0xc2()
Product:	[Fedora] Fedora	Reporter:	Wolfgang Ulbrich <raveit65.sun>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	urgent	Docs Contact:
Priority:	low
Version:	14	CC:	gansalmon, itamar, jonathan, kernel-maint, kmcmartin, madhu.chinakonda
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	kernel-2.6.35.10-74.fc14	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-12-26 19:54:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Wolfgang Ulbrich 2010-12-21 20:56:51 UTC

Description of problem:
With fc14 i get this kernel-oops from abrt after the gnome-desktop is staying
up. But it's no problem for looking tv (dvb-t) with kaffeine.


Version-Release number of selected component (if applicable):
kernel-2.6.35.10-72.fc14
kernel-2.6.35.10-71.fc14
kernel-2.6.35.10-70.fc14
kernel-2.6.35.10-69.fc14
kernel-2.6.35.10-68.fc14
kernel-2.6.35.10-67.fc14

How reproducible:
Starting fc14 and using a technisat (flexicop chip)dvb-t card

Steps to Reproduce:
1.starting the fc14 system
2.in the booting phase the kernel oops
3.
  
Actual results:
getting an kernel-oops

Expected results:
no kernel-oops

Additional info:
I think it is an old bug that you've fixed in kernel-2.6.34 with the 'flexcop-fix-xlate_proc_name-warning.patch'.
See https://bugzilla.redhat.com/show_bug.cgi?id=575873
It seems that i get the same error messages.

Backtrace:
WARNING: at fs/proc/generic.c:317 __xlate_proc_name+0xbb/0xc2()
Hardware name: System Product Name
name 'Technisat/B2C2 FlexCop II/IIb/III Digital TV PCI Driver'
Modules linked in: b2c2_flexcop_pci(+) b2c2_flexcop dvb_core cx24123 cx24113 snd_pcm saa7146 s5h1420 snd_mpu401_uart ttpci_eeprom sky2 snd_rawmidi iTCO_wdt asus_atk0110 snd_seq_device snd_timer shpchp snd iTCO_vendor_support i2c_i801 soundcore i2c_core snd_page_alloc btrfs zlib_deflate libcrc32c 3w_9xxx
Pid: 616, comm: modprobe Tainted: P            2.6.35.10-72.fc14.x86_64 #1
Call Trace:
 [<ffffffff8104d999>] warn_slowpath_common+0x85/0x9d
 [<ffffffff8104da54>] warn_slowpath_fmt+0x46/0x48
 [<ffffffff8121f7cb>] ? string.clone.2+0x3d/0xa4
 [<ffffffff81164c63>] __xlate_proc_name+0xbb/0xc2
 [<ffffffff8116524c>] __proc_create+0x55/0x129
 [<ffffffff81165582>] proc_mkdir_mode+0x2e/0x5a
 [<ffffffff811655c4>] proc_mkdir+0x16/0x18
 [<ffffffff810a8790>] register_handler_proc+0xf3/0x11d
 [<ffffffff810a6ac3>] __setup_irq+0x287/0x31c
 [<ffffffffa00bd14b>] ? flexcop_pci_isr+0x0/0x147 [b2c2_flexcop_pci]
 [<ffffffff810a6c88>] request_threaded_irq+0x130/0x190
 [<ffffffffa00bd433>] flexcop_pci_probe+0x1a1/0x2f3 [b2c2_flexcop_pci]
 [<ffffffff81232e49>] local_pci_probe+0x17/0x1b
 [<ffffffff81233604>] pci_device_probe+0xd2/0x104
 [<ffffffff8116f9da>] ? sysfs_create_link+0x13/0x15
 [<ffffffff812d804b>] driver_probe_device+0x14b/0x271
 [<ffffffff812d81ce>] __driver_attach+0x5d/0x81
 [<ffffffff812d8171>] ? __driver_attach+0x0/0x81
 [<ffffffff812d6f4f>] bus_for_each_dev+0x56/0x82
 [<ffffffff812d7c1c>] driver_attach+0x1e/0x20
 [<ffffffff812d77f6>] bus_add_driver+0xf1/0x25e
 [<ffffffff812d8432>] driver_register+0x9b/0x108
 [<ffffffff81233830>] __pci_register_driver+0x56/0xc2
 [<ffffffffa0bbe000>] ? flexcop_pci_module_init+0x0/0x20 [b2c2_flexcop_pci]
 [<ffffffffa0bbe01e>] flexcop_pci_module_init+0x1e/0x20 [b2c2_flexcop_pci]
 [<ffffffff810021a1>] do_one_initcall+0x5e/0x155
 [<ffffffff8107cc7d>] sys_init_module+0xa6/0x1e4
 [<ffffffff81009cf2>] system_call_fastpath+0x16/0x1b

So pls reenable this patch again if you've drop out this patch.

Comment 1 Kyle McMartin 2010-12-21 21:10:15 UTC

Hrm, it is enabled...

Comment 2 Kyle McMartin 2010-12-21 21:11:34 UTC

Ah, I see, fixing. Thanks.

Comment 3 Kyle McMartin 2010-12-21 21:17:55 UTC

For some reason, Jarod's v4l rebase decided to trample over this patch despite it having been sent upstream. I'll go kick people, thanks.

Comment 4 Kyle McMartin 2010-12-21 21:33:05 UTC

Could you please confirm it fixed in this scratch build?
http://koji.fedoraproject.org/koji/taskinfo?taskID=2682721

Comment 5 Wolfgang Ulbrich 2010-12-21 23:13:29 UTC

Perfect!
Your scratch kernel build working well.
The error messages are gone away.
Thx for your very quick reaction...........respect!

One question, is it possible to fix kernel 2.6.36 and 2.6.37 with this patch for fedora rawhide?

Wolfgang Ulbrich, berlin germany

Comment 6 Fedora Update System 2010-12-23 20:47:59 UTC

kernel-2.6.35.10-74.fc14 has been submitted as an update for Fedora 14.
https://admin.fedoraproject.org/updates/kernel-2.6.35.10-74.fc14

Comment 7 Kyle McMartin 2010-12-23 20:54:18 UTC

Thanks for the reminder, I've got it in rawhide now and poked upstream about it.

Comment 8 Wolfgang Ulbrich 2010-12-24 10:08:09 UTC

I can confirm that kernel-2.6.35.10-74.fc14 is working well.
No error messages.

Comment 9 Fedora Update System 2010-12-25 00:26:11 UTC

kernel-2.6.35.10-74.fc14 has been pushed to the Fedora 14 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update kernel'.  You can provide feedback for this update here: https://admin.fedoraproject.org/updates/kernel-2.6.35.10-74.fc14

Comment 10 Fedora Update System 2010-12-26 19:54:29 UTC

kernel-2.6.35.10-74.fc14 has been pushed to the Fedora 14 stable repository.  If problems still persist, please make note of it in this bug report.

Comment 11 Wolfgang Ulbrich 2011-01-05 00:16:34 UTC

thx for building new kernel-release for fc14 and fc15.