Description of problem: Run rds-info from rds-tools 2.0.6 on Version-Release number of selected component (if applicable): kernel-2.6.38.8-32.fc15.x86_64 How reproducible: Always Steps to Reproduce: 0. boot system 1. wget http://oss.oracle.com/projects/rds/dist/files/sources/rds-tools-2.0.6.tar.gz 2. cd rds-tools-2.0.6 3. ./configure && make 4. ./rds-info Actual results: [462923.474297] ------------[ cut here ]------------ [462923.479015] WARNING: at kernel/softirq.c:159 _local_bh_enable_ip+0x44/0x8e() [462923.486151] Hardware name: X8DTH-i/6/iF/6F [462923.490336] Modules linked in: rds ipmi_devintf ib_ipoib rdma_ucm ib_ucm ib_uverbs ib_umad rdma_cm ib_cm iw_cm w83627ehf hwmon_vid adm1021 ib_addr ib_sa ipmi_si ipmi_msghandler mlx4_ib ib_mad ib_core mlx4_en ghes microcode hed serio_raw ses enclosure i7core_edac mlx4_core iTCO_wdt igb joydev i2c_i801 edac_core i2c_core iTCO_vendor_support ioatdma dca ipv6 dm_round_robin mpt2sas scsi_transport_sas raid_class dm_multipath [last unloaded: scsi_wait_scan] [462923.531330] Pid: 2161, comm: rds-info Not tainted 2.6.38.8-32.fc15.x86_64 #1 [462923.538468] Call Trace: [462923.541009] [<ffffffff8105511a>] warn_slowpath_common+0x83/0x9b [462923.547109] [<ffffffff8105514c>] warn_slowpath_null+0x1a/0x1c [462923.553037] [<ffffffff8105a546>] _local_bh_enable_ip+0x44/0x8e [462923.559049] [<ffffffff8105a59e>] local_bh_enable_ip+0xe/0x10 [462923.564891] [<ffffffff81475b1d>] _raw_read_unlock_bh+0x15/0x17 [462923.570903] [<ffffffff813b6e10>] sock_i_ino+0x3b/0x43 [462923.576141] [<ffffffffa01e77c3>] rds_sock_info+0xa7/0x119 [rds] [462923.582238] [<ffffffffa01e9402>] rds_info_getsockopt+0x11a/0x1b8 [rds] [462923.589153] [<ffffffffa01e78ce>] rds_getsockopt+0x70/0xcc [rds] [462923.595453] [<ffffffff813b51a2>] sys_getsockopt+0x7a/0x98 [462923.601230] [<ffffffff81009bc2>] system_call_fastpath+0x16/0x1b [462923.607527] ---[ end trace d6257fa12728aa32 ]--- Expected results: No warning Additional info: Seems like there was a patch that could address this in February: https://lkml.org/lkml/2011/2/17/607
The patch you linked to doesn't look related to this oops at all given that you aren't using the pch_uart or pcm_dma modules. Could you try to recreate this with the latest 2.6.40.x F15 kernel update?
Reproduced this with rds-tools 2.0.6 which is up for review: https://bugzilla.redhat.com/show_bug.cgi?id=772243 while running 3.1.1-1.fc16.x86_64.
Here's another link to what seems to be an actual discussion about this issue: http://comments.gmane.org/gmane.linux.network/211976
(In reply to comment #3) > Here's another link to what seems to be an actual discussion about this issue: > > http://comments.gmane.org/gmane.linux.network/211976 That discussion died out entirely. Since that one fared so well, I started another: http://article.gmane.org/gmane.linux.network/218645
(In reply to comment #4) > (In reply to comment #3) > > Here's another link to what seems to be an actual discussion about this issue: > > > > http://comments.gmane.org/gmane.linux.network/211976 > > That discussion died out entirely. Since that one fared so well, I started > another: > > http://article.gmane.org/gmane.linux.network/218645 Sweet, that worked. I tested a patch against a rawhide kernel and the issue is resolved (at least that particular backtrace). Once it hits Linus' tree, I'll look at backporting it to f16.
Patch applied in Fedora git. Will be in the next build for f16.
kernel-3.2.2-1.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/kernel-3.2.2-1.fc16
Package kernel-3.2.2-1.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing kernel-3.2.2-1.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-0949/kernel-3.2.2-1.fc16 then log in and leave karma (feedback).
kernel-3.2.2-1.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.