/srv/irclogs.ubuntu.com/2008/03/18/#ubuntu-kernel.txt

=== clever_ is now known as clever
alex_joniI notice that the headers deb created for a x86 32-bit kernel, has a bustem symlink in it: include/asm points to asm-i38601:18
alex_joniany ideas what I should check?01:18
=== lamont` is now known as lamont
krautmoin08:16
=== \sh_away is now known as \sh
aboganichuck_: Seem to me that this commit (in mainline)  87d034f3139b5f0d93df2ba58f37d6f2c2c7eeb6  should be added in Hardy.09:15
pwnguinso is the kernel team the best place to ask about initramfs-tools scripts?09:28
aboganiIt is possible but unlikely.09:31
pwnguinwhat on earth is the resume script waiting five seconds for?09:32
aboganiI suggest you to ask on #ubuntu-devel.09:32
pwnguinok then09:33
pwnguinis the ML a better place to watch for kernel work? this place always seems so dead09:39
tonfahi, I'm running gutsy and while debugging something with vanilla .25-rc6 I get dbus errors when logging in in gdm10:08
tonfais this some known issue ?10:08
tonfa(the error is something like "could not connect to /tmp/dbusXXXX")10:08
aboganitonfa: Yes10:14
tonfado you have some pointer ? (is it in launchpad ?)10:15
aboganiBug #14694610:24
ubotuLaunchpad bug 146946 in gnome-control-center "[gutsy] Gnome settings daemon randomly does not work" [Medium,Incomplete] https://launchpad.net/bugs/14694610:24
tonfaok, thanks10:27
tonfaI'll try restarting next time I boot this kernel10:27
tonfathat's weird that it (almost) always happens with .25-rc6 and never with gutsy's kernel10:28
pwnguintiming issues are like that10:29
tonfayup, I'm reading the bug report10:29
tonfathanks a lot for the pointer :)10:29
=== \sh is now known as \sh_away
=== \sh_away is now known as \sh
=== chuck_ is now known as zul
BenCtjaalton: any idea why lrm is not loading nvidia-legacy for me at boot, when I should be (and have always been) using nvidia-new12:24
BenCin fact, I have nvidia-glx-new package installed12:25
Ngwould it be reasonable to target bug 197929 for beta?12:29
ubotuLaunchpad bug 197929 in linux "Backlight adjustment no longer works on Thinkpad X61s" [Medium,Triaged] https://launchpad.net/bugs/19792912:29
Ng(also affects X300)12:30
aboganizul: Seem to me that this commit (in mainline)  87d034f3139b5f0d93df2ba58f37d6f2c2c7eeb6 about Xen should be added in Hardy.12:33
zulabogani: gitweb url? 12:34
BenCNg: we can give it a try12:36
aboganizul: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=34f10fc9886450c2e8a336f7022805c4a73e10f112:37
zulabogani: thanks12:37
aboganizul: Hope this helps.12:38
zulabogani: we dont use paravirt xen for hardy :)12:38
zulabogani: for ibex probably :)12:38
aboganizul: Opsssss :-)12:38
aboganizul: What is virt tech supported by Ubuntu Server Team? KVM?12:39
zulkvm12:39
NgBenC: I'm not sure what the patch was supposed to do, but it's definitely breaking backlight on my laptop, I booted -10 and the backlight works12:40
BenCNg: hmm, ok12:40
BenCtjaalton: oops, I mean it's not loading nvidia-new for me, it's loading nvidia-legacy instead13:20
=== LifeHacker is now known as tuxmaniac
amitkBenC: are we still uploading for Beta?13:50
mjg59#147087 is kind of silly13:50
BenCbug #14708714:24
* BenC kicks ubotu14:24
BenCbug #14708714:24
ubotuLaunchpad bug 147087 in linux "No sound on Aluminium iMac with PCI ID 8086:284b" [Medium,Confirmed] https://launchpad.net/bugs/14708714:24
johanbrIs there any chance the one-line patch from bug #39414 could be applied? Without this patch, many people won't be able to use bluetooth headsets.14:57
ubotuLaunchpad bug 39414 in linux-source-2.6.15 "syslog is flooded with messages after connecting bluetooth usb dongle" [High,Fix released] https://launchpad.net/bugs/3941414:57
aboganiUBUNTU: custom/rt: Disable toshiba_acpi, since it isn't compatible :-?15:29
BenCcking, amitk: ping16:02
ckinghi16:02
amitkping16:04
BenCOk, welcome to the kernel team IRC meeting16:04
BenCFor those that don't know, meeting information is available here: https://wiki.ubuntu.com/KernelTeam/Meeting16:05
BenCSince we are closing in on release, and are under kernel freeze, we are going to keep this short so everyone can get back to work16:05
BenCcking: Can you start off with your status and current focus16:05
ckingYep.  Been looking a various kernel bugs, ranging from the trivial patch to the more perplexing.16:06
ckingFor example, usplash messing up vgacon driver colors and causing blanking not to work for all colors in the palette. 16:07
BenCcking: ok...you said earlier that you were also moving on to looking after the boot loader for intrepid?16:08
ckingYep. I'm getting familiar with the isolinux, grub and so forth.16:08
BenCGood, be glad to see what we can do with grub2 (if anything) for intrepid16:09
BenCcking: thanks16:09
BenCamitk: on to you...16:09
ckingOK. 16:09
amitkbeen testing out some hardware for the ubuntu Mobile project16:10
amitkintegrating drivers for them too16:10
amitkI hope to push out a preliminary Intrepid tree with all the sauce patches next week16:10
BenCamitk: for ume or kernel in general?16:10
BenCthe intrepid tree that is16:11
amitkkernel in general - we will move the lpia out of the normal kernel tree though16:11
amitkas agreed at the kernel sprint16:11
BenCamitk: excellent...are you working on that tree in tandem, or will that come later?16:12
BenCthe lpia tree16:12
amitkBenC: tandem. The lpia tree will follow the main kernel tree closely, only have different checkpoints for uploading than the kernel tree.16:13
amitks/checkpoints/schedule16:13
BenCamitk: Are you removing most of the (unneeded) sauce patches for lpia? e.g. I wouldn't think it would need DSDT-from-initramfs loading16:13
amitkBenC: true, those don't need to be in the lpia tree.16:14
BenCamitk: ok, great...anything else of note?16:14
amitkthat's it from me.. thanks16:15
BenCamitk: thanks16:15
jayamitk: How will this affect my integration of moblin patches to the hardy-ume?16:15
amitkjay: it won't. Hardy tree will continue to be maintained as-is, with you and I doing special uploads to the mobile PPA16:16
jayamitk:ok16:16
amitkIntrepid's new kernel is not yet chalked out in the current Ubuntu Mobile plans16:17
BenCGood thing about the planned separation is that moblin could potentially use an entirely different kernel version in intrepid than we are for mainline16:17
BenCIOW, it could use 2.6.25 instead of our planned 2.6.26, so it can remain at a stable ABI for much longer during the development cycle16:18
BenCbut that's a discussion for UDS16:18
amitkBenC: very true. This will be discussed at UDS16:18
BenCOk, moving on to bugs for hardy16:18
BenCThe kernel team has discussed some basic guidelines for patches/fixes going into the kernel between now and release...16:19
BenCFor starters, the current kernel in the archive is what is planned for beta, barring any major regressions showing up (which I see as unlikely)16:19
mjg59BenC: Where?16:19
BenCmjg59: where what?16:20
mjg59Where was it discussed?16:20
BenCmjg59: on our phone call just before this meeting...and I'm about to outline those guidelines now16:20
mjg59Phone call?16:20
BenCYes, we have a conference call once a week just before the IRC meeting16:20
BenCmostly to discuss NDA issues that can't be discussed here16:21
mjg59Uh.16:21
mjg59But also to discuss bug policies?16:21
BenCThese policies aren't any different than what we've had in past releases16:21
BenCjust noting them now to make sure everyone understands them16:21
mjg59If you're defining the kernel team as the set of people employed by Canonical, I think you're missing the point16:22
BenCJust the bar for a patch getting in now after kernel freeze is very high...and that needs to be pointed out16:22
BenCmjg59: I misspoke...we didn't "define" these policies on the call, we simply reviewed the ones we already have in place16:23
BenCmjg59: we discussed how they were different than the normal policies during the heavy development cycle16:23
BenCIOW, we are in kernel freeze, and only have one more planned upload16:23
mjg59No, the kernel team didn't. The subset of the kernel team involved in this phone call did.16:23
BenCI don't see it as a problem to let my employees know what these policies are, especially considering most of them are new16:24
BenCI also don't think I have to do it in public16:24
BenCespecially since the same policies will be discussed in public16:24
BenCand especially since they haven't changed, they are just being reiterated at a time when they are pertinent16:25
mjg59No, that's not the point I'm mkaing16:25
BenCI don't really see a valid point, to be honest16:25
mjg59You're saying that the kernel team discussed this. That's only true if the kernel team is the set of people who work for Canonical.16:25
BenCExcuse me then, the Canonical Kernel Team discussed this16:26
mjg59Which was not my understanding of how development worked.16:26
BenCand now I am discussed it with the Ubuntu Kernel Team16:26
BenC*discussing16:26
mjg59Ok16:26
BenCmjg59: is that clarification better?16:26
mjg59Yes16:26
BenCGood, so let's move on...16:27
BenCThe basic points of our current bug policy is that we will mainly focus on bugs that prevent users from booting/installing Ubuntu16:28
BenCBugs that fall into this category are mainly graphics and storage related, but generally covers networking as well16:28
BenCOther bugs will either be deferred to 8.04.1 point release, or for 8.10, depending on the bug16:29
BenCExceptions to this can occur, but are not likely...basis for exceptions will be the estimated number of people affected by the bug, and the complexity of the fix (IOW, the trivial fixes with least chances of regression may be considered)16:30
BenCWe only have one more _planned_ kernel upload, as per the kernel release schedule (linked to a google cal from KernelTeam wiki)16:30
BenCAnd just for clarification, these policies, and the kernel release schedule itself were discussed at prior UDS's with community members16:31
BenCAre there any questions concerning this policy?16:32
aboganiNo.16:33
BenCGreat...so now I'll just see if anyone has other items they would like discussed at this point...16:33
BenCNo takers? :)16:35
BenCOk, thanks everyone16:35
BenCMeeting adjourned16:35
amitkthanks16:35
ckingta16:35
alex_joniBenC: can I bug you for a couple of minutes? or should I rather wait till things settle down after beta?16:42
BenCalex_joni: depends on the nature of your bugging :)16:44
alex_joniasking for some pointers building a custom-flavoured kernel (along with headers, lum, lrm), and some other pointers on tracking a possible bug in make-kpkg16:45
BenCalex_joni: re: custom kernels/lum/lrm: Check wiki.ubuntu.com...we don't condone it though16:47
BenCalex_joni: re: kernel-package (make-kpkg), you're on your own, we don't use it or support it :)16:47
BenCalex_joni: best bet is to talk to the maintainer of that package16:48
alex_joniBenC: I started looking at the debian/rules way of building things16:48
alex_joniand I think the problem persists16:48
BenCalex_joni: that's preferred16:48
alex_jonibasicly the generated headers deb contains a broken asm link (points to asm-i386, not asm-x86)16:48
alex_jonibut it might be because of a bad incantation to debian/rules 16:49
alex_jonire: wiki.ubuntu.com, I understand.. already read most of the relevant thigngs, but it's not quite as accurate as I hoped16:50
alex_jonire: custom flavour: can't help it, we're using ubuntu as a base for machine control, so we need an ADEOS/IPIPE patch in the kernel16:50
aboganialex_joni: Can't you use -rt for that?16:51
alex_joniabogani: not at the moment16:51
alex_joni-rt needs to get way better for that16:51
alex_joniatm we're using 5-10 usec interrupts, -rt is a couple magnitudes worse16:52
alex_joni-rt is fine for servo controlling motors with custom hardware, but not for the cheap parport control16:52
alex_joniabogani: however -rt is getting way better, so I hope one day we can fully switch over16:52
zul.26 for ibex?17:45
=== thegodfather is now known as fabbione
_stijn_hey18:46
=== kylem_ is now known as kylem
=== asac_ is now known as asac
=== Traxer is now known as Traxer|on
=== Traxer|on is now known as Traxer
jeplerI want to build and distribute a custom kernel flavor (rtai) and be sure that I fulfill my GPL duties to distribute complete, corresponding source code.  The page https://help.ubuntu.com/community/Kernel/Compile didn't answer my questions about how to build a linux-source package or a debian source package.  What method should I use?20:01
johanbrIs there any chance the one-line patch from bug #39414 could be applied? Without this patch, many people won't be able to use bluetooth headsets.20:40
ubotuLaunchpad bug 39414 in linux-source-2.6.15 "syslog is flooded with messages after connecting bluetooth usb dongle" [High,Fix released] https://launchpad.net/bugs/3941420:40
johanbrThe patch disables eSCO, but that's a relatively minor loss compared to not being able to use your headset at all.20:41
=== Traxer is now known as Traxer|on
=== Traxer|on is now known as Traxer
tjaaltonBenC__: right, I think there's a bug report about it21:46
BenC__tjaalton: are you working on it? Seems important for beta22:10
BenC__brb22:10

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