Date: Tue, 4 Nov 2003 11:33:02 -0600 From: Tillman Hodgson <tillman@seekingfire.com> To: current@freebsd.org Subject: [Tillman: Upgraded to latest -current today, boot hangs on "ata3: resetting devices"] Message-ID: <20031104113302.B6496@seekingfire.com>
next in thread | raw e-mail | index | archive | help
--gn1ylXQ+YRNuZICZ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
It occurs to me that this is likely related to the new interrupt code.
that tends to imply that the fix is "wait a few days and re-cvsup", but
I thought folks here would be interested in seeing Sparc64 feedback.
-T
--
[It] contains "vegetable stabilizer" which sounds ominous. How unstable
are vegetables?
- A.S.R. quote (Jeff Zahn)
--gn1ylXQ+YRNuZICZ
Content-Type: message/rfc822
Content-Disposition: inline
Return-Path: <owner-freebsd-sparc64@freebsd.org>
X-Original-To: tillman@seekingfire.com
Delivered-To: tillman@seekingfire.com
Received: from coyote.seekingfire.com (coyote.seekingfire.prv [192.168.23.2])
by mail.seekingfire.com (Postfix) with ESMTP id AD04725F
for <tillman@seekingfire.com>; Mon, 3 Nov 2003 22:52:05 -0600 (CST)
Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119])
hA44q5xm000810
for <tillman@seekingfire.com>; Mon, 3 Nov 2003 22:52:05 -0600 (CST)
(envelope-from owner-freebsd-sparc64@freebsd.org)
Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18])
by mx2.freebsd.org (Postfix) with ESMTP
id A821655822; Mon, 3 Nov 2003 20:51:56 -0800 (PST)
(envelope-from owner-freebsd-sparc64@freebsd.org)
Received: from hub.freebsd.org (localhost [127.0.0.1])
by hub.freebsd.org (Postfix) with ESMTP
id EE35716A4E3; Mon, 3 Nov 2003 20:51:55 -0800 (PST)
Delivered-To: freebsd-sparc64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
by hub.freebsd.org (Postfix) with ESMTP id B2FF916A4CE
for <sparc64@freebsd.org>; Mon, 3 Nov 2003 20:51:22 -0800 (PST)
Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212])
by mx1.FreeBSD.org (Postfix) with ESMTP id 45EA743FA3
for <sparc64@freebsd.org>; Mon, 3 Nov 2003 20:51:21 -0800 (PST)
(envelope-from tillman@seekingfire.com)
Received: from blues.seekingfire.prv (blues.seekingfire.prv [192.168.23.211])
by mail.seekingfire.com (Postfix) with ESMTP id 444F735B
for <sparc64@freebsd.org>; Mon, 3 Nov 2003 22:51:20 -0600 (CST)
Received: (from tillman@localhost)
by blues.seekingfire.prv (8.11.6/8.11.6) id hA44pK021428
for sparc64@freebsd.org; Mon, 3 Nov 2003 22:51:20 -0600
Date: Mon, 3 Nov 2003 22:51:20 -0600
From: Tillman Hodgson <tillman@seekingfire.com>
To: FreeBSD-Sparc64 <sparc64@freebsd.org>
Message-ID: <20031103225120.S6496@seekingfire.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5.1i
X-Urban-Legend: There is lots of hidden information in headers
Subject: Upgraded to latest -current today, boot hangs on "ata3: resetting
devices"
X-BeenThere: freebsd-sparc64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Sparc <freebsd-sparc64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
<mailto:freebsd-sparc64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-sparc64>;
List-Post: <mailto:freebsd-sparc64@freebsd.org>
List-Help: <mailto:freebsd-sparc64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64>,
<mailto:freebsd-sparc64-request@freebsd.org?subject=subscribe>
Sender: owner-freebsd-sparc64@freebsd.org
Errors-To: owner-freebsd-sparc64@freebsd.org
The serial console shows this:
atapci0: <CMD 646 WDMA2 controller> port 0xc00020-0xc0002f,0xc00018-0xc0001b,0xc00010-0xc00017,0xc00008-0xc0000b,0xc00000-0xc00007 at device 3.0 on pci1
atapci0: [MPSAFE]
ata2: at 0xc00000 on atapci0
ata2: [MPSAFE]
ata3: at 0xc00010 on atapci0
ata3: [MPSAFE]
pcib2: <APB PCI-PCI bridge> at device 1.0 on pci0
pci2: <OFW PCI bus> on pcib2
pcib3: <OFW PCI-PCI bridge> at device 3.0 on pci2
pci3: <OFW PCI bus> on pcib3
pci3: <bridge, PCI-unknown> at device 0.0 (no driver attached)
hme1: <Sun HME 10/100 Ethernet> mem 0x2800000-0x2807fff at device 0.1 on pci3
pcib3: slot 0 INTB is routed to irq 25
hme1: Ethernet address: 08:00:20:c6:7f:c7
miibus1: <MII bus> on hme1
ukphy0: <Generic IEEE 802.3u media interface> on miibus1
ukphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci3: <bridge, PCI-unknown> at device 1.0 (no driver attached)
hme2: <Sun HME 10/100 Ethernet> mem 0x4800000-0x4807fff at device 1.1 on pci3
pcib3: slot 1 INTB is routed to irq 26
hme2: Ethernet address: 08:00:20:c6:7f:c7
miibus2: <MII bus> on hme2
ukphy1: <Generic IEEE 802.3u media interface> on miibus2
ukphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci3: <bridge, PCI-unknown> at device 2.0 (no driver attached)
hme3: <Sun HME 10/100 Ethernet> mem 0x6800000-0x6807fff at device 2.1 on pci3
pcib3: slot 2 INTB is routed to irq 27
hme3: Ethernet address: 08:00:20:c6:7f:c7
miibus3: <MII bus> on hme3
ukphy2: <Generic IEEE 802.3u media interface> on miibus3
ukphy2: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
pci3: <bridge, PCI-unknown> at device 3.0 (no driver attached)
hme4: <Sun HME 10/100 Ethernet> mem 0x8800000-0x8807fff at device 3.1 on pci3
pcib3: slot 3 INTB is routed to irq 24
hme4: Ethernet address: 08:00:20:c6:7f:c7
miibus4: <MII bus> on hme4
ukphy3: <Generic IEEE 802.3u media interface> on miibus4
ukphy3: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Timecounters tick every 0.976 msec
IPsec: Initialized Security Association Processing.
IP Filter: v3.4.31 initialized. Default = pass all, Logging = enabled
ad0: WARNING - SETFEATURES recovered from missing interrupt
ad0: WARNING - SETFEATURES recovered from missing interrupt
ad0: WARNING - SET_MULTI recovered from missing interrupt
ad0: WARNING - SETFEATURES recovered from missing interrupt
GEOM: create disk ad0 dp=0xfffff8001087a6c0
ad0: 8223MB <ST38410A> [16708/16/63] at ata2-master WDMA2
acd0: WARNING - MODE_SENSE_BIG recovered from missing interrupt
ata3: resetting devices ..
It's an Ultra 5 with an IDE drive. I was previously running -current
from after the 09/23 entry in UPDATING. Entries since then don't show
anything particularly relevent. I ran cvsup before beginning the
compile about 8:00am CST.
Are there any known issues like this? Are there known solutions? Even a
"wait until foo is committed then re-cvsp" would be great to hear ;-)
I've tried "load /boot/kernel.old/kernel" from the boot loader to
recover at least a booting system. This worked, though naturally my
userland no longer matches my kernel. Should I be able to re-install a
new kernel & userland from this point safely?
-T
--
"I'm getting a new desk soon! Desk goes up. Desk goes down. Desk goes
up. Desk goes down. Desk goes up. Desk goes down. Desk goes up. Desk
goes down. Desk goes up. Desk goes down. Desk goes up. Desk goes
down. Lunch. Productivity is in the eyes of the beholder."
- A.S.R. quote (Lars Balker Rasmussen)
_______________________________________________
freebsd-sparc64@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-sparc64
To unsubscribe, send any mail to "freebsd-sparc64-unsubscribe@freebsd.org"
--gn1ylXQ+YRNuZICZ--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031104113302.B6496>