| === _ruben_ is now known as _ruben | ||
| === mhcerri_ is now known as mhcerri | ||
| === caribou_ is now known as caribou | ||
| caribou | morning, is there a 'trick' in the kernel build sequence to avoid changing the ABI during the build ? | 11:07 |
|---|---|---|
| caribou | I'm trying to only rebuilt the bzImage for a kernel bissect w/o rebuilding all the modules | 11:07 |
| caribou | Is forcing ABINUM in debian/rules sufficient ? | 11:09 |
| apw | caribou, what are you doing, adding a patch oro something ? | 11:11 |
| caribou | apw: just bissecting b/w two kernel version (4.7 <-> 4.8) to identify a problematic commit | 11:12 |
| apw | slam skipabi=true skipmodule=true (or is that skipmodules=true) on the build | 11:12 |
| caribou | apw: ok, will try that | 11:13 |
| robertfoss | apw: ^ | 11:59 |
| apw | robertfoss, ? (assume i have the memory of a goldfish on Temazepam | 12:00 |
| === ara is now known as Guest69211 | ||
| === RAOF_ is now known as RAOF | ||
| robertfoss | apw: you mentioned some kernel patches to get it compiling with gcc 6.2 | 13:35 |
| apw | oh that, i think i mentioned to work with pie, but i think we are using gcc5 for kernels | 13:35 |
| mamarley | I haven't tried the regular kernel in a while, but the mainline kernels are still compiled with GCC 6. I know the 4.4 kernel that was in Yakkety for a while was compiled with GCC 5 though. | 13:37 |
| robertfoss | mamarley, apw: I just ran a git clone from trunk on a 16.10 box, but it does not compile due to PIE/PIC issues | 13:38 |
| apw | https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/yakkety/commit/?id=d0fb5a1973caeb761d82f5a863b139e23e7f0671 | 13:41 |
| apw | robertfoss, might be that one, that is meant to be making its way upstream from the author | 13:41 |
| robertfoss | apw: thank you! I'll check it out | 13:44 |
| michael-vb | Hello all. Sorry for this hit-and-run reporting (have to move fast, but will stay logged in). | 16:02 |
| michael-vb | I reported a couple of days ago that recent daily builds did not work in a 32-bit VirtualBox VM - the first modeset happens after grub, but the first kernel message does not. | 16:02 |
| michael-vb | Wanted to say that 4.9.0rc1 still shows the same. | 16:02 |
| michael-vb | (Afk, but will read the scroll-back later.) | 16:03 |
| jacalope | Hello folks, I'm having a perpetual kernel panic after trying to return from suspend in my Samsung laptop using (K)ubuntu: http://paste.ubuntu.com/23339007/ | 16:38 |
| jacalope | 4.4.0-* kernels panic, but if I go back to 4.2.0-38-generic, I can get in. | 16:40 |
| jacalope | The link is where I booted with a liveusb and got dmesg and dump files from var/crash -> http://paste.ubuntu.com/23339007/ | 16:41 |
| jacalope | Using 16.04 | 16:42 |
| apw | jacalope, that looks like a very unhappy wireless driver or something like that | 16:44 |
| apw | jacalope, if you file an actual bug we can do a bisection on that maybe | 16:44 |
| apw | jsalisbury, ^ | 16:44 |
| jacalope | apw: thanks. I'm trying to work through filing it as a bug. First time doing that, so it's a bumbling process :) | 16:54 |
| jacalope | apw: Wait. Should I file with ubuntu/launchpad, or directly with linux/kernel? | 16:57 |
| apw | jacalope, i'd start with us, we cna tell you to do that if we cannot help | 16:59 |
| jsalisbury | apw, ack | 17:00 |
| jsalisbury | jacalope, from a terminal run this: ubuntu-bug linux | 17:01 |
| jacalope | jsalisbury: That returns a "the problem cannot be reported" dialog box from apport-- Of course I've booted using an older 4.2 kernel so its message makes sense to me. | 17:04 |
| jacalope | Since the 4.4 kernel panicked, do I need to file bug another way? | 17:05 |
| jsalisbury | jacalope, you can also go directly to the launchpad web interface: | 17:05 |
| jsalisbury | https://bugs.launchpad.net/ubuntu/+source/linux/+filebug | 17:05 |
| michael-vb | (Back briefly...) (18:02:37) michael-vb: Hello all. Sorry for this hit-and-run reporting (...) | 17:24 |
| michael-vb | Would be interested if anyone knows more about that. | 17:24 |
| apw | michael-vb, with yakkey ? | 17:27 |
| michael-vb | Right. | 17:33 |
| michael-vb | 4.8.0 worked fine, everything I tried since 4.8.0-999 October 11 hung, including 4.9.0rc1. | 17:33 |
| michael-vb | (Really have to run, will stay logged in...) | 17:34 |
| apw | i guess i want to know what you mean by 4.8.0, is that the official yakkety kernels ? | 17:35 |
| apw | the others you are mentioning are mainline builds, so often don't work with corner cases | 17:36 |
| jacalope | jsalisbury: apw: I submitted a bug report regarding the kernel panic: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1634214 | 17:55 |
| ubot5` | Ubuntu bug 1634214 in linux (Ubuntu) "kernel panic on resume from suspend with 4.4.0 kernels" [Undecided,New] | 17:55 |
| jacalope | I did my best, if any more info is needed I am more than obliged to provide. | 17:55 |
| rtg | jacalope, try 'sudo modprobe -r iwlwifi' before you close the lid. | 17:59 |
| jacalope | rtg: will be happy to, but I can't get back into any of my 4.4 kernels at the moment | 18:00 |
| jacalope | that removes the wireless driver before suspending, right? | 18:00 |
| rtg | jacalope, right, looks like your wifi adapter is an older model (i2400), though I am still looking | 18:01 |
| rtg | is this really WiMAX ? | 18:02 |
| jacalope | It has WiMAX, yes, but I've never used that particular functionality | 18:05 |
| rtg | jacalope, that appears to be what is crashing. Once you can get booted into a 4.4 kernel please attach the list of modules (lsmod) | 18:06 |
| jacalope | I've never really understood what the WiMAX is for, tbh. WiFi functionality has worked pretty well, except for the occasional > service network-manager restart trick | 18:06 |
| rtg | jacalope, WiMAX is a different kind of wireless, but it is sort of a failed technology | 18:07 |
| jacalope | Yeah, booting into 4.4 is the current issue. The system just hangs with the kernel panic. Is there a way around that? | 18:07 |
| rtg | jacalope, can you boot into an older kernel ? catch the boot process at the grub prompt ? | 18:08 |
| jacalope | Like, is there a locked file or something? Every 4.4 kernel I have is panicking, but the 4.2 lets me in. Seems odd to me since I've used 4.4 for months | 18:08 |
| jacalope | yeah, I can get into grub and 4.2 | 18:08 |
| rtg | a 4.2 kernel should be fine for getting the modules list. you can also blacklist the i2400 driver once you've got a filesystem mounted. | 18:09 |
| jacalope | rtg: ok, I've attached the lsmod output to the bug report. | 18:12 |
| rtg | jacalope, ok, read up on http://askubuntu.com/questions/110341/how-to-blacklist-kernel-modules and blacklist i2400m and i2400m_usb. | 18:14 |
| rtg | jacalope, this also has some good tricks, especially at the end using the kernel command line: https://wiki.archlinux.org/index.php/kernel_modules | 18:16 |
| jacalope | ok, scanning now. Just to confirm, add the "blacklist xxxx" lines at the end of blacklist.conf? (There seem to be files specializing in some way, e.g. blacklist-modem.conf etc.) | 18:18 |
| apw | jacalope, you could make a like blacklist-jackalope.conf as long as it ends .conf | 18:19 |
| jacalope | ok, so I added my blacklist-jacalope.conf file (thanks for that btw) and rebooted into 4.2. lsmod doesn't report i2400m or i2400m_usb. | 18:30 |
| jacalope | However, 4.4 still seems to panic, or at leas the visual results appears the same | 18:30 |
| hans109h | can someone help explain why every 15 minutes my kernel log says kernel: [ 1682.088022] sda: | 20:11 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!