Bug 90395

Summary: Viper redboot network load/debug unreliable
Product: [Retired] eCos Reporter: Jonathan Larmour <jifl-bugzilla>
Component: RedBootAssignee: Jonathan Larmour <jifl-bugzilla>
Status: CLOSED WONTFIX QA Contact: Jonathan Larmour <jifl-bugzilla>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.0   
Target Milestone: ---   
Target Release: ---   
Hardware: powerpc   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-06-20 16:25:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jonathan Larmour 2003-05-07 16:55:01 UTC
Description of problem:

Using both 2.0 redboot and current CVS trunk, redboot on viper is unreliable
over the net. Loading via GDB by itself seems okay, but it doesn't take much
more traffic for things to go badly wrong. When watching with tcpdump, it seems
things quickly get stuck in a rut with the viper sending a packet, and the host
responding with an ack, but the viper waiting 1 sec and resending anyway.

Verified with both Linux and NT hosts so it's not a host stack problem.

I need to look closer at this, but need the bug entered for 2.0 known problems...

Comment 1 Alex Schuilenburg 2003-06-20 16:25:37 UTC
This bug has moved to http://bugs.ecos.sourceware.org/show_bug.cgi?id=90395