dtchen | Kano: ar9170usb isn't enabled in the Ubuntu builds AFAIR; i've been using compat-wireless with the firmware from linux-firmware.git. | 00:52 |
---|---|---|
Kano | you are lying | 00:52 |
dtchen | is it enabled now for karmic? | 00:53 |
Kano | http://packages.ubuntu.com/search?searchon=contents&keywords=ar9170usb.ko&mode=exactfilename&suite=karmic&arch=any | 00:53 |
Kano | they are of course in the image | 00:54 |
dtchen | ah, good | 00:54 |
dtchen | apw: would you sync the ar9170usb config (=m) in the c-o-d builds, too? | 00:55 |
Kano | where are the 2.6.30 source packages | 00:55 |
dtchen | canonically? they're gone; karmic is using 2.6.31-git. you'll have to use launchpadlibrarian for older source packages (e.g., https://edge.launchpad.net/ubuntu/+source/linux/2.6.30-10.12). | 00:57 |
Kano | you dont used a orig file? | 00:58 |
dtchen | it doesn't appear so | 00:59 |
Kano | no errors about dm with 2.6.31 in launchpad? | 01:03 |
Kano | that's definitely broken | 01:03 |
dtchen | i can't speak for karmic's source package at the moment; i'm using a c-o-d build (2009-07-09) | 01:05 |
Kano | c-o-d? | 01:07 |
dtchen | "crack of the day" builds: http://kernel.ubuntu.com/~kernel-ppa/mainline/daily/ | 01:11 |
Kano | i see | 01:12 |
Kano | wenn i can not use those, i do not use ubuntu as base. i always have to apply some patches before building | 01:12 |
dtchen | are you patching pristine upstream? those are upstream kernel.org sources. | 01:13 |
Kano | no some config settings | 01:15 |
Kano | i enable the wireless legacy code and some other things on the fly, also i correct known bugs | 01:16 |
Kano | somehow u likes to have some bugs, prefer to fix em | 01:16 |
dtchen | :-) | 01:17 |
Kano | like my kernel has working dm, comedi s626 only loading for one special device not generic, and some other changes | 01:18 |
Kano | http://kanotix.com/files/excalibur/linux-2.6.31-generic/source/ | 01:19 |
Kano | i even have got aufs2 | 01:19 |
Kano | also i use lzma compression | 01:20 |
Kano | for vmlinuz | 01:20 |
sn9 | which lzma patch did you choose? there are several | 01:26 |
Kano | no patch | 01:27 |
Kano | thats one config setting | 01:27 |
Kano | CONFIG_KERNEL_LZMA=y | 01:28 |
Kano | i compress kernel + initrd with lzma, u uses lzma compression for initrd only in live mode it seems | 01:30 |
Kano | but they still did not compress the kernel image with lzma | 01:30 |
apw | smb it is possible that it can be allowed to be interrupted | 08:43 |
apw | as the semantic is likely 'when complete all cpus must have flushed the tlb' | 08:43 |
smb | Hm, ok. Cause in that one case it looked like | 08:43 |
smb | from the printk's I saw the printk before calling the function (after changing the attrs) and the BUG trace is from some acpi code | 08:44 |
smb | but I have two more printk's in global_flush_tlb | 08:44 |
apw | there is no guarentee they have not been 'printed' and not yet flushed out | 08:45 |
apw | which acpi code is blammoing | 08:45 |
smb | wouldn't it with the BUG statement? Something generic called from thread helper: autoremove.wake.function->...>acpi.os.execute.deferred | 08:46 |
apw | depends on the output device, all printk does is queue it for printing in the dmesg buffer and then wake up the drivers | 08:48 |
apw | some drivers are more immediate than others | 08:48 |
apw | serial for instance definatly is not | 08:49 |
apw | smb what is the specific panic, do you have a picture? | 08:50 |
smb | Hm, currently using vga with smal font | 08:50 |
smb | apw, yes | 08:50 |
apw | there must be more information in there, can you get the picture up somewhere | 08:50 |
smb | null pointer dereference | 08:50 |
apw | hrm | 08:50 |
apw | if the remapping was gone correctly then it would not make any difference if the flush has occured or not | 08:52 |
smb | http://www.krikkit.de/aa1debug/07100001.JPG | 08:54 |
smb | http://www.krikkit.de/aa1debug/07100003.JPG is a bit better | 08:54 |
smb | https://pastebin.canonical.com/19558/ | 08:59 |
apw | that is bugging twice | 08:59 |
smb | That would be the code snippled called | 08:59 |
apw | the stack is not from the original bug by the looks | 08:59 |
apw | and the first one is between your two debug statements | 08:59 |
smb | apw, Oh it is only one. Just two pictures of it | 09:00 |
apw | need to find our where that first EIP is on line 4 | 09:00 |
smb | But the rest yeah | 09:00 |
apw | smb, no in the second picture there are two panics | 09:00 |
apw | one on lines 4-6 | 09:00 |
apw | and one on 7- | 09:01 |
apw | the stack is as likely to be from the second one | 09:01 |
smb | Oh, right. The Null pointer and then Oops: 0003 | 09:01 |
apw | need to translate c0105550 on your kernel | 09:01 |
smb | Just a second. Booting the build machine | 09:02 |
smb | Hm, c0105550 -> device_not_available | 09:04 |
smb | apw, Oh actually I just noticed the between printing the eip of the first oops and the BUG, the flush_map(...) is from within global_flush_tlb | 09:12 |
smb | One of the debug statements I added | 09:12 |
apw | yeah saw that | 09:12 |
smb | Hrm, missed it on the camera and on the screen :/ | 09:13 |
apw | are interrupts turned off during the conversion to r/o? | 09:14 |
apw | do you know if the other cpu threads are awake when that code runs? | 09:15 |
smb | a) I don't think so, just spinlocks while taking lists out afaik. b) not sure but checking | 09:15 |
apw | smb, ok the first panic is very odd as its panicing on the stack push | 09:16 |
smb | b) it is after bringing up the hyperthreads | 09:17 |
smb | apw, dumb question, how do I see this? | 09:17 |
apw | so its possible the other thread is losing its stack or similar | 09:17 |
apw | ENTRY(device_not_available) | 09:18 |
apw | RING0_INT_FRAME | 09:18 |
apw | pushl $-1 # mark this as an int | 09:18 |
apw | CFI_ADJUST_CFA_OFFSET 4 | 09:18 |
apw | pushl $do_device_not_available | 09:18 |
apw | CFI_ADJUST_CFA_OFFSET 4 | 09:18 |
apw | jmp error_code | 09:18 |
apw | CFI_ENDPROC | 09:18 |
apw | END(device_not_available) | 09:18 |
apw | it the eip is exactly device_not_available ... then it is pushing a frame | 09:18 |
smb | Ok, yes it is. As the next eip is exactly the entry of call_function_interrupt | 09:19 |
apw | smb, i don't understand | 09:19 |
apw | phone? | 09:19 |
smb | ok | 09:20 |
* apw watches his fan turn on and off correctly on his thinkpad .. amazing | 11:08 | |
sahil_ | hey all, got a bit of an issue, when i boot with acpi=off everything boots but of course acpi does not work, when i boot with nolapic acpi works but wireless does not, any ideas? | 13:12 |
apw | why are you booting with either of those? | 13:19 |
=== fabbione is now known as fabbione-vac | ||
primes2h | ogasawara_: I have again the laptop I told you some days ago. Tell me if you need something. | 14:38 |
primes2h | ogasawara_: Ehm, Hello, first of all... ;) | 14:47 |
maco | 2.6.31-2: does it include the fix for tun interfaces? | 14:53 |
rgz | Is there a generic problem with the 2.6.28-13 kernel build on i386? | 15:06 |
smb | rgz, It runs for me | 15:10 |
smb | What problem do you have? | 15:10 |
rgz | smb: It first gives off some error about my resolution bindings, after grub's loaded; says that 307 doesn't exist, I change the splash resolution, it boots up gdm but all I/O devices don't function. | 15:13 |
rgz | I'll get a log as soon as I can, just wondered if anyone else experienced something similar. | 15:14 |
smb | rgz, It does not ring a bell immediately. Hm, 307 might be a resolution but why this affects IO devices. HAve you once tried removing splash? | 15:16 |
rgz | smb: Yeah, I looked through the logs, might be something to do with nvidia drivers, but I'm not entirely sure. | 15:21 |
rgz | It's a pain; but I'll come back when I have the logs in check. | 15:23 |
smb | rgz, Just to enlighten me. ;-) Did using splash or not make a difference. Ok | 15:23 |
nanomad | Can anyone have a look at #21367 it can be fixed in (at most) 5 minutes | 15:26 |
rgz | smb: No, no difference. | 15:27 |
smb | rgz, ok thanks | 15:27 |
=== Nicke_ is now known as Nicke | ||
jdstrand | there is a newer version of firmware for ipw2200 than what's in linux-firmware (bug #357968). license in the tarball is the same. would I be stepping on anyone's toes if I uploaded an updated linux-firmware to karmic? | 16:08 |
ubot3 | Malone bug 357968 in linux-firmware "Please update ipw2200 firmware to version 3.1" [Undecided,Triaged] https://launchpad.net/bugs/357968 | 16:08 |
smb | jdstrand, I would not believe so. I believe the names were incremental (so old ones stay there), right? | 16:14 |
jdstrand | smb: I don't understand your question. it is a native package, I would adjust the version appropriately | 16:14 |
smb | jdstrand, It is rather about the version of the firmware file. I just believe those get adapted, sod the old firmware files stay | 16:15 |
jdstrand | smb: linux-firmware simply has the untarred files in firmware/ipw2200. I figured I'd put the new ones there instead | 16:17 |
jdstrand | is that not the proper way? | 16:17 |
jdstrand | all the filenames are the same | 16:17 |
jdstrand | the LICENSE is the same | 16:17 |
smb | Oh I see I confused that with other wireless firmaware which has version numbers in the filename and the driver loads just the highest supported | 16:19 |
smb | So here it is just a replacement as it looks | 16:19 |
* jdstrand nods | 16:20 | |
smb | There has been a request to upgrade the iwl4965 just today. I wonder whether it will make sense to get that done with one update | 16:21 |
smb | oh.. forgott, jdstrand ^ | 16:22 |
jdstrand | smb: I don't know anything about iwl4965. I can say preliminary testing shows the ipw2200 driver works fine on 2.6.28 (haven't tested on karmic) | 16:23 |
smb | apw, Would you feel being stepped on something when the firmware package gets done? | 16:23 |
jdstrand | I'm happy to do an ipw2200 only upload | 16:24 |
jdstrand | otherwise, the details are in the bug for ipw2200 | 16:24 |
smb | jdstrand, Ok, for simplicity. Lets do one by one | 16:24 |
jdstrand | alright, consider it done :) | 16:24 |
apw | smb, jdstrand the only thing about firmware is legal issues, i would just touch based with pgraner to make sure he is happy | 16:29 |
jdstrand | apw: the license in the new tarball is the same as in firmware/ipw2200 of linux-firmware | 16:29 |
apw | then that sounds fine to me, i would just let pgraner know you are updating it, as there is a review ongoing | 16:30 |
pgraner | jdstrand: then it good | 16:30 |
jdstrand | thanks guys-- will test on karmic and upload | 16:30 |
pgraner | apw, jdstrand: I have it noted. Thanks for the heads up | 16:30 |
nanomad | jdstrands, Can anyone have a look at #21367 also? | 16:30 |
jdstrand | nanomad: not really my jurisdiction, sorry | 16:31 |
nanomad | jdstrand, np, thanks anyway | 16:31 |
jdstrand | nanomad: and that isn't linux-firmware, bug linux anyway | 16:32 |
nanomad | yes, i noticed that :) | 16:32 |
apw | bug #21367 | 16:32 |
ubot3 | Malone bug 21367 in linux "Wifi-enabled led is not lit on ipw2200 cards" [Low,Confirmed] https://launchpad.net/bugs/21367 | 16:32 |
smb | The question is really why upstream did not change the default. It might be work on many but just not on all. Pragmatically I got a ipw2200 and my led works without... | 16:34 |
apw | nanomad, whats the question with it? | 16:35 |
nanomad | apw, it got disabled in karmic | 16:35 |
apw | it was fixed in Jaunty if I understand things | 16:35 |
nanomad | since it is not fixed upstream | 16:35 |
nanomad | it got lost from jaunty -> karmic | 16:35 |
nanomad | if i manually modprobe ipw2200 with led=1 it works | 16:36 |
smb | Hm, ok. So we had it with the other default in Jaunty | 16:37 |
nanomad | smb, looks like that | 16:37 |
apw | smb can you accept the nom for jaunty for me on that bug | 16:37 |
apw | and i'll sort out the states | 16:37 |
* smb wait for lp | 16:38 | |
smb | ok | 16:38 |
nanomad | actually, it would be nice to report it upstream. Or we will have the same bug at the next kernel bump | 16:38 |
apw | smb, ok thats been applied to jaunty since the karmic fork and all the commits there are on my list to review | 16:38 |
smb | apw, We should check to get it upstream this time,... | 16:39 |
smb | nanomad, yep | 16:39 |
smb | Either we will know why not or wo't loose it agian | 16:39 |
apw | smb yep. will do that as its been on for 3 months | 16:39 |
smb | apw, ok, quickly scanned the ipw2200 bugs and it did not look like there was one of "suddenly broke" | 16:43 |
apw | smb, might be worth rejecting the nom for karmic on that bug as it means nothing | 16:43 |
apw | smb, thanks for that | 16:43 |
smb | apw, Yeah, will reject that. You are not on it nw? | 16:44 |
apw | i've assigned it me and added it to my list to close when karmic has it | 16:46 |
smb | apw, ok, nomination rejected | 16:46 |
=== bjf_afk is now known as bjf | ||
apw | smb, thanks | 16:47 |
nanomad | apw, smb, thanks guys. | 16:49 |
=== maco_ is now known as maco | ||
jdstrand | apw: I uploaded linux-firmware 1.14 to karmic. I tried to git clone http://kernel.ubuntu.com/git-repos/ubuntu/linux-firmware-karmic.git/ but got: | 17:05 |
jdstrand | fatal: http://kernel.ubuntu.com/git-repos/ubuntu/linux-firmware-karmic.git//info/refs not found: did you run git update-server-info on the server? | 17:05 |
apw | its meant to get run on every commit magically | 17:05 |
jdstrand | apw: I uploaded the new source package to /home/jamie/uploads/karmic on chinstrap | 17:05 |
jdstrand | apw: I looked around for docs on how to update linux-firmware, but nothing popped up | 17:06 |
jdstrand | apw: if you point me at it, I'll do it, otherwise you can get the source package on chinstrap or wait for LP | 17:06 |
apw | ack | 17:07 |
wip | hi people, i've been using jaunty for months, but the RT-kernel is still not updated. it's full of bug. any release date? is someone working on it? | 17:09 |
wip | example, worst bug for me: https://bugs.launchpad.net/ubuntu/+source/linux-rt/+bug/374026 | 17:12 |
ubot3 | Malone bug 374026 in linux-rt "Kernel threads using 100% on one of the two CPUs" [Undecided,Confirmed] | 17:12 |
smb | apw, Is there actually a git for linux-firmware...? | 17:12 |
apw | smb dunno, wanna try and find out and sort that for me | 17:13 |
* apw is snowed | 17:13 | |
wip | still undecided... | 17:13 |
smb | wip, The rt kernel is community maintained. Don't know the status | 17:13 |
smb | apw, can do | 17:13 |
wip | smb: thanks for the information, it | 17:15 |
wip | smb: but it means that i should recompile my kernel... ouch... | 17:15 |
=== ogasawara_ is now known as ogasawara | ||
Q-FUNK | hello | 20:09 |
Q-FUNK | could anyone help me with LP bug #396286 ? | 20:10 |
ubot3 | Malone bug 396286 in linux "kernel 2.6.31-generic oops after loading initramfs" [Undecided,New] https://launchpad.net/bugs/396286 | 20:10 |
Q-FUNK | apw: I beleive that you were the one who replied to LP bug #241307 earlier. I think that we managed to narrow down the source of the problem. is there anythign else I can add? | 20:12 |
ubot3 | Malone bug 241307 in linux "kernel oops during bootup in LTSP" [High,In progress] https://launchpad.net/bugs/241307 | 20:12 |
apw | Q-FUNK, looks like you have some significant update there | 20:13 |
apw | i need to read what you've said and comment, busy right now, will look next week | 20:14 |
Q-FUNK | apw: at least, it looks like wwx and leio/mraudsepp (freenode) have done a good job of narrowing down the cause. | 20:14 |
Q-FUNK | apw: wwx pointed out that with early releases of kernel 2.6.23, it was still possible to revert the change with an easy patch, but not anymore. | 20:15 |
Q-FUNK | alright. I'll wait for your followup, then. :) | 20:15 |
apw | yeah probabally futzed by the merge of 32 and 64 bit x86 | 20:16 |
apw | on my list for next week | 20:16 |
Q-FUNK | is that what the code that replaced the old ia32 init code in ASM does? attempt to combine init code for x32 and x64 into one? | 20:17 |
apw | no i mean that is what likely futses reverting the patch | 20:20 |
apw | the previous bug you mention sounds liek a very early panic, normally we take piccies of those with a digitcal camera and attach those to the bug | 20:20 |
Q-FUNK | I'd gladly take a pic (as I previously did for the 2.6.24 kernel bug), but not much core dump fits on the default 24-line VGA screen. | 20:21 |
Q-FUNK | yes, it indeed feels like an early kernel panic. I'm just not sure what causes it | 20:21 |
apw | if you add vga=ask to the kernel command line it lets you pick a smaller font | 20:23 |
Q-FUNK | yup. but the max still is 80x60. we cannot quite fit the whole kernel dump | 20:33 |
Q-FUNK | anyhow. attached. hope it helps. | 20:34 |
vitovt | Hi everybody! I need more recent kernel like 2.6.29. I installed it from http://kernel.ubuntu.com/~kernel-ppa/. But there is no restricted extras. Where I could get config of existing kernel (like 2.6.28) including RESTRICTED EXTRAS. How could I buld new kernel very similar to default ? | 20:41 |
maco | vitovt, um, restricted extras packags just have like...flash and java and mp3 | 20:56 |
vitovt | ow. sorry. i mean restricted-modules | 20:58 |
vitovt | it's too late in my country and I sleeppy now :) | 20:59 |
vitovt | 2 | 21:04 |
vitovt | 3 | 21:04 |
vitovt | 4 | 21:04 |
vitovt | 5 | 21:04 |
vitovt | 6 | 21:04 |
vitovt | 7 | 21:04 |
vitovt | 21:04 | |
vitovt | I have a big problem with 2.6.28 kernel in mainline. | 21:04 |
vitovt | When i'm out of RAM - swap usage allmost impossible. | 21:04 |
vitovt | There are a lot of errors in syslog (Error allocating memory). | 21:04 |
vitovt | I used kernel 2.6.29 from (http://kernel.ubuntu.com/~kernel-ppa/). It works great. But miss some important modules for me. | 21:04 |
vitovt | Also I need to make some modification (framebuffers support) | 21:04 |
vitovt | How I can build restricted extras for 2.6.29 and make configuration allmost similar to 2.6.28-generic ? | 21:04 |
vitovt | Sorry for possible flood | 21:04 |
dtchen | vitovt: clone the git tree; see kernel.ubuntu.com/git/ | 21:45 |
dtchen | vitovt: see the knowledgebase on the kernel wiki for pointers to build it against the appropriate kernel headers | 21:46 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!