Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #79618 > unrolled thread

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

Started byAlMa <AlMa0@ro.ru>
First post2023-07-15 17:20 +0200
Last post2023-08-01 01:20 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#1041197: "ata2.00: supports DRM functions and may not be fully accessible" and ACPI commands filtered out or rejected AlMa <AlMa0@ro.ru> - 2023-07-15 17:20 +0200
    Bug#1041197: marked as done ("ata2.00: supports DRM functions and  may not be fully accessible" and ACPI commands filtered out or rejected) "Debian Bug Tracking System" <owner@bugs.debian.org> - 2023-08-01 01:20 +0200

#79618 — Bug#1041197: "ata2.00: supports DRM functions and may not be fully accessible" and ACPI commands filtered out or rejected

FromAlMa <AlMa0@ro.ru>
Date2023-07-15 17:20 +0200
SubjectBug#1041197: "ata2.00: supports DRM functions and may not be fully accessible" and ACPI commands filtered out or rejected
Message-ID<GRPdT-qM5-3@gated-at.bofh.it>
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

[toc] | [next] | [standalone]


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

From"Debian Bug Tracking System" <owner@bugs.debian.org>
Date2023-08-01 01:20 +0200
SubjectBug#1041197: marked as done ("ata2.00: supports DRM functions and may not be fully accessible" and ACPI commands filtered out or rejected)
Message-ID<GXKlb-49LV-5@gated-at.bofh.it>
In reply to#79618

[Multipart message — attachments visible in raw view] — view raw

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

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web