[arch-general] [signoff] linux-3.3.1-1
Hi guys, please signoff 3.3 series for both arches. Upstream changes: http://kernelnewbies.org/LinuxChanges Config cleanup: - disabled comedi staging modules - disabled not needed GPIO modules - disabled W1 support - disabled charger and battery modules - disabled snd_soc module - disabled regulator modules - disabled SPI support Fixed Bugs and feature requests: - New default 'ondemand' cpufreq govenor #28778 - added mtd header files #29076 - more I can't remember ;) greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org
On 04/06/2012 06:54 AM, Tobias Powalowski wrote:
Hi guys, please signoff 3.3 series for both arches.
First off thank you arch devs. I am newish to arch (was with fedora/redhat since about RH 3). I am very happy with the arch - huge thank you. On 3.3.1, obviously I can't sign off - but here's some fedeback. I can attest that the OOPS i was seeing with 3.3 (crash on shutdown or sleep - bluetooth) has not yet happened with 3.3.1. I have seen no other problems (encrypted swap / home, 1 laptop w iwlwifi, 3 desktops). It has been very stable - no issues and no worrisome logs on any of the machines I am testing on. Thanks! gene/
Am 06.04.2012 12:54, schrieb Tobias Powalowski:
Hi guys, please signoff 3.3 series for both arches.
Upstream changes: http://kernelnewbies.org/LinuxChanges
Config cleanup: - disabled comedi staging modules - disabled not needed GPIO modules - disabled W1 support - disabled charger and battery modules - disabled snd_soc module - disabled regulator modules - disabled SPI support
Fixed Bugs and feature requests: - New default 'ondemand' cpufreq govenor #28778 - added mtd header files #29076 - more I can't remember ;)
greetings tpowa
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1]. [1] https://bugzilla.kernel.org/show_bug.cgi?id=43038 -- Regards, Richard Schütz
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Am 06.04.2012 12:54, schrieb Tobias Powalowski:
Hi guys, please signoff 3.3 series for both arches.
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready. -jh
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Am 06.04.2012 12:54, schrieb Tobias Powalowski:
Hi guys, please signoff 3.3 series for both arches.
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi. P.S. At first I post message in worng ML, sorry. --- WBR, Vladimir Lomov -- Mix a little foolishness with your serious plans; it's lovely to be silly at the right moment. -- Horace
Am 07.04.2012 12:33, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Am 06.04.2012 12:54, schrieb Tobias Powalowski:
Hi guys, please signoff 3.3 series for both arches.
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi.
And with 3.2.x there were no problems like that for both of you? -- Regards, Richard Schütz
On Sun, 08 Apr 2012 13:48:11 +0200, Richard Schütz wrote:
Am 07.04.2012 12:33, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Am 06.04.2012 12:54, schrieb Tobias Powalowski:
Hi guys, please signoff 3.3 series for both arches.
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi.
And with 3.2.x there were no problems like that for both of you?
Correct. The "won't resume on 3.3.x" eeepc is suspending / resuming happily with 3.2.13-1-ARCH (downgraded a couple of days ago). As it's the wife's machine, I dare not touch it now it's working again. I'm somewhat baffled by the whole thing; there is nothing obvious in any logs, but X fails to come back from sleep. -jh
Hello, ** Jonathan Hudson [2012-04-08 12:53:42 +0100]:
On Sun, 08 Apr 2012 13:48:11 +0200, Richard Schütz wrote:
Am 07.04.2012 12:33, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi.
And with 3.2.x there were no problems like that for both of you?
Correct. The "won't resume on 3.3.x" eeepc is suspending / resuming happily with 3.2.13-1-ARCH (downgraded a couple of days ago). As it's the wife's machine, I dare not touch it now it's working again.
I'm somewhat baffled by the whole thing; there is nothing obvious in any logs, but X fails to come back from sleep.
Do you mean "suspend to RAM" or "suspend to DISK"? I tried before "suspend to DISK": 3.3.1 and 3.3.0 works fine. P.S. I use advice found on wiki and systemd. --- WBR, Vladimir Lomov -- People will accept your ideas much more readily if you tell them that Benjamin Franklin said it first.
On Sun, 8 Apr 2012 21:20:35 +0900, Vladimir Lomov wrote:
Hello, ** Jonathan Hudson [2012-04-08 12:53:42 +0100]:
On Sun, 08 Apr 2012 13:48:11 +0200, Richard Schütz wrote:
Am 07.04.2012 12:33, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi.
And with 3.2.x there were no problems like that for both of you?
Correct. The "won't resume on 3.3.x" eeepc is suspending / resuming happily with 3.2.13-1-ARCH (downgraded a couple of days ago). As it's the wife's machine, I dare not touch it now it's working again.
I'm somewhat baffled by the whole thing; there is nothing obvious in any logs, but X fails to come back from sleep.
Do you mean "suspend to RAM" or "suspend to DISK"? I tried before "suspend to DISK": 3.3.1 and 3.3.0 works fine.
P.S. I use advice found on wiki and systemd.
--- WBR, Vladimir Lomov
Suspend to RAM. -jh
Am 08.04.2012 14:20, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-08 12:53:42 +0100]:
On Sun, 08 Apr 2012 13:48:11 +0200, Richard Schütz wrote:
Am 07.04.2012 12:33, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi.
And with 3.2.x there were no problems like that for both of you?
Correct. The "won't resume on 3.3.x" eeepc is suspending / resuming happily with 3.2.13-1-ARCH (downgraded a couple of days ago). As it's the wife's machine, I dare not touch it now it's working again.
I'm somewhat baffled by the whole thing; there is nothing obvious in any logs, but X fails to come back from sleep.
Do you mean "suspend to RAM" or "suspend to DISK"? I tried before "suspend to DISK": 3.3.1 and 3.3.0 works fine.
I'm talking about suspend to RAM, but it shouldn't make that big difference in my case, because something seems to be wrong with device suspension already. -- Regards, Richard Schütz
On Sun, Apr 8, 2012 at 07:34, Richard Schütz
Am 08.04.2012 14:20, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-08 12:53:42 +0100]:
On Sun, 08 Apr 2012 13:48:11 +0200, Richard Schütz wrote:
Am 07.04.2012 12:33, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
> Since 3.3.0 suspend isn't working on my desktop computer anymore. > Looks > like device suspension fails somewhere. Furthermore 3.3.1 seriously > breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi.
And with 3.2.x there were no problems like that for both of you?
Correct. The "won't resume on 3.3.x" eeepc is suspending / resuming happily with 3.2.13-1-ARCH (downgraded a couple of days ago). As it's the wife's machine, I dare not touch it now it's working again.
I'm somewhat baffled by the whole thing; there is nothing obvious in any logs, but X fails to come back from sleep.
Do you mean "suspend to RAM" or "suspend to DISK"? I tried before "suspend to DISK": 3.3.1 and 3.3.0 works fine.
I'm talking about suspend to RAM, but it shouldn't make that big difference in my case, because something seems to be wrong with device suspension already.
-- Regards, Richard Schütz
I'm probably speaking out of turn here since I don't use a laptop but suspend-to-ram works fine with the power button. If you've already tried this, sorry for the duplication. My system : Linux 3.3-1-1-Arch My boards : Gigabyte GA-MA78GM-S2H North bridge AMD780 South bridge SB700 Gigabyte GA-A75M-D2H Processor AMD A6-3500 Llano 2.1GHz (2.4GHz Max Turbo) Socket FM1 65W Triple-Core Desktop APU (CPU + GPU) with DirectX 11 Graphic AMD Radeon HD 6530D I use the following script that uses upower to do the work. http://linuxtidbits.wordpress.com/2012/02/24/power-management-from-the-comma... Hope this helps. Myra -- Life's fun when your sick and psychotic!
Hello, ** Richard Schütz [2012-04-08 13:48:11 +0200]:
Am 07.04.2012 12:33, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Am 06.04.2012 12:54, schrieb Tobias Powalowski:
Hi guys, please signoff 3.3 series for both arches.
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi.
And with 3.2.x there were no problems like that for both of you?
I didn't notice any problem with wireless on my notebook before kernel 3.3.1 (I use it every evening). Right now I downgraded to kernel 3.3.0 (took necessary files from projects.archlinux.org/... for version 3.3.0 compiled and intalled .tar.xz packages) and wireless works fine. I have access to other notebook with Archlinux and kernel 3.3.1, that notebook provides AP using hostapd (Atheros wireless card), I'll try tomorrow if AP still works (after update to kernel 3.3.1 I didn't test AP). --- WBR, Vladimir Lomov -- Neutrinos are into physicists.
Am 08.04.2012 14:03, schrieb Vladimir Lomov:
Hello, ** Richard Schütz [2012-04-08 13:48:11 +0200]:
Am 07.04.2012 12:33, schrieb Vladimir Lomov:
Hello, ** Jonathan Hudson [2012-04-06 20:00:33 +0100]:
On Fri, 06 Apr 2012 20:41:46 +0200, Richard Schütz wrote:
Am 06.04.2012 12:54, schrieb Tobias Powalowski:
Hi guys, please signoff 3.3 series for both arches.
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks like device suspension fails somewhere. Furthermore 3.3.1 seriously breaks ath9k on my netbook [1].
I have a similar reservation. On two eeepc 901, suspend works just fine. Alas, only only on one of them does resume work with a 3.3 kernel. I'm not convinced that 3.3 is ready.
Same here: Archlinux x86_64, testing, kernel 3.1.1-1 HW: HP Pavilion dv3 (2210er) with nvidia g104m graphics card, atheros wi-fi.
And with 3.2.x there were no problems like that for both of you?
I didn't notice any problem with wireless on my notebook before kernel 3.3.1 (I use it every evening). Right now I downgraded to kernel 3.3.0 (took necessary files from projects.archlinux.org/... for version 3.3.0 compiled and intalled .tar.xz packages) and wireless works fine.
I have access to other notebook with Archlinux and kernel 3.3.1, that notebook provides AP using hostapd (Atheros wireless card), I'll try tomorrow if AP still works (after update to kernel 3.3.1 I didn't test AP).
Ah, you're talking about the wireless problems. I thought you meant the suspend problems with „Same here“. Yeah, ath9k is definitely broken. -- Regards, Richard Schütz
On 04/06/2012 02:41 PM, Richard Schütz wrote:
Am 06.04.2012 12:54, schrieb Tobias Powalowski:
Hi guys, please signoff 3.3 series for both arches.
Upstream changes: http://kernelnewbies.org/LinuxChanges ...
Since 3.3.0 suspend isn't working on my desktop computer anymore. Looks
This may be of interest on suspend/resume for some - I suspend to ram and resume with no problems at all on my lenovo intel based laptop. Glancing at the changelog seems like the patch is not a part of 3.3.1 https://lkml.org/lkml/2012/4/7/33 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=e72a... gene/
hello, well this is a bit off-topic. But linux-ck switched already to 3.3 kernel and I just discovered that ndiswrapper does not compile. It seems there is a patch floating around to allow ndiswrapper to compile with a 3.3 kernel But I see no ndiswrapper package in [community-testing] yet ? Could the ndiswrapper package be included in [extra] instead of [community] ? <mylife> What a bad idea to remove my ethernet cable and to have now to rely on a PCI wifi card only supported via ndiswrapper. :-( </mylife> make -C utils make[1] : on entre dans le répertoire « /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/utils » gcc -g -Wall -I../driver -Wl,-O1,--sort-common,--as-needed,-z,relro,--hash-style=gnu -o loadndisdriver loadndisdriver.c make[1] : on quitte le répertoire « /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/utils » make -C driver make[1] : on entre dans le répertoire « /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver » make -C /usr/src/linux-3.3.1-2-ck M=/home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver make[2] : on entre dans le répertoire « /usr/src/linux-3.3.1-2-ck » LD /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/built-in.o MKEXPORT /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/crt_exports.h MKEXPORT /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/hal_exports.h MKEXPORT /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ndis_exports.h MKEXPORT /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ntoskernel_exports.h MKEXPORT /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ntoskernel_io_exports.h MKEXPORT /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/rtl_exports.h MKEXPORT /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/usb_exports.h CC [M] /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/crt.o CC [M] /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/hal.o CC [M] /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/iw_ndis.o CC [M] /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/loader.o CC [M] /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ndis.o /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ndis.c: In function ‘NdisGetCurrentProcessorCounts’: /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ndis.c:2657:296: erreur: ‘struct kernel_stat’ has no member named ‘cpustat’ /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ndis.c:2658:303: erreur: ‘struct kernel_stat’ has no member named ‘cpustat’ /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ndis.c:2659:289: erreur: ‘struct kernel_stat’ has no member named ‘cpustat’ make[3]: *** [/home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver/ndis.o] Erreur 1 make[2]: *** [_module_/home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver] Erreur 2 make[2] : on quitte le répertoire « /usr/src/linux-3.3.1-2-ck » make[1]: *** [modules] Erreur 2 make[1] : on quitte le répertoire « /home/solstice/abs/ndiswrapper/src/ndiswrapper-1.57/driver » make: *** [driver] Erreur 2
participants (7)
-
Genes MailLists
-
Jonathan Hudson
-
Myra Nelson
-
Richard Schütz
-
solsTiCe d'Hiver
-
Tobias Powalowski
-
Vladimir Lomov