Hello, David S. Miller.
On 31.03.2006 13:12 you said the following:
From: "Boris B. Zhmurov" <[EMAIL PROTECTED]>
Date: Thu, 30 Mar 2006 17:29:09 +0400
Hello, Herbert Xu.
On 30.03.2006 14:12 you said the following:
On Thu, Mar 30, 2006 at 10:02:01AM +0000, Boris B. Zhmurov wrote:
[EMAIL PROTECTED] linux-2.6.16]$ patch -p1 <
../../../SOURCES/linux-2.6.16-e1000-try-to-fix-assertion_sk_forward_alloc_failed_by_Herbert_Xu.patch
patching file drivers/net/e1000/e1000_main.c
Reversed (or previously applied) patch detected! Assume -R? [n]
Herbert, is that patch already included in 2.6.16.1?
Not really. It's just patch being silly (or too smart :)
Here it is again rediffed against 2.6.16.
Nope, with this patch the problem still exists. After 25 min. uptime
with patched kernel 2.6.16.1, I have:
Can you please double and triple check that you're really running a
kernel with the fix from Herbert applied? I make this mistake all
the time :-)
Thanks.
[EMAIL PROTECTED] redhat]$ rpmbuild --sign --rebuild --target=i686
/usr/src/redhat/SRPMS/kernel-2.6.16-1.14.bbel4.src.rpm
Enter pass phrase:
Pass phrase is good.
..... SKIP.....
+ echo 'Patch #295
(linux-2.6.16-e1000-try-to-fix-assertion_sk_forward_alloc_failed_by_Herbert_Xu.patch):'
Patch #295
(linux-2.6.16-e1000-try-to-fix-assertion_sk_forward_alloc_failed_by_Herbert_Xu.patch):
+ patch -p1 -s
...... SKIP .....
And xdelta tells, that e1000.ko was modified :)
P.S.
there is src.rpm of my kernel for RHEL4 and my RHEL4-clone:
ftp://builds.kernelpanic.ru/pub/linux/BBEL/updates/kernel_of_the_day/4/SRPMS/
and yum'able repo of 2.6.16 kernels _with_ Herbert's patch :), if
anybody interested:
ftp://builds.kernelpanic.ru/pub/linux/BBEL/updates/kernel_of_the_day/4/
--
Boris B. Zhmurov
mailto: [EMAIL PROTECTED]
"wget http://kernelpanic.ru/bb_public_key.pgp -O - | gpg --import"
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
