| snadge | i think i've got a fairly simple one i was hoping someone with some more kernel experience could help me with | 01:41 |
|---|---|---|
| snadge | yeah its a problem only with recent kernels and virtualbox.. but still | 01:41 |
| snadge | https://forums.virtualbox.org/viewtopic.php?f=7&t=47078 | 01:41 |
| snadge | exactly the same oops as this guy has.. except hes using some 3.2 rc and mint.. im using ubuntu precise, and latest mainline nightly (3.3.0 #201203250407) | 01:42 |
| snadge | code dissassembly is the same.. and the same call trace | 01:42 |
| snadge | id like to know how to find module_put .. and the section of code that disassembly is referring to | 01:43 |
| snadge | no source packages for the mainline nightlies? | 01:50 |
| snadge | i suppose i have to use git for that | 01:51 |
| snadge | git://kernel.ubuntu.com/ubuntu/linux.git <-- that is mainline ? | 02:00 |
| snadge | *tumbleweed* .. i wonder if i'll finish this git clone before anyone says anything | 02:17 |
| bullgard4 | [Ubuntu 11.10 GNOME Shell 3.2.2.1] Super key > Applications > System tools > Power statistics > Prozessor > Wake-up processes lists 2 types of wakeup processes: i.) Symbol is a rhombus, ii.) Symbol is a gear. What is the name of these two types? | 06:51 |
| === Guest14119 is now known as panda|x201 | ||
| RAOF | bullgard4: App vs IRQ handler, apparently. | 07:00 |
| smb | morning | 07:25 |
| ppisati | moin smb :) | 07:25 |
| smb | Just for forgetting to upgrade on Friday... now its about 230M... at least nothing that wants to get removed... | 07:27 |
| ppisati | did you reboot already? | 07:28 |
| ppisati | is it safe? | 07:28 |
| smb | no just started the dist-upgrade | 07:28 |
| smb | will let you know in a bit... | 07:28 |
| ppisati | 135 pkgs here... | 07:29 |
| ppisati | wtf?!?!? we still have evolution and banshee around, did we sack them in this release? | 07:29 |
| ppisati | *didn't | 07:29 |
| snadge | enjoy unity 5.8 ;) | 07:30 |
| snadge | for some people it causes a blank desktop upon login.. hehe | 07:31 |
| smb | ppisati, It probably won't get deleted when you got them already | 07:31 |
| ppisati | doh! | 07:32 |
| ppisati | snadge: unity2d? | 07:32 |
| ppisati | snadge: is it safe? | 07:32 |
| RAOF | unity2d works; and after a unity --reset, so should 3d. | 07:32 |
| ppisati | smb: btw i still have emacs around, but that's my heritage... | 07:32 |
| * ppisati uses only 2d, cool... | 07:33 | |
| * smb pretends not to know those 5 letters... ;-P | 07:33 | |
| ppisati | well, personally i really like unity (design-wise) | 07:33 |
| ppisati | is all i liked from windowmaker + a status bar with all the indicators&c | 07:34 |
| ppisati | btw, did they revert the secondo screen+second launcher thing? | 07:34 |
| RAOF | ppisati: It's now configurable in the “Displays” capplet; there's a toggle for on-all-screens/a drop box for which screen you want it on. | 07:35 |
| ppisati | RAOF: nice | 07:36 |
| === rsalveti` is now known as rsalveti | ||
| * ppisati -> reboot | 07:45 | |
| * smb reboot | 07:46 | |
| snadge | unity2d is good | 07:47 |
| ppisati | so far so good... | 07:51 |
| smb | So far... as long as you are through the blank (or background only) screen, unity --reset segfaulting and compiz crashing parts... | 07:59 |
| ppisati | ouch | 07:59 |
| snadge | i ran unity --reset from console myself | 08:29 |
| snadge | but my work pc.. didnt need to.. so maybe its related to fglrx | 08:29 |
| snadge | work pc is intel | 08:30 |
| smb | This machine is on ati/radeon | 08:30 |
| snadge | possibly related to amd/ati then | 08:30 |
| smb | Running reset from console just hang, repeating went a bit further and finally running it again from gfx resulted in a segfault of the command. | 08:31 |
| snadge | thats pretty harsh | 08:31 |
| smb | (not really making one trust in its ability to fix things... ;-P) | 08:31 |
| snadge | maybe it'll work now | 08:31 |
| smb | I am up and running right now | 08:32 |
| smb | Fingers crossed | 08:32 |
| snadge | yeah it must be a new compiz setting or an old one that glitches with the update | 08:32 |
| snadge | theres a launchpad bug for it.. i dont have the link offhand | 08:32 |
| snadge | https://bugs.launchpad.net/unity/+bug/963633 | 08:34 |
| ubot2 | Launchpad bug 963633 in unity "Unity 5.8: Login to blank screen (all black or just wallpaper)" [Critical,In progress] | 08:34 |
| snadge | that one has the most heat | 08:34 |
| smb | Yep, sounds like it. | 08:34 |
| snadge | launchpad is great now that heaps of people use ubuntu | 08:34 |
| snadge | bug affects 56 people :P | 08:35 |
| snadge | reported 2 days ago | 08:35 |
| smb | And someone has assigned it at least. Well, there was a weekend in between... :) | 08:35 |
| snadge | 14 duplicates tagged already | 08:36 |
| snadge | i know this isnt a kernel problem.. but i *really* want someone to fix this | 08:37 |
| snadge | https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/770283 | 08:37 |
| ubot2 | Launchpad bug 770283 in compiz-core "[fglrx]title bar does not update on non-maximized windows" [Medium,In progress] | 08:37 |
| smb | snadge, Then you may tell "them" in #ubuntu-unity... maybe | 08:38 |
| snadge | tried that ;) but yeah.. i will remind them hehe | 08:40 |
| === arun is now known as arun__ | ||
| fsancho | Hi all. Is there any good reason to not activate "CONFIG_DRM_GMA500=m", "CONFIG_DRM_GMA3600=y" and "CONFIG_DRM_GMA_600=y" in config for 3.3 kernel? | 10:49 |
| snadge | yes.. the universe will explode if you do | 10:59 |
| * ogra_ thought the universe does that anyway since the big bang | 11:00 | |
| snadge | right.. but little did you know, thats what caused the big bang | 11:01 |
| snadge | some chose those specific kernel options.. and boom.. here we are now ;) | 11:02 |
| ogra_ | ah, k ... thats the physics lesson i missed at school then :) | 11:02 |
| fsancho | i mean, these options are deactivated in 3.3 builds from kernel.ubuntu.com. Is there a good reason for that? Is there a way to ask the manager of the site to activate it? | 11:03 |
| snadge | well i dont know who manages the daily builds on kernel.ubuntu.com | 11:04 |
| snadge | but i can tell you that more often than not.. those builds suck | 11:04 |
| snadge | i tried out the radeon/drm stuff yesterday.. granted with experimental options and mesa from git | 11:05 |
| fsancho | snadge: My builds with make-kpkg doesn't look as good as those builds | 11:06 |
| snadge | but still.. it caused my computer to reboot after a few minutes of playing minecraft ;) | 11:06 |
| bullgard4 | RAOF: Thank you very much for your help. | 12:08 |
| === smb` is now known as smb | ||
| * ppisati -> lunch | 12:23 | |
| === arun_ is now known as arun | ||
| === bladernr_afk is now known as bladernr_ | ||
| cking | mjg59, what's the current state of play with the patch "PCI: ignore pre-1.1 ASPM quirking when ASPM is disabled" - you mentioned you were working on this: https://lkml.org/lkml/2012/3/19/408 | 13:20 |
| mjg59 | cking: Haven't been able to reproduce, nobody's sent me a bug report containing any worthwhile information | 13:21 |
| cking | mjg59, that's a bummer, we're seeing some machines hang with this patch, bug 961482 | 13:24 |
| ubot2 | Launchpad bug 961482 in linux "3.2.0-19 kernel fails to boot (-18 OK)" [Critical,Confirmed] https://launchpad.net/bugs/961482 | 13:24 |
| mjg59 | Yes, I know - but I can't reproduce and mere inspection doesn't seem to be getting me anywhere. I really need a full backtrace. | 13:24 |
| cking | ah, so in the short term, would pulling this patch be a more sensible option? | 13:25 |
| * cking trying to work out the pros vs cons of keeping this patch | 13:26 | |
| mjg59 | No, that breaks a different set of hardware | 13:28 |
| cking | mjg59, OK - so reverting 3c076351c4027a56d5005a39a0b518a4ba393ce2 "PCI: Rework ASPM disable code" may at least allow these machines to boot? | 13:31 |
| mjg59 | I really don't know at this point | 13:31 |
| mjg59 | I'd like to see some effort to fix the bug from people who have access to users who see the bug | 13:32 |
| mjg59 | The ones who have contacted me about it are not especially useful in terms of actually giving me feedback... | 13:32 |
| cking | I realise this, just trying to explore options at the mo. | 13:32 |
| tgardner | cking, do we have any affected machines within OEM or somewhere else ni the company ? | 13:33 |
| mjg59 | Reverting all ASPM changes back to the 3.2 baseline will probably boot things, but you'll be back to spending 5W extra per machine | 13:33 |
| cking | tgardner, not that I know of, I've seen zero reports on this from OEM | 13:33 |
| tgardner | cking, well, see if you can get one of the affected folks in the bug report to respond. | 13:35 |
| cking | tgardner, ack | 13:35 |
| cking | mjg59, so a *full* backtrace is required, anything else especially useful to add in? | 13:38 |
| mjg59 | cking: They're probably going to need either a serial console or USB debug to get it | 13:38 |
| cking | sigh | 13:40 |
| * cking will check with OEM to see if we have one of the offending Dells | 13:41 | |
| === yofel_ is now known as yofel | ||
| * ogasawara back in 20 | 14:38 | |
| jjohansen1 | ogasawara, tgardner: is there going to be 1 more kernel upload before beta2? | 15:48 |
| * jjohansen1 knows the answer is no but needs to ask | 15:49 | |
| tgardner | jjohansen1, certainly one more before freeze | 15:49 |
| tgardner | likely april 3 | 15:49 |
| ogasawara | jjohansen1: I wasn't planning on one before beta-2, but definitely one more before kernel freeze | 15:49 |
| jjohansen1 | tgardner: right, but not before beta2 | 15:49 |
| jjohansen1 | ogasawara: okay thanks | 15:50 |
| tgardner | jjohansen1, that would almost require a freeze exception from the release team | 15:50 |
| jjohansen1 | tgardner: right, I will let the server team request that if they want | 15:50 |
| ogasawara | tgardner: I am concerned though about bug 961482 being unresolved for beta-2, but there does seem to be a workaround so I was going to release note it. | 15:51 |
| ubot2 | Launchpad bug 961482 in linux "3.2.0-19 kernel fails to boot (-18 OK)" [Critical,Confirmed] https://launchpad.net/bugs/961482 | 15:51 |
| tgardner | ogasawara, cking is working on it | 15:51 |
| ogasawara | tgardner: ack. if we did get a fix in time for beta-2, I'd lobby the release team for an upload. | 15:52 |
| cking | ogasawara, I'm not sure yet if we can get a fix in time though, it's pretty tight | 15:52 |
| ogasawara | cking: indeed, we'd have to get something in by tomorrow which is not a large window. | 15:53 |
| ogasawara | cking: were you able to get a hold of anyone in OEM who could reproduce? | 15:53 |
| cking | ogasawara, not yet, but they possibly have some H/W which I will try and get shipped to me | 15:54 |
| ogasawara | cking: I think bryceh might have a system showing the issue? | 15:54 |
| cking | ogasawara, this kinda bug requires gathering most of the oops, so it's kinda serial console kinda work | 15:55 |
| jjohansen1 | ogasawara, tgardner: sounds like server team is going to work around the issue for beta 2 so no freeze exception request for the kernel | 15:57 |
| tgardner | jjohansen1, ack. what was theissue ? | 15:57 |
| jjohansen1 | tgardner: its around containers and apparmor confinement | 15:58 |
| jjohansen1 | tgardner: there is a pseudo workaround, that they will use for beta2 | 15:58 |
| cking | rats, hit an inode race bug in btrfs | 16:28 |
| henrix | smb: thanks for the background info on iscsitarget, in your email | 16:34 |
| henrix | smb: about the bug itself, in my (quick) investigation, i found that the bug has been solved already upstreams | 16:35 |
| * henrix kept a link to thread somewhere... | 16:36 | |
| smb | henrix, welcome. Ok, I have not seen a good pointer in the debian changelogs, but have not yet check upstream | 16:36 |
| henrix | smb: let me take a look at my notes, i'm sure i found a reference to this | 16:36 |
| smb | Seems version-wise we are back a few versions compared to debian testing but that late in the game I would rather not try to get someone to re-sync. | 16:37 |
| henrix | ah! found the reference | 16:38 |
| henrix | smb: https://bugzilla.novell.com/show_bug.cgi?id=676803 | 16:39 |
| ubot2 | bugzilla.novell.com bug 676803 in Kernel "iscsi enterprise target just hangs" [Critical,Resolved: fixed] | 16:39 |
| henrix | i guess it's the same issue, and they closed the issue with a newer version of the package | 16:39 |
| smb | Ok, 1.4.20.3 is newer than what the Debian version says. But I remember that there was an odd versioning thing with the sourceforge project. In their svn files there was references to the new number but not tarballed and released as is... | 16:43 |
| henrix | smb: yeah, can't remember the details, but when i was looking at that i found 1.4.20.3 only on the svn (or cvs...) | 16:45 |
| henrix | smb: but not on the tarballs | 16:45 |
| smb | Hm, so svn is at version470, if I read the Debian changlog correctly they went to 453 | 16:45 |
| smb | the suse report has someone claiming it works with 466... | 16:47 |
| smb | henrix, Hm, that might be the relevant commit... http://iscsitarget.svn.sourceforge.net/viewvc/iscsitarget/trunk/kernel/iscsi.c?r1=462&r2=461&pathrev=462 | 16:54 |
| henrix | smb: yeah, it could be | 16:54 |
| henrix | smb: i can take a closer look at this bug again if you want me to | 16:55 |
| henrix | smb: right now i'm working on the sru cycle, but i may get some time later on | 16:56 |
| henrix | smb: (tomorrow, probably) | 16:56 |
| smb | henrix, Since I have been poking at that package already, I could carry on as well. Just don't want to rip it from you in case you wanted to go on... | 16:58 |
| henrix | smb: well, from my activity report, this bug was not on my todo list anyway :) | 17:00 |
| henrix | smb: so, feel free to have some fun with it | 17:00 |
| smb | henrix, :) Ok, then let me try to find out whether we can fix it by that upstream change. | 17:01 |
| henrix | smb: cool. anyway, if you're busy, feel free to "delegate" it on me :) | 17:02 |
| smb | henrix, I would never say I am not busy (that just conjures new issues)... But it should fit in. ;) | 17:04 |
| tgardner | sforshee, are you seeing any video tearing on your MB Air ? maximize a shell, then click on the wi-fi icon a few times. | 17:35 |
| tgardner | cking, otp | 18:09 |
| cking | tgardner, ack | 18:09 |
| sforshee | tgardner, I haven't noticed any tearing, and I'm not seeing any doing what you described either | 18:11 |
| === arun__ is now known as arun_ | ||
| === tgardner is now known as tgardner-lunch | ||
| === tgardner-lunch is now known as tgardner | ||
| === shadeslayer_ is now known as shadeslayer | ||
| * tgardner relocates | 19:29 | |
| * tgardner -> EOD | 20:18 | |
| === adam_g_ is now known as adam_g | ||
| === bladernr_ is now known as bladernr_afk | ||
| RAOF | We would appear to be missing some ivybridge fixes in our kernel. The mainline build of drm-intel-next is stable, but our 3.2-20 kernel tends to hard-lock in Unity. | 23:04 |
| RAOF | I'm seeing if I can get some netconsole output when it dies to narrow down what the problem is. | 23:05 |
| ohsix | are there too many patches between drm-intel-next and 3.2-20 to see what one it may be? | 23:08 |
| RAOF | ohsix: There's almost two full kernel releases worth of development. | 23:11 |
| ohsix | ic | 23:11 |
| RAOF | Which is why I'm looking for some sort of error message other than “the system goes entirely unresponsive” - that should help point to a patch. | 23:11 |
| RAOF | Of course, now that I've got a netconsole hooked up it's not hanging. | 23:18 |
| ohsix | gpu hangs are scary | 23:19 |
| bryceh | RAOF, see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/961482 | 23:24 |
| ubot2 | Launchpad bug 961482 in linux "3.2.0-19 kernel fails to boot (-18 OK)" [Critical,Confirmed] | 23:24 |
| bryceh | (in case you hadn't already run across it) | 23:25 |
| bryceh | (and in case it's the same bug. that one is not ivybridge-specific afaik) | 23:25 |
| RAOF | That's not it; the system comes up fine, and works for an indeterminate period of time. | 23:26 |
| RAOF | And then, at some point (usually associated with alt-tab?) it hangs. | 23:26 |
| bryceh | ok | 23:27 |
| RAOF | Bah. That's highly annoying. | 23:31 |
| RAOF | netconsole stays around *just* long enough to print the timestamp of the kernel message when everything freezes. | 23:32 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!