Desai, Kashyap wrote:
Sachin, This may be related to something specific to your system's APIC/or bad HW rather than pure driver issue. Below line from log is important to note. "mptsas 0000:03:04.0: can't find IRQ for PCI INT A; probably buggy MP table" It means LSI controller is not able to reserve IRQ line and that is where all problem starts. Need to broaden the scope of the issue. Another confusing thing to me. I have seen "probably buggy MP table" print only in arch/x86, but you have mentioned that in your case arch is x86_64. Thanks, Kashyap
This actually was because of some other problem. Here is the post for it. http://marc.info/?l=linux-kernel&m=126741813906116&w=2 Which was eventually fixed. Patch is available here. http://marc.info/?l=linux-kernel&m=126745177832615&w=2 Thanks -Sachin
-----Original Message----- From: linux-scsi-owner@xxxxxxxxxxxxxxx [mailto:linux-scsi- owner@xxxxxxxxxxxxxxx] On Behalf Of Sachin Sant Sent: Tuesday, February 09, 2010 6:12 PM To: linux-scsi Cc: linux-next@xxxxxxxxxxxxxxx; LKML; Moore, Eric Subject: [-next Feb 9] Boot failure on x86_64: mptbase fails to initialize Today's next failed to boot on my 4 way x86_64 box because of mptbase driver initialization failure. Snippet of messages during boot : Fusion MPT SAS Host driver 3.04.14 mptsas 0000:03:04.0: can't find IRQ for PCI INT A; probably buggy MP table mptbase: ioc0: Initiating bringup ioc0: LSISAS1064 A3: Capabilities={Initiator} mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! mptbase: ioc0: Initiating recovery mptbase: ioc0: Attempting Retry Config request type 0x1, page 0x2, action 0 mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! mptbase: ioc0: Initiating recovery mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! mptbase: ioc0: Initiating recovery mptbase: ioc0: Attempting Retry Config request type 0x1, page 0x1, action 0 mptbase: ioc0: WARNING - Issuing Reset from mpt_config!! Eventually machine fails to boot. I have similar problem on a x86 box but with IPS driver. So might not be a driver specific issue. I had similar problem with yesterday's next.IIRC the last successful boot was with next-20100203. Have attached the boot log from x86_64 box. Thanks -Sachin -- --------------------------------- Sachin Sant IBM Linux Technology Center India Systems and Technology Labs Bangalore, India ---------------------------------
-- --------------------------------- Sachin Sant IBM Linux Technology Center India Systems and Technology Labs Bangalore, India --------------------------------- -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
