From owner-freebsd-bugs@FreeBSD.ORG Wed Dec 3 04:50:28 2003 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E66416A4CE for ; Wed, 3 Dec 2003 04:50:28 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5B9B543FDF for ; Wed, 3 Dec 2003 04:50:27 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.9/8.12.9) with ESMTP id hB3CoQFY061158 for ; Wed, 3 Dec 2003 04:50:26 -0800 (PST) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.9/8.12.9/Submit) id hB3CoQOA061157; Wed, 3 Dec 2003 04:50:26 -0800 (PST) (envelope-from gnats) Date: Wed, 3 Dec 2003 04:50:26 -0800 (PST) Message-Id: <200312031250.hB3CoQOA061157@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Daniel Lang Subject: Re: kern/59260: Panic by integer divide fault in Thinkpad A31p / IRQ Problem? X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Daniel Lang List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 Dec 2003 12:50:28 -0000 The following reply was made to PR kern/59260; it has been noted by GNATS. From: Daniel Lang To: freebsd-gnats-submit@FreeBSD.org Cc: imp@freebsd.org, jhb@freebsd.org Subject: Re: kern/59260: Panic by integer divide fault in Thinkpad A31p / IRQ Problem? Date: Wed, 3 Dec 2003 13:48:35 +0100 Dear Warner, Dear John, I believe the problem is solved now. Although the live debugging did not turn up anything useful to me, meanwhile, I stumbled upon something else: In a newsarticle hw.pci.allow_unsupported_io_range was mentioned, together with a (different) problem on a Thinkpad (different model). I set this sysctl to 1 in /boot/loader.conf and now, it appears the system works like charm now. I'm not sure how to rate this. I guess it means quirky hardware, that is out of spec, but there exists a workaround. I'm happy that my system seems to work now, but I guess the panics should be prevented. Maybe the quirky hardware can be detected, a big warning messages issued during boot, and the workaround activated? Well, I guess that would be difficult if not impossible, otherwise it would have been done already. Please submit this workaround to the PR (my last email to you and freebsd-gnats-submit@ was somehow not included into the audit trail). Feel free to close it then. Thanks again for your explanations. Best regards, Daniel -- IRCnet: Mr-Spock - Truth lies in the eye of the beholder - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/