sata_via hotplug does not work

The Hardy Heron Alpha2 release will be coming out soon. It will have an updated version of the kernel. It would be great if you could test with this new release and verify if this issue still exists. I'll be sure to update this report when Alpha2 is available. Thanks!

I'm opened a new task against the actively developed kernel. However, because there exists a workaround, I'm closing the report against linux-source-2.6.22 as it does not meet the criteria for a stable release update. You can learn more about the stable release update process at https://wiki.ubuntu.com/StableReleaseUpdates . Thanks!

Also can you provide the output of lspci -vvv?

Thanks
chuck

You can download and try the new Hardy Heron Alpha2 release from http://cdimage.ubuntu.com/releases/hardy/alpha-2/ . You should be able to then test the new kernel via the LiveCD. General information regarding the release can also be found here: http://www.ubuntu.com/testing/hardy/alpha2 . Thanks!

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

Hello Leann,

I came across this report when I was attempting to solve a very similar sounding issue to the reported above. I thought I would give you my feedback...

I was using Hardy 8.04.1 on x86. I have a RAID bus controller: VIA Technologies, Inc. VT6421 IDE RAID Controller (rev 50) card which was also not showing any drives which attached.

I have installed 8.10 Alpha 5 (a clean install - the upgrade did not appear to work very well). But now it appears that the clean install does the same thing, it takes a _very_ long time to start up, at first I actually thought it never would which is why I reinstalled.

The machine is quite old, a 1GHz Athlon, but it is not intended to be under much load.

I have attached the information which was requested above, the results of dmesg and lspci -vvv

I still do not see the attched drives, although another time I started up, gparted did see one of the two drives.

Regards,

Jerry

Just a follow up.

It seems that the long start up with lots of errors logged is intermittent. Other times it seems to start up reasonably quickly. Gparted still only sees one drive of the two attached to the RAID controller. The controller is a SafeCom SATAV-3S1U a three channel controller. It is configured for no RAID (JBOD mode).

Here are the results of dmesg and lspci from when boot up was quick...
[dmesg]:
[ 0.000000] Initializing cgroup subsys cpuset
[ 0.000000] Initializing cgroup subsys cpu
[ 0.000000] Linux version 2.6.27-2-generic (buildd@palmer) (gcc version 4.3.2 (Ubuntu 4.3.2-0ubuntu1) ) #1 SMP Thu Aug 28 17:20:02 UTC 2008 (Ubuntu 2.6.27-2.3-generic)
[ 0.000000] BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: 0000000000000000 - 000000000009fc00 (usable)
[ 0.000000] BIOS-e820: 000000000009fc00 - 00000000000a0000 (reserved)
[ 0.000000] BIOS-e820: 00000000000f0000 - 0000000000100000 (reserved)
[ 0.000000] BIOS-e820: 0000000000100000 - 0000000027ff0000 (usable)
[ 0.000000] BIOS-e820: 0000000027ff0000 - 0000000027ff8000 (ACPI data)
[ 0.000000] BIOS-e820: 0000000027ff8000 - 0000000028000000 (ACPI NVS)
[ 0.000000] BIOS-e820: 00000000ffff0000 - 0000000100000000 (reserved)
[ 0.000000] last_pfn = 0x27ff0 max_arch_pfn = 0x100000
[ 0.000000] kernel direct mapping tables up to 27ff0000 @ 7000-d000
[ 0.000000] RAMDISK: 2781e000 - 27fdf05f
[ 0.000000] DMI 2.3 present.
[ 0.000000] ACPI: RSDP 000FABB0, 0014 (r0 AMI )
[ 0.000000] ACPI: RSDT 27FF0000, 0028 (r1 AMIINT 10 MSFT 97)
[ 0.000000] ACPI: FACP 27FF0030, 0074 (r1 AMIINT 10 MSFT 97)
[ 0.000000] ACPI: DSDT 27FF00B0, 1E4B (r1 AMD75X IRONGATE 1000 MSFT 100000B)
[ 0.000000] ACPI: FACS 27FF8000, 0040
[ 0.000000] 0MB HIGHMEM available.
[ 0.000000] 639MB LOWMEM available.
[ 0.000000] mapped low ram: 0 - 27ff0000
[ 0.000000] low ram: 00000000 - 27ff0000
[ 0.000000] bootmap 00009000 - 0000e000
[ 0.000000] (9 early reservations) ==> bootmem [0000000000 - 0027ff0000]
[ 0.000000] #0 [0000000000 - 0000001000] BIOS data page ==> [0000000000 - 0000001000]
[ 0.000000] #1 [0000001000 - 0000002000] EX TRAMPOLINE ==> [0000001000 - 0000002000]
[ 0.000000] #2 [0000006000 - 0000007000] TRAMPOLINE ==> [0000006000 - 0000007000]
[ 0.000000] #3 [0000100000 - 00005dfba0] TEXT DATA BSS ==> [0000100000 - 00005dfba0]
[ 0.000000] #4 [002781e000 - 0027fdf05f] RAMDISK ==> [002781e000 - 0027fdf05f]
[ 0.000000] #5 [00005e0000 - 00005e3000] INIT_PG_TABLE ==> [00005e0000 - 00005e3000]
[ 0.000000] #6 [000009f400 - 0000100000] BIOS reserved ==> [000009f400 - 0000100000]
[ 0.000000] #7 [0000007000 - 0000009000] PGTABLE ==> [0000007000 - 0000009000]
[ 0.000000] #8 [0000009000 - 000000e000] BOOTMAP ==> [0000009000 - 000000e000]
[ 0.000000] Zone PFN ranges:
[ 0.000000] DMA 0x00000000 -> 0x00001000
[ 0.000000] Normal 0x00001000 -> 0x00027ff0
[ 0.000000] HighMem 0x00027ff0 -> 0x00027ff0
[ 0.000000] Movable zone start PFN for each node
[ 0.000000] early_node_map[2] activ...

Another boot and this time gparted sees both drives attached to the SATA drive. Gparted is very slow to do anything though. Took a long time (more than 5 minutes - I left it then) to scan devices.

Getting repeated errors in kernel log:
Sep 12 07:26:45 Foundation kernel: [32670.916207] ata4.00: status: { DRDY }
Sep 12 07:26:45 Foundation kernel: [32670.916225] ata4: hard resetting link
Sep 12 07:26:46 Foundation kernel: [32671.640144] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 12 07:26:46 Foundation kernel: [32671.685719] ata4.00: configured for UDMA/33
Sep 12 07:26:46 Foundation kernel: [32671.685782] ata4: EH complete
Sep 12 07:26:46 Foundation kernel: [32671.695524] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
Sep 12 07:26:46 Foundation kernel: [32671.698391] sd 3:0:0:0: [sdc] Write Protect is off
Sep 12 07:26:46 Foundation kernel: [32671.698403] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Sep 12 07:26:46 Foundation kernel: [32671.706136] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Sep 12 07:27:16 Foundation kernel: [32701.752165] ata4.00: exception Emask 0x12 SAct 0x0 SErr 0x18b0400 action 0xe frozen
Sep 12 07:27:16 Foundation kernel: [32701.752195] ata4: SError: { Proto PHYRdyChg PHYInt 10B8B LinkSeq TrStaTrns }
Sep 12 07:27:16 Foundation kernel: [32701.752212] ata4.00: cmd c8/00:01:04:00:00/00:00:00:00:00/e0 tag 0 dma 512 in
Sep 12 07:27:16 Foundation kernel: [32701.752216] res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x16 (ATA bus error)
Sep 12 07:27:16 Foundation kernel: [32701.752223] ata4.00: status: { DRDY }
Sep 12 07:27:16 Foundation kernel: [32701.752242] ata4: hard resetting link
Sep 12 07:27:18 Foundation kernel: [32704.076136] ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
Sep 12 07:27:18 Foundation kernel: [32704.124518] ata4.00: configured for UDMA/33
Sep 12 07:27:18 Foundation kernel: [32704.124582] ata4: EH complete
Sep 12 07:27:18 Foundation kernel: [32704.136131] sd 3:0:0:0: [sdc] 781422768 512-byte hardware sectors (400088 MB)
Sep 12 07:27:18 Foundation kernel: [32704.136979] sd 3:0:0:0: [sdc] Write Protect is off
Sep 12 07:27:18 Foundation kernel: [32704.136991] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00
Sep 12 07:27:18 Foundation kernel: [32704.137709] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA

Appears to me that although sdc is seen now, the system doesn't like it! Keeps resetting and reconnecting.

Care to confirm this is still an issue with the latest pre-release of Jaunty - http://cdimage.ubuntu.com/releases/jaunty/alpha-2/ . Thanks.

Sorry, I thought that I had posted my update in here already.

I upgraded my kernel to the 2.6.27 as suggested and this worked fine...

Thanks, marking this Fix Released.