/srv/irclogs.ubuntu.com/2010/09/17/#ubuntu-kernel.txt

keesogasawara: looks like -22.32 is missing the guard page change00:34
ogasawarakees: hrm, were there additional patches besides the one I mentioned earlier?00:58
undriedseaHi everyone, I'm having a problem with a kernel module crashing when I attempt to modify the system call table. Which would be expected, except that I have made its page in memory writable before attempting this feat. Any ideas would be very much appreciated :) http://codepad.org/W3ThQbb802:45
AceLan_undriedsea: wow, interesting02:50
undriedsealol, are you being sarcastic Ace? I know its not terribly complex, but it has me stumped02:51
AceLan_undriedsea: no, I never thought of you can modify sys_call_table by that way02:52
jk-undriedsea: are you just trying to catch calls to sys_open?02:52
undriedseayes, but this is just a test. I have a bunch of system calls I need to hook into at a low level. LD linking is not good enough for me because apps could call the syscall directly and not use the C lib, and I need to handle that02:53
lifelessundriedsea: there is a runtime patching system for the kernel some US guys wrote a few years back; they do this sort of thing and much more complex too - have a look into that02:54
jk-are you looking to modify the syscall's behaviour, or just monitor it?02:54
undriedseain this test I am monitoring. I will be changed the behavior02:55
undriedsea*changing 02:55
undriedseaI will take a look at that lifeless. I still, for my own sake, would really like to understand why my code does not work02:55
jk-undriedsea: also, you can still do this in userspace via ptrace()02:57
undriedseathanks jk, I thought about that, but for the project the context switch overhead would kill performance02:58
undriedseaI realize this is the old/dirty way to intercept a syscall, but it is also very fast- and I can't think of why that code does not work. However, I must confess- I have not spent much time with this kernel 03:00
jk-undriedsea: so what's the oops message you're seeing?03:01
undriedseaSep 16 19:51:02 kdev kernel: [  145.012726] BUG: unable to handle kernel paging request at ffffffff8155139003:01
undriedseathat is the address of the system call table03:01
undriedseaor actually sys_call_table[__NR_open]03:02
jk-could you paste the rest of the log?03:02
jk-err, pastebin, not paste in the chan03:03
undriedseasure http://codepad.org/O01qFsdz03:03
undriedseaThank you for bothering to take a look :)03:04
jk-and what's the instruction at init_module+0x51 ?03:05
jk-(could you pastebin a disassembly of init_module?)03:06
AceLan_undriedsea: I got BUG: at set_memory_rw() function call03:06
AceLan_undriedsea: not OOPS03:06
undriedseathat is interesting, what is your platform? I am amd6403:07
undriedseaAlso, did you change the sys_call_table address to match your own system AceLan?03:07
jk-AceLan_: yeah, it's probably bugging in change_page_attr_set_clr, because the page address is not page-aligned03:07
AceLan_undriedsea: a normal i386 kernel03:08
undriedseajk, can I use hexdump to do that?03:08
AceLan_undriedsea: sure, I changed the address03:08
jk-undriedsea: objdump -d 03:08
jk-undriedsea: you're probably seeing that WARN_ON_ONCE too03:08
undriedseajk: the dump http://codepad.org/FcHuSS0c03:09
undriedseajk: do I need to make sure my call to set_memory_rw is 4k aligned?03:10
jk-undriedsea: it should be, but that's not what's causing the oops03:12
jk-also, are you sure that this disassembly matches the module that you inserted to cause this oops?03:12
undriedseaMaybe- I ran that objdump on the .o, should it have been on the .ko ? (n00b sorry...)03:13
jk-on the .o is fine03:13
jk-but the oops log reports that your init_module function is 0x70 bytes in size, whereas the disassemly would indicate that it's 0x49 bytes03:14
AceLan_undriedsea: read this # http://www.downloadpipe.com/forums/linux/Problem-set_memory_rw-ftopict76420.html03:14
AceLan_system call table is on .rodata section and set_memory_rw() doesn't03:14
AceLan_allow change attributes on .rodata sections(not .text) 03:14
undriedseamy .ko dump is much larger03:14
undriedseaThanks ace!03:15
undriedseaI guess I will have to modify the page table directly to accomplish my goal03:15
undriedsea:(03:16
jk-or patch sys_open03:16
AceLan_undriedsea: yes, you have to export sys_call_table 03:16
undriedseaThat would require my end users to install a custom kernel wouldn't it, rather than just install my module?03:17
AceLan_undriedsea: you have to modify the kernel :(03:17
jk-but this is all pretty ugly, what are you actually trying to do?03:17
jk-AceLan_: exporting it will only expose the linkage, will still be able to refer to it by symbol address03:18
undriedseaI am writing a process live migration module, I need to capture sys_calls and translate file handles, process IDs etc. For example, a process might get moved to a machine where its PID conflicts with an existing PID, so I need to hide this03:19
undriedseaIf I was writing this 6 years ago before all this stop exporting the sys_call_table, make it RO nonsense, it would be much easier :)03:19
AceLan_wow, sounds so cool, process moves among machines03:20
undriedseaWell, I hope it is cool when I am done, or I will be working on my masters project a looong time lol :)03:21
AceLan_undriedsea: how about not real move the process, indtead of recreating the same one on another machine?03:21
undriedseaThose are the same things, I am doing two things, replicating the process state, and hiding namespace issues (file handle number, PIDs, semphore ids, etc)03:22
undriedseaI cannot change the PID even after moving becuase the programmer of the application may have made a call eariler to get the PID and their code might now be depending on that value03:23
AceLan_right, very reasonable03:24
undriedseaThere are other methods besides doing what I am doing, but they are either slow (because the involve kernel/user-mode context switches) or they only capture syscalls made through the standard libraries (which means I could not migrate applications which directly make system calls)03:25
AceLan_undriedsea: have you to use 2.6 kernel? I think modify sys_call_table in 2.4 kernel is much easier03:26
undriedseaSo I guess I will be directly changing the page table using the low level instructions because the kernel is silly and won't do it03:26
undriedseaYou are correct, however, I want people to be able to do useful things with the result of my project03:26
undriedseaI could just make my own kernel build that turns the security off in 2.6 too, but ideally, I only want people to need to load a module (if at all possible)03:27
jk-undriedsea: what are you doing about kernel state - open files, sockets, etc?03:29
undriedseareplicating it03:30
jk-how?03:30
undriedseaBy keeping track of kernel state of live migration processes and recreating that state on the new host. The unique identifier might not match, but my namespace translation later takes care of that03:32
undriedseaor will, I am just getting started03:33
jk-undriedsea: have you read Eric Roman's survey of Checkpoint/Restart implementations?03:40
jk-undriedsea: and Zhong and Nieh's CRAK paper?03:40
undriedseaCRAK and ZAP yes, I will look for Erics03:42
undriedseaI found the code that is killing me,  832        if (!pgprot_val(mask_set) && !pgprot_val(mask_clr) && !force_split)03:43
undriedsea 833                return 0;03:43
undriedseahttp://lxr.linux.no/#linux+v2.6.31/arch/x86/mm/pageattr.c#L81803:43
jk-you can control the fd table, so you don't need to worry about translating FDs03:44
undriedseafd, file descriptors?03:45
jk-yep03:45
undriedseacool, that will be nice03:45
undriedseaWhen looking at System.map, what do the single character values after the address and before the symbolic name denote?04:09
AceLan_undriedsea: The "How to get sys_call_table" and "Simple sys_call_table hook" might useful # http://www.slideshare.net/fisher.w.y/rootkit-on-linux-x86-v2604:44
=== BenC___ is now known as BenC
undriedseaAceLan, that is very interesting, thank you04:57
=== fddfoo is now known as fdd
lagdiwic: Hi08:20
diwicHi lag08:21
lagI'm assuming you have a vast array of test audio files?08:21
lagDo you have any S32_LE?08:21
diwiclag, naah, but use the plug layer and it will convert it for you08:22
lagOkay08:22
lagCheers08:22
lagI'll probably be pestering you a few times today - stay alert ;)08:22
diwiclag, or if that doesn't work, I can create one in audacity for you08:23
lagCool, thanks08:23
=== diwic is now known as diwic_afk
=== amitk is now known as amitk-afk
=== diwic_afk is now known as diwic
=== makx_ is now known as maks_
diwicogasawara, ping10:28
=== diwic is now known as diwic_afk
=== amitk-afk is now known as amitk
=== diwic_afk is now known as diwic
lagdiwic: Can you come into #ubuntu-arm?13:03
=== bjf[afk] is now known as bjf
bjfJFo: cranberry is now running lucid14:55
JFoexcellent14:55
diwicbjf, I talked to takashi about his dailies, he said they were created after midnight, his time. So if you run your script approx UTC+3, that would be optimal15:01
bjfdiwic, thanks, I can make that happen15:01
diwicbjf, great :-)15:02
bjfdiwic, where does takashi live?15:03
diwicbjf, in Germany I believe. 15:04
diwicbjf, which is UTC+1 +DST15:05
bjfdiwic, ok, that puts him 9 hours ahead of me15:05
diwicbjf, and me as well then - amazing you're up already ;-)15:06
smbdiwic, UTC+215:06
bjfdiwic, it's 7 a.m. already! where has the day gone?15:07
diwicsmb, UTC+1 in winter and UTC+2 in summer, right?15:07
smbright15:07
diwicsame as here.15:07
diwicsmb, you are from Germany as well, right?15:08
smbI am, yes. I am never sure about Takasi thoug. :)15:08
bjfdiwic, so his midnight should be my 15:00 15:09
smbPeople tended to believe GregKH to be in Germany, too as he has a suse.de email address as well. 15:09
smbbjf, Its 4:10pm here if that helps15:09
JFobrb15:10
bjfsmb, the math still works out :-)15:11
bjfdiwic, time on the cron job has been adjusted15:13
diwicbjf, thumbs up15:13
cndogasawara, manjo: bug 64132015:14
ubot2Launchpad bug 641320 in linux (Ubuntu) "Touchpad is not working since last kernel update in maverick (affects: 1) (heat: 6)" [Critical,Triaged] https://launchpad.net/bugs/64132015:14
cnddue to the new ALPS patch15:15
cndmanjo, why did you push the dell patch instead of the patch on LP that had bug fixes in it?15:15
manjocnd, I picked the patch from the LP 15:15
manjocnd, and jerone tested it at dell 15:16
cndoh, someone on the LP bug thought it wasn't that patch15:16
cndthey thought it was the upstream patch15:16
cndeither way, we probably need to revert the patch15:17
apwperhaps one of you could confirm we didn't end up taking the upstream patch15:17
manjocnd, :) heh funny coz you recommended that  patch in the 1st place 15:17
cndheh, I pointed it out :)15:17
apwit may have been assumed it was the same and that one cherry-picked instread15:18
cndno recommendation15:18
cndjust that it has some fixes the dell one doesn't15:18
cndbtw, sorry if I'm a bit curt15:18
cndin the middle of xds :)15:18
apwcnd/manjo, which was the original bug15:18
cndapw, I need to dig it out15:18
cndhttp://bugs.launchpad.net/bugs/63288415:19
ubot2Launchpad bug 632884 in linux (Ubuntu) (and 1 other project) " Add support for Intellimouse Mode in ALPS touchpad on Dell Latitude series Laptops (affects: 1) (heat: 10)" [Undecided,Fix released]15:19
bjfmanjo, cnd, this sounds like the problem davidm is also having15:19
cndmanjo, apw, the sauce patch in ubuntu doesn't match the LP patch15:22
manjocnd which lp patch are you taking about ? 15:22
apwcnd, seems to match the 'final patch' link15:22
manjoThe final patch can be found here:15:23
manjohttps://patchwork.kernel.org/patch/118834/15:23
manjothat is what I pushed 15:23
cndmanjo, which is the upstream submitted dell patch I said not to use :)15:23
manjocnd, I don't see any other patch there 15:24
cndmanjo, it's on the LP bug15:24
Sarvattcnd: bug work right so soon after you get done with a talk? you're a machine! :)15:24
cndheh15:24
cndhttp://launchpadlibrarian.net/54076279/2.6.35-alps-730264-imps-emulation.patch15:24
apwdammit this is serious, we have pushed the final maverick kernels15:24
cndmanjo, that's the patch I pointed to ^15:24
apwto get this fixed we need to get an exception15:24
cndfrom https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/550625/comments/15415:25
ubot2Launchpad bug 550625 in linux (Ubuntu Lucid) (and 2 other projects) "Alps touchpad is recognized but synaptics clients and scrolling do not work (affects: 113) (dups: 9) (heat: 576)" [Medium,Incomplete]15:25
apwbjf, does davidm have a bug also ?15:25
* apw will switch the patch and get some test kernles out to these bugs15:25
bjfapw, yes, though he's been unable to actually file it due to LP timeouts15:26
manjocnd, there is no mention of 550625 in 632884 so when you asked me to help with 632884 I did by picking up the final patch there 15:26
apwmanjo, there is though in comment #115:27
apwmanjo, anyhow i'll get some kernels together15:28
cndapw, might I suggest just pulling the patch?15:30
cndgit revert15:30
cndthe patch hasn't been reviewed upstream and we're so late15:30
cndand the trackpads still work without the patch, just not with scrolling support15:30
apwcnd, i thought you needed that in to get multi-touch or some shit15:30
cndapw, nope15:31
cndit was just a bug I wanted someone to look at15:31
cndsince I had seen someone in the community had worked on the patch some15:31
cndI didn't want it to fall through the cracks15:31
cndand disappear forever into LP :)15:31
hallynoh goodie, i get to blame manjo for breaking my tp :)15:32
manjocnd, so why did you ask me to look at it if it was not important ? 15:33
* hallyn shakes his fist15:33
cndI never said it was important :)15:33
cndI just said someone should look at it15:33
Sarvattthere are quite a large number of bugs against synaptics at least regarding the alps scroll situation that i'm moving over to that one right now, I wouldn't say its unimportant. not having touchpad scroll is a pretty crappy user experience15:38
cndSarvatt, it's not whether it's important or not15:40
cndit's that we're in kernel freeze15:40
cndand we aren't positive that we won't add more regressions with the patch from LP15:40
apwSarvatt, right, we really are past the point where we want to make any changes as someone has to respin every CD as a result15:41
apwand we have no time to get any testing on it, i'll mark the bug for consideration after release15:41
apw(the original one) and we can then test it more thoroughly15:41
cndmy hope was that someone would take a look at the LP patch many weeks ago, put it in a development kernel, and then we can work on upstreaming it15:44
cndthen oem services wanted proper alps support, and manjo and vanhoof looked at it a week or two ago15:45
cndtiming just wasn't as good as one could hope :(15:45
cndand I didn't have enough time to work the bug properly myself...15:45
robbiewJFo: ping15:46
JForobbiew, pong16:00
JFos'what I get for working on 2 machines16:01
robbiewJFo: nevermind...was going to ask you about I bug, but I decided it was easier to just ask the submitter as a comment ;)16:02
JFoheh16:03
apwhallyn, hey ... i'm just reverting that patch and will have some test kernels in about 10 mins for testing if you could confirm the revert fixes you16:10
hallynapw: cool16:10
* JFo stepping out for a bit. some errands and packing to complete before flying for Taipei tomorrow.16:13
ogasawarakees: about?  want to check back with you about the stack guard change you said was missing?16:19
ogasawarakees: I'd only applied the one patch from smb - http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-maverick.git;a=commit;h=1ccc5359a8f055b153a2e0cfec02a594a844336016:20
ogasawarakees: is there additional patches I need to get applied?16:21
ogasawarajjohansen: re "[PATCH 3/3] UBUNTU: SAUCE: AppArmor: allow newer tools to load policyon older kernels"16:24
ogasawarajjohansen: is there something you want modified with that patch per tetsuo's comments?16:24
hallynapw: actually gotta run for a bit, i'll test when i get back16:24
ogasawarajjohansen: we might have a chance to get that fixed and squeezed into a last minute upload16:25
keesogasawara: let me check if it passes now that I've rebooted16:25
keesogasawara: doesn't seem to pass16:25
keessmb: the test still fails on maverick with that applied ^^16:26
smbkees, hm...16:26
keesoh wait16:26
keesI'm still on the wrong kernel, one sec16:26
* smb holds his breath16:27
* ogasawara crosses fingers the right kernel works16:27
* smb turns slightly purple...16:27
keeskees@sec-maverick-i386:~/qa-regression-testing/scripts/kernel/guard-page$ cat /proc/version_signature 16:27
keesUbuntu 2.6.35-22.32-generic 2.6.35.416:27
keeskees@sec-maverick-i386:~/qa-regression-testing/scripts/kernel/guard-page$ ./split-stack stack start changed due to mlock call (0xbfa2c000 != 0xbfa4b000)!16:27
keesstill fails16:27
smbkees, is there more output to look at?16:28
keesfails on hardy even. *scratch head*16:28
ogasawarakees: how critical is this for landing in Maverick's release?16:28
ogasawarakees: as we've likely got one last shot for an upload16:29
smbI would say not very critical16:29
ogasawarasmb: so it could potentially be resolved via an SRU post maverick release?16:29
smbYes, sounds reasonable16:29
* kees will boot an upstream vanilla kernels16:29
keess/s$//16:30
smbkees, But those addresses seem to be too far apart to be one page...16:30
smbkees, Thats weird16:30
smbDo you have the full output of maps somewhere?16:30
keessmb: it goes from:16:30
keesbff13000-bff34000 rw-p 00000000 00:00 0          [stack]16:30
keesto:16:31
keesbff13000-bff33000 rw-p 00000000 00:00 0 16:31
keesbff33000-bff34000 rw-p 00000000 00:00 0          [stack]16:31
keesacross the mlock call16:31
smbkees, There does not seem to be a whole in there to me16:31
smberr hole16:31
keeshm? but the thing that got called "stack" got chopped up16:32
keesmaybe I misunderstood the issue?16:32
smbI suppose16:32
smbwron would be16:32
smbbff13000-bff33000 rw-p 00000000 00:00 016:32
smberrr what would be bff333000 +4k.16:33
=== tgardner is now known as tgardner-afk
jjohansenogasawara: yes, if we can squeeze it in16:34
smbkees, Seems to be an unfortunate example16:34
ogasawarajjohansen: yep, just get me a patch to the ml asap16:34
jjohansenogasawara: okay16:34
smbThe problem _was_ that you saw a gap between  the vmas16:34
apwsmb, 4k == 1000 hex16:34
smbapw, ta16:35
kees7fff810d6000-7fff810f7000 rw-p 00000000 00:00 0                          [stack]16:35
keesvs16:35
kees7fff810d6000-7fff810f5000 rw-p 00000000 00:00 0 16:35
kees7fff810f6000-7fff810f6000 rw-p 00000000 00:00 0                          [stack]16:35
=== yofel_ is now known as yofel
keessmb: there's a gap between 7fff810f5000 and 7fff810f600016:35
keesis that the bug?16:35
keesmy testcase is wrong, I guess.16:35
* smb scratches his head16:36
keesI thought it was the fact that the stack got misidentified16:36
smbkees, That looks more broken than anything I saw16:36
ogasawarajjohansen: if you prefer, just give me two patches, one to revert the original SAUCE patch and then the fixed up version16:36
jjohansenogasawara: okay16:37
smbkees, The problem was that the first page of a stack vma got hidden (start was moved up one page). 16:38
keesthat would seem to be what the "gap between 7fff810f5000 and 7fff810f6000" demonstrates16:39
smbkees, May be what you posted last. 6000-6000 (basically size 0)16:39
smbThe 6000-5000 looks really weird16:40
apwsmb, thats doesn't say 6000->500016:40
keesokay, the kernels before the guard page show:16:41
keesbfdd1000-bfde6000 rw-p 00000000 00:00 0          [stack]16:41
keesinto16:41
keesbfdd1000-bfde3000 rw-p 00000000 00:00 0 16:41
keesbfde3000-bfde4000 rw-p 00000000 00:00 0          [stack]16:41
apwit says d6000->f500016:41
keesso the split is "ok". it's the _gap_ that is bad.16:41
smbapw, ah ok missed that16:41
keesI'll fix the test case16:42
smbkees, But the second exapmple has no gap, right? bfdd1000-bfde3000 and bfde3000-bfde400016:42
smbkees, oh ah16:42
smbkees, yes16:42
* kees nods16:43
smbkees, the split is ok. but the address range should be connected16:43
keesI thought the bug was the splitting at all. I didn't realize the gap16:43
keesright16:43
keesfixing testcase...16:43
apwit always has to be split cause the permissions differ after the mlock16:43
keesapw: though oddly, the state of mlock isn't shown in maps16:44
kees(nor vma growth direction)16:44
apwkees, indeed, maps is a little useless16:44
apwkees, might be more in smaps16:45
tseliotapw: it seems that the following commit was included after 2.6.35-20:16:45
tseliothttp://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=c41d68a513c71e35a14f66d71782d27a79a81ea616:45
tseliotapw: this breaks fglrx16:45
tseliotcompat_alloc_user_space(), that is16:46
apwtseliot, how does it manifest, what breaks16:46
tseliotapw: I get error: implicit declaration of function ‘compat_alloc_user_space’16:47
tseliotapw: when trying to build the kernel module for fglrx16:47
smbtseliot, ITs likely because they exported thy symbol GPL16:47
apwtseliot, try converting the call to arch_compat_alloc_user_space()16:47
smbEXPORT_SYMBOL_GPL(compat_alloc_user_space)16:48
apwahh ... doh16:48
tseliotapw, smb: I could use arch_compat_alloc_user_space() but would this work on previous 2.6.35 kernels?16:48
ogasawaraogra, mpoirier: bug 630885, is that release critical?  or ok as a post release SRU?16:48
ubot2Launchpad bug 630885 in linux (Ubuntu) (and 1 other project) "Preinstalled Maverick netbook image has no display on omap3 EVM (no LCD) (affects: 1) (heat: 14)" [Undecided,In progress] https://launchpad.net/bugs/63088516:48
apwtseliot, nope16:48
tseliotapw: it was a rhetorical question ;)16:49
ograogasawara, we dont have such HW in the team, probably for linaro 16:49
ograogasawara, but since i expect changes for omap3 anyway it wouldnt do harm to have it too16:49
tseliotsmb: do you mean to say that they did EXPORT_SYMBOL_GPL(compat_alloc_user_space) in the fglrx code?16:49
smbtseliot, No they made the export like that in kernel/compat.c16:50
smbBefore that it was an inline function16:50
apwtseliot, no he is saying the kernel has been changed to only export it to GPL stuff16:50
tseliotsmb: ah, I get it now16:50
mpoirierogasawara: the request came from a TI guy - is we get it in great, otherwise that's just life.16:50
apwtseliot, sounds like you have just need to include a header though16:51
apwas the code you are compiling is GPL right, the shim is GPL16:51
ogasawarampoirier: and the patch itself is going upstream?16:51
mpoirierogasawara: I wish it could...16:51
mpoirierbut haven't had any luck with all our beagle work.16:52
ogasawarampoirier: tgardner had inquired16:52
smbtseliot, yeah, mabe including <linux/compat.h> works16:52
mpoirieryes, tgardner and I have talked about it.16:52
tseliotapw, smb: including <linux/compat.h> works but I can't because it's GPL while the file that should include it is not16:53
mpoirierogasawara: I'm thinking about enlisting outside key contributors to help with the push up.16:53
ogasawarampoirier: might be good to post the result of the discussion to the mailing list so we're all in the loop16:53
apwtseliot, add a shim funtion in the gpl file ?16:54
ogasawarampoirier: and I assume I should add the additional provenance for the patch?16:54
mpoirierogasawara: should we mumble ?16:54
ogasawarampoirier: sure16:54
MTecknologyI've been playing with compiling the kernel and trying to figure it out on that level. I got myself stuck though. I'm missing a module (I assume) but I have no idea what module it might be.. My system boots pretty nice. It even loads to TTY7 (only 1 and 7). This is what I wind up seeing. http://pastebin.ubuntu.com/495371/ (Maverick). Any chance I could get a little pointer?16:58
=== amitk is now known as amitk-afk
jjohansenogasawara: patches should be on the list now17:03
ogasawarajjohansen: great, thanks17:03
tseliotapw: ah, so a simple function that calls arch_compat_alloc_user_space() in asm/compat.h?17:05
smbtseliot, I probably would rather do a simple function that call compat_alloc_userspace (to get the benefit of the additional checks) which is defined in a gpl'ed code17:07
apwtseliot, indded as smb suggests17:10
apwfgrlx_alloc_user_space() { compat_aloc_user_space() }17:10
apwstylee17:10
apwand that should be compatible either way i think17:10
apwthus showing how stupid the whole export_gpl stuff really is, as you can comply with the rules17:11
tseliotapw, smb: ah, so I could add that function in asm/compat.h and the thing would be legal? This would mean adding something like #define ALLOC_COMPAT_LEGACY (or a better name) so that fglrx can see whether it needs to call fgrlx_alloc_user_space() at build time.17:17
smbNo, not changing anything in the normal kernel code. This should go into the fglrx code (the part that is gpl)17:18
tseliotsmb: this is what they currently do in fglrx:17:21
tseliotvoid* ATI_API_CALL KCL_IOCTL_AllocUserSpace32(long size)17:21
tseliot{17:21
tseliot    return compat_alloc_user_space(size);17:21
tseliot}17:21
apwand they do that in non-GPL file right ?17:21
tseliotyep17:21
apwbut they ahve a GPL file, so change that to fgrlc_alloc....(size)17:21
apwand add an identicle wrapper to the GPL file17:21
apwas i say, the separation is pointless17:22
apwhallyn, kernel for testing is at: http://people.canonical.com/~apw/lp641320-maverick/17:23
apwtseliot, do u mumble ?17:24
tseliotapw: yep but I need to connect the microphone17:24
apwmight be easier to talk17:24
tseliotapw: right but my microphone doesn't seem to be detected...17:27
* tseliot blames it on pulseaudio17:28
MTecknologyIs there a ureadahead module in the ubuntu version of the kernel that's required to boot - even if you don't have ureadahead?17:30
tseliotapw: ok, it works now, let's talk17:34
tseliotapw: where shall we talk?17:37
apwwe are in cafinated conversation ... under Kernel17:38
smbtseliot, kernel teams caffeinated conversation17:38
tseliotsmb, apw: ok, I'm there17:39
tseliotapw: can you hear me?17:43
smbHe cannot17:43
tseliotoh17:43
smbIn fact none of us. :)17:43
tseliotok, let me reconfigure mumble17:43
tseliotsmb, apw: now it's telling me that my password is wrong. I'll give up on mumble for now.17:47
tseliotapw, smb: were you suggesting that I define the function in the GPL file and export the function?17:47
tseliotthe fgrlx_alloc_user_space() function that is17:48
smbRight, you do it in the GPL file and export it (or link) it to the non-gpl file17:48
tseliotok, I see what you mean now17:49
tseliotthanks17:49
tseliotsmb, apw: thanks a lot for your help17:56
smbnp :)17:56
hallynapw: that kernel is good17:58
apwhallyn, thanks can you update the bug pls17:58
hallynapw: done, thanks18:00
hallynthough now, periodically the x display just hange.  right now i'm typing typing typing and not seeing anything, but i'tll suddenly just catch up  maybe18:05
ogasawaraapw: http://pastebin.ubuntu.com/495420/18:19
ogasawaraapw: http://pastebin.ubuntu.com/495429/ - updated revision18:39
Sarvattwould something like this work for all of these vaio F series that need i8042.nopnp? http://sarvatt.com/downloads/patches/vaio-vpcf-i8042-quirk.patch18:54
SarvattVPCF1290X VPCF126FM VPCF12S1E VPCF12M1E VPCF121FD are the models i've found so far needing it18:56
mjg59Given that Windows uses pnp to identify i8042 devices, that seems very much like the wrong fix18:57
Sarvattmjg59: thanks, it was a shot in the dark. it looks to be all VPCF12xxx devices, VPCF11xxx that hallyn has doesn't need the quirk to have the touchpad working19:08
mjg59Sarvatt: What's the bug number for this?19:08
mjg59Sarvatt: And does it have dmesg in both cases?19:08
Sarvattthere are a whole rack of bugs i'm noticing now that i'm looking and haven't condensed them yet, one sec i'll get you a list. they all have this in dmesg19:09
Sarvatt[    1.377980] PNP: PS/2 Controller [PNP0303:PS2K] at 0x60,0x64 irq 119:09
Sarvatt[    1.377982] PNP: PS/2 appears to have AUX port disabled, if this is incorrect please boot with i8042.nopnp19:09
mjg59Awesome19:10
mjg59Sarvatt: Need acpidump as well19:10
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/63663819:10
ubot2Ubuntu bug 636638 in linux (Ubuntu) "Touchpad is not detected on Sony VPCF126FM (affects: 1) (heat: 848)" [Undecided,New]19:10
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/64116919:11
ubot2Ubuntu bug 641169 in linux (Ubuntu) "alps touchpad sony vaio recognized, but not working (affects: 1) (heat: 6)" [Undecided,New]19:11
Sarvatt^ that one has acpidump but no dmesg, he put his dmesg in another bug19:11
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/63821919:11
ubot2Ubuntu bug 638219 in linux (Ubuntu) "Touchpad does not work on Sony Vaio VPCF12M1E (affects: 1) (heat: 1692)" [Undecided,New]19:11
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/63684219:11
ubot2Ubuntu bug 636842 in linux (Ubuntu) "Touchpad not found on Sony Vaio VPCF12S1E (affects: 1) (heat: 6)" [Undecided,New]19:11
Sarvattsorry for the spam19:12
mjg59Sarvatt: I think 641169 is different19:12
Sarvattit is, kind of, we were working through that with him in #ubuntu-devel and he was hitting 2 bugs at once19:12
Sarvatthe needed the fix for that bug + i8042.nopnp to actually work19:12
mjg59Which one did you say had acpidump?19:13
Sarvattoh shoot, getting my bugs mixed up19:13
Sarvatthttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/64132419:14
ubot2Ubuntu bug 641324 in linux (Ubuntu) "Sony Vaio touch pad is not working (affects: 1) (heat: 10)" [Undecided,New]19:14
Sarvattlet me ask these people for acpidumps :)19:14
Sarvatthttp://launchpadlibrarian.net/55810189/vaio_bug.txt 19:15
mjg59Interesting. That should definitely be picked up.19:17
mjg59There's a PNP0F13 device.19:18
mjg59But it's got an invalid _HID19:18
mjg59Maybe we're ignoring it in that case19:18
mjg59Sarvatt: My suspicion is that this is an issue in the acpipnp parser19:20
mjg59Sarvatt: Bet http://fpaste.org/NDs1/ will fix it19:21
mjg59Or, at least, will result in it crashing in some entertaining way19:21
apwclap4ham19:21
Sarvatti'll try to condense these bugs and submit a bug to b.k.org19:21
mjg59apw: ...19:22
Sarvattoh, nice19:22
apwheheh ...that poor password 19:22
apwthats why i have a different screen saver password to anything useful :)19:22
mjg59Sarvatt: It certainly looks like we stop parsing acpipnp devices if there's an invalid HID, and this HID is certainly invalid19:22
apwdone that twice this week already :)19:22
ckingdoh19:22
mjg59It's supposed to be three letters followed by four hex digits. Instead it's SNYALP001219:23
mjg59Thony19:23
apwits only my screen lock password, thats why it has to be different19:23
=== ivoks is now known as ivoks-afk
mjg59Sarvatt: http://marc.info/?l=linux-acpi&m=127563868423035&w=219:36
Sarvattmjg59: \o/ thank you for looking at it and the heads up on that patch19:38
* ogasawara lunch20:11
jjohansen-> lunch20:34
=== bjf is now known as bjf[afk]
=== mdeslaur_ is now known as mdeslaur
robbiewogasawara: regarding the Kernel Freeze Exception, just cut and paste that email into the bug comment...that should be enough22:02
ogasawararobbiew: you're reading my mind, doing that right now22:03
robbiew;)22:03
robbiewI figured I didn't need to say it, but didn't want you thinking we needed separate bugs for each bugfix or something nuts like that :)22:03
ogasawararobbiew: bug 64161822:05
ubot2Launchpad bug 641618 in linux (Ubuntu) "Maverick Kernel Freeze Exception (affects: 1) (heat: 10)" [Undecided,New] https://launchpad.net/bugs/64161822:05
ogasawararobbiew: will respond with the bug# in email to keep everyone informed22:05
robbiewogasawara: cool..thnx22:05
=== Daviey_ is now known as Daviey

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