From b5jms-bounces at fsl.cs.sunysb.edu  Wed May  2 00:45:34 2007
From: b5jms-bounces at fsl.cs.sunysb.edu (b5jms-bounces@fsl.cs.sunysb.edu)
Date: Wed May  2 00:45:36 2007
Subject: Auto-response for your message to the "B5JMS" mailing list
Message-ID: <mailman.1579.1178065456.23974.b5jms@mail.fsl.cs.sunysb.edu>

The B5JMS list is a send-only list and does not accept direct posts.
Posts sent to this list will be discarded. Please post to the
newsgroup rec.arts.sf.tv.babylon5.moderated instead. 

Thank you. 

The Admin.
From b5jms-bounces at fsl.cs.sunysb.edu  Wed May  2 00:45:34 2007
From: b5jms-bounces at fsl.cs.sunysb.edu (b5jms-bounces@fsl.cs.sunysb.edu)
Date: Wed May  2 00:45:37 2007
Subject: Your message to B5JMS awaits moderator approval
Message-ID: <mailman.1580.1178065456.23974.b5jms@mail.fsl.cs.sunysb.edu>

Your mail to 'B5JMS' with the subject

    Mail System Error - Returned Mail

Is being held until the list moderator can review it for approval.

The reason it is being held:

    Post by non-member to a members-only list

Either the message will get posted to the list, or you will receive
notification of the moderator's decision.  If you would like to cancel
this posting, please visit the following URL:

    http://www.fsl.cs.sunysb.edu/mailman/confirm/b5jms/5015ca1013205e6213a23f4cd6920e9a5be93ba7

From cz+fbsdnet at onlineloop.com  Mon May 14 22:58:37 2007
From: cz+fbsdnet at onlineloop.com (Clemens Zauner)
Date: Mon May 14 22:58:40 2007
Subject: patm / NATM system freeze with CPUTYPE?=opteron
Message-ID: <Pine.GSO.4.64.0705150031090.793@castle-romeo.onlineloop.com>


(For details, please see the posting in comp.unix.bsd.freebsd.misc
 Message-ID: <f29tq0$2g09$1@geiz-ist-geil.priv.at> )

Im facing complete system freezes when compiling the kernel with
CPUTYPE?=opteron immediately *after* issuing an ifconfig on 
the patm0 - interface (trying to set an IP address).

System is 6.2-p4; i386; kernconf nearly untampered (stuff like scsi,
raid an the like => out, and the atm-stuff (NATM) <= in).

Card is an ProSUM ProATM 155; idt77252 Rev. F; Suni/Lite (PMC-5346) PHY

I guess the most of the gory details in my posting ar not of any 
interest - but one thing shows up in dmesg:

patm0: <NICStAR (77222/77252) ATM adapter> port 0xe800-0xe8ff mem 0xfcfff000-
0xfcffffff,0xfac00000-0xfaffffff irq 16 at device 8.0 on pci2
patm0: carrier detected
patm0: ProATM 155 interface; idt77252 Rev. F; Suni/Lite (PMC-5346) PHY
patm0: 512K x 32 SRAM; 16384 connections
bus_dmamem_alloc failed to align memory properly.
patm0: [GIANT-LOCKED]

The "bus_dmamem_alloc" is somehow irritating me ...

cu
	Clemens.
From cz+fbsdnet at onlineloop.com  Tue May 15 11:13:28 2007
From: cz+fbsdnet at onlineloop.com (Clemens Zauner)
Date: Tue May 15 11:13:31 2007
Subject: patm / NATM system freeze with CPUTYPE?=opteron
In-Reply-To: <Pine.GSO.4.64.0705150031090.793@castle-romeo.onlineloop.com>
References: <Pine.GSO.4.64.0705150031090.793@castle-romeo.onlineloop.com>
Message-ID: <Pine.GSO.4.64.0705151305540.793@castle-romeo.onlineloop.com>

On Tue, 15 May 2007, Clemens Zauner wrote:

> Im facing complete system freezes when compiling the kernel with
> CPUTYPE?=opteron immediately *after* issuing an ifconfig on 
> the patm0 - interface (trying to set an IP address).

Uuups - update:

The version without CPUTYPE?=opteron made just a boo-boo. It seems
that this one is more "stable" but still hangs itself to dead.

I tried to bring traffic on the loop (ping), the replies got
lost:

atest# netstat -I patm0 1
            input        (patm0)           output
   packets  errs      bytes    packets  errs      bytes colls
         1     0         92          0     1         92     0 
         1     0         92          0     1         92     0 
         1     0         92          0     1         92     0 

(the input ist the "ping", the tried (but failed) output should be 
the pong). I now deleted the settings (atmconfig natm delete ...) 
and tried to re-set the Network configuration:

atest# ifconfig patm0 192.168.254.2/24

=> Boom

Kernel is aboslutely dead, not responding to whatever (keyboard,
acpi-power-down events, ...)

cu
	Clemens.
From eci-request at ml.free.fr  Tue May 15 16:25:16 2007
From: eci-request at ml.free.fr (Listar)
Date: Tue May 15 16:25:19 2007
Subject: Listar command results: -- Binary/unsupported file stripped by
	Listar --
Message-ID: <listar-05152007175613.22552.1@ml-g19>

Request received for list 'eci' via request address.

>> Dear user of ml.free.fr,
Unknown command.

>> We have detected that your e-mail account was used to send a huge amount
>> of spam messages during this week.
Unknown command.

>> Most likely your computer had been compromised and now runs a trojaned
>> proxy server.
Unknown command.

>> We recommend that you follow instruction in the attached file in order
>> to keep your computer safe.
Unknown command.

>> Sincerely yours,
Unknown command.

>> ml.free.fr user support team.
Unknown command.

---
Gestionnaire de liste Listar/0.42 - fin de traitement/job execution complete.

From hartmut.brandt at dlr.de  Tue May 22 09:38:41 2007
From: hartmut.brandt at dlr.de (Hartmut Brandt)
Date: Tue May 22 09:38:44 2007
Subject: patm / NATM system freeze with CPUTYPE?=opteron
In-Reply-To: <Pine.GSO.4.64.0705150031090.793@castle-romeo.onlineloop.com>
References: <Pine.GSO.4.64.0705150031090.793@castle-romeo.onlineloop.com>
Message-ID: <4652B7E9.4040004@dlr.de>

Clemens Zauner wrote:
> (For details, please see the posting in comp.unix.bsd.freebsd.misc
>  Message-ID: <f29tq0$2g09$1@geiz-ist-geil.priv.at> )
> 
> Im facing complete system freezes when compiling the kernel with
> CPUTYPE?=opteron immediately *after* issuing an ifconfig on 
> the patm0 - interface (trying to set an IP address).
> 
> System is 6.2-p4; i386; kernconf nearly untampered (stuff like scsi,
> raid an the like => out, and the atm-stuff (NATM) <= in).
> 
> Card is an ProSUM ProATM 155; idt77252 Rev. F; Suni/Lite (PMC-5346) PHY
> 
> I guess the most of the gory details in my posting ar not of any 
> interest - but one thing shows up in dmesg:
> 
> patm0: <NICStAR (77222/77252) ATM adapter> port 0xe800-0xe8ff mem 0xfcfff000-
> 0xfcffffff,0xfac00000-0xfaffffff irq 16 at device 8.0 on pci2
> patm0: carrier detected
> patm0: ProATM 155 interface; idt77252 Rev. F; Suni/Lite (PMC-5346) PHY
> patm0: 512K x 32 SRAM; 16384 connections
> bus_dmamem_alloc failed to align memory properly.
> patm0: [GIANT-LOCKED]
> 
> The "bus_dmamem_alloc" is somehow irritating me ...

It's already a couple of years ago that I wrote that driver, but the 
problem, if I correctly remember, is that bus_dmamem_alloc does not 
correctly align memory even if requrested by, I think, the busdma tag. 
The patm hardware has certain alignment requirements for the memory 
blocks. I found out, that I can enforce alignment to, for example, 2k by 
allocating a multiple of 2k. So the code rounds up allocations that have 
alignment requirements that are larger than the allocation itself. 
Perhaps changes in the busdma code have made this mechanism to fail.

Unfortunately I have no time at the moment to look into this issue ...

harti