[00:10]  * away_Sgiomlairea is now away - Reason : dinner
[02:44]  * Sgiomlaireachd is no longer away : Gone for 2 hours 34 minutes 41 seconds
[07:30] <lucent> ping?
[07:33] <JFo> lucent, is there anyone in particular you want to ping? If you have a question, just ask. 
[07:37] <lucent> JFo: thanks, when I disconnect a firewire device from one of my controllers, all controllers stop working correctly
[07:37] <lucent> dmesg is kind of quiet though, I only see the storage layer complain
[07:38] <lucent> how do I get more info about firewire? 
[08:00] <lucent> crickets.  hence the ping?
[08:47] <lag> lucent: Can you paste me the output of lsmod at paste.ubuntu.com please?
[08:48] <lucent> lag: one moment, will do
[08:49] <lucent> lag: http://paste.ubuntu.com/508598/
[08:49] <lag> lucent: Obviously with the Firewire controller up and working
[08:50] <lag> Okay, that's good
[08:50] <lag> Wait one
[08:51] <lucent> I have a ricoh chipset that's built into the laptop, and an expresscard with a TI chipset
[08:52] <lucent> since using the new firewire stack my problems are data corruption on either one or both, after removing a storage device from either firewire bus
[08:52] <lucent> old firewire stack never showed these problems for me.
[08:52] <lag> lucent: Issue: echo 1 | sudo tee -a /sys/module/firewire_ohci/parameters/debug
[08:53] <lucent> lag: okay, no output
[08:54] <lag> Try: echo -1 | sudo tee -a /sys/module/firewire_ohci/parameters/debug
[08:54] <lucent> output "-1"
[08:56] <lag> If that doesn't work paste me the result of "ls /boot/config-`uname -r`"
[08:56] <lucent> /boot/config-2.6.35-22-generic
[08:57] <lag> Yes, cat that file and paste me the output
[08:57] <lucent> oh okay! 
[08:57] <lag> By the way, when you issued "echo -1 | sudo tee -a /sys/module/firewire_ohci/parameters/debug" did you then unplug your Firewire device and check your logs?
[08:58] <lucent> lag: http://paste.ubuntu.com/508602/
[08:58] <lag> All that command does is place the Firewire module into debug mode
[08:58] <lucent> and no sir, I didn't know that I should... 
[08:58] <lag> Sorry, I assumed too much :)
[08:58] <lag> That's what you need to do
[08:58] <lag> Let me check your .config
[08:59] <lag> That's good - you have CONFIG_FIREWIRE_OHCI_DEBUG=y
[09:00] <lucent> lag: I am willing and motivated to reproduce this bug again with firewire debug on, take logs, whatever but I'm just needing some help like you have said to get that information :)
[09:01] <lag> dmesg should be sufficient 
[09:02] <lucent> dmesg at http://paste.ubuntu.com/508603/
[09:02] <lag> And now you have your output :)
[09:03] <lag> Is there anything else I can help you with? ;)
[09:04] <lucent> that's fantastic
[09:04] <lucent> in theory should I be able to unload the firewire modules ?
[09:04] <lucent> I've tried and it led to kernel panic
[09:05] <lag> Are you able to paste the panic?
[09:05] <lucent> I don't know that it will panic again if I do so again this time, but is firewire supposed to be unloadable at runtime?
[09:05] <lucent> "so... would it be a bug if I did get a panic?" is my question 
[09:05] <lag> Yes
[09:05] <lag> Any panic is a bug
[09:06] <lucent> good to know, then.
[09:06] <lucent> thank you for the advice. I will go try to catch this bug and report 
[09:06] <lag> Thank you
[09:07] <lag> Insure to attach the pastes you've sent me
[09:07] <lag> They would be helpful
[10:29] <JFo> well, I updated my Maverick box and everything that was working nicely has gone to crap now
[10:36]  * ikepanhc try to remember when I pushed the upgrade button...
[10:36] <lag> JFo: Such as?
[10:36] <ikepanhc> ah, I updated 7hr ago...
[10:39] <JFo> general sluggishness
[10:39] <JFo> diagnosing now
[10:41] <JFo> looking like it may be rhythmbox badness
[10:42] <JFo> as that is the last of the items to test across all of my trials
[10:45] <JFo> doing a final test to see
[10:49] <JFo> yep, rhythmbox is effing hosed
[10:50] <JFo> playing through a song and suddenly it stops playing. go to the interface and it appears to be set to play, but clicking the pause button causes the song to start for a second then go to the next song
[10:50] <JFo> while looking, for all intent and purpose as if it were paused
[10:51] <JFo> which explains some of the other oddities I have been seeing tonight
[11:17] <lag> JFo: I thought you used musica
[11:22] <tgardner> smb, can you look at bug #644452 ? It appears that rfkill is the root of this guys problem. Had the HP platform driver changed from Lucid to Maverick?
[11:22] <ubot2> Launchpad bug 644452 in linux (Ubuntu) "Atheros AR928X not connecting on wireless HP G60-468CA (affects: 10) (dups: 3) (heat: 253)" [Undecided,New] https://launchpad.net/bugs/644452
[11:23] <smb> tgardner, Let me have a look. I haven't followed that driver
[11:27] <JFo> lag, pete uses musica
[11:27] <lag> Ah, okay
[12:00] <avruser> Hi, people!
[12:04] <avruser> I have a problem with debugging kernel crash on 8.04.4.
[12:05] <avruser> I got crash dump with kdump, and trying to debug it with crash utility.
[12:06] <avruser> crash utility exit with error:
[12:06] <avruser> please wait... (gathering module symbol data)a)
[12:06] <avruser> crash: invalid kernel virtual address: 4a2001  type: "pgd page"
[12:09] <lag> avruser: What kind of crash are you trying to debug?
[12:13] <avruser> Kernel panic - not syncing: Fatal exception in interrupt
[12:14] <lag> Okay, can you past your dmesg at paste.ubuntu.com please?
[12:14] <avruser> ok
[12:20] <avruser> http://paste.ubuntu.com/508708/
[12:20] <lag> I don't see a panic?
[12:21] <avruser> this is current dmesg
[12:22] <lag> Perhaps I should have been more clear :)
[12:22] <lag> Can you paste the panic?
[12:23] <lag> If it's not in the current dmesg, it will most likely be in /var/log/kern.log or /var/log/messages
[12:23] <lag> (or both)
[12:24] <avruser> ok
[12:24] <lag> Thanks
[12:32] <avruser> Panic was not logged in any log files, but at the moment of crash on the monitor appears this messages:
[12:32] <avruser> Code: Bad EIP value
[12:32] <avruser> EIP: [<0000 0000>] 0x0 SS:ESP 0068:c043bf14
[12:32] <avruser> Kernel panic - not syncing: Fatal exception in interrupt
[12:36] <avruser> http://paste.ubuntu.com/508716/
[12:36] <avruser> part of kern.log at time of crash
[12:44] <lag> avruser: It's hard to say whether that last line is related to the crash
[12:45] <lag> avruser: I need the lines prior to "Code: Bad EIP value" to make any sense of it
[12:45] <lag> avruser: Did it dump the at any point? A list of function names
[12:47] <lag> avruser: Have you changed any hardware recently? A Bad EIP value can be related to dodgy hardware; NICs, ATA Disks etc
[12:48] <avruser> I was used bluetooth dongle
[12:48] <lag> Try and use it again
[12:48] <lag> See if you can replicated the issue - narrow it down to a piece of hardware
[12:48] <lag> Bad RAM can cause the EIP issue too
[12:49] <avruser> I can replicate this crash
[12:49] <lag> How?
[12:50] <lag> s/Did it dump the at any point/Did it dump the stack at any point
[12:50] <avruser> It happens then i pass voice through the usb bluetooth dongle
[12:51] <lag> Shouting at it?
[12:51] <lag> I'd kernel panic if you shouted at me too :)
[12:52] <avruser> :)
[12:52] <lag> I'd need more information if I was going to rectify this
[12:52] <lag> What were the lines preceding "Code: Bad EIP value"
[12:53] <avruser> OK, I need to connect monitor to my server
[12:57] <lag> avruser: Is there any solid reason why your server is still running Hardy?
[13:10] <avruser> 'cause LTS
[13:10] <lag> So is Lucid :)
[13:10] <avruser> I need very stable system
[13:11] <avruser> hardy got many patches
[13:11] <lag> Did you install dahdi yourself?
[13:11] <avruser> yes
[13:11] <avruser> I got some trace from my screen:)
[13:12] <lag> Good, good
[13:12] <apw> avruser, the number of patches is pretty much proportional to age of the release
[13:13] <lag> avruser: I think people would be even more inclined to help you if you didn't have such an old OS, despite the fact that we're still supporting it
[13:13] <lag> Besides, I think your problem my lie in dahdi
[13:13] <lag> I've just installed it
[13:13] <lag> Going to have a play
[13:14] <avruser> I experience this problem only when i make call through the chan_mobile
[13:15] <avruser> this module use bluetooth stack
[13:16] <lag> How can I do that?
[13:16] <lag> Do I need specific hardware to do that?
[13:16] <lag> I have a bluetooth enabled phone and a dongle?
[13:16] <avruser> This enough
[13:17] <avruser> Have you chan_mobile compiled?
[13:17] <lag> I also have dahdi installed
[13:17] <avruser> From asterisk-addons 1.6.2
[13:17] <lag> In the repos? Or from source?
[13:18] <lag> Just installed asterisk-1.6.2
[13:20] <avruser> 8.04.4 have not asterisk-1.6 and addons-1.6 in off repo
[13:20] <avruser> I have installed from source
[13:20] <lag> I can't see addons
[13:20] <lag> But the asterisk-1.6 is in the Lucid repos
[13:21] <lag> I've just installed it
[13:21] <lag> Now how do I reproduce this bug?
[13:22] <lag> Connected to Asterisk 1.6.2.5-0ubuntu1 currently running on computer (pid = 15415)
[13:23] <avruser> Do you have chan_mobile?
[13:23] <avruser> asterisk -r
[13:23] <lag> I did that
[13:23] <lag> I have CLI now
[13:24] <lag> computer*CLI> channel 
[13:24] <lag> originate  redirect   request 
[13:24] <avruser> module show like chan_mobile.so
[13:24] <lag> Where?
[13:24] <avruser> in CLI
[13:24] <lag> cmd?
[13:24] <avruser> yes
[13:25] <lag> system1*CLI> chan_mobile.so
[13:25] <lag> No such command 'chan_mobile.so' (type 'core show help chan_mobile.so' for other possible commands)
[13:25] <avruser> 'module show like chan_mobile.so' command
[13:26] <avruser> what version of kernel?
[13:27] <lag> It would help if the modules were listed in lexicographical order
[13:27] <lag> chan_phone.so                  Linux Telephony API Support              0
[13:28] <avruser> Did you installed asterisk-addons?
[13:28] <lag> http://paste.ubuntu.com/508753/
[13:28] <lag> No
[13:28] <lag> It wasn't there
[13:30] <lag> http://paste.ubuntu.com/508754/
[13:30] <lag> Perhaps asterisk-mobile
[13:31] <lag> avruser: Nope
[13:31] <avruser> yes, maybe 
[13:32] <lag> It's still not there
[13:32] <lag> Are you sure it's not been renamed to -phone?
[13:33] <avruser> did you installed asterisk-mobile?
[13:33] <lag> Yes
[13:34] <avruser> restart asterisk?
[13:34] <lag> Why don't you email me the module?
[13:34] <lag> /usr/lib/asterisk/modules/chan_mobile.sh
[13:34] <lag> /usr/lib/asterisk/modules/chan_mobile.so
[13:34] <avruser> no problem
[13:35] <avruser> lag: can we complete this tomorrow?
[13:35] <lag> We can continue on Monday
[13:35] <lag> I might be around tomorrow
[13:35] <lag> But I can't promise 
[13:36] <avruser> Thanks:)
[13:36] <lag> Can you email me the commands that you use to replicate this bug
[13:37] <avruser> sure
[13:38] <avruser> Good Bye!
[14:01] <lucent> how do I get the full dmesg output?  man page for dmesg hints at -s option, however I can find no example of this
[14:17]  * ericm|ubuntu reconnects
[15:06] <vanhoof> ogasawara: \o/
[15:06] <vanhoof> ogasawara: you made my week
[15:06] <vanhoof> lol
[15:06] <vanhoof> progress++
[15:06] <ogasawara> heh
[15:07] <ogasawara> vanhoof:  cking did all the leg work testing :) , but it indeed sounds promising
[15:08] <lag> Is there a (ex or currently) release manger around that can spare me a couple of minutes? 
[15:08] <ogasawara> lag: as in the entire distro release manager? or kernel release manager? or ....?
[15:09] <cooloney> lag, kernel release manager = ogasawara
[15:10] <lag> Anyone with release manager permissions on LP :)
[15:10] <lag> Yes, I know that cooloney :)
[15:10] <ogasawara> lag: ah, that might be a different story in you need LP permissions somewhere.
[15:10] <ogasawara> lag: what do you need changed in LP?
[15:11] <lag> bug 22070
[15:11] <ubot2> Launchpad bug 22070 in linux-source-2.6.20 (Ubuntu) (and 2 other projects) "Logitech Quickcam Messenger is not usable (affects: 15) (dups: 3) (heat: 144)" [Undecided,Won't fix] https://launchpad.net/bugs/22070
[15:11] <ogasawara> whoa, 2.6.20
[15:12] <ogasawara> lag: and what do you need changes with that bug?
[15:12] <ogasawara> s/changes/changed/
[15:12] <lag> Just looking
[15:12] <vanhoof> ogasawara: well he's here with a machine in hand :)
[15:13] <lag> I need the Nominated for Mavericks removing 
[15:13] <lag> And the Lucids removing from linux-source-2.6.15 (Ubuntu) and linux-source-2.6.20 (Ubuntu)
[15:14] <ogasawara> lag: ah, so that's a quirk in launchpad that you can't remove the nomination once it's been added.  You can only decline it now.
[15:14] <lag> That seems silly
[15:14] <ogasawara> lag: it is, but I can decline them for you.
[15:15] <lag> I would have only like to add the nominated for on on line too, but it added them all :(
[15:15] <lag> That's fine :)
[15:15] <ogasawara> lag: yah, also another quirk that's annoying
[15:15] <lag> Just leave The top Lucid one
[15:15] <ogasawara> lag: ack
[15:15] <lag> Thanks Leann
[15:15]  * ogasawara wonders if I decline a nomination for one, if it'll decline it for all
[15:16] <lag> Another stupid quirk?
[15:17] <ogasawara> well that's stupid, it does decline it for all
[15:18] <lag> Grrrr
[15:18] <lag> What about if you allow the top Lucid one?
[15:18] <ogasawara> lag: ok, so I approved the Lucid nomination which of course approved it for all the packages
[15:18] <lag> Then deline the others?
[15:18] <lag> Doh!
[15:19] <lag> Whaaaa, now what?
[15:19] <ogasawara> lag: so then I just marked the Lucid nominations for linux-source-2.6.15 and linux-source-2.6.20 as Inavlid
[15:19] <lag> Ah, okay
[15:19] <ogasawara> what a painful process
[15:19] <lag> No kidding
[15:20] <lag> Once you've declined it, can you change it again?
[15:21] <lag> I remember why I nominated it for Maverick now
[15:21] <ogasawara> lag: yep, I can approve it
[15:21] <lag> No I can split them and mark Maverick as Fix Released 
[15:21] <lag> Can you approve Maverick please
[15:21] <lag> I think I can then change then to invalid etc after
[15:21] <lag> s/then/them
[15:22] <ogasawara> lag: sure, although it's sorta implied it's already Fix Released for Maverick
[15:22] <ogasawara> lag: as the linux task itself always reflects the actively developed release, ie Maverick at the moment
[15:24] <ogasawara> wow, so I approved it and it propagates the status automatically.
[15:25]  * lag tuts
[15:25] <lag> Oh, you mean Fix Released
[15:26] <ogasawara> lag: right
[15:26] <lag> Weird 
[15:26] <ogasawara> lag: so for example the linux-source-2.6.15 package being Fix Released for Maverick makes no sense
[15:27] <lag> Yep, just seen/changed that
[15:28] <lag> Neither does the "Status tracked in Maverick"
[15:28] <ogasawara> yah, that's confusing too
[15:28] <lag> Okay, I think that's correct now
[15:29] <lag> Why does the "linux-source-2.6.15 (Ubuntu)" have to be different?
[15:29] <lag> And has no dropdown?
[15:30] <ogasawara> lag: I think that's due to the nominations now, eg each nomination has a dropdown
[15:31] <lag> None of them are the same
[15:31] <lag> Top one is "Status tracked...", but is white
[15:32] <lag> The second one is the same, but yellow
[15:32] <lag> And the last one is while with a dropdown
[15:32] <lag> And is Won't fix
[15:32] <ogasawara> lag: the yellow highlight is due to the way the url is crafted
[15:32] <ogasawara> lag: eg https://bugs.edge.launchpad.net/ubuntu/+source/linux-source-2.6.15/+bug/22070 points to the linux-source-2.6.15 package and thus highlights it
[15:32] <ubot2> Launchpad bug 22070 in linux-source-2.6.20 (Ubuntu Maverick) (and 8 other projects) "Logitech Quickcam Messenger is not usable (affects: 15) (dups: 3) (heat: 142)" [Undecided,Invalid]
[15:37] <lag> Ah, okay
[15:38] <lag> bug 22070
[15:38] <ubot2> Launchpad bug 22070 in linux-source-2.6.20 (Ubuntu Maverick) (and 8 other projects) "Logitech Quickcam Messenger is not usable (affects: 15) (dups: 3) (heat: 140)" [Undecided,Invalid] https://launchpad.net/bugs/22070
[15:39] <lag> But the bug relates to linux-source-2.6.20
[15:39] <lag> Odd
[15:45] <ogasawara> lag: I'm guessing the bot just picks up the last package in the set of bug tasks
[15:45] <lag> Stupid bot :)
[17:20] <tgardner> apw, bug #642241
[17:20] <ubot2> Launchpad bug 642241 in initramfs-tools (Ubuntu) "package initramfs-tools 0.92bubuntu78 [modified: usr/sbin/update-initramfs] failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 (affects: 1) (heat: 269)" [Undecided,New] https://launchpad.net/bugs/642241
[17:24] <tgardner> bug #642421
[17:24] <ubot2> Launchpad bug 642421 in linux (Ubuntu) "Maverick could not load /lib/modules/2.6.35-22-generic/modules.dep (affects: 41) (dups: 2) (heat: 206)" [Medium,Confirmed] https://launchpad.net/bugs/642421
[19:22] <mpoirier> friends, how do I generate the [PATCH 0/0] such as this one http://paste.ubuntu.com/508973/ when submitting multipile patches ?
[19:23] <bjf> mpoirier, have you tried "git format-patch --cover-leter" ?
[19:26] <mpoirier> bjf: will this command generate the information I have in the paste bin ?
[19:26] <bjf> mpoirier, try it
[19:27] <bjf> mpoirier, i am assuming that you use git format-patch to create your patches?
[19:27] <mpoirier> yes.
[19:27] <mpoirier> Now I need to generate the final 0/0.
[19:27] <bjf> mpoirier, just add --cover-letter to the options you are already use
[19:28] <mpoirier> ok, I'll try.
[19:47] <mpoirier> bjf: git format-patch --cover-letter HEAD~6..HEAD will do the trick.
[19:47] <mpoirier> thanks for the tip.
[19:48] <bjf> mpoirier, git format-patch --cover-letter -6
[19:48] <bjf> mpoirier, also: git format-patch --cover-letter HEAD~6...
[19:50] <mpoirier> bjf: indeed, they all seem to have the same effect.
[20:01] <ogasawara> kees: hrm, for the day 0 Maverick kernel upload which is primarily CVE fixes, I was originally going to upload to -proposed and then get it immediately promoted to -updates.  But does it need to get to the -security pocket as well?
[20:01] <kees> ogasawara: yup. but we can pocket-copy it there too.
[20:01] <ogasawara> kees: ok cool
[20:02] <kees> ogasawara: this early in the cycle I'm not worried about build dep problems due to building in the regular queue vs security queue
[20:02] <kees> for anything other than a 0day SRU, I'd be nervous :)
[20:02]  * ogasawara nods