I second that. The .37-rc3 mainline kernel works as expected.
But i also vote for fixing it in maverick ... not everyone likes to
run bleeding edge packages.
2010/12/6 Mathieu Simon <email address hidden>:
> Hi Fabio and Florian
>
> I can confirm that the phison module works again using a 2.6.37-rc3
> kernel. A dmesg output looks sane compared to what I got using 2.6.35
> and .36-based kernels. Output looks same/similar to what I got under
> 2.6.34 where the driver worked last time.
>
> uname -a
> Linux n-sim-01 2.6.37-020637rc3-generic #201011220905 SMP Mon Nov 22 09:08:55 UTC 2010 x86_64 GNU/Linux
>
> I'd really like to see this bug fixed in maverick's kernel images,
> essentially because it resulted out of a merge error that happened
> upstream and it's fix is trivial.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/669343
>
> Title:
> [staging] phison Module broken: ExpressCard SSD not usable
>
> Status in “linux” package in Ubuntu:
> Triaged
>
> Bug description:
> Description: Ubuntu 10.10
> Release: 10.10
>
> I have been using a Verbatim 32GB SSD ExpressCard that is attached via PCIe as a IDE drive.
> The card works out of the box in lucid but in maverick dmesg just throws a stack trace.
> Shutdown and reboot are blocked until the card is removed.
>
> The card needs the "phison" module.
>
> Ubuntu lucid amd64 (good)
> [ 23.003156] pciehp 0000:00:1c.3:pcie04: Card present on Slot(3)
> [ 23.130232] pci 0000:05:00.0: reg 10 io port: [0x00-0x07]
> [ 23.130265] pci 0000:05:00.0: reg 14 io port: [0x00-0x03]
> [ 23.130291] pci 0000:05:00.0: reg 18 io port: [0x00-0x07]
> [ 23.130317] pci 0000:05:00.0: reg 1c io port: [0x00-0x03]
> [ 23.130343] pci 0000:05:00.0: reg 20 io port: [0x00-0x0f]
> [ 23.130603] pci 0000:05:00.0: no hotplug settings from platform
> [ 23.130778] pata_acpi 0000:05:00.0: enabling device (0000 -> 0001)
> [ 23.130790] pata_acpi 0000:05:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> [ 23.130847] pata_acpi 0000:05:00.0: setting latency timer to 64
> [ 23.130875] pata_acpi 0000:05:00.0: PCI INT A disabled
> [ 23.137678] phison: module is from the staging directory, the quality is unknown, you have been warned.
> [ 23.138392] phison_e-box 0000:05:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> [ 23.138445] phison_e-box 0000:05:00.0: setting latency timer to 64
> [ 23.138920] scsi4 : phison_e-box
> [ 23.139000] scsi5 : phison_e-box
> [ 23.139033] ata5: PATA max UDMA/100 cmd 0x2010 ctl 0x2020 bmdma 0x2000 irq 19
> [ 23.139035] ata6: PATA max UDMA/100 cmd 0x2018 ctl 0x2024 bmdma 0x2008 irq 19
> [ 23.970550] ata5.00: ATA-7: ExpressCard SSD, PER1.36, max UDMA/133
> [ 23.970553] ata5.00: 62881792 sectors, multi 0: LBA
> [ 23.990561] ata5.00: configured for UDMA/100
> [ 23.990664] scsi 4:0:0:0: Direct-Access ATA ExpressCard SSD PER1 PQ: 0 ANSI: 5
> [ 23.990816] sd 4:0:0:0: Attached scsi generic sg2 type 0
> [ 23.990918] sd 4:0:0:0: [sdb] 62881792 512-byte logical blocks: (32.1 GB/29.9 GiB)
> [ 23.990955] sd 4:0:0:0: [sdb] Write Protect is off
> [ 23.990957] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> [ 23.990976] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
> [ 23.991087] sdb: sdb1
> [ 23.992355] sd 4:0:0:0: [sdb] Attached SCSI disk
>
> Then the partitions can be mounted - all fine,
>
> With maverick the output is rather long, the dmesg paste can be found here:
> http://pastebin.com/gZXyF6FN
>
> Seems to be a regression? :-/
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/669343/+subscribe
>
I second that. The .37-rc3 mainline kernel works as expected.
But i also vote for fixing it in maverick ... not everyone likes to
run bleeding edge packages.
2010/12/6 Mathieu Simon <email address hidden>: 020637rc3- generic #201011220905 SMP Mon Nov 22 09:08:55 UTC 2010 x86_64 GNU/Linux /bugs.launchpad .net/bugs/ 669343 1c.3:pcie04: Card present on Slot(3) pastebin. com/gZXyF6FN /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/669343/ +subscribe
> Hi Fabio and Florian
>
> I can confirm that the phison module works again using a 2.6.37-rc3
> kernel. A dmesg output looks sane compared to what I got using 2.6.35
> and .36-based kernels. Output looks same/similar to what I got under
> 2.6.34 where the driver worked last time.
>
> uname -a
> Linux n-sim-01 2.6.37-
>
> I'd really like to see this bug fixed in maverick's kernel images,
> essentially because it resulted out of a merge error that happened
> upstream and it's fix is trivial.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https:/
>
> Title:
> [staging] phison Module broken: ExpressCard SSD not usable
>
> Status in “linux” package in Ubuntu:
> Triaged
>
> Bug description:
> Description: Ubuntu 10.10
> Release: 10.10
>
> I have been using a Verbatim 32GB SSD ExpressCard that is attached via PCIe as a IDE drive.
> The card works out of the box in lucid but in maverick dmesg just throws a stack trace.
> Shutdown and reboot are blocked until the card is removed.
>
> The card needs the "phison" module.
>
> Ubuntu lucid amd64 (good)
> [ 23.003156] pciehp 0000:00:
> [ 23.130232] pci 0000:05:00.0: reg 10 io port: [0x00-0x07]
> [ 23.130265] pci 0000:05:00.0: reg 14 io port: [0x00-0x03]
> [ 23.130291] pci 0000:05:00.0: reg 18 io port: [0x00-0x07]
> [ 23.130317] pci 0000:05:00.0: reg 1c io port: [0x00-0x03]
> [ 23.130343] pci 0000:05:00.0: reg 20 io port: [0x00-0x0f]
> [ 23.130603] pci 0000:05:00.0: no hotplug settings from platform
> [ 23.130778] pata_acpi 0000:05:00.0: enabling device (0000 -> 0001)
> [ 23.130790] pata_acpi 0000:05:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> [ 23.130847] pata_acpi 0000:05:00.0: setting latency timer to 64
> [ 23.130875] pata_acpi 0000:05:00.0: PCI INT A disabled
> [ 23.137678] phison: module is from the staging directory, the quality is unknown, you have been warned.
> [ 23.138392] phison_e-box 0000:05:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
> [ 23.138445] phison_e-box 0000:05:00.0: setting latency timer to 64
> [ 23.138920] scsi4 : phison_e-box
> [ 23.139000] scsi5 : phison_e-box
> [ 23.139033] ata5: PATA max UDMA/100 cmd 0x2010 ctl 0x2020 bmdma 0x2000 irq 19
> [ 23.139035] ata6: PATA max UDMA/100 cmd 0x2018 ctl 0x2024 bmdma 0x2008 irq 19
> [ 23.970550] ata5.00: ATA-7: ExpressCard SSD, PER1.36, max UDMA/133
> [ 23.970553] ata5.00: 62881792 sectors, multi 0: LBA
> [ 23.990561] ata5.00: configured for UDMA/100
> [ 23.990664] scsi 4:0:0:0: Direct-Access ATA ExpressCard SSD PER1 PQ: 0 ANSI: 5
> [ 23.990816] sd 4:0:0:0: Attached scsi generic sg2 type 0
> [ 23.990918] sd 4:0:0:0: [sdb] 62881792 512-byte logical blocks: (32.1 GB/29.9 GiB)
> [ 23.990955] sd 4:0:0:0: [sdb] Write Protect is off
> [ 23.990957] sd 4:0:0:0: [sdb] Mode Sense: 00 3a 00 00
> [ 23.990976] sd 4:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
> [ 23.991087] sdb: sdb1
> [ 23.992355] sd 4:0:0:0: [sdb] Attached SCSI disk
>
> Then the partitions can be mounted - all fine,
>
> With maverick the output is rather long, the dmesg paste can be found here:
> http://
>
> Seems to be a regression? :-/
>
> To unsubscribe from this bug, go to:
> https:/
>