kern/53566: IBM Eserver (245 || 345) + ServeRaid 5i ips driver panic

[Jack Patton]

The following reply was made to PR kern/53566; it has been noted by GNATS.

From: Jack Patton <jackp at flag.60north.net>
To: <freebsd-gnats-submit at freebsd.org>, <jackp at flag.60north.net>
Cc: <nate at root.org>, <ntwaddel at webspacesolutions.com>,
	<current at freebsd.org>
Subject: Re: kern/53566: IBM Eserver (245 || 345) + ServeRaid 5i ips driver panic
Date: Wed, 25 Jun 2003 20:04:54 -0000

 In this mail:
 http://www.freebsd.org/cgi/getmsg.cgi?
 fetch=29403+32287+/usr/local/www/db/text/2003/freebsd-scsi/20030615.freebsd-
 scsi
 
 It was suggested to do a backtrace on it. I didn't have the option in 5.1-
 RELEASE, but I grabbed the 20030624 snapshot and was able to get the 
 following information.
 
 First of all the error seems slightly different, but the end result is the 
 same, unable to boot fully. First I get (the relevant parts IMO):
 
 ..
 pcib5: <ServerWorks host to PCI bridge(unknown chipset)> at pcibus 5 on 
 motherboard
 pci5: <PCI Bus> on pcib5
 ips0: <IBM ServeRAID Adapter> mem 0xf4000000--xf7ffffff irq 9 at device 3.0 
 on pci5
 ips0: failed to get configuration from device
 device_probe_and_attach: ips0 attach returned 6
 ..
 pci9: <PCI bus> in pcib9
 Memory modified after free 0xc18cd700(252)
 panic: Most recently used by devbuf
 
 Here's the trace:
 
 
 Debugger(c0502455,c05c50e0,c05193ad,c0b35ca4,100) at Debugger+0x54
 panic(c05193ad,c0500cf7,fc,c0c3aea0) at panic+0xcc
 mtrash_ctor(c18cd700,100,0,553,0) at mtrash_ctor+0x5d
 uma_zalloc_arg(c0c3aea0,0,101,c0327620,c0599b48) at uma_zalloc_arg+0x17f
 malloc(a8,c0556960,101,c052254c,c0b35d6c) at malloc+0xd4
 device_get_children(c433a380,c0b35d58,c0b35d5c,c0325c62,c18dd700) at 
 device_get_children+0x47
 isa_probe_children(c433a380,c051c4db,0,c0b35d98,c02e9925) at 
 isa_probe_children+0x2d
 configure(0,b32000,b32c00,b32000,0) at configure+0x4b
 mi_startup() at mi_startup+0xb5
 begin() at begin+0x2c
 
 
 This machine is the 235, as we had to install linux on the 345 to get it into 
 production. I'm not sure how long I can do testing with this machine.
 Also, if someone knows how to report these backtraces without having to type 
 them in I would be appriciate a heads up on it. Thanks.