Yeah, I reckon these errors are safe to ignore. My point is: they are
misleading and can led to bug reports like this one :)
That's why they either shouldn't be displayed as an error in the dmesg
output (change these to warnings maybe?) or make these PM scripts
smarter by checking module options.
On Sat, Nov 22, 2014 at 01:41:55AM -, Michael Heuberger wrote:
> Ok, understood. Well, I spotted the error in my dmesg output. There was
> something else trying to turn the powersave off which failed of course
> and an error was printed. That confused me.
>
> If I have power support disabled,
Ok, understood. Well, I spotted the error in my dmesg output. There was
something else trying to turn the powersave off which failed of course
and an error was printed. That confused me.
If I have power support disabled, then no entity should try to switch
powersave off. This to prevent error poll
I stated it backwards in comment #6 - if ps_enable is 0 then the
operation should fail, and if it's 1 it should work. Since you're
reading it as 0 (which is the default) that means power save support is
disabled and the operation is going to fail. iw probably just doesn't
output an error message in
Thanks.
```
$ sudo iw wlan0 set power_save off
```
seemed to work without any errors.
```
$ cat /sys/module/ath9k/parameters/ps_enable
0
```
Yes it returned a zero.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a me
Here's a couple of possibilities.
First of all, iwconfig uses wireless extensions, which is deprecated but
supported through emulation. I'm honestly not sure whether changing the
power save option is expected to work that way. Try using 'sudo iw wlan0
get power_save" for reading the power save sta
Oops, I've got a typo in comment #6. The command to change the power
save state should be 'sudo iw wlan0 set power_save ", not
"powersave".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394163
Title:
Yes, power management is off on my side.
In that case it should NOT print an error. Just a warning. Because an
error is misleading.
PS: Sorry, do not want to try the latest kernel. Had too many bad
experiences installing beta kernels in the past.
** Tags added: kernel-unable-to-test-upstream
**
Michael Heuberger, as per your Bug Description your Power Management is
off. Hence, was it already off when you ran the command, or was it on,
you ran the command, and then it was turned off?
I also get the same message as per the Bug Description if the Power
Management is already off when I attem
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v3.18 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix t
10 matches
Mail list logo
