Date: Sun, 6 Oct 2002 19:52:40 -0400 From: Carl Schmidt <carl@slackerbsd.org> To: Seth Hieronymus <sethh@principia.edu> Cc: freebsd-current@freebsd.org Subject: Re: My problems with GEOM Message-ID: <20021006235240.GB62367@carbon.slackerbsd.org> In-Reply-To: <OE35VSSFcl3impgeByb00019a07@hotmail.com> References: <OE35VSSFcl3impgeByb00019a07@hotmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Oct 06, 2002 at 05:08:00PM -0600, Seth Hieronymus wrote:
> Hello,
>
> After recompiling a kernel after the GEOM transition, my boot gets as
> far as:
>
> Initializing GEOMetry subsystem
> ad0: 28629MB <ST330630A> [58168/16/63] at ata0-master UDMA33
> acd0: CDROM <Lite-On LTN483S 48x Max> at ata1-master PIO4
> afd0: 239MB <IOMEGA ZIP 250 ATAPI> [239/64/32] at ata1-slave PIO3
> Mounting root from ufs:/dev/ad0s1a
>
> and hangs -- only a physical reset works. However, breaking into the
> debugger, and running a trace, I get (hand-copied):
>
> Debugger("manual escape to debugger")
> Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0
> db> trace
> Debugger(c0331a32,4,1,0,1) at Debugger+0x54
> scgetc(c03cc1e0,2,c031a8f5,2fd,c1876b40) at scgetc+0x445
> sckbdevent(c03a6ee0,0,c03cc1e0,c034b1c0,8) at sckbdevent+0x1d0
> atkbd_intr(c03a6ee0,0,c8793d0c,c01a25c2,c03a6ee0) at atkbd_intr+0x2c
> atkbd_isa_intr(c03a6ee0,0,c0317bac,215,c0bbf370) at atkbd_isa_intr+0x21
> ithread_loop(c185fe00,c8793d48,c031790b,34d,7641000a) at
> ithread_loop+0x182
> fork_exit(c01a2440,c185fe00,c8793d48) at fork_exit+0xa5
> fork_trampoline() at fork_trampoline+0x1a
> --- trap 0x1, eip = 0, esp = 0xc8793d7c, ebp = 0 ---
>
> Am I doing something wrong here? Thanks for any help. My pre-GEOM
> dmesg, and kernel config follow. A kernel and world from the day before
> the GEOM switch works fine.
I also have the aforementioned problem. I had this problem several
months before GEOM was enabled so I can not vouch for it being GEOM-
related. Any time I trace after this apparent hang I get a mostly
identical trace as you have shown. I have no idea why it happens. I
only know that it happens only with FreeBSD on my laptop. No other
operating system I have tried on it has this problem. Unfortunately I
cannot be more verbose (that I am aware of) than the trace. I have
been unsuccessful at forcing a core dump, and I do not know why.
I am at the point where if someone offers an idea to get more
information I could possily be more useful. I will try adding printf's
where I think would be useful but this is a needle in a haystack issue
for me since I am not 100% aware of the internals.
--
Carl Schmidt
[Random Quote]
Be different: conform.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20021006235240.GB62367>