From: Alois Fertl <alois_fertl@TalkNet.de>
To: "linuxppc-dev@lists.linuxppc.org" <linuxppc-dev@lists.linuxppc.org>
Subject: linux-2.2.2 kernel hangs
Date: Mon, 01 Mar 1999 07:08:53 +0000 [thread overview]
Message-ID: <36DA3D05.2E16F658@talknet.de> (raw)
On Saturday I managed to update my kernel sources to 2.2.2 from
vger/linux
at cvs.samba.org. There was some restructuring on samba and I had to
find
out how to update my Repository and Root CVS files.
This 2.2.2 version has severe problems on a Motorola RiscPC. Actually
the
kernel hangs within a short time if cpio'ing files from a NFS tree to
the
local scsi drive. It starts with a message about the nfs server not
responding and than endlessly repeats scsi timeouts. Due to my problems
with CVS I do not have any of the versions between 2.1.130 and 2.2.2.
The
2.1.130 version did not show the problem.
Is this a known problem.
Did anybody else experiance the same problem.
Here is a sample output:
nfs: server dino not responding, still trying
scsi : aborting command due to timeout : pid 3940, scsi0, channel 0, id
0, lun 0 0x0a 02 ff c0 80 00
ncr53c8xx_abort: pid=3940 serial_number=3947
serial_number_at_timeout=3947
scsi : aborting command due to timeout : pid 3941, scsi0, channel 0, id
0, lun 0 0x0a 03 00 5a 02 00
ncr53c8xx_abort: pid=3941 serial_number=3948
serial_number_at_timeout=3948
ncr53c810-0: abort ccb=c0195020 (cancel)
SCSI host 0 abort (pid 3941) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=3941 reset_flags=2 serial_number=3948
serial_number_at_timeout=3948
SCSI host 0 abort (pid 3941) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=3941 reset_flags=2 serial_number=3949
serial_number_at_timeout=3949
SCSI host 0 abort (pid 3941) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=3941 reset_flags=2 serial_number=3951
serial_number_at_timeout=3951
SCSI host 0 abort (pid 3941) timed out - resetting
SCSI bus is being reset for host 0 channel 0.
ncr53c8xx_reset: pid=3941 reset_flags=2 serial_number=3953
serial_number_at_timeout=3953
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next reply other threads:[~1999-03-01 7:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-01 7:08 Alois Fertl [this message]
1999-03-01 11:08 ` linux-2.2.2 kernel hangs VALETTE Eric
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36DA3D05.2E16F658@talknet.de \
--to=alois_fertl@talknet.de \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).