Tejun Heo wrote:
> Andreas John wrote:
>> 00:00.0 Host bridge [0600]: ATI Technologies Inc Unknown device [1002:7910]
>
> Okidoki, another ATI host bridge which can't forward MSI write upto the
> cpu. I'll blacklist it. Thanks.
Scrap that. I got confused. You weren't using MSI.
In the log, y
Hi,
my system has an Nvidia "nForce 630A MCP" chipset.
(Asrock ALiveNF7G-HDready mainboard)
If it helps, I've uploaded the output of "lspci -vvxxx" to:
http://datenparkplatz.de/DiesUndDas/lspci-vvxxx.output.txt.
Best wishes,
Ulrich
-
To unsubscribe from this list: send the line "unsubscribe
Hm,
it seems we are victim of a SATA NCQ HORKAGE:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg08936.html
Disableing NCQ seems to work on the sb600. Samsung already ships a newer
edition ("403" instead of "401") but there is no fix for the NCQ in
the 401 edition. With Samsungs HUTIL you cann
Andreas John wrote:
> 00:00.0 Host bridge [0600]: ATI Technologies Inc Unknown device [1002:7910]
Okidoki, another ATI host bridge which can't forward MSI write upto the
cpu. I'll blacklist it. Thanks.
--
tejun
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
Hi,
as requested by Tejun here comes dmesg and lspci -nn. Additionally I
found something dmesg (See 1.), probably caused by the low-level error.
Best Regards,
Andreas
1.)
[81739.06] sd 1:0:0:0: [sdb] Result: hostbyte=DID_BAD_TARGET
driverbyte=DRIVER_OK,SUGGEST_OK
[81739.06] end_request: I
Andreas John wrote:
> Hm,
> I should add that on 2.6.22-amd64 (ubuntu gutsy) the log entry is as
> follows:
>
> 8<--
> ata2.00 excetion Emask 0x40 SAct 0x0 SErr 0x800 action 0x2 frozen
> ata2.00 tag 0 cmd 0xea Emask 0x44 stat 0x40 err 0x0 timeout
> 1st FIS failed
> 8<--
Please pos
Hm,
I should add that on 2.6.22-amd64 (ubuntu gutsy) the log entry is as
follows:
8<--
ata2.00 excetion Emask 0x40 SAct 0x0 SErr 0x800 action 0x2 frozen
ata2.00 tag 0 cmd 0xea Emask 0x44 stat 0x40 err 0x0 timeout
1st FIS failed
8<--
rgds,
Andreas
Andreas John schrieb:
> Hi SB600
Hi SB600-folks,
we bought some AMD690/sb600 based mobos and try go get them working. I
followed the patches on LKML and switched from Debian Etch 2.6.18-x
kernel to 2.6.22, just to ensure that all patches are already applied.
But we still have strange errors/lockups and we found a way to reproduce
On 3/15/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
Conke Hu wrote:
>> E Internal error: The host bus adapter experienced an internal error
>> that caused the operation to fail and may have put the host bus adapter
>> into an error state. Host software should reset the interface before
>> re-trying
Conke Hu wrote:
>> E Internal error: The host bus adapter experienced an internal error
>> that caused the operation to fail and may have put the host bus adapter
>> into an error state. Host software should reset the interface before
>> re-trying the operation. If the condition persists, the host
On 3/14/07, Tejun Heo <[EMAIL PROTECTED]> wrote:
Hello,
Conke Hu wrote:
>When there is no media in SATA CD/DVD drive or media is not ready,
> AHCI controller fails to execute the ATAPI commands TEST_UNIT_READY,
> READ_CAPACITY or READ_TOC and reports PORT_IRQ_TF_ERR. But ATI SB600
> SATA con
Hello,
Conke Hu wrote:
>When there is no media in SATA CD/DVD drive or media is not ready,
> AHCI controller fails to execute the ATAPI commands TEST_UNIT_READY,
> READ_CAPACITY or READ_TOC and reports PORT_IRQ_TF_ERR. But ATI SB600
> SATA controller sets SERR_INTERNAL bit in the error registe
12 matches
Mail list logo
