From owner-freebsd-current  Thu Nov 18 23:56:26 1999
Delivered-To: freebsd-current@freebsd.org
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by hub.freebsd.org (Postfix) with ESMTP id 5931B14E54
	for <current@FreeBSD.ORG>; Thu, 18 Nov 1999 23:56:18 -0800 (PST)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id IAA03179;
	Fri, 19 Nov 1999 08:56:04 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: Taavi Talvik <taavi@uninet.ee>
Cc: current@FreeBSD.ORG
Subject: Re: Current hangs when dump is run? 
In-reply-to: Your message of "Fri, 19 Nov 1999 09:32:45 +0200."
             <Pine.BSF.3.95.991119091824.10715A-100000@ns.uninet.ee> 
Date: Fri, 19 Nov 1999 08:56:03 +0100
Message-ID: <3177.942998163@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


If you're using the ata driver, please remove the ad_sleep() call
at the bottom of the adopen() in ata-disk.c and see if that
helps you.

Poul-Henning

In message <Pine.BSF.3.95.991119091824.10715A-100000@ns.uninet.ee>, Taavi Talvi
k writes:
>
>Current seems to hangs, when amanda tries to run dump.
>This appeared approximately 2 weeks ago, and is present in
>yesterdays current also.
>
>#0  0xc013daa4 in boot ()
>(kgdb) bt
>#0  0xc013daa4 in boot ()
>#1  0xc013de41 in panic ()
>#2  0xc011d739 in db_panic ()
>#3  0xc011d6d9 in db_command ()
>#4  0xc011d79e in db_command_loop ()
>#5  0xc011f82f in db_trap ()
>#6  0xc02011fb in kdb_trap ()
>#7  0xc020f444 in trap ()
>#8  0xc0201457 in Debugger ()
>#9  0xc01fcb12 in scgetc ()
>#10 0xc01f827d in sckbdevent ()
>#11 0xc01f1a9b in atkbd_intr ()
>#12 0xc021cd84 in atkbd_isa_intr ()
>#13 0xc0202fe2 in vec1 ()
>#14 0xc0140a55 in tsleep ()
>#15 0xc0146889 in diskopen ()
>#16 0xc0170251 in spec_open ()
>#17 0xc017014d in spec_vnoperate ()
>#18 0xc01bb579 in ufs_vnoperatespec ()
>#19 0xc016a57c in vn_open ()
>#20 0xc01669dd in open ()
>#21 0xc020fd12 in syscall ()
>#22 0xc0201b06 in Xint0x80_syscall ()
>#23 0x804b91a in ?? ()
>#24 0x804b6b3 in ?? ()
>#25 0x80491c0 in ?? ()
>
>and ps shows
>[127:0] taavi@tt:/var/crash #ps -raxwu -M vmcore.4 -N kernel.4
>USER     PID %CPU %MEM   VSZ  RSS  TT  STAT STARTED      TIME COMMAND
>amanda   380 99.0  0.0   628    0  ??  R     1Jan70   0:00.00  (dump)
>root       1  0.0  0.0   516    0  ??  ILs   1Jan70   0:00.02 /sbin/init
>--
>root       2  0.0  0.0     0    0  ??  RL    1Jan70   0:00.01
>(pagedaemon)
>root       3  0.0  0.0     0    0  ??  DL    1Jan70   0:00.00  (vmdaemon)
>root       4  0.0  0.0     0    0  ??  RL    1Jan70   0:00.01  (bufdaemon)
>root       5  0.0  0.0     0    0  ??  RL    1Jan70   0:00.28  (syncer)
>.....
>
>I have kernel and core saved, if someone needs them.
>
>best regards,
>taavi
>-----------------------------------------------------------
>Taavi Talvik                    | Internet: taavi@uninet.ee 
>Unineti Andmeside AS            | phone: +372 6405150
>Ravala pst. 10                  | fax: +372 6405151
>Tallinn 10143, Estonia          |
>
>
>
>To Unsubscribe: send mail to majordomo@FreeBSD.org
>with "unsubscribe freebsd-current" in the body of the message
>

--
Poul-Henning Kamp             FreeBSD coreteam member
phk@FreeBSD.ORG               "Real hackers run -current on their laptop."
FreeBSD -- It will take a long time before progress goes too far!


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message