Processing commands for cont...@bugs.debian.org:
> reassign 1010128 src:broadcom-sta
Bug #1010128 [src:linux] linux-image-5.17.0-1-amd64: DKMS Module Rebuild for
Broadcom Wireless Chip BCM4352 Fails to Build
Bug reassigned from package 'src:linux' to 'src:broadcom-sta'.
No longer marked as found
Hi,
On Tue, Apr 26, 2022 at 03:50:21PM +0200, Vincent Blut wrote:
> Package: src:linux
> Followup-For: Bug #1010146
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA512
>
> Hi Tobias,
>
> The AMD P-State driver has been enabled in linux 5.17.3-1 available in
> testing/unstable. The kernel you
Package: src:linux
Version: 5.17.3-1
Severity: normal
While looking at the journalctl logs, I've noticed the following errors
that have been regularly occurring since March 1:
Apr 26 15:22:01 cventin kernel: sr 2:0:0:0: [sr0] tag#7 FAILED Result:
hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
A
Package: src:linux
Followup-For: Bug #1010146
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi Tobias,
The AMD P-State driver has been enabled in linux 5.17.3-1 available in
testing/unstable. The kernel you are using does not include it.
Cheers,
Vincent
-BEGIN PGP SIGNATURE-
iHUEARY
Processing commands for cont...@bugs.debian.org:
> reassign 1010146 src:linux 5.17.1-1~exp1
Bug #1010146 [linux-headers-5.17.0-trunk-amd64] modprobe: ERROR: could not
insert 'amd_pstate': No such device
Warning: Unknown package 'linux-headers-5.17.0-trunk-amd64'
Bug reassigned from package 'linux
I can confirm this on my machine (2014 Macbook Pro).
Note that DKMS for NVIDIA appears to work. I guess the problem is on
Broadcom side using deprecated APIs.
Regards
On Tue, Apr 26, 2022 at 10:40:45AM +0200, John Paul Adrian Glaubitz wrote:
> (changing configuration options here)
> $ debian/rules orig
> $ debian/rules debian/control
$ debian/rules source
> $ ~/kernel-team/utils/kconfigeditor2/process.py .
Bastian
--
Warp 7 -- It's a law we can live with.
Processing commands for cont...@bugs.debian.org:
> merge 947685 953114 986050 992131
Bug #947685 [src:linux] linux-image-5.4.0-1-amd64: NETDEV WATCHDOG: enp5s0f1
(r8169): transmit queue 0 timed out
Bug #953114 [src:linux] linux-image-5.4.0-4-amd64: r8169 temporarely looses
netwok connectivity
Th
Processing commands for cont...@bugs.debian.org:
> forwarded 953114
> https://lore.kernel.org/netdev/97b0eb30-7ae2-80e2-6961-f52a8bb26...@gmail.com/T/#m35578a2dc04faa7d552f68c2fbb35e31dbd2ea36
Bug #953114 [src:linux] linux-image-5.4.0-4-amd64: r8169 temporarely looses
netwok connectivity
Set Bug
Hello!
I'm trying to change the kernel configuration for the two ia64 flavors using
the following workflow:
$ fakeroot make -f debian/rules.gen setup_ia64_none_itanium
$ make -C debian/build/build_ia64_none_mckinley nconfig
(changing configuration options here)
$ debian/rules orig
$ debian/rule
Processing commands for cont...@bugs.debian.org:
> severity 953114 important
Bug #953114 [src:linux] linux-image-5.4.0-4-amd64: r8169 temporarely looses
netwok connectivity
Severity set to 'important' from 'normal'
> severity 986050 important
Bug #986050 [src:linux] linux-image-5.10.0-0.bpo.3-amd
Processing commands for cont...@bugs.debian.org:
> reopen 947685
Bug #947685 {Done: Vincas Dargis } [src:linux]
linux-image-5.4.0-1-amd64: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0
timed out
Bug reopened
Ignoring request to alter fixed versions of bug #947685 to the same values
previo
I've been trying to track down the cause of this myself. The problem I'm
having is that there is no documentation available for the Marvell 88E8001
Ethernet controller.
I've found that if I modify my I/O device to insert a 1 ms delay between
receiving the command frame and sending the response fr
13 matches
Mail list logo
