+ not
installed !
==
While the output seems to suggest a hardware problem, the same system
loads the hisax driver perfectly on recent 2.4 kernels.
We tried several kernel versions, up to 2.6.21.3
Any hints are appreciated
ession..
--
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]
Mo
-info.html
Please read the FAQ at http://www.tux.org/lkml/
--
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
Justin Piszcz wrote:
On Thu, 31 May 2007, Parag Warudkar wrote:
Robert Hancock wrote:
I think that mem=8832M would work as well, to make the kernel use
only the memory that is marked cacheable. (It looks like this
parameter takes the highest memory address we want the kernel to use
Justin Piszcz wrote:
On Thu, 31 May 2007, Parag Warudkar wrote:
Robert Hancock wrote:
I think that mem=8832M would work as well, to make the kernel use
only the memory that is marked cacheable. (It looks like this
parameter takes the highest memory address we want the kernel to use
read the FAQ at http://www.tux.org/lkml/
--
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
..
--
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
a handler for that interrupt (it's not in the
list of handlers, only USB is). Maybe retrieving the interrupt before
pci_enable_device? (I haven't looked at the code in question.)
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http
, immediately after the previous one ends.
Jeff
Theoretically NVIDIA nForce4 ADMA could likely do this as well, as it
seems to allow chaining up multiple commands to execute in succession
(assuming they're not NCQ)..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam
(). In this case the select() is only
looking at read()'s.
It's because you haven't done anything to handle the error which is
still persisting. Likely the only thing sane you can do in this case is
close the fd and try to reopen it later.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam
Parag Warudkar wrote:
Robert Hancock wrote:
0-3319MB
4096-8832MB
leaving 64MB of memory at the top of RAM uncached. What do you want to
bet that something important (kernel code?) is getting loaded there..
So essentially it's a BIOS problem, it's not setting up the MTRRs
properly in order
by Rajesh Shah from Intel.
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
---
This should fix up some of the whitespace/formatting problems in the previous
version. There were actually some bugs in the check_mcfg_resource function,
there were some <= that should have been <.
ap length
to 0 characters to switch that off. Apparently disabling format=flowed
is needed as well, however :-)
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from this list: sen
Jesse Barnes wrote:
On Tuesday, May 29, 2007 9:01:22 Robert Hancock wrote:
These two patches implement some changes in behavior related to PCI
MMCONFIG configuration space access. One changes the way in which we
validate the MCFG table provided by the BIOS by checking it against
ACPI
. As Andi says, complain
to Intel.
--
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 [EM
Linus Torvalds wrote:
> On Tue, 29 May 2007, Robert Hancock wrote:
>> This path adds validation of the MMCONFIG table against the ACPI reserved
>> motherboard resources.
>
> Please fix the formatting of your code.
>
> "for" and "if"
are essentially what the 4GB/64GB memory options
control) are not needed in 64-bit mode, since we can access the entire
64-bit address space directly.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberth
says, complain
to Intel.
--
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
Jesse Barnes wrote:
On Tuesday, May 29, 2007 9:01:22 Robert Hancock wrote:
These two patches implement some changes in behavior related to PCI
MMCONFIG configuration space access. One changes the way in which we
validate the MCFG table provided by the BIOS by checking it against
ACPI
that off. Apparently disabling format=flowed
is needed as well, however :-)
--
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
by Rajesh Shah from Intel.
Signed-off-by: Robert Hancock [EMAIL PROTECTED]
---
This should fix up some of the whitespace/formatting problems in the previous
version. There were actually some bugs in the check_mcfg_resource function,
there were some = that should have been . Also forgot
Parag Warudkar wrote:
Robert Hancock wrote:
0-3319MB
4096-8832MB
leaving 64MB of memory at the top of RAM uncached. What do you want to
bet that something important (kernel code?) is getting loaded there..
So essentially it's a BIOS problem, it's not setting up the MTRRs
properly in order
are essentially what the 4GB/64GB memory options
control) are not needed in 64-bit mode, since we can access the entire
64-bit address space directly.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe
Linus Torvalds wrote:
On Tue, 29 May 2007, Robert Hancock wrote:
This path adds validation of the MMCONFIG table against the ACPI reserved
motherboard resources.
Please fix the formatting of your code.
for and if are not functions, and they have a space before the
parenthesis
Can you send your full dmesg output from the 8GB bootup?
--
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
this disabling on host bridge devices, as it is reported that
some of them do silly things like disable CPU to RAM access if this is done.
Based on an original patch by Jesse Barnes.
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.22-rc2-mm1/drivers/pci/probe.c2007-05-23
These two patches implement some changes in behavior related to PCI
MMCONFIG configuration space access. One changes the way in which we
validate the MCFG table provided by the BIOS by checking it against
ACPI motherboard resources instead of the E820 table. The BIOS is not
required to reserve
required
allocation.
-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 mapped it over other things it
shouldn't
have.
Signed-off-by: Robert
These two patches implement some changes in behavior related to PCI
MMCONFIG configuration space access. One changes the way in which we
validate the MCFG table provided by the BIOS by checking it against
ACPI motherboard resources instead of the E820 table. The BIOS is not
required to reserve
required
allocation.
-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 mapped it over other things it
shouldn't
have.
Signed-off-by: Robert
this disabling on host bridge devices, as it is reported that
some of them do silly things like disable CPU to RAM access if this is done.
Based on an original patch by Jesse Barnes.
Signed-off-by: Robert Hancock [EMAIL PROTECTED]
--- linux-2.6.22-rc2-mm1/drivers/pci/probe.c2007-05-23 21:21
from the 8GB bootup?
--
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
, you should get the latest RHEL errata update
kernel and see if that helps. There have been hundreds of bugfixes in
RHEL kernels since that version.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.roberth
, you should get the latest RHEL errata update
kernel and see if that helps. There have been hundreds of bugfixes in
RHEL kernels since that version.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com
bypasses this mechanism, you'll see this problem.
--
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
bypasses this mechanism, you'll see this problem.
--
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
t as
we ended up with a buffer that was mapped by the IOMMU for some reason
and that was not below 2GB.
The physical address you mean? If that is still happening then it needs
to get fixed. The allocation should not succeed if it can't provide
memory that's inside the DMA mask for the device..
-
be shutting it off entirely. Hopefully with the ACPI reservation
checking patch and the disable-decode-during-BAR-sizing patch
we wouldn't need to add that restriction.
But yes, post-2.6.22 for all of this :-)
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL
d sense that it was needed. (And if there
is some chipset where it is actually needed, better just disable
MMCONFIG on that one, as there's no way to use it sanely.)
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.robe
r solution?
I don't think that is going to be viable in the long run now that
Windows Vista is out and MS is actually encouraging HW developers to
allow using that config space..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTEC
Jesse Barnes wrote:
On Tuesday, May 22, 2007 6:06 pm Robert Hancock wrote:
There was a big discussion about this back in 2002, in which Linus
wasn't overly enthused about disabling the decode during probing due
to risk of causing problems with some devices:
http://lkml.org/lkml/2002/12/19/145
Jesse Barnes wrote:
On Tuesday, May 22, 2007 6:06 pm Robert Hancock wrote:
There was a big discussion about this back in 2002, in which Linus
wasn't overly enthused about disabling the decode during probing due
to risk of causing problems with some devices:
http://lkml.org/lkml/2002/12/19/145
?
I don't think that is going to be viable in the long run now that
Windows Vista is out and MS is actually encouraging HW developers to
allow using that config space..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http
. (And if there
is some chipset where it is actually needed, better just disable
MMCONFIG on that one, as there's no way to use it sanely.)
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com/
-
To unsubscribe from
be shutting it off entirely. Hopefully with the ACPI reservation
checking patch and the disable-decode-during-BAR-sizing patch
we wouldn't need to add that restriction.
But yes, post-2.6.22 for all of this :-)
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED
with a buffer that was mapped by the IOMMU for some reason
and that was not below 2GB.
The physical address you mean? If that is still happening then it needs
to get fixed. The allocation should not succeed if it can't provide
memory that's inside the DMA mask for the device..
--
Robert Hancock
Jesse Barnes wrote:
On Tuesday, May 22, 2007, Robert Hancock wrote:
Eww. I don't see where we disable the decode at all while we probe the
BARs on the device. That seems like a bad thing, especially with the way
we probe 64-bit BARs (do the low 32 bits first and then the high 32
bits
Jesse Barnes wrote:
On Tuesday, May 22, 2007, Robert Hancock wrote:
Eww. I don't see where we disable the decode at all while we probe the
BARs on the device. That seems like a bad thing, especially with the way
we probe 64-bit BARs (do the low 32 bits first and then the high 32
bits
?
--
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 ht
he normal halt state).
--
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 m
?
--
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 Tuesday, May 22, 2007, Robert Hancock wrote:
Eww. I don't see where we disable the decode at all while we probe the
BARs on the device. That seems like a bad thing, especially with the way
we probe 64-bit BARs (do the low 32 bits first and then the high 32
bits
Jesse Barnes wrote:
On Tuesday, May 22, 2007, Robert Hancock wrote:
Eww. I don't see where we disable the decode at all while we probe the
BARs on the device. That seems like a bad thing, especially with the way
we probe 64-bit BARs (do the low 32 bits first and then the high 32
bits
states? I'm using 64-bit Gentoo. My mobo is Asus P5B Deluxe. Otherwise
ACPI works fine.
The BIOS has to expose this support in ACPI, if it doesn't (which is
often the case on desktop boards) you won't get any C-state support
(well, except for C1 which is just the normal halt state).
--
Robert
her the corresponding
address in the MCFG table is problematic (i.e. has something else mapped
over it), or maybe that device just doesn't like being probed with MCFG
somehow.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://www.robe
ble.
> > Here's a rediffed version of the same.
>
> Please update libata as well when you udpate the blacklists.
Sure, point me at the table(s) ?
Dave
ata_device_blacklist in drivers/ata/libata-core.c
--
Robert Hancock Saskatoon, SK, Canada
To email, remove &q
ose commands.
This won't handle the case where the driver is loaded after the system
was already suspended to RAM and resumed, however I don't know exactly
how one could handle that in this situation..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PR
ng GTM). I imagine
this is what the Windows default IDE driver is doing (just using the
boot-up mode and feeding it back using GTM/STM on suspend/resume cycles).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home Page: http://w
e.
Right, you should see that showing up as ahci.
--
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
oller
into AHCI mode for best performance.
--
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
for best performance.
--
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
. How
can you tell from the Linux boot messages that the controller is in AHCI
mode - is it as simple as looking for AHCI driver messages? In this case
the
scsi0 : ata_piix
scsi1 : ata_piix
indicate that things are suboptimal I assume.
Right, you should see that showing up as ahci.
--
Robert
imagine
this is what the Windows default IDE driver is doing (just using the
boot-up mode and feeding it back using GTM/STM on suspend/resume cycles).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com
commands.
This won't handle the case where the driver is loaded after the system
was already suspended to RAM and resumed, however I don't know exactly
how one could handle that in this situation..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page
of the same.
Please update libata as well when you udpate the blacklists.
Sure, point me at the table(s) ?
Dave
ata_device_blacklist in drivers/ata/libata-core.c
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http
the corresponding
address in the MCFG table is problematic (i.e. has something else mapped
over it), or maybe that device just doesn't like being probed with MCFG
somehow.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http://www.roberthancock.com
of
these issues (and others, like the laptops that have a short 40-wire
cable that is good for high UDMA speeds which we presently have to
hard-code detection for specific models).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL PROTECTED]
Home
Randy Dunlap wrote:
On Sun, 20 May 2007 11:45:03 -0600 Robert Hancock wrote:
Indan Zupancic wrote:
Everything seems to work fine without sd_resume(), so why is it needed?
Because not all disks spin up without being told to do so and like it or
not spinning disks up on resume is the default
it configurable.
Not even after they receive a read command? Ugh.
ATA disks are supposed to spin up, yes. SCSI disks require a command to
tell them to spin up if they're in the "stopped" state.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from [EMAIL
that the drive is detecting a 40-wire cable on its side.
--
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
it configurable.
Not even after they receive a read command? Ugh.
ATA disks are supposed to spin up, yes. SCSI disks require a command to
tell them to spin up if they're in the stopped state.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http
Randy Dunlap wrote:
On Sun, 20 May 2007 11:45:03 -0600 Robert Hancock wrote:
Indan Zupancic wrote:
Everything seems to work fine without sd_resume(), so why is it needed?
Because not all disks spin up without being told to do so and like it or
not spinning disks up on resume is the default
of
these issues (and others, like the laptops that have a short 40-wire
cable that is good for high UDMA speeds which we presently have to
hard-code detection for specific models).
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page: http
-bit DMA addresses (where
supported by platform) and eliminates the annoying 64k DMA boundary
found in legacy PCI IDE BMDMA engines.
Looks like it doesn't allow 64-bit DMA addresses, it only gets rid of
the 64K boundary limitation.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove
-bit DMA addresses (where
supported by platform) and eliminates the annoying 64k DMA boundary
found in legacy PCI IDE BMDMA engines.
Looks like it doesn't allow 64-bit DMA addresses, it only gets rid of
the 64K boundary limitation.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove
NCQ on
this drive if it happens repeatedly. See the code in ahci.c in
ahci_host_intr.
This comment still applies:
Additional/general comments:
Think you need some code to handle suspend and resume (re-enable SATA
MMIO space, etc.)
--
Robert Hancock Saskatoon, SK, Canada
To email, remo
. See the code in ahci.c in
ahci_host_intr.
This comment still applies:
Additional/general comments:
Think you need some code to handle suspend and resume (re-enable SATA
MMIO space, etc.)
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL PROTECTED]
Home Page
blem, libata default DMA mask is 32 bits (which
isn't overridden with this controller) and so the block layer will
bounce any data being read/written above that point with IOMMU or
swiotlb. The comment is a bit unnecessarily scary.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove &
Peer Chen wrote:
Add the Software NCQ support to sata_nv.c for MCP51/MCP55/MCP61 SATA
controller.
This patch base on sata_nv.c file from kernel 2.6.22-rc1
See attachment for the patch.
Signed-off-by: Kuan Luo <[EMAIL PROTECTED]>
Signed-off-by: Peer Chen <[EMAIL PROTECTED]>
Good to finally
Peer Chen wrote:
Add the Software NCQ support to sata_nv.c for MCP51/MCP55/MCP61 SATA
controller.
This patch base on sata_nv.c file from kernel 2.6.22-rc1
See attachment for the patch.
Signed-off-by: Kuan Luo [EMAIL PROTECTED]
Signed-off-by: Peer Chen [EMAIL PROTECTED]
Good to finally see
DMA mask is 32 bits (which
isn't overridden with this controller) and so the block layer will
bounce any data being read/written above that point with IOMMU or
swiotlb. The comment is a bit unnecessarily scary.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove nospam from [EMAIL
Looks like the radeon driver has the same problem as the i915 driver
mentioned on the known problems page - I get 60 wakeups/sec from it on
my Compaq X1000 laptop (Radeon 9000 graphics) while in X, which
essentially prevents entry into C3.
--
Robert Hancock Saskatoon, SK, Canada
To email
of this patch.
Signed-off-by: Robert Hancock <[EMAIL PROTECTED]>
--- linux-2.6.21.1/drivers/ata/libata-eh.c 2007-04-27 15:49:26.0
-0600
+++ linux-2.6.21.1edit/drivers/ata/libata-eh.c 2007-05-14 17:38:35.0
-0600
@@ -1523,6 +1523,27 @@ static void ata_eh_report(struct a
of this patch.
Signed-off-by: Robert Hancock [EMAIL PROTECTED]
--- linux-2.6.21.1/drivers/ata/libata-eh.c 2007-04-27 15:49:26.0
-0600
+++ linux-2.6.21.1edit/drivers/ata/libata-eh.c 2007-05-14 17:38:35.0
-0600
@@ -1523,6 +1523,27 @@ static void ata_eh_report(struct ata_por
Looks like the radeon driver has the same problem as the i915 driver
mentioned on the known problems page - I get 60 wakeups/sec from it on
my Compaq X1000 laptop (Radeon 9000 graphics) while in X, which
essentially prevents entry into C3.
--
Robert Hancock Saskatoon, SK, Canada
To email
and included. Could it be included into the mainline
for now?
It's not really a fix, that value might be legitimately supposed to be
in the config space. Sounds like some driver is disabling the device
before saving the state or something..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove
Counter logging not supported
[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
Sounds like SMART is likely disabled on that drive. You can try doing
"smartctl -s on /dev/sda" and see if that will turn it on.
--
Robe
these commands? CCing linux-ide in case anyone
knows what would cause 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 the line "unsubscribe linux-kern
Gerhard Mack wrote:
On Wed, 9 May 2007, Robert Hancock wrote:
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
don't need volatile in that case, rmb() can be used.
--
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
volatile in that case, rmb() can be used.
--
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
Gerhard Mack wrote:
On Wed, 9 May 2007, Robert Hancock wrote:
Gerhard Mack wrote:
On Wed, 9 May 2007, Jeff Garzik wrote:
Gerhard Mack wrote:
May 9 14:51:35 mgerhard kernel: ata1.00: exception Emask 0x0 SAct 0x0
SErr
0x180 action 0x2 frozen
May 9 14:51:35 mgerhard kernel: ata1.00: cmd
these commands? CCing linux-ide in case anyone
knows what would cause 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 the line unsubscribe linux-kernel in
the body
Counter logging not supported
[GLTSD (Global Logging Target Save Disable) set. Enable Save with '-S on']
Device does not support Self Test logging
Sounds like SMART is likely disabled on that drive. You can try doing
smartctl -s on /dev/sda and see if that will turn it on.
--
Robert Hancock
and included. Could it be included into the mainline
for now?
It's not really a fix, that value might be legitimately supposed to be
in the config space. Sounds like some driver is disabling the device
before saving the state or something..
--
Robert Hancock Saskatoon, SK, Canada
To email, remove
Tejun Heo wrote:
Chuck Ebbert wrote:
Robert Hancock wrote:
+ ehc->i.serror & SERR_TRANS_ST_ERROR ? "TransStatTransErr "
: "",
+ ehc->i.serror & SERR_UNRECOG_FIS ? "UnrecogFIS " : "",
+ ehc->i.serror & SERR
Tejun Heo wrote:
Chuck Ebbert wrote:
Robert Hancock wrote:
+ ehc-i.serror SERR_TRANS_ST_ERROR ? TransStatTransErr
: ,
+ ehc-i.serror SERR_UNRECOG_FIS ? UnrecogFIS : ,
+ ehc-i.serror SERR_DEV_XCHG ? DevExchanged : );
I'm not really convinced whether
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
human readable
form is also a bit cryptic and can get quite long. So, mild NACK from me.
It certainly seems useful when debugging hotplug issues or random SATA
problems which end up being caused by communication problems. Without
this output, Joe User stands no chance of figuring out what's g
801 - 900 of 1555 matches
Mail list logo
