From owner-freebsd-current@FreeBSD.ORG Thu May 6 05:15:06 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CFAB816A4CF for ; Thu, 6 May 2004 05:15:06 -0700 (PDT) Received: from spider.deepcore.dk (cpe.atm2-0-53484.0x50a6c9a6.abnxx9.customer.tele.dk [80.166.201.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 330D643D5E for ; Thu, 6 May 2004 05:15:05 -0700 (PDT) (envelope-from sos@DeepCore.dk) Received: from DeepCore.dk (sos.deepcore.dk [194.192.25.130]) by spider.deepcore.dk (8.12.11/8.12.10) with ESMTP id i46CEvJo059517; Thu, 6 May 2004 14:15:02 +0200 (CEST) (envelope-from sos@DeepCore.dk) Message-ID: <409A2C41.8000103@DeepCore.dk> Date: Thu, 06 May 2004 14:14:57 +0200 From: =?UTF-8?B?U8O4cmVuIFNjaG1pZHQ=?= User-Agent: Mozilla Thunderbird 0.5 (X11/20040329) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mark Santcroos References: <20040505195425.GA2559@laptop.6bone.nl> <409948A7.1040100@DeepCore.dk> <20040506212202.O19882@gamplex.bde.org> <20040506120541.GA1131@laptop.6bone.nl> In-Reply-To: <20040506120541.GA1131@laptop.6bone.nl> Content-Type: multipart/mixed; boundary="------------050308020105060204090500" X-mail-scanned: by DeepCore Virus & Spam killer v1.4 cc: current@FreeBSD.org Subject: Re: ATA_FLUSHCACHE failing X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 May 2004 12:15:06 -0000 This is a multi-part message in MIME format. --------------050308020105060204090500 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Mark Santcroos wrote: > On Thu, May 06, 2004 at 09:36:31PM +1000, Bruce Evans wrote: > >>Panic dumps cannot use either device interrupts or timeouts, not to >>mention normal locks, since panics may occur in almost any context; >>in particular they may occur with all interrupts masked and important >>locks in a bad state. Immediate mode must be used, but it doesn't >>seem to be, and a comment says that it is only used for other things: > > > My eye felt on the same code and comments! > > But if this is indeed the problem, why isn't everyone experiencing this > issue? Good question, maybe interrupts are not treated equally on all platforms, I just tested here on a couble and they work just fine hmm.. Anhow try this patch: -- -Søren --------------050308020105060204090500 Content-Type: text/plain; name="imm" Content-Transfer-Encoding: base64 Content-Disposition: inline; filename="imm" SW5kZXg6IGF0YS1kaXNrLmMKPT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09 PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQpSQ1MgZmlsZTogL2hvbWUvbmN2cy9z cmMvc3lzL2Rldi9hdGEvYXRhLWRpc2suYyx2CnJldHJpZXZpbmcgcmV2aXNpb24gMS4xNzIK ZGlmZiAtdSAtcjEuMTcyIGF0YS1kaXNrLmMKLS0tIGF0YS1kaXNrLmMJMTMgQXByIDIwMDQg MDk6NDQ6MjAgLTAwMDAJMS4xNzIKKysrIGF0YS1kaXNrLmMJNiBNYXkgMjAwNCAxMjowODoz MSAtMDAwMApAQCAtMzM1LDYgKzMzNSw3IEBACiAgICAgaWYgKCFhZHApCiAJcmV0dXJuIEVO WElPOwogCisgICAgYWRwLT5kZXZpY2UtPmNoYW5uZWwtPmZsYWdzIHw9IEFUQV9JTU1FRElB VEVfTU9ERTsKICAgICBiemVybygmcmVxdWVzdCwgc2l6ZW9mKHN0cnVjdCBhdGFfcmVxdWVz dCkpOwogICAgIHJlcXVlc3QuZGV2aWNlID0gYWRwLT5kZXZpY2U7CiAKQEAgLTM1Miw3ICsz NTMsNyBAQAogICAgIH0KICAgICBlbHNlIHsKIAlyZXF1ZXN0LnUuYXRhLmNvbW1hbmQgPSBB VEFfRkxVU0hDQUNIRTsKLQlyZXF1ZXN0LmZsYWdzID0gQVRBX1JfQ09OVFJPTDsKKwlyZXF1 ZXN0LmZsYWdzID0gKEFUQV9SX0NPTlRST0wgfCBBVEFfUl9JTU1FRElBVEUpOwogICAgIH0K IAogICAgIGlmIChyZXF1ZXN0LmRldmljZS0+Y2hhbm5lbC0+aHcudHJhbnNhY3Rpb24oJnJl cXVlc3QpID09IEFUQV9PUF9DT05USU5VRVMpIHsK --------------050308020105060204090500--