From owner-freebsd-hardware@FreeBSD.ORG Fri Feb 11 11:58:50 2005 Return-Path: Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 052AF16A4CE for ; Fri, 11 Feb 2005 11:58:50 +0000 (GMT) Received: from reed.uran.net.ua (reed.uran.net.ua [212.111.192.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E65B43D46 for ; Fri, 11 Feb 2005 11:58:45 +0000 (GMT) (envelope-from edd@reed.uran.net.ua) Received: by reed.uran.net.ua (Postfix, from userid 1000) id 49C84BA26; Fri, 11 Feb 2005 14:04:43 +0200 (EET) Date: Fri, 11 Feb 2005 14:04:43 +0200 From: Edward Melnik To: freebsd-hardware@freebsd.org Message-ID: <20050211120443.GB14427@reed.uran.net.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=koi8-u Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Subject: [q] scsi disks or what the problem? X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Feb 2005 11:58:50 -0000 Hello! My server paniced: panic: ufs_dirbad: bad dir cpuid = 0; boot() called on cpu#0 syncing disks, buffers remaining... panic: breemfree: removing a buffer not on a queue cpuid = 0l boot() called on cpu#0 Uptime: 46s amr0: flushing cache... kernel trap 12 with interrupts disabled Fatal trap 12: page fault while in kernel mode cpuid = 1; apic id = 01 fault virtual address = 0x24 fault code = supervisor read, page not present instruction pointer = 0x8:0xc05bbf8e stack pointer = 0x10:0xe081cc64 frame pointer = 0x10:0xe081cc88 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = resume, IOPL = 0 current process = 59 (irq48: amr0) trap number = 12 spin lock shed lock held by 0xc521ea00 for > 5 seconds panic: spin lock held too long cpuid = 0; This caused after power on/off for maintenance work with server. And trying after power on rebuiling the system via make buildworld, make ... . System paniced after 3-7min on this procedure. Before this problem server working a 1,5 year without any problem. Now, paniced on startup. System: 5.2.1-p11, 1xXeon 2.4, amr0 - RAID 1 on two 36GB SCSI disks (IBM). On startup - RAID1 (optimal). Controller - LSI Megalogic 320-1. Need more info ? Please write me, but server is down :( Anybody help me? This is a problem with hdd, mb, ram or system? -- Edward Melnik