[<prev] [next>] [day] [month] [year] [list]
Message-ID: <d2d13c8a-47f9-40b1-bd80-caa7b3b42a6d@zmail06.collab.prod.int.phx2.redhat.com>
Date: Fri, 23 Sep 2011 05:20:51 -0400 (EDT)
From: CAI Qian <caiqian@...hat.com>
To: linux-kernel@...r.kernel.org
Cc: Jon Mason <mason@...i.com>, Jordan_Hargrave@...l.com,
esse Barnes <jbarnes@...tuousgeek.org>
Subject: regression introduced by "PCI: Set PCI-E Max Payload Size on fabric" patch
After reverted this commit,
b03e7495a862b028294f59fc87286d6d78ee7fa1
PCI: Set PCI-E Max Payload Size on fabric
A server with qla2xxx is able to boot the latest mainly kernel.
QLogic Fibre Channel HBA Driver: 8.03.07.03-k
qla2xxx 0000:06:02.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
qla2xxx 0000:06:02.0: Found an ISP2422, irq 17, iobase 0xf9dfe000
qla2xxx 0000:06:02.0: Configuring PCI space...
qla2xxx 0000:06:02.0: Configure NVRAM parameters...
qla2xxx 0000:06:02.0: Verifying loaded RISC code...
qla2xxx 0000:06:02.0: FW: Loading via request-firmware...
qla2xxx 0000:06:02.0: Allocated (64 KB) for EFT...
qla2xxx 0000:06:02.0: Allocated (773 KB) for firmware dump...
scsi1 : qla2xxx
Otherwise, it hung right here.
scsi0 : ioc0: LSISAS1064E B1, FwRev=011b5700h, Ports=1, MaxQ=277, IRQ=19
mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 5, phy 0, sas_addr 0x5000cca0007ed401
scsi scan: INQUIRY result too short (5), using 36
scsi 0:0:0:0: Direct-Access PQ: 0 ANSI: 0
mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 4, phy 1, sas_addr 0x5000c50017501eb1
scsi 0:0:1:0: Direct-Access IBM-ESXS ST9146803SS B536 PQ: 0 ANSI: 5
mptsas: ioc0: attaching raid volume, channel 1, id 3
scsi 0:1:3:0: Direct-Access LSILOGIC Logical Volume 3000 PQ: 0 ANSI: 2
sd 0:1:3:0: [sda] 285155328 512-byte logical blocks: (145 GB/135 GiB)
sd 0:1:3:0: [sda] Write Protect is off
sd 0:1:3:0: [sda] Got wrong page
sd 0:1:3:0: [sda] Assuming drive cache: write through
sd 0:1:3:0: [sda] Got wrong page
sd 0:1:3:0: [sda] Assuming drive cache: write through
CAI Qian
--
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