[00:00] <marrusl> bjf, np.  thank you!
[03:24] <elpis> I want to ask question how to grep in order to get only the essid and signal level when i issue the iwlist command. 
[03:27] <elpis> I want to ask question how to grep in order to get only the essid and signal level when i issue the iwlist command. 
[05:18] <elpis> hello there can someone help me how to use grep in this problem given . http://pastebin.com/c01UX1B8 
[05:37] <Eimann> iwlist wlan0 scan|egrep 'ESSID|Signal'|sed -e 's/.*"\(.*\)"[^"]*$/\1/' -e 's/.*=\(.*\)*$/\1/' -e 's/ dBm//'
[05:39] <FreezingCold> How does Debian and Ubuntu's kernel differ?
[06:16] <elpis> Eimann: thank you so much you are really great you save my day. BTW do you have any good tutorials on how you do it ?
[06:17] <Eimann> I used http://regex101.com/
[06:19] <elpis> Eimann: thank you so much
[08:11] <ppisati> moin
[08:55] <cking> yawn
[09:11]  * apw yawns hard
[09:11] <apw> smb is in network hell ... 
[16:37]  * ppisati disappears for a bit
[17:12] <qengho> Hi all.  I have a thinkpad with a hard crash that leaves no log file and blinking caps-lock and I want to file a bug report in LP. I can reproduce easily. Is there a good way to capture the crash log? I think my photo of the console is terrible.
[17:12] <antarus> does sysrq work?
[17:14] <qengho> Hrm. Thinkpad funniness. I think I tried right-alt, SysRq, S-U-B and Fn + right-alt, SysRq, S-U-B and had to push the power button.  I can try it again.
[17:14] <qengho> antarus: If it does, what should I do?
[17:15] <qengho> (I have only this target machine here, so IRC debugging is iffy.)
[17:17] <qengho> IRC client on my phone. Rock. Okay, I can do that.
[17:17] <qengho> antarus: Okay, now what?
[17:19] <qengho> dang. hang and reboot that time.
[17:19] <psusi> isn't it time for the kernel meeting?
[17:28] <cking> psusi, it was cancelled 
[17:29] <apw> psusi, we don't typically do them between release and UDS
[17:29] <apw> psusi, if you have something you want to bring up you are more likley to get a response here though as you would there
[17:30] <apw> qengho, if sysrq doesn't get you anything better, then filing a bug with the photo however bad it is is the right thing
[17:30] <apw> with little to go on we would then recommend you start looking for an older kernel which was ok
[17:31] <apw> as i assume this is a new issue to you
[17:38] <psusi> hrm... ok, I've just been wanting to float the idea of CONFIG_EXT[23]=n
[17:38] <apw> =n ok
[17:38] <psusi> with them disabled, the ext4 driver will take over and do a better job than the old code, and give a smaller kernel ;)
[17:39] <apw> so ... the right thing to do is probabally to add that to the vuds kernel session
[17:39] <psusi> ok
[17:39] <apw> as that is quite a big scarey sounding challenge, and we will want to get someone to do some real testing to confirm it works ok
[17:40] <apw> psusi, you would be free to come to the session and discuss or just put it on the adgenda, as i am happy to bring it up
[17:40] <psusi> will do
[17:40] <apw> https://blueprints.launchpad.net/ubuntu/+spec/core-1311-kernel
[17:40] <psusi> as an added benefit, the ext4 driver allows online resize on ext2 filesystems, which the ext2 driver can't handle
[17:40] <apw> that is the one it needs to be associated with
[17:40] <apw> psusi, heh ... don't frighten me
[17:41] <psusi> hehe
[17:41] <psusi> I've been trying to get gparted to handle online resize and in testing noticed that I had built my kernel with the ext2/3 drivers disabled so it worked, but on a stock kernel ext2 can't do the resize online
[17:42] <apw> psusi, include that nugget
[17:43] <psusi> so I shuold report a bug and link it to that bp?
[17:44] <apw> hmmmm, i guess that might make sense if you can be bothered
[18:00] <bjf> arges, are you able to verify bug 1208740?
[18:00] <ubot2> Launchpad bug 1208740 in linux (Ubuntu Raring) "Large pastes into readline enabled programs causes breakage from kernels v2.6.31 onwards" [Medium,Fix committed] https://launchpad.net/bugs/1208740
[18:04] <antarus> bjf: that is my teams bug
[18:04] <bjf> antarus, cool, can you verify ?
[18:04] <antarus> bjf: I can have marga verify
[18:04] <antarus> won't be until tomorrow pobably
[18:05] <bjf> antarus, ok, it has been waiting for verification for over a week
[18:08] <antarus> I sent her a note
[18:08] <bjf> antarus, thanks much
[18:14] <antarus> no worries, we are trying to be better about this sort of thing ;)
[18:14] <antarus> mostly we just need a launchpad bot that syncs launchpad with our internal bugtracker
[18:14] <antarus> because we mostly ignore launchpad ;p
[18:14] <bjf> antarus, i can relate to that
[18:20] <arges> bjf: looking
[18:20] <arges> bjf: i'll do this today
[18:21] <bjf> arges, thanks
[18:22] <xnox> apw: i think debian starting building with  CONFIG_EXT[23]=n, i'll check.
[18:22] <apw> xnox, thanks
[18:44] <nhm> I've got 13.04 and am trying to use the dwarf support in perf (ie "-g dwarf").  It appears that this isn't enabled in the 3.11.0-12-generic version of perf I have.  Was NO_LIBUNWIND set when that version of perf was built?
[18:45] <nhm> or maybe the build machine didn't have libunwind?
[18:48] <apw> likely the latter
[18:48] <apw> nhm, could you file a bug and put some details in it, and ping me the number, file it against linux
[18:52] <nhm> apw: sure, will do
[19:13] <nhm> apw: I'm afraid I' don't file launchpad bugs very often, so hopefully I did this right: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1248289
[19:13] <ubot2> Launchpad bug 1248289 in linux (Ubuntu) "Missing libunwind support in perf" [Undecided,New]
[19:14] <bjf> nhm, looks good
[19:22] <qengho> apw: not necessarily new bug. It's new hardware.
[19:23] <qengho> referring to mine of 2 hours ago.  Just submitting now.