[08:43] <tepsipakki> hi, is someone awake?-)
[08:43] <tepsipakki> I'm doing the X11R7.2 merge, and someone pointed out that the drm-modules in kernel need an update
[08:44] <tepsipakki> https://beta.launchpad.net/ubuntu/+source/xorg/+bug/84731
[08:44] <tepsipakki> look at the latest entries
[08:45] <crimsun> yes, I verified as much about two weeks ago when I was building against git
[08:46] <crimsun> it was /really/ fun rebuilding the entire stack
[08:46] <tepsipakki> :/
[08:46] <tepsipakki> 03:46 < gravity> Urgh... the intel driver requires pieces of the server source to build now. This is going to get ugly.
[08:46] <tepsipakki> that from #debian-x last night
[08:47] <crimsun> I'll peek in later, need to sleep a couple hours now
[08:47] <tepsipakki> heh
[08:53] <Mithrandir> aiui, those bits would get dragged in automatically in newer intel driver releases.
[09:57] <tepsipakki> I'm having problems with Thinkpad X60s shutting down the display when changing brightness. The workaround is to blacklist video.o, so this is a kernel-issue?
[09:58] <tepsipakki> http://www.mail-archive.com/ibm-acpi-devel@lists.sourceforge.net/msg00092.html
[01:29] <pkl_> tepsipakki: if you have to disable a kernel module to make it work correctly, then it is a kernel issue, yes.
[02:02] <tepsipakki> pkl_: yeah, I'll file a bug
[02:16] <BenC> technically speaking, that may also be an ACPI issue :)
[02:16] <BenC> IOW, a BIOS bug
[02:16] <tepsipakki> userspace?
[02:16] <BenC> BIOS
[02:16] <BenC> like your computer is broken because it doesn't use ACPI correctly
[02:16] <tepsipakki> I knew it
[02:17] <BenC> we can blacklist your computer from the video module though
[02:17] <BenC> so file the bug, and attach the output of "sudo dmidecode"
[02:18] <tepsipakki> I just filed it, will attach that to it
[02:27] <zul_> heylo
[02:29] <tepsipakki> BenC: bug 87028
[02:29] <tepsipakki> hm
[02:29] <tepsipakki> anyway, dmidecode output attached
[02:33] <BenC> tepsipakki: thanks
[02:50] <zdzichuBG> hi guys
[02:50] <zdzichuBG> I believe you won't backport dyntics to Feisty kernel?
[03:42] <BenC> zdzichuBG: that's correct
[04:50] <abogani> Mithrandir: Can i disturb you for one question?
[04:56] <Mithrandir> abogani: sure
[04:58] <abogani> What my Spec (https://blueprints.launchpad.net/ubuntu/+spec/realtime) lacks to achieve its mission (== inclusion in the Universe repositary)?
[05:00] <seb128> hi
[05:01] <Mithrandir> abogani: the kernel package would have to be done as a patch to linux-source and not ship a complete copy of the linux kernel source.
[05:01] <seb128> I've a problem similar to bug #76489 with a RTL-8029 card, do you guys prefer a new bug because that's not the same card model?
[05:03] <abogani> Mithrandir: kernel package is only a comfort for testers
[05:03] <Mithrandir> abogani: well, it's what would end up in universe.
[05:05] <seb128> pkl_: ping? about the bug I just mentioned, you marked it Fix Commited
[05:07] <pkl_> seb128: yes a new bug would be prefered, because it will require a separate workaround.
[05:07] <seb128> ok
[05:07] <seb128> thank you
[05:07] <seb128> what informations do you need?
[05:07] <seb128> lspci output?
[05:08] <abogani> Mithrandir: As you can see from https://wiki.ubuntu.com/RealTime now i release also a patch (obtained with a git-diff).
[05:10] <pkl_> seb128: yes, as much information as you can give  :-) dmesg, and lspci definately.
[05:37] <seb128> pkl_: bug #87078, do you need something else?
[05:46] <pkl_> seb128: I'll have a look into the bug.  If I need more info I'll ask...
[05:46] <seb128> ok, thank you
[06:10] <zul> BenC: where does the ubuntu/ms/memstick.c come from?
[06:10] <BenC> zul: Some evil place...I don't think it works though
[06:10] <zdzichuBG> :( too bad, I think my laptop would love dynticks
[06:11] <zul> ah ok because its missing a header file 
[06:11] <zul> #86725
[06:33] <ScottK> I recently reported a wireless bug (bug #86742).  I wanted to check in and see if it's complete so it'll be useful when someone gets to it.
[06:41] <fdoving> .. what can make ksoftirqd/0 use ~90% cpu?.. anyone seen that before?
[07:10] <BenC> fdoving: Usually some kernel task...could be anything, since it's a generic drop for some core tasks (network bottom halves I believe, etc)
[07:13] <fdoving> ok. could it be related to the broken bcm43xx driver i try to use?
[07:13] <BenC> could be
[07:14] <fdoving> thanks, i'll keep that in mind and see if i encounter it again without the driver.
[07:15] <BenC> fixed up bcm43xx coming tonight
[07:17] <maks_> bcm43xx can be fixed?
[07:18] <BenC> maks_: Withing reason :)
[07:30] <zul> heh the mad bug reporter is at it again
[07:30] <Nafallo> haha
[09:37] <Mithrandir> so, I have an external USB-powered hard drive which seems to fail if I move lots of data to or from it.  Is there anything I can twiddle in the kernel to either give it more power (I guess that's impossible) or limit the transfer speed somehow?
[09:56] <BenC> Mithrandir: there's some stuff you can set for usb-storage, they might help
[09:57] <BenC> Mithrandir: does the hd have the ability to connect to external power so you can test your theory?
[09:58] <Mithrandir> BenC: no, it doesn't.  It also seems to be happy in some cases, typically after being plugged in, unplugged a few times..
[09:58] <Mithrandir> I have the same problem from multiple machines (two amd64s, one x40 laptop), so I suspect it's not just a dodgy usb controller.
[09:58] <BenC> Mithrandir: do you have any other usb-storage devices to compare?
[09:58] <BenC> ah, ok
[09:59] <Mithrandir> I have another usb disk which has some of the same problems; my media player is fine (but that's solid state and just charges off USB)
[10:00] <Mithrandir> I guess it could be that the disk is so shit it ends up overrunning its buffer somehow and then getting into a cough.
[10:00] <Mithrandir> it typically looks like:
[10:00] <Mithrandir> 273764.964000]  sd 1:0:0:0: SCSI error: return code = 0x00050000
[10:00] <Mithrandir> [273764.964000]  end_request: I/O error, dev sdb, sector 4128
[10:00] <Mithrandir> [275435.140000]  end_request: I/O error, dev sda, sector 202664311
[10:01] <Mithrandir> and then Buffer I/O error and "lost page write" for a little while before ext3 abrts the journal and the fs is remounted r/o
[10:03] <zul> maybe it needs an entry in the unusual_devs.h 
[10:04] <BenC> Mithrandir: Are you sure the drive isn't going bad?
[10:04] <BenC> Failed sector reads usually mean that..I would have expected usb-storage weirdness to cause a timeout rather than sector errors
[10:05] <BenC> the return code is usually from the device itself
[10:05] <Mithrandir> BenC: I haven't badblocked it, so no, I'm not sure
[10:06] <Mithrandir> it also seems to refuse to talk SMART with my machine.
[10:10] <Mithrandir> trying a badblocks test now.
[10:10] <zul> later..
[10:23] <JanC> maybe you can get the disk out of the case and put it in a PC?
[10:25] <Mithrandir> I'd prefer not to void the warranty on a disk only a couple of months old. :-)