On Fri, 2018-01-05 at 17:08 +0100, Robert Senger wrote:
> Package: linux-source-4.9
> Version: 4.9.65-3+deb9u2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Dear Maintainer,
>
> compilation of Kernel sources 4.9.65-3+deb9u2 fails:
>
>
binary:acpi-modules-4.9.0-0.bpo.5-686-di is NEW.
binary:acpi-modules-4.9.0-0.bpo.5-686-pae-di is NEW.
binary:acpi-modules-4.9.0-0.bpo.5-amd64-di is NEW.
binary:affs-modules-4.9.0-0.bpo.5-4kc-malta-di is NEW.
binary:affs-modules-4.9.0-0.bpo.5-loongson-3-di is NEW.
linux_4.9.65-3+deb9u2~bpo8+1_amd64.changes uploaded successfully to localhost
along with the files:
linux_4.9.65-3+deb9u2~bpo8+1.dsc
linux_4.9.65-3+deb9u2~bpo8+1.debian.tar.xz
linux-headers-4.9.0-0.bpo.5-common_4.9.65-3+deb9u2~bpo8+1_all.deb
Package: linux-source-4.9
Version: 4.9.65-3+deb9u2
Severity: serious
Justification: fails to build from source (but built successfully in the past)
Dear Maintainer,
compilation of Kernel sources 4.9.65-3+deb9u2 fails:
[snip]
CC arch/x86/mm/gup.o
CC arch/x86/mm/setup_nx.o
CC
Package: firmware-atheros
Version: 20170823-1~bpo9+1
--- Please enter the report below this line. ---
The same problem here with firmware-atheros version 20170823-1~bpo9+1
and kernel 4.14.0-2-amd64.
It's a dell xps 13 8th gen, with a:
3a:00.0 Network controller: Qualcomm Atheros QCA6174
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Thu, 04 Jan 2018 12:12:40 +0100
Source: linux
Binary: linux-source-4.9 linux-support-4.9.0-5 linux-doc-4.9 linux-manual-4.9
linux-kbuild-4.9 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.9
libusbip-dev
Accepted:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Format: 1.8
Date: Fri, 05 Jan 2018 21:20:26 +0100
Source: linux
Binary: linux-source-4.14 linux-support-4.14.0-3 linux-doc-4.14
linux-kbuild-4.14 linux-cpupower libcpupower1 libcpupower-dev linux-perf-4.14
usbip hyperv-daemons lockdep
Hi,
I have the same error with a very old machine, a Pentium-M one, (and so
no SMP...) trying to compile the source from 4.9.65-3+deb9u2 with a
custom config.
The problem is: the "load_new_mm_cr3" function in arch/x86/mm/tlb.c is
compiled only when SMP config is defined, but is used in code
Hi Michael
> I just uploaded a new raspi3-firmware package which uses ttyS1 on Linux
> ≥ 4.14, which is the new device name for the UART on the pin header:
> https://anonscm.debian.org/cgit/pkg-raspi/raspi3-firmware.git/commit/?id=
> 4da2e6b1576f0a7513bffe7f95882693fdadd7ae
Many thanks - this
linux_4.14.12-1_allonly.changes uploaded successfully to localhost
along with the files:
linux_4.14.12-1.dsc
linux_4.14.12.orig.tar.xz
linux_4.14.12-1.debian.tar.xz
linux-doc-4.14_4.14.12-1_all.deb
linux-headers-4.14.0-3-common-rt_4.14.12-1_all.deb
Hi,
On Fri, Jan 05, 2018 at 09:19:30PM +0100, David Reviejo wrote:
> Hi,
>
> I have the same error with a very old machine, a Pentium-M one, (and so
> no SMP...) trying to compile the source from 4.9.65-3+deb9u2 with a
> custom config.
>
> The problem is: the "load_new_mm_cr3" function in
Source: linux
Version: 4.15~rc5-1~exp1
Severity: wishlist
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
Hello,
The 4.15 kernel comes with initial support for RISC-V.
Enabling support to build linux-libc-dev is one of the first steps to bootstrap
the architecture, so please
2018-01-06 01:09 Manuel A. Fernandez Montecelo:
Source: linux
Version: 4.15~rc5-1~exp1
Severity: wishlist
Tags: patch
User: debian-ri...@lists.debian.org
Usertags: riscv64
Hello,
The 4.15 kernel comes with initial support for RISC-V.
Enabling support to build linux-libc-dev is one of the
I have similar issue with 4.14.0-3-amd64
make[6]: Entering directory '/usr/src/linux-headers-4.14.0-3-amd64'
AR /tmp/tmp.VCaeAIqv24/built-in.o
make[9]: *** No rule to make target 'tools/objtool/objtool', needed by
'/tmp/tmp.VCaeAIqv24/test.o'. Stop.
Package: src:linux
Version: 4.14.7-1~bpo9+1
Severity: important
Dear Maintainer,
System updated from backports, rebooted, GDM fails, rolledback kernel version
to previous (running now) and all is OK.
-- Package-specific info:
** Kernel log: boot messages should be attached
** Model
Dear Ozgur,
On Fri, Jan 05, 2018 at 10:29:56AM +0300, Ozgur wrote:
>
> thanks for reply and I'm using the stable version (Debian stretch). I updated
> last night and I don't seen any new kernel patch yet.
>
Please use a user list for your support, this mailing list is for development
Ok, so x86_64_BUG_CPU_INSECURE will be optional in kernel config.
As I read Meltdown is primary a security risk on server farms where
multiple customers use same CPU.
If I have my own private server on own hardware, and thereby have full
control over software in use, then I might get a
05.01.2018, 10:56, "maximilian attems" :
> Dear Ozgur,
Hello Max,
> On Fri, Jan 05, 2018 at 10:29:56AM +0300, Ozgur wrote:
>> thanks for reply and I'm using the stable version (Debian stretch). I
>> updated last night and I don't seen any new kernel patch yet.
>
> Please use a
Control: found -1 4.14+88~bpo9+1
Same here, using a MacBookPro10,1. I cannot get the driver to work
when SDHC Samsung Evo 16GB is placed in card reader (bug is totally
reproducible). If I remove the card and place it in a USB reader
(USB-HUB reader) then everything is fine. I even tested using
Processing control commands:
> found -1 4.14+88~bpo9+1
Bug #830303 [src:linux] sdhci_pci: SD card reader gives error "mmc0: error -110
whilst initialising SD card"
The source 'linux' and version '4.14+88~bpo9+1' do not appear to match any
binary packages
Marked as found in versions
Processing commands for cont...@bugs.debian.org:
> reopen 886387
Bug #886387 {Done: Mehdi Dogguy } [src:linux]
linux-image-4.14.0-0.bpo.2-amd64: When booting with the latest 4.14+88~bpo9+1
kernel GDM fails to start
'reopen' may be inappropriate when a bug has been closed with
Also for reference:
$ sudo lspci -s 03:00.1 -vvx
03:00.1 SD Host controller: Broadcom Limited BCM57765/57785 SDXC/MMC
Card Reader (rev 10) (prog-if 01)
Subsystem: Broadcom Limited BCM57765/57785 SDXC/MMC Card Reader
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping-
Your message dated Fri, 05 Jan 2018 11:49:58 +
with message-id
and subject line Bug#886387: fixed in mstflint 4.8.0-2
has caused the Debian Bug report #886387,
regarding linux-image-4.14.0-0.bpo.2-amd64: When booting with the latest
4.14+88~bpo9+1 kernel
reopen 886387
found 886387 linux/4.14.7-1~bpo9+1
kthxbye
On Fri, Jan 05, 2018 at 11:51:07AM +, Debian Bug Tracking System
wrote:
> mstflint (4.8.0-2) unstable; urgency=medium
> .
>* Make the build reproducible (Closes: #886387). Thanks to Chris Lamb
> for
Processing commands for cont...@bugs.debian.org:
> # not a src:linux but a src:linux-latest version
> notfound 830303 4.14+88~bpo9+1
Bug #830303 [src:linux] sdhci_pci: SD card reader gives error "mmc0: error -110
whilst initialising SD card"
The source 'linux' and version '4.14+88~bpo9+1' do not
Processing commands for cont...@bugs.debian.org:
> found 830303 4.14.7-1~bpo9+1
Bug #830303 [src:linux] sdhci_pci: SD card reader gives error "mmc0: error -110
whilst initialising SD card"
Marked as found in versions linux/4.14.7-1~bpo9+1.
>
End of message, stopping processing here.
Please
Processing commands for cont...@bugs.debian.org:
> forwarded 882414 https://marc.info/?l=linux-scsi=151515500806381=2
Bug #882414 [src:linux] [src:linux] Oops: NULL pointer dereference - RIP:
isci_task_abort_task+0x30/0x3e0 [isci]
Set Bug forwarded-to-address to
binary:acpi-modules-4.14.0-3-686-di is NEW.
binary:acpi-modules-4.14.0-3-686-pae-di is NEW.
binary:acpi-modules-4.14.0-3-amd64-di is NEW.
binary:affs-modules-4.14.0-3-4kc-malta-di is NEW.
binary:affs-modules-4.14.0-3-5kc-malta-di is NEW.
binary:affs-modules-4.14.0-3-loongson-3-di is NEW.
Your message dated Fri, 05 Jan 2018 23:01:53 +
with message-id
and subject line Bug#885348: fixed in linux 4.14.12-1
has caused the Debian Bug report #885348,
regarding Latest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on
Intel 82579V
29 matches
Mail list logo