Re: Problem with "Happy Meal" drivers

2004-01-13 Thread Blars Blarson
In article <[EMAIL PROTECTED]>
[EMAIL PROTECTED] writes:
>I am reasonably certain this doesn't happen on (some?) sparc hardware.  I've
>had an Ultra30 plugged into our E450 via serial, and when I rebooted it,
>I don't recall finding the E450 at PROM later.
>
>I could be wrong, of course.

Rebooting will not normally cause the problem, only actually powering
down, and it is somewhat hardware dependant.  (If your terminal acts
as an open circuit when unpowered, it will not cause this problem.)

Some sparc models can be set to ignore break on the serial console.
(This may also depend on openboot version.)
-- 
Blars Blarson   [EMAIL PROTECTED]
http://www.blars.org/blars.html
With Microsoft, failure is not an option.  It is a standard feature.



Re: Problem with "Happy Meal" drivers

2004-01-12 Thread Mike Edwards
I am reasonably certain this doesn't happen on (some?) sparc hardware.  I've
had an Ultra30 plugged into our E450 via serial, and when I rebooted it,
I don't recall finding the E450 at PROM later.

I could be wrong, of course.


On Sun, Jan 11, 2004 at 03:54:17AM -0800, [EMAIL PROTECTED] said:
> Date: Sun, 11 Jan 2004 03:54:17 -0800
> From: [EMAIL PROTECTED]
> To: bath66 <[EMAIL PROTECTED]>
> Cc: Andrew Sharp <[EMAIL PROTECTED]>, debian-sparc@lists.debian.org
> Subject: Re: Problem with "Happy Meal" drivers
> User-Agent: Mutt/1.3.28i
> X-Spam-Status: No, hits=0.3 required=4.0 tests=NO_REAL_NAME autolearn=no 
>   version=2.60
> X-Spam-Level: 
> 
> On Sun, Jan 11, 2004 at 08:58:17AM +0100, bath66 wrote:
> > "Andrew Sharp" <[EMAIL PROTECTED]> was quoted as saying by some wrong mail 
> > agent
> > operated by Mr. bath66 who should know better
> > >
> > > Before you turn off the PC that is connected to the Sun's serial
> > > console, remove the cable from the sun.  That way, the sun will stay
> > > running and you won't have these problems.
> > >
> > Thanks for the conseil .. It work now ... but can you explain me why ?
> 
> A break signal on the sun serial port drops it into the openboot prompt.
> 'go' restarts it where it left off.
> 
> In rs232 a break is signaled by holding the line low for longer than
> 10 bit times (therefore it cannot be a valid byte b/c a valid byte
> would have ended with a high stop bit at the 9th bit[1]).
> 
> Some PCs inadvertently drive TX low for that long as power goes down.
> There isn't much you can do; I even tried lowering the baud rate
> and even as 1200 the PC's signal was long enough to act as a break.
> 
> -Nicolas Dade
> 
> [1] assuming 8N1; the principal is the same with other data settings---
> a break is unambiguously not a data transfer
> 
> 
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> 

-- 
Mike Edwards <[EMAIL PROTECTED]>
System Administrator
Psychology Department, Rutgers University, Newark campus
973-353-5440 x246



Re: Problem with "Happy Meal" drivers

2004-01-12 Thread Alex Yung


On 1/11/2004 5:54 AM, [EMAIL PROTECTED] wrote:
> On Sun, Jan 11, 2004 at 08:58:17AM +0100, bath66 wrote:
> 
>>"Andrew Sharp" <[EMAIL PROTECTED]> was quoted as saying by some wrong mail 
>>agent
>>operated by Mr. bath66 who should know better
>>
>>>Before you turn off the PC that is connected to the Sun's serial
>>>console, remove the cable from the sun.  That way, the sun will stay
>>>running and you won't have these problems.
>>>
>>
>>Thanks for the conseil .. It work now ... but can you explain me why ?
> 
> 
> A break signal on the sun serial port drops it into the openboot prompt.
> 'go' restarts it where it left off.
> 
> In rs232 a break is signaled by holding the line low for longer than
> 10 bit times (therefore it cannot be a valid byte b/c a valid byte
> would have ended with a high stop bit at the 9th bit[1]).
> 
> Some PCs inadvertently drive TX low for that long as power goes down.
> There isn't much you can do; I even tried lowering the baud rate
> and even as 1200 the PC's signal was long enough to act as a break.
> 
> -Nicolas Dade
> 
> [1] assuming 8N1; the principal is the same with other data settings---
> a break is unambiguously not a data transfer

Run this command to over come the hardware BREAK signal:
/sbin/sysctl -w kernel/stop-a=0

The above is the same as Solaris "/etc/default/kbd" with:
KEYBOARD_ABORT=disable



Re: Problem with "Happy Meal" drivers

2004-01-11 Thread ndade
On Sun, Jan 11, 2004 at 08:58:17AM +0100, bath66 wrote:
> "Andrew Sharp" <[EMAIL PROTECTED]> was quoted as saying by some wrong mail 
> agent
> operated by Mr. bath66 who should know better
> >
> > Before you turn off the PC that is connected to the Sun's serial
> > console, remove the cable from the sun.  That way, the sun will stay
> > running and you won't have these problems.
> >
> Thanks for the conseil .. It work now ... but can you explain me why ?

A break signal on the sun serial port drops it into the openboot prompt.
'go' restarts it where it left off.

In rs232 a break is signaled by holding the line low for longer than
10 bit times (therefore it cannot be a valid byte b/c a valid byte
would have ended with a high stop bit at the 9th bit[1]).

Some PCs inadvertently drive TX low for that long as power goes down.
There isn't much you can do; I even tried lowering the baud rate
and even as 1200 the PC's signal was long enough to act as a break.

-Nicolas Dade

[1] assuming 8N1; the principal is the same with other data settings---
a break is unambiguously not a data transfer



Re: Problem with "Happy Meal" drivers

2004-01-11 Thread bath66
Thanks for the conseil .. It work now ... but can you explain me why ?

bath66.
- Original Message - 
From: "Andrew Sharp" <[EMAIL PROTECTED]>
To: "bath66" <[EMAIL PROTECTED]>
Cc: 
Sent: Sunday, January 11, 2004 5:04 AM
Subject: Re: Problem with "Happy Meal" drivers


> Before you turn off the PC that is connected to the Sun's serial
> console, remove the cable from the sun.  That way, the sun will stay
> running and you won't have these problems.
>
> a
>
> On Sun, Jan 11, 2004 at 02:38:26AM +0100, bath66 wrote:
> > Hello,
> >
> > I'm using a Sun Ultra (sparc64) which is running under the kernel
> > 2.4.24-SMP. I also use two network cards handled by your driver (sunhme)
:
> > A SunSwift (eth1) which is connected to my LAN and the onboard card
(eth0)
> > which is connected to the internet thru PPPoE. Im using this machine as
a
> > small gateway.
> >
> > Unfortunately, i've got a very annoying problem : when all the computers
of
> > the network are switched off - the gateway remaining the only active
> > computer on the LAN - it is irremediably crashing. So I switch on one
PC,
> > connect to the console port (the network isn't working anymore) and then
> > type 'return', i get into the PROM and type 'go' and get this message :
>
>
> -- 
> To UNSUBSCRIBE, email to [EMAIL PROTECTED]
> with a subject of "unsubscribe". Trouble? Contact
[EMAIL PROTECTED]
>
>




Re: Problem with "Happy Meal" drivers

2004-01-10 Thread Andrew Sharp
Before you turn off the PC that is connected to the Sun's serial
console, remove the cable from the sun.  That way, the sun will stay
running and you won't have these problems.

a

On Sun, Jan 11, 2004 at 02:38:26AM +0100, bath66 wrote:
> Hello,
> 
> I'm using a Sun Ultra (sparc64) which is running under the kernel
> 2.4.24-SMP. I also use two network cards handled by your driver (sunhme) :
> A SunSwift (eth1) which is connected to my LAN and the onboard card (eth0)
> which is connected to the internet thru PPPoE. Im using this machine as a
> small gateway.
> 
> Unfortunately, i've got a very annoying problem : when all the computers of
> the network are switched off - the gateway remaining the only active
> computer on the LAN - it is irremediably crashing. So I switch on one PC,
> connect to the console port (the network isn't working anymore) and then
> type 'return', i get into the PROM and type 'go' and get this message :



Problem with "Happy Meal" drivers

2004-01-10 Thread bath66
Hello,

I'm using a Sun Ultra (sparc64) which is running under the kernel
2.4.24-SMP. I also use two network cards handled by your driver (sunhme) :
A SunSwift (eth1) which is connected to my LAN and the onboard card (eth0)
which is connected to the internet thru PPPoE. Im using this machine as a
small gateway.

Unfortunately, i've got a very annoying problem : when all the computers of
the network are switched off - the gateway remaining the only active
computer on the LAN - it is irremediably crashing. So I switch on one PC,
connect to the console port (the network isn't working anymore) and then
type 'return', i get into the PROM and type 'go' and get this message :

eth1: Happy Meal out of receive descriptors, packet dropped.

I type 'return' again and the computer doesn't react anymore, I can't even
access the PROM. Further more, when I reboot, this message doesn't appears
in the logs. By the way, between the last computer's switch off and the
reboot of the gateway, nothing at all appears in the logs, which comfort me
in the idea that the computer has totally crashed.

Moreover, switching the network cards has no effects - the result is the
same when the Sunswift is connected to the LAN, which leads my suspicions to
the driver.

My network is composed of a 8 ports switch 100mbps which connects a PC, a
laptop and the sparc. I tried to apply the patch which adds "udelay(1)" to
the line 1983 (found at
http://sparclinux.net/pub/patches/U1-hme-lockup.patch) but it doesn't change
anything and the problem stays the same.

Here are a few informations that might help you :

My Kernel configuration :
#
# Automatically generated by make menuconfig: don't edit
#

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y

#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODVERSIONS=y
CONFIG_KMOD=y

#
# General setup
#
# CONFIG_BBC_I2C is not set
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_SMP=y
CONFIG_NR_CPUS=32
CONFIG_SPARC64=y
CONFIG_HOTPLUG=y
CONFIG_HAVE_DEC_LOCK=y
# CONFIG_RWSEM_GENERIC_SPINLOCK is not set
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
# CONFIG_ISA is not set
# CONFIG_ISAPNP is not set
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_PCMCIA is not set
CONFIG_SBUS=y
CONFIG_SBUSCHAR=y
CONFIG_BUSMOUSE=y
CONFIG_SUN_MOUSE=y
CONFIG_SERIAL=y
CONFIG_SUN_SERIAL=y
CONFIG_SERIAL_CONSOLE=y
CONFIG_SUN_KEYBOARD=y
CONFIG_SUN_CONSOLE=y
CONFIG_SUN_AUXIO=y
CONFIG_SUN_IO=y
# CONFIG_PCI is not set
CONFIG_SUN_OPENPROMFS=y
CONFIG_NET=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_KCORE_ELF=y
CONFIG_SPARC32_COMPAT=y
CONFIG_BINFMT_ELF32=y
# CONFIG_BINFMT_AOUT32 is not set
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=m
# CONFIG_SUNOS_EMUL is not set
# CONFIG_SOLARIS_EMUL is not set

#
# Parallel port support
#
CONFIG_PARPORT=m
CONFIG_PARPORT_PC=m
CONFIG_PARPORT_PC_CML1=m
# CONFIG_PARPORT_SERIAL is not set
CONFIG_PARPORT_PC_FIFO=y
# CONFIG_PARPORT_PC_SUPERIO is not set
# CONFIG_PARPORT_AMIGA is not set
# CONFIG_PARPORT_MFC3 is not set
# CONFIG_PARPORT_ATARI is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_SUNBPP is not set
# CONFIG_PARPORT_OTHER is not set
CONFIG_PARPORT_1284=y
# CONFIG_PRINTER is not set

#
# Console drivers
#
CONFIG_PROM_CONSOLE=y

#
# Frame-buffer support
#
CONFIG_FB=y
CONFIG_DUMMY_CONSOLE=y
# CONFIG_FB_CYBER2000 is not set
CONFIG_FB_SBUS=y
CONFIG_FB_CREATOR=y
CONFIG_FB_CGSIX=y
# CONFIG_FB_BWTWO is not set
# CONFIG_FB_CGTHREE is not set
# CONFIG_FB_LEO is not set
# CONFIG_FB_VIRTUAL is not set
# CONFIG_FBCON_ADVANCED is not set
CONFIG_FBCON_CFB8=y
CONFIG_FBCON_CFB16=y
CONFIG_FBCON_CFB24=y
CONFIG_FBCON_CFB32=y
CONFIG_FBCON_FONTWIDTH8_ONLY=y
CONFIG_FONT_SUN8x16=y
# CONFIG_FBCON_FONTS is not set

#
# Misc Linux/SPARC drivers
#
CONFIG_SUN_OPENPROMIO=y
CONFIG_SUN_MOSTEK_RTC=y
# CONFIG_OBP_FLASH is not set
# CONFIG_SUN_BPP is not set
# CONFIG_SUN_VIDEOPIX is not set
CONFIG_SUN_AURORA=m

#
# Linux/SPARC audio subsystem (EXPERIMENTAL)
#
# CONFIG_SPARCAUDIO is not set
# CONFIG_SPARCAUDIO_CS4231 is not set
# CONFIG_SPARCAUDIO_DUMMY is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
CONFIG_BLK_DEV_MD=m
CONFIG_MD_LINEAR=m
CONFIG_MD_RAID0=m
CONFIG_MD_RAID1=m
CONFIG_MD_RAID5=m
CONFIG_MD_MULTIPATH=m
CONFIG_BLK_DEV_LVM=m
CONFIG_BLK_DEV_RAM=m
CONFIG_BLK_DEV_RAM_SIZE=4096
# CONFIG_BLK_DEV_INITRD is not set

#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
CONFIG_FILTER=y
CONFIG_UNIX=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
CONFIG_IP_ADVANCED_ROUTER=y
# CONFIG_IP_MULTIPLE_TABLES is not set
# CONFIG_IP_ROUTE_MULTIPATH is not set
# CONFIG_IP_ROUTE_TOS is not set
# CONFIG_IP_ROUTE_VERBOSE is not set
# CONFIG_IP_PNP is not set
CONFIG_NET_IPIP=m
CONFIG_NET_IPGRE=m
CONFIG_NET_IPGRE_BROADCAST=y
CONFIG_IP_MROUTE=y
CONFIG_IP_PIMSM_V1=y
CONFIG_