(Please provide enough information to help the Debian
maintainers evaluate the report efficiently - e.g., by filling
in the sections below.)

My previous release is: <codename or version from which you are upgrading>
I am upgrading to: <codename or version of the release you are upgrading to>
Archive date: <Timestamp, available as project/trace/ftp-master.debian.org
     on your mirror or .disk/info on your CD/DVD set>
Upgrade date: <Date and time of the upgrade>
uname -a before upgrade: <The result of running uname -a on a shell prompt>
uname -a after upgrade: <The result of running uname -a on a shell prompt>
Method: <How did you upgrade?  Which program did you use?>

Contents of /etc/apt/sources.list:


- Were there any non-Debian packages installed before the upgrade?  If
  so, what were they?

- Was the system pre-update a 'pure' system only containing packages
  from the previous release? If not, which packages were not from that
  release?

- Did any packages fail to upgrade?

- Were there any problems with the system after upgrading?


Further Comments/Problems:


Please attach the output of "COLUMNS=200 dpkg -l" (or "env COLUMNS ...",
depending on your shell) from before and after the upgrade so that we
know what packages were installed on your system.



I have just recently updated my S/W. using latest linux kernel (think 51). Have the quiet mode removed from the linux line in
grub so that I can see system start. After updating the S/W I booted computer just before it entered gdm3 a message was
displayed on start up   r8169 0000:02:00.0: invalid VPD tag 0x80 (size 8817) at offset 31554.

I understand that an invalid VPD tag means that PCI config information is in error. This indicates a bug in the updated
kernel.  Got round problem by selecting boot using previous kernel (think 50). This is debian 12 - bookworm

Hi
  After the boot problems yesterday as explained I was able to boot up by selecting the old kernel on the grub menu login.
Have booted up today - using the latest kernel and it worked. No VPD invalid message.
Looks like an intermittent problem that somehow corrupts the VPD data.
I can send you a log file of the command lshw. plus log files that show the S/W installed - both normal and python. I wouldneed to refresh the log files by executing the script that generates them. This script does a whole load of things and takes time to run which isnt a problem 
Can also generate the output from any command line sequence you wish to request
Also my machine is old and I've tweeked a few things to improve performance. I have my own script that is included in the boot up which uses systemd to shut things down. I have had previous problems which I am still working on. My script was taking to long to run and wasnt finished when gdm3 was activated. Result was keyboard wasnt flushed by the time the login screen appeared and the computer wasnt talking to the keyboard. Had to reinstall my debian partition from backup because of this
This script has been split in 2 a short one that is called as part of the boot sequence and the full script which is ran once I have logged in.I can send you the scripts should you wish to see them plus the log files that they generate.

ThanksRobin