[01:40] <spijet> Good Mourning!
[01:41] <spijet> Excuse me for my bad English, i have a problem with 2.6.30.5 kernel.
[01:44] <spijet> When i have installed it, it starts, but after ~2 seconds in usplash, it (crashes?) to a black screen with cursor in a upper-left corner.
[01:45] <spijet> And it is NOT terminal, because i can't switch it.
[11:20] <gnomefreak> is the system beep controled by the kernel?
[13:29] <rtg> smb, what is it you're asking me about the joystick regression? I realize the same patch is upstream, but looks to be incorrect. Are you gonna work with the upstream developers to find a better fix?
[13:32] <smb> rtg, I, if asking is the right word, just wanted you to be aware of it. The question is whether this patch is incorrect or the Saitek joystick driver in its use of a certain button code. That is a bit beyond y knowledge, but I am checking on the upstream bug.
[13:50] <rtg> smb, is this causing wide spread carnage, or are we helping more then we hurt?
[13:50] <smb> rtg, Spread enough in Jaunty to cause complains. Otherwise I just was notified as I was in the SOB
[13:51] <rtg> smb, you were notified that upstream is changing the patch?
[13:52] <smb> No of the started bugzilla regarding the regression
[13:52] <rtg> smb, ah.
[13:52] <smb> But the initial comment from Dmitry sounds like he also believes BTN_DIGI is for digitizers and not for joysticks
[13:52] <smb> to be continued
[13:53] <rtg> smb, ok. I assume this'll find its way into a stable update eventually.
[13:54] <smb> rtg, I'd say so. As said, just for you to know when gamers complain to you about it. 
[13:55] <rtg> smb, huh, like _I'll_ hear about it. It'll be Andy that gets most of the noise.
[13:55] <smb> rtg, Heh, well he is not around for a bit...
[15:02] <juliux> hi, how could i find out with which gcc version my kernel was build?
[15:02] <ogra> dmesg|head
[15:05] <juliux> thxs
[16:04] <thjc> Hi all, I need some help debugging a system crash (sudden reboot) which I can reproduce compiling certain files with an arm cross compiler. This seems to be related to the specific revision of the hardware in the machine (ich8 rev3) as I have tried the same hard disk and operation in a similar laptop with ich8 rev4 hardware
[16:05] <thjc> also a centos 2.6.18 kernel doesnt have the issue, but ubuntu Jaunty and Karmic kernels do
[16:07] <ameno> does it always happen while compiling the exactly same file? (you said fileS)
[16:07] <thjc> it doesnt always happen, but there are server files that I can set up a bash do while loop over compiling and it will die within 2 mins
[16:09] <thjc> no oops messages of any sort, hard reboot. does the same thing if I boot recovery mode and run the compile loop there
[16:53] <dholbach> hello everybody
[16:53] <dholbach> can somebody take a look at  https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/277556 ?
[16:53] <ubot3`> Malone bug 277556 in open-vm-tools "should build kernel modules with dkms" [Undecided,Confirmed] 
[16:56] <rtg> dholbach, seems like a server team issue. kirkland could probably answer your questions.
[16:56] <dholbach> I was pinged about it and know nothing about dkms stuff
[16:57] <dholbach> funnily enough I got another email about something with dkms today
[16:57] <rtg> dholbach, its just a method for building external kernel modules (like nVidia)
[16:57] <dholbach> right
[16:57] <dholbach> that much I knew :)
[17:23] <smoser> rtg, the other i spoke with you about -virtual inclusion of acpiphp under bug 364916
[17:24] <ubot3`> Malone bug 364916 in eucalyptus "When running Ubuntu as an Eucalyptus VM instance, module acpiphp is not available to be loaded, complicating the use EBS volume" [Undecided,Confirmed] https://launchpad.net/bugs/364916
[17:24] <smoser> i'm new-ish to this process... what do you need me to do for a.) karmic b.) jaunty.  
[17:26] <rtg> smoser, You need to send an SRU request with a patch to the kernel team mailing list. Get with smb or ogasawara if yiou have questions. zul can also help.
[17:27] <smoser> ok. that is for sru. what about karmic?
[17:29] <smb> smoser, Generally (you have a bug, thats point 1) Then send a patch with a short impact, change and testcase description to the kernel-team mailing list. You can add that the same is needed for karmic
[17:29] <smoser> thanks.
[17:31] <rtg> smoser, you could also just create the report, then bribe someone on the kernel team to fix it (which might be faster depending on your kernel build skills). I know for a fact that smb is not immune to the charms of beer.
[17:32] <smoser> do you know people who *are* immune to charms of beer?
[17:32] <smb> some are rather into wine...
[17:32] <smoser> i'll avoid the shortcut for now, though.
[17:32] <sbeattie> smb: why is the intrepid-proposed kernel still pending?
[17:33] <smb> sbeattie, because the sru team is overworked and also because today a potential regression was found which forced me to reupload
[17:34] <sbeattie> smb: ah, okay, thanks.
[17:38] <ogasawara> fabbione, smb: re bug 416266, I'll roll a new patch to include enabling for ia64 and hppa.  just going to kick of some test builds first and will resubmit.
[17:38] <ubot3`> Malone bug 416266 in linux "Please enable multicast routing support for sparc" [Medium,In progress] https://launchpad.net/bugs/416266
[17:38] <smb> ogasawara, Just because rtg is thinking this does not mean I am convinced
[17:39] <ogasawara> smb: that's why I'm gonna push the new patch to a different branch and let you choose :)
[17:40] <rtg> resistance is futile
[17:40] <smb> ogasawara, Ok, if we find someone who can verify this works, I am ok.
[17:40] <smb> rtg, That is what you think. :)
[17:41] <smb> rtg, If you can provide test results, I am fine. Otherwise...
[17:43] <rtg> smb, honestly, for the 4 ia64/hppa users out there, who really cares? I'm not gonna push this particular case, but for the future we _are_ going to continue to maintain a common config settings algorithm.
[17:47] <smb> rtg, We definitely should avoid having common options different over different archs. And with the new config system we less likely will forget to do so in the first place. My point is just that even though the change sound logical, it is always a risk I would like to minimize. 
[17:49] <smb> Maybe we can ask lamont to test this with hppa and someone else for ia64. A quick boot and network test would be good to make that change more compfortable
[17:50] <rtg> smb, ah, its hardly worth the effort. I'm just chapping your ass :)
[17:51] <smb> rtg, And I try to save my ass from the spanking if that 4 users would get regression. :-P
[17:51] <lamont> so... if it's a karmic kernel, hppa is not in karmic.
[17:51] <lamont> if it's a hardy kernel, then I kinda care
[17:51] <lamont> some
[17:51] <lamont> a little.
[17:51] <smb> No we were talking about hardy
[17:51] <lamont> ia64, yeah I still care
[17:52] <lamont> hardy - definitely would love to test a kernel
[17:52] <rtg> lamont, what are these boxes being used for? Surely not BGP routing?
[17:53] <smb> Well at least it would prove that the normal use case is unaffected
[17:54] <lamont> rtg: heh. not so much
[17:54] <lamont> actually, I am aware of ia64 boxen being used in a very heavy sctp environment, with a routing protocol (OSPF?) under that
[17:54] <lamont> OTOH, they're not running ubuntu
[17:55] <rtg> lamont, huh, then maybe I sit corrected.
[17:58] <lamont> rtg: so mostly I just care that the box still boots after I do a dist-upgrade
[17:58] <rtg> lamont, I'll try to convince smb to not break things :)
[17:58] <lamont> and while I have people's attention, I should really check and see if the most recent kernel upgrade on jaunty made it so that windoze XP Pro/SP2 still boots in kvm
[17:59] <lamont> 2.6.28-11.42 was the last working verison
[17:59] <lamont> version
[17:59] <smb> Well when ogasawara posts the update to the config settings I try to get lamont do a quick test to make sure I do not.
[18:00] <ogasawara> smb: I'll CC lamont on the email
[18:00] <smb> ogasawara, ok, deal
[18:00] <lamont> "quick test"...
[18:00] <lamont> that involves being >8PM or so mountain time, or < 7AM
[18:00] <smb> lamont, Well see it still boots and has a network
[18:01] <lamont> OTOH, booting can be done remotely, and if I temporarily brick that box, it's prolly OK.
[18:01] <lamont> hrm... I might even have remote serial console on that machine
[18:01] <smb> lamont, about the kvm thingy. have you spoken with kirkland about that?
[18:06] <lamont> smb: I don't remember.  it's quite possible that I even filed a bug in launchpad
[18:06] <lamont> I do know that kvm had changes in the security release that broke things....
[18:07] <fabbione> ogasawara: works for me...
[18:07] <fabbione> lamont: hey dude
[18:08] <lamont> fabbione: on hppa or sparc?
[18:08] <lamont> dude
[18:08] <lamont> long time no chat
[18:09] <lamont> though getting dragged out to lunch atm
[18:09] <smb> lamont, broke in the security. Hm, if you find that bug pass the number to ogasawara. She will add it to our nag-list
[18:09] <fabbione> lamont: enjoy lunch :)
[18:09] <fabbione> lamont: i tested on sparc, but I can test ia64 and hppa too if needed
[18:09] <fabbione> lamont: the netcode is pretty rock solid on "special" endian and alignment anyway
[18:10] <fabbione> lamont: so i am not worried to enable it again
[18:10] <lamont> smb: sigh.  looks like the only jaunty-pain-with-kvm I  filed was  	353995  	 BLTs appear broken - moving blocks on the remote leaves cruft
[18:11] <smb> fabbione, if you have both other archs too, I am fine with either of you doing a quick test. I just want a bit of it
[18:11] <lamont> I'll upgrade and see what breaks later
[18:12] <fabbione> smb: i am not entirely sure I'll have the time to test them properly, but if you can make me test kernels ready, that will help
[18:13] <smb> fabbione, Sure I build them and link those to the bug
[18:13] <fabbione> smb: ok cool thanks
[18:13] <ogasawara> smb, fabbione: I'm actually kicking off some test builds so can post the test kernels when they finish
[18:13] <fabbione> ogasawara: i am actually about to go and do my househusband duties, cleaning the kitchen and everything else :)
[18:14] <smb> ogasawara, Ok, cool. Torturing the porters a bit :)
[18:14] <fabbione>  /msg me or add the urls to the test kernels
[18:14] <fabbione> and I 'll give them a run tomorrow
[18:14] <ogasawara> fabbione: heh, now worries, I'll post it to the bug
[18:14] <fabbione> it's been a while since I needed so much extra heat in the room
[18:14] <fabbione> and it's summer time
[18:14] <fabbione> :)
[18:14] <smb> hehe
[18:20] <fabbione> later guys
[18:20] <fabbione> thanks for listening to an old sparc fart kernel maintainer :)
[18:23] <smb> fabbione, Any time :)
[18:23] <smb> fabbione, later
[18:43] <Nafallo> Aug 26 18:41:50 wizard kernel: [13942.429730] ext4: find_group_flex failed, fallback succeeded dir 114612
[18:44] <Nafallo> lots of stuff like that on my laptop. should I be worried?
[18:44] <Nafallo> jaunty
[18:45] <rtg_> Nafallo, you should be running a Karmic kernel, or a mainline 2.6.28. Something in the Ubuntu kernel is not quite right wrt ext4. ogasawara might have some test kernels for you.
[18:46] <Nafallo> hehe. that wasn't really the answered I wanted :-P
[18:46] <rtg_> and yes, you should be worried.
[18:46] <ogasawara> Nafallo: I recall a bug for that, and I think I have a test kernel.  just a sec
[18:47] <Nafallo> yay! no need to dist-upgrade yet :-)
[18:47] <ogasawara> Nafallo: https://bugs.edge.launchpad.net/ubuntu/+bug/367065
[18:47] <ubot3`> Malone bug 367065 in linux "ext4: find_group_flex failed, fallback succeeded dir" [Medium,In progress] 
[18:48] <ogasawara> Nafallo: test kernel at http://people.canonical.com/~ogasawara/lp367065/
[18:48] <ogasawara> Nafallo: would be great if you can test and post a comment to the bug, I'll then submit it for SRU to Jaunty
[18:48]  * Nafallo goes to read up on it and grab the kernel.
[18:56] <Nafallo> hmm. can't see the message after reboot with the test kernel.
[18:57] <Nafallo> is that expected?
[19:09] <ogasawara> Nafallo: others commented that the warning wasn't always present, even the orig reporter said they only saw it once
[19:10] <ogasawara> Nafallo: what I'd expect is if you do happen to see the warning again, it's only printed once, not repeatedly
[19:10] <Nafallo> ah. I've only seen it just now and used this as my panic room :-)
[19:11] <ogasawara> Nafallo: if you'd be willing to run that kernel for a while and see if it pops up again that'd be great.  If not, if you could still post a comment to the bug that'd be great.
[19:12] <Nafallo> ogasawara: oki. I'll use it for a while then.
[19:12] <ogasawara> Nafallo: thanks
[19:20] <MTeck> Are you guys aware of this little bug 418685 ?
[19:20] <ubot3`> Malone bug 418685 in cryptsetup "cryptsetup hangs" [High,Confirmed] https://launchpad.net/bugs/418685
[19:22] <rtg_> MTeck, looking at it right now
[20:06] <smoser> ok, i'm doing something stupid. please enlighten me. following https://wiki.ubuntu.com/KernelTeam/KernelMaintenanceStarter .
[20:06] <smoser> i made debian/control and prepare-generic
[20:06] <smoser> then tried
[20:06] <smoser> binary-server . it fails
[20:06] <smoser> with 'tail: cannot open `debian/changelog' for reading: No such file or directory'
[20:07] <smoser> which, makes sense, because there is no debian/changelog.... i'm sure there is some user error.  any help?
[20:14] <MTeck> rtg_: what's your opinion on that?
[20:16] <rtg_> smoser, 'fakeroot debian/rules clean;fakeroot debian/rules binary-debs flavours=server'
[20:17] <smoser> rtg_, will flavours=server make -virtual ?
[20:18] <rtg_> smoser, -virtaul is based off of -server, so you have to make it first. I don't think there is a shortcut for -virtual
[20:20] <smoser> so how would i make it ? 
[20:20] <smoser> does it just get made along with server ?
[20:20] <jsteel> Does anybody know how ubuntu kernels are versioned? Specifically I'm looking for what exactly the 60 means in 2.6.24-24.60. I'm trying to create a custom kernel and want to know if I should name it 2.6.24-24foo1 so that I can upgrade it to 2.6.24foo2 and so on. Or should I call it 2.6.24-24.60foo1? I cant find anywhere a reference that describes Ubuntus kernel versioning.
[20:31] <rtg_> jsteel, its just an upload number. if you look at the tags in git you can see how they are encoded, 'git tag|grep Ubuntu'
[20:33] <jsteel> rtg_: It looks like there are usually 2 or three upload versions. ie 2.6.24-24.59 and 2.6.25-25.60. Why would there be more than one upload version?
[20:45] <awe> rtg_, ping
[20:45] <rtg_> awe, dude
[20:46] <awe> i just updated my macbook to -7, and associated drivers and it's hosed now.  ;(
[20:46] <awe> need some help recovering it..
[20:46] <rtg_> jsteel, somewhere in here is a discussion of version numbers: https://wiki.ubuntu.com/KernelTeam/KernelMaintenance
[20:47] <rtg_> awe, boot back to -6. the root the problem appears to be buildd related.
[20:47] <awe> I tried that, but I still end up at a cmd-prompt
[20:47] <awe> so y'all are aware of the problem I take it?
[20:48] <rtg_> awe, some of the problems, but they appear to be related to encrypted swap
[20:48] <awe> lovely...
[20:50] <awe> ok, well i'll guess i'll switch over to using my old mbpro ( what i'm typing on now ), and look for some guidance on how to fix my macbook later...
[20:50] <rtg_> awe, did you have encrypted swap?
[20:50] <awe> rtg_, no, but i do have home-dir encrypt
[20:51] <rtg_> awe, going back to -rc6 should have fixed it (I think)
[20:51] <awe> rtg_, it didn't for me...
[20:52] <awe> rtg_, it didn't for me.  sometimes it won't even boot to the grub menu ( 50/50 )
[20:52] <rtg_> awe, no that seems like a different problem. can you boot from LiveCD consistently?
[20:52] <rtg_> you had issues in Dublin
[20:52] <awe> haven't tried yet...
[20:53] <awe> rtg_, the issues in dublin were this box ( mbpro ).  returned it to apple and they replaced both fans & a memory module
[20:53] <rtg_> huh
[20:53] <awe> new issues are on my new macbook, and appeared as soon as i updated to -7
[20:53] <awe> i also noticed an nvdia update at the same time...
[20:53] <jsteel> rtg_: Thanks for the link. I didn't see your post.
[20:55] <rtg_> awe, nvidia shouldn't affect the boot to grub
[20:57] <awe> well, lemme see if I can get the console output shrunk so I can see the all the actual errors...  I'm just trying to get this box setup first though, so I have email, etc...
[21:45] <Q-FUNK> one question about karmic:   was there any change in network modules that could explain why an host with an IPv6 address could be pinged under jaunty but not karmic?
[21:47] <rtg_> Q-FUNK, they are 3 full kernel versions different, 2.6.28 v.s. 2.6.31. Maybe you could use some of the mainline builds to find out when things quit working.
[21:48] <Q-FUNK> I'm still using 2.6.28 on that host.  2.6.31 won't boot (bug filed, ogasawara is working on it) and 2.6.30 are gone from the karmic repo.
[21:49] <rtg_> Q-FUNK, look in http://kernel.ubuntu.com/kernel-ppa for maniline builds
[21:49] <Q-FUNK> however, I thought that maybe some newer version of e.g. ufw might load network modules that it didn't in jaunty or something similar
[21:50] <rtg_> you could talk to jdstrand about ufw
[22:00] <Q-FUNK> rtg_: I cannot think of anything different in the network config I use on my karmic and jaunty hosts either, yet the only host that cannot be ping'ed with 'mtr' is my karmic host.
[22:01] <rtg_> Q-FUNK, get a bug started so we don't forget it. gotta go.
[22:03] <Q-FUNK> I'd love to but, at this point, I'm not even sure if it's kernel related
[22:08] <Quintasan> hi there, sometime ago I asked about bug 330824, how can I help dealing with it? -15 kernel does not solve the problem :(
[22:08] <ubot3`> Malone bug 330824 in linux "Soft lockups (freezes) when deleting files from ext4 partitions on 2.6.28" [Medium,Confirmed] https://launchpad.net/bugs/330824