/srv/irclogs.ubuntu.com/2012/03/21/#ubuntu-kernel.txt

rsalveticooloney: can you check bug 960770?01:19
ubot2`Launchpad bug 960770 in dkms "Packages requiring dkms at Pandaboard (omap 4) will also pull linux-headers-generic because current dkms dependencies" [Medium,New] https://launchpad.net/bugs/96077001:19
cooloneyrsalveti: cool, let me take a look01:19
rsalveticooloney: thanks :-)01:25
rsalveticooloney: also, perf is currently broken on omap401:31
rsalvetiif you want to take a look on that :-)01:32
cooloneyrsalveti: i remember i fixed linux-tools package for ti-omap4 before, but haven't try it for a long time01:54
=== smb` is now known as smb
* apw yawns08:03
* smb waves08:04
ckingyawn too08:20
_ruben+308:23
dholbachhiya08:23
dholbachcan anyone comment on http://fridge.ubuntu.com/2012/02/23/ubuntu-12-04-development-update-15/comment-page-1/#comment-4633?08:23
apwthey are asking about a patch in a comment on a blog post and expecting that to get to the right people ?08:30
diwicapw, obviously it seems to succeed? :-)08:31
apwjust making me grumpy08:33
smb+108:34
diwicwe've all been newbies08:34
apwsmb, are you able to sync the stable queue ?08:34
smbapw, not this morning apparently08:34
apwbah that makes a cogent answer hard to make, i want to know if his patch is in there08:35
smbapw, give me a sec08:35
smbapw, I only found a mail in the archive discussing the addition of the stable cc, but not yet the announcement to have it queued08:36
apwsmb, ok ... thanks ... now ... why can't i pull this thing ... kernel.org OI08:37
smbapw, Linus tree still works...08:37
smbBut neither linux-stable nor linux-stable-queue do08:37
apwok both work for me, but linus is zippy and stable is clears swimming in treacle08:38
apwthere was a suggestion that linus might get its own backend server for security separation08:38
smbapw, Hm, and it does not look like the patch has cc: stable added08:39
apwthats something, as you say its not in there yet08:42
smbapw, Well as they seem to have "forgot" the cc: stable... not sure it will08:42
smbMan, kernel.org really is unpredictable right now08:43
apwsmb, perhaps one of the servers in the rotation is sick or something08:44
smbapw, Or rebooting. When you first asked I got the connection reset, now a fetch just is stuck forever as it seems08:45
smbWow, 5minutes later it succeeds...08:48
apwthat is officially not rapid08:49
smbspring tiredness ...08:49
smbmoco time...08:59
apwdholbach, http://fridge.ubuntu.com/2012/02/23/ubuntu-12-04-development-update-15/comment-page-1/#comment-4642 have replied09:01
dholbachapw, thanks a bunch - pushed it through the queue09:01
* apw reboots to get new shineies09:43
ckingapw, crash n burn09:45
Davieybrendand: hey.. so bug 960311 .. you are seeing it on every release?09:53
ubot2`Launchpad bug 960311 in linux "Networking on Dell PowerEdge R300 with Broadcom Corporation NetXtreme BCM5722 Gigabit Ethernet PCI Express is not functional" [High,Incomplete] https://launchpad.net/bugs/96031109:53
brendandDaviey, so far i tried with Oneiric and Precise (beta1 kernel)09:53
Davieybrendand: Did this hardware never work.. or has something changed on the server?09:53
brendandDaviey, the hardware worked last on monday09:54
brendandDaviey, i *suspect* a firmware upgrade was done, but i still didn't get a confirmation from the lab engineer09:54
Davieybrendand: has anything changed in the hardware since then.. bios flash?09:54
Davieyah09:54
Davieybrendand: How soon can you get confirmation ?09:55
* cking wonders if a data base of firmware versions per machine is being kept so one can look this up easily09:55
Davieycking: a validation one, or by those looking after servers?09:56
DavieyI always thought, bios flashing was only done if you encounter issues with the current bios.. I learnt recently that people seem to be doing as a matter of course.09:57
brendandcking, would be a good idea...09:57
brendandDaviey, another thing is this:09:57
brendandfailed dmesg:09:57
ckingbrendand, because BIOS is firmware and firmware changes effectively make the machine behave differently, so it *should* be tracked09:57
Daviey(smb, are you following this?)09:57
brendandeth0: no IPv6 routers present09:58
brendandearlier log, no fail09:58
brendandthat message doesn't appear09:58
Davieybrendand: no, that is fine.. it just means it's an IPv4 only network09:58
smbDaviey, No I am drinking coffee.. :-P09:58
Davieysmb: And you didn't make one for the rest of us?!09:58
brendandDaviey - but that wasn't there before?09:58
brendandDaviey, with the same image so nothing different software side09:59
brendandjust one day and the lack of that message09:59
brendandand there have *definitely* been lab config changes09:59
brendandthat i know for sure09:59
ckingapw, we can hear you but you can't seem to hear us09:59
Davieybrendand: I think this bug is blocked on knowing what has changed.10:00
smbDaviey, yes, I hope my comment there was clear enough. 10:03
apwdiwic, just had to kill pulseaudio again to get output to work in mumble10:03
apwafter a fresh reboot ... it seemed to lose its mind when i asked the mic to change from one channel to another10:04
apwdiwic, and after that output no longer worked10:04
smbDaviey, Since the message in the dmesg points to firmware and there has actually been a bios/fw update, I really would rahter expect a hw failure10:04
brendandDaviey, email sent to lab engineer. cc'd you and smb10:04
diwicapw, could you *not* kill pulseaudio the next time it happens, so the faulty state could be examined better?10:05
apwdiwic, sure10:05
apwi was in a hurry to get on mumble today10:05
diwicapw, unless you have pulseaudio already on verbose log mode in syslog?10:05
brendandsmb - bear in mind this is not a black and white case of the card never working. it still works to allow the system to pxe install and is accesible for a few minutes after boot10:06
apwdiwic, not on tnis machine indeed10:06
brendandsmb - you'll notice those errors come several minutes after boot10:06
diwicapw, ok.10:06
smbbrendand, I would bear that in mind if that was written down in the bug report10:07
brendandsmb - i can state that explicitly, of course. dmesg already says pretty much the same thing10:07
smbbrendand, It does not tell you about pxe boot explicitely and it only shows me a message right after setting up interrupts for it about a fw issue. It won't tell anything about the bios update or anything else. And that wasn't in the initial report either. 10:10
brendandsmb - i don't know if there was a bios update, that's the problem10:11
amitkjk-: common clock is finally going in, congratulations and thanks for starting the effort!10:12
smbbrendand, Well, what I am trying to say is that even the possibility of it mentioned is something that should be in the report. Or whether this is a machine that used to work or... context is important. We do not own working crystal balls10:14
brendandsmb - i know. i am adding details as i obtain them. sorry for not mentioning the pxe install in the first instance. the other things i have just been finding out today, or have yet to find out10:15
brendandsmb - btw, can you tell me what the current development kernel version is? to make sure i get the right one10:16
smbbrendand, Just feeling that the order of things is a bit out of order. First to gather info , then mark the bug critical would be better than the other way round. ;)10:17
* ppisati -> brb10:17
smbFor 3.2 I think we uploaded yesterday...10:17
apwsmb, sitting in the new queue now across the board10:18
smbok so 3.2.0-19.30 is latest as of now10:18
brendandsmb - well, *i* didn't set the importance :) anyway, i'm focusing right now on completing the picture according to all the requests so hopefully all the info will be there soon10:21
jk-amitk: woooot :)10:28
amitkjk-: those 6-7 patches have taken 2 years I think :)10:30
apwamitk, thats pretty quick :/10:31
amitkapw: if you see the thread, there are still arguments (after the maintainer accepting them) to mark them EXPERIMENTAL10:32
amitkit's been a saga10:32
apwheh ... never ends does it10:32
amitkeven the popcorn went stale a long time ago10:32
apwunopened popcorn would have gone off by now10:32
amitkjk-: beers on me if you decide to make the trip to Hong Kong10:33
apwppisati, do your panda boards boot on the precise images ?10:43
apwppisati, i have reports that they do not, and wondering if you are seeing issues10:47
ppisatiapw: last time i tried yes, they worked11:07
ppisatiapw: any particular image or just the last one?11:07
apwthe compainant is implying that they have not worked for some time, so if you have booted someting in the last week that is interesting, is that !XM, XM or both you have done?11:12
apwoh that is beagle isn't it11:12
apwppisati, ^^11:12
ppisatiyep11:12
ppisatiuhm11:13
ppisatii think i tested it last week11:13
ppisatiiirc11:13
ppisatii mean, omap3 (beagle, beagle xm)11:13
ppisatiwhile i use panda eveyday11:13
ppisatiso, is it beagle or panda? omap3 or omap4?11:14
apwits panda i am told, so panda you tested in the last 24 hours and it works11:14
ppisatidefinitely11:15
ppisatii'm using latest kernel i released11:15
ppisatibut i'm downloading latest preinstalled image just to see11:15
apwppisati, let me know ... thanks11:16
apwppisati, he has a 'rev 1A pandaboard' is that older than yours, do you have one?11:18
ppisatiapw: same here, rev A111:19
apwA1 or 1A11:20
ppisatisticker on the back of my board says rev A111:20
ppisatidid he use the daily preinstalled image?11:20
apwyep checking if his is 1A or he typo'd it11:20
apwok its A111:21
apwppisati, if it works for you, could you also paste the URL for the working image you used11:31
ppisatiyep11:33
ppisatidd takes ages...11:33
apwsd cards are soooo fast11:34
ppisatiapw: works here, i'm in the installer11:39
ppisatiapw: let me finish the installation11:39
apwppisati, thanks11:39
ppisatiah11:41
ppisatia new installer! :)11:41
ppisatiwe can choose a pic now11:41
ppisatior even take one11:41
apwshiney, yeah i think i saw that somewhere, i like the burning match11:42
ppisatihttp://cdimage.ubuntu.com/daily-preinstalled/current/precise-preinstalled-desktop-armhf+omap4.img.gz11:55
ppisatizcat Downloads/precise-preinstalled-desktop-armhf+omap4.img.gz | sudo dd of=/dev/sdc bs=4M11:56
ppisatiput the resulting sd card in the panda sd slot,  power the board and follow the installation procedure11:56
ppisatiapw: ^^11:56
ppisatiof course, 'of=/dev/sdc' is system dependent (i don't want to wipe his system)11:57
apwyep :)12:10
=== smb` is now known as smb
Davieyppisati: yes you do :)12:16
apwtgardner, can you hear us ?12:35
tgardnerfu576`3ing pulse12:36
ericm|ubuntudiwic, are you still on mumble? I seems to be dropped and not succeeded in connecting so far12:39
diwicericm|ubuntu, meeting has ended, sorry12:39
ericm|ubuntudiwic, due to connection problem?12:39
diwicericm|ubuntu, we figured you were about to say something evil about the government and they proactively cut you off12:40
ericm|ubuntudiwic, yeah I was about to12:40
ericm|ubuntudiwic, but how does the great firewall predicts that?12:40
diwicericm|ubuntu, it is very intelligent12:40
diwicericm|ubuntu, the meeting ended when the few of us who were there had said what we were supposed to say12:41
ericm|ubuntudiwic, really impressed by the party's cutting edge technology12:41
ericm|ubuntudiwic, the rest just cannot get on again?12:41
ericm|ubuntudiwic, just want to make sure it's not happening to me _only_12:41
diwicericm|ubuntu, only you and a16g had connection problems, for the others it was fine I believe12:42
ericm|ubuntudiwic, sounds like a connection problem behind the great firewall12:43
apwglxinfo -l | grep GL_MAX_TEXTURE_SIZE12:45
tgardnerapw, GL_MAX_TEXTURE_SIZE = 819212:46
ppisatia new kernel is baking, in the mean time i'm out for a bit13:06
tgardnerppisati, have you seen bug #961133 ?13:20
ubot2`Launchpad bug 961133 in linux "Ubuntu Desktop ARM Images do not boot on my Pandaboard" [Undecided,Incomplete] https://launchpad.net/bugs/96113313:20
tgardnerogasawara, gomeisa arm* chroots appear to be working again.13:29
ogasawaratgardner: cool, what changed?13:29
tgardnerqemu-static AFAICT13:29
tgardnerlooks like I still need to twiddle with armhf, nut armel is working13:29
tgardner*but13:29
ppisatitgardner: i think that's what apw told me earlier this morning13:38
tgardnerppisati, ok13:39
ppisatitgardner: i tested today's image and it's working ok on my panda13:39
ppisatibtw13:39
tgardnerppisati, I noticed he's got an A113:39
ppisatiat least on tangerine, armhf chroot kind-of work13:39
tgardnerwould that make a difference ?13:39
ppisatitgardner: yes and no, but i got an A1 too and it's working13:39
* cking reboots13:56
tgardnerogasawara, I'm dribbling ABI bumper cruft into precise master-next14:02
ogasawaratgardner: ack14:02
tgardnerogasawara, so no need to startnewrelease, etc14:03
=== yofel_ is now known as yofel
vanhoofanyone know if it's possible to create a config idential to what I see in /boot/config-3.2.0-1409-omap4 from git?  Been playing w/ fdr genconfigs/genportconfigs as well as splitconfigs.pl but I must be doing something wrong, I always end up with a common omap config14:31
tgardnervanhoof, our config algorithm is a many to one relationship, so its hard to go backwards14:33
ogasawaravanhoof: which branch are you in?14:34
vanhoofogasawara: the wrong one :)14:38
vanhoofogasawara: ikepanhc got me hooked up14:38
ikepanhc:)14:39
vanhoofafter a checkout of the right branch, i'm all set after fdr clean..genconfigs14:39
ckingrtg, you may also like to try http://www.piware.de/2012/02/power-usage-report-find-power-drain-causes/14:41
apwppisati, are there jumpers on your A1, if so perhaps you could enumerate your settings14:45
apw(in that bug(14:45
* ogasawara back in 2014:45
apwvanhoof, and yes fdr clean; fdr genconfigs would be the approved way to get the configs out14:46
ppisatisometimes i don't understand git rebase...15:09
ppisatiapw: panda is jumperless15:09
apwppisati, git rebase> why whats it done15:10
apwppisati, panda> ahh ok, then not that then15:10
ppisativanhoof: export $(dpkg-architecture -aarmhf); export CROSS_COMPILE=arm-linux-gnueabihf-; fakeroot debian/rules clean prepare-omap415:11
ppisativanhoof: in ti-omap4 branch (git checkout ti-omap4 from an ubuntu-precise git tree)15:11
ppisatiapw: well, it's reapplying patches i din't expect should be reapplied15:12
apwppisati, you rebasing against a rebased tree?15:12
ppisatiapw: yes15:13
ppisatiapw: P/omap4 on P/master15:13
apwppisati, and are you telling it where your base is ?15:13
ogra_my panda jumps if i hit the table really hard15:13
apwas it cannot find the bottom of the rebase correctly in that situation15:13
ppisatiapw: good point, but i never had to15:13
ppisatiapw: ok wait15:14
keesokay, I have a git tree based on 3.3, and I've got the precise tree. is there a sane way to pull a chunk of patches off the top of the 3.3 tree onto the precise tree without doing per-commit cherry-picks?15:14
apwppisati, yeah and it'll probabally work mostly as long as there arn't any commits dropped in the original master15:14
ogasawarakees: you can cherry-pick a range of commits now15:14
ppisatiapw: let's say you are in topic branch created from master15:14
keesogasawara: oh! that's much better15:14
apwbut the most reliable way is to use the rebase --onto origin/master-next old-master15:14
apwform of re15:14
ppisatiapw: git co topic; git rebase master15:14
apwrebase15:14
ogasawarakees: I know!  just found that out a week or so ago.15:14
ppisatiapw: and it almost immediately complain about a clashing commit15:15
apwppisati, that is valid _if_ master is not a rebased branch15:15
apwppisati, as in P it still is you need to use: git rebase --onto master oldmaster15:15
apwwhere oldmaster is where you last were rebased to, or the commit before your first one15:16
ppisatiapw: you go look at your actual tree just to notice that is different from master (while i expect the first thing it does is to kind of format-patch the pile of patches not present in master, git reset --hard origin/master and then apply all of the patches one by one)15:16
apwgit cannot work out the correct base point in your case till P releases, then we stop rebasing master and life is fine15:16
ppisatifine, i'll do15:17
apwand that is what it does, but it does it by working out where the previous common commit is between the old and new branches, and using that base to lift all the patches15:17
apwas wehave rebased too the common merge point is back on mainline somwhere and so you try and pick up the whole of leanns stuff too, fail15:17
ppisatiso according to merge-base i should be in Linux-3.2.9 but i'm not there either15:17
ppisatiyep, i figured that out15:18
apwwhat does merge-base say15:18
ppisatiLinux-3.2.915:18
ppisatiso it picks all the stuff from there on (almost)15:18
ppisatiok15:18
apwyep, it can detect some identicle commits are the same and drop them15:18
apwbut its not very easy and tends to go pop15:18
ppisatii got it while talking15:19
ppisatithe funny thing is that we had these apparmor commit before15:19
apwanyhow if your base is a rebase tree then --onto is the only sane way to use it15:19
ppisatithese where dropped15:19
ppisatilater reapplied (last kernel)15:19
ppisatiah, nevermind15:20
apwppisati, we are dropping and readding apparmor en-toto so that the patches can be updated to match upstream exactly to make maintenance of the result easier15:21
ppisatiright15:21
GrueMasterppisati: Just fyi, I have been seeing strange lockups on the pandaES with the desktop image.  I'm trying to capture some log output, but so far unsuccessful.   System has to sit for a long while (this particular try has run since Monday evening).15:31
GrueMasterOther community members have seen it also on #ubuntu-arm.15:32
ppisatiGrueMaster: are you using the sgx driver?15:33
ppisatiGrueMaster: if yes, try to uninstall it15:33
GrueMasterNo.  Desktop image from 20120319.  No updates, fresh image.15:33
ppisatik15:33
GrueMasterI do not see it on server, which leads me to believe it may be kernel/Xorg related.  I saw something similar during Natty(?) where the system would lose the monitor during sleep and hang as a result, but it would at least spew stuff in the log.  This is a hard lock (solid LED instead of heartbeat).15:35
GrueMasterI enabled serial console on this image in the hopes of capturing something, but I don't have anything on the serial console post Upstart.15:38
ppisatithat reminds me i should expense an ES board15:39
ogra_++15:39
ppisatiogra_: you, stop bumpinmg your board! :)15:41
ogra_hehe15:42
GrueMasterppisati: Rebooted and looking for residue in the logs.  I am seeing a lot of spamming (every ~1.5 sec) from the kernel: ti_hdmi_4xxx_detect: by detect line: 1 (1 == connected)15:49
ogra_i have that too here 15:49
ogra_doesnt kill the board for me though15:50
GrueMasterYea, I see it on all systems, including the headless ones.15:52
ppisatiGrueMaster: i'll kill it in the next update16:01
GrueMasterk, thanks.16:01
apwogasawara, so that EDID patch ... you might want to hold fire on reading it right now ... seems upstream now has a different way ... BAH ... i find out 30s after I sent it16:02
ogasawaraapw: ack16:03
smblamont, Ok, just updated the bug with test kernel location. Now hopefully you see some magic "Dropped by" messages in dmesg ...16:03
tgardnerapw, too late. I've already been polluted.16:05
sforsheetgardner, ogasawara: the apple-gmux driver that's landing upstream has a couple of changes from what we're carrying in precise. I'd like to update precise -- would you prefer patches on top of our sauce patch or replacing it with the patches headed upstream?16:16
ogasawarasforshee: I prefer to replace with what's heading upstream16:16
sforsheeogasawara, ack16:17
lamontsmb: I'll upgrade later today and see what we see16:22
smblamont, ack16:22
* ppisati -> disappear for a bit16:31
vindexhi16:36
vindexhas anybody used perf successfully on ubuntu?16:36
vindexim having trouble getting a custom vanilla kernel compiled with perf properly working16:36
vindex3.2.1016:36
vindex(vm guest)16:36
apwvindex, yes i have used basic perf on ubuntu kernels16:37
vindexapw: im experiencing a "vmlinux symtab| mismatch, and after stracing the process it never opens a vmlinux image, only kallsyms16:37
vindexthe kernel has proper perf support compiled in, dbg symbols and other stuff16:37
vindex(im doing kernel development)16:38
apwhmm never seens that, though we 16:38
apwwe build perf with the kernel when we build it16:38
apwas it is in theory build differently based on the kernel16:38
vindexwell, ive done make oldconfig, all/modules/bzimage, modules instal, install, boot16:38
vindexand then cd tools/perf make16:39
vindexyes, it uses kernel sources / headers directly so it is influenced16:39
apwthen that sounds reasonable faximily of what our packaging does, so i'd not expect issues indeed16:39
tgardnervindex, is what you're doing work on a stock Ubuntu kernel ?16:39
vindexthats why im quite pissed at this stage to have issues16:39
apwother than saying it seems to work ok without our packages, i am not sure what the issue is16:39
vindextgardner: it is applicable, but i like to work on git vanilla srcs first16:40
vindexsince i develop for the kernel, not ubuntu. ubuntu is the platform i use for development, and the patches i work on apply fine to ubuntu kernels16:40
vindexbut it is far from being the only audience i target16:40
apwvindex, yep ... but no we've not seen that16:40
vindexvmlinux symtab matches kallsyms: failed16:41
vindexthats the error, nothing obvious when i try to see what might fail16:41
vindexall open() calls seem successful16:41
vindexhow is linux-image-tools built for each kernel?16:42
apwvindex basically the way you indicate, and they seem to work here16:43
vindexi mean how could i replicate the pkg from vanilla sources? it doesnt seem like a make-kpkg target16:43
vindexwhere does perf read the vmlinux file from normally?16:44
apw/boot i assume as thats the only one in place16:44
apwthe master branches in our git repos represent the raw source we use, building that package drops the linux-tools package16:45
vindexis there any backport/testing pkg for 3.2?16:46
vindexperhaps i could use linux-tools from those16:46
apwthere are 3.2.12 ish based kernels in the archive for precise16:47
apwwe only build tools in the official ubuntu builds16:47
vindexseems like at least the ubuntu perf exec looks for vmlinux in /boot16:50
vindexvanilla doesnt16:57
vindexweird.16:57
=== tgardner is now known as tgardner-lunch
ogasawarabjf: I'm looking at http://people.canonical.com/~kernel/reports/_precise-open-bugs_.html and am just curious how it determines which bugs to put on there?18:14
ogasawarabjf: more specifically I guess I'm curious how bug 936552 is still managing to show up there18:14
ubot2`Launchpad bug 936552 in xserver-xorg-input-synaptics "MacBookAir 4,1 trackpad does not work with evdev/multitouch driver" [Medium,Confirmed] https://launchpad.net/bugs/93655218:14
ogasawarabjf: is it the kernel-da-key tag?18:15
bjflooking18:16
bjfogasawara: it shouldn't be, i'll look into it18:20
ogasawarabjf: ack18:20
keesogasawara: karblewy, pull request for seccomp delivered!19:18
ogasawarakees: thanks!19:18
keesit's huuuuge :)19:18
ogasawarakees: sounds ominous19:19
kees 39 files changed, 1660 insertions(+), 74 deletions(-)19:21
keesit's relatively isolated, as it turns out, but it's still big.19:21
keesanyway, the Chrome security team was really hoping they could see it in beta 2, so I cranked it out today. Upstream seems pretty settled on everything, so I figure the day before beta 2 freeze is about as late as I can stand. :)19:22
apwkees, i susect you have missed the boat, as the kernel takes 2 days to get done19:50
keesapw: noooo19:58
keesapw: that sucks -- the freeze is tomorrow! :P19:58
=== tgardner-lunch is now known as tgardner
* tgardner -> EOD20:30
keesogasawara: so, is it likely that seccomp will see beta 2?20:43
ogasawarakees: what time is freeze tomorrow?20:43
keesogasawara: I have no idea :P20:44
* kees asks in #u-release20:44
ogasawarakees: I'm going to assume it's an ABI bumper in which case I'm not sure we could make the freeze deadline20:44
ogasawarakees: so we likely would need to get a freeze exception20:45
ogasawarakees: which probably wouldn't be too painful if we give them a heads up20:45
keesogasawara: 2100 UTC20:45
* ogasawara checks what time it is now20:45
kees20:45 UTC, so just over 24 hrs from now20:45
ogasawaracommit 8e8079f9e951ef1921b0de648568ea4b10c38d8b21:23
ogasawaraAuthor: Andy Lutomirski <luto@amacapital.net>21:23
ogasawaraDate:   Mon Jan 30 08:17:26 2012 -080021:23
ogasawara    UBUNTU: SAUCE: SECCOMP: Add PR_{GET,SET}_NO_NEW_PRIVS to prevent execve from granting privs21:23
ogasawara    21:23
ogasawara    With this set, a lot of dangerous operations (chroot, unshare, etc)21:23
ogasawara    become a lot less dangerous because there is no possibility of21:23
ogasawara    subverting privileged binaries.21:23
ogasawara    21:23
ogasawara    This patch completely breaks apparmor.  Someone who understands (and21:23
ogasawara    uses) apparmor should fix it or at least give me a hint.21:23
ogasawarakees: ^^ "This patch completely break apparmor" has me concerned21:24
ogasawarakees: breaks apparmor how?21:24
ogasawarakees: ha, disregard21:26
ogasawarakees: I'm now seeing the next patch :)21:26
keesogasawara: heh, yes :)21:31
=== egon_ is now known as egon
pbuckleyanyone have a good link for the differences between ubuntu's 11.10 kernel (3.0) and the 12.04 kernel (3.2)?21:35
ohsixkernelnewbies has most of the interesting stuff in the release notes21:36
pbuckleycool thanks21:36
ohsixbeyond that, git log :>21:36
pbuckleyheh.. that seems like a like of commits to go thru.. just trying to justify building our next project on 12.04 vs 11.10 thats going to ship in like 6 months21:37
pbuckley+alot21:37
ohsixlinus has a release message that has interesting stuff in it too, but kernelnewbies is the meat21:39
pbuckleyhrmm i only see 3.321:40
* pbuckley digs around some more21:40
pbuckleyhttp://kernelnewbies.org/Linux_3.221:41
pbuckley\o/21:41
ogasawarakees: getting build failures on arm21:51
ogasawarakees: kernel/seccomp.c:27:25: fatal error: asm/syscall.h: No such file or directory compilation terminated.21:51
* kees shakes a fist21:52
ogasawarakees: I gotta drop off for a bit, I'll check back in a bit21:52
keesokay21:52
keesogasawara: I don't have an ARM build environment :(21:53
* Daviey passes kees a qemu-system-arm.21:53
keesogasawara: can you wrap the #include line with #ifdef CONFIG_HAVE_ARCH_SECCOMP_FILTER block maybe?21:53
keesDaviey: if only it were that easy! :)21:53
Davieykees: i'd love to know how long cpu virt takes to build an arm kernel :)21:53
* kees cries21:54
Davieykees: ScottK was given two arm 'server' boxes to setup for community access.. he's had them over a year, ask them how access is progressing. :)21:56
keesactually, it turns out I've already set up for qemu-arm, I just need to override the mirror and mk-sbuild will DTRT21:57
ogra_Daviey, they were slow ones and still havent finished their boot :P21:58
Davieyogra_: I blame the canonical arm team for the slow booting :P21:58
ogra_haha, you never booted an ac100 with a recent image, did you ?21:59
ogra_(boots faster than any x86 SSD based machine i have around)21:59
ogra_(though indeed ac100 is a community effort, cant credit the ubuntu arm team for it ;) )22:00
keesmk-sbuild --arch=armel precise --debootstrap-mirror=""22:02
keeswheee22:02
apwkees, can't you cross compile, thats what most of us do to confirm compilability22:07
jjohansenapw: for the apparmor rebase should I do a whole sale drop in of 3.4 aa as a single patch, or cherry pick the 20 or so upstream patches22:11
bandit5432what channel should i be in to talk about the latest mainline release?22:34
pbuckleyoh yay.. that numa stuff made it into 3.122:39
bandit5432any have any regressions with 3.3 from rc7 and optical drives?22:44
bandit5432kernel v3.3-precise does not recognize my ide optical drives any thoughts? v3.3-rc7-precise works fine22:54
ogasawaradiff --git a/kernel/seccomp.c b/kernel/seccomp.c23:04
ogasawaraindex 8af235b..d22ef26 10064423:04
ogasawara--- a/kernel/seccomp.c23:04
ogasawara+++ b/kernel/seccomp.c23:04
ogasawara@@ -24,7 +24,9 @@23:04
ogasawara #include <linux/slab.h>23:04
ogasawara #include <linux/uaccess.h>23:04
ogasawara+#ifdef CONFIG_HAVE_ARCH_SECCOMP_FILTER23:04
ogasawara #include <asm/syscall.h>23:04
ogasawara+#endif23:04
ogasawarakees: ^^ seems to fix it23:04
ogasawarakees: I'm just gonna squash it with "UBUNTU: SAUCE: SECCOMP: seccomp: add system call filtering using BPF"23:05
=== bladernr_ is now known as bladernr_afk
c_smithhey, I encountered something strange, and fixed it after quite a while, but it pertains to the kernel, as it kept either dumping a crash log to my screen, or throwing me a Kernel Panic, the situation was that I had all 3 of my RAM slots in my desktop filled with a 1 GB PC-3200 RAM stick each, and kept getting said crash dumps and kernel panics.23:31
bandit5432did you test the ram?23:32
c_smithYes, I did, once with each ram stick inserted one at a time and then again with all 3, memtest86 reported no errors.23:32
c_smithand I ran all 9 tests with Memtest86.23:33
bandit5432how did you fix it?23:33
c_smithremoved one stick.23:33
ohsixdid you check your motherboard documentation, some of them aren't expected to be stable with the ram slots filled in different ways23:33
bandit5432do you have a bad ram slot23:33
ohsixeg. they need to go in as pairs or the like23:33
c_smithsadly, I don't have the documentation, the desktop was given to me.23:33
bandit5432you can download the docs from the manufacture 23:34
ohsixsome chipsets don't even terminate the other banks when there's one piece of memory in a pair of slots :P23:34
c_smithand it might be the slot, no clue. I got the desktop only recently.23:34
c_smithhmmm, that might be handy, I'll look at the manufacturer.23:34
c_smithofc, I have no clue as to even the model for the mainboard.23:35
c_smithwould it say on the mainboard?23:35
bandit5432yes23:35
c_smithcool, I'll get to that info,23:35
c_smiththanks for the tip. :)23:35
bandit5432and if its a hp dell etc look up the model #23:35
c_smithit's a Gigabyte mainboard, that much I know from the BIOS.23:36
bandit5432gigabytes are easy to look up23:36
bandit5432look to the left of the first ram slot23:37
c_smiththanks23:37
bandit5432np23:37
c_smithand I am curious, how outdated would PC-3200 RAM be?23:37
c_smithnot that it's essential, just a curiousity.23:38
ohsixram doesn't usually go out of date, it goes in the bin with the computer :P23:38
ohsixbut we're to ddr3 now23:38
c_smithok23:38
c_smithyay for tiny text..... having a tough time finding it.... >.<23:40
c_smithok, think I found it.23:41
c_smithyep, found it, would have helped to have the flash light ready from the start,23:42
c_smithso, it looks like the max supported RAM is what I had, 3GB via 3 DIMM slots.23:46
c_smithso, mightn't it be the slot even if Memtest86 reported no errors with all 3 slots being occupied?23:47
bandit5432it could be anything what kernel are you running with it breaks?23:50
c_smiththe latest one in the Oneiric updates, but it also happened with the second latest.23:52
c_smithlet me plug it in to get you the latest one that the desktop is running23:53
bandit5432search for kernel panics and the kernel ## and see what causes them I had a bad powersupply that caused kernel panics so it could be a lot of things23:54
jMCgHow do I get this string 'lib/x86_64-linux-gnu' from debian build tools?23:55
c_smithkk23:55
c_smithwhat do I search in?23:56
bandit5432google23:56
c_smithkk.23:56
bandit5432uname -r to get the kernel version23:56
bandit5432in a terminal23:57
c_smiththe kernel version is 3.0.0-16-generic. uname ftw! :)23:57
c_smithmeh, not finding anything useful...... only an Atheros panic that was fixed in 3.0.0-1623:59

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!