of figuring out what's going on,
and neither does Joe libata Developer unless they really care to dig
through the spec and count bits to figure out what they mean. At least
with this you can see that there was a CRC error, etc. and go from that..
--
Robert Hancock Saskatoon, SK, Canada
To email
output. With libata errors, if they're at the console (which they'd have
to be to see these messages), unless something has actually caused a
panic the scrollback buffer should still be functional and they'd be
able to see the entire output..
--
Robert Hancock Saskatoon, SK, Canada
To email
looking at error
reports. Some bits that drivers/ide decoded are not decoded here, since the bits
are either command-dependent or obsolete, and properly parsing them would add
too much complexity.
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.21.1/drivers/ata/libat
the Transport layer since the last time this bit was cleared."
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"
Ben Collins wrote:
On Tue, 2007-05-08 at 08:46 -0600, Robert Hancock wrote:
Ben Collins wrote:
The original HPA patch that Kyle worked on has gone into current git
without some fixes that we worked through late in the Ubuntu feisty
release. Here's the main copy of the notes I sent to Alan
split and reducing the kernel memory available so much.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
split and reducing the kernel memory available so much.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Ben Collins wrote:
On Tue, 2007-05-08 at 08:46 -0600, Robert Hancock wrote:
Ben Collins wrote:
The original HPA patch that Kyle worked on has gone into current git
without some fixes that we worked through late in the Ubuntu feisty
release. Here's the main copy of the notes I sent to Alan
time this bit was cleared.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
looking at error
reports. Some bits that drivers/ide decoded are not decoded here, since the bits
are either command-dependent or obsolete, and properly parsing them would add
too much complexity.
Signed-off-by: Robert Hancock [EMAIL PROTECTED]
--- linux-2.6.21.1/drivers/ata/libata-eh.c 2007
ted to libata-dev).
We've not had any reports of further problems.
That sata_nv issue should not be present anymore in the current
libata-dev tree.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To uns
to libata-dev).
We've not had any reports of further problems.
That sata_nv issue should not be present anymore in the current
libata-dev tree.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from
don't want to use polling).
Is there a way to listen-in on multiple kernel sockets from one kernel
thread? In the user space I would have used select(), but I am not
familiar with a similar solution for the kernel space.
Thanks,
Eitan.
Eitan Richardson
AudioCodes Ltd.
--
Robert Hancock
don't want to use polling).
Is there a way to listen-in on multiple kernel sockets from one kernel
thread? In the user space I would have used select(), but I am not
familiar with a similar solution for the kernel space.
Thanks,
Eitan.
Eitan Richardson
AudioCodes Ltd.
--
Robert Hancock
drivers/ide ever really played well when built modular, at
least not in 2.4, quite possibly in 2.6 as well. Things like DMA not
getting turned on automatically when the low-level driver was a module,
etc. Likely why Red Hat/Fedora never built it modular when they did
everything else..
--
R
ADMA status if the port has ADMA switched off because of an ATAPI device, and
it also checks to see if any ADMA interrupt has been raised even when we are in
port-register mode.
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.21.1/drivers/ata/sata_nv.c2007-04-27
ADMA status if the port has ADMA switched off because of an ATAPI device, and
it also checks to see if any ADMA interrupt has been raised even when we are in
port-register mode.
Signed-off-by: Robert Hancock [EMAIL PROTECTED]
--- linux-2.6.21.1/drivers/ata/sata_nv.c2007-04-27 15:49
modular, at
least not in 2.4, quite possibly in 2.6 as well. Things like DMA not
getting turned on automatically when the low-level driver was a module,
etc. Likely why Red Hat/Fedora never built it modular when they did
everything else..
--
Robert Hancock Saskatoon, SK, Canada
To email
that will
track down the one that is causing the lockup, if it is an actual
MMCONFIG access that's doing it..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "un
that will
track down the one that is causing the lockup, if it is an actual
MMCONFIG access that's doing it..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux
Jesse Barnes wrote:
On Wednesday, May 2, 2007 7:34 am Robert Hancock wrote:
Jesse Barnes wrote:
On Tuesday, May 01, 2007, Jesse Barnes wrote:
I'm testing it now on my 965...
Bah... nevermind Robert, I see you're doing this already in
pci_mmcfg_reject_broken. I'm about to reboot & test
days..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
Jesse Barnes wrote:
On Wednesday, May 2, 2007 7:34 am Robert Hancock wrote:
Jesse Barnes wrote:
On Tuesday, May 01, 2007, Jesse Barnes wrote:
I'm testing it now on my 965...
Bah... nevermind Robert, I see you're doing this already in
pci_mmcfg_reject_broken. I'm about to reboot test now
Jesse Barnes wrote:
On Monday, April 30, 2007 4:20 pm Robert Hancock wrote:
Right, but you patch should obsolete this stuff anyway. I'll test
it out in the next few days.
We likely still want this chipset-specific support, it will catch the
case where the MCFG table lists a location which
Jesse Barnes wrote:
On Monday, April 30, 2007 4:20 pm Robert Hancock wrote:
Right, but you patch should obsolete this stuff anyway. I'll test
it out in the next few days.
We likely still want this chipset-specific support, it will catch the
case where the MCFG table lists a location which
Olivier Galibert wrote:
On Sun, Apr 29, 2007 at 08:14:37PM -0600, Robert Hancock wrote:
-Validate that the area is reserved even if we read it from the
chipset directly and not from the MCFG table. This catches the case
where the BIOS didn't set the location properly in the chipset and
has
Jesse Barnes wrote:
On Sunday, April 29, 2007 7:10 pm Robert Hancock wrote:
Jesse Barnes wrote:
Add support for Intel 915 bridge chips to the new PCI MMConfig
detection code. Tested and works on my sole 915 based platform (a
Toshiba laptop). I added register masking per Oliver's suggestion
this.
It seems they've left those chipsets out in the cold, as we have ADMA
support on the nForce4 and the latest 6-series chipsets apparently
support AHCI..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberth
this.
It seems they've left those chipsets out in the cold, as we have ADMA
support on the nForce4 and the latest 6-series chipsets apparently
support AHCI..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com
Jesse Barnes wrote:
On Sunday, April 29, 2007 7:10 pm Robert Hancock wrote:
Jesse Barnes wrote:
Add support for Intel 915 bridge chips to the new PCI MMConfig
detection code. Tested and works on my sole 915 based platform (a
Toshiba laptop). I added register masking per Oliver's suggestion
Olivier Galibert wrote:
On Sun, Apr 29, 2007 at 08:14:37PM -0600, Robert Hancock wrote:
-Validate that the area is reserved even if we read it from the
chipset directly and not from the MCFG table. This catches the case
where the BIOS didn't set the location properly in the chipset and
has
-by: Robert Hancock <[EMAIL PROTECTED]>
diff -up linux-2.6.21.1/arch/i386/pci/init.c
linux-2.6.21.1edit/arch/i386/pci/init.c
--- linux-2.6.21.1/arch/i386/pci/init.c 2007-04-27 15:49:26.0 -0600
+++ linux-2.6.21.1edit/arch/i386/pci/init.c 2007-04-29 18:36:32.0
-0600
@@
TEL_82915GM_HB,
pci_mmcfg_intel_915 },
{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82945G_HB,
pci_mmcfg_intel_945 },
};
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this
Jesse Barnes wrote:
On Sunday, April 29, 2007, Robert Hancock wrote:
Problem is that even if we read the MMCONFIG table location from the
hardware registers, that doesn't mean we can trust the result. It could
be that the BIOS hasn't lied about where it put the table, it just stuck
it someplace
r solution.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo i
wants to allocate memory and use other kernel services that
are not available in really early boot. It could be probably done somehow,
but would be quite ugly with lots of special cases.
Yeah, if we can do this part of MMCONFIG initialization later that would
likely be a better solution.
--
Robert
Jesse Barnes wrote:
On Sunday, April 29, 2007, Robert Hancock wrote:
Problem is that even if we read the MMCONFIG table location from the
hardware registers, that doesn't mean we can trust the result. It could
be that the BIOS hasn't lied about where it put the table, it just stuck
it someplace
},
{ PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_82945G_HB,
pci_mmcfg_intel_945 },
};
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
-by: Robert Hancock [EMAIL PROTECTED]
diff -up linux-2.6.21.1/arch/i386/pci/init.c
linux-2.6.21.1edit/arch/i386/pci/init.c
--- linux-2.6.21.1/arch/i386/pci/init.c 2007-04-27 15:49:26.0 -0600
+++ linux-2.6.21.1edit/arch/i386/pci/init.c 2007-04-29 18:36:32.0
-0600
@@ -12,7 +12,7
Chuck Ebbert wrote:
Robert Hancock wrote:
I've seen a lot of systems (including brand new Xeon-based servers from
IBM and HP) that output messages on boot like:
PCI: BIOS Bug: MCFG area at f000 is not E820-reserved
PCI: Not using MMCONFIG.
So Microsoft is explicitly telling the BIOS
Chuck Ebbert wrote:
Robert Hancock wrote:
I've seen a lot of systems (including brand new Xeon-based servers from
IBM and HP) that output messages on boot like:
PCI: BIOS Bug: MCFG area at f000 is not E820-reserved
PCI: Not using MMCONFIG.
So Microsoft is explicitly telling the BIOS
proper mappings, this will blow up if it tries to access memory above
the 4GB mark if the device cannot do >32bit DMA..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from th
proper mappings, this will blow up if it tries to access memory above
the 4GB mark if the device cannot do 32bit DMA..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send
ough it
has locked the mutex even though it has not.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mess
like the aha1542 driver doesn't set the DMA mask, so the kernel
will default to thinking it can do 32-bit DMA when it should be 24-bit.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubs
like the aha1542 driver doesn't set the DMA mask, so the kernel
will default to thinking it can do 32-bit DMA when it should be 24-bit.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from
the mutex even though it has not.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
[] _spin_lock_irqsave+0x9/0xd
[] __wake_up+0x18/0x43
[] __wake_up_bit+0x2e/0x33
[] shrink_inactive_list+0x483/0x6c9
RAM issues are a possibility for this sort of problem, tried running
Memtest86+?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home
] _spin_lock_irqsave+0x9/0xd
[c041febf] __wake_up+0x18/0x43
[c04379ce] __wake_up_bit+0x2e/0x33
[c045a496] shrink_inactive_list+0x483/0x6c9
RAM issues are a possibility for this sort of problem, tried running
Memtest86+?
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from
without ACPI anymore, so going without ACPI can be
problematic.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
without ACPI anymore, so going without ACPI can be
problematic.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
of
that header has everything inside #ifdef __KERNEL__ stripped out.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
t
of that header. The userspace version of
that header has everything inside #ifdef __KERNEL__ stripped out.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux
covered under the GPL).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
and thus
covered under the GPL).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
hat basis it doesn't seem like a valid check to
require it to be so reserved, then.
Really, I think we should be basing this check on whether the
corresponding memory range is reserved in the ACPI resources, like
Windows expects. This does require putting more fingers into ACPI from
this early bo
#include
#endif
Did I missed something? Please guide me how to fix it.
Sincerely
You're trying to use a kernel data structure in a user-space program.
Don't. The definitions in that header are inside #ifdef __KERNEL__ and
so the provided userspace headers remove that part.
--
Robe
amount of SATA fixes backported from 2.6.21...
News to me.. pleast post details.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kern
Some drives seem to spin up at step #3 even when its cache is clean and
power goes off right after the disk finishes the command. So, it's
really bad when it happens - spin down, spin up followed by immediate
power off.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam&
) is much greater than the number of people
running a SAN, multi-initiator, etc. environment where you might not
want this..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from
,
Steve
That patch on its own will not help, you also need Tejun's
stop-on-shutdown patch, otherwise the kernel will not try to stop the
disk before powering off.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home
of the drive and controller just not getting along,
but you might want to try a different SATA cable as well.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line &q
of the drive and controller just not getting along,
but you might want to try a different SATA cable as well.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux
,
Steve
That patch on its own will not help, you also need Tejun's
stop-on-shutdown patch, otherwise the kernel will not try to stop the
disk before powering off.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com
) is much greater than the number of people
running a SAN, multi-initiator, etc. environment where you might not
want this..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send
Some drives seem to spin up at step #3 even when its cache is clean and
power goes off right after the disk finishes the command. So, it's
really bad when it happens - spin down, spin up followed by immediate
power off.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL
amount of SATA fixes backported from 2.6.21...
News to me.. pleast post details.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
check to
require it to be so reserved, then.
Really, I think we should be basing this check on whether the
corresponding memory range is reserved in the ACPI resources, like
Windows expects. This does require putting more fingers into ACPI from
this early boot stage, though..
--
Robert Hancock
this problem in Linux on the X86 plateform???
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message
region above 3GB
preventing RAM from being mapped there, and doesn't support remapping
the covered RAM to above 4GB. Nothing the kernel can do about it.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberth
region above 3GB
preventing RAM from being mapped there, and doesn't support remapping
the covered RAM to above 4GB. Nothing the kernel can do about it.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com
this problem in Linux on the X86 plateform???
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
such a problem.
So now we wonder if this might be an MCE bug, or really a HW problem,
and if it is one of the CPUs, or the RAM thats faulty.
We are running 2.6.18.
Sounds like some bad RAM..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home
such a problem.
So now we wonder if this might be an MCE bug, or really a HW problem,
and if it is one of the CPUs, or the RAM thats faulty.
We are running 2.6.18.
Sounds like some bad RAM..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http
hed() voluntarily since CONFIG_PREEMPT_VOLUNTARY and
CONFIG_PREEMPT_BKL are both turned on? From my understanding these 2
options should make schedule happen even if CPU is under heavy
load..
No, only CONFIG_PREEMPT will do that.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove &quo
dn't
have to, and yet the drive loses power so it does an emergency retract.
Making the kernel shutdown on reboot would only add more spindown/up
cycles for normally working systems.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTEC
to, and yet the drive loses power so it does an emergency retract.
Making the kernel shutdown on reboot would only add more spindown/up
cycles for normally working systems.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http
() voluntarily since CONFIG_PREEMPT_VOLUNTARY and
CONFIG_PREEMPT_BKL are both turned on? From my understanding these 2
options should make schedule happen even if CPU is under heavy
load..
No, only CONFIG_PREEMPT will do that.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from
to disable the pagecache?
Not as far as I know, it's unlikely this would be of any benefit.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscri
to disable the pagecache?
Not as far as I know, it's unlikely this would be of any benefit.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
/WhyWritingFilesFromKernelIsBad
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More maj
/WhyWritingFilesFromKernelIsBad
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
to be personally CC'ed in the answers/comments posted in
response to this post ?
Your compiler is probably too new to be able to compile 2.6.9. You'd
likely be better off trying the latest kernels and making a detailed
report of the problems you're having with it..
--
Robert Hancock Saskatoon
(defective RAM? Bad application or device
driver?), please let me know as I'm pulling what
little hair I have left out on this one. Suggestions
on what to try would be greatly appreciated. Thanks!
First try updating to the latest RHEL update kernel, that one's out of date.
--
Robert Hancock
(defective RAM? Bad application or device
driver?), please let me know as I'm pulling what
little hair I have left out on this one. Suggestions
on what to try would be greatly appreciated. Thanks!
First try updating to the latest RHEL update kernel, that one's out of date.
--
Robert Hancock
to be personally CC'ed in the answers/comments posted in
response to this post ?
Your compiler is probably too new to be able to compile 2.6.9. You'd
likely be better off trying the latest kernels and making a detailed
report of the problems you're having with it..
--
Robert Hancock Saskatoon
share a physical interrupt line
and there is no way to separate them in software. You can try moving the
card(s) to different slots..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubs
share a physical interrupt line
and there is no way to separate them in software. You can try moving the
card(s) to different slots..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from
is
"make modules_install install".
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a mes
Jeff Garzik wrote:
Robert Hancock wrote:
This adds some NCQ blacklist entries taken from the Silicon Image
3124/3132
Windows driver .inf files. There are some confirming reports of problems
with these drives under Linux (for example
http://lkml.org/lkml/2007/3/4/178)
so let's disable NCQ
Jeff Garzik wrote:
Robert Hancock wrote:
This adds some NCQ blacklist entries taken from the Silicon Image
3124/3132
Windows driver .inf files. There are some confirming reports of problems
with these drives under Linux (for example
http://lkml.org/lkml/2007/3/4/178)
so let's disable NCQ
is
make modules_install install.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
B keyboard/mouse on the same hub would prevent it from getting enough
bandwidth.
Essentially the driver should fallback to a lower-bandwidth descriptor
if the one it tries to use fails rather than just bailing out.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nosp
is disabled you can't take advantage
of CPU clock frequency scaling to save power.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line "unsubscri
is disabled you can't take advantage
of CPU clock frequency scaling to save power.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
/mouse on the same hub would prevent it from getting enough
bandwidth.
Essentially the driver should fallback to a lower-bandwidth descriptor
if the one it tries to use fails rather than just bailing out.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED
This adds some NCQ blacklist entries taken from the Silicon Image 3124/3132
Windows driver .inf files. There are some confirming reports of problems
with these drives under Linux (for example http://lkml.org/lkml/2007/3/4/178)
so let's disable NCQ on these drives.
Signed-off-by: Robert Hancock
This adds some NCQ blacklist entries taken from the Silicon Image 3124/3132
Windows driver .inf files. There are some confirming reports of problems
with these drives under Linux (for example http://lkml.org/lkml/2007/3/4/178)
so let's disable NCQ on these drives.
Signed-off-by: Robert Hancock
901 - 1000 of 1555 matches
Mail list logo
