=== bjf is now known as bjf[afk]
jjohansenrunning errands, back on later00:20
=== jjohansen is now known as jj-afk
=== bjf[afk] is now known as bjf
=== bjf changed the topic of #ubuntu-kernel to: Home: https://wiki.ubuntu.com/Kernel/ || Maverick Kernel Version: 2.6.35 || Ubuntu Kernel Team Meeting - October-5 - 17:00 UTC || If you have a question just ask, and do wait around for an answer!
=== ivoks is now known as ivoks-afk
=== diwic is now known as diwic_afk
=== diwic_afk is now known as diwic
avinashhmhi, is there any runtime way to find a physical addr corresponds to which virtual add,.... i mean ,any sysfs entry or something like that07:25
=== smb` is now known as smb
=== smb is now known as smb`
=== smb` is now known as smb
* smb yawns08:26
jj-afkmorning smb08:28
smbgood night jj-afk :)08:28
smbMorning cking. A little question to start the morning. Not really important but I wonder whether the new installer dialog for Ubuntu still offers some place to add a caching proxy. Not sure whether i just missed it but cannot remember to have seen it in Kubuntu or Ubuntu alternate install...09:06
ckingsmb, hrm, the installer has been simplified, and I did not see that option either09:08
smbI guess its the least of a common users problem...09:08
* cking wonders if it's available on the alternate installer09:13
* smb did not see it09:13
smbNice, radeon-kms on my external monitor does not give me headaches in Maverick (ignoring the purpely background). One would hope this would be a simple change to be SRUed into Lucid...09:35
=== diwic is now known as diwic_afk
Kanohi, when will rc6 be ready?10:33
Kanoalso how about a special branch with aufs patch?10:33
=== diwic_afk is now known as diwic
apwKano, as always a couple of hours, its in the queue10:39
apwKano, so far there is no aufs2 for 2.6.36 based kernels10:39
Kanowould be better when it would be mainline...10:40
apwits unlikely to be mainline ... it was rejected and the author and upstream not keen on compromise10:40
Kanoand anything similar10:41
=== diwic is now known as diwic_afk
Kanoapw: is 35.7 in the queue too12:00
=== diwic_afk is now known as diwic
araJFo, morning mate12:10
araJFo, do you have a minute?12:10
diwicevery now and then, I bump into a problem where I find things like this in dmesg: "disagrees about version of symbol snd_ctl_add"12:17
diwicHow do you trace such problems down?12:18
=== cking is now known as cking-afk
JFoara, I do13:14
JFoprovided you still need me13:14
araJFo, yes, I need13:56
JFoI feel needed13:57
araJFo, davmor2 found a bug today with the Broadcom STA driver13:57
arabug  https://bugs.launchpad.net/bugs/64935713:57
ubot2Launchpad bug 649357 in network-manager (Ubuntu) "network-manager on une will not connect (affects: 1) (heat: 6)" [Undecided,New]13:57
* JFo opens the bug13:57
aracan you have a quick look to see if it could be a regression-potential on the kernel?13:57
* smb wonders. Wasn't sta == bcmwl13:58
arahe's happy to add any other information you may need13:58
JFoara, can do :)13:58
* tgardner wonders. wasn't bcmwl an OEM problem?13:58
smbWell at least it might be a jockey problem13:58
smbI remember that you need to blacklist ssb and b44 to allow bcmwl to load13:59
Kanodo you use
JFoKano, I'm not sure what that number is in ref to?14:00
JFosmb, who do you think is appropriate to look at that bug?14:00
Kanowell if you dont use the ubuntu package14:00
JFosomeone who works on Jockey?14:00
Kanothat script installs it too14:00
* smb would volunteer tgardner but that may retaliate to himself...14:01
Kanowith dkms support and correct blacklisting14:01
JFosmb, heh14:01
JFoKano, ah, now I see :)14:01
Kanobut you may NOT use the default ubuntu package for it then14:02
smbJFo, I think first step would be whether it is a module load problem or something else14:02
smbJFo, And no I have not looked at the bug. :-P14:02
smbJFo, Looking at it that is at least not the driver14:03
smbAs it seems to work when running normal destktop14:03
smbJFo, Maybe asac can make a guess here14:05
JFoI've asked him to take a look in #u-devel14:10
JFoodd bug 64279214:27
ubot2Launchpad bug 642792 in linux (Ubuntu) (and 1 other project) "ALT+PrtSc not recognised (affects: 4) (dups: 1) (heat: 412)" [Undecided,Confirmed] https://launchpad.net/bugs/64279214:27
JFofrom comments "ALT+PrtSc+H I get the magic SysRq key help, so it looks like the kernel is trapping ALT+PrtSc."14:28
JFowonder how that regression could happen14:28
smbJFo, That the kernel looks for that has always been the case14:28
smbIt just was intercepted when running X to do a print screen14:29
JFobut it doesn't looks to be doing anything with it14:29
smbJFo, The thing is that most keyboards have alt+ptrscr == sysreq14:29
JFoI see14:30
JFoand in this case it may not be?14:30
popeymy keyboard does indeed have alt+ptrscr == sysreq14:30
smbOr whatever used to intercept the keypress of alt+ptrscr before does not work for some reason14:31
JFothere are several bugs on this14:31
JFowonder what could have changed14:32
JFomaybe X?14:32
smbJFo, Maybe loking at keyboard shortcuts helps14:32
JFohmmm, my kbd uses Fn+PrtScrn for SysRq14:33
smbJFo, Funny, in Lucid even removing the shortcuts for PrtScr and alt+PrtScr does not stop gnome from doing it. Bah14:34
JFointeresting way to discover the close channel key combo14:41
JFosmb, cyphermox is looking into the STA driver bug from earlier.14:41
smbHeh, something like please press ctrl-alt-del to continue in earlier days? :)14:42
smbJFo, Yeah saw that14:42
JFonot sure what it was. I was typing to you about the bug and apparently hit the right rune for it to close just this channel :)14:42
* smb thinks of ctrl+w14:44
ogasawaraJFo: I was actually looking at that bug 642792 yesterday15:56
ubot2Launchpad bug 642792 in linux (Ubuntu) (and 1 other project) "ALT+PrtSc not recognised (affects: 4) (dups: 1) (heat: 412)" [Undecided,Confirmed] https://launchpad.net/bugs/64279215:56
JFoah :)15:57
JFowhat do you think ogasawara?15:57
JFolook like something up the stack broken?15:57
ogasawaraJFo: from what I can gather, it's expected behavior because sysrq handling is enabled by default in the kernel thus Alt+PrintScreen is interpreted as SysRq15:57
JFoso no bug15:58
ogasawaraJFo: If we don't want that enabled by default, we should set "kernel.sysrq = 0" in /etc/sysctl.conf15:58
JFowant me to convey that to reporters?15:58
ogasawaraJFo: I was going to write up a comment this morning to the bug, just haven't gotten to it yet15:58
JFook cool15:58
JFoif you like15:58
ogasawarapopey: ^^15:58
smbogasawara, The interesting part is that in Lucid the printscreen from gnome is chinming in even with it enabled15:58
JFoI will mimic you to the other bugs I find15:58
ogasawarasmb: I'm wondering if that's actually a bug in Lucid that it is capturing a screenshot when sysrq handling is enabled15:59
popeyI am struggling to see how this isn't a regression bug. this has worked for years.16:00
popeyand in system -> preferences -> keyboard shortcuts, it does indeed recognise ALT+PrScr in <Lucid.16:00
ogasawarapopey: indeed, it's still expected behavior that Alt+PrintScreen will take a screenshot of the currently selected window by default16:00
popeywell, <= Lucid.16:00
smbogasawara, Initially I thought it would be ok when the shortcuts define this combination to be screenshot. The slightly annoying part is that i removed that definitions through the dialog and it still happens16:01
ogasawarapopey: which is why I'd think we should disable SysRq handling by default to restore original behavior16:01
popeydisabling via kernel.sysrq has the byproduct that the keyboard shortcut dialog doesn't say "Alt+PrSc" when you are defining the key, but "Alt+SysRq"16:02
popeywhich is odd16:02
popeyIIRC under Lucid it says Alt+Print, but I dont have any Lucid boxen to test on right this moment16:02
smbogasawara, In Lucid it depends whether you are on the console or not. In X -> screenshot. On the console (text) the sysrq keys are active16:03
smbpopey, It does (or did)16:03
smbogasawara, Or in theory they are probably active both, but by the time you get to press something like alt+prtscr+s, you have several screenshot windows in your face16:05
ogasawarasmb: was gonna ask if you still get screenshots even after pressing a key in combination with alt+prtscr, so it sounds like you do16:06
smbLet me try whether it does actually do it beside the many screenshots16:07
smbogasawara, confirmed. It does both16:07
ogasawarasmb: so that just seems odd and annoying to me16:08
smbogasawara, So the bug that alt-prtscr does not do a screenshot is just that gnome does not do it. The kernel behaves as before. Well seems some feature compability with the other os. With keyboards having sysrq on fn+something it might be less confusing16:09
smbas long as something is not prtscr, that is16:10
popeythanks for looking at the bug ogasawara / JFo 16:11
popey(and smb) :D16:11
JFono sweat popey16:12
JFoI think we had actually discussed the issue briefly before but got pulled into other things16:12
hackeronJFo: any luck? :)16:15
JFohackeron, sadly no16:16
JFosmb, are you familiar with linux-crashdump?16:16
smbJFo, no, not really16:16
JFome either16:17
JFohackeron is having issues getting it to work16:17
JFoand I am not familiar enough to help16:17
JFoodd bug 64704316:17
ubot2Launchpad bug 647043 in linux (Ubuntu) "Unable to detect USB ports (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/64704316:17
JFo2 USB issues in the same week16:17
hackeronJFo: did it not store the panic in /var/crash for you either?16:17
JFohackeron, I never got round to changing that setting jj showed us yesterday16:18
JFowill try it now16:18
hackeronthanks :) - just to make sure it's not just my system16:19
JFono sweat16:20
JFolooks like it is working for me hackeron 16:21
JFoI have 2 crashes in there now16:21
hackeronhmmm, is that with the setting jj showed yesterday or without?16:21
hackeronI have crashes there, just nothing related to linux-image16:21
JFoone sec16:21
hackeronI have _usr_bin_landscape-sysinfo.0.crash - which is not to do with the kernel16:22
=== JanC_ is now known as JanC
=== ivoks-afk is now known as ivoks
ogasawaravanhoof: bug 644237, did you have access to hw that could reproduce that warning?18:06
ubot2Launchpad bug 644237 in linux (Ubuntu) (and 1 other project) "WARNING: at /build/buildd/linux-2.6.35/arch/x86/include/asm/processor.h:1005 read_measured_perf_ctrs+0x78/0x90() (dup-of: 615153)" [Medium,Triaged] https://launchpad.net/bugs/64423718:06
ubot2Launchpad bug 615153 in linux (Ubuntu) (and 1 other project) "WARNING: at /build/buildd/linux-maverick-2.6.35/arch/x86/include/asm/processor.h:1005 read_measured_perf_ctrs+0x6c/0x80() (affects: 29) (dups: 33) (heat: 276)" [Undecided,Confirmed] https://launchpad.net/bugs/61515318:06
vanhoofogasawara: i do18:06
vanhoofogasawara: Sarvatt has one in hand as well18:06
ogasawaravanhoof, Sarvatt: cool, seems like there might be a patch upstream.  If I build you a test kernel with it applied, could you do some quick testing for me?18:07
Sarvattyep! thanks for that ogasawara18:07
jjohansenogasawara: do you remember if we opened a bug for the AA 0 day18:45
ogasawarajjohansen: yah, I added it to bug 647071 (see bottom of bug description)18:45
ubot2Launchpad bug 647071 in linux (Ubuntu Maverick) (and 1 other project) "0-day Maverick Kernel Upload (affects: 1) (heat: 12)" [High,Confirmed] https://launchpad.net/bugs/64707118:45
jjohansenogasawara: thanks, I got the okay from jdstrand so I will post it to the list now18:46
ogasawarajjohansen: cool, thanks18:46
jdstrandyep, works great :)18:46
jjohansenogasawara: should I open a separate bug as well?18:47
ogasawarajjohansen: nah, I'd just use 64707118:47
ogasawaraSarvatt: when you time to get a chance to test - http://people.canonical.com/~ogasawara/lp644237/amd64/18:53
JFoogasawara, she has sent the dmesg for that USB bug18:53
ogasawaraJFo: hrm, it's not showing that any device was even detected.  don't suppose she could boot a Lucid LiveCD and confirm that the port isn't dead and attach dmesg from the working scenario.18:58
JFok, will ask18:58
ogasawaraJFo: is she in Millbank?19:00
ogasawaraJFo: as we'll have actual bodies in Millbank next week19:00
JFowas thinking the same19:01
JFoshe lives in CT19:01
ogasawaraJFo: also just curious if she plugs the devices prior to booting are they then detected?19:07
JFoshe is going to test that19:07
* tgardner lunches19:08
=== amitk is now known as amitk-afk
JFoshe's also going to test the windows she has installed dual-boot19:10
JFosee if it works there19:10
JFoogasawara, windows has no issues with the USB19:12
JFothey work there19:12
JFoogasawara, 19:53
JFo<lisas> BusyBox v1.15.3 (Ubuntu 1:1.15.3-1ubuntu4) built in shell (ash)19:53
JFo<lisas> Enter 'help' for a list oof built-in commands19:53
JFo<lisas> (initramfs) Unable to find a medium containing a live file system19:53
JFo* rickspencer3 has quit (Ex-Chat)19:53
JFo<lisas> jfo ^^^ this is what is showing on my screen now when trying to boot from USB19:53
ogasawaraJFo: that's for Lucid?19:55
ogasawaraJFo: or for Maverick?19:55
ogasawaraJFo: I'd expect Lucid to work, Maverick not so much19:57
ogasawaraJFo: I basically want to be able to compare the dmesg's from a working Lucid and a broken Maverick19:58
ogasawaraJFo: ok, so that seems expected19:59
JFoyeah, I have asked for Lucid19:59
JFoshe'll have to d/l it19:59
ogasawaraJFo: she's got some error messages in her Maverick dmesg with respect to usb that look suspect19:59
ogasawaraJFo: if you could walk her through testing the latest 2.6.36-rc6 mainline kernel too that'd be good20:00
JFoyeah, I asked her about that initially20:00
scrllockhmm, looks like xm shutdown times out with -rc6 as well20:07
JFohackeron, I have yet to get my kernel to fail :-/20:09
JFoI suppose I should be happy20:10
* ogasawara lunch20:49
vanhoofJFo: you want to panic your box? :)21:45
tgardnerogasawara, you doing anything on tangerine? I need to rebuild the maverick chroots21:52
ogasawaratgardner: go ahead, I'm inbetween test builds21:53
tgardnerogasawara, bouncing21:53
JFoogasawara, her last to me today was that Lucid appeared to work fine on the LiveISO22:43
ogasawaraJFo: ok thanks, will look at the logs in a bit22:44
JFoI'm fighting a massive headache, so I think I am going to call it for today. May check back in later22:44
JFothanks ogasawara :)22:44
=== yofel_ is now known as yofel

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