Probleme mit PCI und USB-Karten

Carsten Weisky <[email protected]>
Newsgroups spline.eisxen
Organization spline
Message-ID <[email protected]>
Hallo zusammen,
habe scheinbar ein Problem mit den PCI Karten.

folgendes kommt im Kernellog am Eisxen:
sagt euch das was?


│May  3 09:57:39 eisxen kernel: [   86.728250] pciback 0000:00:1d.0: 
Driver tried to write to a read-only configuration space field at offset 
0xc0, size 2. This may be harmless, b▒
│May  3 09:57:39 eisxen kernel: [   86.728251] 1) see permissive 
attribute in sysfs 
                                           ▒
│May  3 09:57:39 eisxen kernel: [   86.728252] 2) report problems to the 
xen-devel mailing list along with details of your device obtained from 
lspci.                             ▒
│May  3 09:57:39 eisxen kernel: [   86.829248] PCI: Enabling device 
0000:00:1d.1 (0000 -> 0001) 
                                        ▒
│May  3 09:57:39 eisxen kernel: [   86.829259] ACPI: PCI Interrupt 
0000:00:1d.1[B] -> GSI 19 (level, low) -> IRQ 19 
                                         ▒
│May  3 09:57:39 eisxen kernel: [   86.829316] PCI: Setting latency 
timer of device 0000:00:1d.1 to 64 
                                        ▒
│May  3 09:57:39 eisxen kernel: [   86.829403] pciback 0000:00:1d.1: 
Driver tried to write to a read-only configuration space field at offset 
0xc0, size 2. This may be harmless, b▒
│May  3 09:57:39 eisxen kernel: [   86.829405] 1) see permissive 
attribute in sysfs 
                                           ▒
│May  3 09:57:39 eisxen kernel: [   86.829405] 2) report problems to the 
xen-devel mailing list along with details of your device obtained from 
lspci.                             ▒
│May  3 09:57:40 eisxen kernel: [   86.933212] PCI: Enabling device 
0000:00:1d.2 (0000 -> 0001) 
                                        ▒
│May  3 09:57:40 eisxen kernel: [   86.933225] ACPI: PCI Interrupt 
0000:00:1d.2[C] -> GSI 18 (level, low) -> IRQ 20 
                                         ▒
│May  3 09:57:40 eisxen kernel: [   86.933282] PCI: Setting latency 
timer of device 0000:00:1d.2 to 64 
                                        ▒
│May  3 09:57:40 eisxen kernel: [   86.933363] pciback 0000:00:1d.2: 
Driver tried to write to a read-only configuration space field at offset 
0xc0, size 2. This may be harmless, b▒
│May  3 09:57:40 eisxen kernel: [   86.933365] 1) see permissive 
attribute in sysfs 
                                           ▒
│May  3 09:57:40 eisxen kernel: [   86.933366] 2) report problems to the 
xen-devel mailing list along with details of your device obtained from 
lspci.                             ▒
│May  3 09:57:40 eisxen kernel: [   87.037200] PCI: Enabling device 
0000:00:1d.3 (0000 -> 0001) 
                                        ▒
│May  3 09:57:40 eisxen kernel: [   87.037213] ACPI: PCI Interrupt 
0000:00:1d.3[D] -> GSI 16 (level, low) -> IRQ 16 
                                         ▒
│May  3 09:57:40 eisxen kernel: [   87.037274] PCI: Setting latency 
timer of device 0000:00:1d.3 to 64 
                                        ▒
│May  3 09:57:40 eisxen kernel: [   87.037354] pciback 0000:00:1d.3: 
Driver tried to write to a read-only configuration space field at offset 
0xc0, size 2. This may be harmless, b▒
│May  3 09:57:40 eisxen kernel: [   87.037356] 1) see permissive 
attribute in sysfs 
                                           ▒
│May  3 09:57:40 eisxen kernel: [   87.037356] 2) report problems to the 
xen-devel mailing list along with details of your device obtained from 
lspci.                             ▒
│May  3 09:57:40 eisxen kernel: [   87.141408] PCI: Enabling device 
0000:00:1d.7 (0000 -> 0002) 
                                        ▒
│May  3 09:57:40 eisxen kernel: [   87.141416] ACPI: PCI Interrupt 
0000:00:1d.7[A] -> GSI 23 (level, low) -> IRQ 18 
                                         ▒
│May  3 09:57:40 eisxen kernel: [   87.141478] PCI: Setting latency 
timer of device 0000:00:1d.7 to 64 
                                        ▒
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.