similar to: RE: qla2xxx driver failed in dom0 - invalid opcode: 0000[1] SMP

I wanted to post this in case there is a real bug here. The system this is on is running Debian Etch with the Xen packages from Debian Unstable (currently 3.0.2+hg9697-1). I am running all packaged software so this is probably slightly out of date. This is on an HP DL320 G4 with a Pentium D 930 processor. I tried unloading and reloading the qla2xxx module, but rmmod reported it in use, however

Hello, I''m having trouble during high IO activities: Oct 8 10:38:51 matrix kernel: irq 16: nobody cared (try booting with the "irqpoll" option) Oct 8 10:38:51 matrix kernel: Oct 8 10:38:51 matrix kernel: Call Trace: <IRQ> <ffffffff801519b0>{__report_bad_irq+48} Oct 8 10:38:51 matrix kernel: <ffffffff80151c0f>{note_interrupt+511}

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

> > Well, i''m using here the qla2340 on several boxes. It works > > with Xen 2.0 but noch with Xen 3.0. as part of SUSE Linux 10.0: > > Interesting. If the driver really doews work flawlessly in > Xen 2, then I think the culprit has to be interrupt routeing. > > Under Xen 3, does /proc/interrupts show you''re receiving interrupts? I cannot boot with

> When running on 4GB of total memory instead of 12GB, > everything is just fine. (the three virtual machines, Dom0 + > 2 x DomU are assigned 1GB of memory each, in both test runs). > Does that help? Is this with the kernel and xen from -unstabele/3.0.3 ? Have you changed the config? What storage device do you have? What NIC? Are you setting mem=4096M on the Xen command line? If

I''ve compiled the 3.0-devel version on SUSE Linux 9.3. The ony problem is the qla2300 driver, which will not start all correctly on boot. So i cannot see other partitions than sda. --------------------------------------------------------------------------------- QLogic Fibre Channel HBA Driver ACPI: PCI Interrupt 0000:04:02.0[A] -> GSI 24 (level, low) -> IRQ 185 qla2300

CentOS Errata and Enhancement Advisory 2016:0682 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-0682.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: beb8bae27284f3d614fc06a783956a67bdf4954962014a9e79e6dca337a4d65f kmod-qla2xxx-8.07.00.26.06.8_k-1.el6_7.i686.rpm x86_64:

CentOS Errata and Enhancement Advisory 2016:1375 Upstream details at : https://rhn.redhat.com/errata/RHEA-2016-1375.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 08a6bc752e27c15e9416e7e517f3d8196230222a0b48500feabb503a51526233 kmod-qla2xxx-8.07.00.33.07.3_k-1.el7_2.x86_64.rpm Source:

hi All, Re below - thanks for the replies to the fsck question. I have run fsck -r /data and this eventually completed with several changes made. Now I am getting the following error from the qla2xxx driver on boot . . . qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort. qla2xxx 0000:05:0d.0: Mailbox command timeout occured. Scheduling ISP abort. . etc . It looks

hi All, thanks for the responses. After being dropped into the # Filesystem repair prompt, ( on account of "inode 27344909 has illegal blocks" ) following warm reboot (via "reboot") after finding (SAN ) filesystem in read-only mode yesterday morning (possibly because of HBA fault on SAN) , I ran fsck -r /data (Linux version 2.6.18-92.1.18.el5 , Red Hat 4.1.2-42 , ext3

Hello list, I just got this ominous bug on my machine, that has already been seen several times: http://lists.xensource.com/archives/html/xen-devel/2006-01/msg00180.html The machine is very similar, it''s a machine with two dual-core opterons, running one of the latest xen-3.0.3-unstable (20060926 hypervisor, and a vanilla 2.6.18 + xen patch from Fedora from 20060915). This machine was

We have several large ext3 file system partitions. One of them sets itself to read-only after getting journel problems. I understand that's a good thing, but obviously I need to correct the problem so that it will stop locking itself. Here are some details; OS is Redhat EL4 x86_64 running on a SunFire v40z, kernel is 2.6.9-42.0.2.ELsmp. The disk storage in question is external, via

We are using the Hp-Agents continuously on our Servers. The latest Version with centos-3.3 was no Problem. Mainly it depends on the used kernel Versions, because the raid driver modules are not for vanilla kernels, only for official Kernels from Redhat, Suse ... The only thing you have to do, is to fake the /etc/redhat-release, because the installer looks for supported Linux Versions. After

I am debating installing CentOS on a new HP DL580 with an MSA1000 SAN. HP offers drivers that are specific to RHEL and will not install on other RH distros i.e. RH 9. Has anyone gotten the HP SupportPack to install under CentOS? Thanks! -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

Here's my setup: - Single Mac OS X Panther client w/ latest patches. - Single Windows NT4 w/ latest SPs client. - Debian stable Samba server(2.2.3a-13) w/ custom 2.4.26 kernel. Oplocks enabled. - Cisco 2950 - All nodes 100Mb and everything on the same switch. - HP DL360 w/ 2.8GHz hyper-threaded processor and 1GB of memory. - HP

Hi all, has anyone seen such a behaviour?: I delegated successfully my NIC to a domU, but access to it from domU is not possible. Device appears, but access to it via ''ifconfig ethX up'' doesn''t work. Ends up in dmesg output like: tg3: tg3_reset_hw timed out for eth1, firmware will not restart magic=00000000 Delegating my USB controllers e.g. works flawlessly. Full

we started using an ocfs file system about 4 months ago as the shared archived redo destination for the 4-node rac instances (HP dl380, msa1000, RH AS 2.1) . last night we are seeing some weird behavior, and my guess is the inode directory in the file system is getting corrupted. I've always had a bad feeling about OCFS not being very robust at handling constant file creation and deletion