Re: [parisc-linux] ipv6 problem with 2.6.7-pa1

Re: [parisc-linux] ipv6 problem with 2.6.7-pa1

[Joel Soete]

Hello all,

I find interesting to report the success of following test on my c110 with k-2.6.7-pa1 + ncr patch:

* I just tar my kernel src tree in a 'big' file of about 200Mb (previous patch that was enough to crash the system)
* I scp (ipv4 first) this file to my pc (it takes about 4:15 with a 10Mb nic that's a rate of less then 1MB/s Ok for me)
     (i do this from hppa to pc because Guy's report indicates that tx stuff was the pb)
* I recompile the kernels (pc & hppa) to add just CONFIG_EXPERIMENTAL & CONFIG_IPV6 (also CONFIG_IPV6_PRIVACY don't know yet if 
required)
* refering to <http://people.debian.org/~csmall/ipv6/setup.html> and with Guy's help, after reboot I choose the simplest way and
* config my second pc nic with 'ifconfig eth1 add 2001:0db8:0005:0006::79/64'
* config the buildin nic of my hppa with: 'ifconfig eth0 add 2001:db8:5:6::78/64'
* i can ping6 (added thanks to iputils-ping dpkg) each other ;)
* I just add those to ip6 address to my /etc/hosts:
2001:db8:5:6::78	hpal-ip6
2001:db8:5:6::79	sidh-ip6

* i re-launch scp of previous 200Mb file from hppa to pc and all is Ok ;)
* and do the reverse (pc to hppa) with same success (just a bit slowest: ie 4:47 min in place of 04:12)

Cheers,
	Joel

Grant Grundler wrote:
> On Tue, Jun 22, 2004 at 07:09:33PM +0200, Joel Soete wrote:
> 
>>Very intersecting, c3k is using a tulip as builtin nic (iirc) and
>>not ccio-dma.
> 
> 
> c3k is using sba_iommu.c instead.
> 
> 
>>OTC d250 (as well as c110) uses LASI ASIC interface.
>>
>>Grant could you let me know if this last nic also interface with ccio-dma?
> 
> 
> Yes. All IO goes through the IOMMU when it's part of the system.
> 
> 
>>even over my ncr patch on this d model?
> 
> 
> seems jejb would prefer to see your patch get committed and then
> move upstream.
> 
> 
>>Is this kind of interface also use the scatter/gather list?
> 
> 
> NICs don't scatter gather. They only map a single buffer at
> a time.
> 
> grant
> 
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] ipv6 problem with 2.6.7-pa1

[M. Grabert]

On Sun, Jun 27, 2004 at 02:59:56PM +0000, Joel Soete wrote:
> Hello all,
> 
> I find interesting to report the success of following test on my c110
> with k-2.6.7-pa1 + ncr patch:
> 
> * I just tar my kernel src tree in a 'big' file of about 200Mb
>   (previous patch that was enough to crash the system)
> * I scp (ipv4 first) this file to my pc (it takes about 4:15 with
>   a 10Mb nic that's a rate of less then 1MB/s Ok for me)

BTW, what kind of NIC (ne2k, tulip, etherexpress, some 3com ...?)

>   (i do this from hppa to pc because Guy's report indicates that
>    tx stuff was the pb)

I'm still suspicious that the network card (ie. the driver) could
cause Guy's problem, although his kernel stack dump doesn't give
any indication and suggests to look somewhere else (ie. IPv6)

> * I recompile the kernels (pc & hppa) to add just CONFIG_EXPERIMENTAL & 
>   CONFIG_IPV6 (also CONFIG_IPV6_PRIVACY don't know yet if required)

If you don't assign a IPv6 address to a NIC manually, IPv6 does
create one automatically. With 'Privacy Extensions' enabled,
the address autoconfiguration uses 'random' IPv6 addresses instead
of deriving them from the MAC address (EUI-64).

Since you set up your IPv6 addresses manually, you don't need
CONFIG_IPV6_PRIVACY). BTW, you also have to explicitly turn those
'privacy extensions' on (via /proc) if you want to use it.

> * refering to <http://people.debian.org/~csmall/ipv6/setup.html>
>   and with Guy's help, after reboot I choose the simplest way and
> * config my second pc nic with 'ifconfig eth1 add 
>   2001:0db8:0005:0006::79/64'
> * config the buildin nic of my hppa with: 'ifconfig eth0 add 
>   2001:db8:5:6::78/64'
> * i can ping6 (added thanks to iputils-ping dpkg) each other ;)
> * I just add those to ip6 address to my /etc/hosts:
>   2001:db8:5:6::78	hpal-ip6
>   2001:db8:5:6::79	sidh-ip6
> * i re-launch scp of previous 200Mb file from hppa to pc and all is Ok ;)
> * and do the reverse (pc to hppa) with same success (just a bit
>   slowest: ie 4:47 min in place of 04:12)

Well, what else is different from Guy's config?
He's using the machine as a IPv6 router, so you might have to
simulate this aswell in order to trigger the same problem that Guy
has. As I said, I have virtually the same IPv6 setup as Guy has,
but I don't have the problem on my C3000.

Greetings,
   Max
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] ipv6 problem with 2.6.7-pa1

[Joel Soete]

M. Grabert wrote:
> On Sun, Jun 27, 2004 at 02:59:56PM +0000, Joel Soete wrote:
> 
>>Hello all,
>>
>>I find interesting to report the success of following test on my c110
>>with k-2.6.7-pa1 + ncr patch:
>>
>>* I just tar my kernel src tree in a 'big' file of about 200Mb
>>  (previous patch that was enough to crash the system)
>>* I scp (ipv4 first) this file to my pc (it takes about 4:15 with
>>  a 10Mb nic that's a rate of less then 1MB/s Ok for me)
> 
> 
> BTW, what kind of NIC (ne2k, tulip, etherexpress, some 3com ...?)
>
umm I don't yet test hwinfo but btw dmesg tells me:

LASI 82596 driver - Revision: 1.30
Found i82596 at 0xffd07000, IRQ 87
CLASS: registering class device: ID = 'eth0'
eth0: 82596 at 0xffd07000, 00 60 B0 07 1E EA IRQ 87.

> 
>>  (i do this from hppa to pc because Guy's report indicates that
>>   tx stuff was the pb)
> 
> 
> I'm still suspicious that the network card (ie. the driver) could
> cause Guy's problem,

Should be: the builtin card is the same as the c110 (at least uses the same driver) but the additional one uses 3c509.c
(with one I had so much pb some time ago on my i386)

> although his kernel stack dump doesn't give
> any indication and suggests to look somewhere else (ie. IPv6)
>
The same for the ncr, it's only thanks to knowledge and experience of Grant, James, Matthew (sorry if I forget somebody else) that 
I reach to locate and fix the pb. Mel Gorman tool CodeViz just help me to figureout a bit how to read the stack dump but not 
really more.

> 
>>* I recompile the kernels (pc & hppa) to add just CONFIG_EXPERIMENTAL & 
>>  CONFIG_IPV6 (also CONFIG_IPV6_PRIVACY don't know yet if required)
> 
> 
> If you don't assign a IPv6 address to a NIC manually, IPv6 does
> create one automatically. With 'Privacy Extensions' enabled,
> the address autoconfiguration uses 'random' IPv6 addresses instead
> of deriving them from the MAC address (EUI-64).
> 
> Since you set up your IPv6 addresses manually, you don't need
> CONFIG_IPV6_PRIVACY). BTW, you also have to explicitly turn those
> 'privacy extensions' on (via /proc) if you want to use it.
> 
> 
>>* refering to <http://people.debian.org/~csmall/ipv6/setup.html>
>>  and with Guy's help, after reboot I choose the simplest way and
>>* config my second pc nic with 'ifconfig eth1 add 
>>  2001:0db8:0005:0006::79/64'
>>* config the buildin nic of my hppa with: 'ifconfig eth0 add 
>>  2001:db8:5:6::78/64'
>>* i can ping6 (added thanks to iputils-ping dpkg) each other ;)
>>* I just add those to ip6 address to my /etc/hosts:
>>  2001:db8:5:6::78	hpal-ip6
>>  2001:db8:5:6::79	sidh-ip6
>>* i re-launch scp of previous 200Mb file from hppa to pc and all is Ok ;)
>>* and do the reverse (pc to hppa) with same success (just a bit
>>  slowest: ie 4:47 min in place of 04:12)
> 
> 
> Well, what else is different from Guy's config?
> He's using the machine as a IPv6 router, so you might have to
> simulate this aswell in order to trigger the same problem that Guy
> has.
Yes, I just try step by step. More over I don't have second nic (and no chance no cache another one), so that will be difficult :(

> As I said, I have virtually the same IPv6 setup as Guy has,
> but I don't have the problem on my C3000.
> 
Thanks again,
	Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] ipv6 problem with 2.6.7-pa1

[Joel Soete]

M. Grabert wrote:
> On Sun, Jun 27, 2004 at 04:50:27PM +0000, Joel Soete wrote:
> 
>>>BTW, what kind of NIC (ne2k, tulip, etherexpress, some 3com ...?)
>>>
>>
>>umm I don't yet test hwinfo but btw dmesg tells me:
>>
>>LASI 82596 driver - Revision: 1.30
>>Found i82596 at 0xffd07000, IRQ 87
>>CLASS: registering class device: ID = 'eth0'
>>eth0: 82596 at 0xffd07000, 00 60 B0 07 1E EA IRQ 87.
> 
> 
> Ooops, sorry. I thought you also used a second NIC ...
> 
No pb.
> 
> I mean his additional network card (the 3com) could be the trouble
> maker.
> 
Well I also miss something important: this 3com is certainly a isa model and so btw uses the wax-eisa driver which afaik is not 
the must (http://lists.parisc-linux.org/pipermail/parisc-linux/2003-November/021613.html ?)

> 
>>Should be: the builtin card is the same as the c110 (at least uses the
>>same driver) but the additional one uses 3c509.c
>>(with one I had so much pb some time ago on my i386)
> 
> 
> And which I had so much trouble half a year ago in my C3000.
> 
Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] ipv6 problem with 2.6.7-pa1

[Joel Soete]

M. Grabert wrote:
> On Sun, Jun 27, 2004 at 06:02:22PM +0000, Joel Soete wrote:
> 
> 
>>>Well I also miss something important: this 3com is certainly a isa model 
>>>and so btw uses the wax-eisa driver which afaik is not the must 
>>>(http://lists.parisc-linux.org/pipermail/parisc-linux/2003-November/021613.html ?)
>>>
>>
>>Or more recent again:
>><http://lists.parisc-linux.org/pipermail/parisc-linux/2004-March/022686.html>
> 
> 
> Sorry to disappoint you (and me), but our theory of a broken EISA/network
> card driver is pointless. Guy already pointed out that he's only using
> the onboard lasi card,
Yes he remember me ()

> and that there is in fact no card in the EISA slot atm.
?
any way, in the dmesg he sent us this card appears well and I have no clue how much this card, even not used could disturbe its 
system?
> I even doubt the 3com network card driver (compiled as module) is loaded into
> kernel space.
> 
> Also interesting is the fact that his system is still running after the
> kernel oops, and only the network (IPv4 and IPv6) is not working anymore.

I presume that the developper find the fact to not being able to tx a data is less critical then lost to write data on disk?

> Might this indicate that it is not really IPv6-stack related, but the problem
> is somewhere else in the networking code?
> 
I have this feeling (so similar to my ncr pb: same lasi+ccio-dma drivers, when writing and with high i/o rate?)
It's possible that my patch is not enough or has border effect?
For the moment Guy as recompile a 2.6.6-pa4 with my patch and awaiting to reboot it.
If it unfortunately it still failled, I will ask to try a 2.6.3 (ie the last one I can boot without pb on my c110 ;)

Regards,
	Joel
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux

Re: [parisc-linux] ipv6 problem with 2.6.7-pa1

[Kyle McMartin]

On Mon, Jun 21, 2004 at 03:30:15PM +0200, Guy Martin wrote:
> skput:over: 10271684:194 put:138 dev:<NULL>kernel BUG at net/core/skbuff.c:88!
> Kernel addresses on the stack:

The fact that dev is NULL is kind of suspect. I'm not exactly sure, but
I do not think this is a PA-RISC bug. Perhaps netdev@oss.sgi.com could
be more helpful in debugging this.

>  [<10327bc0>] ip6_forward+0x1c4/0x434
>  [<10106138>] dump_stack+0x18/0x24
>  [<10271a4c>] i596_interrupt+0x930/0xdf0
>  [<10121a00>] activate_task+0x44/0xa8
>  [<104205b4>] start_kernel+0x4/0x1e4
>  [<101078ec>] do_irq+0x14c/0x154
>  [<102da778>] dev_watchdog+0x88/0xf4
>  [<10107ab4>] do_irq_mask+0xb4/0xcc
>  [<10129d34>] tasklet_action+0x78/0xe4
>  [<102377ec>] busdev_barked+0x3c/0x44
>  [<101078ec>] do_irq+0x14c/0x154
>  [<10102840>] __sched_text_end+0x44/0x48
>  [<101079f0>] do_cpu_irq_mask+0xfc/0x10c
>  [<101717a8>] may_open+0x58/0x1c8
>  [<1010c068>] intr_return+0x0/0x14
>  [<10112368>] cpu_idle+0x28/0x3c
>  [<101717a8>] may_open+0x58/0x1c8
>  [<10160c30>] dentry_open+0x154/0x238
>  [<101744b0>] locate_fd+0x154/0x190
>  [<104205b4>] start_kernel+0x4/0x1e4
>  [<10112378>] cpu_idle+0x38/0x3c
>  [<10420768>] start_kernel+0x1b8/0x1e4
> 

> KERNEL: assertion (!atomic_read(&skb->users)) failed at net/core/dev.c (1666)
> 
I think this is a symptom of the problem, afaict it does contribute.

Cheers,
-- 
Kyle McMartin
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux