similar to: Bug#602109: [linux-2.6] 1 multicall(s) failed: cpu 0

+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

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, I have a *very* strange problem, unfortunately it's kind of a show stopper regarding the deployment of the machine. :( I have two Intel Gigabit Ethernet NICs on board (Supermicro-based Server), quoting lspci (full output see at the end of the email): 0d:00.0 Ethernet controller: Intel Corporation 82573E Gigabit Ethernet Controller

Hello, I own a PCI-Express parallel card installed on my server Fujitsu TX100 S2. I am running CentOS 6 x64. In Kernel version 2.6.32-71.29.1.el6.x86_64, it was correctly detected as: [root at Carmen ~]# lspci -vvv -s 05:00.2 05:00.2 Parallel controller: NetMos Technology Device 9912 (prog-if 03 [IEEE1284]) Subsystem: Device a000:2000 Physical Slot: 4 Control: I/O+ Mem+

Hi, I am working with a westemere based server. I need to find out if the NIC installed there supports SR-IOV - what would be the best way to determine that? Regards, Kashyap hwconfig ------------- Summary: HP DL160 G6, 2 x Xeon E5620 2.40GHz, 15.7GB / 16GB 1333MHz, 1 x 500GB SATA System: HP ProLiant DL160 G6, C-2N/16/500, ySPEC 25.0 Processors: 2 x Xeon E5620 2.40GHz (HT

On Fri, Jan 2, 2015 at 1:35 AM, Rafeal Stewart <mechy2k2000 at gmail.com> wrote: > On Thu, 2015-01-01 at 22:01 -0800, John R Pierce wrote: > > On 1/1/2015 9:41 PM, mechy2k2000 wrote: > > > Hello I am thinking of buying this card to and wanted to know if this > NIC > > > is supported. The card is a Sun Microsystems PCI-X Quad-Port Gigabit > > >

This is a return to an issue I first raised back in June. We had a similar occurrence in September while I was away and so I am revisiting the entire matter. Steve Clark on 6 Jun 16:02 2014 wrote: > Hi, > > We ran into this problem also - the interface would disappear. > There is newer e1000e driver that fixes it or you could > add pcie_aspm=off to your kernel command line. >

On 09/03/2013 09:45 PM, Ben Skeggs wrote: > On Fri, Aug 30, 2013 at 5:11 PM, Lucas Stach <dev at lynxeye.de> wrote: >> Am Freitag, den 30.08.2013, 15:36 +1000 schrieb Ben Skeggs: >>> On Fri, Aug 30, 2013 at 12:01 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote: >>>> On Thu, Aug 29, 2013 at 9:58 PM, Ben Skeggs <skeggsb at gmail.com> wrote:

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

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

Hi Brian, From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. You can check PCI bus whether support MSI like: cat /sys/bus/pci/devices/00:0e.0/msi_bus Other, do you call pci_enable_device() before pci_enable_msi() ? On

Hi, any pointer on how to debug this: [ 19.741005] nouveau 0000:01:00.0: enabling device (0541 -> 0543) [ 19.741095] nouveau 0000:01:00.0: Using 32-bit DMA via iommu [ 19.741165] nouveau 0000:01:00.0: NVIDIA GP108 (138000a1) [ 19.752562] tg3 0004:01:00.0 enP4p1s0f0: renamed from eth0 [ 19.832879] [drm] Initialized ast 0.1.0 20120228 for 0005:02:00.0 on minor 0 [ 19.856391] nouveau

On 2014/7/4 10:45, Brian Becker wrote: > Yijing, > > cat /sys/bus/pci/devices/0000\:00\:0e.0/msi_bus returns 1, suggesting > that it supports MSI. However, this "00:0e.0 PCI bridge: PLX > Technology, Inc. PEX8112 x1 Lane PCI Express-to-PCI Bridge (rev aa)" > is a component of the addin card. Wouldn't the lack of support for MSI > by the chipset "00:00.0

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #20 from Andreas Loew <awl1 at gmx.net> --- Had been missing my "lspci -nnvv" information: 01:00.0 VGA compatible controller [0300]: NVIDIA Corporation G86M [Quadro NVS 130M] [10de:042a] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Device [1179:0002] Control: I/O+ Mem+

On 2014/7/4 10:43, Ilia Mirkin wrote: > On Thu, Jul 3, 2014 at 10:35 PM, Yijing Wang <wangyijing at huawei.com> wrote: >> Hi Brian, >> From your 01:00.0 VGA compatible controller PCI config register, it supports 1 MSI vector, so I think this >> card has no problem. But you didn't answer what's the pci_enable_msi() return during it enable MSI fail. >>

On 04/10/2014 05:14 PM, Ilia Mirkin wrote: > You might mention what hardware you have (lspci output for the nvidia > card... just need the chip name), and what kernels the various distros > are using. (I think that Ubuntu/Fedora tend not to make frankenkernels > like RHEL does, so the version has some sort of correlation to actual > upstream versions.) That might help identify

Hi List, I have an ASUS G73S laptop with our favorite OS installed and all up-to-date. Sound has always "just worked" When I use the Preferences>Sound app I can setup the hardware, input, output and was overall very impressed. One can check each speaker and the laptop has a front left and right and also has a bass speaker which seems to be connected to the left rear. The various

On Tue, 2013-03-19 at 11:13 -0400, Peter Hurley wrote: > On vanilla 3.9.0-rc3, I get this 100% repeatable oops after login when > the user X session is coming up: Perhaps I wasn't clear that this happens on every boot and is a regression from 3.8 I'd be happy to help resolve this but time is of the essence; it would be a shame to have to revert all of this for 3.9 Regards, Peter

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #10 from Paulo Castro <pauloedgarcastro at gmail.com> --- Hi. I have exactly the same issue. I seem to be able to trigger it faster by opening firefox on a page with many images. Current Kernel: 3.8.3-103.fc17.x86_64 Other kernels affected: kernel-3.7.9-104.fc17.x86_64 kernel-3.7.9-101.fc17.x86_64 01:00.0 VGA compatible