[12:59] <msa> I've kernel mod doing debug <7> msg's, however cant seem to get them visible anywhere on intrepid... (used to -work fine earlier into syslog
[13:00] <msa> killing syslogd and klogd, and doing "sudo cat /proc/kmsg" shows them, but does not do it continuously (again, -used to work fine)
[13:02] <msa> (e.g. I can see all messages wth cat /proc/kmsg, but have to keep doing ctrl-c and reissuing the command)
[13:15] <riham> guys, I would like to ask a Q about kernel native aio , io_submit seems to be blocking so ...  does anybody have a clue ?
[15:15] <JackWinter> is this the right place for problems compiling a kernel module under kubuntu 8.04 ?
[15:19] <JackWinter> i'm trying to install vbox-2.1.4 on kubuntu 8.04.  i can compile the kernel module but when i try to load it i get the following error: [  621.528827] vboxdrv: Unknown symbol __stack_chk_fail
[15:20] <JackWinter> have tried different kernels and also removing and reinstalling linux-headers
[15:20] <mjg59> Build with -fno-stack-protector
[15:20] <JackWinter> mjg59: sorry not very good at this.  how do i do that ?  can i change a global option for my system ?
[15:21] <mjg59> I've no idea how the virtualbox build system works
[15:22] <JackWinter> it's got a Makefile.  what is strange is that it worked before, something must have changed on my system
[15:22] <smb_tp> In general I would suspect they use a "normal" out of tree thing...
[15:23] <smb_tp> What exactly is before. 8.04 but older kernel?
[15:23] <JackWinter> i think i have a problem loading the closed nvidia drivers too.  also a kernel module
[15:25] <smb_tp> JackWinter, Hm, could it be that this happened after getting 2.6.24-23.48 kernel?
[15:25] <JackWinter> no i have the problem with any 8.04 kernels i try.  before = a few weeks ago with the same kernels i'm trying now.   probably my fault, since i've tried to compile my  own kernel and failed on something related to the nvidia driver.  not sure if it has anything to do with it, but i suspect so...
[15:26] <JackWinter> smb_tp: could be but happens with .21 .16 etc....
[15:27] <smb_tp> Ok, in that case it isn't what I had in mind.
[15:27] <JackWinter> vbox people tell me that the vbox module should compile with settings from the linux-headers of my kernel, so i don't understand why it doesn't
[15:29] <smb_tp> Right IIRC those builds take the config from /lib/modules/$(uname -r)/build. So it should be right if nothing changed that contents
[15:30] <JackWinter> if it helps ls -l /usr/src: http://pastebin.com/d3e120806
[15:31] <smb_tp> looks sensible
[15:34] <JackWinter> and ls -l /lib/modules/2.6.24-16-generic: http://pastebin.com/d1683e7b6
[15:36] <JackWinter> could it not be that some global default has changed for my build enviroment, and that the Makefile doesn't take it into account so tries to build the module with stack checking while the kernel doesn't have it ?
[15:36] <smb_tp> what does "grep STACK /lib/modules/2.6.24-23-generic/build/.config" print for you
[15:37] <JackWinter> smb_tp: http://pastebin.com/d363cc5a7
[15:38] <smb_tp> ok, same here
[15:40] <JackWinter> and "grep STACK /lib/modules/2.6.24-16-generic/build/.config" shows the same
[15:44] <smb_tp> JackWinter, A compile for 1.5.6 vboxdrv works here. Maybe you want to pastebin a build log to compare
[15:48] <JackWinter> smb_tp: here is the build log: http://pastebin.com/d501a6128, but think that works fine, it's when it's trying to load it that there is a problem
[15:50] <JackWinter> my guess is that something went wrong when i tried to build a kernel.  i managed to build a couple of kernels based on the config of my existing kernel.  they failed to install from package though due to some conflict with the nvidia driver.  i had some problems until i manually removed the half installed kernels, but think i've cleaned the system out...
[15:51] <smb_tp> JackWinter, I had hoped the log would be a bit more verbose. To see which options are taken.
[15:51] <JackWinter> no it doesn't really show very much at all :(
[15:53] <JackWinter> my guess is that for some reasons the modules build with the wrong options and thus can't load.  i think i have the same problem with the nvida closed driver, the module builds but can't load.  prefer to trouble shoot with the vbox module though :)
[15:53] <smb_tp> As it saves a little time, yes. :)
[16:10] <JackWinter> smb_tp: mind you that i have no clue what i'm doing, but i copied the vbox module source from /var/lib/dkms/vboxdriver/2.1.4 to my home and tried to run a make from the build directory, this is the output: http://pastebin.com/m30123aa1
[16:11] <smb_tp> JackWinter, Well, good clueless thinking... ;-)
[16:15] <JackWinter> smb_tp: in any case the beginning of the output.  i have no clue as to what i'm expecting, but it doesn't look like all is in order ?
[16:16] <smb_tp> It looks strange, some things might be testing some environment. Give me a sec
[16:19] <JackWinter> here is ls -l /usr/local: http://pastebin.com/d7d6df7c2  include is indeed not a dierectory and the date is recent ?  and no worries about when, i am happy for all help i can get :)
[16:22] <JackWinter> on another install i have /usr/local/include is indeed a driectory, so this must be at least one thing borked with my system
[16:24] <smb_tp> It is an empty directory on my system
[16:25] <smb_tp> So at least this being a file is quite strange
[16:26] <JackWinter> looks to be emtpy on my 8.10 system too.  do you think i can just delete it and then recreate it with the right owner and access rights ?
[16:27] <smb_tp> May be look into it (or at least save it as evidence) to know what probably has written there
[16:28] <smb_tp> It might be worth a try to replace it by an empty dir again, but who knows what else got changed
[16:31] <JackWinter> hehe, looks like cpp code :)
[16:32] <JackWinter> must have been written when i tried to install a program from source...:(
[16:35] <smb_tp> JackWinter, Things like this could happen more likely if /usr/local/include was not there before. 
[16:37] <JackWinter> smb_tp: think it was always there...  in any case i removed it, recreated the dir and recompiled the kernel module.  it installed without a problem.  hopefully that was the extent of the problem, because i don't really feel like reinstalling the whole system...
[16:38] <smb_tp> Maybe it got its options wrong since the build system got confused. With the older vboxdrv module on my system here, I saw that -fno-stack-protector was used. This seems to be the case for you again.
[16:38] <JackWinter> am gonna remove the offending source, because that build didn't complete anyway and i don't really need it.  hopefully nvidia will also build again...  Many thanks for your help!
[16:39] <smb_tp> JackWinter, Np, I was just pointing a bit :)
[16:39] <JackWinter> :))
[16:45] <Laney> Quick instant-triage on this: https://s3.amazonaws.com/pikchurimages/pic_mba_l.jpg - kernel issue?
[16:45] <Laney> (just happened to my PC on Jaunty upgrade)
[16:45] <mjg59> Either your hard drive died or it's a kernel issue
[16:45] <mjg59> The latter is probably more likely
[16:46] <Laney> hdd dying is a coincidence too far
[16:46] <Laney> I will file a bug soon then
[16:52] <mdz> I noticed the following run-on message in dmesg:
[16:52] <mdz> [   20.835571] psmouse serio1: ID: 10 00 64<6>elantech.c: unexpected magic knock result 0x5a, 0x03, 0xc8.
[16:52] <mdz> I think there was supposed to be a newline in there somewhere
[17:18] <JackWinter> probably off topic but since i'm already here and you guys might know.  if i install the closed nvidia 180.29 drivers on my kubuntu 8.04 system, kernel 2.6.24, will dkms still work ?
[17:59] <apw> mdz, what did the next line look like?
[18:00] <apw> its possible they really are interlieved one from the interrupt handler
[18:00] <mdz> apw: 
[18:00] <mdz> [   20.835571] psmouse serio1: ID: 10 00 64<6>elantech.c: unexpected magic knock result 0x5a, 0x03, 0xc8.
[18:00] <mdz> [   21.197163] Adding 1023976k swap on /dev/sdb6.  Priority:-1 extents:1 across:1023976k
[18:00] <apw> mdz ta
[18:02] <apw> mdz indeed that looks like a missing newline
[18:03] <apw> mdz can you confirm you have an alps touchpad: cat /sys/devices/platform/i8042/serio1/protocol
[18:03] <mdz> apw: no I do not, this is a desktop
[18:03] <apw> hmmmm
[18:03] <mdz> mizar:[~] cat /sys/devices/platform/i8042/serio1/protocol
[18:03] <mdz> ImPS/2
[18:03] <apw> oddness
[18:05] <apw> ahh i see, this gets dropped out whether the alps driver attaches or not
[18:06] <apw> mdz i'll get that patched and push it upstream
[18:06] <mdz> apw: thanks
[18:33] <_ruben> hmm .. for some reason my module-assistant built kmod wont load .. earlier versions did work just fine .. now i get: scst: disagrees about version of symbol struct_module
[18:34] <_ruben> the headers i built against match the running system's kernel
[18:45] <maxb> "Latest kernel upload:" in the topic really really isn't
[18:50] <_ruben> bah .. this is annoying .. cant figure out what broke it
[19:08] <_ruben> hmm .. apparently using m-a on a 2.6.27-9-server system with 2.6.27-11-server headers installed, doesnt create proper kmods for 2.6.27-11-server systems
[19:08] <_ruben> (did use the -l option, and the package name looked ok)
[20:19] <maco> apw: hello?
[20:19] <apw> maco, hi
[20:21] <maco> apw: pgraner says you'd be the person to ask about figuring out how to add support for 2 hotkeys that are on my laptop but don't show up in asus_laptop.c
[20:23] <maco> apw: i disassembled the dsdt with iasl, but i don't really understand it
[20:23] <apw> i can have a look at the problem, is there a bug for it?
[20:25] <maco> bug 268429 and bug 327949 ...the web browser key and the video output switch key respectively.
[20:25] <ubot3> Malone bug 268429 in linux "asus-laptop module has incomplete support for hotkeys on Asus" [Undecided,New] https://launchpad.net/bugs/268429
[20:25] <ubot3> Malone bug 327949 in linux "Asus Z37E no keypress registered for video output switching key" [Low,New] https://launchpad.net/bugs/327949
[20:26] <maco> hrm i should probably attach the dsdt to the bugs
[20:26] <apw> yeah do that
[20:28] <maco> ok its attached to 32749
[20:28] <maco> er 327949
[20:29] <apw> maco, ok will have a look at the pair, and see what i can do, whats your normal around hours UTC?
[20:29] <maco> i looked about half way through it trying to make sense of it. i saw CPU and LED sections, and dtchen said the hotkeys won't be named, they'll likely be hex values....but that's all i got
[20:30] <maco> um...16 UTC to 7 UTC, i guess
[20:30] <apw> ok cool.  will see what i can figure out, likely talk to you your am
[20:31] <maco> ok. do you mind explaining it after you have a look? i'd like to learn
[20:34] <apw> sure, we can learn together!
[20:35] <maco> hahaha
[20:36] <maco> the most sense i can make of it is that it looks rather similar to verilog
[21:35] <maco> Keybuk: that email you just sent out about stop_machine_create(), you mentioned a 1/2 second delay.  is that 1/2 second total for 40 modules, or is that 1/2 second *per* module?
[21:36] <Keybuk> total for 40 modules
[21:36] <maco> ok
[21:37] <maco> was just wondering :)