Hi Christoph,
Christoph Pfister (2019-01-02):
> tl;dr: This is a regression introduced in Debian 9.6
> (linux/4.9.130-2); it is caused by [1] and fixed by [2]. Please fix :)
>
> I'm taking the liberty to hijack this bug because I'm experiencing the
> same issue [3] when powering off a usb3 hdd.
Processing commands for cont...@bugs.debian.org:
> reassign 914491 src:linux 4.18.20-1
Bug #914491 [linux-image-4.18.0-3-amd64] linux-image-4.18.0-3-amd64: Please
revert the STIBP patch from 4.18.20
Warning: Unknown package 'linux-image-4.18.0-3-amd64'
Bug reassigned from package
Hi Riku,
On Wed, Jan 2, 2019 at 6:28 PM wrote:
>
> From: Riku Voipio
>
> bison/flex is now needed always for building for kconfig. Some build
> dependencies depend on kernel configuration, enable them as needed:
>
> - libelf-dev when UNWINDER_ORC is set
> - libssl-dev for
On Wed, Jan 02, 2019 at 07:48:12PM +, Ben Hutchings wrote:
> On Wed, 2019-01-02 at 11:23 +0200, riku.voi...@linaro.org wrote:
> > From: Riku Voipio
> >
> > bison/flex is now needed always for building for kconfig. Some build
> > dependencies depend on kernel configuration, enable them as
On Wed, 2019-01-02 at 11:23 +0200, riku.voi...@linaro.org wrote:
> From: Riku Voipio
>
> bison/flex is now needed always for building for kconfig. Some build
> dependencies depend on kernel configuration, enable them as needed:
>
> - libelf-dev when UNWINDER_ORC is set
> - libssl-dev for
Control: tag -1 unreproducible
On Wed, 2019-01-02 at 05:41 +0300, pavel piankov wrote:
> > update-initramfs: Generating /boot/initrd.img-4.18.0-3-amd64
> > cryptsetup: ERROR: Couldn't resolve device rootfs
> > ^^^
>
> this is due
> rootfs / rootfs
Processing control commands:
> tag -1 unreproducible
Bug #916670 [src:linux] cryptsetup: ERROR: Couldn't resolve device rootfs
Added tag(s) unreproducible.
--
916670: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=916670
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: src:linux
Version: 4.20-1~exp1
Severity: normal
Hi,
I frequently send my desktop PC to sleep (suspend-to-ram) and wake it up
from remote when I need to access it. To do so, I use a script on a
banana pi which ends up calling etherwake 54:04:a6:82:21:00. This
has worked reliably up to
On 02/01/2019 17:48, Yves-Alexis Perez wrote:
> On Wed, 2019-01-02 at 17:37 +0100, Mikhail Morfikov wrote:
>> I have one question. Let's say I set the kernel options that are described
>> here[1]. Do I have to use DEB_BUILD_MAINT_OPTIONS or set any additional flags
>> in the debian/rules file to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-01-02 at 17:37 +0100, Mikhail Morfikov wrote:
> I have one question. Let's say I set the kernel options that are described
> here[1]. Do I have to use DEB_BUILD_MAINT_OPTIONS or set any additional flags
> in the debian/rules file to
Processing commands for cont...@bugs.debian.org:
> forwarded 918036 https://lore.kernel.org/lkml/20181106054212.GA31768@nautica/
Bug #918036 [src:linux] linux: uptime after reboot wrong (kvm-clock related?)
Set Bug forwarded-to-address to
Processing commands for cont...@bugs.debian.org:
> tags 918036 + upstream
Bug #918036 [src:linux] linux: uptime after reboot wrong (kvm-clock related?)
Added tag(s) upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
918036:
Hi Thorsten,
On Wed, Jan 02, 2019 at 04:08:23PM +, Thorsten Glaser wrote:
> Package: src:linux
> Version: 4.19.13-1
> Severity: normal
>
> I’ve just rebooted this VM and get:
>
> root@ci-busyapps:~ # uptime
> 16:06:57 up 58 days, 21:22, 1 user, load average: 0.62, 0.98, 0.46
>
> In
On 02/01/2019 15:28, Yves-Alexis Perez wrote> the kernel is not a standard ELF
binary, so you can't really run hardening-
> check on it and expect sound results.
>
> Yes, the kernel has some protection/hardening (see for example the work done
> by the Kernel Self Protection Project).
I have one
Your message dated Wed, 2 Jan 2019 17:24:12 +0100
with message-id <20190102162412.GA13145@eldamar.local>
and subject line Re: Bug#917206: linux-image-4.9.0-8-amd64: NULL ptr
dereference in xhci_hub_control [xhci_hcd] with USB Mass Storage (Kingston)
has caused the Debian Bug report #917206,
Source: linux
Source-Version: 4.9.144-1
Hi Christoph,
On Wed, Jan 02, 2019 at 12:29:02PM +0100, Christoph Pfister wrote:
> found 917206 4.9.130-2
> thanks
>
> tl;dr: This is a regression introduced in Debian 9.6
> (linux/4.9.130-2); it is caused by [1] and fixed by [2]. Please fix :)
>
> I'm
Package: src:linux
Version: 4.19.13-1
Severity: normal
I’ve just rebooted this VM and get:
root@ci-busyapps:~ # uptime
16:06:57 up 58 days, 21:22, 1 user, load average: 0.62, 0.98, 0.46
In syslog, I see this:
Jan 2 15:55:01 ci-busyapps CRON[3287]: (root) CMD (command -v debian-sa1 >
On Wed, 2019-01-02 at 03:08 +0100, Mikhail Morfikov wrote:
> Also how to get "not stripped" instead of "stripped" kernel?
It is available as the file `vmlinux` at the root of the source tree
after building, if you still have access to that.
There is also the `linux-image-$(uname -r)-dbg`
On 02/01/2019 16:08, Ian Campbell wrote:
> It is available as the file `vmlinux` at the root of the source tree
> after building, if you still have access to that.
Yes, it is.
> That said, Yves-Alexis is correct that despite being an ELF binary the
> kernel is in some ways a bit of a special
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, 2019-01-02 at 03:08 +0100, Mikhail Morfikov wrote:
> So does the kernel is protected or not? If yes, why hardening-check can't
> detect it?
> Also how to get "not stripped" instead of "stripped" kernel?
Hi,
the kernel is not a standard
Processing commands for cont...@bugs.debian.org:
> found 917206 4.9.130-2
Bug #917206 [src:linux] linux-image-4.9.0-8-amd64: NULL ptr dereference in
xhci_hub_control [xhci_hcd] with USB Mass Storage (Kingston)
Marked as found in versions linux/4.9.130-2.
> thanks
Stopping processing here.
found 917206 4.9.130-2
thanks
tl;dr: This is a regression introduced in Debian 9.6
(linux/4.9.130-2); it is caused by [1] and fixed by [2]. Please fix :)
I'm taking the liberty to hijack this bug because I'm experiencing the
same issue [3] when powering off a usb3 hdd. The oops is easy to
From: Riku Voipio
bison/flex is now needed always for building for kconfig. Some build
dependencies depend on kernel configuration, enable them as needed:
- libelf-dev when UNWINDER_ORC is set
- libssl-dev for SYSTEM_TRUSTED_KEYRING
Since the libssl-dev is needed for extract_cert binary,
Package: firmware-amd-graphics
Version: 20181218-1
Severity: important
Dear Maintainer,
Kaveri APUs, along with other SI and CIK parts, still uses the radeon driver
by default. They can also use the amdgpu driver by setting some options.
In linux 4.19 at least, the amdgpu driver doesn't load
- Forwarded message from Nye Liu -
Unfortunately, the bug is not fixed in 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1
(2018-12-22) x86_64 GNU/Linux
[297269.085315] WARNING: CPU: 1 PID: 451 at
drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1431 iwl_mvm_rx_tx_cmd+0x1e6/0x650
[iwlmvm]
Processing commands for cont...@bugs.debian.org:
> unarchive 886292
Bug #886292 {Done: Ben Hutchings } [src:linux] (no
subject)
Unarchived Bug 886292
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
886292: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886292
Processing commands for cont...@bugs.debian.org:
> reopen 886292
Bug #886292 {Done: Ben Hutchings } [src:linux] (no
subject)
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked
Processing commands for cont...@bugs.debian.org:
> reopen 887045
Bug #887045 {Done: Ben Hutchings } [src:linux] iwlwifi:
TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using hostapd
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and
28 matches
Mail list logo
