I too was having issues with the new ACPI patch; lost interrupt errors with my promise controller and no network.Evil Dark Archon wrote:finally found the real culprit, the new acpi patch in mm2 is what was causing the problem, it kept giving errors about i8xxx(don't remember the numbers i know it has something to do with the ps/2 mouse port) and disabling interrupt 12 and also the siimage lost interrupt problem. Now that all that is sorted out (by disabling acpi) its running good, and as an added bonus its doing so faster than -love3.
Code: Select all
USE="freedom -software_patents" emerge --deep --update world

So you aplly it to 2.6.1 or you could just use the provided ebuild =)Patch Name: patch-2.6.2-rc2
Description: The latest prepatch for the 2.6 tree
Testing: Patch applies cleanly and compiles cleanly
Patch Name: 2.6.2-rc2-mm1
Description: The latest from Andrew Morton
Testing: Patch applies cleanly and compiles cleanly
me too and OneOfOne too . I guess that we are using intel motherboards.pdptrojan wrote:With this kernel, my hard driver thrashes like crazy and i have very poor responsivness when at 100% cpu. This didn't happen in the 2.6.2_rc1 love sources. Like some other people, an hdparm -tT shows terrible speeds in comparison before (and yes, all the dma etc. is working). Anybody know why this is or what I can do to fix it?
I also have this problem, anyone tried vanilla 2.6.2-rc2 or mm to se where the problem was added?ed0n wrote:me too and OneOfOne too . I guess that we are using intel motherboards.pdptrojan wrote:With this kernel, my hard driver thrashes like crazy and i have very poor responsivness when at 100% cpu. This didn't happen in the 2.6.2_rc1 love sources. Like some other people, an hdparm -tT shows terrible speeds in comparison before (and yes, all the dma etc. is working). Anybody know why this is or what I can do to fix it?
That's why I also got back to love1.


nsahoo wrote:my mouse is still getting stuck. it happens every 5-10 mins. when i unplug and plug the mouse again, it starts working but for next 10 mins or so. I am using MS intellimouse (optical, USB, 5 button). Any help?
I switched to 2.6.0-test11 and the problem was gone. Now I am in 2.6.1-gentoo-r1 and the problem hasn't happened in last 15-20 mins. May be one of these patches did it.Evil Dark Archon wrote:are you sure that you have eliminated all other possible problems other than the kernel, it may be a problem with the mouse itself, does it work if you boot into a previous version, could you post your .config file.

I noticed the same problem in 2.6.2-rc2-mm1, will be trying vanilla and see if the problem comes from there or if it was introduced in mm.d99ma wrote:I also have this problem, anyone tried vanilla 2.6.2-rc2 or mm to se where the problem was added?ed0n wrote:me too and OneOfOne too . I guess that we are using intel motherboards.pdptrojan wrote:With this kernel, my hard driver thrashes like crazy and i have very poor responsivness when at 100% cpu. This didn't happen in the 2.6.2_rc1 love sources. Like some other people, an hdparm -tT shows terrible speeds in comparison before (and yes, all the dma etc. is working). Anybody know why this is or what I can do to fix it?
That's why I also got back to love1.


Code: Select all
CHK include/linux/compile.h
LD init/built-in.o
LD arch/i386/kernel/built-in.o
CC [M] drivers/net/r8169.o
drivers/net/r8169.c:420: `RxUnderrun' undeclared here (not in a function)
drivers/net/r8169.c: In function `rtl8169_print_mac_version':
drivers/net/r8169.c:509: warning: implicit declaration of function `dprintk'
drivers/net/r8169.c: In function `rtl8169_phy_timer':
drivers/net/r8169.c:677: `RTL8169_PHY_TIMEOUT' undeclared (first use in this function)
drivers/net/r8169.c:677: (Each undeclared identifier is reported only once
drivers/net/r8169.c:677: for each function it appears in.)
drivers/net/r8169.c: In function `rtl8169_request_timer':
drivers/net/r8169.c:706: `RTL8169_PHY_TIMEOUT' undeclared (first use in this function)
drivers/net/r8169.c: In function `rtl8169_init_one':
drivers/net/r8169.c:880: `RTL8169_TX_TIMEOUT' undeclared (first use in this function)
drivers/net/r8169.c: In function `rtl8169_open':
drivers/net/r8169.c:1104: `R8169_TX_RING_BYTES' undeclared (first use in this function)
drivers/net/r8169.c:1109: `R8169_RX_RING_BYTES' undeclared (first use in this function)
drivers/net/r8169.c: In function `rtl8169_hw_start':
drivers/net/r8169.c:1155: `EarlyTxThres' undeclared (first use in this function)
drivers/net/r8169.c:1155: `EarlyTxThld' undeclared (first use in this function)
drivers/net/r8169.c: In function `rtl8169_try_rx_copy':
drivers/net/r8169.c:1466: `rx_copybreak' undeclared (first use in this function)
drivers/net/r8169.c: In function `rtl8169_interrupt':
drivers/net/r8169.c:1584: `priv' undeclared (first use in this function)
drivers/net/r8169.c: In function `rtl8169_close':
drivers/net/r8169.c:1622: structure has no member named `phy_timer_t'
drivers/net/r8169.c:1646: structure has no member named `TxDescArrays'
drivers/net/r8169.c:1647: structure has no member named `RxDescArrays'
drivers/net/r8169.c:1648: structure has no member named `TxDescArrays'
drivers/net/r8169.c:1649: structure has no member named `RxDescArrays'
drivers/net/r8169.c:1656: warning: implicit declaration of function `RTL8169_FREE_RXSKB'
drivers/net/r8169.c: In function `rtl8169_set_rx_mode':
drivers/net/r8169.c:1721: warning: passing arg 2 of `set_bit' from incompatible pointer type
drivers/net/r8169.c: At top level:
drivers/net/r8169.c:1046: warning: `rtl8169_suspend' defined but not used
drivers/net/r8169.c:1072: warning: `rtl8169_resume' defined but not used
make[2]: *** [drivers/net/r8169.o] Error 1
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
I'm going to try the gentoo-dev-sources and se how they work. Keep us posted on vanilla-performance. Seems unlikley that such a noticable bug would be in the main tree though.silverter wrote:I noticed the same problem in 2.6.2-rc2-mm1, will be trying vanilla and see if the problem comes from there or if it was introduced in mm.d99ma wrote:I also have this problem, anyone tried vanilla 2.6.2-rc2 or mm to se where the problem was added?ed0n wrote:me too and OneOfOne too . I guess that we are using intel motherboards.pdptrojan wrote:With this kernel, my hard driver thrashes like crazy and i have very poor responsivness when at 100% cpu. This didn't happen in the 2.6.2_rc1 love sources. Like some other people, an hdparm -tT shows terrible speeds in comparison before (and yes, all the dma etc. is working). Anybody know why this is or what I can do to fix it?
That's why I also got back to love1.