From owner-freebsd-current Mon Nov 25 11:41:40 2002 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 6952137B404 for ; Mon, 25 Nov 2002 11:41:36 -0800 (PST) Received: from angelica.unixdaemons.com (angelica.unixdaemons.com [209.148.64.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5516543EA9 for ; Mon, 25 Nov 2002 11:41:35 -0800 (PST) (envelope-from hiten@angelica.unixdaemons.com) Received: from angelica.unixdaemons.com (hiten@localhost.unixdaemons.com [127.0.0.1]) by angelica.unixdaemons.com (8.12.5/8.12.1) with ESMTP id gAPJfMSu019625; Mon, 25 Nov 2002 14:41:22 -0500 (EST) X-Authentication-Warning: angelica.unixdaemons.com: Host hiten@localhost.unixdaemons.com [127.0.0.1] claimed to be angelica.unixdaemons.com Received: (from hiten@localhost) by angelica.unixdaemons.com (8.12.5/8.12.1/Submit) id gAPJfMIO019624; Mon, 25 Nov 2002 14:41:22 -0500 (EST) (envelope-from hiten) Date: Mon, 25 Nov 2002 14:41:22 -0500 From: Hiten Pandya To: Philip Paeps Cc: current@FreeBSD.ORG Subject: Re: I'm impressed, but ... Message-ID: <20021125194122.GA17986@angelica.unixdaemons.com> References: <20021125004934.GA604@juno.home.paeps.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021125004934.GA604@juno.home.paeps.cx> User-Agent: Mutt/1.4i X-Operating-System: FreeBSD i386 X-Public-Key: http://www.pittgoth.com/~hiten/pubkey.asc X-URL: http://www.unixdaemons.com/~hiten X-PGP: http://pgp.mit.edu:11371/pks/lookup?search=Hiten+Pandya&op=index Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Mon, Nov 25, 2002 at 01:49:34AM +0100, Philip Paeps wrote the words in effect of: > | [...] > | vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 > | unknown: can't assign resources (port) > | unknown: can't assign resources (irq) > | unknown: can't assign resources (port) > | unknown: can't assign resources (port) > | unknown: can't assign resources (port) > | unknown: can't assign resources (port) > | unknown: can't assign resources (port) > | Timecounters tick every 10.000 msec > | ahc0: Someone reset channel A > | [...] > > All my hardware (the stuff I've tested anyway) appears to work. Any idea > which device is being unknown, or how I could find out? Hi there. Can you try changing the hardware tunable, hw.pci.allow_unsupported_io_range, to the value of 1 in your loader.conf. I think this should do it. You can then check this value after you booted by `sysctl hw.pci`. > 2. This one's the most irritating. I use Mutt as my mailclient using > Maildirs for storage. It occasionally happens that Mutt just 'hangs' > reading a directory, and there's no way for me to kill it. Ps axl shows > it as being in state Ds or Ds+ and blocked by ufs. Hmm, this also happens in the case of dd(1). If you invoke dd(1) as: # dd if=/dev/zero of=/tmp/somefile As you can see, it gets stuck when not provided with a count variable. It hangs in the `ufs' state. I am currently looking into this. I am thinking, this is because a 0 byte file is found disturbing. > 3. I can't seem to restart my machine properly. This might be related to the > above, as the only reason for me to restart the machine is the fact that I > can't kill Mutt however much I try, and really would like to read my mail. > It will sync disks and say 'done', but then it just sits there doing > nothing until I flip the power-switch. Exactly the same thing happens when any process hangs in the `ufs' state. It syncs the disks, when you `shutdown` or `fastboot`. This indicates a bug in the kernel. > As I said, I'm happy to help analyse and debug these issues, but I don't know > where to look :-) Can you try using `ktrace`, like this: root# ktrace mutt (or the command which makes it hang) root# kdump -f ktrace.out (this is the output needed) Cheers. -- Hiten Pandya (hiten@unixdaemons.com, hiten@uk.FreeBSD.org) http://www.unixdaemons.com/~hiten/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message