Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.kernel > #60513 > unrolled thread
| Started by | "LeJacq, Jean Pierre" <jeanpierre.lejacq@quoininc.com> |
|---|---|
| First post | 2018-03-20 18:30 +0100 |
| Last post | 2018-03-22 17:50 +0100 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.debian.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Bug#887304: linux-image-4.14.0-0.bpo.2-amd64: Error crypto/algapi.c:348 and a long system boot. "LeJacq, Jean Pierre" <jeanpierre.lejacq@quoininc.com> - 2018-03-20 18:30 +0100
Bug#887304: linux-image-4.14.0-0.bpo.2-amd64: Error crypto/algapi.c:348 and a long system boot. "LeJacq, Jean Pierre" <jeanpierre.lejacq@quoininc.com> - 2018-03-21 16:10 +0100
Bug#887304: linux-image-4.14.0-0.bpo.2-amd64: Error crypto/algapi.c:348 and a long system boot. Salvatore Bonaccorso <carnil@debian.org> - 2018-03-22 17:50 +0100
| From | "LeJacq, Jean Pierre" <jeanpierre.lejacq@quoininc.com> |
|---|---|
| Date | 2018-03-20 18:30 +0100 |
| Subject | Bug#887304: linux-image-4.14.0-0.bpo.2-amd64: Error crypto/algapi.c:348 and a long system boot. |
| Message-ID | <vvtfb-7dl-1@gated-at.bofh.it> |
Package: src:linux Followup-For: Bug #887304 Dear Maintainer, This issue exists in the latest version, linux-image-4.14.0-0.bpo.3-amd64, as well. -- System Information: Debian Release: 9.4 APT prefers stable APT policy: (1000, 'stable'), (500, 'stable-updates'), (2, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.14.0-0.bpo.3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- JP
[toc] | [next] | [standalone]
| From | "LeJacq, Jean Pierre" <jeanpierre.lejacq@quoininc.com> |
|---|---|
| Date | 2018-03-21 16:10 +0100 |
| Message-ID | <vvNxf-3E9-1@gated-at.bofh.it> |
| In reply to | #60513 |
I've tested the following two kernels from sid on a stretch system and they both DO NOT exhibit this bug: linux-image-4.15.0-1-amd64 linux-image-4.15.0-2-amd64 Instead of the kernel null pointer exception, I see the following in the boot log: kernel: usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 kernel: alg: ecdh: test failed on vector 3, err=-14 kernel: Bluetooth: Core ver 2.22 My bluetooth devices now work while they didn't with the 4.14.0 kernels. -- JP
[toc] | [prev] | [next] | [standalone]
| From | Salvatore Bonaccorso <carnil@debian.org> |
|---|---|
| Date | 2018-03-22 17:50 +0100 |
| Message-ID | <vwbzA-2L3-9@gated-at.bofh.it> |
| In reply to | #60517 |
Hi, On Wed, Mar 21, 2018 at 10:56:57AM -0400, LeJacq, Jean Pierre wrote: > I've tested the following two kernels from sid on a stretch system and they > both DO NOT exhibit this bug: > > linux-image-4.15.0-1-amd64 > linux-image-4.15.0-2-amd64 > > Instead of the kernel null pointer exception, I see the following in the boot > log: > > kernel: usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b > kernel: usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0 > kernel: alg: ecdh: test failed on vector 3, err=-14 > kernel: Bluetooth: Core ver 2.22 > > My bluetooth devices now work while they didn't with the 4.14.0 kernels. Looking at the traces you posted, this might be the same issue as #886556 and fixed with 4.14.17-1? Regards, Salvatore
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.kernel
csiph-web