Description of problem: Module smsc47m is detected as a valid driver by sensors-detect from lm_sensors package. modprobe-ing it freezes the machine: # modprobe smsc47m1 Unable to handle kernel paging request at 00000002e0be74f0 RIP: [<ffffffff885d74de>] :smsc47m1:smsc47m1_probe+0xd6/0x466 PGD 46f662067 PUD 0 Oops: 0000 [1] SMP last sysfs file: /devices/pci0000:00/0000:00:06.0/0000:03:00.0/0000:04:08.0/0000:0b:00.1/irq CPU 5 Modules linked in: smsc47m1 autofs4 hidp rfcomm l2cap bluetooth lockd sunrpc cpufreq_ondemand acpi_cpufreq freq_table ipv6 xfrm_nalgo crypto_api 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 e1000e serio_raw pcspkr sg dm_raid45 dm_message dm_region_hash dm_mem_cache dm_snapshot dm_zero dm_mirror dm_log dm_mod usb_storage qla2xxx scsi_transport_fc shpchp mptsas mptscsih mptbase scsi_transport_sas sd_mod scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd Pid: 5000, comm: modprobe Not tainted 2.6.18-185.el5 #1 RIP: 0010:[<ffffffff885d74de>] [<ffffffff885d74de>] :smsc47m1:smsc47m1_probe+0xd6/0x466 RSP: 0018:ffff81046b0c1d98 EFLAGS: 00010286 RAX: 000000006b0c1f28 RBX: 00000000fffffff4 RCX: 0000000000000000 RDX: ffffffff885e2000 RSI: ffffffff885d7dbb RDI: ffff81046f9d03e0 RBP: ffff81047e237810 R08: 0000000000000a00 R09: 0000000000000000 R10: 0000000000000001 R11: ffffffff885d7408 R12: ffff810473ab0f60 R13: ffff81046f9d03c0 R14: ffffffff8033ab20 R15: 0000000000000000 FS: 00002abf5d18a240(0000) GS:ffff81010fdec540(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b CR2: 00000002e0be74f0 CR3: 000000046c286000 CR4: 00000000000006e0 Process modprobe (pid: 5000, threadinfo ffff81046b0c0000, task ffff810474286820) Stack: 0000000000000292 ffff81010ff96980 ffff81047fa9ec80 0000000000000000 ffff81047e237810 ffffffff885d96e8 0000000000000000 ffffffff8033ab20 0000000000000000 ffffffff801c7f31 0000000000000000 ffffffff801c7f89 Call Trace: [<ffffffff801c7f31>] driver_probe_device+0x52/0xaa [<ffffffff801c7f89>] __device_attach+0x0/0x5 [<ffffffff801c76dc>] bus_for_each_drv+0x40/0x72 [<ffffffff801c7fe0>] device_attach+0x52/0x5f [<ffffffff801c73e3>] bus_attach_device+0x1a/0x35 [<ffffffff801c66a3>] device_add+0x261/0x372 [<ffffffff801c971e>] platform_device_add+0xd8/0x129 [<ffffffff8831f1b4>] :smsc47m1:sm_smsc47m1_init+0x1b4/0x1eb [<ffffffff8009bcb9>] blocking_notifier_call_chain+0x2d/0x36 [<ffffffff800a7b79>] sys_init_module+0xaf/0x1f2 [<ffffffff8005e28d>] tracesys+0xd5/0xe0 Code: 48 8b 04 c5 b0 7b 5d 88 49 89 45 08 e8 3e fb a5 f7 4c 89 ad RIP [<ffffffff885d74de>] :smsc47m1:smsc47m1_probe+0xd6/0x466 RSP <ffff81046b0c1d98> CR2: 00000002e0be74f0 <0>Kernel panic - not syncing: Fatal exception Version-Release number of selected component (if applicable): kernel-2.6.18-185.el5.x86_64 How reproducible: always Steps to Reproduce: modprobe smsc47m1
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
in kernel-2.6.18-190.el5 You can download this test kernel from http://people.redhat.com/jwilson/el5 Please update the appropriate value in the Verified field (cf_verified) to indicate this fix has been successfully verified. Include a comment with verification details.
Verified in RHEL5.5-Server-20100225.nightly (2.6.18-190.el5) that inserting the smsc47m1 module does not make the kernel to panic: # modprobe smsc47m1 # lsmod | grep smsc47m1 smsc47m1 14025 0 hwmon 7365 3 smsc47m1,coretemp,power_meter
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2010-0178.html