Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 10 Nov 1996 13:00:47 +0100 (MET)
From:      Andreas Klemm <andreas@klemm.gtn.com>
To:        FreeBSD-gnats@freefall.freebsd.org, freebsd-bugs@freefall.freebsd.org
Cc:        gibbs@freebsd.org
Subject:   Re: kern/1989: dump problems, if tagged command queueing is enabled
Message-ID:  <Pine.BSF.3.95.961110124759.237A-100000@klemm.gtn.com>
In-Reply-To: <199611101010.CAA27861@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 10 Nov 1996 FreeBSD-gnats@freefall.freebsd.org wrote:

> Thank you very much for your problem report.
> It has the internal identification `kern/1989'.
> The individual assigned to look at your
> bug is: freebsd-bugs. 
> 
> >Category:       kern
> >Responsible:    freebsd-bugs
> >Synopsis:       dump(8) fails to dump if tagged command queuing is enabled
> >Arrival-Date:   Sun Nov 10 02:10:01 PST 1996

Another experiences ...
Made a brand new kernel using the same kernel konfig file, because
Justin suggested so ... to make sure, that his last changes are in.

I made a backup of /bin using tar. No problem.

I tried to make a backup of / and /var usging dump...
The first time I tried that caused only the messages, that I already
wrote in my initial bug report.

Then I dumped a minute after that agin / and /var.
There were many many messages, that flushed over the screen, so 
I was only able to write down some, when the flushing finished...

Bad news, with the default syslog.conf settings (I made sure to use
the newest -current version), completely nothing was logged in the
/var/log/messages file. Could someone please tell me better settings,
so that I can send you a more complete list of what is going on ...
Or do you think, that perhaps syslogd was unable to write to the disk,
what could also be possible ...

Before that messages below, there were additionally some messages
indicating, that the scsi bus was reconfigured to use asynchronous
data transmission.

sd0(ahc0:0:0) timed out in message in phase SCSISIGI == 0x86
kernel: Ordered Tag queued
sd0(ahc0:0:0) timed out in message in phase SCSISIGI == 0x86
st0(ahc0:4:0) abort message in message buffer
st0(ahc0:4:0) timed out in message in phase SCSISIGI == 0x96
Ordered Tag sent
ahc0: Issued Channel A Bus Reset, 3SCB's aborted.
...
-----
Ordered Tag set
panic: ahc0: Timed out command times out again
Fatal trap 12: page fault while in kernel mode
...
----
dumping to dev 20409, offset 65536
ahc0: board is not responding
cmd fail
device bad
----
Then the machine is rebooted. I didn't power down the machine
and noticed, that the first disk with SCSI ID 0 wasn't recognized
by the 2940 host adapter. Only the other 3 scsi devices
(disk 1 on ID1, Tape on ID4 and CD-ROM on ID 6).

Please tell me, what I can do additionally, to help you to get the
bug fixed.

	Andreas ///

--
andreas@klemm.gtn.com         /\/\___      Wiechers & Partner Datentechnik GmbH
   Andreas Klemm          ___/\/\/         Support Unix -- andreas.klemm@wup.de
pgp p-key  http://www-swiss.ai.mit.edu/~bal/pks-toplev.html  >>> powered by <<<
ftp://sunsite.unc.edu/pub/Linux/system/Printing/aps-491.tgz  >>>    FreeBSD <<<




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.961110124759.237A-100000>