/srv/irclogs.ubuntu.com/2010/08/03/#ubuntu-kernel.txt

komputesSarvatt: awesome, thanks00:31
komputesSarvatt: ATI will show 'drm'?00:32
Sarvattati/intel have drmfb's nouveau only has KMS00:32
komputesah yes - [drm] radeon defaulting to kernel modesetting.00:32
Sarvattits looking for nouveaufb or drmfb00:32
komputesSarvatt: sorry, confused. again from the beginning.00:33
komputes/proc/fb contains a list of frame buffer devices, with the frame buffer device number and the driver that controls it00:34
Sarvattyeah if nouveaufb or any of the drmfb's are in there it's using KMS00:34
komputesSarvatt: and just to be clear those drmfb's are inteldrmfb, nouveaufb, radeonfb00:35
Sarvattnouveaufb radeondrmfb or inteldrmfb00:35
komputescool, thanks Sarvatt 00:35
Sarvattno problem, also I forgot but vmwgfx is svgadrmfb as well00:40
komputesSarvatt: which are?00:47
rippsCan someone please mentor me with l-b-m? I want to add an updated wacom module fix problems with new wacom bamboo tablets. I've already discussed this and submitted a proposal on the mailing list, but nobody has responded. See bugs #568064 and #60627801:45
ubot2Launchpad bug 568064 in linux (Ubuntu) "Wacom new bamboo models are not recognized in Lucid (affects: 19) (heat: 101)" [Undecided,Confirmed] https://launchpad.net/bugs/56806401:45
ubot2Launchpad bug 606278 in linux-backports-modules-2.6.35 (Ubuntu) "Add linux-backports-modules-input (affects: 6) (dups: 1) (heat: 42)" [Undecided,New] https://launchpad.net/bugs/60627801:45
rippsSince I can see any sign of anybody working on this, I wanted to know if somebody can help me write a patch instead. I've taken a look at the l-b-m source, but it's so complicated I can't really make much sense of it.01:46
ripps*don't see any sign01:46
ionIt might be nice to have CONFIG_COMPACTION on.01:49
rippsI'm not some noob with packaging, I was just hoping somebody give me some hints or guidance on how to start adding a new component to l-b-m01:51
Sarvattripps: does l-b-m make sense for something thats not a backport? what's wrong with your dkms package?02:41
rippsSarvatt: nobody would accept it. MOTU's said to try and get it into Debian, and Debian said that it was just working around a problem with the kernel. Problem is, the linuxwacom project isn't updating their wacom kernel source because apparently their refactoring it or something.02:42
rippsAfter discussing it here, I was advised to propose an addition to linux-backport-modules. But apparently, nobody wants to help me get in there, either.02:44
tjaaltonany known regressions in the current lucid kernel? I 07:21
tjaaltonhrm07:21
tjaaltonI'm unable to do a full install (~2500 packages) anymore, since dpkg sees some packages are corrupt (same size, different md5sum as on the archive)07:22
tjaaltonor when unpacking some config stubs in /tmp are missing etc07:23
tjaaltonmaybe I should try with ext3 to rule it out07:23
tjaaltonah, actually.. the installer image is the release one :)07:30
tjaaltonthe one that worked was from March07:30
tjaaltonthough the corruptness happens on an installed system as well, and that has the latest kernel07:34
apw/usr/share/doc/debian-policy/upgrading-checklist.txt.gz08:47
erahi ogasawara, is anything being done to implement this? https://bugs.launchpad.net/ubuntu/+source/ndiswrapper/+bug/590090/comments/708:59
ubot2Ubuntu bug 590090 in ndiswrapper (Ubuntu) (and 1 other project) "package ndiswrapper-dkms 1.56-1 failed to install/upgrade: ndiswrapper kernel module failed to build (affects: 40) (dups: 3) (heat: 206)" [Medium,Confirmed]08:59
apwif ! git remote | grep FOO >/dev/null; then echo NO; fi10:32
=== amitk is now known as amitk-afk
=== amitk-afk is now known as amitk
=== yofel_ is now known as yofel
tumbleweedcan anyone suggest things to try and get useful debug information? Got a user who's USB controller seems to hang ~once a day (leaving him without working keyboard and mouse). Nothing interesting in kernel/X logs, and lsusb hangs on open("/dev/bus/usb/002/005")12:33
tumbleweednm that, after a while, starteg tetting task blocked messages in kernel logs12:34
=== BenC____ is now known as BenC
Ejdesgaard_hi, is there any chance that https://bugzilla.kernel.org/show_bug.cgi?id=16315 will be backported to 10.04 LTS?13:29
ubot2bugzilla.kernel.org bug 16315 in i386 "icebp (opcode 0xf1) no longer causing a SIGTRAP, breaks Wine" [Normal,New]13:29
smbEjdesgaard_, If the patch goes upstream as a stable patch it will come back as soon as upstream stable picks it up13:30
JFolag, the picture is up on my Facebook15:07
=== jjohansen is now known as jj-afk
JFosent to you in e-mail15:09
=== bjf[afk] is now known as bjf
=== sconklin-gone is now known as sconklin
lagJFo: That's awesome!15:30
JFo:)15:30
lagJFo: http://people.canonical.com/~ljones/lastsupper/15:40
JFonice!15:47
JFonot a bad approximation15:48
lagIt's there or there abouts 15:55
lagSomeone is facing completely the wrong way and I'm a few degrees off15:55
lagOverall I think we did okay :)15:55
vanhooflol!15:56
vanhoofyou guys werent kidding around :D15:57
Ejdesgaard_smb, it was included in .35-rc415:57
bjf##15:58
bjf## Kernel team meeting in two hours15:58
bjf##15:58
ogasawaraera: it seems that bug was recently resolved in the last few hours by the package maintainer16:14
ogasawaraera: I'm not opposed to going with their plan B in the future and completely dropping ndiswrapper from the kernel but that's a discussion that needs to probably take place on the kernel-team mailing list16:18
Riddelljcrigby: has the binary package names in the linux-linaro upload been OKed by the kernel team?16:31
tgardnerRiddell, its been uploaded, but is awaiting acceptance by an archive admin16:32
jcrigbyRiddell: I don't know.  What constitutes approval.16:32
Riddelltgardner: why do you think I'm asking :)16:32
Riddelljcrigby: tgardner's blessing? :)16:33
tgardnerRiddell, random curiosity?16:33
tgardnerRiddell, slangasek said he had some concerns, but he's at debconf16:33
Riddellwhy do some of the binary packages have "linaro" in the name and some go for the -1000 suffix?16:34
tgardnerRiddell, um, not supposed to. I guess I'd better look closer. I only looked at the control file16:34
jcrigbyI tried to follow the abstracted debian model.  May have messed up.16:35
Riddellwell it looks deliberate I presume there's a reason why that's the best way to do it16:35
jcrigbytgardner:  I removed a bunch of entries from the control file yesterday.  It now looks like the ti-omap4 control file.16:35
Riddelle.g. linux-headers-2.6.35-100016:35
tgardnerRiddell, whats the URL for looking at the generated packagesd?16:35
Riddelltgardner: there are no generated packages, I'm reviewing the source16:36
jcrigbyI think you will see the same convention in the ubuntu kernel16:38
jcrigbywithout the 100016:38
tgardnerRiddell, according to debian/control I think the package names are correct. it follows the same model as other kernel topic branches16:38
Riddellyeah that's the ABI number16:38
Riddellbut it seems curious to namespace some packages with "linaro" and some with <mega big ABI number>16:39
smbEjdesgaard_, Is that definitely needed for 2.6.32 (10.04 LTS) as the patch seems to have been sent for 2.6.33.y specifically16:39
tgardnerRiddell, oh, you mean the 'linaro' part? I guess he's using it to distinguish these kernel binaries from the omap4 packages that are already in the archive.16:40
Riddelltgardner: yeah that makes sense.  bumping the ABI to 1000 is what seems strange to me16:41
tgardnerjcrigby, so, do you want to respin with new binary package names?16:42
tgardnerRiddell, we use the ABI number to distinguish between kernel topic branches16:42
tgardnerotherwise we'd have binary package name collision16:42
jcrigbytgardner:would be glad to if someone tells me what to change them to16:42
RiddellI'd have thought e.g. linux-linaro-headers-2.6.35-1 would make more sense16:42
tgardnerRiddell, its a restriction of the installer, which insists on the linux-header* pattern16:43
jcrigbyahh16:43
tgardnersimilarly for linux-image*16:43
Riddelltgardner: ah, I knew there'd be a perfectly rational explanation16:43
tgardnerwell, rational is a stretch :)16:43
jcrigbyon a different matter, I changed the control yesterday and removed some stuff and made Architecture: armel for everything16:45
jcrigbyso the build system only tries to build on armel16:45
Riddelljcrigby: in that case should I reject the current upload and save the non-arm buildds the hassle of building something they don't want?16:46
tgardnerjcrigby, I'm not sure you can do that. Some of the packages have to be constructed on the default arch (i386), e.g., the headers _all.deb16:46
jcrigbytgardner:I made it look like the ti-omap4 control16:47
jcrigbyis that known good?16:47
tgardnerRiddell, why don't you go ahead and reject this upload. I16:47
tgardnerI'll work with jcrigby to fix the control file issues16:47
jcrigbytgardner:thanks16:49
Riddellok rejected, ping me when you reupload if you want a quick review16:49
tgardnerRiddell, later today I think. Thanks for your help.16:50
jcrigbytgardner:what is best for you.  Do you want to just send me a patch?16:51
tgardnerjcrigby, send a pull request with your current bits16:52
jcrigbywith the ti-omap4 changes?16:52
jcrigbystyle changes that is16:52
tgardnerjcrigby, yep16:52
jcrigbyok, I notice one thing that your comment above sheds some light on:16:53
jcrigbyPackage: linux-headers-2.6.35-100016:53
jcrigbyArchitecture: armel16:53
jcrigbySection: devel16:53
jcrigbyPriority: optional16:53
jcrigbyDepends: ${misc:Depends}, coreutils | fileutils (>= 4.0)16:53
jcrigby#Provides: linux-linaro-headers, linux-linaro-headers-2.616:53
jcrigbyDescription: Header files related to Linux kernel version 2.6.3516:53
jcrigby This package provides kernel header files for version 2.6.35, for sites16:53
jcrigby that want the latest kernel headers. Please read16:53
jcrigby /usr/share/doc/linux-linaro-headers-2.6.35-1000/debian.README.gz for details16:53
jcrigbyexplains the commented out Provides:16:54
tgardnerjcrigby, correct16:55
apwbjf, is there a meeting today?17:07
bjfapw, yes17:07
apwahh i see your 2 hour warning now17:07
smbsconklin, bjf Seems there is no need to start a new release on Lucid, that was already done17:14
sconklinsmb: yes, I'm just applying the patches. I'll start with the things we wanted on the short list17:15
smbsconklin, ok17:15
smbsconklin, We should sync on the writeback patches. I got the feeling there is a patchset you got and one I have done17:17
sconklinsmb let me check what I have and see if they're in my public repo17:18
smbbug 64361717:18
ubot2smb: Error: Bug #643617 not found.17:18
smbhm17:18
smbbug 54361717:18
ubot2Launchpad bug 543617 in linux (Fedora) (and 3 other projects) "Unmount of an fs with dirty cache buffers causes pathological slowdown (affects: 11) (dups: 2) (heat: 101)" [Unknown,Unknown] https://launchpad.net/bugs/54361717:18
smbsame as bug 58509217:19
ubot2Launchpad bug 585092 in linux (Ubuntu) "giant IO delays (affects: 1) (heat: 22)" [Medium,In progress] https://launchpad.net/bugs/58509217:19
sconklinsmb: yes, there's already a branch "bug bug543617" in my public repo that I used to build the test kernel for that bug17:20
sconklinoops, branch name is simply bug54361717:21
smbsconklin, Let me check what is there. Cause I have been working on that and probably got a different set17:21
smbsconklin, My set is there (http://kernel.ubuntu.com/git?p=smb/linux-2.6.32.y.git;a=shortlog;h=refs/heads/writeback) and looks like being a superset of yours. I am currently trying to get Jens Axboe look at those to get them backported to stable upstream. There is a set for 2.6.34.y as well17:25
smbsconklin, Have you sent your patches for review already. I cannot remember having seen that17:25
sconklinas I recall, they were sent for review weeks ago, and I just picked them up. Let me check17:26
sconklinsmb: [1/2] writeback: fix WB_SYNC_NONE writeback from umount17:27
smbI was holding back because I at least wanted to have some feedback on them before. These series has been taking a lot of time to mature upstream17:27
sconklin[2/2] writeback: ensure that WB_SYNC_NONE writeback with sb pinned is sync17:28
smbOk, maybe my bad not deleting those17:28
sconklinsmb: OK, I just grabbed them and built a test while you were out sick because rtg asked about them17:28
=== jj-afk is now known as jjohansen
smbsconklin, Please don't pick them for applying now17:28
sconklinsmb: they were still active in patchwork also17:29
sconklinok, I won't pick them17:29
smbRight, I should have marked them as superseeded 17:29
smbThanks. Unfortunately there was a time in between when I knew the ones we had were not good but upstream was not fixed yet. And not to forget I did not set them as rejected17:30
bjf##17:31
bjf## Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting17:31
bjf##      agenda: https://wiki.ubuntu.com/KernelTeam/Meeting17:31
bjf##17:31
smbsconklin, The set now seems to be ok, but as you can see in that tree its a huge set.17:32
smbsconklin, The only thing we need to remember is to revert the workaround when we apply the writeback set17:33
sconklinsmb: I'll apply the graphics fixes for the two issues we have patches for, then the writeback patches, then the stable update, OK?17:33
smbsconklin, Leave out the writeback patches completely. I want to get feedback on the backport first and then do another round of sending those to the kt-mailing list17:35
sconklinsmb: ok17:35
vanhoofsconklin: i assume you need that sru sooner than later for the x201 display bug?17:36
sconklinvanhoof: yes, I'd hate for it to end up being the gating factor17:36
vanhoofmanjo: ^^ :D17:36
manjoyes building kernel with patch now 17:37
manjoI will send it to SRU as soon as I am done 17:37
vanhoofmanjo: ok, i can re-test if you'd like17:37
manjoyep that will be great!17:38
sconklinvanhoof, manjo: also, people have been ignoring the SRU requests or not completing them properly. We've been fixing them up without complaining, but I'm going to start bouncing them until they are correct.17:38
smbsconklin, I removed the writeback parts from patchwork for now so there won't be confusion on that part17:39
sconklinsmb: ok, but I think I acked them on the mailing list, so you'll want to follow up on that17:40
smbsconklin, There is another one to disable CONFIG_LGUEST for hardy lpia which went in as part of the security update to fix the build failure17:41
smbsconklin, I probably should post a message there, too17:41
manjoIs there an issue with tangerine ?18:29
manjomanjo@tangerine:~$ dchroot -c lucid-amd6418:29
manjoW: Group ‘sbuild’ not found18:29
manjoE: Access not authorised18:29
manjoI: You do not have permission to access the schroot service.18:29
manjoI: This failure will be reported.18:29
manjomanjo@tangerine:~$ 18:29
manjoI was able to dchroot just couple of hrs ago18:29
JFo<-starving... headed to lunch18:29
manjotgardner, ^^ any idea ?18:31
tgardnermanjo, I guess you're not special.18:31
manjo?18:31
bjftgardner, i think it's because he *is* "special"18:32
tgardnermanjo, just kidding. lemme check18:32
manjobjf, thanks18:32
tgardnerapw, smbgot some oops on tangerine.18:33
* manjo brb18:34
tgardnersmb, ^^ need to reboot.18:34
smbHm, just for compiling six kernels in paralell18:34
smbok18:34
apwtgardner, stuck in writeback ... smb could that be your writeback issue you had patches for ?18:34
tgardnershall we try the 2.6.35 kernel?18:34
bjfogasawara, you want me to leave "delta-review" on the agenda?18:34
smbtgardner, apw Let me have a quick look18:34
ogasawarabjf: I'd say take it off18:35
=== bjf changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Maverick Kernel Version: 2.6.35 || Ubuntu Kernel Team Meeting - August-10 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
ogasawarabjf: the last big item is to review if any of our ubuntu drivers need updating (which I suspect they won't)18:36
bjfogasawara, it's gone18:36
sconklinsmb: do we put the buglink for the stable update bug in every patch that's part of a stable pile?18:36
smbsconklin, yes. maint-modify-patch18:37
sconklinok, doing that now18:37
smbtgardner, apw Seems the process that was stuck first was returning later. So it might well be the slow writeback problem18:37
bjfapw, you still have two agenda items do you want to keep them?18:38
tgardnersmb, lets try the LTS backport kernel for awhile.18:38
simarI want to triage bugs for kernel at first. So I'm going to read documents of Ubuntu Kernel Bug triaging ..18:38
apwbjf, the misc one is likely redundant18:39
smbtgardner, as long as we can switch back to the lts kernel later, ok. Cause that machine is good for running stress io tests18:39
smbtgardner, I am off it again, so you can reboot if you like18:40
* smb is gone18:43
manjotgardner, please let me know when tangerine is back18:45
apwsimar, sounds great for us ...18:50
manjosimar, talk to JFo he should be able to help you as well 18:51
manjosimar, he leads the bug triaging effort 18:52
manjotgardner, looks like tangerine is back... can I use it ?18:56
manjoah same issue cannot dchroot ...  18:57
* manjo getting lunch will be back soon 18:57
tgardnermanjo, should be OK now. you'll need to logout first.18:58
=== bjf is now known as bjf[food]
* ogasawara lunch20:33
* jjohansen lunch too20:33
=== bjf[food] is now known as bjf
sconklinmanjo, vanhoof: The graphics patches you wanted are now in the lucid repo22:06
* manjo sconklin beer++22:06
bjfogasawara, sconklin just pushed some patches to the lucid repo is there anything that will automatically build that (some kind of pre-proposed / stable crack of the day)?22:15
ogasawarabjf: hrm, I can't remember if smb's pre-proposed in the kernel-ppa builds automatically22:15
tgardnerogasawara, bjfAFAIK it does22:16
ogasawarabjf: it certainly should be easy enough to make it do so automatically as apw does the same for the latest maverick tip22:16
bjfogasawara, that's what i thought, was just wondering if we already did it22:16
bjftgardner, i guess we'll know in a bit then22:17
manjolatest maverick iso i386 from cdimage current does not seem to boot ... 22:19
manjoI recall apw posted something in this regard wrt to usb keys .. anyone recall ? 22:19
ogasawaramanjo: bug 608382 ?22:21
vanhoofsconklin: awesome!22:21
ubot2Launchpad bug 608382 in usb-creator (Ubuntu) (and 1 other project) "USB images of Maverick CDs fail to boot with -- Error: Unkown keyword in configuration file (affects: 13) (dups: 1) (heat: 70)" [High,New] https://launchpad.net/bugs/60838222:21
manjolooking 22:21
manjoogasawara, thanks a ton 22:23
tgardnerbjf, kernel-ppa@zinc:~$ crontab -l22:24
tgardner# m h  dom mon dow   command22:24
tgardner0 *    *   *   *   $HOME/buildscripts/mainline-build/kernel-version-map >$HOME/public_html/info/kernel-version-map.html.new && mv $HOME/public_html/info/kernel-version-map.html.new $HOME/public_html/info/kernel-version-map.html22:24
tgardner0 09    *   *   *   USER=kernel-ppa $HOME/kteam-tools/mainline-build/mainline-trigger >>$HOME/logs/mainline-trigger 2>&122:24
tgardner5  *    *   *   *   USER=kernel-ppa $HOME/kteam-tools/mainline-build/cod-execute >>$HOME/logs/cod-execute 2>&122:24
tgardner@hourly /srv/kernel.ubuntu.com/www/scripts/gitfind > /dev/null 2>&122:24
manjoogasawara, if you are channel operator can you add "10.10 USB boot issues see https://launchpad.net/bugs/608382 for workaround" ? 22:25
ubot2Ubuntu bug 608382 in usb-creator (Ubuntu) (and 1 other project) "USB images of Maverick CDs fail to boot with -- Error: Unkown keyword in configuration file (affects: 13) (dups: 1) (heat: 70)" [High,New]22:25
=== ogasawara changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Maverick Kernel Version: 2.6.35 || Ubuntu Kernel Team Meeting - August-10 - 17:00 UTC || If you have a question just ask, and do wait around for an answer! || 10.10 USB boot issues see https://launchpad.net/bugs/608382 for workaround
=== sconklin is now known as sconklin-gone
apwogasawara, bjf, sconklin-gone, the pre-proposed engine builds all of the releases, assuming they have non-ignored commits following a release23:23
bjfapw, yes, i was looking at the scripts and sort of decided that23:24
bjfapw, if i understand it, they should kick off 0900 UTC23:24
apwbjf yes indeedy23:25
apwbjf with the new queuing ability we could reschedule the pre-proposed to a better time independantly if needed23:25
apwnight23:26
bjfg'night23:26
=== bjf is now known as bjf[afk]

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