Bug#1011026: linux-headers-amd64: cannot install/upgrade to 5.17.6 on amd64

2022-05-15 Thread Tomas Janousek
Package: linux-headers-amd64
Version: 5.17.6-1
Severity: normal

linux-headers-amd64=5.17.6-1 depends on linux-headers-5.17.0-2-amd64=5.17.6-1, 
but there's only 5.17.6-1+b1 in the amd64 archive as of today.

This results in:

# apt install linux-headers-5.17.0-2-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
   linux-headers-amd64 (5.17.6-1)
The following packages will be upgraded:
   linux-headers-5.17.0-2-amd64 (5.17.6-1 => 5.17.6-1+b1)
1 upgraded, 0 newly installed, 1 to remove and 84 not upgraded.
Need to get 963 kB of archives.
After this operation, 12.3 kB disk space will be freed.

On another Debian instance, where linux-headers-amd64 is still at 
5.17.3-1, it looks like this:

# apt install linux-image-amd64 linux-headers-amd64
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 linux-headers-amd64 : Depends: linux-headers-5.17.0-2-amd64 (= 5.17.6-1) 
but it is not going to be installed
E: Unable to correct problems, you have held broken packages.

# apt policy linux-headers-5.17.0-2-amd64
linux-headers-5.17.0-2-amd64:
  Installed: (none)
  Candidate: 5.17.6-1+b1
  Version table:
 5.17.6-1+b1 990
500 https://deb.debian.org/debian unstable/main amd64 Packages

-- System Information:
Debian Release: bookworm/sid
  APT prefers stable-security
  APT policy: (990, 'stable-security'), (990, 'testing'), (500, 
'unstable-debug'), (500, 'testing-debug'), (500, 'stable-debug'), (500, 
'unstable'), (500, 'stable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.17.0-1-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_CPU_OUT_OF_SPEC, TAINT_USER, TAINT_WARN
Locale: LANG=cs_CZ.UTF-8, LC_CTYPE=cs_CZ.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages linux-headers-amd64 depends on:
ii  linux-headers-5.17.0-2-amd64  5.17.6-1

linux-headers-amd64 recommends no packages.

linux-headers-amd64 suggests no packages.

-- no debconf information

-- 
Tomáš "liskin" ("Pivník") Janoušek, https://lisk.in/


Bug#1011020: Linux fail to traverse struct boot_params on real mode.

2022-05-15 Thread Jonathan Nieder
Hi,

Corcodel Marian wrote:

> On struct boot_params not have only type 16 or 8 bits and become unusable on
> real mode.

Forgive my ignorance: I'm not understanding what you mean to say here.
Do you mean that Linux fails to build, or that it's failing to boot, or
that some operation you run after booting is failing?  What steps should
I use to reproduce this, what is the expected result, and what happens
instead?

Thanks,
Jonathan



Bug#1011020: linux-source-4.19: Linux fail to traverse struct boot_params on real mode.

2022-05-15 Thread Corcodel Marian
Package: linux-source-4.19
Severity: normal

On struct boot_params not have only type 16 or 8 bits and become unusable on
real mode.



-- System Information:
Debian Release: 10.12
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable-proposed-updates'), 
(500, 'oldoldstable'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.7.8+ (SMP w/2 CPU cores)
Kernel taint flags: TAINT_DIE, TAINT_WARN
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US:en 
(charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages linux-source-4.19 depends on:
ii  binutils  2.31.1-16
ii  xz-utils  5.2.4-1+deb10u1

Versions of packages linux-source-4.19 recommends:
ii  bc1.07.1-2+b1
ii  bison 2:3.3.2.dfsg-1
ii  flex  2.6.4-6.2
ii  gcc   4:8.3.0-1
ii  libc6-dev [libc-dev]  2.28-10+deb10u1
pn  linux-config-4.19 
ii  make  4.2.1-1.2

Versions of packages linux-source-4.19 suggests:
ii  libncurses-dev [ncurses-dev]  6.1+20181013-2+deb10u2
pn  libqt4-dev
ii  pkg-config0.29-6



Bug#1010365: probably related - seeed studio dual gigabit CM4 does not reboot + does not boot once upgraded.

2022-05-15 Thread Eugen Stan

Hello,

I have a seeed studio CM4 dual gigabit board that I have installed Raspi 
Debian on it 
https://raspi.debian.net/tested/20220121_raspi_4_bookworm.img.xz .



System works fine but does not reboot.
If I reboot it hangs instead and I push the small reset button to 
restart it (or unplug + plug).


I configured wireless AP and ran apt update + apt upgrade on the system.
It upgraded kernel and raspberry-firmware and then it did not boot again.

I had to start in boot mode again and reflash the debian image on the 
system to make it work.


Working system runs linux 5.15.0-2-arm64 - 5.15.5.-2 .
Raspi firmware is 1.20210805+ds-1


For some background, I flashed OpenWrt 22.xx-rc1 before Debian and 
reboot worked. 
https://github.com/sergey-brutsky/openwrt-seeed-carrier-board/issues/1 .


--
Eugen Stan

+40770 941 271  / https://www.netdava.combegin:vcard
fn:Eugen Stan
n:Stan;Eugen
email;internet:eugen.s...@netdava.com
tel;cell:+40720898747
x-mozilla-html:FALSE
url:https://www.netdava.com
version:2.1
end:vcard