[1] MLD-5.x / General / Meldungen in /var/log/messages -> Problem?
 

Offline LincolnTC

  • Newbie
  • *
  • Posts: 32
    • View Profile
Meldungen in /var/log/messages -> Problem?
« on: December 22, 2021, 16:15:28 »
Hallo,

nach dem ich MLD (5.5 Testing) gestern installiert und "in Betrieb" genommen hatte, habe ich jetzt mal in mein Syslog geschaut und folgende wiederkehrende Meldungen gefunden:
Code: [Select]
Dec 22 15:25:04 MLD user.warn kernel: [49505.415017] clear: done = 0, 0 fifo bytes
Dec 22 15:25:04 MLD user.warn kernel: [49505.464047] clear: done = 0, 0 fifo bytes
Dec 22 15:25:13 MLD user.warn kernel: [49514.612915] clear: done = 0, 0 fifo bytes
Dec 22 15:25:13 MLD user.warn kernel: [49514.720877] clear: done = 0, 0 fifo bytes
Dec 22 15:25:16 MLD user.warn kernel: [49517.297046] clear: done = 0, 0 fifo bytes
Dec 22 15:25:29 MLD user.info kernel: [49529.982339] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:25:29 MLD user.warn kernel: [49529.982361] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:25:29 MLD user.warn kernel: [49529.982367] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:25:29 MLD user.warn kernel: [49529.982374] pcieport 0000:00:1c.3:    [12] Timeout

Code: [Select]
Dec 22 15:26:40 MLD user.err vdr: video: get hwaccel context, not supported
Dec 22 15:26:40 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:26:46 MLD user.err vdr: video: get hwaccel context, not supported
Dec 22 15:26:46 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:26:47 MLD user.warn kernel: [49608.290789] clear: done = 0, 0 fifo bytes
Dec 22 15:26:54 MLD user.err vdr: video: get hwaccel context, not supported
Dec 22 15:26:54 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:26:54 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:26:54 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:26:54 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:26:54 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:26:56 MLD user.warn kernel: [49617.499518] clear: done = 0, 0 fifo bytes
Dec 22 15:27:02 MLD user.info kernel: [49623.773009] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:27:02 MLD user.warn kernel: [49623.773031] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:27:02 MLD user.warn kernel: [49623.773035] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:27:02 MLD user.warn kernel: [49623.773041] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:27:04 MLD user.warn kernel: [49625.415585] clear: done = 0, 0 fifo bytes
Dec 22 15:27:04 MLD user.err vdr: video: get hwaccel context, not supported
Dec 22 15:27:05 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:05 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:05 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:05 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:05 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:05 MLD user.warn kernel: [49626.804902] clear: done = 0, 0 fifo bytes
Dec 22 15:27:06 MLD user.warn kernel: [49627.564474] clear: done = 0, 0 fifo bytes
Dec 22 15:27:07 MLD user.err vdr: video: get hwaccel context, not supported
Dec 22 15:27:07 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:07 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:07 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:07 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:07 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:09 MLD user.warn kernel: [49630.599896] clear: done = 0, 0 fifo bytes
Dec 22 15:27:10 MLD user.err vdr: video: get hwaccel context, not supported
Dec 22 15:27:10 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:12 MLD user.err vdr: video: get hwaccel context, not supported
Dec 22 15:27:12 MLD user.err vdr: video/vdpau: can't render mixer: An invalid handle value was provided.
Dec 22 15:27:17 MLD user.info kernel: [49638.487394] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:27:17 MLD user.warn kernel: [49638.487418] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:27:17 MLD user.warn kernel: [49638.487424] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:27:17 MLD user.warn kernel: [49638.487432] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:28:06 MLD user.info kernel: [49687.559518] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:28:06 MLD user.warn kernel: [49687.559538] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:28:06 MLD user.warn kernel: [49687.559544] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:28:06 MLD user.warn kernel: [49687.559551] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:28:14 MLD user.warn kernel: [49695.405423] clear: done = 0, 0 fifo bytes
Dec 22 15:28:14 MLD user.warn kernel: [49695.406958] clear: done = 0, 0 fifo bytes
Dec 22 15:28:14 MLD user.warn kernel: [49695.408255] clear: done = 0, 0 fifo bytes
Dec 22 15:28:19 MLD user.info kernel: [49700.578128] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:28:19 MLD user.warn kernel: [49700.578147] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:28:19 MLD user.warn kernel: [49700.578153] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:28:19 MLD user.warn kernel: [49700.578160] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:28:19 MLD user.info kernel: [49700.594106] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:28:19 MLD user.warn kernel: [49700.594121] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:28:19 MLD user.warn kernel: [49700.594126] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:28:19 MLD user.warn kernel: [49700.594132] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:28:20 MLD user.info kernel: [49701.313447] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:28:20 MLD user.warn kernel: [49701.313465] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:28:20 MLD user.warn kernel: [49701.313471] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:28:20 MLD user.warn kernel: [49701.313478] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:28:35 MLD user.warn kernel: [49716.535317] clear: done = 0, 0 fifo bytes
Dec 22 15:29:05 MLD user.info kernel: [49746.233091] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:29:05 MLD user.warn kernel: [49746.233110] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:29:05 MLD user.warn kernel: [49746.233116] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:29:05 MLD user.warn kernel: [49746.233123] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:29:45 MLD user.info kernel: [49786.354343] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:29:45 MLD user.warn kernel: [49786.354362] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:29:45 MLD user.warn kernel: [49786.354368] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:29:45 MLD user.warn kernel: [49786.354375] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:29:53 MLD user.info kernel: [49794.711538] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:29:53 MLD user.warn kernel: [49794.711558] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:29:53 MLD user.warn kernel: [49794.711564] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:29:53 MLD user.warn kernel: [49794.711571] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:30:00 MLD user.warn kernel: [49801.093931] clear: done = 0, 0 fifo bytes
Dec 22 15:30:00 MLD user.warn kernel: [49801.100922] clear: done = 0, 0 fifo bytes
Dec 22 15:30:07 MLD user.warn kernel: [49808.173674] clear: done = 0, 0 fifo bytes
Dec 22 15:30:49 MLD user.info kernel: [49850.786921] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:30:49 MLD user.warn kernel: [49850.786941] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:30:49 MLD user.warn kernel: [49850.786947] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:30:49 MLD user.warn kernel: [49850.786954] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:30:51 MLD user.warn kernel: [49852.520464] clear: done = 0, 0 fifo bytes
Dec 22 15:31:00 MLD user.warn kernel: [49861.651592] clear: done = 0, 0 fifo bytes
Dec 22 15:31:31 MLD user.info kernel: [49892.142616] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:31:31 MLD user.warn kernel: [49892.142635] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:31:31 MLD user.warn kernel: [49892.142641] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:31:31 MLD user.warn kernel: [49892.142648] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:31:42 MLD user.info kernel: [49903.828933] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:31:42 MLD user.warn kernel: [49903.828952] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:31:42 MLD user.warn kernel: [49903.828959] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:31:42 MLD user.warn kernel: [49903.828965] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:32:04 MLD user.info kernel: [49925.511320] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:32:04 MLD user.warn kernel: [49925.511339] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:32:04 MLD user.warn kernel: [49925.511346] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:32:04 MLD user.warn kernel: [49925.511352] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:32:17 MLD user.info kernel: [49938.155757] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:32:17 MLD user.warn kernel: [49938.155779] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:32:17 MLD user.warn kernel: [49938.155785] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:32:17 MLD user.warn kernel: [49938.155792] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:32:27 MLD user.warn kernel: [49948.178100] clear: done = 0, 0 fifo bytes
Dec 22 15:32:27 MLD user.warn kernel: [49948.181951] clear: done = 0, 0 fifo bytes
Dec 22 15:32:48 MLD user.warn kernel: [49969.318449] clear: done = 0, 0 fifo bytes
Dec 22 15:32:48 MLD user.warn kernel: [49969.319015] clear: done = 0, 0 fifo bytes
Dec 22 15:32:52 MLD user.info kernel: [49973.493825] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:32:52 MLD user.warn kernel: [49973.493845] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:32:52 MLD user.warn kernel: [49973.493851] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:32:52 MLD user.warn kernel: [49973.493858] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:32:57 MLD user.warn kernel: [49978.539032] clear: done = 0, 0 fifo bytes
Dec 22 15:32:57 MLD user.warn kernel: [49978.582085] clear: done = 0, 0 fifo bytes
Dec 22 15:33:06 MLD user.warn kernel: [49987.730265] clear: done = 0, 0 fifo bytes
Dec 22 15:33:06 MLD user.warn kernel: [49987.755018] clear: done = 0, 0 fifo bytes
Dec 22 15:33:10 MLD user.info kernel: [49991.789240] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:33:10 MLD user.warn kernel: [49991.789260] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:33:10 MLD user.warn kernel: [49991.789265] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:33:10 MLD user.warn kernel: [49991.789273] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:33:23 MLD user.info kernel: [50004.622031] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:33:23 MLD user.warn kernel: [50004.622050] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:33:23 MLD user.warn kernel: [50004.622056] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:33:23 MLD user.warn kernel: [50004.622063] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:34:04 MLD user.info kernel: [50045.108320] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:34:04 MLD user.warn kernel: [50045.108341] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:34:04 MLD user.warn kernel: [50045.108347] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:34:04 MLD user.warn kernel: [50045.108354] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:34:12 MLD user.warn kernel: [50053.842348] clear: done = 0, 0 fifo bytes
Dec 22 15:34:12 MLD user.warn kernel: [50053.842914] clear: done = 0, 0 fifo bytes
Dec 22 15:34:26 MLD user.info kernel: [50066.958510] pcieport 0000:00:1c.3: AER: Corrected error received: 0000:00:1c.3
Dec 22 15:34:26 MLD user.warn kernel: [50066.958530] pcieport 0000:00:1c.3: PCIe Bus Error: severity=Corrected, type=Data Link Layer, (Transmitter ID)
Dec 22 15:34:26 MLD user.warn kernel: [50066.958536] pcieport 0000:00:1c.3:   device [8086:06bb] error status/mask=00001000/00002000
Dec 22 15:34:26 MLD user.warn kernel: [50066.958543] pcieport 0000:00:1c.3:    [12] Timeout
Dec 22 15:34:33 MLD user.warn kernel: [50073.959796] clear: done = 0, 0 fifo bytes
Dec 22 15:34:33 MLD user.warn kernel: [50073.989199] clear: done = 0, 0 fifo bytes


Ist das "schlimm" oder ist das "normal"? Habe ich ein Problem? Wie kann ich das beheben?

Gestern, nach dem Installieren (mein erster MLD, Umstieg von EasyVDR) und ein paar Stunden TV bzw. Ansehen von Aufnahmen, hatte ich einen Absturz, so dass ich den PC manuell neu starten musste - auch über das WebInterface konnte ich weder den VDR stoppen, noch herunterfahren. Aber da hatte ich auch vorher noch Plugins entfernt und hinzugefügt und Einstellungen im OSD geändert, etc.; deshalb würde ich den "Absturz" erstmal nicht beachten, sondern schauen, wie sich das Teil im weiteren Verlauf verhält...

Mir geht es im Moment darum, ob ich ein echtes Problem habe bzw. wie ich es lösen kann/ muss... Ich habe gerade nochmal nachgesehen: Der VDR ist die Nacht bis jetzt durchgelaufen, die Timer scheinen alle ausgeführt zu sein, die Aufnahmen sind gemäss Stichprobe ok und ich konnte alle 4 Tuner durchschalten und bekam Bild und Ton. Von daher bin ich erstmal vorsichtig entspannt...

Eine Antwort von euch könnte natürlich auch sein: "Nimm doch 5.4 Stable, da hast du keine Probleme!" Das wäre natürlich auch ok, ich will euch ja nicht nerven!

Vielen Dank & viele Grüße
Dirk

P.S.: Das Debug-Log habe ich mal hier angehängt.
Softwareware:
MLD 5.5 (Testing)
Hardware:
Intel Core i5-10500 auf ASUS TUF Gaming H470-Pro mit 8GB
Asus GeForce GT 1030 2GB (SoftHDDevice)
Digital Devices 2x DuoFlex S2 v4A
Flirc
System: SSD // Daten: HDD WD RedPlus
---
Rudimentäre Linux-Kenntnisse sind vorhanden - aber nicht wirklich belastbar...

Offline LincolnTC

  • Newbie
  • *
  • Posts: 32
    • View Profile
Meldungen in /var/log/messages -> Problem?
« Reply #1 on: December 22, 2021, 22:49:39 »
Hallo,

Asche auf mein Haupt - zumindest erstmal: Ich habe einfach mal Onkel Google gefragt und als erstes folgende Antwort bekommen:
https://www.thomas-krenn.com/de/wiki/PCIe_Bus_Error_Status_00001100_beheben

Ich werde in den nächsten Tagen erstmal versuchen, ob ich ASPM einfach mal im BIOS ausschalten kann.

Ansonsten würde ich gerne das hier versuchen:
Code: [Select]
Bei unseren Tests konnten wir das Problem durch Setzen des Kernel Paramenters pcie_aspm=off lösen.
Um diese Einstellung dauerhaft zu setzen, führen Sie folgende Schritte aus:
    Öffnen Sie die Grub Konfigurationsdatei in einem Editor, z.B. in vi:
        sudo vi /etc/default/grub
    Passen Sie die Variable GRUB_CMDLINE_LINUX_DEFAULT folgendermaßen an, speichern Sie die Datei und schließen Sie den Editor:
        GRUB_CMDLINE_LINUX_DEFAULT="quiet pcie_aspm=off"
    Nach der Konfigurationsänderung aktualisieren Sie den Grub Bootloader mit folgendem Kommando:
        sudo update-grub
    Führen Sie abschließend einen Neustart durch.

Aber diese Datei "/etc/default/grub" ist zumindest bei mir nicht vorhanden - wo müsste das bei MLD hin?

Vielen Dank & viele Grüße
Dirk
Softwareware:
MLD 5.5 (Testing)
Hardware:
Intel Core i5-10500 auf ASUS TUF Gaming H470-Pro mit 8GB
Asus GeForce GT 1030 2GB (SoftHDDevice)
Digital Devices 2x DuoFlex S2 v4A
Flirc
System: SSD // Daten: HDD WD RedPlus
---
Rudimentäre Linux-Kenntnisse sind vorhanden - aber nicht wirklich belastbar...

Offline clausmuus

  • Administrator
  • Expert Member
  • ********
  • Posts: 20414
    • View Profile
    • ClausMuus.de
Meldungen in /var/log/messages -> Problem?
« Reply #2 on: December 22, 2021, 22:55:56 »
Die MLD verwendet nicht grub sondern syslinux als Bootloader. Dementsprechend musst Du lediglich in der Datei /boot/syslinux/syslinux.conf die erste append Zeile um den Parameter erweitern.
MLD 5.5 - Raspberry PI - 7" Touch TFT - Squeeze Play
MLD 5.5 - lirc yaUsbIR - OctopusNet - XFX GeForce 9300 mit Intel E3200 - 2GB RAM - 12TB HDD - Lian Li PC-C37B - Samsung LE40A559

[1] MLD-5.x / General / Meldungen in /var/log/messages -> Problem?
 



Users Online Users Online

0 Members and 1 Guest are viewing this topic.