lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 6 Sep 2011 16:39:48 +0800
From:	Jeff Chua <jeff.chua.linux@...il.com>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	lkml <linux-kernel@...r.kernel.org>, Jordan_Hargrave@...l.com,
	Jon Mason <mason@...i.com>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: linux-3.1-0-rc4 bus error ... MPS configured higher than maximum
 supported by the device. If a bus issue occurs, try running with pci=pcie_bus_safe.

On Tue, Sep 6, 2011 at 2:25 PM, Eric Dumazet <eric.dumazet@...il.com> wrote:
> Le mardi 06 septembre 2011 à 14:09 +0800, Jeff Chua a écrit :
>> On Mon, Sep 5, 2011 at 10:55 PM, Jeff Chua <jeff.chua.linux@...il.com> wrote:
>> > Got the following error after upgrading from linux-2.6.36 to
>> > linux-3.1.0-rc4 on a Dell PowerEdge 2950 that has a PCIe fax card, and
>> > the system LED panel shows "Bus Fatal Error".
>> >
>> >
>> > Is is normal or should I try out "pci=pcie_bus_safe" or "pci=pci" as
>> > suggested in the dmesg?
>> >
>> > There was another error that also showed up on 2.6.36 but I'm ignoring
>> > that for now ( ... disabling ASPM on pre-1.1 PCIe device.  You can
>> > enable it with 'pcie_aspm=force')
>> >
>> > pci 0000:07:00.0: Dev MPS 128 MPSS 256 MRRS 4096
>> > pci 0000:07:00.0: Dev MPS 256 MPSS 256 MRRS 128
>> > pci 0000:08:00.0: Dev MPS 128 MPSS 128 MRRS 128
>> > pci 0000:08:00.0: MPS configured higher than maximum supported by the
>> > device.  If a bus issue occurs, try running with pci=pcie_bus_safe.
>> > pci 0000:08:00.0: Dev MPS 256 MPSS 256 MRRS 128
>> > Uhhuh. NMI received for unknown reason 31 on CPU 0.
>> > Do you have a strange power saving mode enabled?
>> > Dazed and confused, but trying to continue
>> > pci 0000:07:01.0: Dev MPS 128 MPSS 256 MRRS 4096
>> > pci 0000:07:01.0: Dev MPS 256 MPSS 256 MRRS 128
>> > pci 0000:00:06.0: Dev MPS 256 MPSS 256 MRRS 128
>> > pci 0000:0e:00.0: Dev MPS 128 MPSS 128 MRRS 512
>> > pci 0000:0e:00.0: MPS configured higher than maximum supported by the
>> > device.  If a bus issue occurs, try running with pci=pci
>>
>> The above aspm and bus error went away after I added pcie_aspm=force
>> and pci=pcie_bus_safe.
>>
>> Instead of default to pcie_bus_perf that caused problems, why not
>> default to the formal behavior (see commit
>> b03e7495a862b028294f59fc87286d6d78ee7fa1).
>
> I believe a revert is in progress anyway, see my other thread (scsi:
> hpsa: how to destroy your files)

Eric,

Thanks. I saw that. And the system nearly got trashed even though I've
no hpsa. Grub went into rescue mode after reboot, and I had to rebuild
the grub boot sector.

Now, it's all ok with pcie_aspm=force and pci=pcie_bus_safe.

Thanks,
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ