Description of problem: After installing F14 i686 system, there are after reboot oops in "/var/log/messages" as: Oct 1 06:59:25 ns kernel: imklog 4.6.3, log source = /proc/kmsg started. Oct 1 07:08:26 ns kernel: ------------[ cut here ]------------ Oct 1 07:08:26 ns kernel: WARNING: at lib/dma-debug.c:791 check_unmap+0x7a/0x59b() Oct 1 07:08:26 ns kernel: Hardware name: EP45-DQ6 Oct 1 07:08:26 ns kernel: dl2k 0000:09:00.0: DMA-API: device driver tries to free an invalid DMA memory address Oct 1 07:08:26 ns kernel: Modules linked in: bluetooth rfkill nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat xt_u32 ipt_LOG xt_limit uinput iTCO_wdt i2c_i801 iTCO_vendor_support r8169 mii i2c_core dl2k microcode raid1 [last unloaded: hwmon_vid] Oct 1 07:08:26 ns kernel: Pid: 2454, comm: ip Tainted: G W 2.6.35.4-28.fc14.i686.PAE #1 Oct 1 07:08:26 ns kernel: Call Trace: Oct 1 07:08:26 ns kernel: [<c0441f39>] warn_slowpath_common+0x6a/0x7f Oct 1 07:08:26 ns kernel: [<c05dfbc6>] ? check_unmap+0x7a/0x59b Oct 1 07:08:26 ns kernel: [<c0441fc1>] warn_slowpath_fmt+0x2b/0x2f Oct 1 07:08:26 ns kernel: [<c05dfbc6>] check_unmap+0x7a/0x59b Oct 1 07:08:26 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 07:08:26 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:08:26 ns kernel: [<c05daf43>] ? debug_object_deactivate+0x28/0x92 Oct 1 07:08:26 ns kernel: [<c05e0195>] debug_dma_unmap_page+0x5a/0x62 Oct 1 07:08:26 ns kernel: [<f7e6b2d5>] pci_unmap_single+0x58/0x63 [dl2k] Oct 1 07:08:26 ns kernel: [<f7e6cd5c>] rio_close+0x9e/0x114 [dl2k] Oct 1 07:08:26 ns kernel: [<c075058a>] __dev_close+0x70/0x85 Oct 1 07:08:26 ns kernel: [<c07519d9>] __dev_change_flags+0x98/0x10d Oct 1 07:08:26 ns kernel: [<c0751abe>] dev_change_flags+0x18/0x44 Oct 1 07:08:26 ns kernel: [<c075a44f>] do_setlink+0x253/0x52e Oct 1 07:08:26 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 07:08:26 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:08:26 ns kernel: [<c04d0bf9>] ? handle_mm_fault+0x342/0x8f4 Oct 1 07:08:26 ns kernel: [<c075af7a>] rtnl_newlink+0x218/0x3a6 Oct 1 07:08:26 ns kernel: [<c075ae18>] ? rtnl_newlink+0xb6/0x3a6 Oct 1 07:08:26 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:08:26 ns kernel: [<c075a0f0>] ? rtnl_lock+0x14/0x16 Oct 1 07:08:26 ns kernel: [<c075a0f0>] ? rtnl_lock+0x14/0x16 Oct 1 07:08:26 ns kernel: [<c07e3e85>] ? __mutex_lock_common+0x2d0/0x2da Oct 1 07:08:26 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:08:26 ns kernel: [<c075ad62>] ? rtnl_newlink+0x0/0x3a6 Oct 1 07:08:26 ns kernel: [<c075abb7>] rtnetlink_rcv_msg+0x19c/0x1ab Oct 1 07:08:26 ns kernel: [<c075aa1b>] ? rtnetlink_rcv_msg+0x0/0x1ab Oct 1 07:08:26 ns kernel: [<c076a19a>] netlink_rcv_skb+0x37/0x78 Oct 1 07:08:26 ns kernel: [<c075a112>] rtnetlink_rcv+0x20/0x27 Oct 1 07:08:26 ns kernel: [<c0769d7b>] netlink_unicast+0xc6/0x121 Oct 1 07:08:26 ns kernel: [<c076a004>] netlink_sendmsg+0x22e/0x23b Oct 1 07:08:26 ns kernel: [<c0740d65>] __sock_sendmsg+0x56/0x5f Oct 1 07:08:26 ns kernel: [<c0741056>] sock_sendmsg+0x98/0xac Oct 1 07:08:26 ns kernel: [<c04ce553>] ? might_fault+0x4c/0x86 Oct 1 07:08:26 ns kernel: [<c0469b00>] ? lock_release+0x17f/0x186 Oct 1 07:08:26 ns kernel: [<c07497a1>] ? copy_from_user+0xd/0xf Oct 1 07:08:26 ns kernel: [<c0749ad7>] ? verify_iovec+0x43/0x70 Oct 1 07:08:26 ns kernel: [<c0742b45>] sys_sendmsg+0x182/0x1e6 Oct 1 07:08:26 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 07:08:26 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:08:26 ns kernel: [<c04cec8e>] ? __do_fault+0x206/0x396 Oct 1 07:08:26 ns kernel: [<c04cedf2>] ? __do_fault+0x36a/0x396 Oct 1 07:08:26 ns kernel: [<c0469bb8>] ? lock_acquire+0xb1/0xbc Oct 1 07:08:26 ns kernel: [<c04ce553>] ? might_fault+0x4c/0x86 Oct 1 07:08:26 ns kernel: [<c0469b00>] ? lock_release+0x17f/0x186 Oct 1 07:08:26 ns kernel: [<c0742f43>] sys_socketcall+0x168/0x1a8 Oct 1 07:08:26 ns kernel: [<c05d5d74>] ? trace_hardirqs_on_thunk+0xc/0x10 Oct 1 07:08:26 ns kernel: [<c04089df>] sysenter_do_call+0x12/0x38 Oct 1 07:08:26 ns kernel: ---[ end trace a70d91368aa35943 ]--- Oct 1 07:13:51 ns kernel: imklog 4.6.3, log source = /proc/kmsg started. Oct 1 07:26:33 ns kernel: ------------[ cut here ]------------ Oct 1 07:26:33 ns kernel: WARNING: at lib/dma-debug.c:791 check_unmap+0x7a/0x59b() Oct 1 07:26:33 ns kernel: Hardware name: EP45-DQ6 Oct 1 07:26:33 ns kernel: dl2k 0000:09:00.0: DMA-API: device driver tries to free an invalid DMA memory address Oct 1 07:26:33 ns kernel: Modules linked in: bluetooth rfkill cpufreq_ondemand acpi_cpufreq mperf nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat xt_u32 ipt_LOG xt_limit uinput i2c_i801 i2c_core microcode e1000e dl2k r8169 iTCO_wdt iTCO_vendor_support mii raid1 [last unloaded: hwmon_vid] Oct 1 07:26:33 ns kernel: Pid: 2845, comm: ip Not tainted 2.6.35.4-28.fc14.i686.PAE #1 Oct 1 07:26:33 ns kernel: Call Trace: Oct 1 07:26:33 ns kernel: [<c0441f39>] warn_slowpath_common+0x6a/0x7f Oct 1 07:26:33 ns kernel: [<c05dfbc6>] ? check_unmap+0x7a/0x59b Oct 1 07:26:33 ns kernel: [<c0441fc1>] warn_slowpath_fmt+0x2b/0x2f Oct 1 07:26:33 ns kernel: [<c05dfbc6>] check_unmap+0x7a/0x59b Oct 1 07:26:33 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 07:26:33 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:26:33 ns kernel: [<c05daf43>] ? debug_object_deactivate+0x28/0x92 Oct 1 07:26:33 ns kernel: [<c05e0195>] debug_dma_unmap_page+0x5a/0x62 Oct 1 07:26:33 ns kernel: [<f7fa02d5>] pci_unmap_single+0x58/0x63 [dl2k] Oct 1 07:26:33 ns kernel: [<f7fa1d5c>] rio_close+0x9e/0x114 [dl2k] Oct 1 07:26:33 ns kernel: [<c075058a>] __dev_close+0x70/0x85 Oct 1 07:26:33 ns kernel: [<c07519d9>] __dev_change_flags+0x98/0x10d Oct 1 07:26:33 ns kernel: [<c0751abe>] dev_change_flags+0x18/0x44 Oct 1 07:26:33 ns kernel: [<c075a44f>] do_setlink+0x253/0x52e Oct 1 07:26:33 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 07:26:33 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:26:33 ns kernel: [<c04d0bf9>] ? handle_mm_fault+0x342/0x8f4 Oct 1 07:26:33 ns kernel: [<c075af7a>] rtnl_newlink+0x218/0x3a6 Oct 1 07:26:33 ns kernel: [<c075ae18>] ? rtnl_newlink+0xb6/0x3a6 Oct 1 07:26:33 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:26:33 ns kernel: [<c075a0f0>] ? rtnl_lock+0x14/0x16 Oct 1 07:26:33 ns kernel: [<c075a0f0>] ? rtnl_lock+0x14/0x16 Oct 1 07:26:33 ns kernel: [<c07e3e85>] ? __mutex_lock_common+0x2d0/0x2da Oct 1 07:26:33 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:26:33 ns kernel: [<c075ad62>] ? rtnl_newlink+0x0/0x3a6 Oct 1 07:26:33 ns kernel: [<c075abb7>] rtnetlink_rcv_msg+0x19c/0x1ab Oct 1 07:26:33 ns kernel: [<c075aa1b>] ? rtnetlink_rcv_msg+0x0/0x1ab Oct 1 07:26:33 ns kernel: [<c076a19a>] netlink_rcv_skb+0x37/0x78 Oct 1 07:26:33 ns kernel: [<c075a112>] rtnetlink_rcv+0x20/0x27 Oct 1 07:26:33 ns kernel: [<c0769d7b>] netlink_unicast+0xc6/0x121 Oct 1 07:26:33 ns kernel: [<c076a004>] netlink_sendmsg+0x22e/0x23b Oct 1 07:26:33 ns kernel: [<c0740d65>] __sock_sendmsg+0x56/0x5f Oct 1 07:26:33 ns kernel: [<c0741056>] sock_sendmsg+0x98/0xac Oct 1 07:26:33 ns kernel: [<c04ce553>] ? might_fault+0x4c/0x86 Oct 1 07:26:33 ns kernel: [<c0469b00>] ? lock_release+0x17f/0x186 Oct 1 07:26:33 ns kernel: [<c07497a1>] ? copy_from_user+0xd/0xf Oct 1 07:26:33 ns kernel: [<c0749ad7>] ? verify_iovec+0x43/0x70 Oct 1 07:26:33 ns kernel: [<c0742b45>] sys_sendmsg+0x182/0x1e6 Oct 1 07:26:33 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 07:26:33 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 07:26:33 ns kernel: [<c04cec8e>] ? __do_fault+0x206/0x396 Oct 1 07:26:33 ns kernel: [<c04cedf2>] ? __do_fault+0x36a/0x396 Oct 1 07:26:33 ns kernel: [<c0469bb8>] ? lock_acquire+0xb1/0xbc Oct 1 07:26:33 ns kernel: [<c04ce553>] ? might_fault+0x4c/0x86 Oct 1 07:26:33 ns kernel: [<c0469b00>] ? lock_release+0x17f/0x186 Oct 1 07:26:33 ns kernel: [<c0742f43>] sys_socketcall+0x168/0x1a8 Oct 1 07:26:33 ns kernel: [<c05d5d74>] ? trace_hardirqs_on_thunk+0xc/0x10 Oct 1 07:26:33 ns kernel: [<c04089df>] sysenter_do_call+0x12/0x38 Oct 1 07:26:33 ns kernel: ---[ end trace c9bd8c211794835b ]--- Oct 1 07:27:46 ns kernel: imklog 4.6.3, log source = /proc/kmsg started. Oct 1 08:30:29 ns kernel: ------------[ cut here ]------------ Oct 1 08:30:29 ns kernel: WARNING: at lib/dma-debug.c:791 check_unmap+0x7a/0x59b() Oct 1 08:30:29 ns kernel: Hardware name: EP45-DQ6 Oct 1 08:30:29 ns kernel: dl2k 0000:09:00.0: DMA-API: device driver tries to free an invalid DMA memory address Oct 1 08:30:29 ns kernel: Modules linked in: bluetooth rfkill it87 hwmon_vid coretemp cpufreq_ondemand acpi_cpufreq mperf nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat xt_u32 ipt_LOG xt_limit uinput r8169 microcode i2c_i801 dl2k i2c_core iTCO_wdt iTCO_vendor_support e1000e mii raid1 [last unloaded: scsi_wait_scan] Oct 1 08:30:29 ns kernel: Pid: 2939, comm: ip Not tainted 2.6.35.4-28.fc14.i686.PAE #1 Oct 1 08:30:29 ns kernel: Call Trace: Oct 1 08:30:29 ns kernel: [<c0441f39>] warn_slowpath_common+0x6a/0x7f Oct 1 08:30:29 ns kernel: [<c05dfbc6>] ? check_unmap+0x7a/0x59b Oct 1 08:30:29 ns kernel: [<c0441fc1>] warn_slowpath_fmt+0x2b/0x2f Oct 1 08:30:29 ns kernel: [<c05dfbc6>] check_unmap+0x7a/0x59b Oct 1 08:30:29 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 08:30:29 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 08:30:29 ns kernel: [<c05daf43>] ? debug_object_deactivate+0x28/0x92 Oct 1 08:30:29 ns kernel: [<c05e0195>] debug_dma_unmap_page+0x5a/0x62 Oct 1 08:30:29 ns kernel: [<f7f632d5>] pci_unmap_single+0x58/0x63 [dl2k] Oct 1 08:30:29 ns kernel: [<f7f64d5c>] rio_close+0x9e/0x114 [dl2k] Oct 1 08:30:29 ns kernel: [<c075058a>] __dev_close+0x70/0x85 Oct 1 08:30:29 ns kernel: [<c07519d9>] __dev_change_flags+0x98/0x10d Oct 1 08:30:29 ns kernel: [<c0751abe>] dev_change_flags+0x18/0x44 Oct 1 08:30:29 ns kernel: [<c075a44f>] do_setlink+0x253/0x52e Oct 1 08:30:29 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 08:30:29 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 08:30:29 ns kernel: [<c04d0bf9>] ? handle_mm_fault+0x342/0x8f4 Oct 1 08:30:29 ns kernel: [<c075af7a>] rtnl_newlink+0x218/0x3a6 Oct 1 08:30:29 ns kernel: [<c075ae18>] ? rtnl_newlink+0xb6/0x3a6 Oct 1 08:30:29 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 08:30:29 ns kernel: [<c075a0f0>] ? rtnl_lock+0x14/0x16 Oct 1 08:30:29 ns kernel: [<c075a0f0>] ? rtnl_lock+0x14/0x16 Oct 1 08:30:29 ns kernel: [<c07e3e85>] ? __mutex_lock_common+0x2d0/0x2da Oct 1 08:30:29 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 08:30:29 ns kernel: [<c075ad62>] ? rtnl_newlink+0x0/0x3a6 Oct 1 08:30:29 ns kernel: [<c075abb7>] rtnetlink_rcv_msg+0x19c/0x1ab Oct 1 08:30:29 ns kernel: [<c075aa1b>] ? rtnetlink_rcv_msg+0x0/0x1ab Oct 1 08:30:29 ns kernel: [<c076a19a>] netlink_rcv_skb+0x37/0x78 Oct 1 08:30:29 ns kernel: [<c075a112>] rtnetlink_rcv+0x20/0x27 Oct 1 08:30:29 ns kernel: [<c0769d7b>] netlink_unicast+0xc6/0x121 Oct 1 08:30:29 ns kernel: [<c076a004>] netlink_sendmsg+0x22e/0x23b Oct 1 08:30:29 ns kernel: [<c0740d65>] __sock_sendmsg+0x56/0x5f Oct 1 08:30:29 ns kernel: [<c0741056>] sock_sendmsg+0x98/0xac Oct 1 08:30:29 ns kernel: [<c04ce553>] ? might_fault+0x4c/0x86 Oct 1 08:30:29 ns kernel: [<c0469b00>] ? lock_release+0x17f/0x186 Oct 1 08:30:29 ns kernel: [<c07497a1>] ? copy_from_user+0xd/0xf Oct 1 08:30:29 ns kernel: [<c0749ad7>] ? verify_iovec+0x43/0x70 Oct 1 08:30:29 ns kernel: [<c0742b45>] sys_sendmsg+0x182/0x1e6 Oct 1 08:30:29 ns kernel: [<c0467ae1>] ? print_lock_contention_bug+0x11/0xa8 Oct 1 08:30:29 ns kernel: [<c0467dad>] ? lock_acquired+0x235/0x23d Oct 1 08:30:29 ns kernel: [<c04cec8e>] ? __do_fault+0x206/0x396 Oct 1 08:30:29 ns kernel: [<c04cedf2>] ? __do_fault+0x36a/0x396 Oct 1 08:30:29 ns kernel: [<c0469bb8>] ? lock_acquire+0xb1/0xbc Oct 1 08:30:29 ns kernel: [<c04ce553>] ? might_fault+0x4c/0x86 Oct 1 08:30:29 ns kernel: [<c0469b00>] ? lock_release+0x17f/0x186 Oct 1 08:30:29 ns kernel: [<c0742f43>] sys_socketcall+0x168/0x1a8 Oct 1 08:30:29 ns kernel: [<c05d5d74>] ? trace_hardirqs_on_thunk+0xc/0x10 Oct 1 08:30:29 ns kernel: [<c04089df>] sysenter_do_call+0x12/0x38 Oct 1 08:30:29 ns kernel: ---[ end trace cca054462005f679 ]--- At top of start each oops I got line about system start (imklog .. started), because, which may be interesting, this oops seems appear only once after system start. From last restart at Oct 1 07:27:46 until now (Oct 4 9:40) there is only one oops occuring at Oct 1 08:30:29, about one hour after system started. And other oopses are several minutes after start too. Second interesting thing for me: in three oopses above, first claims "Tainted" and other two "Not tainted". But system is starting already with same configuration, without some SW (un-)install. Should not be after "Tainted:" kernel module name which taint kernel? Can't it meant thereis any memory corruption rtc? Version-Release number of selected component (if applicable): 2.6.35.4-28.fc14.i686.PAE, F14 actual to 30-Sep-2010 (Fedora distro and updates-testing repos)
Created attachment 452534 [details] f13-dl2k-nulify-fraginfo-after-unmap.patch Proposed fix. Can you apply it, build and test kernel? If not I will prepare kernel rpm with patch.
Please try this kernel when it finish to build: http://koji.fedoraproject.org/koji/taskinfo?taskID=2530611
I've compiled dl2k.ko with Your patch for actual 2.6.35.6-39.fc14.i686.PAE kernel, but this computer will be accessible for me as late as end of this week. And it appears that Your kernel is 2.6.34.7-59.bz639824.fc13.i686, not 2.6.35/F14, and I w\don't want return to this version. There was probably some dl2k development lately, as this card works for me in FC5/2.6.17.axp and FC6/2.6.22.i686 distro/kernels, but not in FC10/2.6.27.i686 kernel, and I not sure when will work in 2.6.34.x kernels. I will report how it works at beginning of next week.
(In reply to comment #3) > And it appears that Your kernel is 2.6.34.7-59.bz639824.fc13.i686, not > 2.6.35/F14, Oops, sorry I missed system version. If you are able to apply a patch that's great. I'm waiting for testing results.
Hello Stanislaw, this server with PCI-X Fiber 1000BASE-SX D-Link Network Adapter DGE-550SX (in 32bit slot) and Your dl2k patch on 2.6.35.6-39.fc14.i686.PAE Fedora kernel now works for 3+ days without problems and without any oopses in /var/log/messages. As it works 24x7 with several tens (more likely hunderts) gigabytes every day throught this D-Link card, I thing this problem is away. One interesant thing which I cannot understand and You maybe should clarify that - folks who owned this server performed at 13-Oct kernel upgrade to version 2.6.35.6-39.fc14.i686.PAE. And although, with previous 2.6.35.4-28.fc14.i686.PAE kernel, above oopses occurs always after from several minutes to several few hours (but only once, as I stated above), with this new kernel problem not occured for all four days when was running. I not know for what kernel/driver version You made this patch, but it was probably little different from this 2.6.35.6-39.fc14.i686.PAE in Fedora (which I patched), as patch program found Your changes at different location - but was patching it: $ patch -p0 <f13-dl2k-nulify-fraginfo-after-unmap.patch patching file a/drivers/net/dl2k.c Hunk #1 succeeded at 1753 (offset -2 lines). Hunk #2 succeeded at 1761 (offset -2 lines). It seems as 2.6.35.6-39.fc14.i686.PAE without Your patch works fine too. Or maybe within these four days not occured some conditions which are needed for this oops?
I think bug is still there. It should be 100% reproducible with ifconfig ethX down. Perhaps on older kernel (or user space) there was condition which make device do the close, what not happens anymore after update.
Patch land in linus tree: http://git.kernel.org/linus/9eb710797a21fa4a9e09ae9c86c4b3ec9d291c2d > It seems as 2.6.35.6-39.fc14.i686.PAE without Your patch works fine too. If bug does not bother you, I will not bother myself for fedora backport :-) Since fix is available on 2.6.38 and never, I'm closing bug with upstream resolution.