tcpip stack problem on ppc405

Hi all,

I have ported QNX 6.1 patch A to our PPC405GP driven cpci board.
For our tranfer protocol I need the big tcpip stack.
The board works ok with the tiny stack.
When I use the big stack, I cannot “ifonfig en0 …”:

io-net -dtulip -ptcpip &

pidin


8201 1 -net/ppc/be/io-net 10r SIGWAITINFO
8201 2 -net/ppc/be/io-net 10r RECEIVE 1
8201 3 -net/ppc/be/io-net 10r RECEIVE 1
8201 4 -net/ppc/be/io-net 10r RECEIVE 1
8201 5 -net/ppc/be/io-net 21r RECEIVE 5
8201 6 -net/ppc/be/io-net 18r RECEIVE 9

ls -l /dev/io-net

total 0
crw-rw-rw- 1 root root 0, 1 Jan 01 01:53 en0
crw-rw-rw- 1 root root 0, 1 Jan 01 01:53 ip0
crw-rw-rw- 1 root root 0, 1 Jan 01 01:53 ip_en

ifconfig en0 10.0.17.100 netmask 10.0.255.255

ifconfig: socket: No such device or address

There is no change, if I use the “devn-ppc405.so” network driver.
Any ideas ?

Thanks in advance
Michael Tasche, esd Germany

Michael Tasche <michael.tasche@esd-electronics.com> wrote:
: Hi all,

: I have ported QNX 6.1 patch A to our PPC405GP driven cpci board.
: For our tranfer protocol I need the big tcpip stack.
: The board works ok with the tiny stack.
: When I use the big stack, I cannot “ifonfig en0 …”:

: # io-net -dtulip -ptcpip &

: # pidin
: …
: 8201 1 -net/ppc/be/io-net 10r SIGWAITINFO
: 8201 2 -net/ppc/be/io-net 10r RECEIVE 1
: 8201 3 -net/ppc/be/io-net 10r RECEIVE 1
: 8201 4 -net/ppc/be/io-net 10r RECEIVE 1
: 8201 5 -net/ppc/be/io-net 21r RECEIVE 5
: 8201 6 -net/ppc/be/io-net 18r RECEIVE 9
: …

: # ls -l /dev/io-net
: total 0
: crw-rw-rw- 1 root root 0, 1 Jan 01 01:53 en0
: crw-rw-rw- 1 root root 0, 1 Jan 01 01:53 ip0
: crw-rw-rw- 1 root root 0, 1 Jan 01 01:53 ip_en
: #

: # ifconfig en0 10.0.17.100 netmask 10.0.255.255
: ifconfig: socket: No such device or address

This error seems a little strange. Can you ‘ping 127.1’. If
so, I don’t see how the socket() call could fail, especially with
that errno. Is it actually something like:

ifconfig: SIOCGIFFLAGS en0: No such device or address

Are you running straight 6.1 patch A?


-seanb

: There is no change, if I use the “devn-ppc405.so” network driver.
: Any ideas ?

: Thanks in advance
: Michael Tasche, esd Germany

Sean Boudreau <seanb@qnx.com> wrote in news:a7skqj$r6r$1@nntp.qnx.com:

Michael Tasche <> michael.tasche@esd-electronics.com> > wrote:
: Hi all,

: I have ported QNX 6.1 patch A to our PPC405GP driven cpci board.
: For our tranfer protocol I need the big tcpip stack.
: The board works ok with the tiny stack.
: When I use the big stack, I cannot “ifonfig en0 …”:


Are you running straight 6.1 patch A?


-seanb

This has been fixed for 6.2


\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

Hi,

here are my current problems:

  1. Big stack and ppc is completly unusable with 6.1 Patch A.

  2. Our udp based protocol can be switched to use udp broadcast instead
    of multicast.
    So I can use the tiny stack, but after a short time interval the whole
    io-net process dies without comments.

  3. I must have it running during april 2002, but I don’t know the
    release date of 6.2.

What can I do?
Can I get a bugfix for the stack, which runs under 6.1 Patch A ?
Is there a usable 6.2 Beta for ppc?

Michael

Adam Mallory wrote:

Sean Boudreau <> seanb@qnx.com> > wrote in news:a7skqj$r6r$> 1@nntp.qnx.com> :

Michael Tasche <> michael.tasche@esd-electronics.com> > wrote:
: Hi all,

: I have ported QNX 6.1 patch A to our PPC405GP driven cpci board.
: For our tranfer protocol I need the big tcpip stack.
: The board works ok with the tiny stack.
: When I use the big stack, I cannot “ifonfig en0 …”:


Are you running straight 6.1 patch A?


-seanb


This has been fixed for 6.2


Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

This isn’t a stack issue so there is no simple update
available.

-seanb

Michael Tasche <michael.tasche@esd-electronics.com> wrote:
: Hi,

: here are my current problems:

: 1) Big stack and ppc is completly unusable with 6.1 Patch A.

: 2) Our udp based protocol can be switched to use udp broadcast instead
: of multicast.
: So I can use the tiny stack, but after a short time interval the whole
: io-net process dies without comments.

: 3) I must have it running during april 2002, but I don’t know the
: release date of 6.2.

: What can I do?
: Can I get a bugfix for the stack, which runs under 6.1 Patch A ?
: Is there a usable 6.2 Beta for ppc?

: Michael

Michael Tasche <michael.tasche@esd-electronics.com> wrote in
news:3CA2E8B8.8A1E0606@esd-electronics.com:

What can I do?
Can I get a bugfix for the stack, which runs under 6.1 Patch A ?
Is there a usable 6.2 Beta for ppc?

You need to contact your sales rep. to organize getting a fix for the
PPC405.


\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

Thanks for your answers.

Knowing the IBM bug list of the 405GP I contact my sales rep. in
February.
I wanted to get a list of the solved and unsolved 405GP bugs.
Well, after a short delay I got a few fragments of such a list and the
info, 6.2 will solve something.

Now you told me about a fix for the 405GP.

It seems to be a big problem for my sales rep. to get the 405GP fix or
the detailed bug list from the QNX headquarter.

Best regards,
Michael, esd Hannover Germany

Adam Mallory schrieb:

Michael Tasche <> michael.tasche@esd-electronics.com> > wrote in
news:> 3CA2E8B8.8A1E0606@esd-electronics.com> :

What can I do?
Can I get a bugfix for the stack, which runs under 6.1 Patch A ?
Is there a usable 6.2 Beta for ppc?

You need to contact your sales rep. to organize getting a fix for the
PPC405.


Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net

Michael Tasche <michael.tasche@privat.kkf.net> wrote in
news:3CA43C26.24BDA6DB@privat.kkf.net:

Thanks for your answers.

Knowing the IBM bug list of the 405GP I contact my sales rep. in
February.

That IBM errata list is big eh? :slight_smile:

I wanted to get a list of the solved and unsolved 405GP bugs.

Are you refering to 405GP(and CR) bugs or Neutrino bugs? The 405 has a
problem with the load/link/store conditional not being atomic. When an
interrupt goes off at the same time as this intruction, it gets stalled in
the pipeline, and thus is “not stable”. We’re implmenting a work around
for this CPU bug, but this is by no means a QNX bug.

Well, after a short delay I got a few fragments of such a list and the
info, 6.2 will solve something.

Now you told me about a fix for the 405GP.

It seems to be a big problem for my sales rep. to get the 405GP fix or
the detailed bug list from the QNX headquarter.

You can contact customer support directly 1 800 676-0566 for north america
to discuss you needs.


\

Cheers,
Adam

QNX Software Systems Ltd.
[ amallory@qnx.com ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <pschon@baste.magibox.net>

Adam Mallory schrieb:

Michael Tasche <> michael.tasche@privat.kkf.net> > wrote in
news:> 3CA43C26.24BDA6DB@privat.kkf.net> :

Thanks for your answers.

Knowing the IBM bug list of the 405GP I contact my sales rep. in
February.

That IBM errata list is big eh? > :slight_smile:
Yes, very big.

I wanted to get a list of the solved and unsolved 405GP bugs.

Are you refering to 405GP(and CR) bugs or Neutrino bugs?
405GP Bugs.



The 405 has a
problem with the load/link/store conditional not being atomic. When an
interrupt goes off at the same time as this intruction, it gets stalled in
the pipeline, and thus is “not stable”. We’re implmenting a work around
for this CPU bug, but this is by no means a QNX bug.
I agree.

But without the workaround e.g. mutexes should not work correctly.
On another operating system we found two threads inside the critical
path once per week.
It is very important for me, to know which revision of QNX will solve
the load/link/store cond…
Is the workaround part of the 405GP fix, you told about?

Michael

Well, after a short delay I got a few fragments of such a list and the
info, 6.2 will solve something.

Now you told me about a fix for the 405GP.

It seems to be a big problem for my sales rep. to get the 405GP fix or
the detailed bug list from the QNX headquarter.

You can contact customer support directly 1 800 676-0566 for north america
to discuss you needs.


Cheers,
Adam

QNX Software Systems Ltd.
[ > amallory@qnx.com > ]

With a PC, I always felt limited by the software available.
On Unix, I am limited only by my knowledge.
–Peter J. Schoenster <> pschon@baste.magibox.net