EC reports that Thermal Table has changed

Hi,

I get the following message when I plug/unplug the AC-Adapter:

Oct  8 03:44:48 kiwi kernel: [  450.000018] thinkpad_acpi: EC reports 
that Thermal Table has changed

Can I ignore it or is there something wrong?

Thanks,

PJ

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference

Re: EC reports that Thermal Table has changed

On Thu, 08 Oct 2009, Peter Jordan wrote:
> I get the following message when I plug/unplug the AC-Adapter:
> 
> Oct  8 03:44:48 kiwi kernel: [  450.000018] thinkpad_acpi: EC reports 
> that Thermal Table has changed
> 
> Can I ignore it or is there something wrong?

You can ignore it.

--

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference

bluetooth off state not remembered accross reboots?

Hey,

since some time (I guess 2.6.29 or 2.6.30 kernel), it seems that the
bluetooth “off” state isn't remembered on my T61. I usually turn
bluetooth off (using Fn+F5 with rfkill-input loaded and hal configured
to send “blueooth” event on that keypress), but when I reboot, it's
turned back on.

I don't reboot often, but I remember at one point it was implemented and
working, so I wonder if something is broken here.

What do you think?

Cheers,
--

-- 
Yves-Alexis

------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay 
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference

_______________________________________________
ibm-acpi-devel mailing list
ibm-acpi-devel@...
https://lists.sourceforge.net/lists/listinfo/ibm-acpi-devel

Re: bluetooth off state not remembered accross reboots?

On Sat, 10 Oct 2009, Yves-Alexis Perez wrote:
> since some time (I guess 2.6.29 or 2.6.30 kernel), it seems that the
> bluetooth ???off??? state isn't remembered on my T61. I usually turn

The driver can remember state, yes. It *might* not work though. And it can
be overriden by userspace.

Do note that when thinkpad-acpi switches bluetoot off, it *disappears* from
the bus (so, lsusb won't find it, etc).

If bluetooth is still present in the bus, but the bluetooth interface is
down, then your problem is not related directly or indirectly to
thinkpad-acpi.

Now, if the bluetooth state persistence used to work on your thinkpad and it
doesn't work anymore, then the problem is likely in userspace.

> I don't reboot often, but I remember at one point it was implemented and
> working, so I wonder if something is broken here.

Well, it *is* possible.  But it is more likely that something is turning it
on by force at boot.

> What do you think?

Compile thinkpad-acpi with the Kconfig option "CONFIG_THINKPAD_ACPI_DEBUG"
enabled, and pass thinkpad-acpi the module option "debug=0x8004", either
through the kernel command line (if it is builtin:
thinkpad_acpi.debug=0x8004) or through an "options thinkpad-acpi ..." line
in /etc/modprobe.d/*.

Re: bluetooth off state not remembered accross reboots?

On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 10 Oct 2009, Yves-Alexis Perez wrote:
> > since some time (I guess 2.6.29 or 2.6.30 kernel), it seems that the
> > bluetooth ???off??? state isn't remembered on my T61. I usually turn
> 
> The driver can remember state, yes. It *might* not work though. And it can
> be overriden by userspace.
> 
> Do note that when thinkpad-acpi switches bluetoot off, it *disappears* from
> the bus (so, lsusb won't find it, etc).
> 
> If bluetooth is still present in the bus, but the bluetooth interface is
> down, then your problem is not related directly or indirectly to
> thinkpad-acpi.

In fact, I check with the bluetooth LED state.
> 
> Now, if the bluetooth state persistence used to work on your thinkpad and it
> doesn't work anymore, then the problem is likely in userspace.

In fact, I watched the LED accross the boot, and it lights on when the
following is displayed:

[   19.441103] Bluetooth: Core ver 2.15
[   19.451982] Bluetooth: HCI device and connection manager initialized
[   19.456402] Bluetooth: HCI socket layer initialized
[   19.497216] Bluetooth: Generic Bluetooth USB driver ver 0.5

So I guess thinkpad-acpi correctly tries to keep bluetooth off, but the
bluetooth module re-enables it for some reason.

Re: bluetooth off state not remembered accross reboots?

On Sat, 10 Oct 2009, Yves-Alexis Perez wrote:
> On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> > Do note that when thinkpad-acpi switches bluetoot off, it *disappears* from
> > the bus (so, lsusb won't find it, etc).

It appears I was not clear enough... when thinkpad-acpi disables bluetooth,
for all intents and purposes, your computer *ceases to have bluetooth
hardware* as far as the rest of the Linux kernel knows.

So, the bluetooth core is not able to "reenable" bluetooth.

> > If bluetooth is still present in the bus, but the bluetooth interface is
> > down, then your problem is not related directly or indirectly to
> > thinkpad-acpi.
> 
> In fact, I check with the bluetooth LED state.

Do it with lsusb (run it as root), instead.

> > Now, if the bluetooth state persistence used to work on your thinkpad and it
> > doesn't work anymore, then the problem is likely in userspace.
> 
> In fact, I watched the LED accross the boot, and it lights on when the
> following is displayed:
> 
> [   19.441103] Bluetooth: Core ver 2.15
> [   19.451982] Bluetooth: HCI device and connection manager initialized
> [   19.456402] Bluetooth: HCI socket layer initialized
> [   19.497216] Bluetooth: Generic Bluetooth USB driver ver 0.5

Re: bluetooth off state not remembered accross reboots?

On dim, 2009-10-11 at 09:39 -0300, Henrique de Moraes Holschuh wrote:
> On Sat, 10 Oct 2009, Yves-Alexis Perez wrote:
> > On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> > > Do note that when thinkpad-acpi switches bluetoot off, it *disappears* from
> > > the bus (so, lsusb won't find it, etc).
> 
> It appears I was not clear enough... when thinkpad-acpi disables bluetooth,
> for all intents and purposes, your computer *ceases to have bluetooth
> hardware* as far as the rest of the Linux kernel knows.
> 
> So, the bluetooth core is not able to "reenable" bluetooth.

HMh, ok.
> 
> > > If bluetooth is still present in the bus, but the bluetooth interface is
> > > down, then your problem is not related directly or indirectly to
> > > thinkpad-acpi.
> > 
> > In fact, I check with the bluetooth LED state.
> 
> Do it with lsusb (run it as root), instead.

Attached are both lsusb with on and off.
> 
> > > Now, if the bluetooth state persistence used to work on your thinkpad and it
> > > doesn't work anymore, then the problem is likely in userspace.
> > 
> > In fact, I watched the LED accross the boot, and it lights on when the
> > following is displayed:
> > 

Re: bluetooth off state not remembered accross reboots?

On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> > What do you think?
> 
> Compile thinkpad-acpi with the Kconfig option "CONFIG_THINKPAD_ACPI_DEBUG"
> enabled, and pass thinkpad-acpi the module option "debug=0x8004", either
> through the kernel command line (if it is builtin:
> thinkpad_acpi.debug=0x8004) or through an "options thinkpad-acpi ..." line
> in /etc/modprobe.d/*.
> 
> Make sure you're logging kernel debug messages somewhere (check
> rsyslog/klogd/syslogd/whatever configuration).
> 
> After that, do some testing and check the kernel log, thinkpad-acpi will
> tell you if something tries to manipulate radio state, and it will also tell
> you when it stores radio state to NVRAM.  It should give us some idea of
> what's happening.

When booting with debug-0x8004 I can see:

[   16.036499] thinkpad_acpi: bluetooth_init: initializing bluetooth subdriver
[   16.037608] thinkpad_acpi: bluetooth_init: bluetooth is supported, status 0x01
[   16.039494] PM: Adding info for No Bus:rfkill0
[   16.039930] thinkpad_acpi: tpacpi_rfk_hook_set_block: request to change radio state to blocked
[   16.039939] thinkpad_acpi: bluetooth_set_status: will attempt to disable bluetooth

and then:

[   16.055929] thinkpad_acpi: tpacpi_rfk_hook_set_block: request to change radio state to unblocked
[   16.055938] thinkpad_acpi: bluetooth_set_status: will attempt to enable bluetooth

Re: bluetooth off state not remembered accross reboots?

On dim, 2009-10-11 at 15:03 +0200, Yves-Alexis Perez wrote:
> On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> > > What do you think?
> > 
> > Compile thinkpad-acpi with the Kconfig option "CONFIG_THINKPAD_ACPI_DEBUG"
> > enabled, and pass thinkpad-acpi the module option "debug=0x8004", either
> > through the kernel command line (if it is builtin:
> > thinkpad_acpi.debug=0x8004) or through an "options thinkpad-acpi ..." line
> > in /etc/modprobe.d/*.
> > 
> > Make sure you're logging kernel debug messages somewhere (check
> > rsyslog/klogd/syslogd/whatever configuration).
> > 
> > After that, do some testing and check the kernel log, thinkpad-acpi will
> > tell you if something tries to manipulate radio state, and it will also tell
> > you when it stores radio state to NVRAM.  It should give us some idea of
> > what's happening.
> 
Ok, I played a bit more.

This is from THinkpad, booted. Bluetooth is on, LED is on, appears in
lsusb.

sudo modprobe thinkpad-acpi debug=0x8004

Oct 11 16:02:52 hidalgo kernel: [ 3915.851563] PM: Adding info for No Bus:nvram
Oct 11 16:02:52 hidalgo kernel: [ 3915.851616] Non-volatile memory driver v1.3
Oct 11 16:02:52 hidalgo kernel: [ 3915.855681] PM: Adding info for platform:thinkpad_acpi
Oct 11 16:02:52 hidalgo kernel: [ 3915.857154] PM: Adding info for platform:thinkpad_hwmon
Oct 11 16:02:52 hidalgo kernel: [ 3915.857258] PM: Adding info for No Bus:hwmon1

Re: bluetooth off state not remembered accross reboots?

On Sun, 11 Oct 2009, Yves-Alexis Perez wrote:
> On sam, 2009-10-10 at 13:49 -0300, Henrique de Moraes Holschuh wrote:
> > Compile thinkpad-acpi with the Kconfig option "CONFIG_THINKPAD_ACPI_DEBUG"
> > enabled, and pass thinkpad-acpi the module option "debug=0x8004", either
> > through the kernel command line (if it is builtin:
> > thinkpad_acpi.debug=0x8004) or through an "options thinkpad-acpi ..." line
> > in /etc/modprobe.d/*.
> > 
> > Make sure you're logging kernel debug messages somewhere (check
> > rsyslog/klogd/syslogd/whatever configuration).
> > 
> > After that, do some testing and check the kernel log, thinkpad-acpi will
> > tell you if something tries to manipulate radio state, and it will also tell
> > you when it stores radio state to NVRAM.  It should give us some idea of
> > what's happening.
> 
> When booting with debug-0x8004 I can see:
> 
> [   16.036499] thinkpad_acpi: bluetooth_init: initializing bluetooth subdriver
> [   16.037608] thinkpad_acpi: bluetooth_init: bluetooth is supported, status 0x01
> [   16.039494] PM: Adding info for No Bus:rfkill0
> [   16.039930] thinkpad_acpi: tpacpi_rfk_hook_set_block: request to change radio state to blocked
> [   16.039939] thinkpad_acpi: bluetooth_set_status: will attempt to disable bluetooth
> 
> and then:
> 
> [   16.055929] thinkpad_acpi: tpacpi_rfk_hook_set_block: request to change radio state to unblocked
> [   16.055938] thinkpad_acpi: bluetooth_set_status: will attempt to enable bluetooth

Ok.  This means something is asking thinkpad-acpi to enable bluetooth at