[01:09] <kengyu> ogasawara, hi, do you think will do 3.2.14 rebase before the kernel freeze?
[01:41] <Sarvatt> kengyu: http://kernel.ubuntu.com/git?p=ubuntu/ubuntu-precise.git;a=shortlog;h=refs/heads/master-next
[01:42] <kengyu> Sarvatt, ahh, cool, already done!
[01:54] <wrostek> Im having trouble with my Ubuntu Install, I was building kernels the ubuntu way, and then using dpkg -i <kernalname> to install and apt-get purge <kernelname> to remove..  Next day Ubuntu boots into lighted but freezes shortly after, no message in logs, can't ssh in.. its useless
[01:54] <wrostek> Im having trouble with my Ubuntu Install, I was building kernels the ubuntu way, and then using dpkg -i <kernalname> to install and apt-get purge <kernelname> to remove..  Next day Ubuntu boots into lighted but freezes shortly after, no message in logs, can't ssh in.. its useless
[01:55] <wrostek> Is there a way to repair the installation?
[01:58] <RAOF> wrostek: There's always a livecd.
[01:58] <RAOF> And what do you mean by “lighted”?  If you can boot into recovery mode and not have it hang then you've got the opportunity to do basically everything.
[01:59] <wrostek> RAOF what can I do? which package should I try to reinstall?
[02:00] <wrostek> I booted into recovery mode, reinstalled the kernel, unity, lightedm,  not sure what else
[02:00] <wrostek> I could reinstall
[02:00] <RAOF> That kinda depends on what's breaking.  I'd start by just booting into the original Ubuntu kernel and seeing if that works.
[02:00] <wrostek> It does not, it usually gets to the point of lighted login, or just before the login appears and stops, no hard drive light nothing.. its just dead
[02:01] <wrostek> lightdm sorry
[02:01] <wrostek> There is nothing in the log ( no errors ) so Im not sure what else I can try
[02:02] <wrostek> Is there anyway to have ubuntu reinstall all packages or something?
[02:04] <RAOF> You can run an ‘aptitude reinstall ~n’, which will reinstall all packages.
[02:04] <wrostek> do you think that would help?
[02:05] <RAOF> No, not really.
[02:06] <wrostek> Ok, is there a way to boot to console?  Maybe x is causing the problem, is there a way to test that?
[02:06] <RAOF> Recovery mode boots to console.
[02:06] <RAOF> But if you *are* booting the Ubuntu kernel which previously worked then I don't think the kernel is your problem.
[02:06] <wrostek> But it doesn't load all the other services, maybe the problem is just in x
[02:07] <wrostek> Yes, I think when I was removing old kernels something got removed with them
[02:07] <RAOF> But X hasn't changed?
[02:07] <wrostek> No, I havnt touched it
[02:08] <RAOF> I'd just try installing ubuntu-desktop (and possibly “apt-get --fix-policy install” to pull in any Recommends that have gone away).
[02:08] <wrostek> thanks, let me try
[02:10] <wrostek> fix policy installs all the recommended packages correct?
[02:13] <RAOF> Yes.
[03:11] <wrostek> HEY RAOF, thanks for your help, somehow that worked
[07:38] <ppisati> moin
[07:38] <apw> morning
[07:40] <smb> morning
[07:43]  * apw reboots to get the latest 'goodness' i may be sometime
[07:46]  * ppisati -> reboot too
[07:49] <infinity> apw: Around?
[07:49] <infinity> apw: Opinions on picking up the patch in http://www.spinics.net/lists/raid/msg37775.html ?
[07:50] <infinity> apw: Those ioctl printks are scary as all get out, until one researches them (which people shouldn't really be forced to do to prevent heart attacks)
[07:52] <infinity> apw: Picking it up for precise, and dropping it for Q would be my vote, if upstream still wants the printks there to track userspace behaviour.  But it doesn't belong in a "production" (especially LTS) kernel, IMO, to whine at me every time mdadm does something harmless.
[07:52] <apw> infinity, what you doing which triggers it, this on your ppc ?
[07:53] <infinity> apw: No, on my amd64 server.  mdadm trips over this every time it does, well, anything.
[07:53] <infinity> [3704718.535581] mdadm: sending ioctl 1261 to a partition!
[07:53] <infinity> [3704718.535587] mdadm: sending ioctl 1261 to a partition!
[07:53] <infinity> [3704726.247198] mdadm: sending ioctl 800c0910 to a partition!
[07:53] <infinity> [3704726.247204] mdadm: sending ioctl 800c0910 to a partition!
[07:53] <infinity> Etc.
[07:53] <apw> infinity, then that fix isn't enough to fix it
[07:53] <apw> as you have two ioctls there
[07:54] <apw> and are they safe ?
[07:54] <infinity> I see 7 in the patch.
[07:54] <infinity> But I'm not sure what they all map to.
[07:54] <infinity> Everywhere I look for the above, I get LKML hits saying "it's harmless reporting, ignore it", and the like.
[07:54] <apw> ahh so there is, i should open my eyes
[07:54] <infinity> But it sure doesn't LOOK harmless.
[07:55] <infinity> Not to the casual observer.
[07:55] <apw> infinity, sounds reasonable to me, i wonder if L has uploaded yesterday bulk updates
[07:55] <infinity> Hence, I suspect, SUSE carrying the above patch for SLED.
[07:55] <apw> got a reference to a clean patch is is that the only reference
[07:56] <infinity> apw: One message up in the thread, lazypants? :)
[07:56] <infinity> apw: Or do you mean a ref to a git tag or some such?  In which case, dunno, I have no idea where SUSE does their kernel work.
[09:36] <apw> infinity, got a bug number ?
[11:02] <ikepanhc> smb: could you please take a look at bug 940056
[11:02] <ubot2> Launchpad bug 940056 in debian-installer "[public] armadaxp net installer fails to properly setup initrd for raid (md)" [High,New] https://launchpad.net/bugs/940056
[11:02] <ikepanhc> smb: is that the same issue as bug 969248 ?
[11:02] <ubot2> Launchpad bug 969248 in linux "d-i: dmraid4-5 module is missing from udebs" [Medium,Fix committed] https://launchpad.net/bugs/969248
[11:08] <apw> ikepanhc, i don't think it would be ... dmraid-45 is a PC BIOS specific s/w raid configuration model i believe
[11:09] <apw> ikepanhc, and if i am reading the bug right we fail to install mdadm tools which is not in the kernel at all: 
[11:09] <apw> Note: raid devices may be detected after "sudo apt-get install mdadm && reboot"
[11:10] <ikepanhc> apw: ok, thanks.
[11:10] <ikepanhc>  I have little knowledge about netboot
[11:11] <apw> ikepanhc, i beleive netboot is very similar to an ordinary alternate image
[11:13] <ikepanhc> what I know is netboot will load Image and Initrd via tftp, because the d-i name is also incorrect in armadaxp kernel, so I just wonder if the root cause if dm-raid45.ko is not found - well, this is a wrong guess
[11:16]  * ikepanhc is reading device mapper page, looks nothing with mdadm
[11:16] <ikepanhc> s/with/about
[11:36] <dileks> hi
[11:37] <dileks> can everyone participate at the kernel-team meeting today?
[11:37] <ogra_> its in a public channel ;)
[11:52] <smb> ikepanhc, apw is right, if you are not using dmraid to set up a RAID that has been defined in BIOS it is not using dm-raid45
[11:53] <smb> madmn would use raid456 or something other md modules. Note that mdadm is completely different from device-mapper
[11:55] <smb> Also the bug seems to mix raid and dm-crypt... Are you setting up encrypted lvm or a RAID ?
[11:56] <apw> smb, doesn lvm use dm underneath ?
[11:56] <smb> lvm does but not md
[11:56] <ikepanhc> I do not with the hardware..
[11:57]  * ikepanhc review the bug again
[11:57] <smb> And usually RAID is defined using md / mdadm
[11:57] <smb> I see the log has a raid10
[11:57] <smb> but I need to read more carefully from the beginning
[12:01]  * ppisati -> lunch
[12:06] <ikepanhc> ok, I see what confused me :( md v.s. dm
[12:07] <smb> ikepanhc, This setup seems to include as much as it can for confusion
[12:07] <smb> ext4, xfs, lvm, md
[12:09] <ikepanhc> ok, so, for this bug, what I shall do is check the config and make sure the software raid is on and included in Image or Initrd
[12:09]  * ikepanhc feels little chance that raid crash after reboot
[12:12] <tgardner> jjohansen, henrix, ppisati, ayan: rebooting tangerine for kernel related update
[12:13] <jjohansen> tgardner: ack
[12:13] <henrix> tgardner: ack. logged out already
[12:31]  * smb might have missed things (since 12:09UTC)
[12:33] <apw> smb, forget to reset your router again ?
[12:34] <smb> apw, I probably have to again :/
[12:34] <smb> Once did but is seems to delevop a fancy to play dumb games around early afternoon
[12:35] <apw> t'is when BT tend to do line work for me too, so i get dropped then sometimes
[12:37] <smb> yeah, logs say I was disconnected about the time. Of course there is no reason code...
[13:54] <tgardner> ogasawara, still struggling with the Q rebase to 3.4-rc1 ?
[13:54] <ogasawara> tgardner: I am, hitting a few build failures that I'm getting cleaned up
[13:55] <ogasawara> tgardner: am gonna get precise prepped and uploaded and then get back to hammering on q
[13:55] <tgardner> ogasawara, good plan :)
[14:39]  * ogasawara back in 20
[15:08] <tgardner> ppisati, who in Q/A has panda HW ? Tobin ?
[15:24] <jsalisbury> herton, bjf, some possible regressions in 3.0.0-18: bug 972033 and bug 972529
[15:24] <ubot2> Launchpad bug 972033 in linux "After today incoming linux-image-3.0.0-18-generic upgrade cannot get my session working" [High,Confirmed] https://launchpad.net/bugs/972033
[15:25] <ubot2> Launchpad bug 972529 in linux "3.0.0-18 "everything crashing" regression" [High,New] https://launchpad.net/bugs/972529
[15:26] <bjf> jsalisbury: i've already added a comment to 972529
[15:26] <jsalisbury> bjf, great, thanks.  
[15:29]  * ppisati backs off for a bit
[15:31] <jsalisbury> bjf, herton bug 972173 looks similar 
[15:31] <ubot2> Launchpad bug 972173 in linux "Crash!" [High,Confirmed] https://launchpad.net/bugs/972173
[15:33] <jsalisbury> henrix, ^^^ Should have included you in the SRU team list.
[15:33] <henrix> jsalisbury: feel free to do it next time :)
[15:34] <jsalisbury> henrix, will do
[15:34] <tgardner> bjf, re: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/972529/comments/2 , the dmesg _is_ from a -17 kernel
[15:34] <ubot2> Launchpad bug 972529 in linux "3.0.0-18 "everything crashing" regression" [High,New]
[15:38] <bjf> tgardner: ack
[15:40] <herton> wow everything on fire, not good. I used 3.0.0-18 on Oneiric (now already on master-next -19), didn't notice anything bad, but may be it's the applications I use, don't use KDE/opera like in reports
[15:41] <henrix> my guess is that its related with PM + hda-intel driver
[15:41] <herton> I suspect "epoll: limit paths" may have something to do with it, there is a later fix for it not on -18 (93dc6107a76daed81c07f50215fa6ae77691634f), could explain this type of breakage, just a hunch though
[15:42] <henrix> oops, i was referring about the previous one, #968675
[15:47] <ogasawara> commit 79cd378824107633c86ea4cbee1253b40c967537
[15:47] <ogasawara> Author: Rick Jones <rick.jones2@hp.com>
[15:47] <ogasawara> Date:   Mon Nov 7 13:29:27 2011 +0000
[15:47] <ogasawara>     sweep the floors and convert some .get_drvinfo routines to strlcpy
[15:47] <ogasawara>     
[15:47] <ogasawara>     BugLink: http://bugs.launchpad.net/bugs/921793
[15:47] <ogasawara>     
[15:47] <ubot2> Launchpad bug 921793 in emulex "Update be2net driver in 12.04" [High,Confirmed]
[15:47] <ogasawara>     Per the mention made by Ben Hutchings that strlcpy is now the preferred
[15:47] <ogasawara>     string copy routine for a .get_drvinfo routine, do a bit of floor
[15:47] <ogasawara>     sweeping and convert some of the as-yet unconverted ethernet drivers to
[15:47] <ogasawara>     it.
[15:47] <ogasawara>     
[15:47] <ogasawara>     Signed-off-by: Rick Jones <rick.jones2@hp.com>
[15:47] <ogasawara>     Signed-off-by: David S. Miller <davem@davemloft.net>
[15:47] <ogasawara>     Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
[15:47] <ogasawara> tgardner: am getting build failures on powerpc with the above commit
[15:47] <ogasawara> tgardner: was that a clean cherry-pick from upstream or a backport?
[15:48] <ogasawara> drivers/net/ethernet/marvell/mv643xx_eth.c: In function 'mv643xx_eth_get_drvinfo':
[15:48] <ogasawara> drivers/net/ethernet/marvell/mv643xx_eth.c:1505:59: error: 'info' undeclared (first use in this function)
[15:48] <ogasawara> drivers/net/ethernet/marvell/mv643xx_eth.c:1505:59: note: each undeclared identifier is reported only once for each function it appears in
[15:48] <tgardner> ogasawara, clean. so just disbale it from power since I don't think it exists in real life.
[15:49] <ogasawara> tgardner: it looks like it should be s/info/drvinfo/
[15:49] <tgardner> ogasawara, I wonder if there is an upstream patch for it. perhaps nobody upstream actually builds it for powerpc
[15:50] <tgardner> ogasawara, hmm, not seeing anything obvious
[15:51] <ogasawara> tgardner: looks like an honest mistake based on other changes in that commit, I'll test out my fix and send it up
[15:51] <tgardner> ogasawara, net: mv643xx_eth: fix build erro
[15:51] <tgardner> 6f39da2c5eab64921f92a9ff4a48f3d14a8db24c
[15:52] <ogasawara> ah, how did I miss that
[15:52]  * ogasawara cherry-picks
[15:55] <tgardner> ogasawara, super green ?
[16:23] <jsalisbury> **
[16:23] <jsalisbury> ** Ubuntu Kernel Team Meeting - Today @ 17:00 UTC - #ubuntu-meeting
[16:23] <jsalisbury> **
[16:57] <jsalisbury> YIKES, the root disk is full on cranberry
[17:39] <salaria> Guess, I'm at right place. Anyone here?
[17:58] <tjaalton> so.. i was planning to backport support for new wacom models to the precise kernel, but is 15 commits (11 from 3.3, 4 for intuos5 support not yet upstream) too much to shove in this late?
[18:00] <tjaalton> make that 13
[18:05] <apw> tjaalton, with kernel freeze already on us, and the last upload in progress, you'll need to be pretty persuasive
[18:05] <tjaalton> apw: yeah, I'll stop :)
[18:06] <apw> :)
[18:06] <tjaalton> probably not sru'able either, so lbm then
[18:08] <apw> lbm sounds viable ... though thats always a huge pain to maintain
[18:08] <tjaalton> in what way? haven't touched that at all..
[18:08] <apw> tjaalton, is this touchpads or something else ?
[18:08] <tjaalton> tablets
[18:08] <apw> tjaalton, they are jsut 'different'
[18:09] <apw> ok so not mainstream things in a common sense
[18:09] <tjaalton> nope
[18:09] <ppisati> tgardner-lunch: last pull req for P/omap4 sent (config changes to reduce master skew)
[18:09] <apw> cool, ogasawara is our lbm expert :
[18:09] <apw> :)
[18:09] <tjaalton> well, built-in touchscreens tend to use wacom too
[18:09]  * ogasawara looks up
[18:10] <tjaalton> ogasawara: so, if I wanted to provide some way to support 3rd gen bamboos and intuos5 tablets, would lbm make any sense or would a wacom dkms package be better?
[18:10] <tjaalton> (the dkms package actually exists in some ppa)
[18:11] <ogasawara> tjaalton: if the dkms package already exists and works, I'd just go that route
[18:12] <tjaalton> ogasawara: ok, I'll probably test that and just tell people to use it if it works :)
[18:12] <apw> problem solved :)
[18:13] <tjaalton> less pain for everyone :)
[18:13] <apw> presumably we can put it in universe still
[18:13] <ogasawara> I'd assume so
[18:14] <tjaalton> hmm, maybe. ppa's are easy to use though, and keep updated
[18:14] <tjaalton> I'll ask the author what he feels about it
[18:34] <apw> t
[18:34] <apw> tgardner, 32 or 64
[18:34] <tgardner> apw, 64
[18:36] <apw> tgardner, thanks ... will get you some bits to test
[18:42] <infinity> apw: I didn't file a bug for the ioctl printk spam, no.
[18:42] <infinity> apw: Do you need one?
[18:42] <apw> infinity, s'ok tgardner did the do
[18:43] <infinity> Kay.
[18:43] <apw> sh-keygen -f "/home/apw/.ssh/known_hosts" -R greenback.local
[18:43] <apw> no, not that ... thats not helpful
[18:43] <apw> http://bugs.launchpad.net/bugs/972355
[18:43] <ubot2> Launchpad bug 972355 in linux "linux: Supress some ioctl warnings which are known benign" [Medium,Fix released]
[18:43] <apw> infinity, ^^
[18:43]  * apw takes it ogasawara has uploaded :)
[18:44] <ogasawara> I have :)
[18:44] <apw> infinity, if you could test that kernel does what you need when its built then we can backport it
[18:44] <apw> ogasawara, you are the (wo)man
[18:49] <infinity> apw: You mean I have to reboot my server?  *whine*
[18:50] <infinity> apw: (Yeah, I'll test soon)
[18:50] <ogasawara> tgardner: 3.4-rc1 rebase pushed to q (I folded in all the build fixes with the one exception of temporarily disabling overlayfs which I left at the tip of the tree)
[18:50] <tgardner> ogasawara, cool
[18:50] <apw> infinity, its a few days from building it its for ppc
[18:51]  * ogasawara sync's the latest patches from precise to q
[18:51] <infinity> apw: It's amd64.  Not *all* my hardware is PPC.
[18:51] <apw> infinity, you say that now, its probablly emulating :)
[18:52] <infinity> (Mostly because I don't want to mail a POWER machine to a co-lo facility, so I lease)
[18:53] <apw> infinity, a plan indeed.  s'what i do too
[18:58] <apw> tgardner, http://people.canonical.com/~apw/vt-handoff-grub-precise/ <-- using the kernel there, and applying grub-10_linux.diff to /etc/grub.d/10_linux, could you boot, SHIFT into the menu and change the set gfxpayload=$fooo to =text and then let it boot ... and tell me if its better then and also get me a dmesg
[18:58] <tgardner> apw, 10-15 mins yet....
[19:00] <apw> tgardner, faster, faster, more whips
[19:01] <tgardner> apw, its that desktop seed. its over a 1000 packages now
[19:04] <bjf> ogasawara: commit 203aa5260edca2ab1872ad8b08386d874f7132f3 may be the cause of a rash of problems on oneiric, precise has the same commit
[19:05] <bjf> ogasawara: 93dc6107a76daed81c07f50215fa6ae77691634f seems to fix the problem
[19:06] <tgardner> bjf, rtg@salmon:~/ubuntu/ubuntu-oneiric$ git log -p 203aa5260edca2ab1872ad8b08386d874f7132f3
[19:06] <tgardner> fatal: bad object 203aa5260edca2ab1872ad8b08386d874f7132f3
[19:07] <bjf> tgardner: precise 
[19:07] <ogasawara> bjf: ack, is that fix going to come back down through stable?
[19:07] <bjf> ogasawara: i don't see a cc stable on it
[19:07] <ogasawara> bjf: is there a bug# for this?
[19:08] <bjf> ogasawara: i'm tracking 6 that are possibly related to this
[19:08] <ogasawara> bjf: need a precise test kernel?  I can whip one up for ya.
[19:09] <bjf> bug 971746
[19:09] <ubot2> Launchpad bug 971746 in linux "Kernel 3.0.0-18 - Unitiy does not start (Lifebook T4220)" [Medium,Confirmed] https://launchpad.net/bugs/971746
[19:09] <bjf> ogasawara: ^
[19:10] <ogasawara> bjf: thanks, looks like feedback is good there.  I assume henrix is going to push this through as an SRU
[19:10] <bjf> yes
[19:10] <ogasawara> bjf: if so, I can just pick the patch for Precise when he sends it to the list etc.
[19:10]  * apw is a bit perplexed at the description of the fix ... if so why does it not break all installs
[19:11] <apw> why just the lifebook ?
[19:12] <bjf> apw, not sure but most(all) our reports are coming in for i386 kernels
[19:13] <apw> bjf, its just such a generic fix that its amazing that if tis the cause of anything, and if it is how anything avoids tripping it
[19:13] <apw> bjf, litterly one of those where when you find it its liek "how the heck did this ever work"
[19:14] <bjf> apw, agreed
[19:15]  * apw can hear booze being poured, thats mean
[19:16] <herton> apw, the other similar reports we have, bjf was passing some of those: 972173 972033 972285 972529
[19:20] <apw> herton, i don't doubt it real, whats amazing is its only a few machines given the fix
[19:20] <apw> it should be _all_ machines running anything without it really
[19:22] <herton> apw, indeed, this issue is weird, may be there is something else that makes especifically trigger on these machines, only common thing seems it happens on i386
[19:24] <apw> signdness or something indeed
[19:30] <tgardner> apw, still have to <ESC> to get the passphrase menu. zinc.canonical.com:/home/rtg/dmesg.txt
[19:54]  * tgardner -> EOD
[22:34] <rlaager> Can someone please re-open #570542? It has multiple comments confirming the bug is present in Maverick final, Oneiric, and Natty and #658461 has been marked as a duplicate of it.
[22:46] <bryceh> ogasawara, ^^