I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one
of
my Ubuntu machines without success.
It keeps giving errors like this:
[ 9.115544] ata9: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x10
frozen
[ 9.115550] ata9.00: failed command: READ FPDMA QUEUED
[ 9.115556] ata9.00: cmd 60/04:00:
d4:82:85/00:00:1f:00:00/40 tag 0 ncq 2048 in
[ 9.115557] res 40/00:18:d3:82:85/00:00:1f:00:00/40 Emask 0x4 (timeout)
[ 9.115560] ata9.00: status: { DRDY }
[ 9.115562] ata9.00: failed command: READ FPDMA QUEUED
I''ve searched and found some bugs referencing this type of problem and
followed some suggestions:
I added libata.force=noncq to the kernel boot line but it did not help.
My hardware is like this:
# lspci
00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge
00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge
(int gfx)
00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge
(PCIE port 5)
00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA
Controller [AHCI mode]
00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0
Controller
00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0
Controller
00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller
00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller
00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a)
00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller
00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA)
00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller
00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge
00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2
Controller
00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron,
Athlon64, Sempron] HyperTransport Configuration
00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron,
Athlon64, Sempron] Address Map
00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron,
Athlon64, Sempron] DRAM Controller
00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron,
Athlon64, Sempron] Miscellaneous Control
00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron,
Athlon64, Sempron] Link Control
01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3300
Graphics
01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23
IEEE-1394a-2000 Controller (PHY/Link)
I''ve tested the hard drives with manufacturers surface test tools and
the drives show no errors. Smartctl shows no errors after testing.
Is there some kernel switch I need to support this hardware w/2.6.37-12
kernels?
Regards,
Gerry
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Jan-13 20:21 UTC
Re: [Xen-devel] bug: kernel 2.6.37-12 READ FPDMA QUEUED
On Thu, Jan 13, 2011 at 02:23:07PM -0500, Gerry Reno wrote:> I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of > my Ubuntu machines without success.How much memory do you have in your box? HAve you tried to limit it (dom0_mem=max:1GB)? What does you full serial log console look like? Do you see ''swiotlb'' in your dmesg output? Did you follow the PVOPS Wiki about troubleshooting?> > It keeps giving errors like this: > > [ 9.115544] ata9: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x10 > frozen > [ 9.115550] ata9.00: failed command: READ FPDMA QUEUED > [ 9.115556] ata9.00: cmd 60/04:00: > > d4:82:85/00:00:1f:00:00/40 tag 0 ncq 2048 in > [ 9.115557] res 40/00:18:d3:82:85/00:00:1f:00:00/40 Emask 0x4 (timeout) > [ 9.115560] ata9.00: status: { DRDY } > [ 9.115562] ata9.00: failed command: READ FPDMA QUEUED > > I''ve searched and found some bugs referencing this type of problem and > followed some suggestions: > > I added libata.force=noncq to the kernel boot line but it did not help. > > My hardware is like this: > # lspci > 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge > 00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge > (int gfx) > 00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge > (PCIE port 5) > 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA > Controller [AHCI mode] > 00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 > Controller > 00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller > 00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller > 00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 > Controller > 00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller > 00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller > 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a) > 00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller > 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) > 00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller > 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge > 00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 > Controller > 00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, > Athlon64, Sempron] HyperTransport Configuration > 00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, > Athlon64, Sempron] Address Map > 00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, > Athlon64, Sempron] DRAM Controller > 00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, > Athlon64, Sempron] Miscellaneous Control > 00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, > Athlon64, Sempron] Link Control > 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3300 > Graphics > 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller > 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. > RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) > 03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 > IEEE-1394a-2000 Controller (PHY/Link) > > I''ve tested the hard drives with manufacturers surface test tools and > the drives show no errors. Smartctl shows no errors after testing. > > Is there some kernel switch I need to support this hardware w/2.6.37-12 > kernels? > > > Regards, > Gerry > > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 01/13/2011 03:21 PM, Konrad Rzeszutek Wilk wrote:> On Thu, Jan 13, 2011 at 02:23:07PM -0500, Gerry Reno wrote: >> I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of >> my Ubuntu machines without success. > > How much memory do you have in your box?Memory: 8 GB> HAve you tried to limit it > (dom0_mem=max:1GB)?No.> What does you full serial log console look like?Will dmesg output do? Here is the latest output: [ 7001.105099] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7001.111572] ata7.00: irq_stat 0x40000008 [ 7001.115489] ata7.00: failed command: READ FPDMA QUEUED [ 7001.120664] ata7.00: cmd 60/08:00:b6:05:7c/00:00:13:00:00/40 tag 0 ncq 4096 in [ 7001.120666] res 51/40:08:b6:05:7c/00:00:13:00:00/40 Emask 0x409 (media error) <F> [ 7001.136190] ata7.00: status: { DRDY ERR } [ 7001.140229] ata7.00: error: { UNC } [ 7001.156146] ata7.00: configured for UDMA/133 [ 7001.160457] ata7: EH complete [ 7005.404610] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7005.411095] ata7.00: irq_stat 0x40000008 [ 7005.415016] ata7.00: failed command: READ FPDMA QUEUED [ 7005.420187] ata7.00: cmd 60/08:00:b6:05:7c/00:00:13:00:00/40 tag 0 ncq 4096 in [ 7005.420189] res 51/40:08:b6:05:7c/00:00:13:00:00/40 Emask 0x409 (media error) <F> [ 7005.435710] ata7.00: status: { DRDY ERR } [ 7005.439732] ata7.00: error: { UNC } [ 7005.455682] ata7.00: configured for UDMA/133 [ 7005.459966] sd 6:0:0:0: [sde] Unhandled sense code [ 7005.464806] sd 6:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 7005.472074] sd 6:0:0:0: [sde] Sense Key : Medium Error [current] [descriptor] [ 7005.479374] Descriptor sense data with sense descriptors (in hex): [ 7005.485620] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 7005.492289] 13 7c 05 b6 [ 7005.495601] sd 6:0:0:0: [sde] Add. Sense: Unrecovered read error - auto reallocate failed [ 7005.503941] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 13 7c 05 b6 00 00 08 00 [ 7005.511064] end_request: I/O error, dev sde, sector 326895030 [ 7005.516839] ata7: EH complete [ 7005.520160] md/raid1:md6: read error corrected (8 sectors at 294668640 on sde3) [ 7005.527491] md/raid1:md6: redirecting sector 294668400 to other mirror: sdf3 [ 7010.087434] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7010.093924] ata7.00: irq_stat 0x40000008 [ 7010.097845] ata7.00: failed command: READ FPDMA QUEUED [ 7010.103011] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag 0 ncq 4096 in [ 7010.103012] res 51/40:08:be:05:7c/00:00:13:00:00/40 Emask 0x409 (media error) <F> [ 7010.118520] ata7.00: status: { DRDY ERR } [ 7010.122549] ata7.00: error: { UNC } [ 7010.138492] ata7.00: configured for UDMA/133 [ 7010.142799] ata7: EH complete [ 7014.386961] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7014.393424] ata7.00: irq_stat 0x40000008 [ 7014.397347] ata7.00: failed command: READ FPDMA QUEUED [ 7014.402521] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag 0 ncq 4096 in [ 7014.402522] res 51/40:08:be:05:7c/00:00:13:00:00/40 Emask 0x409 (media error) <F> [ 7014.418048] ata7.00: status: { DRDY ERR } [ 7014.422087] ata7.00: error: { UNC } [ 7014.438017] ata7.00: configured for UDMA/133 [ 7014.442328] ata7: EH complete [ 7018.686482] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7018.692966] ata7.00: irq_stat 0x40000008 [ 7018.697289] ata7.00: failed command: READ FPDMA QUEUED [ 7018.702463] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag 0 ncq 4096 in [ 7018.702465] res 51/40:08:be:05:7c/00:00:13:00:00/40 Emask 0x409 (media error) <F> [ 7018.718007] ata7.00: status: { DRDY ERR } [ 7018.722038] ata7.00: error: { UNC } [ 7018.737532] ata7.00: configured for UDMA/133 [ 7018.741839] ata7: EH complete [ 7022.986007] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7022.992477] ata7.00: irq_stat 0x40000008 [ 7022.996403] ata7.00: failed command: READ FPDMA QUEUED [ 7023.001567] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag 0 ncq 4096 in [ 7023.001568] res 51/40:08:be:05:7c/00:00:13:00:00/40 Emask 0x409 (media error) <F> [ 7023.017131] ata7.00: status: { DRDY ERR } [ 7023.021173] ata7.00: error: { UNC } [ 7023.037063] ata7.00: configured for UDMA/133 [ 7023.041375] ata7: EH complete [ 7027.285527] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7027.291997] ata7.00: irq_stat 0x40000008 [ 7027.295913] ata7.00: failed command: READ FPDMA QUEUED [ 7027.301078] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag 0 ncq 4096 in [ 7027.301080] res 51/40:08:be:05:7c/00:00:13:00:00/40 Emask 0x409 (media error) <F> [ 7027.316596] ata7.00: status: { DRDY ERR } [ 7027.320635] ata7.00: error: { UNC } [ 7027.336589] ata7.00: configured for UDMA/133 [ 7027.340904] ata7: EH complete [ 7031.585052] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 [ 7031.591525] ata7.00: irq_stat 0x40000008 [ 7031.595450] ata7.00: failed command: READ FPDMA QUEUED [ 7031.600641] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag 0 ncq 4096 in [ 7031.600642] res 51/40:08:be:05:7c/00:00:13:00:00/40 Emask 0x409 (media error) <F> [ 7031.616150] ata7.00: status: { DRDY ERR } [ 7031.620185] ata7.00: error: { UNC } [ 7031.636113] ata7.00: configured for UDMA/133 [ 7031.640422] sd 6:0:0:0: [sde] Unhandled sense code [ 7031.645207] sd 6:0:0:0: [sde] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE [ 7031.652470] sd 6:0:0:0: [sde] Sense Key : Medium Error [current] [descriptor] [ 7031.659746] Descriptor sense data with sense descriptors (in hex): [ 7031.665982] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 [ 7031.672633] 13 7c 05 be [ 7031.675936] sd 6:0:0:0: [sde] Add. Sense: Unrecovered read error - auto reallocate failed [ 7031.684279] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 13 7c 05 be 00 00 08 00 [ 7031.691390] end_request: I/O error, dev sde, sector 326895038 [ 7031.697155] ata7: EH complete [ 7031.700488] md/raid1:md6: read error corrected (8 sectors at 294668648 on sde3) [ 7031.707820] md/raid1:md6: redirecting sector 294668648 to other mirror: sdf3> Do you see ''swiotlb'' in your dmesg output?$ dmesg | grep swiotlb $> Did you follow the PVOPS Wiki > about troubleshooting?Right now I''m not even trying to work with dom0 or Xen. Just trying to get the basic kernel to run on the hardware.>> >> It keeps giving errors like this: >> >> [ 9.115544] ata9: exception Emask 0x0 SAct 0xf SErr 0x0 action 0x10 >> frozen >> [ 9.115550] ata9.00: failed command: READ FPDMA QUEUED >> [ 9.115556] ata9.00: cmd 60/04:00: >> >> d4:82:85/00:00:1f:00:00/40 tag 0 ncq 2048 in >> [ 9.115557] res 40/00:18:d3:82:85/00:00:1f:00:00/40 Emask 0x4 (timeout) >> [ 9.115560] ata9.00: status: { DRDY } >> [ 9.115562] ata9.00: failed command: READ FPDMA QUEUED >> >> I''ve searched and found some bugs referencing this type of problem and >> followed some suggestions: >> >> I added libata.force=noncq to the kernel boot line but it did not help. >> >> My hardware is like this: >> # lspci >> 00:00.0 Host bridge: Advanced Micro Devices [AMD] RS780 Host Bridge >> 00:01.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge >> (int gfx) >> 00:0a.0 PCI bridge: Advanced Micro Devices [AMD] RS780 PCI to PCI bridge >> (PCIE port 5) >> 00:11.0 SATA controller: ATI Technologies Inc SB700/SB800 SATA >> Controller [AHCI mode] >> 00:12.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 >> Controller >> 00:12.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller >> 00:12.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller >> 00:13.0 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI0 >> Controller >> 00:13.1 USB Controller: ATI Technologies Inc SB700 USB OHCI1 Controller >> 00:13.2 USB Controller: ATI Technologies Inc SB700/SB800 USB EHCI Controller >> 00:14.0 SMBus: ATI Technologies Inc SBx00 SMBus Controller (rev 3a) >> 00:14.1 IDE interface: ATI Technologies Inc SB700/SB800 IDE Controller >> 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) >> 00:14.3 ISA bridge: ATI Technologies Inc SB700/SB800 LPC host controller >> 00:14.4 PCI bridge: ATI Technologies Inc SBx00 PCI to PCI Bridge >> 00:14.5 USB Controller: ATI Technologies Inc SB700/SB800 USB OHCI2 >> Controller >> 00:18.0 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, >> Athlon64, Sempron] HyperTransport Configuration >> 00:18.1 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, >> Athlon64, Sempron] Address Map >> 00:18.2 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, >> Athlon64, Sempron] DRAM Controller >> 00:18.3 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, >> Athlon64, Sempron] Miscellaneous Control >> 00:18.4 Host bridge: Advanced Micro Devices [AMD] K10 [Opteron, >> Athlon64, Sempron] Link Control >> 01:05.0 VGA compatible controller: ATI Technologies Inc Radeon HD 3300 >> Graphics >> 01:05.1 Audio device: ATI Technologies Inc RS780 Azalia controller >> 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. >> RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02) >> 03:0e.0 FireWire (IEEE 1394): Texas Instruments TSB43AB23 >> IEEE-1394a-2000 Controller (PHY/Link) >> >> I''ve tested the hard drives with manufacturers surface test tools and >> the drives show no errors. Smartctl shows no errors after testing. >> >> Is there some kernel switch I need to support this hardware w/2.6.37-12 >> kernels? >> >> >> Regards, >> Gerry >> >> >>_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Konrad Rzeszutek Wilk
2011-Jan-13 21:42 UTC
Re: [Xen-devel] bug: kernel 2.6.37-12 READ FPDMA QUEUED
On Thu, Jan 13, 2011 at 03:41:09PM -0500, Gerry Reno wrote:> On 01/13/2011 03:21 PM, Konrad Rzeszutek Wilk wrote: > > On Thu, Jan 13, 2011 at 02:23:07PM -0500, Gerry Reno wrote: > >> I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of > >> my Ubuntu machines without success. > > > > How much memory do you have in your box? > > Memory: 8 GB > > > HAve you tried to limit it > > (dom0_mem=max:1GB)? > > No.Please try. Wait .. are you running this with Xen hypervisor?> > > > What does you full serial log console look like? > Will dmesg output do? Here is the latest output:I need the full output. From start please.> > [ 7001.105099] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 > [ 7001.111572] ata7.00: irq_stat 0x40000008 > [ 7001.115489] ata7.00: failed command: READ FPDMA QUEUED > [ 7001.120664] ata7.00: cmd 60/08:00:b6:05:7c/00:00:13:00:00/40 tag > 0 ncq 4096 in > [ 7001.120666] res 51/40:08:b6:05:7c/00:00:13:00:00/40 > Emask 0x409 (media error) <F> > [ 7001.136190] ata7.00: status: { DRDY ERR } > [ 7001.140229] ata7.00: error: { UNC } > [ 7001.156146] ata7.00: configured for UDMA/133 > [ 7001.160457] ata7: EH complete > [ 7005.404610] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 > [ 7005.411095] ata7.00: irq_stat 0x40000008 > [ 7005.415016] ata7.00: failed command: READ FPDMA QUEUED > [ 7005.420187] ata7.00: cmd 60/08:00:b6:05:7c/00:00:13:00:00/40 tag > 0 ncq 4096 in > [ 7005.420189] res 51/40:08:b6:05:7c/00:00:13:00:00/40 > Emask 0x409 (media error) <F> > [ 7005.435710] ata7.00: status: { DRDY ERR } > [ 7005.439732] ata7.00: error: { UNC } > [ 7005.455682] ata7.00: configured for UDMA/133 > [ 7005.459966] sd 6:0:0:0: [sde] Unhandled sense code > [ 7005.464806] sd 6:0:0:0: [sde] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE > [ 7005.472074] sd 6:0:0:0: [sde] Sense Key : Medium Error [current] > [descriptor] > [ 7005.479374] Descriptor sense data with sense descriptors (in hex): > [ 7005.485620] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 > [ 7005.492289] 13 7c 05 b6 > [ 7005.495601] sd 6:0:0:0: [sde] Add. Sense: Unrecovered read error > - auto reallocate failed > [ 7005.503941] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 13 7c 05 b6 00 > 00 08 00 > [ 7005.511064] end_request: I/O error, dev sde, sector 326895030 > [ 7005.516839] ata7: EH complete > [ 7005.520160] md/raid1:md6: read error corrected (8 sectors at > 294668640 on sde3) > [ 7005.527491] md/raid1:md6: redirecting sector 294668400 to other > mirror: sdf3 > [ 7010.087434] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 > [ 7010.093924] ata7.00: irq_stat 0x40000008 > [ 7010.097845] ata7.00: failed command: READ FPDMA QUEUED > [ 7010.103011] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag > 0 ncq 4096 in > [ 7010.103012] res 51/40:08:be:05:7c/00:00:13:00:00/40 > Emask 0x409 (media error) <F> > [ 7010.118520] ata7.00: status: { DRDY ERR } > [ 7010.122549] ata7.00: error: { UNC } > [ 7010.138492] ata7.00: configured for UDMA/133 > [ 7010.142799] ata7: EH complete > [ 7014.386961] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 > [ 7014.393424] ata7.00: irq_stat 0x40000008 > [ 7014.397347] ata7.00: failed command: READ FPDMA QUEUED > [ 7014.402521] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag > 0 ncq 4096 in > [ 7014.402522] res 51/40:08:be:05:7c/00:00:13:00:00/40 > Emask 0x409 (media error) <F> > [ 7014.418048] ata7.00: status: { DRDY ERR } > [ 7014.422087] ata7.00: error: { UNC } > [ 7014.438017] ata7.00: configured for UDMA/133 > [ 7014.442328] ata7: EH complete > [ 7018.686482] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 > [ 7018.692966] ata7.00: irq_stat 0x40000008 > [ 7018.697289] ata7.00: failed command: READ FPDMA QUEUED > [ 7018.702463] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag > 0 ncq 4096 in > [ 7018.702465] res 51/40:08:be:05:7c/00:00:13:00:00/40 > Emask 0x409 (media error) <F> > [ 7018.718007] ata7.00: status: { DRDY ERR } > [ 7018.722038] ata7.00: error: { UNC } > [ 7018.737532] ata7.00: configured for UDMA/133 > [ 7018.741839] ata7: EH complete > [ 7022.986007] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 > [ 7022.992477] ata7.00: irq_stat 0x40000008 > [ 7022.996403] ata7.00: failed command: READ FPDMA QUEUED > [ 7023.001567] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag > 0 ncq 4096 in > [ 7023.001568] res 51/40:08:be:05:7c/00:00:13:00:00/40 > Emask 0x409 (media error) <F> > [ 7023.017131] ata7.00: status: { DRDY ERR } > [ 7023.021173] ata7.00: error: { UNC } > [ 7023.037063] ata7.00: configured for UDMA/133 > [ 7023.041375] ata7: EH complete > [ 7027.285527] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 > [ 7027.291997] ata7.00: irq_stat 0x40000008 > [ 7027.295913] ata7.00: failed command: READ FPDMA QUEUED > [ 7027.301078] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag > 0 ncq 4096 in > [ 7027.301080] res 51/40:08:be:05:7c/00:00:13:00:00/40 > Emask 0x409 (media error) <F> > [ 7027.316596] ata7.00: status: { DRDY ERR } > [ 7027.320635] ata7.00: error: { UNC } > [ 7027.336589] ata7.00: configured for UDMA/133 > [ 7027.340904] ata7: EH complete > [ 7031.585052] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 > [ 7031.591525] ata7.00: irq_stat 0x40000008 > [ 7031.595450] ata7.00: failed command: READ FPDMA QUEUED > [ 7031.600641] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag > 0 ncq 4096 in > [ 7031.600642] res 51/40:08:be:05:7c/00:00:13:00:00/40 > Emask 0x409 (media error) <F> > [ 7031.616150] ata7.00: status: { DRDY ERR } > [ 7031.620185] ata7.00: error: { UNC } > [ 7031.636113] ata7.00: configured for UDMA/133 > [ 7031.640422] sd 6:0:0:0: [sde] Unhandled sense code > [ 7031.645207] sd 6:0:0:0: [sde] Result: hostbyte=DID_OK > driverbyte=DRIVER_SENSE > [ 7031.652470] sd 6:0:0:0: [sde] Sense Key : Medium Error [current] > [descriptor] > [ 7031.659746] Descriptor sense data with sense descriptors (in hex): > [ 7031.665982] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 > [ 7031.672633] 13 7c 05 be > [ 7031.675936] sd 6:0:0:0: [sde] Add. Sense: Unrecovered read error > - auto reallocate failed > [ 7031.684279] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 13 7c 05 be 00 > 00 08 00 > [ 7031.691390] end_request: I/O error, dev sde, sector 326895038 > [ 7031.697155] ata7: EH complete > [ 7031.700488] md/raid1:md6: read error corrected (8 sectors at > 294668648 on sde3) > [ 7031.707820] md/raid1:md6: redirecting sector 294668648 to other > mirror: sdf3> > > > Do you see ''swiotlb'' in your dmesg output? > > $ dmesg | grep swiotlbForgot -i> $ > > > Did you follow the PVOPS Wiki > > about troubleshooting? > > Right now I''m not even trying to work with dom0 or Xen. Just trying to > get the basic kernel to run on the hardware.So you are running this under baremetal then? _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 01/13/2011 04:42 PM, Konrad Rzeszutek Wilk wrote:> On Thu, Jan 13, 2011 at 03:41:09PM -0500, Gerry Reno wrote: > >> On 01/13/2011 03:21 PM, Konrad Rzeszutek Wilk wrote: >> >>> On Thu, Jan 13, 2011 at 02:23:07PM -0500, Gerry Reno wrote: >>> >>>> I''ve been trying to install a 2.6.37-12 kernel from kernel-ppa on one of >>>> my Ubuntu machines without success. >>>> >>> How much memory do you have in your box? >>> >> Memory: 8 GB >> >> >>> HAve you tried to limit it >>> (dom0_mem=max:1GB)? >>> >> No. >> > Please try. Wait .. are you running this with Xen hypervisor? >Not yet.> >> >> >>> What does you full serial log console look like? >>> >> Will dmesg output do? Here is the latest output: >> > I need the full output. From start please. >Ok, will try to attach it. It''s several thousand lines long. If that doesn''t work I''ll email it directly to you.>> [ 7001.105099] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 7001.111572] ata7.00: irq_stat 0x40000008 >> [ 7001.115489] ata7.00: failed command: READ FPDMA QUEUED >> [ 7001.120664] ata7.00: cmd 60/08:00:b6:05:7c/00:00:13:00:00/40 tag >> 0 ncq 4096 in >> [ 7001.120666] res 51/40:08:b6:05:7c/00:00:13:00:00/40 >> Emask 0x409 (media error) <F> >> [ 7001.136190] ata7.00: status: { DRDY ERR } >> [ 7001.140229] ata7.00: error: { UNC } >> [ 7001.156146] ata7.00: configured for UDMA/133 >> [ 7001.160457] ata7: EH complete >> [ 7005.404610] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 7005.411095] ata7.00: irq_stat 0x40000008 >> [ 7005.415016] ata7.00: failed command: READ FPDMA QUEUED >> [ 7005.420187] ata7.00: cmd 60/08:00:b6:05:7c/00:00:13:00:00/40 tag >> 0 ncq 4096 in >> [ 7005.420189] res 51/40:08:b6:05:7c/00:00:13:00:00/40 >> Emask 0x409 (media error) <F> >> [ 7005.435710] ata7.00: status: { DRDY ERR } >> [ 7005.439732] ata7.00: error: { UNC } >> [ 7005.455682] ata7.00: configured for UDMA/133 >> [ 7005.459966] sd 6:0:0:0: [sde] Unhandled sense code >> [ 7005.464806] sd 6:0:0:0: [sde] Result: hostbyte=DID_OK >> driverbyte=DRIVER_SENSE >> [ 7005.472074] sd 6:0:0:0: [sde] Sense Key : Medium Error [current] >> [descriptor] >> [ 7005.479374] Descriptor sense data with sense descriptors (in hex): >> [ 7005.485620] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 >> [ 7005.492289] 13 7c 05 b6 >> [ 7005.495601] sd 6:0:0:0: [sde] Add. Sense: Unrecovered read error >> - auto reallocate failed >> [ 7005.503941] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 13 7c 05 b6 00 >> 00 08 00 >> [ 7005.511064] end_request: I/O error, dev sde, sector 326895030 >> [ 7005.516839] ata7: EH complete >> [ 7005.520160] md/raid1:md6: read error corrected (8 sectors at >> 294668640 on sde3) >> [ 7005.527491] md/raid1:md6: redirecting sector 294668400 to other >> mirror: sdf3 >> [ 7010.087434] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 7010.093924] ata7.00: irq_stat 0x40000008 >> [ 7010.097845] ata7.00: failed command: READ FPDMA QUEUED >> [ 7010.103011] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag >> 0 ncq 4096 in >> [ 7010.103012] res 51/40:08:be:05:7c/00:00:13:00:00/40 >> Emask 0x409 (media error) <F> >> [ 7010.118520] ata7.00: status: { DRDY ERR } >> [ 7010.122549] ata7.00: error: { UNC } >> [ 7010.138492] ata7.00: configured for UDMA/133 >> [ 7010.142799] ata7: EH complete >> [ 7014.386961] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 7014.393424] ata7.00: irq_stat 0x40000008 >> [ 7014.397347] ata7.00: failed command: READ FPDMA QUEUED >> [ 7014.402521] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag >> 0 ncq 4096 in >> [ 7014.402522] res 51/40:08:be:05:7c/00:00:13:00:00/40 >> Emask 0x409 (media error) <F> >> [ 7014.418048] ata7.00: status: { DRDY ERR } >> [ 7014.422087] ata7.00: error: { UNC } >> [ 7014.438017] ata7.00: configured for UDMA/133 >> [ 7014.442328] ata7: EH complete >> [ 7018.686482] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 7018.692966] ata7.00: irq_stat 0x40000008 >> [ 7018.697289] ata7.00: failed command: READ FPDMA QUEUED >> [ 7018.702463] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag >> 0 ncq 4096 in >> [ 7018.702465] res 51/40:08:be:05:7c/00:00:13:00:00/40 >> Emask 0x409 (media error) <F> >> [ 7018.718007] ata7.00: status: { DRDY ERR } >> [ 7018.722038] ata7.00: error: { UNC } >> [ 7018.737532] ata7.00: configured for UDMA/133 >> [ 7018.741839] ata7: EH complete >> [ 7022.986007] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 7022.992477] ata7.00: irq_stat 0x40000008 >> [ 7022.996403] ata7.00: failed command: READ FPDMA QUEUED >> [ 7023.001567] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag >> 0 ncq 4096 in >> [ 7023.001568] res 51/40:08:be:05:7c/00:00:13:00:00/40 >> Emask 0x409 (media error) <F> >> [ 7023.017131] ata7.00: status: { DRDY ERR } >> [ 7023.021173] ata7.00: error: { UNC } >> [ 7023.037063] ata7.00: configured for UDMA/133 >> [ 7023.041375] ata7: EH complete >> [ 7027.285527] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 7027.291997] ata7.00: irq_stat 0x40000008 >> [ 7027.295913] ata7.00: failed command: READ FPDMA QUEUED >> [ 7027.301078] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag >> 0 ncq 4096 in >> [ 7027.301080] res 51/40:08:be:05:7c/00:00:13:00:00/40 >> Emask 0x409 (media error) <F> >> [ 7027.316596] ata7.00: status: { DRDY ERR } >> [ 7027.320635] ata7.00: error: { UNC } >> [ 7027.336589] ata7.00: configured for UDMA/133 >> [ 7027.340904] ata7: EH complete >> [ 7031.585052] ata7.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 >> [ 7031.591525] ata7.00: irq_stat 0x40000008 >> [ 7031.595450] ata7.00: failed command: READ FPDMA QUEUED >> [ 7031.600641] ata7.00: cmd 60/08:00:be:05:7c/00:00:13:00:00/40 tag >> 0 ncq 4096 in >> [ 7031.600642] res 51/40:08:be:05:7c/00:00:13:00:00/40 >> Emask 0x409 (media error) <F> >> [ 7031.616150] ata7.00: status: { DRDY ERR } >> [ 7031.620185] ata7.00: error: { UNC } >> [ 7031.636113] ata7.00: configured for UDMA/133 >> [ 7031.640422] sd 6:0:0:0: [sde] Unhandled sense code >> [ 7031.645207] sd 6:0:0:0: [sde] Result: hostbyte=DID_OK >> driverbyte=DRIVER_SENSE >> [ 7031.652470] sd 6:0:0:0: [sde] Sense Key : Medium Error [current] >> [descriptor] >> [ 7031.659746] Descriptor sense data with sense descriptors (in hex): >> [ 7031.665982] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 >> [ 7031.672633] 13 7c 05 be >> [ 7031.675936] sd 6:0:0:0: [sde] Add. Sense: Unrecovered read error >> - auto reallocate failed >> [ 7031.684279] sd 6:0:0:0: [sde] CDB: Read(10): 28 00 13 7c 05 be 00 >> 00 08 00 >> [ 7031.691390] end_request: I/O error, dev sde, sector 326895038 >> [ 7031.697155] ata7: EH complete >> [ 7031.700488] md/raid1:md6: read error corrected (8 sectors at >> 294668648 on sde3) >> [ 7031.707820] md/raid1:md6: redirecting sector 294668648 to other >> mirror: sdf3 >> > >> >> >>> Do you see ''swiotlb'' in your dmesg output? >>> >> $ dmesg | grep swiotlb >> > Forgot -i >Ok, here it is: $ dmesg | grep -i swiotlb $>> $ >> >> >>> Did you follow the PVOPS Wiki >>> about troubleshooting? >>> >> Right now I''m not even trying to work with dom0 or Xen. Just trying to >> get the basic kernel to run on the hardware. >> > So you are running this under baremetal then? >Yes. Regards, Gerry _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2011-Jan-14 08:53 UTC
Re: [Xen-devel] bug: kernel 2.6.37-12 READ FPDMA QUEUED
On 01/13/2011 04:42 PM, Konrad Rzeszutek Wilk wrote:> On Thu, 2011-01-13 at 21:53 +0000, Gerry Reno wrote: > > Please try. Wait .. are you running this with Xen hypervisor? > Not yet.Um, so why on earth are you posting to xen-devel about it then? And did you really not think it was worth mentioning this fact prominently up front? If you have an issue with a bare metal kernel supplied by Ubuntu then you should be reporting it to the Ubuntu kernel maintainers in the first instance. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On 01/14/2011 03:53 AM, Ian Campbell wrote:> On 01/13/2011 04:42 PM, Konrad Rzeszutek Wilk wrote: > >> On Thu, 2011-01-13 at 21:53 +0000, Gerry Reno wrote: >> >>> Please try. Wait .. are you running this with Xen hypervisor? >>> >> Not yet. >> > Um, so why on earth are you posting to xen-devel about it then? And did > you really not think it was worth mentioning this fact prominently up > front? >The whole point of the exercise was to get dom0 and Xen working on this machine. On the way to that I found that I could not even get 2.6.37 running at all on the baremetal. I figured there was just some kernel switch I needed so I searched and then posted on the xen-devel list thinking someone would know what switch might be necessary. But now it seems the problem is somewhat more involved than just a simple setting.> If you have an issue with a bare metal kernel supplied by Ubuntu then > you should be reporting it to the Ubuntu kernel maintainers in the first > instance. >And I have. I found a Ubuntu bug, https://bugs.launchpad.net/ubuntu/+bug/550559, that described the same problem and posted my findings into it. As have many others. Sorry, if this issue was of no interest to you. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel