[11:54] <AnAnt> Hello
[14:42] <pmatulis> how can i more info on what's happening at the kernel level during the shutdown process?  i have a system that sometimes hangs at the very end of the shutdown
[15:24] <cking> pmatulis, it could be that acpi S5 shutdown fails.
[15:25] <pmatulis> cking: any way to get extra kernel debug logs (to a file)?
[15:27] <pmatulis> cking: i see that if i use boot option '--debug', stuff does end up in /var/log/debug, but this seems more for services
[15:27] <cking> well, one could try and bypass this by using apm to shutdown (which is ugly workaround).  I generally shove debug into the kernel at this point to see why it's not working. 
[15:28] <pmatulis> cking: your debug different than mine?  ;)  (or special debug kernel?)
[15:28] <cking> pmatulis, try kernel parameter "apm=power-off"   (I've never tried this) 
[15:29] <cking> this should shut the machine down using the old BIOS APM mechanism.
[15:29] <pmatulis> cking: also, this is wubi.  some special shutdown issues can arise?  (releasing the underlying file?)
[15:30] <mjg59> cking: Wurgh. I'm pretty sure we'll refuse to touch apm if the system's booted with ACPI
[15:30] <cking> mjg59, ok 
[15:31] <mjg59> pmatulis: Does it work if it's booted raw (ie, non-wubi)?
[15:31] <mjg59> pmatulis: There's some potential for things to go wrong during shutdown if / relies on fuse stuff that's no longer there
[15:31] <pmatulis> mjg59: not sure, customer system
[15:32] <cking> yep, factor out the wubi complexity first
[15:32] <pmatulis> is there a special debug kernel somewhere?
[15:36] <cking> pmatulis, no, we generally have to ask a kernel engineer to cruft one up.
[15:38] <pmatulis> cking: k
[15:39] <cking> apw, ^ any chance of generating a debug kernel for pmatulis?
[15:56] <JFo> hi skaet :-D
[15:56] <skaet> hi JFo,  no bug list for you yet, ;)
[15:57] <JFo> :-) I thought not... I suspect you, much like me, got caught up in tons of other stuff
[15:57] <JFo> no problem :-)
[15:58] <skaet> will plan on hiding out somewhere this afternoon, and see what interesting things I can find...  :P
[15:59] <JFo> ok :)
[15:59] <JFo> skaet, you know... I'm ok if you don't find any too :-P
[16:00] <skaet> lol,  indeed.
[18:03] <ekoore> hi to all
[18:03] <ekoore> i have a question
[18:03] <ekoore> in what way i can disable a interrupt in the kernel?
[18:08] <ekoore> can you help me?
[18:22] <JFo> hi ekoore 
[18:22] <JFo> may be a while before someone responds
[18:23] <JFo> we are all at a series of meetings that last all week
[18:23] <JFo> from what I am being told, there may be some sort of masking possible
[18:24] <JFo> but it is difficult to answer off the top of the head
[18:26] <ekoore> is possible disable  a interrupt of the kenrel, from grub?
[18:28] <JFo> not that I am aware of currently ekoore 
[18:28] <JFo> I can ask, but I am pretty sure the person who would possibly know is offline just now
[18:28]  * JFo makes a note
[18:29] <ekoore> is a long story
[18:29] <ekoore> i have the file rc.local with a script that disable gpe11
[18:29] <JFo> ok
[18:29] <ekoore> rc.local is executte in the end of the boot process
[18:33] <JanC> that's about ACPI interrupts?
[18:37] <Kano> hi, are the changes files for the kernels stored somewhere?
[18:40] <JFo> what do you mean exactly Kano?
[18:40] <Kano> well when i only want to fetch a kernel from u repo it would be nice to parse the files
[18:40] <JFo> what changes were added between kernels?
[18:40] <Kano> no the changes file you get when you create a deb
[18:41] <Kano> there you get checksum + names of the packages
[18:41] <JFo> so the generated changelogs from the deb builds?
[18:41] <Kano> basically signed, but i dont need the signed ones
[18:41] <Kano> the changelog is there too yes
[18:41] <Kano> or is there an extra repo only with kernels?
[18:42] <JFo> hmmm, they should be available in Launchpad
[18:42] <Kano> as ppa?
[18:42] <Kano> i want something that i could parse...
[18:43] <JFo> one sec...
[18:43] <Kano> since the kernel does not disable hpa by default i would not need to recompile em
[18:43] <Kano> i hated that default
[18:43] <JFo> it will be in the build directory as a link
[18:44] <JFo> from launchpad.net/ubuntu/+source/linux
[18:44] <Kano> the the build dir always the same?
[18:44] <bjf> Kano, does http://bazaar.launchpad.net/~ubuntu-archive/ubuntu-archive-tools/trunk/annotate/head:/sru-report show you how to do what you want?
[18:44] <JFo> well, you would select the specific build you want from there
[18:45] <Kano> i want to write a script that fetches the latest kernel only
[18:46] <Kano> this time the ones for natty
[18:46] <Kano> but no udebs
[18:47] <Kano> and i only need the generic(-pae) ones
[18:47] <kamal> Kano: you can get the .changes file this way:   https://launchpad.net/ubuntu/+source/linux  , then click the arrow next to the kernel version under "The Natty Narwhal",  then select one of the builds (amd64, armel, i386) ...
[18:47] <kamal> Kano: that'll take you to a page e.g. https://launchpad.net/ubuntu/+source/linux/2.6.37-12.26/+build/2125796  which has a link to the .changes file itself.
[18:48] <Kano> ah there are the changes
[18:49] <kamal> Kano: yeah, launchpad sure makes you work to find that :-)
[18:49] <Kano> well not really optimal for scripts...
[18:49] <Kano> click there ;)
[18:50] <kamal> Kano: agreed
[18:51] <Kano> it would be too simple when the changes files would be uploaded
[18:51] <Kano> in the repo
[18:57] <Kano> hmm i think i can parse it
[18:57] <Kano> when the website will be still the same...
[19:01] <Kano> wget -qO- https://launchpad.net/ubuntu/+source/linux|grep listing-archive-extra|head -1|sed 's/href=//;s/"//g'|wget -B https://launchpad.net -i- -qO-|grep \\.deb  
[19:01] <Kano> something like that a bit more optimized then
[19:03] <Kano> thx