All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roman Mamedov <roman@rm.pp.ru>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] ASUS CUSL2: sensors work with 2.6.30,
Date: Mon, 01 Mar 2010 14:46:58 +0000	[thread overview]
Message-ID: <20100301194658.11a37e17@natsu> (raw)
In-Reply-To: <20100301033233.66b4f25f@natsu>


[-- Attachment #1.1: Type: text/plain, Size: 614 bytes --]

On Mon, 1 Mar 2010 15:25:39 +0100
Luca Tettamanti <kronos.it@gmail.com> wrote:

> To revert to the old behaviour you can pass
> "acpi_enforce_resources=lax" on the kernel command line, but I cannot
> guarantee that it's a safe operation.

Thanks, this helped. I wonder if similar situations could be detected and
pointed at during sensors-detect. E.g. failures to load modules because of
resource conflicts, if you see my earlier sensors-detect log, it is
completely silent about being unable to insert the module because of the
conflict (which is reported in dmesg only).

-- 
With respect,
Roman

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

[-- Attachment #2: Type: text/plain, Size: 153 bytes --]

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  parent reply	other threads:[~2010-03-01 14:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-28 22:32 [lm-sensors] ASUS CUSL2: sensors work with 2.6.30, Roman Mamedov
2010-03-01 10:35 ` Jean Delvare
2010-03-01 12:48 ` Roman Mamedov
2010-03-01 12:55 ` Luca Tettamanti
2010-03-01 13:49 ` Roman Mamedov
2010-03-01 14:25 ` Luca Tettamanti
2010-03-01 14:46 ` Roman Mamedov [this message]
2010-03-01 14:53 ` Jean Delvare
2010-03-01 15:33 ` Luca Tettamanti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100301194658.11a37e17@natsu \
    --to=roman@rm.pp.ru \
    --cc=lm-sensors@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.