From jens@ptchgate.rz.tu-bs.de  Sun Apr  6 18:59:06 2003
Return-Path: <jens@ptchgate.rz.tu-bs.de>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 65A1837B401
	for <FreeBSD-gnats-submit@freebsd.org>; Sun,  6 Apr 2003 18:59:06 -0700 (PDT)
Received: from ptchgate.rz.tu-bs.de (ptchgate.rz.tu-bs.de [134.169.246.49])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 7D33943F85
	for <FreeBSD-gnats-submit@freebsd.org>; Sun,  6 Apr 2003 18:59:05 -0700 (PDT)
	(envelope-from jens@ptchgate.rz.tu-bs.de)
Received: from ptchgate.rz.tu-bs.de (localhost [127.0.0.1])
	by ptchgate.rz.tu-bs.de (8.12.6p2/8.12.6) with ESMTP id h371xHBg000757
	for <FreeBSD-gnats-submit@freebsd.org>; Mon, 7 Apr 2003 03:59:17 +0200 (CEST)
	(envelope-from jens@ptchgate.rz.tu-bs.de)
Received: (from root@localhost)
	by ptchgate.rz.tu-bs.de (8.12.6p2/8.12.6/Submit) id h371xHKt000756;
	Mon, 7 Apr 2003 03:59:17 +0200 (CEST)
Message-Id: <200304070159.h371xHKt000756@ptchgate.rz.tu-bs.de>
Date: Mon, 7 Apr 2003 03:59:17 +0200 (CEST)
From: j.roeder@tu-bs.de
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: reboot causes SRM console to loop endless error and needs to be restetted hard 
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         50659
>Category:       alpha
>Synopsis:       reboot causes SRM console to loop endless error and needs to be restetted hard
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-alpha
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Apr 06 19:00:32 PDT 2003
>Closed-Date:    Wed May 14 02:14:25 PDT 2003
>Last-Modified:  Wed May 14 02:14:25 PDT 2003
>Originator:     jens
>Release:        FreeBSD 5.0-RELEASE-p7 alpha
>Organization:
TU-Braunschweig 
>Environment:
System: FreeBSD ptchgate.rz.tu-bs.de 5.0-RELEASE-p7 FreeBSD 5.0-RELEASE-p7 #1: Mon Mar 31 02:29:29 CEST 2003 root@ptchgate.rz.tu-bs.de:/home/bsd/src/sys/alpha/compile/FIREWALL alpha


	
>Description:
	When rebooting the kernel on alphastation 500 the kernel sends probably a wrong message to the 
	SRM console and the console prints out endless lines of:

TU PCI BUSS Error; CSR5 ffffffff 

	The only way is to reset the entire box  the hard way. The error isn't that nice, as the machine would not reboot without manual work after a kernel panic.



>How-To-Repeat:

	simply reboot

	
>Fix:
no idea due to my limited knowledge
	


>Release-Note:
>Audit-Trail:

From: Wilko Bulte <wkb@freebie.xs4all.nl>
To: j.roeder@tu-bs.de
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: alpha/50659: reboot causes SRM console to loop endless error and needs to be restetted hard
Date: Mon, 7 Apr 2003 11:46:49 +0200

 On Mon, Apr 07, 2003 at 03:59:17AM +0200, j.roeder@tu-bs.de wrote:
 
 It would be interesting to know what SRM version you running. I have
 not seen this on my AS500/266
 
 Wilko
 
 
 > >Number:         50659
 > >Category:       alpha
 > >Synopsis:       reboot causes SRM console to loop endless error and needs to be restetted hard
 > >Confidential:   no
 > >Severity:       serious
 > >Priority:       medium
 > >Responsible:    freebsd-alpha
 > >State:          open
 > >Quarter:        
 > >Keywords:       
 > >Date-Required:
 > >Class:          sw-bug
 > >Submitter-Id:   current-users
 > >Arrival-Date:   Sun Apr 06 19:00:32 PDT 2003
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     jens
 > >Release:        FreeBSD 5.0-RELEASE-p7 alpha
 > >Organization:
 > TU-Braunschweig 
 > >Environment:
 > System: FreeBSD ptchgate.rz.tu-bs.de 5.0-RELEASE-p7 FreeBSD 5.0-RELEASE-p7 #1: Mon Mar 31 02:29:29 CEST 2003 root@ptchgate.rz.tu-bs.de:/home/bsd/src/sys/alpha/compile/FIREWALL alpha
 > 
 > 
 > 	
 > >Description:
 > 	When rebooting the kernel on alphastation 500 the kernel sends probably a wrong message to the 
 > 	SRM console and the console prints out endless lines of:
 > 
 > TU PCI BUSS Error; CSR5 ffffffff 
 > 
 > 	The only way is to reset the entire box  the hard way. The error isn't that nice, as the machine would not reboot without manual work after a kernel panic.
 > 
 > 
 > 
 > >How-To-Repeat:
 > 
 > 	simply reboot
 > 
 > 	
 > >Fix:
 > no idea due to my limited knowledge
 > 	
 > 
 > 
 > >Release-Note:
 > >Audit-Trail:
 > >Unformatted:
 > _______________________________________________
 > freebsd-alpha@freebsd.org mailing list
 > http://lists.freebsd.org/mailman/listinfo/freebsd-alpha
 > To unsubscribe, send any mail to "freebsd-alpha-unsubscribe@freebsd.org"
 ---end of quoted text---
 
 -- 
 |   / o / /_  _   		wilko@FreeBSD.org
 |/|/ / / /(  (_)  Bulte				

From: =?ISO-8859-1?Q?Jens_R=F6der?= <j.roeder@tu-bs.de>
To: Wilko Bulte <wkb@freebie.xs4all.nl>
Cc: <FreeBSD-gnats-submit@freebsd.org>
Subject: Re: alpha/50659: reboot causes SRM console to loop endless error
 and needs to be restetted hard
Date: Mon, 7 Apr 2003 19:28:01 +0200 (METDST)

 Hello Wilko,
 
 I am sorry for not mentioning the version:
 
 The machine is an "alphastation 500" from digital and the srm version is
 "V7.2-2".
 
 It run perfectly under FreeBSD 4.7 but unfortunately the kernel was not
 stable with having probably problems in memory so that I tried the 5.0.
 This signifficantly runs more stalbe as long one does not use ipfw
 command. "ipfw show" sometimes panics the kernel and on the reboot, as
 well as by any other reboot, the srm console gets into an desolate
 condition. Using "halt" works fine as expected.
 
 I am quite new to all of this stuff, so if you need more detailed
 information, please ask me what to check for.
 
 with best regards
 
 Jens
 
 
 
 On Mon, 7 Apr 2003, Wilko Bulte wrote:
 
 > On Mon, Apr 07, 2003 at 03:59:17AM +0200, j.roeder@tu-bs.de wrote:
 >
 > It would be interesting to know what SRM version you running. I have
 > not seen this on my AS500/266
 >
 > Wilko
 >
 >
 > > >Number:         50659
 > > >Category:       alpha
 > > >Synopsis:       reboot causes SRM console to loop endless error and ne=
 eds to be restetted hard
 > > >Confidential:   no
 > > >Severity:       serious
 > > >Priority:       medium
 > > >Responsible:    freebsd-alpha
 > > >State:          open
 > > >Quarter:
 > > >Keywords:
 > > >Date-Required:
 > > >Class:          sw-bug
 > > >Submitter-Id:   current-users
 > > >Arrival-Date:   Sun Apr 06 19:00:32 PDT 2003
 > > >Closed-Date:
 > > >Last-Modified:
 > > >Originator:     jens
 > > >Release:        FreeBSD 5.0-RELEASE-p7 alpha
 > > >Organization:
 > > TU-Braunschweig
 > > >Environment:
 > > System: FreeBSD ptchgate.rz.tu-bs.de 5.0-RELEASE-p7 FreeBSD 5.0-RELEASE=
 -p7 #1: Mon Mar 31 02:29:29 CEST 2003 root@ptchgate.rz.tu-bs.de:/home/bsd/s=
 rc/sys/alpha/compile/FIREWALL alpha
 > >
 > >
 > >
 > > >Description:
 > > =09When rebooting the kernel on alphastation 500 the kernel sends proba=
 bly a wrong message to the
 > > =09SRM console and the console prints out endless lines of:
 > >
 > > TU PCI BUSS Error; CSR5 ffffffff
 > >
 > > =09The only way is to reset the entire box  the hard way. The error isn=
 't that nice, as the machine would not reboot without manual work after a k=
 ernel panic.
 > >
 > >
 > >
 > > >How-To-Repeat:
 > >
 > > =09simply reboot
 > >
 > >
 > > >Fix:
 > > no idea due to my limited knowledge
 > >
 > >
 > >
 > > >Release-Note:
 > > >Audit-Trail:
 > > >Unformatted:
 > > _______________________________________________
 > > freebsd-alpha@freebsd.org mailing list
 > > http://lists.freebsd.org/mailman/listinfo/freebsd-alpha
 > > To unsubscribe, send any mail to "freebsd-alpha-unsubscribe@freebsd.org=
 "
 > ---end of quoted text---
 >
 > --
 > |   / o / /_  _   =09=09wilko@FreeBSD.org
 > |/|/ / / /(  (_)  Bulte
 >
 
 ---------------------------------------------------------------------------=
 --
 Physikalische und Theoretische Chemie der TU-Braunschweig
 Jens R=F6der, Hans-Sommer Str.10, 38106 Braunschweig
 ---------------------------------------------------------------------------=
 --
 
State-Changed-From-To: open->closed 
State-Changed-By: wilko 
State-Changed-When: Wed May 14 02:11:30 PDT 2003 
State-Changed-Why:  
The SRM issue I tried hard to reproduce on my AS500 
but I could never make that happen.  

Please submit  a PR against ipfw on Alpha to address the 
panic caused by ' ipfw show'. Unaligned accesses in the 
kernel caused by ipfw need to be fixed by the ipfw maintainer. 


http://www.freebsd.org/cgi/query-pr.cgi?pr=50659 
>Unformatted:
