ernst, thanks for pointing that out. I think I must have gained tunnel-
vision after chasing that sata_mv similarity!
For reference, lsmod will no longer be so reliable for checking modules
in Jaunty and later since we're now building a lot of modules into the
kernel. sata_nv is one of those built
It doesn't look like I'm using "sata_nv", more like I'm using the "ahci"
driver:
00:09.0 IDE interface: nVidia Corporation MCP67 AHCI Controller (rev a2)
(prog-if 85 [Master SecO PriO])
Subsystem: ABIT Computer Corp. Device 1c2f
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VG
Got it with 2.6.28-02062807-generic now also, left
while true; do dpkg -i *.deb; done
running over night with some packages.
--
[jaunty] ata timeout exception with data loss
https://bugs.launchpad.net/bugs/343919
You received this bug notification because you are a member of Ubuntu
Bugs, which
There was a similar issue affecting the sata_mv driver for Marvell SATA
chip-sets where an iport address for interrupt handling was incorrectly
set. Although in this case a different driver is used (sata_nv) it is
possible something similar to that issue might cause this one.
For reference, that c
Ah, now I did reproduce it, pretty quickly too! Now running
2.6.28-10-generic
--
[jaunty] ata timeout exception with data loss
https://bugs.launchpad.net/bugs/343919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
This is the user's hardware listing (copied from a pastebin)
lspci -nn
00:00.0 RAM memory [0500]: nVidia Corporation MCP67 Memory Controller
[10de:0547] (rev a2)
00:01.0 ISA bridge [0601]: nVidia Corporation MCP67 ISA Bridge [10de:0548] (rev
a2)
00:01.1 SMBus [0c05]: nVidia Corporation MCP67 SMB
The output of smartctl --all /dev/sda4
So the filesystem that's allways affected it my /dev/sda4 ext4 filesystem
mounted on / , to summarise.
(I think, I haven't seen the problem with any other filesystem.)
** Attachment added: "smart.txt"
http://launchpadlibrarian.net/23955269/smart.txt
--
Now as you can see it's always a "timeout" exception. My first reaction to that
is...
1) maybe it could wait a little longer?
2) is it really that bad? Try again?
3) has some timeout value changed between 2.6.27 and 2.6.28?
You can see that it's on different sectors each time.
"smartctl --all"
** Attachment added: "dmesg 4"
http://launchpadlibrarian.net/23953795/fel4.txt
--
[jaunty] ata timeout exception with data loss
https://bugs.launchpad.net/bugs/343919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Attachment added: "fel3.txt"
http://launchpadlibrarian.net/23953789/fel3.txt
--
[jaunty] ata timeout exception with data loss
https://bugs.launchpad.net/bugs/343919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs m
** Attachment added: "dmesg 2"
http://launchpadlibrarian.net/23953785/fel2.txt
--
[jaunty] ata timeout exception with data loss
https://bugs.launchpad.net/bugs/343919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
** Attachment added: "dmesg 1"
http://launchpadlibrarian.net/23953769/fel.txt
--
[jaunty] ata timeout exception with data loss
https://bugs.launchpad.net/bugs/343919
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
12 matches
Mail list logo
