search for: 111d

i cannot read or write any disk inserted in my acd0 <PIONEER DVD-RW DVR-111D/1.29> when this device in udma mode. kernel endlessly repeat that acd0: setting up DMA failed and I can access my data on dvd or cd only if I set atacontrol mode acd0 pio4 Does anybody have such a problem too? is there any ways to bring this device into udma mode again? dmesg: ... atapci1...

...4]: Intel Corporation 80333 Segment-B PCI Express-to-PCI Express Bridge [8086:0372] 09:0e.0 RAID bus controller [0104]: Areca Technology Corp. ARC-1220 8-Port PCI-Express to SATA RAID Controller [17d3:1220] 0c:00.0 PCI bridge [0604]: Integrated Device Technology, Inc. PES12N3A PCI Express Switch [111d:8018] (rev 04) 0d:00.0 PCI bridge [0604]: Integrated Device Technology, Inc. PES12N3A PCI Express Switch [111d:8018] (rev 04) 0d:01.0 PCI bridge [0604]: Integrated Device Technology, Inc. PES12N3A PCI Express Switch [111d:8018] (rev 04) 0e:00.0 Ethernet controller [0200]: Intel Corporation 82571...

...c \ --with-ssl=openssl --with-ssldir=/local/dovecot.2.2.6/ssl \ --with-statedir=/local/dovecot-2.2.6/lib \ --with-moduledir=/local/dovecot-2.2.6/lib \ --with-rundir=/run/dovecot Bret Bret Jordan CISSP | Sr Security Architect PGP Fingerprint: 62A6 5999 0F7D 0D61 4C66 D59C 2DB5 111D 63BC A303 "Without cryptography vihv vivc ce xhrnrw, however, the only thing that can not be unscrambled is an egg." -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 841 bytes Desc: Message sign...

Hi, I have been receiving messages on a new DomU''s kern.log. I''ve done a lot of googling, but haven''t came up with anything very useful, at least not in a Xen context. I was wondering if anyone had any suggestions about what could be wrong. From everything I have read, there should be a stack trace included, but I am not seeing one. Thanks in advance, Ian. on

Hi list, I've recently managed to install CentOS 4.4 on an Apple Mac Pro. Functionality-wise everything works great, but when trying to benchmark the system, I don't get stable runtimes, they differ by more than 30%. For example a benchmark run with our PDE solving code takes between 500 and 800 s on the completely unloaded machine. Suspicious kernel output (complete output attached):