/srv/irclogs.ubuntu.com/2012/04/02/#ubuntu-kernel.txt

=== kengyu__ is now known as kengyu
=== smb` is now known as smb
* ppisati -> reboot08:30
vaneetHi everyone.08:54
vaneetI know a bit of linux and i am not an expert.08:55
vaneetI have installed 11.10 ubuntu from CD08:55
vaneetmany times during the day, it crashes 08:55
vaneeti read yesterday that desktop GUI issues are normally kernel issues.08:55
vaneetcan someone help please.08:55
vaneetthank you in advance08:55
=== himcesjf1 is now known as himcesjf
vaneetanyone there09:03
=== htorque__ is now known as htorque
vaneethi09:22
didrockshey apw! I normally get a kernel panic every 2 days (my disk is really slow and I'm under the impression that I trigger it when I do a lot of ios). This morning, I got 3 of them :( what should I provide to help your team debugging?09:28
apwdidrocks, do you get a stack trace from the crash, thats the most useful part09:56
didrocksapw: never got a crash in /var/crash/ related to the kernel from what I can see09:56
apwdidrocks, so whats the symptoms when it 'crashes'09:57
didrocksapw: the disk is spinning a lot due to a lot of io, then screen freezes and I see both caps lock and scroll lock flashing which is what tells there is a kernel panic, isn't it?09:58
apwdidrocks, yes usually flashing those is its last ditch attempt to tell you ... from their its worth doing the sysrq sync  as if syslog got the crash it may not hit the disk until you sync09:59
didrocksapw: ok, will do the sysrq sync at my next (hopefully not too soon though ;)) crash10:00
didrocksapw: will keep you posted10:00
apwdidrocks, which kernel is this running, assuming precise latest?  so do get a bug filed so we can track which versions it definatly occurs in10:00
apwdidrocks, i don't think i've seen any hard crashers this cycle on any of my kit thankfully, they are very hard to locate10:01
didrocksapw: yeah, I got that for 2/3 weeks already, always updated to latest (and updated to latest again this morning)10:01
didrocksapw: yeah, I really think I trigger it a lot as my HD is near EOL10:01
didrocksso all my laptop is very slow due to this, so easier for me to trigger weird cases10:01
apwdidrocks, i asume its not old enough to have a serial port10:02
apwwhy oh why did they take those off10:02
didrocksapw: no, I would have played with minicom otherwise ;)10:03
apwdidrocks, sometimes a netconsole will get the crash, sometimes10:04
didrocksinteresting, not used to do that though ;) for most of my stack, it's either on a terminal or a tty if it's the window manager. Quite easier ;)10:04
apwdidrocks, fingers crossed the sync will get it10:09
didrocksapw: I hope so as well. Will keep you in touch, thanks!10:09
apwand let us know the bug number so we can get it to jo10:10
apwjoe10:10
* ppisati -> back in a bit10:18
* ppisati -> lunch11:08
ckingditto11:14
ppisati*burp*11:33
ckingsatisfying lunch then ppisati?11:35
ppisatiwell, good enough, thanks for asking :)11:42
smbppisati, Wanna mint? :)12:02
ppisatismb: the meaning of life? :)12:13
smb`ppisati, yep12:13
smb`:)12:13
=== smb` is now known as smb
apwb smb12:37
smbb happy12:37
TeduardoAnyone have any clue when 12.04 will be happily thrust upon us?13:08
smbWhen it is released...? ;) https://wiki.ubuntu.com/13:10
=== bladernr_afk is now known as bladernr_
=== bladernr_ is now known as bladernr_afk
=== bladernr_afk is now known as bladernr_
Kanohi, please add http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=commit;h=c9651e70ad0aa499814817cbf3cc1d0b806ed3a114:01
Kanoif not already done14:01
ppisatiapw: https://wiki.ubuntu.com/KernelTeam/Specs/PreciseKernelConfigReviewBeta2omap4 is it periodically autogenerated or you intervene manually?14:07
apwppisati, totally manual, need it updating ?14:08
ppisatiapw: not yet14:09
apwKano, that is already applied and uploaded, iirc we were in the loop in getting that fix identified14:10
Kanofine14:11
Kanoi bisected it again ;)14:11
Kanothen i saw that there was already a fix14:11
* ogasawara back in 2014:42
ppisatiapw: when there's a dash it means it's not available there, right?14:45
apwppisati, yes right15:00
=== yofel_ is now known as yofel
tgardnercking, do you have a regression test for bug #885744 ? It needs Oneiric verification.15:19
ubot2Launchpad bug 885744 in ecryptfs "pathconf() does not reflect reality" [High,In progress] https://launchpad.net/bugs/88574415:19
ogasawaratgardner: I'm gonna rebase q to 3.4-rc1, just wanted to make sure you're not already doing so15:19
ckingtgardner, yep, I'm in the process of verifying these15:19
tgardnerogasawara, nope, still grinding through my email backlog. thats what I get for taking the weekend off.15:19
tgardnercking, thanks15:20
tgardnercking, which reminds me, I should compare 2.6.32.y against our ecryptfs patches and send the deltas to stable15:21
jwiapw: otoh, the aspm fix hasn't been applied to oneiric-proposed yet...15:33
* ppisati kicks another build and disappears for a bit in the mean tim15:43
ppisatie15:43
tgardnerjwi, just emailed it for review at kernel-team@lists.ubuntu.com15:43
=== bladernr_ is now known as bladernr_afk
apwtgardner, do we not need a second fix from cking on that one ^ ?15:48
tgardnerapw, nah, taht was just an override thingy. it wouldn't hurt, but its also not related15:48
ckingyep15:49
* apw looks confused15:49
* apw will let you duke it out on the mail thread15:49
tgardnerapw, you're takling about Oneiric "ASPM: Fix pcie devices with non-pcie children", right ?15:50
apwtgardner, indeed15:50
* apw spits feathers at the launcher, get off my damn screen i am using it15:50
tgardnerapw, and I assume to 2nd patch to which refer is "UBUNTU: SAUCE: PCI: Allow pcie_aspm=force to work even when FADT indicates it is unsupported"15:51
apwcking, is that the one i mean, i know there was a followup for it, which was related to regressions induced by the first patch15:52
apwbah it wants to remove all my 32 bit support again ... not a good time to update15:58
apwppisati, did we resolved the issues that pushed us back for beta2 on arm?16:07
=== bladernr_afk is now known as bladernr_
tgardnersforshee, have you noticed suspend/resume issues on your MB Air ?16:36
sforsheetgardner, I filed a bug about some touchpad problems after S3, but that's the only one I've seen recently16:36
tgardnersforshee, yeah, I'm seeing mouse lockage16:37
=== htorque_ is now known as htorque
tgardnersforshee, I didn't notice it until recently 'cause I'd been using an external mouse16:37
sforsheeit just showed up recently16:37
sforsheetgardner, bug 96884516:38
ubot2Launchpad bug 968845 in xserver-xorg-input-synaptics "bcm5974 touchpad doesn't work after S3" [Undecided,Confirmed] https://launchpad.net/bugs/96884516:38
sforsheeif you suspend from the menu things are okay16:38
tgardnersforshee, do you have time to bisect for it? is it a kernel issue ?16:38
sforsheetgardner, I'm pretty sure it's not a kernel issue16:38
tgardnerah, then not a kernel problem16:38
sforsheetgardner, I subscribed cnd to the bug, hopefully he'll have some input16:39
cndsforshee, tgardner: no input :(16:40
cndI don't know what might have changed16:40
cndbut there has been some work done to the bcm5974 and suspend stuff16:40
cndthere might be upstream patches in 3.3 or 3.4 that fix it too16:41
sforsheecnd, it seems like the touchpad still works fine, just that userland isn't doing anything with it16:41
sforsheei'll check upstream for patches though16:41
cndsforshee, are you saying that evtest still works, for example, but no events are coming through X?16:42
sforsheecnd, input events shows reasonable-looking events, and if I restart lightdm it starts working fine on the desktop16:43
cndsforshee, try using xinput test-xi2 to see if you get events from X16:45
sforsheecnd, yes, I get events16:46
cndsforshee, so you get events, but the cursor doesn't move?16:46
sforsheeexactly16:46
cndsforshee, what kinds of events are you getting when you use one finger?16:46
cndtouch or motion?16:46
sforsheeoh, sometimes I get right clicks too16:46
sforsheecnd, I see RawTouch* events16:47
cndsforshee, ok, we don't care about raw events for now16:47
sforsheethat's all I'm seeing16:47
cndsforshee, what non-raw events do you see if you put two touches down?16:48
sforsheecnd, none, just RawTouch stuff16:50
cndsforshee, and three touches?16:51
ppisatiapw: nope, since my panda's video out is still broken, waiting for the new one16:51
cndalso, please pastebin the output of "xinput list-props bcm5974"16:51
ppisatiapw: i think it'll have to wait until after first SRU16:51
ppisatiapw: since thursday is KF16:52
sforsheecnd, the same16:52
cndhmm16:52
cndsforshee, check for any errors in your Xorg.log16:53
sforsheecnd, the only thing I find are some "unable to find touch point 0" messages16:54
cndhmm... that could be related16:54
cndsforshee, I seem to recall someone saying that on lid closure the trackpad sometimes emits touch events16:55
apwppisati, kernel freeze means we move to SRU mode, limiting updates without appropriate acking, its not impossible to get things in, and easier probabally than after release16:55
apwppisati, where is your replacement coming from?16:55
cndI don't know if it's a capacitive effect or merely your fingers are close to it when closing the lid16:55
cndI wonder if some evdev events are getting lost at suspend/resume time16:56
cndso a touch is stuck in the "open" state16:56
cndsforshee, it might be worthwhile to do a suspend/resume while recording events using evtest16:56
sforsheecnd, here's something strange16:56
apwwe probabally reset the thing having powered it off for suspend16:56
cndand then seeing if there are any anomalies16:56
ppisatiapw: austria, but "upstream" didn't deliver any boards to them yet, it seems there's a shortage16:56
sforsheeI'm noticing that right now my one-finger touches are behaving like two-finger touches; i.e. they are causing scrolling16:57
cndsforshee, ahh yes!16:57
cndthat's exactly what I was thinking might be happening16:57
apwppisati, and we don't have any you can test on anywhere we can either get you access to 'em or send one to you?16:57
cndsforshee, a touch is stuck in a state where X thinks it is active16:57
ppisatiapw: pgraner told me he was sending me a board this week16:57
cndsforshee, how reproducible is it?16:58
ppisatiapw: actuallyt i could try another rebase tomorrow, and shell it to someone on #arm16:58
sforsheecnd, it happens 100% of the time if I suspend using the lid16:58
ppisatiapw: for testing16:58
apwppisati, well thats something, but we should hastle as the timeing is very poor16:58
apwppisati, yes use them and abuse them16:58
cndsforshee, ok, then do the evtest thing during a suspend/resume16:58
cndlet's see if we catch any bad events16:59
sforsheecnd, ack16:59
apwcnd, i wonder if it sees its own lid :)16:59
cndapw, could be :)16:59
ppisatiapw: just to clarify, the TI stuff is up to date (no more pulling from them) we are slacking behind wrt to master16:59
pgranerppisati, I sent it to millbank and msm will be sending it down to you16:59
ppisatipgraner: k, thanks16:59
apwppisati, ok its arrived in london and i'll be winging its way tommorrow17:01
sforsheecnd, is it important that there be a suspend/resume, or just a lid close/open? Because the device is being grabbed when I'm on the desktop, so evtest can't get the events.17:01
ppisatiapw: cool17:01
cndsforshee, switch to a VT17:01
cndthen run evtest17:01
cndoh, but then it doesn't suspend17:02
cndI see17:02
sforsheeyep :)17:02
cndsforshee, so you can use an Xorg.conf rule to tell X not to grab the device17:02
apwcnd, we need a bpf for the events ...17:02
sforsheeI can do sleep 2; pm-suspend on the VT17:02
cndapw, bpf?17:02
apwberkely packet filter, its whats uses to pick out ehternet frames, and i tink now usb and bt frames17:03
apwand they were using it for something else mad the other day, now what was that17:03
apwseccomp maybe it was17:03
sforsheesyscall filtering17:03
sforsheeyep17:03
apwso it must be the right thing for event monitoring :)17:03
cndheh17:03
cndsforshee, there's a better way to do this17:04
cndbut the faster/hackish way is:17:04
cndadd 'Option "GrabEventDevice" "false"' to /usr/share/X11/xorg.conf.d/50-synaptics.conf17:05
cndinside the touchpad catchall block17:05
cndI don't think you'll see any issues when you have the option set17:05
cndI think it's there for a couple of very specific circumstances17:05
cndsforshee, once you've added it, you need to log out and back in17:06
cndthen you should be able to evtest while in X17:06
apwstopping people reading your keyboard while you are typing perhaps17:06
cndapw, no, that input class section is only for trackpads17:06
cndat one point I knew why we grabbed devices by default17:07
cndit papers over missing functionality needed in the X synaptics driver17:07
apwi am glad to hear your brain has flushed that information17:07
apwmine does it all the time17:07
cndheh17:07
sforsheecnd, that seems to be working17:08
cndcool17:08
sforsheecnd, http://pastebin.ubuntu.com/911740/17:10
cndsforshee, did all this occur just by closing the lid?17:13
apwoh joy firefox, chromium, and libreoffice updates ...17:13
sforsheecnd, i did wiggle my finger on the touchpad after resume17:14
cndsforshee, oh...17:14
cndsforshee, can you get a clean recording without any intentional touchpad interaction?17:14
sforsheeI can redo it without the wiggling17:14
cndthanks17:14
apwcnd, though its reporting a 4 finger touch right?  and i assume he only did one17:14
apwor he used his forhead17:15
sforsheei always use my forhead, is that unusual?17:15
cndheh17:15
cndapw, good point17:15
cndsforshee, did you only use one finger?17:15
apwbut you do want a clean 'un17:15
sforsheecnd, yep, one finger17:15
cndhmm... then my guess is the driver is screwed up too :)17:16
cndsforshee, btw, you can probably reset the state back to a good starting point by reloading the bcm5974 driver17:17
* tgardner relocates17:17
sforsheecnd, non-wiggling evtest output: http://pastebin.ubuntu.com/911751/17:18
cndsforshee, really?17:18
cndthere's a ton of stuff going on :)17:18
cndbut it's masked by bad state too17:18
apwEvent: time 1333386946.147384, type 3 (EV_ABS), code 50 (ABS_MT_WIDTH_MAJOR), value 763017:19
apwEvent: time 1333386946.147386, type 3 (EV_ABS), code 51 (ABS_MT_WIDTH_MINOR), value 649217:19
sforsheecnd, reloading bcm5974 did get pointer motion back, and compiz also crashed :)17:19
cndsforshee, can you do the same after reloading the driver?17:19
apwwaht the resolution of this thing ?17:19
cndfun...17:19
apwthats a pretty big finger in most coordinate systems17:19
cndapw, look at the top of the printout17:19
cndit gives the axis max and min for each code17:19
cndit has a pretty high resolution :)17:19
apwso those are outside the surface area then no ?17:20
sforsheecnd, you want the evtest output again after reloading the driver?17:20
cndlooks like it17:20
cndsforshee, yeah17:20
apwas its saying 1280x800, and then saying you have a 7k wide finder17:20
apwfinger17:20
apw      Max     204817:20
apwso that number can't be >2k ... ooops17:20
cndapw, or the driver writer had never seen a value higher than that17:21
cndthe X and Y max and min for the magic trackpad are merely the highest and lowest values I could get17:21
cndwe don't have specs for apple devices :(17:21
apwahh ok17:21
cndapw, but those numbers are *way* beyond the max17:22
cndso something seems wrong17:22
sforsheecnd, http://pastebin.ubuntu.com/911758/17:23
cndapw, oh, I think I know what's going on with those numbers17:23
cndthe width values are supposed to be scaled, as best as possible, to device units17:23
cndbut often times the width values reported by the devices are in some random other unit17:24
cndso a scale factor is devised17:24
cndI would have rather seen evdev report the raw values from the device; that was a henrik decision17:24
cndsforshee, there's still a lot going on, but this is a good baseline17:26
cndso in the first packet there are two new touches17:26
cndin the second packet there appear to be three touches17:26
cndhowever, BTN_TOUCH is 0 and BTN_TOOL_TRIPLETAP is left at 017:27
cndI don't understand what is going on there17:27
apwcnd, could they be getting softer, cause the pressure is also 017:28
apwcould this literally be the screen bouncing off the touchpad ?  does the machine have a touchscreen too?17:28
cndapw, could be, but the touches are still active17:28
cndapw, touchscreen would be a different evdev node, but this doesn't have a touchscreen anyways17:28
sforsheeapw, no touchscreen17:28
apwi was more thinking is the screen made of something that acts like fingers, obviously gloved hands don't work etc17:29
cndit seems like the single touch events (BTN_TOUCH, BTN_TOOL_*) are not in sync with the mt events17:29
cndwhich is bad enough17:29
apwcnd, i dee in the next packet we have 4 taps17:29
cndyeah17:29
sforsheeI do think there are magnets involved in the lid switch mechanism, which may be close to the touchpad17:29
cndsforshee, does the cursor still move?17:30
apwthen we move, drop to three touches (correctly), back to four, then lose the touch with them again17:30
cndafter this particular recording17:30
cndbecause all the touches have ended17:30
sforsheecnd, it does now because I reloaded bcm597417:30
cndoh17:30
sforsheebut it didn't after I killed evtest17:30
cndhmmm17:30
* apw wonders if he has any magnest to wave at his touchpad17:31
cndheh17:31
apwcking, you have magnets i bet ... do they affect touchpads to you know?17:31
cndsforshee, I would send a note to henrik, and cc linux-input, asking about this behavior17:31
cndI think others have seen it17:31
cndbut I can't seem to find any emails17:31
ckingapw, I can find some... let me see what the kids have17:31
apwoh i have a fridge magnet, let me try that17:32
cndsforshee, there seem to be two issues:17:32
apwthis machine has an ssd so i should keep the disk contents :)17:32
cnd1. the driver is not in sync between mt and st data17:32
cnd2. has anyone looked into this already, is there a fix or a workaround?17:32
ckingapw, so what do you want me to try then?17:32
apwcking, does it affect your touchpad at all17:32
ckinghere goes..17:33
apwdoesn't on mine (found a ladybird on the fridge)17:33
sforsheeapw, I'm failing to get a reaction from the touchpad using a magnet17:33
ckingapw, no, but my HDD is now wiped ;-)17:33
cndsforshee, try taking the screen of another laptop and hovering it over the trackpad?17:33
* cking saunters off, was on at 7am..17:33
cndmaybe the LCD is doing it :)17:33
apwcnd, you have a separate one of those don't you?17:34
ckingcnd, bet the speaker magnets in the LCD are affecting it17:34
apwcking, well except they don't on yours at least17:34
cndapw, you mean a magic trackpad?17:34
cndI could try that17:34
apwyeah that is likely similar device is it not17:34
apwi guess the trackpads are metal whereas mine may not be, so it may have more effect there17:35
cndapw, ooo!17:35
apwcnd, it does vomit for some time either side doesn't it17:35
apwoooo ! ?17:35
cndI got stuff when waving my MT across the top of my macbook lid17:35
cndwhere the magnets are17:35
apwthere are serious magnets in there17:36
ckinghttp://www.gizmag.com/100-tesla-pulsed-magnet/21946/17:36
cking100 tesla magnet will do 17:36
apwanother apple special then, their own trackpad is affected by the magnets they use to close the box17:36
cndactually, it does it to the screen too17:36
cndso it may not be the magnets17:36
apwcnd, i suspect thats not normal for other touchpad types17:36
sforsheeapw, cnd: I can get events by holding a macbook pro near the macbook air touchpad17:37
cndapw, hard to tell17:37
apwsforshee, so if you shove two or three sheets of paper in the gap and close/open does it do that17:37
apwwe might be able to tell if its magnets (longer range) or plastic coating touching (short/zero) range17:37
sforsheeapw, yes, when the lid is very close to closing I start getting some events17:37
cndsforshee, I wonder if you add a resume hook to the driver to reset the state if it will fix things?17:37
sforsheebasically it seems to happen at the point where the lid tries to snap closed17:38
apwcnd, should we not worry they could make 'valid' events and do something awful like close or move a window17:38
cndhmm... good point17:38
apwlike needing to disable the touchpad stream as soon as the lid event starts or something?17:38
cndyeah17:38
cndI don't know exactly how you would do that though...17:39
apwsforshee, can we tell when the lid event occurs, ie does the machine suspend if you close it reallly really slowly17:39
apwcnd, well OSX must be able to cope, so likely the lid event is in before the interferance starts17:39
apwsforshee, as a test maybe you could do something like close the lid in glacial time17:39
apwand see if it triggers before the events start17:39
cndapw, yeah, probably17:39
cndapw, but how could you code that up in a linux driver17:40
cnd?17:40
apwyou'd need to let the two kernel dirvers know about each other17:40
cndI don't know if there's some way the bcm5974 driver can listen for lid events17:40
apwwhich is vileness extreme17:40
cndyes17:40
mjg59Not trivially17:40
mjg59You could add a notificaiton chain17:40
cndmjg59, ahh, should have pinged you earlier :)17:40
mjg59Or you could push it out to userspace17:40
apwyeah its bound to be a violation of about 20 layering17:40
cndmjg59, if you pushed it out to userspace you might have race conditions17:41
mjg59Have a udev helper fire on the lid event and disable any USB input devices that are flagged as non-removable17:41
cndmjg59, how could you be sure the bcm5974 driver will get it in time?17:41
mjg59cnd: It's going to be racy on a multi-threaded system in any case17:41
cndI'm not meaning issues between cores17:41
cndI mean issues in time17:41
apwi think if it even does it of course, you would have to have the MT driver check before emitting any packet17:41
apwwhich would mean looking at something global and shared in the kernel, which stinks17:42
cndlike, the event reaches userspace, userspace processes it and turns the touchpad off in 100 ms17:42
cndbut that's already too late17:42
cndI suppose my theory is that keeping things in kernel will reduce the time enough that it is more reliable17:43
apwwe'd need to confirm somehow the order of the events, is there anything we hear of in time even17:43
* cnd wonders how we haven't seen this before17:43
apwhttp://askubuntu.com/questions/91534/disable-touchpad-while-the-lid-is-down17:43
apwsforshee, you might be able to use that to get a hint as to whether the lid closes before the problem happens if you arn't to quick :)17:44
cndI bet because of behavior changes in X17:44
sforsheeso I'm pretty sure at this point it is the magnet, as I can hold a macbook pro close to the touchpad but not touching and get touchpad events17:44
cndapw, that will only turn off the device at the X level17:44
sforsheeI also know I can suspend the machine without completely closing the lid17:45
cndmaybe that's good enough though17:45
cndsforshee, you can evtest both the bcm5974 and the lid switch devices17:45
cndand compare the timestamps17:46
apwsforshee, when does the backlight go off relative to the problem occuring too17:46
cndsee how close they get with fast lid closures17:46
ohsixit can be emi too, though i dunno much of which would be near where the magnets are17:46
apwsforshee, what cnd suggests makes the most sense.17:46
ohsixmy friend could make his macbook reboot by putting his phone next to his computer, they can be pretty sensitive :D17:46
apwlets see if they are in any sort of sensible order17:46
sforsheeapw, it goes off earlier -- there seems to be something else in play for the lid event17:46
cndsforshee, what goes off earlier?17:47
sforsheeI can't make the machine suspend by holding the MBP closeby17:47
sforsheecnd, the backlight17:47
cndoh17:47
apwsforshee, isn't that triggered by the lid event ?17:47
* apw thinks we need the double evtest comparison17:47
* sforshee is getting it right now17:48
* cnd whipers17:48
cndwhispers...17:48
cndI ruined it17:48
sforsheethe lid switch event happens first, by about 400 ms17:51
apwok so we at least have something to tell us when we need to ignore it17:51
cndsforshee, including when you try to close it as fast as possible without breaking it?17:51
apwsforshee, i assume it unhappens after the flood stops too yes?17:51
sforsheecnd, I was just about to say, let me try again closing the lid as quickly as possible17:51
ohsixsforshee: was the input periodic or just fast/seemingly random17:51
cndohsix, http://pastebin.ubuntu.com/911758/17:52
apwohsix, its a bunch of fat fingers reported all over the touchpad17:52
apwcnd, this feels very familiar you know, is the matrix broken ?17:52
ohsixinteresting, it could be the lcd17:52
apwohsix, i think experimentation says its the lid in some sense, which bit isn't so interesting17:53
sforsheerats, now I start getting touchpad events about 7 ms before the lid event17:53
cndugh17:53
apwsforshee, well ... remember we have to get them out into userspace17:53
apwwho puts the timestamps on them, the uspace daemon ?17:53
sforsheeapw, yes17:53
sforsheebut they're certainly very close17:54
cndapw, that doesn't even matter now17:54
cndthe lid switch is occurring *after* the bad touches17:54
apwcnd, where is the timestamp we see added17:54
ohsixright but a magnet isn't going to capacitively couple with a touchpad, it may induce currents but only as it moves (no matter how strong it is)17:54
cndapw, hmm?17:54
cndI didn't understand the question17:54
apwcnd, we have two streams of data with timestamps, who put the stamps on them, the kernel or the evtest app17:55
cndapw, the kernel17:55
sforsheeapw, 7 ms seems long enough that I doubt they're getting reordered anyway17:55
ohsixsome heuristics in the touchpad firmware are probably going bonkers because it's coupling with something in the display17:55
apwohsix, yep i think we know that ... what we don't know is how to stop it17:55
apwgiven the lid is not going to change compisition17:56
ohsixright :] it's just not a magnet17:56
ohsixyou may be able to control SSC or something in the lcd panel that could affect it tho17:56
apwsforshee, it may be worth looking for reports of whining on osx about closing the lid and it being bad17:57
apw(if you do it fast)17:57
cndbtw, my MT sees touches even when the screen is off17:57
sforsheeohsix, there seems to be a magnet in the lid that holds the lid down when it's closed17:57
cndso merely turning the screen off isn't a fix either17:57
sforsheeso when you close the lid it will be moving, period17:57
ohsixcnd: what model is it?17:57
sforsheemacbook air 4,117:57
cndohsix, I was playing with a magic trackpad and a macbook 5,1 (I think)17:57
apwcnd, yeah wasn't thinking we want to turn off the screen, i was thinking we want to disable the touchpad17:58
cndyeah, I was just throwing it out there17:58
cndin case anyone else thought about it :)17:58
apwcnd, that link i posted is from something with MSI hotkeys, doing the same sort of thing17:59
cndapw, I missed the link17:59
cndoh, nm17:59
cndI got it17:59
apwsforshee, so i assume if you turn off 'suspend when closed' we could get a trace then which would tell us if its the screen moving or it being closed at all is the issue17:59
sforsheecnd, the root problem though is that userland is in a confused state though, right? so can we reset the userland state after s3?17:59
apwsforshee, what if it quad clicks on something18:00
cndsforshee, maybe18:00
sforsheeapw, true18:00
apwcnd, actually arn't the touches 'really really big' ?18:00
cndnot all of them18:00
apwcnd, and doesn't osx have "stop palms from doing bad things" support ?18:00
apwmaybe they get away with it cause of that18:00
sforsheeapw, cnd: actually I've noticed a few times that the dash is up after S3 when I'm sure it wasn't before, so that's probably caused by these events18:00
cndmaybe18:00
cndheh18:01
apweeek18:01
apwsforshee, so maybe try the thing they do in there and see if it helps any18:01
mjg59Ok, easier way:18:01
mjg59Have the X server tag all input devices as internal or external (or unknown)18:01
mjg59The X server is single threaded, so can't race against itself18:01
mjg59On lid close, stop listening to internal events18:02
ohsixthe magnets are pretty far away from the camera18:02
mjg59Doesn't help in the case where the events are out of order, but...18:02
apwmjg59, sounds logical, at least there it has only a 7ms window instead of 'all night' to get events18:02
cndmjg59, there's no real way for one X input module to listen to events from another18:02
ohsixhere's the stuff at the top of the frame http://guide-images.ifixit.net/igi/jcpGIlZE1LLllEoQ.medium http://guide-images.ifixit.net/igi/fGqAJCnKVgROdlkl.medium18:02
cndIIRC18:02
cndand part of the state that needs to be maintained is in the X synaptics module18:03
cndhowever, the X server could turn off an input driver18:03
ohsixheh what mjg59 suggests is probably a good idea for all machines :D (if there's a reliable indication when the lid is working)18:03
cndmjg59, that still doesn't resolve the problem of fast lid closure18:04
cndwhere the lid event occurs after the bad touches18:04
apwcnd, we actually can't program round bad h/w design18:04
apwcnd, if you close it fast and it presses random shit, there is little we can do about it18:04
cndyeah18:04
apwi know you don't want to hear an apple product has bad design, but ... i suspect it does18:05
sforsheei literally slammed the lid, it will rarely be closed that fast18:05
cndsadly, I can't test this18:05
cndbecause my macbook won't suspend/resume properly18:05
cndok, then maybe it will be good enough18:05
apwsforshee, the joys of work owned test key :)18:08
apwkit18:08
=== tgardner is now known as tgardner-lunch
* sforshee goes to find some food18:10
=== tgardner-lunch is now known as tgardner
ppisatiunity2d can finally enjoy the launcher on the second screen... @$#%@#@$@#...18:49
beata|lemurI get an error message when I run the 'git rebase --onto origin/master origin/master@{1}' command listed on the kernel git guide wiki, section 'Maintaining local changes': 'fatal: Needed a single revision' 'invalid upstream origin/master@{1}'19:08
apwogasawara, that testing came in, postitive so am about to push those hyper-v patches19:10
ogasawaraapw: ack.  go ahead and push, I'll wait to rebase to 3.2.14 till after you've pushed.19:10
apwogasawara, ok done, thanks19:12
tgardnerogasawara, how's the Q rebase going ?19:13
ogasawaratgardner: just finishing it up and am about to test build19:13
Kanoapw: could you touch the missing include file maybe? even a 0 size file is enough to fix compilation issues19:46
Kanodid somebody else notice that kernel 3.3+ boots faster than 3.2?20:07
Kanosimilar speed to 2.6.38 which was faster than .39+20:07
Kanodebian 3.2: 8s, mainline u config: 7s, since 3.3: 5s20:09
Kanoi boot wheezy btw ;)20:12
=== popey_ is now known as popey
=== stgraber_ is now known as stgrber
=== stgrber is now known as stgraber
* tgardner -> EOD20:31
* ppisati -> reboot21:16
Kanodoes anybody know why booting via efi is slower22:00
lesshasteis there a workaround for https://bugs.launchpad.net/ubuntu/+source/linux/+bug/884210 ?22:01
ubot2Launchpad bug 884210 in linux "PCI/internal sound not working randomly, random hangs: "cannot set freq 16000 to ep 0x86" shown in syslog" [High,Confirmed]22:01
lesshasteoh is there an easy way to test a more recent ubuntu kernel?22:02
lesshasteI am on oneiric22:02
ayanall: what determines which modules are loaded at boot time?  i notice /etc/modprobe.d/* but those files seem to determine what isn't loaded more than what is.22:10
Kanoudev22:11
Kanolesshaste: which gfx card22:11
lesshaste01:00.0 VGA compatible controller: nVidia Corporation NV44 [Quadro NVS 285] (rev a1)22:13
lesshasteKano, ^^22:13
Kanonvidia binary used?22:13
lesshasteI just switched to nouveau22:13
lesshasteto see if it would help22:13
Kanobecause you need hacks for newer kernels22:13
lesshasteI still get  cannot set freq 16000 to ep 0x8622:13
lesshasteI just want to be able to use the quickcam without it destroying my compute r:)22:14
ayanKano: i suspected udev might do it but -- for example -- i have psmouse loaded but i don't see it anywhere in any of the udev configuration files.22:14
Kanoalias:          serio:ty05pr*id*ex*22:14
Kanoalias:          serio:ty01pr*id*ex*22:14
Kanoyou see with modinfo psmouse22:14
lesshasteKano, are there no kernels in backports?22:15
lesshasteKano, that I can use in 11.1022:15
Kanoi dont use ubuntu22:15
lesshastewe are in #ubuntu-kernel!? :P_)22:15
KanoKERNEL22:16
Kanoi recompile it or use mainline ones22:16
=== infinity1 is now known as infinity

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!