Bug 483208 - [atk0110] oops on loading previous lm_sensors configuration (w83627ehf))
Summary: [atk0110] oops on loading previous lm_sensors configuration (w83627ehf))
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-01-30 08:18 UTC by Yanko Kaneti
Modified: 2009-01-30 15:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-01-30 15:27:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
oops log (35.77 KB, text/plain)
2009-01-30 08:18 UTC, Yanko Kaneti
no flags Details

Description Yanko Kaneti 2009-01-30 08:18:29 UTC
Created attachment 330449 [details]
oops log

With the new atk0110 hwmon driver in rawhide , I get the following oops when lm_sensors starts and tries to load its previous configuration.

This particular trace was reproduced by booting in runlevel 1 and modprobing w83627ehf once or twice

Comment 1 Hans de Goede 2009-01-30 09:40:23 UTC
Ah,

What you see is a bug in the w83627ehf, where it does not clean up after itself properly when acpi_check_resource_conflict() tells it to bugger of as the resource is already in use by ACPI.

Easy enough to fix, I'll mail the w83627ehf maintainer about this, so that we get the right / best fix in one go.

In the mean time, the solution is to not load the w83627ehf driver, remove it from /etc/sysconfig/lm_sensors 

Note that once this is fixed the w83627ehf driver still will not load (as loading a native driver for the w83627ehf conflicts with ACPI using it at the same time). but it should no longer oops when you try to load it.

Comment 2 Hans de Goede 2009-01-30 15:27:12 UTC
I've just committed a fix which will be in the next rawhide kernel, closing.


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