[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1041197: marked as done ("ata2.00: supports DRM functions and may not be fully accessible" and ACPI commands filtered out or rejected)

Your message dated Tue, 01 Aug 2023 01:09:37 +0200
with message-id <6531216.tM3a2QDmDi@bagend>
and subject line Re: Debian's BTS is not for regular user questions
has caused the Debian Bug report #1041197,
regarding "ata2.00: supports DRM functions and may not be fully accessible" and ACPI commands filtered out or rejected
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
1041197: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1041197
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-6.1.0-10-amd64
Version: 6.1.37-1
In the depths of my journal I discover the following two warnings (“ata2.00: supports DRM functions and may not be fully accessible” are marked orange): 

$ grep -i ata2 -C 1 /tmp/j.log
Jul 15 15:21:43 AnonymizedMachineName kernel: ata1: SATA max UDMA/133 abar m2048@0xf7f36000 port 0xf7f36100 irq 28 Jul 15 15:21:43 AnonymizedMachineName kernel: ata2: SATA max UDMA/133 abar m2048@0xf7f36000 port 0xf7f36180 irq 28 Jul 15 15:21:43 AnonymizedMachineName kernel: ata3: SATA max UDMA/133 abar m2048@0xf7f36000 port 0xf7f36200 irq 28 
--
Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: New USB device found, idVendor=0a5c, idProduct=5801, bcdDevice= 1.01 Jul 15 15:21:43 AnonymizedMachineName kernel: ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out 
Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: Product: 5880
Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: Manufacturer: Broadcom Corp Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x51 Err=0x04) Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: SerialNumber: 0123456789ABCD Jul 15 15:21:43 AnonymizedMachineName kernel: usb 3-1.8: config 0 descriptor?? Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: supports DRM functions and may not be fully accessible Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ATA-11: Samsung SSD 860 PRO 1TB, RVM01B6Q, max UDMA/133 Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: 2000409264 sectors, multi 1: LBA48 NCQ (depth 32), AA Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: Features: Trust Dev-Sleep NCQ-sndrcv Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd f5/00:00:00:00:00:00(SECURITY FREEZE LOCK) filtered out Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd b1/c1:00:00:00:00:00(DEVICE CONFIGURATION OVERLAY) filtered out Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x51 Err=0x04) Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: supports DRM functions and may not be fully accessible Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: configured for UDMA/133 Jul 15 15:21:43 AnonymizedMachineName kernel: scsi 1:0:0:0: Direct-Access ATA Samsung SSD 860 1B6Q PQ: 0 ANSI: 5 
--
Jul 15 15:21:43 AnonymizedMachineName kernel: ata3.00: Enabling discard_zeroes_data Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: Enabling discard_zeroes_data Jul 15 15:21:43 AnonymizedMachineName kernel: sd 2:0:0:0: [sdb] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB) 
--
Jul 15 15:21:43 AnonymizedMachineName kernel: sd 1:0:0:0: [sdc] Preferred minimum I/O size 512 bytes Jul 15 15:21:43 AnonymizedMachineName kernel: ata2.00: Enabling discard_zeroes_data 
Jul 15 15:21:43 AnonymizedMachineName kernel:  sdc: sdc1 sdc2
In plain English, what do the two warnings “ata2.00: supports DRM functions and may not be fully accessible” tell us? What does DRM stand for in this context? There are also rejected ACPI commands and ACPI-cmd errors marked as non-errors (i.e., in usual, maintext gray-white), e.g., “ACPI cmd 00/00:00:00:00:00:a0(NOP) rejected by device (Stat=0x51 Err=0x04)”. Is there a configuration issue; do we have to worry about these warnings and errors? The machine is a Dell Mobile Precision M6700; ata2 most likely refers to an internal 2.5-inch SATA SSD. The machine has problems later during boot, so it's important for us to know the extent and the implications of the warnings and errors here. 

Gratefully,
AlMa

--- End Message ---
--- Begin Message --- 
On Sat, 15 Jul 2023 03:13:51 +0200 AlMa <AlMa0@ro.ru> wrote:
> In the journal I see two yellow lines (which, probably, constitute 
> warnings) directly following one another:
> … 
> Later in the journal we see a white line
> … 
> 
> As the machine (Dell Mobile Precision M6700) experiences various 
> high-level issues later in the boot process, I'm unsure about the 
> contribution of the two issues in the log.  Which software or hardware 
> problems do these warnings inform us about?  Any fix or remedy?

You filed various bugs talking about yellow and white lines of which you 
suspect that yellow may be a warning (which you should be able to find out by 
yourself if that's the case).

The Debian BTS is not meant to ask questions like "what could this message 
tell us?". Put it in a search engine or use one of the MANY user support 
options for that. Computers/Linux put various debug/informational/warning msgs 
in various logs, which _could_ be helpful in case there's an actual ERROR.

But the only *potential* error I see here is "various high-level issues", 
which is so vague so that's completely useless and inactionable.

So I'm going to close this and similar vague bug reports, which aren't 
actually bug reports, but just questions.
And all those ACPI errors? Contact the machine vendor as they're the only ones 
who could resolve such issue. Linux is only reporting that there are issues.

"If we believe Jean Delvare" ... and Jean Delvare response in that bug report:
"This is not a support forum, sorry. If you need help, use support forums and 
mailing lists." ...

From 'bug' #1041191: "Will the fingerprint sensor not work?"
I _assume_ you have the device/machine, so why don't you try it out?
*IF* it turns out it doesn't work then you first use a search engine to see if 
you can make it work yourself by trying out various hints you'll undoubtedly 
find and if that doesn't make it work, *THEN* you have something to file a bug 
about.

You filed *8* different 'bugs' which (almost?) all are about a Dell Mobile 
Precision M6700 ... and not once did you say what actual problem you 
experienced?!?

If you file a bug, you're (basically) asking (several) people to read about a 
problem you're having and then subsequently (potentially) spend time to fix 
that/those problem(s).
Please be more considerate with other people's time and only file bugs for 
*actual* problems and then provide enough information/context so that they
can actually (potentially) act upon it and help you fix that problem.

I initially intended to respond to some actual problems you (also) reported, 
but I've already spend way too much time on these non-issues, so I'm done.

Attachment: signature.asc
Description: This is a digitally signed message part.


--- End Message ---
Reply to: