=== tsimpson_ is now known as tsimpson === Daviey_ is now known as Daviey === yokel_ is now known as yokel === gerald is now known as Guest93072 === mwhudson is now known as zz_mwhudson === zequence_ is now known as zequence === fmasi is now known as Guest59397 [11:17] hi, question on boot: is the /boot/abi file necessary for successful booting ? I've been reading about abi but can't figure this out === lool- is now known as lool [11:39] hvn2: No, it's just there as a reference. [11:46] inifinity: ok, thank you. I'm trying to figure out why my custom kernel 3.5.7 (for 12.04) won't boot and keeps hanging at "Uncompressing Linux... done, booting the kernel.". So far I found no solution. [12:28] hvn2, that is very early, try adding debug and loglevel=9 to the boot [12:28] hvn2, also does the mainline 3.5.7 [12:28] boot for your machine [12:29] hvn2, as infinity says the /boot/abi is not used at runtime at all [12:30] * apw hates on debconf questions which always appear 10s after you leave an upgrade to finish by itself [12:31] apw: where should I add debug and loglevel ? [12:32] apw: e.g. in the kernel or in boot.scr ? [12:34] on the kernel command line, however you are setting that [12:34] as it is a boot.scr i assume it is some kind of arm board [12:35] apw: yes it is an armv7 board [12:37] apw: I assume then I should put loglevel=9 in boot.scr ? [12:39] and debug in whever you set the kernel command line [12:39] that is likely there, but i don't have the same boards, and they don't all work the saem [12:41] apw: do you have a suggestion for how to put debug ? [12:42] debug is the word you want, like loglevel it instructs the kernel to be noisier [12:43] so, just put the word debug in boot.scr ? [12:49] hvn2, put it with loglevel=9 in the kernel command line specification hwever that is done in your boot loader [12:50] apw: ok [13:12] apw: I put loglevel and debug in boot.scr and rebooted...it hangs again, but how do I check on the loglevel and debug now ? === gerald is now known as Guest4455 === Guest59397 is now known as fmasi === sforshee` is now known as sforshee [13:42] apw: the syslog is only started after starting the kernel, not after boot ? === Trevinho_ is now known as Trevinho [14:12] smb: hello. i see the neutron kernel crash bug has some more comments. === arges_ is now known as arges [14:12] smb: I wonder if it makes sense for us to provide a machine one of their developers can access so they can setup a reproducer and then we can crash it at will and perform experiements? [14:12] arges, Yeah, not more to work on though , yet [14:12] and also snapshot it [14:13] arges, Feel free to offer that to them [14:17] smb: or would it be too much to ask them to reproduce in a VM, then tar it up so we can download the disk? [14:19] arges, Well that might be simplifying the setup. If they can get a kexec crash they can share with us that sounded good enough. And meanwhile try to find a simpler reproducer [14:20] If ones is found we learn more about the trigger, too [14:20] yup [14:20] If not, maybe still we are lucky and get a dump [14:20] smb: so stilll 1) get a crash dump 2) get a reproducer? [14:21] That was my thinking when proposing it. Or rather 1) get the crashdump and while waiting 2) try to get a reporducer. Not sure I was clear with that :) [14:23] arges, Getting a setup locally may or may not be sucessful. Ok, it could be but also we could find out that it needs a certain environment in which the host is to trigger [14:24] Ok, we could realize that when trying to find a reproducer, too [14:24] smb: i'll send an email with this info you can reply with clarifications [14:27] arges, ok, wfm [19:23] b 3 [20:39] "nunca trates de abarcar el mundo con las dos manos, al final de tus dias, te quedaras sin manos y sin mundo" *bienvenidos: http://castroruben.com *temo_a_un_ser_sin_rival* [21:11] so we have a regression with 3.13 on the wandboard... my box won't boot with 3.13.0-11. Last running kernel was -6, will try to figure out exactly which upload broke it now. [21:31] 3.13.0-10.30 to 3.13.0-11.31 is where the regression happened [21:32] hmm, that doesn't make much sense looking at what changed in 3.13.0-11.31... [21:34] yeah, that actually doesn't make any sense seeing that the armhf configuration didn't change at all in that upload (just bits being moved to common) [21:35] I guess we'll see if 3.13.0-12.32 magically works (in which case I'll blame cosmic rays), if not, then maybe something toolchainy changed?