Hide Forgot
Created attachment 513567 [details] Test script Description of problem: When I ran the bonding testcase in arp monitor mode, the system unable to handle kernel NULL pointer dereference at show_interrupts+0x12e/0x28e,and panic. Version-Release number of selected component (if applicable): kernel 2.6.18-272.el5 How reproducible: Random Steps to Reproduce: 1.Run the script in attchment Actual results: [root@hp-dl580g7-01 ~]# bonding: bond0: Warning: failed to get speed and duplex from eth4, assumed to be 100Mb/sec and Full. bonding: bond0: Warning: failed to get speed and duplex from eth5, assumed to be 100Mb/sec and Full. Unable to handle kernel NULL pointer dereference at 0000000000000031 RIP: [<ffffffff8006d278>] show_interrupts+0x12e/0x28e PGD 0 Oops: 0000 [1] SMP last sysfs file: /class/net/lo/ifindex CPU 23 Modules linked in: autofs4 hidp rfcomm l2cap bluetooth lockd sunrpc be2iscsi ib_iser rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp bnx2i cnic ipv6 xfrm_nalgo crypto_api uio cxgb3i libcxgbi cxgb3 libiscsi_tcp libiscsi2 scsi_transport_iscsi2 scsi_transport_iscsi loop dm_multipath scsi_dh video backlight sbs power_meter hwmon i2c_ec i2c_core dell_wmi wmi button battery asus_acpi acpi_memhotplug ac parport_pc lp parport joydev sr_mod cdrom sg ixgbe tpm_tis be2net tpm hpilo netxen_nic tpm_bios dca i7core_edac edac_mc serio_raw pcspkr 8021q dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero dm_mirror dm_log dm_mod lpfc scsi_transport_fc ata_piix libata shpchp cciss sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 5940, comm: irqbalance Not tainted 2.6.18-272.el5 #1 RIP: 0010:[<ffffffff8006d278>] [<ffffffff8006d278>] show_interrupts+0x12e/0x28e RSP: 0018:ffff81022dbd1e38 EFLAGS: 00010086 RAX: 0000000000000000 RBX: 00000000000000ff RCX: 0000000000000009 RDX: 0000000000000009 RSI: fffffffffffffff5 RDI: ffffffff802cb126 RBP: ffff81042abaa0c0 R08: 0000000000000018 R09: 0000000000000028 R10: 00000000ffffffff R11: 0000000000000000 R12: 00000000000000e5 R13: 0000000000000001 R14: ffffffff804538bc R15: 0000000000000216 FS: 00002b810e8536e0(0000) GS:ffff81024730fcc0(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 0000000000000031 CR3: 000000022dbbc000 CR4: 00000000000006a0 Process irqbalance (pid: 5940, threadinfo ffff81022dbd0000, task ffff81022da2f100) Stack: ffff810107e96980 ffff81042abaa0c0 ffff81022dbd1e90 0000000000000000 0000000000000334 00000000000000cc 00002b810da1a0cc ffffffff8003f4d1 ffff81022dbd1f50 ffff81043bd1eac0 ffff81042abaa0f0 00000000000000e5 Call Trace: [<ffffffff8003f4d1>] seq_read+0x1b8/0x28c [<ffffffff801093e8>] proc_reg_read+0x7e/0x99 [<ffffffff8000b7c7>] vfs_read+0xcb/0x171 [<ffffffff80011d5a>] sys_read+0x45/0x6e [<ffffffff8005d28d>] tracesys+0xd5/0xe0 Code: 49 8b 55 30 48 c7 c6 5e 1d 2b 80 48 89 ef 31 c0 e8 ce 87 fe RIP [<ffffffff8006d278>] show_interrupts+0x12e/0x28e RSP <ffff81022dbd1e38> CR2: 0000000000000031 <0>Kernel panic - not syncing: Fatal exception Expected results: No panic Additional info:
Do you know if this was reproducible on RHEL5.6 too?
(In reply to comment #2) > Do you know if this was reproducible on RHEL5.6 too? yes.
It can be triggered the panic on 2.6.18-238.el5.
No response. Please reopen if this is not fixed by patch for bug 698728. *** This bug has been marked as a duplicate of bug 698728 ***