On Wed, 30 Mar 2005, H. J. Lu wrote:
That is what the assembler generates, and should have generated, for
"movw %ds,(%eax)" since Nov. 4, 2004.
Could this be the reason for the reported slowdown in the last six months?
Can you elaborate?
There's an unexplained slowdown of kernel 2.6 detailed in
On Wed, 30 Mar 2005, H. J. Lu wrote:
On Wed, Mar 30, 2005 at 07:57:28AM -0800, Linus Torvalds wrote:
There is no such an instruction of "movl %ds,(%eax)". The old assembler
accepts it and turns it into "movw %ds,(%eax)".
I disagree. Violently. As does the old assembler, which does not turn
"mov"
On Wed, 30 Mar 2005, H. J. Lu wrote:
On Wed, Mar 30, 2005 at 07:57:28AM -0800, Linus Torvalds wrote:
There is no such an instruction of movl %ds,(%eax). The old assembler
accepts it and turns it into movw %ds,(%eax).
I disagree. Violently. As does the old assembler, which does not turn
mov into
On Wed, 30 Mar 2005, H. J. Lu wrote:
That is what the assembler generates, and should have generated, for
movw %ds,(%eax) since Nov. 4, 2004.
Could this be the reason for the reported slowdown in the last six months?
Can you elaborate?
There's an unexplained slowdown of kernel 2.6 detailed in this
Since 2.2.4-ac28 and 2.4.3 I keep on getting processes in D state that I
cannot kill, usually mozilla or nautilus which use a large amount of RAM.
Today is galeon:
A ps -eo pid,stat,pcpu,nwchan,wchan=WIDE-WCHAN-COLUMN -o args shows the
following:
11520 D 0.0 105db1 down_write_failed
Since 2.2.4-ac28 and 2.4.3 I keep on getting processes in D state that I
cannot kill, usually mozilla or nautilus which use a large amount of RAM.
Today is galeon:
A ps -eo pid,stat,pcpu,nwchan,wchan=WIDE-WCHAN-COLUMN -o args shows the
following:
11520 D 0.0 105db1 down_write_failed
On Wed, 28 Mar 2001, David Brownell wrote:
> Same problem shows up with most of the USB network
> drivers too. /proc/ksyms has the macro-wrapped version
> of those names, not the mangled one.
>
> Haven't established whether there's a problem when these
> drivers are statically linked.
I've
On Wed, 28 Mar 2001, David Brownell wrote:
Same problem shows up with most of the USB network
drivers too. /proc/ksyms has the macro-wrapped version
of those names, not the mangled one.
Haven't established whether there's a problem when these
drivers are statically linked.
I've been sent
I've tried 2.4.2-ac26 to test the new xircom_cb driver but I have had to
reboot on 2.4.3-pre7 as some processes got stuck on D state.
The processes were large apps: once nautilus and once mozilla.
I couldn't get any other information.
Pau
-
To unsubscribe from this list: send the line
I've tried 2.4.2-ac26 to test the new xircom_cb driver but I have had to
reboot on 2.4.3-pre7 as some processes got stuck on D state.
The processes were large apps: once nautilus and once mozilla.
I couldn't get any other information.
Pau
-
To unsubscribe from this list: send the line
On 13 Feb 2001, Stig Brautaset wrote:
> I have a Xircom Combo CardBus (32 bit) 10/100 Ethernet Card + 56k
> Modem (didn't try the modem part) that I have not been able to run
> under 2.2.18 or 2.4.0. The weird part is that everything seems to load
> fine, and I am able to configure the card with
On 13 Feb 2001, Stig Brautaset wrote:
I have a Xircom Combo CardBus (32 bit) 10/100 Ethernet Card + 56k
Modem (didn't try the modem part) that I have not been able to run
under 2.2.18 or 2.4.0. The weird part is that everything seems to load
fine, and I am able to configure the card with an
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-prerelease/kernel/drivers/net/irda/toshoboe.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-prerelease/kernel/drivers/video/atyfb.o
depmod: __bad_udelay
Pau
-
To unsubscribe from this list: send
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-prerelease/kernel/drivers/net/irda/toshoboe.o
depmod: __bad_udelay
depmod: *** Unresolved symbols in
/lib/modules/2.4.0-prerelease/kernel/drivers/video/atyfb.o
depmod: __bad_udelay
Pau
-
To unsubscribe from this list: send
14 matches
Mail list logo
