John W. Linville wrote:
I am now... :-) But, I still don't seem to see any problem. Are there
specific tests I should run?
It crashes for me, too:
- nForce 3-250 Gb, in 100 mbit mode
- slab debugging on
- iommu debug and iommu leak enabled
- x86-64
- tx works.
- rx crashes.
Test case: "p
John W. Linville wrote:
I am now... :-) But, I still don't seem to see any problem. Are there
specific tests I should run?
There are multiple nforce versions - which one do you use?
For example only the most recent one supports 64-bit dma, perhaps
something with the 64-bit code is broken
On Fri, Dec 16, 2005 at 04:47:54AM +0100, Andi Kleen wrote:
>
> Some more testing shows that even the 2.6.14 driver eventually
> causes slab debugging BUGs() like
>
> --- [cut here ] - [please bite here ] -
> Kernel BUG at /home/andi/lsrc/linux-2.6.15rc5-git4/mm/slab.c:23
On Thu, Dec 15, 2005 at 01:58:41PM -0800, David S. Miller wrote:
> From: "John W. Linville" <[EMAIL PROTECTED]>
> Date: Thu, 15 Dec 2005 15:21:37 -0500
>
> > Interesting... FWIW the FC4.netdev.6 kernel seems to be working fine
> > on (a yet-to-be-released box), which is an x86_64 (AMD) box w/
> >
Some more testing shows that even the 2.6.14 driver eventually
causes slab debugging BUGs() like
--- [cut here ] - [please bite here ] -
Kernel BUG at /home/andi/lsrc/linux-2.6.15rc5-git4/mm/slab.c:2307
invalid operand: [1] PREEMPT SMP
CPU 3
Modules linked in:
Pid:
On Thu, Dec 15, 2005 at 01:58:41PM -0800, David S. Miller wrote:
> From: "John W. Linville" <[EMAIL PROTECTED]>
> Date: Thu, 15 Dec 2005 15:21:37 -0500
>
> > Interesting... FWIW the FC4.netdev.6 kernel seems to be working fine
> > on (a yet-to-be-released box), which is an x86_64 (AMD) box w/
> >
From: "John W. Linville" <[EMAIL PROTECTED]>
Date: Thu, 15 Dec 2005 15:21:37 -0500
> Interesting... FWIW the FC4.netdev.6 kernel seems to be working fine
> on (a yet-to-be-released box), which is an x86_64 (AMD) box w/
> forcedeth hardware. The forcedeth.c in the FC4.netdev.6 kernel is
> identic
On Thu, Dec 15, 2005 at 05:50:50PM +0100, Andi Kleen wrote:
> On Thu, Dec 15, 2005 at 11:40:08AM -0500, John W. Linville wrote:
> > On Thu, Dec 15, 2005 at 04:29:04PM +0100, Andi Kleen wrote:
> > >
> > > Hallo,
> > >
> > > When I boot a kernel with iommu=force (this forces all pci_map_sgs
> > > t
On Thu, Dec 15, 2005 at 11:40:08AM -0500, John W. Linville wrote:
> On Thu, Dec 15, 2005 at 04:29:04PM +0100, Andi Kleen wrote:
> >
> > Hallo,
> >
> > When I boot a kernel with iommu=force (this forces all pci_map_sgs
> > through the K8 aperture) and slab debugging on a Nforce4 x86-64
> > system
On Thu, Dec 15, 2005 at 04:29:04PM +0100, Andi Kleen wrote:
>
> Hallo,
>
> When I boot a kernel with iommu=force (this forces all pci_map_sgs
> through the K8 aperture) and slab debugging on a Nforce4 x86-64
> system the network corrupts data very quickly. Even when just
> sshing somewhere ssh qu
Hallo,
When I boot a kernel with iommu=force (this forces all pci_map_sgs
through the K8 aperture) and slab debugging on a Nforce4 x86-64
system the network corrupts data very quickly. Even when just
sshing somewhere ssh quickly aborts with MAC errors etc.
Reverting only forcedeth.c to the one f
11 matches
Mail list logo
