similar to: kernel message - disabling irq #50

I have just bought a 120GB external usb drive but after plugging it in it is not getting mounted. lines from /var/log/messages: > Oct 22 18:54:49 station2 kernel: usb 1-2: new high speed USB device using ehci_hcd and address 2 > Oct 22 18:54:49 station2 kernel: usb 1-2: configuration #1 chosen from 1 choice > Oct 22 18:54:49 station2 kernel: scsi4 : SCSI emulation for USB Mass Storage

Hello, I have an issue with my XEN system. I suspect that it might be a bug, but I''m no linux expert, so I don''t know. Here is my problem: I have an ASUS P7P55D-E Premium motherboard, and a Western Digital Caviar Black SATA-III 1TB hdd. I am trying to use AHCI. The dom0 is an Arch Linux. The dom0 boots fine until Intel VT-d is enabled in the BIOS. When I enable it Arch

Hello List, I'm hoping someone else out there has an Asus DSBF-DE server board, and can tell me if anything special needs to be done to get ports 5 and 6 of the onboard SATA to work under Centos 5.1 x64. I have drives on 1 through 4 that are detected and working properly, however, a drive on 5 is not detected, from what i can tell, the kernel doesn't even see phy's for ports 5 and 6.

I have a user who wants to have 4 monitors attached to his CentOS 6.4 system. I know that you can't use both on-board video and a PCI video card at the same time, but what about two PCI video cards? The system seems to recognize them as shown by the lspci -v output below, but I can't get Xorg to use the second card. Has anyone done this? If so, what is the trick to get it to work?

Ack! This slipped through my email. I am terribly sorry. Thank you so much for responding. On 04/06/2014 08:43 PM, Ilia Mirkin wrote: > On Sun, Apr 6, 2014 at 7:16 PM, ~Stack~ <i.am.stack at gmail.com> wrote: >> Greetings, [snip] >> My working kernel is: 2.6.32-358.23.2.el6.x86_64 (and anything before). >> >> The problem kernel is: 2.6.32-431.1.2.el6.x86_64 and

Package: linux-2.6 Version: 2.6.32-26~bpo50+1 Severity: important --- Please enter the report below this line. --- I've installed the following packages an lenny, which are working well on other maschines. # dpkg -l | grep xen | grep bpo ii libxenstore3.0 4.0.1-1~bpo50+1 Xenstore communications library for Xen ii linux-image-2.6.32-bpo.5-xen-686 2.6.32-26~bpo50+1 Linux 2.6.32 for modern

Hello, I have experienced a dom0 crash where the system became unreachable via the network and the console was unresponsive. I would appreciate help interpretting the logs and any configuration change suggestions. It is a stock Debian Lenny dom0 running xen 3.2.1 with kernel 2.6.26-2-xen-amd64 and an AMD Athlon IIx4 with 4 GB of RAM. It is running 4 VMs. One VM has two PCI NICs being

+cc: ocfs2-devel, sunil Marek, Thanks for the detailed report! Can I trouble you to file a bug at http://oss.oracle.com/bugzilla ... oh, is that your report http://oss.oracle.com/bugzilla/show_bug.cgi?id=1339? This looks like a deadlock of some sort. I don't think your hardware configuration really matters here. We'll keep looking into it. Joel On Tue, Dec 20, 2011 at 08:22:48AM

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-4 Severity: normal Tags: squeeze When the monitor is being restored from power saving mode via DPMS, X will lock up/restart. This only occurs when running Xen hypervisor. Running just 2.6.32-5 -xen-amd64 doesn't produce this effect. Note that both 2.6.32-5-xen-amd64 and 2.6.32-5-xen-amd64 with Xen 4.0.1 are running with nopat (to workaround

On 10/02/2020 07:38 AM, H wrote: > On October 1, 2020 11:58:11 AM EDT, Bruce Ferrell <bferrell at baywinds.org> wrote: >> On 9/30/20 8:52 AM, H wrote: >>> 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset >> Family USB 3.0 xHCI Controller >> My system has these: >> >> 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series

Hi Daniel, On Fri, Aug 24, 2018 at 11:31:54AM +0800, Daniel Drake wrote: > Hi, > > We are facing a suspend/resume problem with many different Asus laptop > models (30+ products) with Intel chipsets (multiple generations) and > nvidia GPUs (several different ones). Reproducers include: Are these systems also affected through runtime power management? For example: modprobe

On 10/28/2017 02:55 PM, Gregory P. Ennis wrote: > Date: Sat, 28 Oct 2017 12:03:51 -0700 > > On 10/28/2017 11:30 AM, Gregory P. Ennis wrote: > > On each of these units I am using the video from the mother board > > which > > is : > > > > Base Board Information > > ?????????Manufacturer: ASUSTeK COMPUTER INC. > > ?????????Product Name: B150M-A/M.2

First off, the current state of support for Maxwell (GM107/NV110) is not very useful to end-users. It's especially not useful if it's a 3d accelerator card without outputs (as yours appears to be), since acceleration is not supported in 3.15 out of the box. You'd have to figure out how to extract the context switching firmware from the blob driver and load it in nouveau. I'm told

On 9/30/20 8:52 AM, H wrote: > 00:14.0 USB controller: Intel Corporation 200 Series/Z370 Chipset Family USB 3.0 xHCI Controller My system has these: 00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 05) 00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 05) 00:1d.0 USB controller: Intel Corporation 8

doing the same on the bridge controller with my workarounds applied: please note some differences: LnkSta: Speed 8GT/s (ok) vs Speed 2.5GT/s (downgraded) SltSta: PresDet+ vs PresDet- LnkSta2: Equalization stuff Virtual channel: NegoPending- vs NegoPending+ both times I executed lspci while the GPU was still suspended. 00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core

Hi, We are facing a suspend/resume problem with many different Asus laptop models (30+ products) with Intel chipsets (multiple generations) and nvidia GPUs (several different ones). Reproducers include: 1. Boot 2. Suspend/resume 3. Load nouveau driver 4. Start X 5. Observe slow X startup and many many errors in logs (primarily nouveau fifo faults) or 1. Boot 2. Load nouveau driver 3. Start X

On 10/28/2017 02:55 PM, Gregory P. Ennis wrote: > Date: Sat, 28 Oct 2017 12:03:51 -0700 > > On 10/28/2017 11:30 AM, Gregory P. Ennis wrote: > > On each of these units I am using the video from the mother board > > which > > is : > > > > Base Board Information > > ?????????Manufacturer: ASUSTeK COMPUTER INC. > > ?????????Product Name: B150M-A/M.2

On Mon, Jun 03, 2019 at 03:18:56PM +0200, Karol Herbst wrote: > @bjorn: any further ideas? Otherwise I'd like to just go ahead and fix > this issue inside Nouveau and leave it there until we have a better > understanding or non Nouveau cases of this issue. Nope, I have no more ideas. > On Tue, May 21, 2019 at 7:48 PM Karol Herbst <kherbst at redhat.com> wrote: > >

ohh nvm. It was a mistake on my end. Sorry for the noise On Wed, Jun 19, 2019 at 2:07 PM Karol Herbst <kherbst at redhat.com> wrote: > > Hi Bjorn, > > I was playing around with some older information again (write into the > PCI config to put the card into d3 state). And there is something > which made me very curious: > If I put the card manually into any other state

On Tue, Sep 4, 2018 at 2:43 PM, Mika Westerberg <mika.westerberg at linux.intel.com> wrote: > Yes, can you check if the failing device BAR is included in any of the > above entries? If not then it is probably not related. mtrr again for reference: reg00: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable reg01: base=0x0a0000000 ( 2560MB), size= 512MB, count=1: uncachable