On Sat, 28 Mar 2020, Darac Marjal wrote: > Date: Sat, 28 Mar 2020 06:55:55 > From: Darac Marjal <mailingl...@darac.org.uk> > To: debian-user@lists.debian.org > Subject: Re: Question regarding an ACPI BIOS Error (bug) > > > On 28/03/2020 09:35, rba...@protonmail.ch wrote: > > Hi all, I've been redirected to this list while using reportbug. I > > would gladly accept some help regarding the determination of the > > Debian package responsible for those traces during boot: > > That would be the kernel itself. The number in square brackets at the > start of the line is the time (in seconds) since the kernel started. At > less than a second after startup, you're unlikely to have any user-space > components loaded yet and, besides, the kernel is what is responsible > for talking to ACPI. > > > > > > [??? 0.410073] ACPI: Added _OSI(Processor Device) > > [??? 0.410073] ACPI: Added _OSI(3.0 _SCP Extensions) > > [??? 0.410073] ACPI: Added _OSI(Processor Aggregator Device) > > [??? 0.410073] ACPI: Added _OSI(Linux-Dell-Video) > > [??? 0.410073] ACPI: Added _OSI(Linux-Lenovo-NV-HDMI-Audio) > > [??? 0.410073] ACPI: Added _OSI(Linux-HPI-Hybrid-Graphics) > > These aren't errors; these ones are just informative. > > > > [??? 0.457794] ACPI BIOS Error (bug): Failure creating named object > > [\_GPE._E4A], AE_ALREADY_EXISTS (20190816/dswload2-323) > > [??? 0.457802] ACPI Error: AE_ALREADY_EXISTS, During name > > lookup/catalog (20190816/psobject-220) > > [??? 0.457805] ACPI: Skipping parse of AML opcode: OpcodeName > > unavailable (0x0014) > > [??? 0.457807] ACPI BIOS Error (bug): Failure creating named object > > [\_GPE._E47], AE_ALREADY_EXISTS (20190816/dswload2-323) > > [??? 0.457811] ACPI Error: AE_ALREADY_EXISTS, During name > > lookup/catalog (20190816/psobject-220) > > [??? 0.457813] ACPI: Skipping parse of AML opcode: OpcodeName > > unavailable (0x0014) > > These are errors. However, as the message says, these are BIOS errors. > ACPI machine language (AML) is basically a program inside your BIOS > which the OS can use to list and control devices. Sometimes these AML > programs have bugs in them; sometimes they are a little too focussed on > what Windows likes (rather than what is proper). The generally accepted > solution to these is: if there is a noticeable issue with your computer > (some device doesn't work or behaves improperly), then consider a BIOS > upgrade. Otherwise, if there is no apparent effect, then you can ignore > these errors. > > > > [??? 0.458226] ACPI: 10 ACPI AML tables successfully acquired and loaded > > [??? 0.459880] ACPI: EC: EC started > > [??? 0.459881] ACPI: EC: interrupt blocked > > [??? 0.461706] ACPI: \: Used as first EC > > [??? 0.461708] ACPI: \: GPE=0x27, EC_CMD/EC_SC=0x66, EC_DATA=0x62 > > [??? 0.461708] ACPI: EC: Boot ECDT EC used to handle transactions > > > > Using apt and apt-file, I found numerous packages related to ACPI and > > there are also a few kernel modules dedicated to ACPI (in the last > > case I would say the package is linux-image-5.4.0-4-amd64 version > > 5.4.19-1 since I'm running a Debian testing) so I'm not sure of the > > package name I should use to report this issue. > > > > Regards, > > > > -- Rapha?l BAZAUD > > Does any Linux app exist to let systems know when bios updates become available for the bios running on those systems? > > >
--
