Bug 557172 - inserting w83627hf kernel module results in panic
Summary: inserting w83627hf kernel module results in panic
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel
Version: 5.5
Hardware: All
OS: Linux
low
high
Target Milestone: rc
: 5.6
Assignee: Dean Nelson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 250561
TreeView+ depends on / blocked
 
Reported: 2010-01-20 16:16 UTC by Jan Tluka
Modified: 2010-03-30 07:41 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-03-30 07:41:36 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2010:0178 0 normal SHIPPED_LIVE Important: Red Hat Enterprise Linux 5.5 kernel security and bug fix update 2010-03-29 12:18:21 UTC

Description Jan Tluka 2010-01-20 16:16:17 UTC
Description of problem:

Reported by Peter Splichal in bug #250561:

I've tested the w83627hf on pogo-cn1100-01.rhts.bos.redhat.com.
That was RHEL5.5-Server-20100117.0 tree, 2.6.18-185.el5 kernel.
http://rhts.redhat.com/cgi-bin/rhts/jobs.cgi?id=117831

Inserting the w83627hf module resulted in kernel panic.

Unable to handle kernel paging request at 000000025a21cb00 RIP: 
 [<ffffffff8851c356>] :w83627hf:w83627hf_probe+0xd0/0x8a6
PGD ebe4d067 PUD 0 
Oops: 0000 [1] SMP 
last sysfs file: /devices/pci0000:00/0000:00:19.3/temp3_input
CPU 1 
Modules linked in: w83627hf hwmon_vid i2c_dev nfs fscache nfs_acl autofs4 hidp
rfcomm l2cap bluetooth lockd sunrpc ipv6 xfrm_nalgo crypto_api dm_multipath
scsi_dh video backlight sbs power_meter i2c_ec dell_wmi wmi button battery
asus_acpi acpi_memhotplug ac lp sg i2c_amd756 ide_cd k8temp e100 i2c_amd8111
floppy parport_pc parport i2c_core k8_edac amd_rng edac_mc hwmon cdrom
serio_raw mii pcspkr dm_raid45 dm_message dm_region_hash dm_mem_cache
dm_snapshot dm_zero dm_mirror dm_log dm_mod shpchp sata_sil libata sd_mod
scsi_mod ext3 jbd uhci_hcd ohci_hcd ehci_hcd
Pid: 13576, comm: modprobe Not tainted 2.6.18-185.el5 #1
RIP: 0010:[<ffffffff8851c356>]  [<ffffffff8851c356>]
:w83627hf:w83627hf_probe+0xd0/0x8a6
RSP: 0000:ffff81005a39fda8  EFLAGS: 00010286
RAX: 000000005a39ff28 RBX: ffff810079211d20 RCX: 0000000000000000
RDX: ffffffff8852a900 RSI: ffffffff8851d3f2 RDI: ffff810075c760d8
RBP: ffff81007fbfd810 R08: 0000000000000295 R09: 0000000000000000
R10: 0000000000000001 R11: ffffffff8851c286 R12: ffff810075c760c0
R13: ffff81007fbfd810 R14: 00000000fffffff4 R15: ffff81007fbfd800
FS:  00002af1e25f8240(0000) GS:ffff8100029ad3c0(0000) knlGS:00000000f7fd46c0
CS:  0010 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 000000025a21cb00 CR3: 00000000ec5b2000 CR4: 00000000000006e0
Process modprobe (pid: 13576, threadinfo ffff81005a39e000, task
ffff810002a3b820)
Stack:  ffff810053131140 0000000000000000 ffff81007fbfd810 ffffffff88520be8
 0000000000000000 ffffffff8033ab20 0000000000000000 ffffffff801c7f31
 0000000000000000 ffffffff801c7f89 ffff81007fbfd810 ffffffff801c76dc
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
 [<ffffffff8822a2b5>] :w83627hf:sensors_w83627hf_init+0x118/0x14f
 [<ffffffff800a7b79>] sys_init_module+0xaf/0x1f2
 [<ffffffff8005e28d>] tracesys+0xd5/0xe0

Code: 48 8b 04 c5 c0 d1 51 88 49 89 44 24 08 e8 c5 ac b1 f7 49 8d 
RIP  [<ffffffff8851c356>] :w83627hf:w83627hf_probe+0xd0/0x8a6
 RSP <ffff81005a39fda8>

CR2: 000000025a21cb00
 <0>Kernel panic - not syncing: Fatal exception</p></div>    

Version-Release number of selected component (if applicable):
RHEL5.5-Server-20100117.0
kernel-2.6.18-185.el5

How reproducible:


Steps to Reproduce:
1. reserve pogo-cn1100-01.rhts.bos.redhat.com system in RHTS
2. modprobe w83627hf / use lm-sensors tool
3.
  
Actual results:
panic 

Expected results:
no panic 

Additional info:
According to test results in 5.3 this worked fine:
https://bugzilla.redhat.com/show_bug.cgi?id=250561#c18

Comment 2 Jan Tluka 2010-01-20 20:47:06 UTC
I've checked kernel from RHEL5-U4 and it has not panicked.

[root@pogolinux-1 ~]# uname -r
2.6.18-164.el5
[root@pogolinux-1 ~]# modprobe w83627hf
[root@pogolinux-1 ~]# lsmod | grep w83627hf
w83627hf               61265  0 
hwmon_vid              35905  1 w83627hf
i2c_isa                39104  1 w83627hf
i2c_core               56129  5 w83627hf,i2c_isa,i2c_ec,i2c_amd8111,i2c_amd756
hwmon                  36553  2 w83627hf,k8temp

Comment 5 RHEL Program Management 2010-02-12 17:28:47 UTC
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.

Comment 7 Jarod Wilson 2010-02-23 20:05:39 UTC
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.

Comment 9 Petr Šplíchal 2010-02-25 16:12:01 UTC
Successfully tested & verified on RHEL5.5-Server-20100225.nightly.
Both inserting the module and sensors functionality are now OK:

drivers: k8temp lm85 w83627hf
sensors: adm1027-i2c-0-2e k8temp-pci-00c3 k8temp-pci-00cb w83627hf-isa-0290
hostname: pogo-cn1100-01.rhts.eng.bos.redhat.com
lm_sensors: lm_sensors-2.10.7-9.el5
kernel: 2.6.18-190.el5

Sensor details
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
...

w83627hf-isa-0290
Adapter: ISA adapter
VCore 1:   +1.38 V  (min =  +1.44 V, max =  +1.86 V)       ALARM  
VCore 2:   +1.39 V  (min =  +1.44 V, max =  +1.86 V)       ALARM  
+3.3V:     +3.41 V  (min =  +2.82 V, max =  +3.79 V)              
+5V:       +5.13 V  (min =  +5.46 V, max =  +1.45 V)       ALARM  
+12V:      +4.92 V  (min = +11.73 V, max = +15.50 V)       ALARM  
-12V:      -1.42 V  (min =  +5.16 V, max =  -3.89 V)       ALARM  
-5V:       -3.64 V  (min =  -4.85 V, max =  -1.28 V)              
V5SB:      +5.70 V  (min =  +0.67 V, max =  +4.78 V)       ALARM  
VBat:      +3.38 V  (min =  +3.20 V, max =  +2.05 V)       ALARM  
fan1:        0 RPM  (min = 1250 RPM, div = 8)              ALARM  
fan2:        0 RPM  (min =  669 RPM, div = 8)              ALARM  
fan3:        0 RPM  (min =  709 RPM, div = 8)              ALARM  
temp1:       +35°C  (high =  +101°C, hyst =    -4°C)   sensor = thermistor          
temp2:     +35.0°C  (high =   +80°C, hyst =   +75°C)   sensor = thermistor          
temp3:     +39.5°C  (high =   +80°C, hyst =   +75°C)   sensor = thermistor          
vid:      +1.350 V  (VRM Version 2.4)
alarms:  
beep_enable:
          Sound alarm enabled


# lsmod | grep w83627hf
w83627hf               27481  0 
hwmon_vid               6849  2 w83627hf,lm85
hwmon                   7365  4 w83627hf,lm85,power_meter,k8temp

Comment 13 errata-xmlrpc 2010-03-30 07:41:36 UTC
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


Note You need to log in before you can comment on or make changes to this bug.