You are not logged in.
Pages: 1
Hello,
after the update today i get additional output during boot.
Unfortunately i can't copy/paste it here.
It's right after the usual "decrompessing kernel" messages.
Something with
run_size: (some hex number)
init_size: (some hex number)
there are a total of about 5 or 6 new lines, all looking similar.
They pass fairly quickly, so i don't manage to read them properly.
Can someone identify this messages? Are they normal? If not i may try and post a picture :-)
Thx,
Lazarus
Offline
Did you look in the dmesg or journactl output?
Offline
@Lazarus555
You are not the only one receiving this!
This is correct early message:
input_data: 0x0000000001a1a3b4
input_len: 0x0000000000412c06
output: 0x0000000001000000
output_len: 0x0000000000e1b9a8
run_size: 0x00000000000f65000I think it is connected with r8169 module error bellow.
...
[44475.959654] r8169 0000:08:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
[44476.966370] r8169 0000:08:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
[44476.970811] r8169 0000:08:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
[44476.987381] r8169 0000:08:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
[44477.961551] r8169 0000:08:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
[44478.961174] r8169 0000:08:00.0 eth0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
...This is probably kernel regression. Can you check dmesg and afterwards lspci to find if you have hw which is using r8169 kernel module?
BTW: i have laptop
Offline
Seeing the same message, also using r8169. So far, the message seems to cause no bugs, it only appears at boot, at least for me.
Offline
I do not have the r8169 module loaded, but I am seeing that message.
This is on an installation using btrfs (that was an ext4 partition). My other, main, installation still uses ext4 and does not report those extra lines.
Last edited by IMBJR (2016-01-08 16:51:21)
Offline
This has nothing to do with any module, it's now part of the kernel & is perfectly fine. Just some debug info seen because CONFIG_X86_VERBOSE_BOOTUP is enabled; See https://github.com/torvalds/linux/commi … 256fdc0fc4
Offline
This has nothing to do with any module, it's now part of the kernel & is perfectly fine. Just some debug info seen because CONFIG_X86_VERBOSE_BOOTUP is enabled; See https://github.com/torvalds/linux/commi … 256fdc0fc4
Any ideas why this is not seen by everyone then?
Offline
No. Is your "main installation" up-to-date (kernel 4.3.3)? Same bootloader config as your other one? (did/do you see the "early console in decompress_kernel" line?) Maybe some bootloader might be configured to hide the console/such messages, or the boot process is fast enough that they're barely visible...
Offline
Hello again,
thx for all clarification.
Just for completion: I do not use the r8169 module.
Good to know where it comes from.
After 2,5 years of using Arch i have never seen a similar change during the boot-up and it tripped me up. :-)
Have a good one.
Lazarus
Offline
Pages: 1