| 2009-03-28 20:03:14 |
Dan Dart |
bug |
|
|
added bug |
| 2009-03-29 05:15:48 |
Paul Dufresne |
linux: status |
New |
Incomplete |
|
| 2009-03-29 05:15:48 |
Paul Dufresne |
linux: statusexplanation |
|
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
|
| 2009-03-29 10:35:39 |
Dan Dart |
bug |
|
|
added attachment 'dmesg.log' (dmesg on working system, with hpet=disable) |
| 2009-03-29 10:36:07 |
Dan Dart |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci on working system) |
| 2009-03-29 10:36:15 |
Dan Dart |
bug |
|
|
added attachment 'dmesg.log' (dmesg.log) |
| 2009-03-29 10:36:15 |
Dan Dart |
bug |
|
|
added attachment 'lspci-vvnn.log' (lspci-vvnn.log) |
| 2009-03-29 16:48:09 |
Paul Dufresne |
linux: status |
Incomplete |
Confirmed |
|
| 2009-03-29 16:48:09 |
Paul Dufresne |
linux: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies Thanks in advance! |
We should probably call it a SATA-1.5Gb/s jumper, because when it is there, the speed is limited.
When it is not there, auto-negotiation is supposed to be made with motherboard (if it supports it).
Anyway, in your case, the motherboards supports it: 4 SATA 3Gb/s connector
I would give the link normally, but there seems to be a bad bug with my mozilla.
Your dmesg log suggest it has some problem to reset the hard disk:
[ 2.008723] scsi3 : ahci
[ 2.008823] ata1: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f100 irq 22
[ 2.008827] ata2: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f180 irq 22
[ 2.008830] ata3: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f200 irq 22
[ 2.008833] ata4: SATA max UDMA/133 abar m1024@0xfe02f000 port 0xfe02f280 irq 22
[ 2.492100] ata1: softreset failed (device not ready)
[ 2.492106] ata1: failed due to HW bug, retry pmp=0
[ 2.656036] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 2.657264] ata1.00: HPA unlocked: 488395055 -> 488397168, native 488397168
[ 2.657269] ata1.00: ATA-7: MAXTOR STM3250310AS, 3.AAF, max UDMA/133
[ 2.657271] ata1.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
[ 2.657277] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 2.658015] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[ 2.658017] ata1.00: configured for UDMA/133
[ 2.976035] ata2: SATA link down (SStatus 0 SControl 300)
[ 3.296033] ata3: SATA link down (SStatus 0 SControl 300)
[ 3.616034] ata4: SATA link down (SStatus 0 SControl 300)
[ 3.616080] isa bounce pool size: 16 pages
I think this bug have enough info for a member of the kernel team to begin investigating.
So I am confirming it. |
|
| 2009-03-31 21:03:21 |
Dan Dart |
bug |
|
|
added attachment 'dmesg-9.04' (dmesg-9.04) |
| 2009-04-01 06:03:08 |
Paul Dufresne |
bug |
|
|
assigned to linux (openSUSE) |
| 2009-04-01 06:11:57 |
Bug Watch Updater |
linux: status |
Unknown |
Fix Released |
|
| 2009-04-01 06:49:32 |
Paul Dufresne |
description |
Ubuntu 8.10 kernel (2.6.27) succeeds booting but only on hpet=disable
Self-compiled kernels up to 2.6.28.2 succeed to boot on ubuntu 8.04 (no initrd)
Anything higher (2.6.28.3+ on Ubuntu 8.10) fails to boot with messages about not being able to find the hard disk, and drops to a prompt (evidently the hard disk was found but appears in /sys as an error instead of /dev)
2.6.29 on Ubuntu 8.10 fails to boot, and lists the disks that the ATA system found (includes hard disk) but gets to a kernel panic because it cannot find (0,0) or the sda device node.
Ubuntu 9.04 kernel (2.6.28.8 based) fails to boot, dropping to busybox prompt, even with acpi=off, nolapic, noapic, hpet=disable, edd=on, "verbose" replacing "splash silent" options. and on expert mode, the messages when finding an ext3 filesystem loop over and over before it gets to busybox.
Motherboard: Gigabyte GA-MA69VM-S2, SATA300 jumper on Maxtor disk removed.
AMD Athlon X2 4800+ 2.5GHz virtualisation enabled
2 GB DDR800 RAM
Cheers! |
{ begin edit section by Paul}
SB600 and SB700 pre revision A21 are problematic on ATI RS690 host bridge:
According to OpenSuse bug, both options are needed: "acpi=off pci=nomsi"
http://lkml.org/lkml/2008/1/24/431
Looks like some patch was given on Linux mailing list but unclear to me if it was finally accepted:
http://lkml.org/lkml/2008/1/24/484
{close edit section }
Ubuntu 8.10 kernel (2.6.27) succeeds booting but only on hpet=disable
Self-compiled kernels up to 2.6.28.2 succeed to boot on ubuntu 8.04 (no initrd)
Anything higher (2.6.28.3+ on Ubuntu 8.10) fails to boot with messages about not being able to find the hard disk, and drops to a prompt (evidently the hard disk was found but appears in /sys as an error instead of /dev)
2.6.29 on Ubuntu 8.10 fails to boot, and lists the disks that the ATA system found (includes hard disk) but gets to a kernel panic because it cannot find (0,0) or the sda device node.
Ubuntu 9.04 kernel (2.6.28.8 based) fails to boot, dropping to busybox prompt, even with acpi=off, nolapic, noapic, hpet=disable, edd=on, "verbose" replacing "splash silent" options. and on expert mode, the messages when finding an ext3 filesystem loop over and over before it gets to busybox.
Motherboard: Gigabyte GA-MA69VM-S2, SATA300 jumper on Maxtor disk removed.
AMD Athlon X2 4800+ 2.5GHz virtualisation enabled
2 GB DDR800 RAM
Cheers! |
|
| 2009-04-01 06:49:32 |
Paul Dufresne |
title |
Gigabyte GA-MA69VM-S2 does not boot Jaunty |
SB600 IDE controller on ATI-RS690 host bridge = Busybox |
|
| 2009-04-01 15:54:03 |
Dan Dart |
bug |
|
|
added attachment 'dmesg' (dmesg with pci=nomsi acpi=off) |
| 2009-04-01 17:53:47 |
Paul Dufresne |
description |
{ begin edit section by Paul}
SB600 and SB700 pre revision A21 are problematic on ATI RS690 host bridge:
According to OpenSuse bug, both options are needed: "acpi=off pci=nomsi"
http://lkml.org/lkml/2008/1/24/431
Looks like some patch was given on Linux mailing list but unclear to me if it was finally accepted:
http://lkml.org/lkml/2008/1/24/484
{close edit section }
Ubuntu 8.10 kernel (2.6.27) succeeds booting but only on hpet=disable
Self-compiled kernels up to 2.6.28.2 succeed to boot on ubuntu 8.04 (no initrd)
Anything higher (2.6.28.3+ on Ubuntu 8.10) fails to boot with messages about not being able to find the hard disk, and drops to a prompt (evidently the hard disk was found but appears in /sys as an error instead of /dev)
2.6.29 on Ubuntu 8.10 fails to boot, and lists the disks that the ATA system found (includes hard disk) but gets to a kernel panic because it cannot find (0,0) or the sda device node.
Ubuntu 9.04 kernel (2.6.28.8 based) fails to boot, dropping to busybox prompt, even with acpi=off, nolapic, noapic, hpet=disable, edd=on, "verbose" replacing "splash silent" options. and on expert mode, the messages when finding an ext3 filesystem loop over and over before it gets to busybox.
Motherboard: Gigabyte GA-MA69VM-S2, SATA300 jumper on Maxtor disk removed.
AMD Athlon X2 4800+ 2.5GHz virtualisation enabled
2 GB DDR800 RAM
Cheers! |
{ begin edit section by Paul}
SB600 and SB700 pre revision A21 are problematic on ATI RS690 host bridge:
Workaround "acpi=off pci=nomsi" did not work.
http://lkml.org/lkml/2008/1/24/431
Looks like some patch was given on Linux mailing list but unclear to me if it was finally accepted:
http://lkml.org/lkml/2008/1/24/484
{close edit section }
Ubuntu 8.10 kernel (2.6.27) succeeds booting but only on hpet=disable
Self-compiled kernels up to 2.6.28.2 succeed to boot on ubuntu 8.04 (no initrd)
Anything higher (2.6.28.3+ on Ubuntu 8.10) fails to boot with messages about not being able to find the hard disk, and drops to a prompt (evidently the hard disk was found but appears in /sys as an error instead of /dev)
2.6.29 on Ubuntu 8.10 fails to boot, and lists the disks that the ATA system found (includes hard disk) but gets to a kernel panic because it cannot find (0,0) or the sda device node.
Ubuntu 9.04 kernel (2.6.28.8 based) fails to boot, dropping to busybox prompt, even with acpi=off, nolapic, noapic, hpet=disable, edd=on, "verbose" replacing "splash silent" options. and on expert mode, the messages when finding an ext3 filesystem loop over and over before it gets to busybox.
Motherboard: Gigabyte GA-MA69VM-S2, SATA300 jumper on Maxtor disk removed.
AMD Athlon X2 4800+ 2.5GHz virtualisation enabled
2 GB DDR800 RAM
Cheers! |
|
| 2009-04-01 17:53:47 |
Paul Dufresne |
title |
SB600 IDE controller on ATI-RS690 host bridge = Busybox |
SB600/RS690 multiple EXT3-fs: mounted filesystem with ordered data mode. -> Busybox |
|
| 2009-04-19 16:55:40 |
Dan Dart |
bug watch added |
|
http://bugzilla.kernel.org/show_bug.cgi?id=12962 |
|
| 2009-04-19 16:55:40 |
Dan Dart |
bug task added |
|
linux |
|
| 2009-04-19 17:45:13 |
Bug Watch Updater |
linux: status |
Unknown |
Confirmed |
|
| 2009-05-03 22:05:02 |
acfrazier |
attachment added |
|
Dmesg output from 9.04 livecd boot. http://launchpadlibrarian.net/26292304/dmesg.out |
|
| 2009-05-03 22:05:50 |
acfrazier |
attachment added |
|
lshw output from working Ubuntu 8.10 LiveCD http://launchpadlibrarian.net/26292348/lshw.out |
|
| 2009-05-06 17:47:18 |
Dan Dart |
summary |
SB600/RS690 multiple EXT3-fs: mounted filesystem with ordered data mode. -> Busybox |
Jaunty does not boot from USB on SB600/RS690 |
|
| 2009-05-06 18:01:13 |
Dan Dart |
attachment added |
|
dmesg http://launchpadlibrarian.net/26402129/dmesg |
|
| 2009-05-16 07:48:25 |
Sergey Zelenev |
attachment added |
|
HP_T5730_Ubuntu_9_04_AMD64_dmesg http://launchpadlibrarian.net/26802320/HP_T5730_Ubuntu_9_04_AMD64_dmesg |
|
| 2009-05-16 07:50:24 |
Sergey Zelenev |
attachment added |
|
HP_T5730_Ubuntu_9_04_AMD64_lspci-vvnn http://launchpadlibrarian.net/26802362/HP_T5730_Ubuntu_9_04_AMD64_lspci-vvnn |
|
| 2009-05-16 07:54:01 |
Sergey Zelenev |
attachment added |
|
HP_T5730_Ubuntu_9_04_AMD64_dmidecode http://launchpadlibrarian.net/26802455/HP_T5730_Ubuntu_9_04_AMD64_dmidecode |
|
| 2009-08-06 17:43:07 |
Daniel Kulesz |
attachment added |
|
thintune_lspci.txt http://launchpadlibrarian.net/29968383/thintune_lspci.txt |
|
| 2011-07-14 03:53:06 |
Brad Figg |
linux (Ubuntu): status |
Confirmed |
Won't Fix |
|
| 2012-06-01 10:49:33 |
Bug Watch Updater |
linux: status |
Confirmed |
Expired |
|
| 2012-10-08 09:50:15 |
Bug Watch Updater |
linux (openSUSE): importance |
Unknown |
High |
|
