[06:56]  * smb adjusts coffee level
[07:15] <ppisati> moin
[07:40] <dileks_> moin moin
[07:40] <dileks_> build_kernel-with-deb-pkg.sh: http://paste.debian.net/164589/
[07:41] <dileks_> might be interesting for people wanting to test upstream GIT kernels
[07:43] <ohsix> there's already an autobuilder for them
[08:16] <dileks_> ohsix: can you give me more infos or a url?
[08:17] <ohsix> https://wiki.ubuntu.com/Kernel/MainlineBuilds
[08:17] <ohsix> that article is pretty crusty, but it links to t he right places
[08:28] <dileks_> ohsix: thanks!
[08:28] <dileks_> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2012-04-22-precise/
[08:28] <dileks_> nice :-)
[08:50] <dileks_> http://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2012-04-22-precise/BUILT
[08:51] <dileks_> Release: lucid ? (VS. built for precise?)
[08:52] <ohsix> the wiki article explains how they're built
[09:03] <dileks_> ohsix: what do you mean by "pretty crusty"? partially outdated?
[09:12] <dileks_> just fyi: CONFIG_FB_VESA is now boolean
[09:12] <dileks_> if not set =y ...
[09:12] <dileks_> config-3.4.0-997-generic:# CONFIG_FB_BOOT_VESA_SUPPORT is not set
[09:12] <dileks_> config-3.4.0-997-generic:# CONFIG_FB_VESA is not set
[09:14] <dileks_> this leads here to black screen (unity login screen should appear, after pressing return I get into unity login screen)
[09:14] <dileks_> config-3.4.0-rc4-2-generic:CONFIG_FB_BOOT_VESA_SUPPORT=y
[09:14] <dileks_> config-3.4.0-rc4-2-generic:CONFIG_FB_VESA=y
[09:14] <dileks_> (from my kernel)
[09:19] <apw> dileks_, indeed that is telling you the compile environment, the -precise tells you the config environment used
[09:20] <dileks_> OK, with release I understood (for) distribution (== precise)
[09:21] <dileks_> ohsix: the autobuild-service is really nice, but I tend to use my script for building custom-kernels
[09:25] <dileks_> not sure if I read here about it...
[09:25] <dileks_> Apr 23 11:08:20 fambox kernel: [    0.294037] pnp 00:0b: can't evaluate _CRS: 12311
[09:26] <dileks_> saw this with my 3.4-rc4 and drm-intel-netx_precise-current
[09:28] <ohsix> the wiki article also says they're unsupported, but you are more likely to be able to file a bug with upstream with them
[09:31] <dileks_> ...will do after a quick look into the sources (and find maintainers with get_maintainer.pl)
[09:32] <ohsix> what you pasted is a bios problem, i don't remember what method _CRS is, but since 'pnp' is there, and the machine still runs, probably not an important one
[09:33] <dileks_> yeah, saw some acpi error or even bugs
[09:34] <dileks_> [    0.241572] [Firmware Bug]: ACPI: BIOS _OSI(Linux) query ignored
[09:34] <dileks_> [    0.279385]  pci0000:00: ACPI _OSC request failed (AE_ERROR), returned control mask: 0x1d
[09:34] <dileks_> [    0.294032] ACPI Error: Invalid/unsupported resource descriptor: Type 0x00 (20120320/utresrc-650)
[09:34] <apw> bug #987052
[09:34] <ubot2> Launchpad bug 987052 in linux "WARNING: at /build/buildd/linux-3.2.0/kernel/softirq.c:159 local_bh_enable_ip+0x7a/0xa0()" [High,Confirmed] https://launchpad.net/bugs/987052
[09:43] <cking> the _OSC request failed occurs when bit 1 of the returned buffer from _OSC is set indicating "Platform Firmware was unable to process the request or query." - which is most likely to be a firmware issue
[09:50] <cking> and the invalid/unsupported resource descriptor is another firmware bug, types 1, 2 or 3 are allowed and for some reason it is set as type 0 (invalid)
[09:50] <dileks_> https://lkml.org/lkml/2012/4/23/105
[09:54] <cking> dileks_, so the "invalid/unsupported resource descriptor" message is due to extra checking added in commit e0fe0a8d4ed5474261d0ee1452f5d9ae77236958 which was part of the ACPI 5.0 updates
[09:54] <cking> nothing new really, same old buggy firmware
[09:54] <dileks_> cking: thanks for your explanations!
[09:55] <dileks_> this is a samsung series-5 ultrabook
[09:55] <cking> why doesn't that surprise me...
[09:57] <dileks_> currently, I even cant find the url for firmware-upgrades
[09:57] <dileks_> my bookmark is showing to nirvana
[10:16] <dileks_> lol, within a few weeks there is now A04 that why I could not find my A01
[10:17] <dileks_> http://www.samsung.com/de/support/model/NP530U3B-A04DE
[10:29] <cking> that's mad
[10:39] <brendand_> apw - during the Q cycle, are you guys going to be backporting the Q kernels to P via the SRU process or some other way?
[10:39] <ppisati> brendand_: you mean, backports?
[10:40] <apw> brendand_, we will be doing LTS backport kernels, i am not sure it is clear how those will be delivered given the other backport plans
[10:40] <apw> but they will exist
[10:40] <brendand> apw, so it will be a case of you have to opt-in?
[10:40] <brendand> apw, like you do with backports now
[10:40] <apw> brendand, you always have to opt in to the backports as far as i know ... indeed
[10:41] <brendand> apw, see i thought this was different, as in the Q kernel would be officially supported
[10:41] <brendand> in P
[10:42] <brendand> and that you would get it when you do a normal upgrade
[10:42] <apw> brendand, the backports kernels are supported, you still have to opt-in
[10:43] <brendand> apw, is there a difference then?
[10:43] <apw> brendand, as far as i know there is not a difference in the model, you will be able to opt-in to the kernels and they will be supported, they may not be delivered in the exact same way
[11:43]  * ppisati -> lunch
[11:49] <Kano> hi, could somebody backport efi stub to 3.2?
[11:49] <Kano> also it should be enabled for 3.3+
[11:51] <Kano> i guess it is a simple backport
[12:00] <dileks_> cking: I could upgrade BIOS from 05XK to 06XK, but the pnp/_CRS warning is still there
[12:01] <Kano> hi tgardner ,did you test efi stub mode yet?
[12:03] <tgardner> Kano, afaik. I think some Dell machines have issues still.
[12:03] <Kano> does not really matter
[12:03] <Kano> but you can enable that feature
[12:03] <Kano> for 3.3+
[12:04] <Kano> for those who know how to use it
[12:04] <Kano> a backport would be best
[12:05] <tgardner> Kano, ain't gonna happen for 12.04. you'll have to wait for the first LTS backport kernel.
[12:05] <Kano> ok, will try to backport on my own. but how about enabling it for mainline kernel?
[12:05] <Kano> i always have to recompile it even for pure intel systems...
[12:06] <tgardner> Kano, I'll check with apw about it.  I'm just looking at Q to see if its enabled.
[12:06] <tgardner> CONFIG_EFI_STUB=y
[12:06] <Kano> yes
[12:07] <Kano> just a tiny bit huger
[12:10] <apw> tgardner, i'll put it on my todo
[12:18] <cking> dileks, that _CRS error code 12311 is 0x3017 -> AE_AML_INVALID_RESOURCE_TYPE - so once again it's buggy resource type info returned when evaluating the _CRS  :-/
[13:03] <cking> dileks, not sure what device PNP0C02, it seems to map to  "General ID for reserving resources required by Plug and Play motherboard registers." so that's a bit nebulous 
[13:04] <mjg59> It's just resources that are used by the platform but not expected to be touched by the OS
[13:04] <mjg59> Although sometimes it covers PCI space
[13:05] <mjg59> The error's probably harmless
[13:05] <mjg59> Although it's probably worth checking to make sure that any valid resources returned in the same call are still parsed
[13:12] <cking> mjg59, ok - so if the firmware is returning a bad _CRS with an invalid resource type it's just too bad, blame it on the firmware and complain to the vendor..
[13:13] <mjg59> cking: Yeah, but if it's returning a list of resources then we shouldn't ignore all of them just because one is invalid
[13:13] <mjg59> But I haven't checked whether the code does that
[13:13] <Kano> apw: could you at least touch the missing include, that would already help
[13:15] <Kano> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/942569
[13:15] <ubot2> Launchpad bug 942569 in linux "binary headers packages are missing include/generated/compile.h" [Low,In progress]
[13:15] <Kano> the content does not really matter, a 0 size file is enough
[13:15] <Kano> would fix nvidia dkms
[13:28] <apw> we may as well fix nvidia to not include it if a 0 length file is sufficient
[13:28] <apw> i would prefer to fix the kernel package right if it is missing files
[13:33] <Kano> apw: it happens when you use u packageing + debian nvidia dkms
[13:33] <Kano> that way it wants that file
[13:33] <Kano> i think one other module wanted it as well but can not remember
[13:34] <Kano> u nvidia dkms is not affected
[13:34] <Kano> but that is not compatible with debian kernels
[13:35] <Kano> i dislike to have to 2 differnet dkms.conf depending on the kernel used
[13:35] <Kano> definitely u packageing is broken. hotfix would be a touch
[13:42] <Kano> apw: what script creates the config for the u mainline builds?
[13:43] <Kano> you updated 3.4rc4?
[13:44] <Kano> ah that has efi stub, nice
[13:46] <Kano> a bit bad that you need to extract rdev from an old util-linux package
[13:47] <Kano> when you use it for efibootmgr you need it
[13:48] <cking> mjg59, looks like pnpacpi_parse_allocated_resource() uses acpi_walk_resources() which bails out if pnpacpi_allocated_resource() hits an unknown resource type :-/
[13:55] <mjg59> cking: That may not be ideal
[14:01] <cking> mjg59, one is kind of screwed at that point, an invalid resource type means one can't figure out what kind of resource it was, hence you can't determine where the next one is, so bailing out is probably the best option rather than trying to scan along the buffer and try and find the next valid resource type data structure. Hence if the firmware got it wrong, too bad
[14:03] <mjg59> Ah, true.
[14:03] <mjg59> A dump of the ACPI tables might be nice
[14:04] <mjg59> Just to see what iasl makes of it
[14:06] <cking> dileks, can you run "sudo acpidump > acpidump.log" and then "pastebinit acpidump.log" and put the URL in the channel
[14:25] <Kano> apw: can you rebuild 3.3.3 with efi stub
[14:25] <Kano> 3.4rc3 rebuild has it
[14:37] <tgardner> ogasawara, I'm working on 3.2.16, OK ?
[14:38] <tgardner> 'cause I see you've pushed a day-0 branch
[14:38] <tgardner> or at least I think it was you
[14:38] <ogasawara> tgardner: ack
[14:39] <ogasawara> tgardner: I'll do 3.4-rc4 then for Q, assuming you haven't?
[14:39] <tgardner> ogasawara, take it away
[14:39]  * dileks has to install pkg which includes acpidump
[14:40] <dileks> Kano: hi :-). drm-intel-next kernel for precise has no efi-stub activated
[14:40] <Kano> it looks that efi stub needs 2 patches
[14:41] <Kano> maybe 3
[14:41]  * ogasawara back in 20
[14:42] <Kano> well the 3rd is only in 3.4
[14:42]  * dileks installs acpidump package
[14:44] <dileks> cking: does the log contain sensitive data?
[14:44] <Kano> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git;a=history;f=arch/x86/boot/compressed
[14:44] <Kano> should be simple to use for 3.2
[14:44] <cking> dileks, just your ACPI tables - so no sweat over it
[14:46] <dileks> cking: http://paste.ubuntu.com/942586/
[14:47] <cking> mjg59, ^^
[14:47] <mjg59> dileks: What kind of machine is this?
[14:47] <mjg59> raw text needs me to log into launchpad?
[14:47] <dileks> ah the expert :-)
[14:47] <mjg59> Sigh.
[14:48] <dileks> samsung series-5 ultrabook
[14:48] <cking> oops, I forgot that
[14:48] <mjg59> No problem
[14:48] <mjg59> I need to find my password again for the plumbers CFP
[14:49] <dileks> http://www.samsung.com/au/consumer/pc-peripherals/notebook-pc/ultra-book/NP530U3B-A01AU-spec
[14:55] <mjg59> Ok, _CRS for PCI is dynamically generated
[14:55] <mjg59> So there's probably a bug in there
[14:56] <cking> for PNP0C01 _CRS is dodgy too if IGDS is false
[14:56] <dileks> so, its fixable in linux-kernel?
[15:00] <mjg59> Probably not trivially
[15:00] <mjg59> And if your machine works, probably not worth the effort
[15:04]  * cking notes its one more thing to check before firmware gets released...
[15:06] <tgardner> ogasawara, I guess you can rename the Q repo now. Quantal Quetzal
[15:07] <ogra_> can you pronounce that please ? 
[15:07] <ogra_> :P
[15:07] <ppisati> :O
[15:07] <ppisati> ‘Quantal Quetzal’
[15:08] <mjg59> Not to be confused with Quantel Paintbox
[15:08]  * ogra_ grins
[15:13] <cking> at least I can type it w/o too many errors
[15:13] <jsalisbury> http://www.youtube.com/watch?v=FO9gFAOAPFQ
[15:17] <sforshee> mjg59, I'm taking a look at radeon graphics on a macbook pro 8,2, efi boot. It seems the os x driver tries to somehow get the video rom address from EFI. Do you have any idea what it might be doing?
[15:18] <mjg59> sforshee: Nope. Only radeon one I have right now is an MBP 1,1
[15:18] <mjg59> But I could believe it's in an EFI variable somewhere, or possibly one of the systab entries is magic
[15:18] <sforshee> the machine does have a number of config tables we don't use
[15:18] <mjg59> sforshee: If there's any way you can get it accessible via ssh, I can play
[15:19] <sforshee> mjg59, sure. give me a few minutes
[15:36] <tgardner> apw, are you OK with me rebooting gomeisa? I checked that 'sudo hdparm --fibmap /boot/grub/grub.cfg' is below the 32 bit LBA limit
[15:43] <apw> tgardner, go ahead
[15:43] <apw> tgardner, go ahead
[15:53] <jsalisbury> apw, Comment #20 in bug 922906 says they hit the oops with the test kernel.
[15:53] <ubot2> Launchpad bug 922906 in linux "Kernel Oops - BUG: unable to handle kernel NULL pointer dereference at 0000009c; EIP is at __ticket_spin_lock+0x8/0x30" [Medium,In progress] https://launchpad.net/bugs/922906
[15:56] <tgardner> bjf, ayan, ppisati, jsalisbury, henrix: rebooting tangerine for kernel update
[15:57] <jsalisbury> tgardner, ack
[15:57] <henrix> tgardner: ack
[15:57] <bjf> tgardner: ack
[16:20] <tgardner> ogasawara, is 3.2.0-23.36 gonna be the release kernel on the ISOs ?
[16:20] <ogasawara> tgardner: yep
[16:20] <tgardner> ogasawara, k
[16:21] <ogasawara> tgardner: but we'll do a day-0 upload.  I intend for that to contain all patches from master-next except the v3.2.15 and v3.2.16 stable patches (as I want those to bake and go through QA)
[16:21] <ogasawara> tgardner: I've coordinated with the release team to upload the day-0 kernel to precise-proposed tomorrow
[16:22] <tgardner> ogasawara, ok, was wondering a bit what you were planning for day 0
[16:22] <bjf> ogasawara: we can package and start precise through the cadence starting next monday
[16:22] <ogasawara> tgardner: I've pushed what I intend to be in our day-0 upload to the day-0 branch in precise
[16:22] <ogasawara> bjf: ack
[16:23] <ogasawara> bjf: after I upload our day-0 I'm thinking I'll hand off precise to you guys
[16:24] <bjf> herton, henrix, sconklin ^ precise is "ours" starting this Friday. We'll turn the crank on it next week just like all the others.
[16:24] <sconklin> Whee!
[16:24] <henrix> bjf: \o/
[16:25] <ogasawara> such enthusiasm, I like it :)
[16:25] <mjg59> sforshee: Well, there does seem to be a ReadEfiRom method in the driver
[16:25] <mjg59> sforshee: Let me try to work out what it actually does
[16:28] <sforshee> mjg59, yeah, I was looking at that
[16:29] <sforshee> it makes some indirect function call, and I have no idea where it goes from there
[16:40]  * cking drinks the btrfs koolaid
[16:40] <tgardner> cking, have you started to gag yet ?
[16:40] <cking> heh, only when I lose all my data
[16:51]  * ppisati -> gym/workout
[17:20] <dileks> hmm
[17:21] <dileks> $ cat /etc/debian_version
[17:21] <dileks> wheezy/sid
[17:21] <dileks> is that intended? (ubuntu precise here)
[17:22] <tgardner> dileks, you're asking in the wrong channel. thats likely a foundations issue
[17:23] <dileks> I am trying to add some improvements to scripts/package/builddeb (shipped with linux upstream)
[17:23] <dileks> trying to determine distribution/codename
[17:28] <tgardner> dileks, have you looked at /etc/lsb-release ?
[17:29] <dileks> hmm, I could check for it
[17:29] <dileks> dunno, if debian has such a file, too
[17:41] <shadeslayer> I'm trying to package the stock ubuntu kernel with a couple of changes and patches, but when I try to set CONFIG_DRM_I915=y in debian.master/config/config.common.ubuntu ... it keeps getting reset to CONFIG_DRM_I915=m during the build
[17:41] <shadeslayer> any ideas how to fix?
[17:43] <bjf> shadeslayer: take a look at: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[17:43]  * shadeslayer looks
[17:44] <shadeslayer> ah ok
[17:48] <shadeslayer> bjf: btw patching works the same way as in standard debian packages right? ( put them in debian/patches )
[17:51] <bjf> shadeslayer: honestly i don't know, i've never done it that way
[17:51] <shadeslayer> oh, how have you done it?
[17:51] <bjf> shadeslayer: i modify a personal git repo to have the changes i want and i build/package that
[17:51] <shadeslayer> ok
[17:52] <shadeslayer> grrr ... CONFIG_DRM_I915 depends on other stuff that is built as a module, and then that stuff depends on other stuff that is built as a module
[18:01] <shadeslayer> herp derp
[18:01] <shadeslayer> http://paste.kde.org/462242/
[18:01] <shadeslayer> and I didn't even change the power-pc config
[18:09] <Kano> apw: all needed commits to boot 3.2 with efi stub you find there: http://kanotix.com/files/fix/efi/linux-3.2-efi-stub-patcher.sh
[18:09] <Kano> just tested and verified
[18:10] <Kano> there was one patch the might be interesting but did not cleanly apply to boot a 32 bit kernel,but for 64 bit this is definitely enough
[18:25] <shadeslayer> Are there any junior jobs that I could look at?
[18:25] <shadeslayer> something small to start off
[19:25] <orated> Could anyone brief me the difference between ubuntu-11.10-preinstalled-server-armel+omap.img and ubuntu-11.10-preinstalled-desktop-armel+omap.img ? What is the differnce in pacakges? I can see one is desktop, other server ...
[19:33] <bjf> orated: you'd get a better answer in #ubuntu-arm probably
[19:34] <orated> bjf: Okay, I'll try. Thanks
[20:32]  * tgardner -> EOD
[23:43] <miconfrink> Hey, I've been looking all over for a comprehensive guide to building "Ubuntized"custom patched  kernels
[23:44] <miconfrink> I'd like to build a Molnars Realtime Kernel with Ubuntu Patches as well
[23:44] <miconfrink> I know I could just patch and make-kpkg 
[23:45] <miconfrink> But isn't there a cleaner way to segregate the patch from the vanilla source?
[23:46] <miconfrink> Any help would be greatly appreciated :-)
[23:57] <bjf> miconfrink: : take a look at: https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel
[23:57] <bjf> miconfrink: i'd suggest starting with a clone of the tree you are interested in
[23:57] <bjf> miconfrink: you can then create a branch for all your patches if you want them kept separately
[23:58] <miconfrink> bjf: this isn't a vanilla kernel
[23:58] <bjf> miconfrink: you are starting with an ubuntu kernel, correct?
[23:58] <miconfrink> Incorrect
[23:58] <miconfrink> vanilla = from kernel.org
[23:59] <miconfrink> Ingo Molnar's patch is quite extensive
[23:59] <miconfrink> what I'm trying to figure out is where to put the patch in the debian tree