home.social

Search

320 results for “kernellogger”

  1. @kernellogger

    Open Source Summit.
    Europe.

    YouTube.
    Sched.

    So, how does anyone take this event, and with it, @linuxfoundation, serious?

    #OSSEU25

  2. patches to allow enabling (aka proper support) for x86, ARM64, and Risc-V were posted for review:

    lore.kernel.org/lkml/202409061

    "The printk bits required for PREEMPT_RT are sitting in linux-next. This was the last known roadblock for PREEMPT_RT. The RT queue has additionally the "atomic console" for the 8250 UART which is not yet in linux-next.[…]"

    See also these earlier other related toots:

    fosstodon.org/@kernellogger/11
    fosstodon.org/@kernellogger/11

  3. John posted v4 of the patch-set "threaded console printing as well as some other minor pieces" which "provides the remaining pieces of the rework." -- e.g. the last big missing piece for support through in the mainline . But note, "this series does *not* provide an nbcon console driver. That will come in a follow-up series."

    lore.kernel.org/all/2024082704

    This comes hot on the heels of the "write_atomic() printing" entering -next: fosstodon.org/@kernellogger/11

  4. John posted v4 of the patch-set "threaded console printing as well as some other minor pieces" which "provides the remaining pieces of the #printk rework." -- e.g. the last big missing piece for #Realtime support through #PREEMPT_RT in the mainline #Linux #Kernel. But note, "this series does *not* provide an nbcon console driver. That will come in a follow-up series."

    lore.kernel.org/all/2024082704

    This comes hot on the heels of the "write_atomic() printing" entering -next: fosstodon.org/@kernellogger/11

  5. John posted v4 of the patch-set "threaded console printing as well as some other minor pieces" which "provides the remaining pieces of the #printk rework." -- e.g. the last big missing piece for #Realtime support through #PREEMPT_RT in the mainline #Linux #Kernel. But note, "this series does *not* provide an nbcon console driver. That will come in a follow-up series."

    lore.kernel.org/all/2024082704

    This comes hot on the heels of the "write_atomic() printing" entering -next: fosstodon.org/@kernellogger/11

  6. John posted v4 of the patch-set "threaded console printing as well as some other minor pieces" which "provides the remaining pieces of the #printk rework." -- e.g. the last big missing piece for #Realtime support through #PREEMPT_RT in the mainline #Linux #Kernel. But note, "this series does *not* provide an nbcon console driver. That will come in a follow-up series."

    lore.kernel.org/all/2024082704

    This comes hot on the heels of the "write_atomic() printing" entering -next: fosstodon.org/@kernellogger/11

  7. John posted v4 of the patch-set "threaded console printing as well as some other minor pieces" which "provides the remaining pieces of the #printk rework." -- e.g. the last big missing piece for #Realtime support through #PREEMPT_RT in the mainline #Linux #Kernel. But note, "this series does *not* provide an nbcon console driver. That will come in a follow-up series."

    lore.kernel.org/all/2024082704

    This comes hot on the heels of the "write_atomic() printing" entering -next: fosstodon.org/@kernellogger/11

  8. After Linus statement ~10 days ago[1] it looked like extensible scheduler class aka the (SCX) patchset would be merged for 6.11. Now there are discussions to change a few things before merging it; as of now it's unclear if that will happen and/or delay things: lore.kernel.org/all/CAHk-=wg3R

    Side note: Tejun a few days ago posted v7 of the patchset and created a korg tree to coordinate development: lore.kernel.org/all/2024061821

    [1] fosstodon.org/@kernellogger/11

  9. @kernellogger and use "journalctl -k -b-1" to see the Kernel messages of the previous boot.

    Replace "-1" with any of the boot IDs provided by "journalctl --list-boots" (requires the journal to be configured as Storage=persistent in /etc/systemd/journald.conf)

    #systemd #journald

  10. @kernellogger good to see HPE's GXP SoC support getting merged. Progress towards an upstream #OpenBMC port!

  11. RE: hachyderm.io/@kernellogger/115

    Not even halfway through the article and this already hit hard:

    "[A]n overall increase in interest in Linux and free software will be driven by a combination of surveillance concerns, forced upgrades, unwanted AI features, and increasing hardware prices."

    This is a flag that almost 20 years back was already being raised in the free software communities. I remember similar discussions at FISL (Porto Alegre's old Free Software Forum) panels, which were met with dismissive statements from most of the tech professionals at the time.

    We already had trust issues after everything Microsoft did in the 90's and early 2000's, but it was clear that it was not a Microsoft-specific issue, that it would be pervasive and widespread in the computing ecosystem as soon as the adoption of IT was ubiquitous. The free software community called it, and thanks to the immense efforts from communities (and some corporate entities who saw value in it, obviously) we avoided being in a hopeless position.

    #foss #linux #FISL #GuessIShouldAlsoMentionGNUOtherwiseStallmanWillHauntMe

  12. RE: hachyderm.io/@kernellogger/115

    Not even halfway through the article and this already hit hard:

    "[A]n overall increase in interest in Linux and free software will be driven by a combination of surveillance concerns, forced upgrades, unwanted AI features, and increasing hardware prices."

    This is a flag that almost 20 years back was already being raised in the free software communities. I remember similar discussions at FISL (Porto Alegre's old Free Software Forum) panels, which were met with dismissive statements from most of the tech professionals at the time.

    We already had trust issues after everything Microsoft did in the 90's and early 2000's, but it was clear that it was not a Microsoft-specific issue, that it would be pervasive and widespread in the computing ecosystem as soon as the adoption of IT was ubiquitous. The free software community called it, and thanks to the immense efforts from communities (and some corporate entities who saw value in it, obviously) we avoided being in a hopeless position.

  13. RE: hachyderm.io/@kernellogger/115

    Not even halfway through the article and this already hit hard:

    "[A]n overall increase in interest in Linux and free software will be driven by a combination of surveillance concerns, forced upgrades, unwanted AI features, and increasing hardware prices."

    This is a flag that almost 20 years back was already being raised in the free software communities. I remember similar discussions at FISL (Porto Alegre's old Free Software Forum) panels, which were met with dismissive statements from most of the tech professionals at the time.

    We already had trust issues after everything Microsoft did in the 90's and early 2000's, but it was clear that it was not a Microsoft-specific issue, that it would be pervasive and widespread in the computing ecosystem as soon as the adoption of IT was ubiquitous. The free software community called it, and thanks to the immense efforts from communities (and some corporate entities who saw value in it, obviously) we avoided being in a hopeless position.

    #foss #linux #FISL #GuessIShouldAlsoMentionGNUOtherwiseStallmanWillHauntMe

  14. Ich würde gern eine neue Konsole nutzen, die besser GDB-tui unterstuzt. Wisst jemand ob #kmscon funktioniert mit GDB besser? Leider bietet Debian kmscon bisher nicht an. Ja, konnte ich selbst diese Anwendung verpacken . . .
    Vielen Dank, @kernellogger

    heise.de/news/Epochaler-Wandel

  15. Ich würde gern eine neue Konsole nutzen, die besser GDB-tui unterstuzt. Wisst jemand ob #kmscon funktioniert mit GDB besser? Leider bietet Debian kmscon bisher nicht an. Ja, konnte ich selbst diese Anwendung verpacken . . .
    Vielen Dank, @kernellogger

    heise.de/news/Epochaler-Wandel

  16. Ich würde gern eine neue Konsole nutzen, die besser GDB-tui unterstuzt. Wisst jemand ob #kmscon funktioniert mit GDB besser? Leider bietet Debian kmscon bisher nicht an. Ja, konnte ich selbst diese Anwendung verpacken . . .
    Vielen Dank, @kernellogger

    heise.de/news/Epochaler-Wandel

  17. Ich würde gern eine neue Konsole nutzen, die besser GDB-tui unterstuzt. Wisst jemand ob #kmscon funktioniert mit GDB besser? Leider bietet Debian kmscon bisher nicht an. Ja, konnte ich selbst diese Anwendung verpacken . . .
    Vielen Dank, @kernellogger

    heise.de/news/Epochaler-Wandel

  18. Ich würde gern eine neue Konsole nutzen, die besser GDB-tui unterstuzt. Wisst jemand ob #kmscon funktioniert mit GDB besser? Leider bietet Debian kmscon bisher nicht an. Ja, konnte ich selbst diese Anwendung verpacken . . .
    Vielen Dank, @kernellogger

    heise.de/news/Epochaler-Wandel

  19. #Linux 7.1-rc5 is out:

    lore.kernel.org/lkml/CAHk-=wjt

    ""To the surprise of absolutely nobody by now, rc5 is pretty big. Quite a bit bigger than rc5's have traditionally been.

    I'm not entirely happy about it - most of this is totally trivial stuff to random drivers, which obviously makes it all less scary, but at the same time I'm really not convinced the churn is worth it at rc5 time. These things are "fixes", sure, but at the same time a lot of them are simply so irrelevant that I think they'd be better off in a linux-next tree and get merged during the merge window.

    So I think I'll start being a bit more hardnosed about this kind of unnecessary churn this late in the game. We are supposed to look for *regressions*. Non-critical fixes to long-standing issues are simply not appropriate for this late in the release cycle.

    End result: this is too big, and this is the heads-up that I'll be pushing back on pointless pull requests with fixes that just aren't that important. And yes, several of these series were triggered by AI code review.

    Because fixes or not - and trivial or not - these kinds of large rc weeks are *not* conducive to long-term stability. Trivial fixes may be trivial, and have a pretty low chance of causing problems, but "low chance" is still not "zero chance".

    So people: start looking closer at your pull requests, and ask yourself: "Is this really a regression or serious enough that it shouldn't just go into the development pile?".

    Linus""

    #kernel #LinuxKernel

  20. got the 3c509 network driver back. It was removed earlier this cycle because it was assumed to be not used by anyone anymore. But that was wrong, so in light of the 's "no regression" rule was brought back:

    git.kernel.org/torvalds/c/28db

    From the commit msg: ""Contrary to the assumption stated with the original commit description this driver is in use and I'm going to maintain it for the foreseeable future.""

  21. #Fedora's #kernel maintainer now maintains a Git branch[1] with fixes for security issues in the #LinuxKernel that are not yet fixed in upstream #Linux because the fixes need more work:

    gitlab.com/cki-project/kernel-

    [1] based on mainline, but I guess it often will apply fine for the latest stable series, too

  22. PSA for those that encounter trouble[1] with Mediatek Bluetooth chips on mainline or some of the latest stable/longterm released yesterday:

    Sorry, this is a known issue. A fix for is is available:

    Bluetooth: btmtk: accept too short WMT FUNC_CTRL events
    lore.kernel.org/all/770d36b073

    Or revert 634a4408c0615c ("Bluetooth: btmtk: validate WMT event SKB length before struct access") [v7.1-rc3, v7.0.7 (70d37a8b9229e3), v6.18.30 (624fb79dadc1b6), v6.12.88 (c411cf1bfde951)]

    [1] error message is "Bluetooth: hci0: Failed to send wmt func ctrl (-22)"

  23. PSA for those that encounter trouble[1] with Mediatek Bluetooth chips on #Linux mainline or some of the latest stable/longterm #kernel released yesterday:

    Sorry, this is a known issue. A fix for is is available:

    Bluetooth: btmtk: accept too short WMT FUNC_CTRL events
    lore.kernel.org/all/770d36b073

    Or revert 634a4408c0615c ("Bluetooth: btmtk: validate WMT event SKB length before struct access") [v7.1-rc3, v7.0.7 (70d37a8b9229e3), v6.18.30 (624fb79dadc1b6), v6.12.88 (c411cf1bfde951)]

    [1] error message is "Bluetooth: hci0: Failed to send wmt func ctrl (-22)"

    #LinuxKernel