[EMAIL PROTECTED] wrote:
>
> Hi,
>
> I thought this problem has been fixed but apparently not in 2.6.11.7.
> Is there any patch for it ? Thanks
>
>
Are you sure the ip_conntrack itself isn't ACTUALLY full? Have you tried
increase this increasing this via
So, heres what I do
cd /usr/src/linux
make mrproper
cp arch/ppc64/configs/pSeries_defconfig .config
make menuconfig
make dep
make clean
make vmlinux
Eventually it bombs out with several messages such as:
ioctl32.c:X: error: (near initialization for `ioctl_translations[Y]')
Culminating in :
So, heres what I do
cd /usr/src/linux
make mrproper
cp arch/ppc64/configs/pSeries_defconfig .config
make menuconfig
exit
make dep
make clean
make vmlinux
Eventually it bombs out with several messages such as:
ioctl32.c:X: error: (near initialization for `ioctl_translations[Y]')
Culminating in
[EMAIL PROTECTED] wrote:
Hi,
I thought this problem has been fixed but apparently not in 2.6.11.7.
Is there any patch for it ? Thanks
Are you sure the ip_conntrack itself isn't ACTUALLY full? Have you tried
increase this increasing this via
/proc/sys/net/ipv4/netfilter/ip_conntrack_max?
O
Benjamin Herrenschmidt wrote:
On Thu, 2005-03-10 at 11:05 -0600, Omkhar Arasaratnam wrote:
2.6.10 seems to have a different kernel panic which I'm investigating
(could be a problem with my ramdisk as it happens in my linuxrc). So
long story short the 2.6.10 sym driver looks ok.
Can you
Benjamin Herrenschmidt wrote:
On Thu, 2005-03-10 at 11:05 -0600, Omkhar Arasaratnam wrote:
2.6.10 seems to have a different kernel panic which I'm investigating
(could be a problem with my ramdisk as it happens in my linuxrc). So
long story short the 2.6.10 sym driver looks ok.
Can you
Benjamin Herrenschmidt wrote:
On Thu, 2005-03-10 at 11:05 -0600, Omkhar Arasaratnam wrote:
2.6.10 seems to have a different kernel panic which I'm investigating
(could be a problem with my ramdisk as it happens in my linuxrc). So
long story short the 2.6.10 sym driver looks ok.
Can you
Benjamin Herrenschmidt wrote:
On Thu, 2005-03-10 at 11:05 -0600, Omkhar Arasaratnam wrote:
2.6.10 seems to have a different kernel panic which I'm investigating
(could be a problem with my ramdisk as it happens in my linuxrc). So
long story short the 2.6.10 sym driver looks ok.
Can you
Benjamin Herrenschmidt wrote:
On Thu, 2005-03-10 at 11:05 -0600, Omkhar Arasaratnam wrote:
2.6.10 seems to have a different kernel panic which I'm investigating
(could be a problem with my ramdisk as it happens in my linuxrc). So
long story short the 2.6.10 sym driver looks ok.
Can you
Benjamin Herrenschmidt wrote:
On Thu, 2005-03-10 at 11:05 -0600, Omkhar Arasaratnam wrote:
2.6.10 seems to have a different kernel panic which I'm investigating
(could be a problem with my ramdisk as it happens in my linuxrc). So
long story short the 2.6.10 sym driver looks ok.
Can you
James Bottomley wrote:
On Thu, 2005-03-10 at 12:17 +, Matthew Wilcox wrote:
Heh, the devel version of sym2 (that isn't submitted yet because
it depends on a few changes to the SPI transport that James hasn't
integrated yet) would probably fix this as it doesn't call iounmap()
until the
James Bottomley wrote:
On Thu, 2005-03-10 at 12:17 +, Matthew Wilcox wrote:
Heh, the devel version of sym2 (that isn't submitted yet because
it depends on a few changes to the SPI transport that James hasn't
integrated yet) would probably fix this as it doesn't call iounmap()
until the
Linus Torvalds wrote:
There are certainly sym changes in there too since 2.6.9, let's see if
James or Willy have any suggestions. It might not be ppc64-specific.
Linus
I have tried with 2.6.10, this appears to fail as well. Unfortunately I
don't have console access right now
Omkhar Arasaratnam wrote:
Benjamin Herrenschmidt wrote:
Are you sure it's plain 2.6.11 and not some bk clone of after 2.6.11 was
released ?
Ben - I am in the process of downloading a clean tarball from
kernel.org to be 100% certain.
I confirmed that this occurs with the 2.6.11 code straight
Benjamin Herrenschmidt wrote:
Are you sure it's plain 2.6.11 and not some bk clone of after 2.6.11 was
released ?
Ben - I am in the process of downloading a clean tarball from kernel.org
to be 100% certain.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body
Seems with 2.6.11 the sym53c8xx kernel module incorrectly identifies the
cache being misconfigured on a p630 (ppc64, POWER4+). 2.6.9 correctly
brings up this adaptor as does AIX with absolutely no indication of a
misconfigured cache.
Doing a simple diff I see ALOT of changes between 2.6.9 and
Seems with 2.6.11 the sym53c8xx kernel module incorrectly identifies the
cache being misconfigured on a p630 (ppc64, POWER4+). 2.6.9 correctly
brings up this adaptor as does AIX with absolutely no indication of a
misconfigured cache.
Doing a simple diff I see ALOT of changes between 2.6.9 and
Benjamin Herrenschmidt wrote:
Are you sure it's plain 2.6.11 and not some bk clone of after 2.6.11 was
released ?
Ben - I am in the process of downloading a clean tarball from kernel.org
to be 100% certain.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
Omkhar Arasaratnam wrote:
Benjamin Herrenschmidt wrote:
Are you sure it's plain 2.6.11 and not some bk clone of after 2.6.11 was
released ?
Ben - I am in the process of downloading a clean tarball from
kernel.org to be 100% certain.
I confirmed that this occurs with the 2.6.11 code straight
Linus Torvalds wrote:
There are certainly sym changes in there too since 2.6.9, let's see if
James or Willy have any suggestions. It might not be ppc64-specific.
Linus
I have tried with 2.6.10, this appears to fail as well. Unfortunately I
don't have console access right now
20 matches
Mail list logo
