Roland Dreier <[email protected]> wrote: > On Tue, Nov 15, 2011 at 11:10 AM, Roland Dreier <[email protected]> > wrote: >> Sorry, I missed the "vanilla" in your original email and just saw > "OFED". >> >> Anyway yes, looks like a bug in the mlx4 driver. > > Actually where is your mlx4 driver coming from? The upstream kernel or OFED?
It comes from OFED. Here it's from OFED-1.5.4 (although you see v1.0-ofed1.5.3 in the kernel log).I think at this point it's useful to show all relevant (i.e. ofed regarding) parts of the kernel log: [ 195.010076] mlx4_core: Mellanox ConnectX core driver v1.0-ofed1.5.3 (January 19, 2011) [ 195.010208] mlx4_core: Initializing 0000:12:00.0 [ 195.010294] PCI: Enabling device: (0000:12:00.0), cmd 2 [ 195.010356] mlx4_core 0000:12:00.0: Warning: couldn't set 64-bit PCI DMA mask. [ 195.010469] mlx4_core 0000:12:00.0: Warning: couldn't set 64-bit consistent PCI DMA mask. <snip> [ 197.479244] Kernel unaligned access at TPC[10061624] mlx4_QUERY_ADAPTER+0xf0/0x11c [mlx4_core] [ 197.479424] Kernel unaligned access at TPC[10061624] mlx4_QUERY_ADAPTER+0xf0/0x11c [mlx4_core] [ 197.479594] Kernel unaligned access at TPC[10061624] mlx4_QUERY_ADAPTER+0xf0/0x11c [mlx4_core] [ 197.479764] Kernel unaligned access at TPC[10061624] mlx4_QUERY_ADAPTER+0xf0/0x11c [mlx4_core] <snip> [ 231.377790] mlx4_ib: Mellanox ConnectX InfiniBand driver v1.0-ofed1.5.3 (January 19, 2011) [ 232.217620] ADDRCONF(NETDEV_UP): ib0: link is not ready [ 233.782679] ib0: enabling connected mode will cause multicast packet drops [ 233.782810] ib0: mtu > 2044 will cause multicast packet drops. [ 233.782916] ib0: mtu > 2044 will cause multicast packet drops. [ 234.860368] ib1: enabling connected mode will cause multicast packet drops [ 234.860502] ib1: mtu > 2044 will cause multicast packet drops. [ 234.860613] ib1: mtu > 2044 will cause multicast packet drops. [ 235.225652] ADDRCONF(NETDEV_CHANGE): ib0: link becomes ready [ 246.210384] ib0: no IPv6 routers present [ 650.857233] swap_free: Bad swap file entry 100005e000061800 [ 650.857363] BUG: Bad page map in process ibv_devinfo pte:bc0000c300104848 pmd:00fc9bc4 [ 650.857481] addr:fffff80100114000 vm_flags:000844fa anon_vma: (null) mapping:fffff807f6e06b38 index:6180082 [ 650.857661] vma->vm_file->f_op->mmap: ib_uverbs_mmap+0x8/0x38 [ib_uverbs] [ 650.857708] Call Trace: [ 650.857747] [00000000004cd430] unmap_vmas+0x514/0x7f4 [ 650.857826] [00000000004d114c] unmap_region+0xb4/0x164 [ 650.857875] [00000000004d2198] do_munmap+0x2a8/0x31c [ 650.857958] [000000000042d340] SyS_64_munmap+0x88/0xa8 [ 650.858042] [0000000000406154] linux_sparc_syscall+0x34/0x44 [ 650.858116] Disabling lock debugging due to kernel taint Please ask if you need more information. I'll provide them promptly. Regards, Lukas -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
