/srv/irclogs.ubuntu.com/2006/06/12/#ubuntu-kernel.txt

WebMavenThis *could* have been fixed prior to Dapper's release.12:04
crimsun_lots of issues /could/ have been. Resource limits are problematic.12:05
WebMavenI'm very grateful that it is supposedly fixed now, but I won't stop worrying until I can verify it for myself.12:06
WebMavencrimsun_: sure, I understand. I also understand that the squeaky wheel gets the grease.12:07
WebMavenSo, I'm squeaking.12:07
WebMavenI'll try to squeak more quietly, thoguh.12:07
WebMaven'though'12:08
=== WebMaven goes back to patient and reflective contemplation for the next few days.
BenCWebMaven: First reported: 2006-06-03 12:28
BenCtwo days after release12:28
BenCthe dupes, did not contain enough info to triage the bug12:29
=== JaneW [n=JaneW@dsl-146-167-152.telkomadsl.co.za] has joined #ubuntu-kernel
infinityBenC: We build kernels for breezy-sparc because we always have?02:36
infinityBenC: sparc wasn't officially supported in breezy, but it was released (same as hppa and ia64, both of which built fine, BTW)02:37
BenCinfinity: will a security update be held back because of sparc FTBFS?02:37
BenCnot sure if we introduced anything in the last breezy update that would have caused that02:37
infinityBenC: If it can't be easily fixed, then I suppose not.  We only support amd64/powerpc/i386 on breezy.  That doesn't mean we shouldn't attempt occasionally to make sure the others work.02:37
zulno i dont think anything touched those files02:38
infinityBenC: Yes, it was FTBFS last time too, and I bounced you the log, you don't recall?02:38
infinity(You told me you'd fix it for the next update)02:38
BenCdamn, guess I forgot :)02:40
infinityLooks like the last one that built successfully was 10.2602:41
infinityAt least, that's the last one that's in the archive.02:41
zulhmm....should i try to fix it?02:41
infinityzul: I'd like it if someone did, but it's not the end of the world if no one does, I guess.02:42
infinityI just dislike dropping a security fix on the floor just because an arch is unsupported (unless it's WAY too much effort)02:42
zulill track a crack at it02:42
infinityLaunchpad should have a resonable source history here, if you need to track back through the changes, since this was pre-git:02:44
infinityhttps://launchpad.net/distros/ubuntu/+source/linux-source-2.6.1202:44
infinityI know that 10.26 is the last version in the archive.  I'll have to dig a bit to see if that was actually the last version to build correctly.02:44
infinityOkay, the first time I saw it fail was 10.32, since before that, Fabio was building sparc/security, not me.02:47
infinitySo, it broke bwteen 10.26 and 10.32 (not that helpful, I know, but I imagine the nature of the breakage won't make it that hard to track down which revision was responsible)02:47
mjg59BenC: How do you get a git tree on kernel.org?02:52
infinitySleep with Linus.02:53
infinity(again)02:53
mjg59I told him how to make his Mac work02:54
infinityThat may be close enough.02:57
BenCmjg59: email ftp-master@ftp.kernel.org I believe02:57
BenCor maybe just @kernel.org02:58
=== BenC forgets
mjg59You need a kernel.org address?02:58
mjg59Uh, account02:58
zulsorry i didnt realized i wasnt registered :(03:02
BenCmjg59: yeah, you'd get a kernel.org email, ssh account, and access to your own area(s) in the ftp tree03:15
BenCI'm not sure of their criteria, but I was like "hey biatch, I'm Ben Collins, give me an account foo"03:16
BenCand they were like "yeah dude, here ya go"03:16
zullol03:17
BenCwell, it went something like that :)03:17
=== BenC is doing a full warning-hunt on the 2.6.17 tree
BenCwe're getting way too many compiler and MODPOST (linker) warnings03:18
BenCand there's a lot of modules that cannot even load on smp machines, so I need to disable them03:18
zulBenC: you did an upload for dapper?03:37
BenCyeah03:54
zulcool03:58
zulill put up the diffs for breezy/hoary tomorrow morning unless if i can do the uploads myself03:59
zulanyays night night04:10
BenCdid you do anything besides the i387 for hoary?04:10
zulwhat do you mean?04:10
zulif you mean the other 3 patches that were there yes04:13
BenCok, you may want bump the hoary version04:14
zulyeah i did..04:14
BenCbecause I uploaded one after you for the i386 build failure on amd6404:14
BenCone more than your last one :)04:14
zullinux-source-2.6.10 (2.6.10-34.19) hoary-security; urgency=low04:15
zulthats wgat i have in the changelog04:17
BenCI did a .1904:17
BenCso maybe make it .2004:17
zulok..ill do it tomorrow morning...same for breezy?04:17
zuloh and i have a couple of patches that im testing right now if they compile alright ill forward them tomorrow04:18
zultoodles04:18
WebMavenBenC: You said " the dupes, did not contain enough info to triage the bug"04:42
WebMavenBenC: But the main dupe had all 'requested' info, ibncluding the information that this was still a problem in the then-current Beta.04:43
WebMavenThe *only* reason my bug eventually had more info is because I kept asking "is there any other info you need" about twice a day.04:44
WebMavenAnd becasue I didn't accept people blaming the ralink module.04:45
WebMavenOnly when another user volunteered the info that 'acpi=off' caused the network problems to go away was the problem solved.04:49
WebMavenWithout that info coming to light I'd probabaly still be asking "is there any furter info you need?" at irregular intervals.04:52
BenCWebMaven: users were asked to try the stuff on the wiki, which included acpi=off05:10
=== ajmitch [n=ajmitch@203.89.166.123] has joined #ubuntu-kernel
=== LordLawless [n=nunya@cm21.sigma17.maxonline.com.sg] has joined #ubuntu-kernel
=== LordLawless [n=nunya@cm21.sigma17.maxonline.com.sg] has left #ubuntu-kernel []
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel
=== Lukketto [n=Lukketto@host147-92.pool8261.interbusiness.it] has joined #ubuntu-kernel
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel
=== doko [n=doko@dslb-088-073-091-142.pools.arcor-ip.net] has joined #ubuntu-kernel
=== pitti [n=pitti@ubuntu/member/pitti] has joined #ubuntu-kernel
pittihi11:25
fabbioneyo11:25
fabbioneBenC: the problem is that for some fucked up mind logic behind -updates11:25
fabbioneif you start using it, you will need to upload the kernel twice each time you do a security or bug fix11:25
fabbionei personally don't care11:25
fabbionebut pitti can explain the details to you11:26
fabbionei would prefer to keep all in one pocket for the sake of baby jesus11:26
fabbionebut you decide11:26
BenCok11:26
pittifabbione: it's not a fucked up logic, it's simply creating another branch we have to care for11:26
BenCi can do security11:27
fabbioneBenC: do you want me to rephrase something to make it look like security?11:27
pittiBenC: which changes do we talk about?11:27
fabbionei am goo at that ;)11:27
BenCpitti: random fixes from malone11:27
pittiBenC: are they just some sparc bug fixes, or that sort?11:27
pittiBenC: safe fixes with obvious patches are fine for me for -security11:28
BenCno, they touch arch-indep code11:28
pittiBenC: and since we should not be less careful with -updates, it doesn't really matter which one we break :)11:28
BenCsimple fixes11:28
fabbioneall i care is to get the sparc stuff in asap11:29
fabbionei don't care how.. beacuse afaik we will need to push d-i into updates due to ogre model build system11:29
pittiBenC: I'd avoid branching if at all possible11:31
pittiBenC: so for me the question is not really -security vs. -updates, but rather whether a patch is appropriate for stable or not11:31
BenCso stick with -security?11:31
pittiyes11:31
fabbionedid we fix already all the known -security issues?11:32
BenCyes11:32
fabbionehmm ok11:33
fabbionegive me 2 minutes11:33
fabbionei will give you a USN with a fix11:33
BenClol11:36
fabbioneBenC, pitti: see /msg11:36
pittiBenC, fabbione: we don't need to invent anything :) we didn't release the current dapper kernel yet, so just update the currently pending one11:37
fabbioneright11:38
fabbionethat would work too11:38
fabbioneBenC: i leave up to you what you prefer.. 11:39
BenCso can you reject that and I can merge .41 back to .40 and reupload .40?11:39
fabbioneyou will need .4111:40
fabbionesources for .40 have been accepted and processed11:40
fabbioneonly the binaries are sitting in NEW11:40
BenCok11:41
fabbionei guess we will still need the ABI files...11:42
BenCyeah, gotta have those11:42
fabbioneyeha11:42
fabbioneinfinity, Kamion, mdz and elmo are not around11:42
fabbioneour only hope is Znarl11:42
fabbioneor to start waking up people11:43
mjg59Colin's on holiday11:43
fabbionemjg59: yeah, that doesn't change that is not around :P11:44
mjg59It was more "If you try to wake him up, really bad things would happen"11:46
fabbionemjg59: yeah thanks :) i was told :)11:47
=== Keybuk [n=scott@quest.netsplit.com] has joined #ubuntu-kernel
=== zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-kernel
zulheylo01:00
=== Lukketto [n=Lukketto@host153-89.pool871.interbusiness.it] has joined #ubuntu-kernel
zulBenC: i should have the updates for you by lunch time at the earliest02:39
=== tuxmaniac [n=aanjhan@60.254.67.17] has joined #ubuntu-kernel
=== tuxmaniac [n=aanjhan@60.254.67.17] has joined #ubuntu-kernel
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-kernel
zulBenC: -20 is up05:07
zulfor hoary at least05:07
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel
=== tuxmaniac [n=aanjhan@60.254.67.17] has joined #ubuntu-kernel
=== tuxmaniac [n=aanjhan@60.254.67.17] has joined #ubuntu-kernel
=== bradb [n=bradb@209.217.74.66] has joined #ubuntu-kernel
bradbIs there an updated orinoco driver that supports WPA?06:19
mdzfabbione,BenC: I'll accept the upload06:43
cjbbradb: Are there orinoco *cards* that support WPA?06:44
mdzhmm, that's odd, it claims it's been in the queue for 5 days? that seems unlikely06:44
mdzoh, different upload06:45
mdzfabbione,BenC: so does linux-source-2.6.17_2.6.17-1.1 need processing or no?06:45
BenCmdz: Yes, it does, thanks06:46
=== mgalvin [n=mgalvin@ubuntu/member/mgalvin] has joined #ubuntu-kernel
bradbcjb: Hm, good question. :)07:18
=== ivoks [n=ivoks@ubuntu/member/ivoks] has joined #ubuntu-kernel
=== Lukketto [n=Lukketto@host153-89.pool871.interbusiness.it] has joined #ubuntu-kernel
=== Lukketto [n=Lukketto@host153-89.pool871.interbusiness.it] has left #ubuntu-kernel []
=== ivoks [n=ivoks@ubuntu/member/ivoks] has joined #ubuntu-kernel
=== mgalvin_ [n=mgalvin@rrcs-24-39-194-210.nys.biz.rr.com] has joined #ubuntu-kernel
zulwheee...iso training is fun08:07
=== mgalvin_ [n=mgalvin@rrcs-24-39-194-210.nys.biz.rr.com] has joined #ubuntu-kernel
=== bradb [n=bradb@209.217.74.66] has left #ubuntu-kernel ["Ex-Chat"]
fabbionemdz: are you driving .15 upload trough dapper-security NEW process?08:20
mdzfabbione: I was not aware that it needed driving08:22
mdzI thought you were talking about edgy08:22
fabbione.15 in dapper-security needs NEW in katie. I am not sure .41 is there already08:23
fabbionemdz: and pitti doesn't have privileges to do it08:23
fabbioneanyway i am heading off for dinner and football08:25
zulc ya fabbione 08:25
fabbionemdz: if there is anything, please just text me08:25
fabbionecya zulligno ;)08:25
mdzfabbione: processing it now08:25
mdzfabbione: done08:25
fabbionemdz: ok cool. thanks08:25
zulgood luck with ghana08:25
fabbionezul: thanks08:25
mdzif .41 builds the same binaries it should go right through08:25
fabbionemdz: yes, it will and .40 accepted is fine, since it stops at amber checkpoint ;)08:26
fabbionelater guys08:27
=== lloydinho [n=andreas@rosinante.egmont-kol.dk] has joined #ubuntu-kernel
=== Alatius [n=johan@c83-253-26-213.bredband.comhem.se] has joined #ubuntu-kernel
AlatiusNot sure if I've come to the right place here, but I wonder, what is the difference between the 386 kernel that is default and the 686 kernel you can download?09:06
AlatiusI mean, is there different patches applied to it, different compile settings, apart from the target platform?09:06
BenCAlatius: 686 is tuned for 686 CPU's, while 386 will run on 486 and better (it's more generic)09:12
BenCalso the 686 version is SMP enabled09:12
AlatiusYeah, I tried the 686 instead, since I have a PIII, but I have an issue with the 686 kernel that I didn't have with the 386...09:14
AlatiusMy computer will now not shut down itself completely, instead it stays on the message "Will now halt". With the  386 kernel it worked perfectly.09:15
alex_joniAlatius: sounds like ACPI is not working09:15
AlatiusI guess there's some issue with ACPI, yes.09:15
AlatiusBut I wonder, is there any reason why the two kernels would handle it differently?09:18
AlatiusI read on the forums (right before they went offline) that I could try to start with "acpi=force lapic", but it didn't help.09:19
=== allee [n=ach@allee.exgal.mpe.mpg.de] has joined #ubuntu-kernel
zullater10:01
=== zul [n=chuck@ubuntu/member/zul] has joined #ubuntu-kernel
zulheylo10:27
zulcrimsun_: ping10:47
crimsun_zul: pong10:48
zulhave you seen this? http://www.kernel.org/hg/linux-2.6/?cs=c7a4c2b71aa710:48
crimsun_no, looking10:48
crimsun_ah, I saw that changeset, but no one complained so it wasn't backported10:49
crimsun_do we have a related bug report now?10:49
zulyeah..#1114910:50
zuli was going to grab it10:50
crimsun_ok, if you want to, that's fine, else I'll queue it for this evening10:50
zulok ill will be in my tree tonight10:50
crimsun_keep an eye on the struct vs. xxx_t changes10:51
zulill send you the patch 10:53
crimsun_ok, thanks.  crimsun at ubuntu10:54
zulok10:54
=== Lure [n=lure@ubuntu/member/lure] has joined #ubuntu-kernel
=== blahblah [n=tinyirc@dsl081-096-038.den1.dsl.speakeasy.net] has joined #ubuntu-kernel
blahblahcan somebody answer a simple question for me regarding kernel update frequency?11:28
zulblahblah: it should be soon11:28
blahblahhow regularly does it happen?  daily/weekly/monthly?11:29
blahblahI need a wireless driver and the stock installed kernel doesn't have it11:29
zulwhat wireless driver?11:29
blahblahbroadcom, model number I forget11:30
blahblahsystem is at work11:30
=== [g2] [n=g2@nslu2-linux/g2] has joined #ubuntu-kernel
crimsun_the bcm43xx has a native driver which works for some values of "works"11:30
blahblahanyhow I'm just curious because I probably do'nt want to use a distro that has kernel updates quarterly or semi-annually :)11:31
[g2] I think some of the OpenWRT have played with/worked on that driver11:31
blahblahI've been using fedora on my laptop for the past two years but I want something less cutting edge11:31
blahblahand something a bit more cohesive11:32
zulwell we dont do quarerly updates or semi-anual updates if that is what you are asking11:33
blahblahwell, I am asking the frequency............11:33
blahblahis there a repository that has testing kernels that don't make it into the main repo?11:34
crimsun_the frequency depends on the accumulation of fixes, generally. Security issues have highest priorities.11:34
blahblahsure sure11:34
blahblahbut still, are we talking days, weeks or months in general?11:34
crimsun_well, none of us can predict the future, but weeks to month{,s} is a decent range11:35
blahblahok so is it safe to say that there will be a kernel update monthly-ish ?11:35
blahblahI can live with that11:35
zulcrimsun_: ttp://zulinux.homelinux.net/ubuntu/kernel/patches/cs46xx.patch11:36
crimsun_I have no idea. I believe LTS wrt kernels is on the agenda at the Paris conf.11:36
crimsun_zul: danke11:36
BenCblahblah: if you are talking about stable (released), then monthly is probably worst case11:37
blahblahah good deal11:37
BenCblahblah: however, if you are talking about following our development cycle, I can definitely put a hurt on your b/w with kernel updates11:37
blahblahif everything worked, I'd be happy with a stock kernel that updated rarely11:37
=== BenC has no mercy in this case :)
blahblahbut right now I'm using ndiswrapper w/ fedora and dapper has broken support for the wireless11:38
BenCwhich wireless card?11:38
blahblahapparently the newer kernel versions have fixed drivers so that's what I'm hoping to get11:38
blahblahit's some broadcom model, forget which11:38
BenCbcm43xx?11:38
blahblahyeah11:38
BenCif it is, you can blacklist bcm43xx and use ndiswrapper just the same as you used to11:39
blahblahah11:39
blahblahcan you point me to a doc on how to do that?11:39
blahblahI do'nt want to kludge my system, but if it's a clean way of doing it I'll be happy with it11:39
blahblahis there a modules.conf or something to tell it to avoid that module?11:40
BenC(as root) echo blacklist bcm43xx > /etc/modutils/bcm-blacklist11:40
blahblahah excellent11:40
BenCthat'll keep udev from loading it up automatically11:40
blahblahexcellent11:40
blahblahthanks for the tip11:41
BenCnp11:41
blahblahadios11:41
zuli think he was just looking for support11:42
=== cjb [n=cjb@pool-151-203-230-202.bos.east.verizon.net] has joined #ubuntu-kernel
cjbHrr.  My machine's been killing itself about once a week since I upgraded to the dapper release.  Maybe it's the temperature or something.11:57

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