[Expired for linux (Ubuntu) because there has been no activity for 60
days.]
** Changed in: linux (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094446
Shinji, could you please provide the full model of your motherboard (ex.
IONITX R Series IONITX-R-E)?
** Tags added: needs-full-motherboard-model
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This issue appears to be an upstream bug, since you tested the latest
upstream kernel. Would it be possible for you to open an upstream bug
report[0]? That will allow the upstream Developers to examine the
issue, and may provide a quicker resolution to the bug.
Please follow the instructions on
Ok... from today it seems not to work with forcing to 1.5GBit any longer
:(
Mar 23 18:00:01 nas CRON[12386]: (shinji) CMD (/usr/bin/imapfilter)
Mar 23 18:00:56 nas kernel: [73823.079958] ata1: exception Emask 0x10 SAct 0x0
SErr 0x199 action 0xe frozen
Mar
Sorry to bother again, but the bug seems to be still there. After two
month without any problems I am getting the same errors again. So I have
to withdraw my statement that the problem has been solved with the 3.8
upstream kernel!
After a restart/Reset my systems says Read error after POST...
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1094446
Title:
failed command: READ FPDMA QUEUED and interface fatal errors
To manage
** Tags added: kernel-fixed-upstream kernel-fixed-
upstream-v3.8-rc1-raring
** Description changed:
I have installed Ubuntu 12.10 server on my Zotac IONITX Board but I am
getting a lot of errors related to my SATA controller. Sometimes the
system partition is remounted read-only after a
I replaced the cables but the error was still there. Then I restricted
the SATA speed to 3.0Gb/s by adding
GRUB_CMDLINE_LINUX=libata.force=3.0
to my /etc/default/grub file and the error was gone!
Both drives are SATA 6Gb/s capable.
Maybe it is a driver or a hardware issue with the NVIDIA MCP79
Huh ok, weird, since as far as I can read from your logs it was only
running it at 3Gb/s anyway.
OK, so the next thing to try is to see if the latest upstream kernel has
the same problem exists if you don't add the libata.force.
From:
Medium: It's a problem with a required hardware component (high) but has
an easy workaround (low) - so I went for medium.
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
To me that looks like a SATA link error - are you sure you've not got a
bad cable or similar?
[ 7927.477839] ata2: SError: { 10B8B Dispar BadCRC }
[ 7927.478874] ata2.00: failed command: READ FPDMA QUEUED
[ 7927.479914] ata2.00: cmd 60/08:00:a7:03:e0/00:00:14:00:00/40 tag 0 ncq 4096
in
[
11 matches
Mail list logo
