=== RAOF_ is now known as RAOF
[01:58] <davidrock> I'm experiencing a bug (no backlight, intel mobile graphics). It is present on 2.6.38 and I've tested up to 2.6.39rc4. The bug is not present in 2.6.35-28 which I'm running now. I'm new to linux, what should I do to report this?
[01:59] <lifeless> run 'ubuntu-bug linux' 
[01:59] <lifeless> though I suspect that this is a known issue, I remember seeing discussion on it
[02:01] <davidrock> If it's known, I won't worry about it. Don't want to flood the bug system
[02:07] <lifeless> RAOF: it is known, right?
=== serge_ is now known as hallyn
[02:35] <RAOF> I think it's known.
[02:35] <RAOF> lifeless: It's not *fixed*, but it's known.
[02:35] <jk-> an unknown known?
[02:35] <RAOF> :)
[03:25] <Darren> hello?
[03:27] <RAOF> Hm.  Suppressing join/part events makes commenting on people who pop in for a minute and then bail less fun.
[03:30] <TheMuso> heh
[03:30] <TheMuso> I think all documentation relating to IRC needs to talk about people idling in channels.
=== michaelh1 is now known as michaelh1|away
=== michaelh1|away is now known as michaelh1
=== michaelh1 is now known as michaelh1|away
=== zz_eagles0513875 is now known as eagles0513875
=== yofel_ is now known as yofel
=== michaelh1|away is now known as michaelh1
=== michaelh1 is now known as michaelh1|away
[09:42] <jussi> hello all!
[09:42] <jussi> I just got a nice kernel panic on natty, anybody care to take a look? 
[09:43] <jussi> also, is it safe to share the panic info or do i need to be careful? 
[09:44] <dupondje> feel free to share
[09:45] <smb> Though in general it is better to open a bug report because otherwise additional info is too easily lost
[09:46] <dupondje> maby there is already a bugreport of it :)
[09:46] <smb> That is quite possible. :)
[09:46] <jussi> http://wstaw.org/m/2011/05/02/2011-05-02_10-47-11_791.jpg
[09:47] <jussi> I can do a bug report no issues, just wanted a bit of feedback first
[09:47] <jussi> phone quality picture ;)
[09:48]  * dupondje needs somebody that can change priority of bug :)
[09:48] <dupondje> jussi: you get that @ random or ?
[09:48] <jussi> dupondje: only happened once. just random in the middle of nothing
[09:49] <smb> That is one of the questions that usually arise. :) Does it happen consistently, when, is it bare metal or a vm, right at boot or later...
[09:49] <smb> But it seems not consistently from the last answer
[09:49] <smb> Was that right at boot?
[09:50] <jussi> smb: first time. I run kubuntu, was not at boot. just "happened"
[09:50] <jussi> the only thing that I can think of that might have been associated with it was that I installed "gobi-loader" from the repos about 5 mins before.
[09:51] <smb> Cause it has some older trace above beginning with start_kernel before. Not that we can trust any of the lines with ? too much (which is unfortunately al of them)
[09:51] <jussi> !info gobi-loader
[09:52] <jussi> ubot2: you dead? 
[09:52] <ubot2> Factoid 'you dead?' not found
[09:52] <smb> Noted
[09:52] <jussi> ok, you guys dont have !info in here. strange. 
[09:52]  * jussi goes to find jpds
[09:52] <smb> jussi, It is probably a special one. Not always cooperative
[09:53] <jussi> smb: Im the owner of ubottu, and on the IRCC, so when somethings missing, I wonder  ;)
[09:53] <smb> jussi, Good to know. :)
[09:55] <dupondje> jussi: the kernel panic looks like a bug in the network driver ...
[09:55] <smb> jussi, Yeah, at least the middle section. 
[09:56] <jussi> dupondje: bah. couild it be something to do with the gobi-loader?  (firmware loader for the 3g card... which incidentally still doesnt work)
[09:56] <smb> But there is always the chance of some general corruption going on, up to some ram faults
[09:57] <dupondje> Well indeed, if the panic is always the same ... then its network driver error
[09:57] <dupondje> else it could be cpu / ram / other shit :)
[09:57] <jussi> hrm, right. So, a bug report is in order? 
[09:57] <smb> jussi, the gobi loader itself would initiate some firmware loading. Of course if somehow that goes wrong maybe stuff gets loaded somewhere bad
[09:57] <jussi> and do I report it against the network manager? gobi-loader? linux-kernel? 
[09:58] <smb> I would start with linux (kernel)
[09:58] <smb> Even if the gobi loader is incorrect, it should not be able to crash the kernle
[09:59] <smb> You should try to see whether it can gfet retriggered somehow
[09:59] <smb> Is that 3g device a usb dongle or builtin?
[09:59] <jussi> ok, linux-image then? :)
[09:59] <jussi> built in. its a HP UN2420
[09:59] <dupondje> https://bugs.launchpad.net/ubuntu/+source/linux
[09:59] <smb> jussi, just linux 
[10:00] <jussi> smb: ahh, k. 
[10:01] <smb> jussi, So probably try to get the loading command to be able to trigger the firmware loading request at will. To see whether that correlates to crashes
[10:02] <jussi> smb: ahh, Ill see if I can what the postinstall scripts are for gobi-loader (see if it is that)
[10:02] <smb> jussi, There should be something in /lib/udev/rules.d as well
[10:03] <smb> Basically gobi_loader plus some devno or id or so. Don't remember the exact details
[10:04] <jussi> http://paste.ubuntu.com/602168/
[10:04] <smb> That would be called on each reboot too, so if it is ok now and you did not deinstall the package, it is probably something else
[10:05] <jussi> ok
[10:08] <jussi> bug 775432
[10:09] <ubot2> Launchpad bug 775432 in linux "Kernel panic. " [Undecided,New] https://launchpad.net/bugs/775432
[10:10] <dupondje> I would at least add the screenshot :) else its quite ... useless :)
[10:12] <jussi> oh bah
[10:13] <jussi> thanks [blushes]
[10:13] <jussi> done :D
[10:14] <jussi> You know, sometimes I just forget things... :(
[10:17] <dupondje> Kernel dev's are in vacation btw ? :)
[10:17] <smb> We never would say. :-P
[10:18] <dupondje> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/774363 => needs to get on the radar :) so it surely gets fixed in next kernel release in natty :)
[10:18] <ubot2> Launchpad bug 774363 in linux "cx88-blackbird driver hangs when used" [Undecided,New]
[10:20] <smb> dupondje, The most failproof way to get those kind of things done is to make sure the upstream developer is made aware that the patch should somehow go to stable upstream as well. Then it flows back to everyone and into the ubuntu kernel automatically
[10:21] <dupondje> Its reported to the kernel dev's :)
[10:21] <dupondje> see https://bugzilla.kernel.org/show_bug.cgi?id=31962
[10:21] <ubot2> bugzilla.kernel.org bug 31962 in cx88 "cx88-blackbird broken (since 2.6.37 ?)" [High,New]
[10:23] <smb> Right, the drawback is that even upstream maintainers do always know how to get into stable (without getting semi-nasty comments from Greg)
[10:24] <smb> Though benh from debian does a lot
[10:25] <dupondje> dunno when it gets into 2.6.38.x or when its just fixed in newer release.
[10:25] <dupondje> Not all bugs get into 2.6.38.x I guess ?
[10:26] <smb> No, the trick is to have a "Cc: stable@kernel.org" in the signed-off-by section when it get submitted for Linus tree
[10:26] <smb> Then most happens automatically
[10:27] <smb> It can be done later, after it hit Linus tree, but then needs manual sending with the upstream id and best from or with the maintainer on cc
[10:28] <dupondje> oh ok :)
[10:28] <dupondje> Then just somebody needs to push it in the Linux tree :)
[10:35] <smb> dupondje, Just... :) It can get a bit tedious. In the kernel tree under scripts, there is a get_maintainer script which provided with the patch would spit out a lost of possible people, mailing lists to post to.
[10:36] <smb> This would make it probably reach those with better knowledge quicker. And of course it always helps to have patches submitted from someone that has the hardware and can state that this is helping.
[10:43] <dupondje> seems like somebody already confirmed it worked ... :)
[10:43] <dupondje> http://thread.gmane.org/gmane.linux.kernel/1118815
[10:47] <smb> Yes, saw that. Just not sure any v4l maintainers were listening (yet). But essentially, first it has to go upstream, then it can get SRUed (best via upstream stable)
=== eagles0513875 is now known as zz_eagles0513875
=== diwic is now known as diwic_afk
=== diwic_afk is now known as diwic
[16:22]  * ogasawara back in an hour (have to run the dog to the vet unexpectedly)
[17:31]  * ppisati -> gym
=== hallyn is now known as hallyn_afk
[18:00] <JFo> <-food
=== kamal1 is now known as kamal
[19:12] <ohsix> can someone comment on if the battery information upower even uses is generally available from the kernel anymore? https://bugs.launchpad.net/ubuntu/+source/upower/+bug/629258
[19:12] <ubot2> Launchpad bug 629258 in devicekit-power "Battery life estimation never comes around" [Medium,In progress]
[19:15]  * tgardner --> lunch
[19:17] <stgraber> there should be a lttng related e-mail in -kernel's moderation queue if someone with the power has a sec to accept it. Thanks
=== michaelh1|away is now known as michaelh1
[19:55] <sconklin> hi folks! Power and internet are back on at my house. We didn't have nearly the devastation as further south but here are some photos, a lot of which are from near where I live:
[19:55] <sconklin> http://photos.al.com/4462/gallery/aerial_view_of_the_north_alabama_tornado_damage_from_april_27_2011/index.html
[19:56] <sconklin> Carter's Gin, Toney, Anderson Hills, Harvest are all about 7 miles from my house
[19:58] <tgardner> sconklin, good to see you back. thats some serious carnage.
[19:59] <jjohansen> sconklin: wow, nice to have you back
[20:01] <sconklin> Physically, we were fine - we had plenty of camping gear and food, and the city water never went down. Although we had filtration available and lots of water available if that had happened.
[20:02] <sconklin> I've been working at the Red Cross office for the last few days, so I could occasionally borrow generator power and an internet connection
[20:03] <sconklin> I was also active during the storms. It was good to be busy
[20:05] <sconklin> I think I'll be back at work tomorrow
=== michaelh1 is now known as michaelh1|away
=== Phoenix][_ is now known as Specialist
[20:40]  * jjohansen lunch
=== zyga is now known as zyga-afk
[20:56] <Specialist> hi there. just a uestion regarding the ubuntu kernel maintenance / bug fixing procedures: now that natty has been released, how do fixes make it into natty's kernel? i am specifically talking about regressions that worked in maverick and for which upstream patches are already available.
[20:59] <bjf> Specialist, natty is now considered a "stable" kernel and the process is our SRU process
[21:00] <bjf> Specialist, if a commit you are interested in is one that has been submitted by upstream to upstream-stable, we will be getting those automatically
[21:00] <Specialist> bjf: perfect, thanks!
=== Sarvatt_ is now known as Sarvatt
=== hallyn_afk is now known as hallyn
[23:20] <root_> who
[23:30] <root_> 
[23:30] <root_> quit
[23:44] <bdmurray> ogasawara: does the dmesg in bug 775754 indicated failure with a cd? a hard drive? or both?
[23:44] <ubot2> Launchpad bug 775754 in linux "package linux-image-generic 2.6.38.8.22 failed to install/upgrade: проблемы зависимостей -- оставляем не настроенным" [Undecided,New] https://launchpad.net/bugs/775754