LSI 1030 mpt doesn't work if I build a new kernel

[eculp at bafirst.com]

Quoting Matthew Jacob <lydianconcepts at gmail.com>:

> Can you tell me more precisely what hardware you have?

It looks like I'm not the only one suffering with this but mine is on a 
colocated machine in another country and I haven't been able to see the 
errors but I haven't been able to boot a new kernel and am still using 
kernel.old from June 16, 2006.  Since all I know from here is that it 
doesn't boot.  It is a dell 2650 and I've attached a boot message for a 
reboot yesterday with the old kernel after failing to boot with the new 
one.

Any help appreciated,

ed

With the old kernel I'm seeing a lot of the following messages that I 
have no idea what they mean much less how to fix them or even if I 
should ignore them, but just in case:

mpt0: <LSILogic 1030 Ultra4 Adapter> port 0xec00-0xecff mem 
0xdfdf0000-0xdfdfffff,0xdfde0000-0xdfdeffff irq 34 at device 5.0 on pci2
...skipping...
(da0:mpt0:0:0:0): tagged openings now 140
(da0:mpt0:0:0:0): Retrying Command
(da0:mpt0:0:0:0): Queue Full
(da0:mpt0:0:0:0): tagged openings now 139
(da0:mpt0:0:0:0): Retrying Command
(da0:mpt0:0:0:0): Queue Full
(da0:mpt0:0:0:0): tagged openings now 138
(da0:mpt0:0:0:0): Retrying Command
(da0:mpt0:0:0:0): Queue Full
(da0:mpt0:0:0:0): tagged openings now 137

>
> On 9/1/06, Rod Person <rodperson at adelphia.net> wrote:
>> I've been struggling with this for a month or two now.
>>
>> I installed FreeBSD current 7 with a march snapshot and this work good,
>> but I've tried to build a new kernel for the 2 month period and building
>> a kernel causes the mpt driver to panic on boot.
>>
>> Here is so of the boot message:
>>
>> mpt1: [GIANT-LOCKED]
>> mpt1: MPI Version=1.2.14.0
>> mpt1: mpt_wait_req(4) timed out
>> mpt1: read_cfg_header timed out
>> mpt1: mpt_wait_req(6) timed out
>> mpt1: port 0 enable timed out
>> mpt1: failed to enable port 0
>>
>> then this repeats until the system hangs:
>>
>> mpt0: Address Reply:
>> SCSI Target Command Buffer Reply @ 0xffffffffacc7a200
>>         IOC Status    Success
>>         IOCLogInfo    0x00000000
>>         MsgLength     0x05
>>         MsgFlags      0x00
>>         MsgContext    0x0003005d
>> mpt0: Reply Frame Ignored
>> mpt0: Default Handler Called: req=0xffffffff80e49050:95
>> reply_descriptor=dc913980 frame=0xffffffffacc7a300
>> mpt0: Address Reply:
>>
>> I was wondering if this is a known problem or if there are any hints on
>> correcting this?
>>
>> Rod
>>
>> _______________________________________________
>> freebsd-current at freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-current
>> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>>
> _______________________________________________
> freebsd-current at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org"
>



-------------- next part --------------
A non-text attachment was scrubbed...
Name: dmesg.boot
Type: application/octet-stream
Size: 6200 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-current/attachments/20060902/e788a806/dmesg.obj