On 18/03/11 15:06, Madhurya Kakati wrote:

On Thu, Mar 17, 2011 at 3:31 AM, Richard Schütz wrote:

...

Am 16.03.2011 20:27, schrieb Tobias Powalowski:

...

Hi guys, please signoff 2.6.38 series for both arches.

Upstream changes: http://kernelnewbies.org/LinuxChanges

Features included: - kernel image is now xz compressed - NUMA is enabled on x86_64 - AUTOSCHED (aka the wonder patch) is enabled - aufs2.1 latest snapshot

greetings tpowa

No signoff. There are graphic glitches on my netbook that have not been there in latest 2.6.37. I found an upstream bug report which seems to deal exactly with my problem: https://bugzilla.kernel.org/show_bug.cgi?id=27572

-- Regards, Richard Schütz

Sorry off-topic. I have kernel version 2.6.37-ARCH. Do i have the wonder patch?

No.

On Sat, Mar 19, 2011 at 12:57 AM, Jeff Cook wrote:

...

Hi guys, please signoff 2.6.38 series for both arches.

Having issues here with ath9k, much slower than it was with 2.6.37. Found this bug re: Ubuntu on Launchpad, haven't checked the kernel tracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/735171

Looks like I'm also getting bit by this on another machine that uses ath5k. Watching wireshark on two machines, almost all packets sent to the ath5k card never make it with 2.6.38. I also tested with a compat-wireless tarball from 2011-03-18 with the same results. Reverting to 2.6.37 makes the issue go away. Definitely seems like an unsafe upgrade at least for Atheros users.

On Sat, Mar 19, 2011 at 7:21 AM, Richard Schütz wrote:

...

On Sat, Mar 19, 2011 at 12:57 AM, Jeff Cook  wrote:

...

Having issues here with ath9k, much slower than it was with 2.6.37. Found this bug re: Ubuntu on Launchpad, haven't checked the kernel tracker: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/735171

Looks like I'm also getting bit by this on another machine that uses ath5k. Watching wireshark on two machines, almost all packets sent to the ath5k card never make it with 2.6.38. I also tested with a compat-wireless tarball from 2011-03-18 with the same results. Reverting to 2.6.37 makes the issue go away. Definitely seems like an unsafe upgrade at least for Atheros users.

I can confirm that. When running 2.6.38 my downstream with ath9k is about 13 times slower compared to 2.6.37.4.

-- Regards, Richard Schütz

What kind of network are you using? A person in IRC suggested that these issues might only exist on certain (relatively rare) networks, like 802.11n or ad-hoc. I bisected and wound up with 8aec7af99b1e45 as the culprit, though that doesn't make much sense as that change was merged into 2.6.37. Here is my git bisect log: git bisect start '--' 'drivers/net/wireless/' # bad: [7d2c16befae67b901e6750b845661c1fdffd19f1] ath9k: fix aggregation related interoperability issues git bisect bad 7d2c16befae67b901e6750b845661c1fdffd19f1 # good: [3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5] Linux 2.6.37 git bisect good 3c0eee3fe6a3a1c745379547c7e7c904aa64f6d5 # bad: [bfe3850b0cfca6ba64395e2705d9a51cd044f374] rndis_wlan: scanning, workaround device returning incorrect bssid-list item count. git bisect bad bfe3850b0cfca6ba64395e2705d9a51cd044f374 # good: [f7ec8fb4d6f8f3ecb8b11e9e46ece95aa66139cc] ath9k_hw: Fix eeprom offset for AR9287 devices (PCI/USB) git bisect good f7ec8fb4d6f8f3ecb8b11e9e46ece95aa66139cc # bad: [692d2c0fb36c02ad07d54641c26f48e644b27fbd] b43: rename config option for N-PHY, drop BROKEN git bisect bad 692d2c0fb36c02ad07d54641c26f48e644b27fbd # bad: [8efa5d7d6ad307ae2d220def37ca89594062c40d] ath5k: Check if pci pdev struct is initialized in common functions. git bisect bad 8efa5d7d6ad307ae2d220def37ca89594062c40d # good: [61cde037234c4b8e6497a23f5f236c64cbf9d41d] ath5k: Extend rate_duration git bisect good 61cde037234c4b8e6497a23f5f236c64cbf9d41d # bad: [61790c5f3c5f158821821a00797d94504531839f] iwlagn: fix microcode error on 4965 git bisect bad 61790c5f3c5f158821821a00797d94504531839f # bad: [8aec7af99b1e4594c4bb9e1c48005e6111f97e8e] ath5k: Support synth-only channel change for AR2413/AR5413 git bisect bad 8aec7af99b1e4594c4bb9e1c48005e6111f97e8e # good: [b2b4c69f682a2868411899a77842061dd745884f] ath5k: Tweak power detector delays on RF5111/RF5112 git bisect good b2b4c69f682a2868411899a77842061dd745884f # good: [f08fbf6cf4a31c8df52b21440c7a7e6fbe474b28] ath5k: Update PLL programming for turbo/half/quarter git bisect good f08fbf6cf4a31c8df52b21440c7a7e6fbe474b28 # good: [4c57581d939fd0f8f244b9730812069f4dac308a] ath5k: Skip powertable setting when we are on the same channel git bisect good 4c57581d939fd0f8f244b9730812069f4dac308a I may have done something wrong, I guess. I was testing with compat-wireless and not applying patches uniformly really, so they may have mucked things up, but I was getting some success with commits from Nov. 23, 2010 as well as some failures. I will try bisecting again soon and will probably just end up rebooting and testing each kernel individually that way, which is a seriously lame pain in the rear way to test just one driver.

Just as a side note: I'm using 2.6.38 without problems here, with fair realtime performance btw.

Excerpts from Richard Schütz's message from Wed 16-Mar-11 23:01:

Am 16.03.2011 20:27, schrieb Tobias Powalowski:

...

Hi guys, please signoff 2.6.38 series for both arches.

Upstream changes: http://kernelnewbies.org/LinuxChanges

Features included: - kernel image is now xz compressed - NUMA is enabled on x86_64 - AUTOSCHED (aka the wonder patch) is enabled - aufs2.1 latest snapshot

greetings tpowa

No signoff. There are graphic glitches on my netbook that have not been there in latest 2.6.37. I found an upstream bug report which seems to deal exactly with my problem: https://bugzilla.kernel.org/show_bug.cgi?id=27572

That bug causes graphic terminals (namely urxvt) almost unusable in my ThinkPad R61 (with Intel GM965) - any new text becomes visible only after focus change or text selection... Cheers, Sergey

Touchpad scrolling stopped working for me with this kernel, for some odd reason.

On Monday 21 of March 2011 22:09:22 Erik Johnson wrote:

Touchpad scrolling stopped working for me with this kernel, for some odd reason. Hi, i had just the same weird issue, for me, going to kde's systemsettings > mouse module fixes that. see https://bugs.archlinux.org/task/23330 cheers, marek

-- Marek Otahal :o)

On Tue, Mar 22, 2011 at 4:49 AM, Marek Otahal wrote:

On Monday 21 of March 2011 22:21:44 you wrote:

...

On Monday 21 of March 2011 22:09:22 Erik Johnson wrote:

...

Touchpad scrolling stopped working for me with this kernel, for some odd reason.

Hi, i had just the same weird issue, for me, going to kde's systemsettings > mouse module fixes that. see https://bugs.archlinux.org/task/23330 cheers, marek sorry, my mistake.  so i can confirm that kernel 2.6.38 breaks the sidebar scrolling on synaptics touchpad.

that's because there's some new multitouch code that has been merged, you should be able to scroll with two fingers anywhere on the touchpad now, this became the default behaviour. To get back the old style, just add: Option "VertEdgeScroll" "true" to /etc/X11/xorg.conf.d/50-synaptics.conf (or whatever it is called on your machine)

On Tue, Mar 22, 2011 at 7:35 AM, Arthur Titeica wrote:

On Tue, 22 Mar 2011 07:24:26 +0700, Emmanuel Benisty wrote:

...

On Tue, Mar 22, 2011 at 4:49 AM, Marek Otahal wrote:

...

On Monday 21 of March 2011 22:21:44 you wrote:

...

On Monday 21 of March 2011 22:09:22 Erik Johnson wrote:

...

Touchpad scrolling stopped working for me with this kernel, for some odd reason.

Hi, i had just the same weird issue, for me, going to kde's systemsettings > mouse module fixes that. see https://bugs.archlinux.org/task/23330 cheers, marek

sorry, my mistake.  so i can confirm that kernel 2.6.38 breaks the sidebar scrolling on synaptics touchpad.

that's because there's some new multitouch code that has been merged, you should be able to scroll with two fingers anywhere on the touchpad now, this became the default behaviour. To get back the old style, just add: Option "VertEdgeScroll" "true" to /etc/X11/xorg.conf.d/50-synaptics.conf (or whatever it is called on your machine)

I'm just curious. Where did you get this info from and how could a normal user know these things when they break? Maybe it's in a wiki somewhere or there's a arch kernel changelog?

I was hit by this "bug" during -rc phase, I just exchanged some few emails with the kernel input maintainer (Dmitry Torokhov) who kindly helped me to solve that.

On 03/22/2011 01:35 AM, Arthur Titeica wrote:

...

On Tue, 22 Mar 2011 07:24:26 +0700, Emmanuel Benisty wrote:

...

On Tue, Mar 22, 2011 at 4:49 AM, Marek Otahal

wrote:

...

On Monday 21 of March 2011 22:21:44 you wrote:

...

On Monday 21 of March 2011 22:09:22 Erik Johnson wrote:

...

Touchpad scrolling stopped working for me with this kernel, for

some odd

...

reason.

Hi, i had just the same weird issue, for me, going to kde's systemsettings > mouse module fixes

...

...

...

...

see https://bugs.archlinux.org/task/23330 cheers, marek

sorry, my mistake. so i can confirm that kernel 2.6.38 breaks

On Tuesday 22 March 2011 02:50:42 Sven-Hendrik Haase wrote: that. the

...

...

...

sidebar scrolling on synaptics touchpad.

that's because there's some new multitouch code that has been merged, you should be able to scroll with two fingers anywhere on the touchpad now, this became the default behaviour. To get back the old style, just add: Option "VertEdgeScroll" "true" to /etc/X11/xorg.conf.d/50-synaptics.conf (or whatever it is called on your machine)

I'm just curious. Where did you get this info from and how could a normal user know these things when they break? Maybe it's in a wiki somewhere or there's a arch kernel changelog?

As for myself I spent one day looking for a solution and found it in ksynaptics (in AUR - this should really get in official repos ;) ).

"man synaptics" gives you all the options.

Will have to look into it someday. Maybe there's something about dragging locks.

Also, there is no ksynaptics.

Sorry about that. It's kcm_touchpad. -- Arthur Titeica PharmEc Software

On Tue, Mar 22, 2011 at 10:44 AM, Erik Johnson wrote:

On Mon, Mar 21, 2011 at 7:24 PM, Emmanuel Benisty wrote:

...

that's because there's some new multitouch code that has been merged, you should be able to scroll with two fingers anywhere on the touchpad now, this became the default behaviour. To get back the old style, just add: Option "VertEdgeScroll" "true" to /etc/X11/xorg.conf.d/50-synaptics.conf (or whatever it is called on your machine)

Weirdly, this wasn't the case on my desktop (x86_64 kernel w/nvidia driver). The edge scrolling works fine there, and it isn't explicitly turned on. On my netbook (i686 w/intel video driver) is where it doesn't work. I'll check the X configuration there when I get a chance, but I'm guessing this will probably be the case.

I guess it's because your other touchpad does not have the same capabilities.