Luming Yu wrote:
From the dmesg, I found a problem NOT relative to the PATA driver.
I would like to know if cpu freq driver works? If not, please enter a
acpi bug on bugzilla.kernel.org.
The acpi-cpufreq driver does work, but there are some other
ACPI-related problems. Most importantly for me,
Luming Yu wrote:
From the dmesg, I found a problem NOT relative to the PATA driver.
I would like to know if cpu freq driver works? If not, please enter a
acpi bug on bugzilla.kernel.org.
The acpi-cpufreq driver does work, but there are some other
ACPI-related problems. Most importantly for me,
Tejun Heo wrote:
* Does putting in a readable CD or DVD make any difference?
Yes, I ran for an hour with an audio CD in the drive and there were no timeouts.
* Does the problem occur in single mode where no HAL or whatever is running?
No, there were no timeouts in single mode even without
Andrew Morton wrote:
From what version of the kernel did you upgrade?
It is very helpful for us to knwo the latest version which worked OK.
The ata_piix driver never worked correctly. The last kernel I used,
2.6.17, used ide_generic by default, so the ata_piix bug never showed
up. Sorry if
Andrew Morton wrote:
From what version of the kernel did you upgrade?
It is very helpful for us to knwo the latest version which worked OK.
The ata_piix driver never worked correctly. The last kernel I used,
2.6.17, used ide_generic by default, so the ata_piix bug never showed
up. Sorry if
Tejun Heo wrote:
* Does putting in a readable CD or DVD make any difference?
Yes, I ran for an hour with an audio CD in the drive and there were no timeouts.
* Does the problem occur in single mode where no HAL or whatever is running?
No, there were no timeouts in single mode even without
What's the difference between synchronize_rcu() and rcu_barrier() (new
function used only by reiser4 code)? From the scant documentation it
seems like they do the same thing.
I'm now happily running 2.6.13-rc4-rt-v0.7.52-14-reiser4 which I compiled by
adding
#define rcu_barrier
What's the difference between synchronize_rcu() and rcu_barrier() (new function
used only by reiser4 code)? From the scant documentation it seems like they do
the same thing.
Keenan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL
What's the difference between synchronize_rcu() and rcu_barrier() (new function
used only by reiser4 code)? From the scant documentation it seems like they do
the same thing.
Keenan
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
What's the difference between synchronize_rcu() and rcu_barrier() (new
function used only by reiser4 code)? From the scant documentation it
seems like they do the same thing.
I'm now happily running 2.6.13-rc4-rt-v0.7.52-14-reiser4 which I compiled by
adding
#define rcu_barrier
Quiet some silly warnings.
--- linux-2.6.13-rc3-mm2/scripts/lxdialog/dialog.orig.h 2005-07-27
13:59:02.389806392 -0400
+++ linux-2.6.13-rc3-mm2/scripts/lxdialog/dialog.h 2005-07-27
13:59:13.437126944 -0400
@@ -163,7 +163,7 @@
int dialog_checklist (const char *title, const char *prompt,
Quiet some silly warnings.
--- linux-2.6.13-rc3-mm2/scripts/lxdialog/dialog.orig.h 2005-07-27
13:59:02.389806392 -0400
+++ linux-2.6.13-rc3-mm2/scripts/lxdialog/dialog.h 2005-07-27
13:59:13.437126944 -0400
@@ -163,7 +163,7 @@
int dialog_checklist (const char *title, const char *prompt,
Vladimir V. Saveliev wrote:
ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.12/reiser4-for-2.6.12-realtime-preempt-2.6.12-final-V0.7.51-29.patch.gz
It applies to 2.6.12 +
http://people.redhat.com/mingo/realtime-preempt/older/realtime-preempt-2.6.12-final-V0.7.51-29
Ah, this is just what I
Vladimir V. Saveliev wrote:
ftp://ftp.namesys.com/pub/reiser4-for-2.6/2.6.12/reiser4-for-2.6.12-realtime-preempt-2.6.12-final-V0.7.51-29.patch.gz
It applies to 2.6.12 +
http://people.redhat.com/mingo/realtime-preempt/older/realtime-preempt-2.6.12-final-V0.7.51-29
Ah, this is just what I
Lee Revell wrote:
Maybe you could apply the broken out reiser4 patches from -mm and the
realtime preempt patches. Testing with PREEMPT_DESKTOP and latency
tracing enabled will tell you whether reiser4 has any latency hot spots.
I'm trying this now and it's not exactly trivial; the patches
Ingo Molnar's realtime-preempt patches used to be based on the -mm
kernels, but now they appear to be based on the mainline kernels, so
they don't support reiser4 (at least until reiser4 is merged into
mainline, which is looking uncertain as I understand it).
Is
Lee Revell wrote:
Maybe you could apply the broken out reiser4 patches from -mm and the
realtime preempt patches. Testing with PREEMPT_DESKTOP and latency
tracing enabled will tell you whether reiser4 has any latency hot spots.
I'm trying this now and it's not exactly trivial; the patches
Ingo Molnar's realtime-preempt patches used to be based on the -mm
kernels, but now they appear to be based on the mainline kernels, so
they don't support reiser4 (at least until reiser4 is merged into
mainline, which is looking uncertain as I understand it).
Is
Sorry about that, we start to talk about it in private with Dave.
But, I did not really it since Keenan Pepper told me it was due
to a bug in the XFree 4.3 driver.
I am now using Xorg and didn't see any DRM problem since.
However, I can't confirm that my bug was surely due to the XFree driver
Sorry about that, we start to talk about it in private with Dave.
But, I did not really it since Keenan Pepper told me it was due
to a bug in the XFree 4.3 driver.
I am now using Xorg and didn't see any DRM problem since.
However, I can't confirm that my bug was surely due to the XFree driver
Oops, should have read all the messages before posting!
I'll try the fix you said, I knew it'd be something like that.
It's attached.
BTW, is attaching things like this the preferred method?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Oops, should have read all the messages before posting!
I'll try the fix you said, I knew it'd be something like that.
It's attached.
BTW, is attaching things like this the preferred method?
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Hi everybody, I just joined the LKML!
Don't worry, this is not just a test message, I do actually have
something to say. I just compiled 2.6.11-rc5-mm1 and got undefined
symbols "match_int", "match_octal", "match_token", and "match_strdup" in
several modules. This is using binutils 2.15 and gcc
Hi everybody, I just joined the LKML!
Don't worry, this is not just a test message, I do actually have
something to say. I just compiled 2.6.11-rc5-mm1 and got undefined
symbols match_int, match_octal, match_token, and match_strdup in
several modules. This is using binutils 2.15 and gcc 3.4.4
24 matches
Mail list logo
