lucnx | How does one debug the ubuntu kernel once it is compiled | 00:57 |
---|---|---|
alkisg | Hi, with an ubuntu 16.04.2 live CD I'm getting 100 times slower *write* speeds in both HDD and SDD, compared to an 12.04.3 live CD | 09:34 |
alkisg | dd if=/dev/zero of=/tmp/sda1/test bs=1M count=1000 => 600 MB/sec in 12.04.3, and 6 MB/sec in 16.04.2 | 09:34 |
alkisg | The read speed, measured e.g. with hdparm, is unaffected | 09:34 |
alkisg | Where would I report that issue, and which info would I need to include? | 09:35 |
apw | alkisg, file a bug against the kernel with the details of the kerenl versions in each | 09:54 |
apw | and paste the bug number here, so we can find | 09:54 |
alkisg | (just tried with 4.4 and it works fine) | 09:54 |
ogra | hmm, i have an arm board with no wlan on board that always loads the cfg80211 module unconditionally ... and obviously that resets the network all 360 minutes ... if i unload or blacklist the module this doesnt happen | 09:56 |
alkisg | Thank you apw, against ubuntu-kernel or upstream kernel? | 09:59 |
apw | i'd start against the ubuntu kernel (ubuntu-bug linux) | 10:00 |
alkisg | Thank you very much, will do so | 10:05 |
cking | alkisg, and I'll pick that bug up and look into it | 10:12 |
alkisg | cking: thank you very much; I will do it tomorrow because the school that has that issue has closed for today. It was on a asus prime b250 plus motherboard. | 10:12 |
cking | alkisg, ok, if you can provide info on the H/W and memory size and media you are using in the bug report then that would be helpful | 10:15 |
apw | cking, i am suspicious this is a media kernel issue only | 10:17 |
apw | if we were seeing it with updated machines we would have a lot of whining in our lives | 10:17 |
cking | apw, indeed | 10:17 |
=== JanC_ is now known as JanC | ||
user14241 | Hi! I just installed mainline kernel from drm-tip, arch amd64, version 994. The problem is that pulseaudio and alsa do not detect my soundcard, its snd-emu10k1. I can find the driver in/lib/modules/4.12.0-994-generic/kernel/sound/pci/emu10k1 however. Any ideas? | 20:06 |
user14241 | I am using Ubuntu 16.04 lts | 20:06 |
user14241 | "aplay -l" only returns hda-intel, but lspci sees the card fine. It also works with regular HWE kernel (4.10), but I need newer kernel due to radeon-related crashes. | 20:08 |
apw | user14241, the only advice i can think of it to try modprobe'ing the driver manually and see what it says about your card | 20:27 |
user14241 | apw, I have, but no output in dmesg|tail. However, I found this manually grepping the kern.log: | 20:28 |
user14241 | "[ 35.659024] snd_emu10k1: probe of 0000:06:00.0 failed with error -14" | 20:28 |
user14241 | thanks.. | 20:29 |
apw | -rc tips like that often have horrible bugs, and they get resolved "later" | 20:29 |
user14241 | apw, well the three "drm-next" from the tail do not even boot. | 20:30 |
apw | yep, doen't supprise me they are built so they can be tested to find that kind of boot issue | 20:31 |
user14241 | 2017-06-07 hangs, 2017-05-31 and 2017-05-30 draw a white line on black screen right after boot, and hang | 20:31 |
user14241 | apw, can you suggest a drm-next that does would boot? :) | 20:32 |
user14241 | "does would"->would | 20:32 |
apw | user14241, heh, no not something i keep tabs on, we make those for the graphics dudes | 20:32 |
user14241 | apw, thanks. Is there a difference between "4.12-rc" and "drm-next" kernels, or are they same? | 20:33 |
user14241 | I am just looking for newer radeon code | 20:34 |
apw | user14241, yes the drm-next have whatever the drm people are intending to merge in the next merge window | 20:34 |
user14241 | the 4.10 and 4.8 are very unstable on R9 280 | 20:34 |
apw | so right now 4.13 planned stuff | 20:34 |
user14241 | apw, ah, so "drm-next" with 4.12, is newer than "v4.12-rc"* ? | 20:35 |
apw | well you never know what they are based on it, could be a random 4.11, but normally yes | 20:35 |
apw | it is the drm maintainers testing tree, it has whatever they want | 20:36 |
user14241 | I think I should have more lucky with 4.12-rc (non-drm-next). | 20:36 |
user14241 | yes, it definitely has a broken audio driver (but hdmi on tahiti gpu detected fine) in "tip" and "drm-next" does not even start. | 20:37 |
user14241 | apw, anyways, thank you very much. Looks like I got myself a borked kernel. :) | 20:37 |
user14241 | apw, thank you, all the best to you! | 20:39 |
tomreyn | would anyone know how to trigger a canonical livepatch run after it failed to apply? | 23:03 |
tomreyn | this software is pretty good in not disclosing how it works :-/ | 23:03 |
cjwatson | tomreyn: "sudo pkill -HUP -f canonical-livepatchd" should do it | 23:26 |
cjwatson | tomreyn: (disclaimer: I've never worked on the livepatch client, and this is just from looking through the slightly old copy of the code that I have access to) | 23:27 |
cjwatson | tomreyn: but the copy I can see has a SIGHUP handler that does just a check-and-apply-if-possible and nothing else | 23:28 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!