[01:11] <cjb> Evening.  My Dell m1330 takes 25 secs to resume from S3, with latest hardy, due to the SATA link timing out.  Is it known?  dmesg snippet at http://pastebin.com/m563c7f79
[01:20] <mjg59> cjb: I've seen that on other hardware, though mostly with older kernel.s
[01:20] <mjg59> cjb: Do you see the same with gutsy?
[01:23] <cjb> mjg59: Dunno, just got the laptop today and installed hardy.  Can find out, though.
[01:24] <mjg59> That'd be helpful. You should be able to check from the CD.
[01:24] <cjb> 'kay.
[01:25] <mjg59> If it's a regression, that makes life much easier. Otherwise, we need to spend a while working out what's going on :)
[01:25] <mjg59> Is this on every resume, or just the first?
[01:31] <cjb> mjg59: possibly every resume *after* the first.
[01:32] <cjb> wow, interrupt storm
[01:32] <mjg59> Hm. Interestiny.
[01:32] <cjb>     4 root      15  -5     0    0    0 R  100  0.0 169:56.08 ksoftirqd/0        
[01:32] <mjg59> Yeah, you lose. What interrupt?
[01:36] <cjb> not sure: http://pastebin.com/m571fa880
[01:41] <cjb> still spinning on ksoftirqd, but the only thing increasing significantly is the timer interrupt at about 100Hz
[01:41] <mjg59> cjb: Huh.
[01:42] <mjg59> That's all very weird.
[01:57] <cjb> works fine with Fedora/Rawhide, for whatever that's worth.
[02:03] <cjb> oh -- the Fedora install is 64-bit, and Hardy is 32-bit 2.6.24-11-generic.
[02:10] <mjg59> Hm. Kernel code should be generic.
=== mdomsch is now known as mdomschbot
=== mdomschbot is now known as mdomsch
=== abogani changed the topic of #ubuntu-kernel to: Ubuntu kernel development discussion ONLY | Kernel Wiki: https://wiki.ubuntu.com/KernelTeam | Latest kernel upload: 2.6.24-11.17 | Latest news: 2.6.24 Release in Hardy | Next meeting: Mar 4, 17:00 UTC | Kernel Team machine: http://kernel.ubuntu.com
[08:21] <kraut> moin
=== asac_ is now known as asac
=== doko_ is now known as doko
[13:18] <dda> hi everyone. not sure if such a question is ok here, but in #ubuntu nobody replies.. how to know what parameters can a kernel module accept? in particular, freq_table
[13:18] <mjg59> modinfo
[13:20] <dda> wow, that's really simple! thanks :)
[13:20] <dda> now I see that there are no params for that module
[15:01] <mathiaz> Hi ! I'm currently reworking the wiki pages of the ServerTesting Team. I was wondering what is the minimal information needed when filing a bug about a failed installation ?
[15:01] <mathiaz> Let
[15:02] <mathiaz> 's that user tried to install alpha5 on a poweredge 1950 and network and disk were not detected
[15:17] <rtg> mjg59: BenC has promised to revisit the ACPI patch that I recently reverted for FTBS. cjwatson also mentioned that you had a VT switching patch ?
[16:00] <BenC> mathiaz: lspci and dmesg are important for those types of bugs
[16:01] <BenC> mathiaz: lspci -vvn to be exact
[16:04] <mathiaz> BenC: lspci -vvnn or -vvn ?
[16:05] <mathiaz> BenC: https://wiki.ubuntu.com/KernelTeamBugPolicies advises -vvnn
=== kylem_ is now known as kylem
[16:29] <mjg59> rtg: Yeah. I'll send the VT switching patch.
[16:31] <rtg> mjg59: I'm gone Mar 6-26, but I'll make sure it gets on the kernel team ToDo list. Thanks.
[16:47] <mario_limonciell> rtg, are you already gone for vacation, or got time for a quick question?
[16:47] <rtg> mario_limonciell: still here for a couple more hours
[16:48] <mario_limonciell> rtg, would it be out of the question to merge sky2 from linus' branch? It appears to resolve some pending suspend issues.  There are a number of commits that we are missing, so i'm not sure particularly which one it is that resolves it
[16:49] <rtg> mario_limonciell: the best approach is either lum or lbm. It depends on how much change there has been.
[16:50] <rtg> mario_limonciell: on 2nd thought, let me look at it.
[16:50] <mario_limonciell> okay
[16:55] <rtg> mario_limonciell: can you pop the sky2 driver into LUM, build it, and see if it solves your problems? There have been a lot of changes since 2.6.24. It may also be a candidate for LBM.
[16:55] <mario_limonciell> rtg, I rebuilt my linux-image with it in place and it appears to resolve the particular issue that we were having 
[16:56] <mario_limonciell> there is still a different suspend issue that happens occassionally (even if that driver isn't loaded), but the symptoms that we get with that old driver loaded don't happen with the new one
[16:57] <rtg> mario_limonciell: the issue that I worry about is regressions if I put sky2 in the kernel (a non-elective package). Thats why I lean towards LBM.
[16:57] <mario_limonciell> rtg, understandable.  
[16:57] <rtg> mario_limonciell: its getting pretty late in the game for big changes.
[16:57] <mario_limonciell> rtg, well i'll see if I can narrow down to a commit or two that resolve it particularly
[16:58] <mario_limonciell> there are some memory alignment commits that I was leaning towards
[16:58] <mario_limonciell> we'd prefer to avoid lbm if possible this time around -
[16:58] <rtg> mario_limonciell: looking at the interwoven history of changes, that may be difficult.
[16:58] <mario_limonciell> right.
[16:59] <BenC> smb, cking, amitk, rtg: ping
[16:59] <amitk> BenC: here
[17:00] <rtg> BenC: yo
[17:00] <cking> BenC: hi
[17:02] <BenC> We'll get started and let smb catch up
[17:03] <BenC> Ok, welcome to the kernel team meeting. We missed last week because the team was in Lexington for a sprint
[17:03] <BenC> Details on out meetings can be found at https://wiki.ubuntu.com/KernelTeam/Meeting
[17:03] <BenC> *our
[17:04] <BenC> We'll start of we individual status
[17:04]  * BenC is not typing well today
[17:04] <BenC> I'll blame it on guitar hero
[17:04] <BenC> amitk: Want to go first?
[17:04] <rtg> 'cause your fingers are bleeding?
[17:04] <amitk> sure
[17:05] <amitk> Mainly worked with the UME team to get a ubuntu mobile image out to Intel
[17:06] <amitk> have been working to integrate newer version of wlan and DRM kernel drivers for the Intel "Atom" processors, as they are now called
[17:07] <BenC> amitk: How did the sprint work out for you last week? Did the time with the MID team help?
[17:07] <amitk> next up is to looks the USB_PERSIST that we need to enabled to get out of the box support for eee pc and some other machines out there
[17:07] <BenC> amitk: out-of-the-box, meaning "with the right kernel param", right? :)
[17:08] <amitk> the sprint helped in clarifying the roles of kernel team and the mid teams. They have to do some of the lifting to ensure the Ubuntu has the latest drivers
[17:08] <amitk> BenC: I am shooting for "enabled-via-sysfs"
[17:08] <amitk> That's it from my end
[17:09] <BenC> ok, thanks
[17:09] <BenC> rtg: time to hear from you
[17:09] <rtg> Besides a zillion bugs and patches applied, the single biggest thing I've worked on is the ABI breakage fixes.
[17:10] <rtg> see https://wiki.ubuntu.com/KernelTeam/Sprints/Feb2008/HeadersABI
[17:10] <rtg> Other then that, its just the minutia of kernel builds, uploads, ABI bumps.
[17:10] <BenC> Oh, for anyone wanting to see what happened at the sprint, here's the low down: https://wiki.ubuntu.com/KernelTeam/Sprints/Feb2008
[17:10] <rtg> I'm gone Mar 6-26.
[17:11] <rtg> thats all from me.
[17:11] <BenC> rtg: thanks
[17:12] <BenC> cking: So how have things been going with you?
[17:12] <cking> OK - working through the list of kernel bugs, the usual, patching, building, etc.. 
[17:13] <cking> ..working out a better work flow now that I getting familiar with git and the various build machines
[17:13] <BenC> cking: Preempted my next question :) Are you finding enough to do in general?
[17:15] <cking> Yes.. and no.  Started to run a bit low end of last week.. ..but Monday comes around with more bugs..
[17:15] <cking> ..are there any extra "challenges" then?
[17:16] <BenC> Ok, ping me anytime if you find yourself running low
[17:16] <BenC> Generally the blueprint list fills in, but this close to release, we don't have that anymore
[17:16] <cking> ..well I did look at a few other kernel issues not listed on the bug list to get my karma rating up :-)
[17:17] <BenC> cking: yeah, definitely don't let the hardy-buglist be your only source for bugs...there's lots more out there :)
[17:17] <BenC> cking: ok, thanks
[17:17] <amitk> cking: I am sure the MID guys would love to see you around too :)
[17:18] <cking> amitk: yeah - how do I get my teeth into that domain?
[17:18] <amitk> cking: you, Ben and I can perhaps discuss this offline
[17:18] <cking> ok
[17:19] <BenC> One thing would be to get the stock+build-system tree up for intrepid/lpia
[17:19] <BenC> for the MID/UME folks
[17:20] <BenC> Alright, not much to say about the bug list from last week except that we completely kicked its ass
[17:20] <cking> Its a good feeling to do that
[17:20] <smb> Oh well, just in case someones interested. ;-) I did mostly bugs. Beside of several smaller bugs, the one which was bigger timewise was the patchset for the i915. Otherwise trying to solve a duplicate vendor id issue upstream and evaluated how to get lum builds without installing the headers (for porter machines and build scripts).
[17:20] <BenC> So great work there...only one bug got carried over from last week, and it's In-Progress
[17:20] <BenC> smb: Ah, you're here...ok...
[17:21] <smb> Yes, sorry. Failed to ping
[17:21] <amitk> BenC: right. I cloned Linus' tree and copied over the debian/ dir. But it needs compile testing before pushing out the interpid trees.
[17:22] <BenC> amitk: ok, good start, we'll keep that moving to hand over to MID/UME at UDS
[17:22] <amitk>  As the plan stands, UME Interpid and Ubuntu Interpid will have identical git trees. I'll push something out next week.
[17:23] <BenC> Ok, that brings the primary agenda to an end...
[17:24] <BenC> First thing I'd like to address is rtg being out for March 6-26...we will be in a general kernel freeze till hardy release, so there wont be much outside of critical bug fixing during that time
[17:24] <BenC> but we have some CVE work and testing (LTS=>LTS mainly) to handle, so the rest of us will have to pull his weight
[17:25] <rtg> actually, I'm out Mar 5-26.
=== phoenix24_ is now known as phoenix24
[17:25] <BenC> Ok, so we wont see you after today until you are sun dried and fat from eating rattle snakes :)
[17:25] <rtg> indeed.
[17:25] <rtg> I'm getting short timers attitude.
[17:27] <BenC> The other thing I want to point out is that we, the kernel team, have been slipping again on using this channel for general discussions
[17:27] <BenC> I'm just as guilty (and probably to blame) for it...but we need to make a strong effort to keep discussions here and be more transparent
[17:29] <BenC> And with that, I'd like to know if anyone has anything they would like to discuss
[17:29] <smb> Hm, not currently
[17:30] <cking> Nothing immediately comes to mind
[17:30] <amitk> nope
[17:30] <BenC> This would also be an opportune time for community to raise any issues
[17:31] <BenC> Ok, thanks everyone...meeting is adjourned
[17:31] <BenC> Have a great week, and see everyone next week (except rtg)
[17:31] <cking> OK
[17:31] <smb> Thanks. Till then
[17:31] <smb> rtg: Have a safe trip
[17:32] <zul> BenC: is there a chance for an iscsi fix im working on to get in for hardy?
[17:33] <zul> its basically a cherrypick
[17:33] <rtg> zul: request a pull so we can look at it.
[17:33] <zul> okies
[17:34] <rtg> zul: use the git protocol. I've found that http doesn't seem to work.
[17:34] <zul> rtg: yeah I always use git
[17:34] <zul> er...git protocol
[17:35] <rtg> zul: no, I mean in the pull request, e.g., git://kernel.ubuntu.com/zul/ubuntu-hardy-xen.git
[17:35] <zul> ok
[17:39] <tjaalton> if you guys want a bug to work on, I've got a crasher which is confirmed :) (bug 189185)
[17:39] <ubotu> Launchpad bug 189185 in linux "Thinkpad X61 hangs when removing from dock" [Medium,Confirmed] https://launchpad.net/bugs/189185
[17:39] <j4k3b> BenC: do you have a second to talk privately?
=== BenC changed the topic of #ubuntu-kernel to: Ubuntu kernel development discussion ONLY | Kernel Wiki: https://wiki.ubuntu.com/KernelTeam | Latest kernel upload: 2.6.24-11.17 | Latest news: 2.6.24 Release in Hardy | Next meeting: Mar 11, 17:00 UTC | Kernel Team machine: http://kernel.ubuntu.com
=== n2diy__ is now known as n2diy
[20:40] <Kano> hi, why does nobody learn from former mistakes?
[20:40] <Kano> http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-hardy.git;a=commitdiff;h=fb82da6120f7a08405b314377750b17576802c56
[20:41] <Kano> that does not only disable the modules which are in lum when you use: # CONFIG_SOUND is not set
[20:41] <Kano> but also the sound modules of video drivers
[20:42] <Kano> that patch is crap
=== j4k3b is now known as jakeb_