Re: Panic #3 (ffs) (MegaRAID)
At 08:30 PM 2/23/00 +0100, Karsten W. Rohrbach wrote: which megaraid adapter do you use in this box (hw, fw ver, bios ver, cntl-m ver)... i've seen those panics on our old news box when there where errors on the scsi busses which did not get detected properly. mainly termination issues *sigh* I dont think its necessarily a termination issue. I have swapped the exact same chain onto a Mylex DAC960 and can pound the box without issue. I have a nasty feeling my 466 might not like my MB chipset. I am using a 466 PERC2/SC on BX chipset ECS MB and its throwing all sorts of fits. When I used a 428 on another box (a plain old Pentium), I didnt have nearly this many problems. Soon as my co-worker is finished with the older Pentium, I can test this theory to see if this is the case. Looking at the release notes for the BIOS revs at AMI, it seems older BIOS revs might have problems with newer MBs From ftp://ftp.megatrends.com/MegaRAID/drivers/466/readme-gh6d.txt Changes in this release: --- 1. CTRL-M is not invoked until after the system BIOS is completed on newer systems that support PMM (POST Memory Management). The system would hang at different places in CTRL-M on these systems prior to these changes. Until I flashed it to this new rev, I was seeing this behaviour. Just to reiterate; I can reliably hang the 466 running with this firmware within a few minutes under the 'amr' driver, while the Dell 3.00 firmware doesn't demonstrate the config-time hangs on any system I've run it on and is also not susceptible to the hang problems. I've been a little distracted with various Mylex-related issues for a little bit now, and am still waiting for some response from AMI before returning to work on these problems. I'm also in need of a more or less permanent loan of a 434 or 438 (preferably) controller as all I have right now are 418/428/466 and Karsten's been reporting issues with all of the 438's firmware. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Panic #3 (ffs)
*sigh*
I think I am going to give up my job and become a buddhist monk...
start = 0, len = 2646, fs = /news
panic: ffs_alloccg: map corrupted
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.372
db trace
Debugger(c01e7ee3) at Debugger+0x35
panic(c01f28bf,c01f28a0,0,a56,c1d0d8d4) at panic+0x70
ffs_mapsearch(c1d0d800,ccd49000,5d2a8,1,b) at ffs_mapsearch+0x143
ffs_alloccg(c1da7700,b,5d2a8,400) at ffs_alloccg+0x21a
ffs_hashalloc(c1da7700,b,5d2a8,400,c0194cb8) at ffs_hashalloc+0x23
ffs_alloc(c1da7700,b,5d2a8,400,c1d38280) at ffs_alloc+0xad
ffs_balloc(d8a1ce68,d8a4c200,c1d6a180,3,d8b74ba0) at ffs_balloc+0x456
ffs_write(d8a1cea0,d6299a80,4c,c1d6a180,c0201d00) at ffs_write+0x319
vn_write(c1d6a180,d8a1ceec,c1d38280,0,d6299a80) at vn_write+0xda
dofilewrite(d6299a80,c1d6a180,18,280c4000,4c) at dofilewrite+0x91
write(d6299a80,d8a1cf80,280ad140,280ad140,280c404d) at write+0x33
syscall(280c002f,280a002f,bfbf002f,280c404d,280ad140) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic #3 (ffs)
which megaraid adapter do you use in this box (hw, fw ver, bios ver,
cntl-m ver)...
i've seen those panics on our old news box when there where errors on
the scsi busses which did not get detected properly. mainly termination
issues *sigh*
/k
Jeroen Ruigrok van der Werven([EMAIL PROTECTED])@Wed, Feb 23, 2000 at 03:36:29PM +0100:
*sigh*
I think I am going to give up my job and become a buddhist monk...
start = 0, len = 2646, fs = /news
panic: ffs_alloccg: map corrupted
Debugger("panic")
Stopped at Debugger+0x35: movb$0,in_Debugger.372
db trace
Debugger(c01e7ee3) at Debugger+0x35
panic(c01f28bf,c01f28a0,0,a56,c1d0d8d4) at panic+0x70
ffs_mapsearch(c1d0d800,ccd49000,5d2a8,1,b) at ffs_mapsearch+0x143
ffs_alloccg(c1da7700,b,5d2a8,400) at ffs_alloccg+0x21a
ffs_hashalloc(c1da7700,b,5d2a8,400,c0194cb8) at ffs_hashalloc+0x23
ffs_alloc(c1da7700,b,5d2a8,400,c1d38280) at ffs_alloc+0xad
ffs_balloc(d8a1ce68,d8a4c200,c1d6a180,3,d8b74ba0) at ffs_balloc+0x456
ffs_write(d8a1cea0,d6299a80,4c,c1d6a180,c0201d00) at ffs_write+0x319
vn_write(c1d6a180,d8a1ceec,c1d38280,0,d6299a80) at vn_write+0xda
dofilewrite(d6299a80,c1d6a180,18,280c4000,4c) at dofilewrite+0x91
write(d6299a80,d8a1cf80,280ad140,280ad140,280c404d) at write+0x33
syscall(280c002f,280a002f,bfbf002f,280c404d,280ad140) at syscall+0x176
Xint0x80_syscall() at Xint0x80_syscall+0x26
--
Jeroen Ruigrok van der Werven Network- and systemadministrator
[EMAIL PROTECTED] bART Internet Services /
BSD: Technical excellence at its best VIA NET.WORKS Netherlands
Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-fs" in the body of the message
--
Hugh Hefner is a virgin.
http://www.webmonster.de http://www.apache.de http://www.splatterworld.de
(NIC-HDL KR433/KR11-RIPE)
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: Panic #3 (ffs)
-On [2223 20:35], Karsten W. Rohrbach ([EMAIL PROTECTED]) wrote: which megaraid adapter do you use in this box (hw, fw ver, bios ver, cntl-m ver)... i've seen those panics on our old news box when there where errors on the scsi busses which did not get detected properly. mainly termination issues *sigh* amr0: AMI MegaRAID mem 0xe300-0xe300 irq 10 at device 10.1 on pci0 amr0: firmware EH61 bios 1.31 16MB memory amrd0: MegaRAID logical drive on amr0 amrd0: 35040MB (71761920 sectors) RAID 0 (optimal) And I receive the panics on BOTH the array and the normal da disks. I know the termination is correct. -- Jeroen Ruigrok van der Werven Network- and systemadministrator [EMAIL PROTECTED] bART Internet Services / BSD: Technical excellence at its best VIA NET.WORKS Netherlands Tel: +31 - (0) 10 - 240 39 70 http://www.bart.nl To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Panic #3 (ffs) (MegaRAID)
At 08:30 PM 2/23/00 +0100, Karsten W. Rohrbach wrote: which megaraid adapter do you use in this box (hw, fw ver, bios ver, cntl-m ver)... i've seen those panics on our old news box when there where errors on the scsi busses which did not get detected properly. mainly termination issues *sigh* I dont think its necessarily a termination issue. I have swapped the exact same chain onto a Mylex DAC960 and can pound the box without issue. I have a nasty feeling my 466 might not like my MB chipset. I am using a 466 PERC2/SC on BX chipset ECS MB and its throwing all sorts of fits. When I used a 428 on another box (a plain old Pentium), I didnt have nearly this many problems. Soon as my co-worker is finished with the older Pentium, I can test this theory to see if this is the case. Looking at the release notes for the BIOS revs at AMI, it seems older BIOS revs might have problems with newer MBs From ftp://ftp.megatrends.com/MegaRAID/drivers/466/readme-gh6d.txt Changes in this release: --- 1. CTRL-M is not invoked until after the system BIOS is completed on newer systems that support PMM (POST Memory Management). The system would hang at different places in CTRL-M on these systems prior to these changes. Until I flashed it to this new rev, I was seeing this behaviour. ---Mike Mike Tancsa, tel +1 519 651 3400 Network Administrator,[EMAIL PROTECTED] Sentex Communications www.sentex.net Cambridge, Ontario Canada To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
