sony-vaio-z-series team mailing list archive

["Craig S. Blackie" <craig@xxxxxxxxxxxxxxxxx>]

Thank you! My VPC-Z11C5E now reboots normally. 

On Wed, 2013-09-25 at 02:04 -0700, Brett Howard wrote:
> Thanks much for the work kind sir.  I've not got a Bugzilla account so
> I can't post this to the bug but I will state that my VPCZ12CGX also
> has this issue and it is resolved by passing the kernel parameter.  
> 
> 
> Here is my output from dmidecode:
> # dmidecode 2.11
> SMBIOS 2.4 present.
> 18 structures occupying 738 bytes.
> Table at 0x000FF500.
> 
> 
> Handle 0x0000, DMI type 0, 24 bytes
> BIOS Information
> Vendor: INSYDE
> Version: R3030C3
> Release Date: 07/30/2010
> ROM Size: 2048 kB
> Characteristics:
> PCI is supported
> PNP is supported
> BIOS is upgradeable
> BIOS shadowing is allowed
> Boot from CD is supported
> Selectable boot is supported
> EDD is supported
> 8042 keyboard services are supported (int 9h)
> CGA/mono video services are supported (int 10h)
> ACPI is supported
> USB legacy is supported
> Smart battery is supported
> BIOS boot specification is supported
> Function key-initiated network boot is supported
> Targeted content distribution is supported
> BIOS Revision: 30.30
> Firmware Revision: 30.30
> 
> 
> Handle 0x0001, DMI type 1, 27 bytes
> System Information
> Manufacturer: Sony Corporation
> Product Name: VPCZ12CGX
> Version: J004A1P1
> Serial Number: 54024526-0001410
> UUID: B04FA3FA-E388-DF11-9C53-0024BED6DF9D
> Wake-up Type: Power Switch
> SKU Number: N/A
> Family: VAIO
> 
> 
> Handle 0x0002, DMI type 2, 10 bytes
> Base Board Information
> Manufacturer: Sony Corporation
> Product Name: VAIO
> Version: N/A
> Serial Number: N/A
> Asset Tag: N/A
> Features:
> Board is a hosting board
> 
> 
> Handle 0x0003, DMI type 3, 17 bytes
> Chassis Information
> Manufacturer: Sony Corporation
> Type: Notebook
> Lock: Not Present
> Version: N/A
> Serial Number: N/A
> Asset Tag: N/A
> Boot-up State: Safe
> Power Supply State: Safe
> Thermal State: Safe
> Security Status: None
> OEM Information: 0x00000000
> 
> 
> Handle 0x0004, DMI type 11, 5 bytes
> OEM Strings
> String 1: 0000067810A
> String 2: FNC-EXTB
> String 3: 9EL73EjlxzzEwsjltqxEwgoltnXdx5es_VJkjhRzzEpkjltrzE
> String 4: Reserved
> String 5: 6.0.3.1195
> 
> 
> Handle 0x0005, DMI type 32, 20 bytes
> System Boot Information
> Status: No errors detected
> 
> 
> Handle 0x0006, DMI type 136, 11 bytes
> OEM-specific Type
> Header and Data:
> 88 0B 06 00 01 44 49 52 53 12 06
> Strings:
> Sony Corporation
> 
> 
> Handle 0x0007, DMI type 16, 15 bytes
> Physical Memory Array
> Location: System Board Or Motherboard
> Use: System Memory
> Error Correction Type: None
> Maximum Capacity: Unknown
> Error Information Handle: Not Provided
> Number Of Devices: 2
> 
> 
> Handle 0x0008, DMI type 17, 21 bytes
> Memory Device
> Array Handle: 0x0007
> Error Information Handle: Not Provided
> Total Width: 64 bits
> Data Width: 64 bits
> Size: 4096 MB
> Form Factor: SODIMM
> Set: None
> Locator: SODIMM1
> Bank Locator: Bank 0
> Type: Unknown
> Type Detail: Unknown
> 
> 
> Handle 0x0009, DMI type 20, 19 bytes
> Memory Device Mapped Address
> Starting Address: 0x00000000000
> Ending Address: 0x000FFFFFFFF
> Range Size: 4 GB
> Physical Device Handle: 0x0008
> Memory Array Mapped Address Handle: 0x000C
> Partition Row Position: Unknown
> Interleave Position: Unknown
> Interleaved Data Depth: Unknown
> 
> 
> Handle 0x000A, DMI type 17, 21 bytes
> Memory Device
> Array Handle: 0x0007
> Error Information Handle: Not Provided
> Total Width: 64 bits
> Data Width: 64 bits
> Size: 4096 MB
> Form Factor: SODIMM
> Set: None
> Locator: SODIMM2
> Bank Locator: Bank 1
> Type: Unknown
> Type Detail: Unknown
> 
> 
> Handle 0x000B, DMI type 20, 19 bytes
> Memory Device Mapped Address
> Starting Address: 0x00100000000
> Ending Address: 0x001FFFFFFFF
> Range Size: 4 GB
> Physical Device Handle: 0x000A
> Memory Array Mapped Address Handle: 0x000C
> Partition Row Position: Unknown
> Interleave Position: Unknown
> Interleaved Data Depth: Unknown
> 
> 
> Handle 0x000C, DMI type 19, 15 bytes
> Memory Array Mapped Address
> Starting Address: 0x00000000000
> Ending Address: 0x001FFFFFFFF
> Range Size: 8 GB
> Physical Array Handle: 0x0007
> Partition Width: 2
> 
> 
> Handle 0x000D, DMI type 4, 35 bytes
> Processor Information
> Socket Designation: N/A
> Type: Central Processor
> Family: Other
> Manufacturer: GenuineIntel
> ID: 52 06 02 00 FF FB EB BF
> Version: Intel(R) Core(TM) i5 CPU       M 540  @ 2.53GHz
> Voltage: 1.4 V
> External Clock: 133 MHz
> Max Speed: 2533 MHz
> Current Speed: 2533 MHz
> Status: Populated, Enabled
> Upgrade: None
> L1 Cache Handle: 0x000F
> L2 Cache Handle: 0x0010
> L3 Cache Handle: 0x000E
> Serial Number: N/A
> Asset Tag: N/A
> Part Number: N/A
> 
> 
> Handle 0x000E, DMI type 7, 19 bytes
> Cache Information
> Socket Designation: L3 Cache
> Configuration: Enabled, Not Socketed, Level 3
> Operational Mode: Write Back
> Location: Internal
> Installed Size: 3072 kB
> Maximum Size: 3072 kB
> Supported SRAM Types:
> Unknown
> Installed SRAM Type: Unknown
> Speed: Unknown
> Error Correction Type: Single-bit ECC
> System Type: Unified
> Associativity: 16-way Set-associative
> 
> 
> Handle 0x000F, DMI type 7, 19 bytes
> Cache Information
> Socket Designation: L1 Cache
> Configuration: Enabled, Not Socketed, Level 1
> Operational Mode: Write Back
> Location: Internal
> Installed Size: 128 kB
> Maximum Size: 128 kB
> Supported SRAM Types:
> Unknown
> Installed SRAM Type: Unknown
> Speed: Unknown
> Error Correction Type: Unknown
> System Type: Unknown
> Associativity: Unknown
> 
> 
> Handle 0x0010, DMI type 7, 19 bytes
> Cache Information
> Socket Designation: L2 Cache
> Configuration: Enabled, Not Socketed, Level 2
> Operational Mode: Write Back
> Location: Internal
> Installed Size: 512 kB
> Maximum Size: 512 kB
> Supported SRAM Types:
> Unknown
> Installed SRAM Type: Unknown
> Speed: Unknown
> Error Correction Type: Single-bit ECC
> System Type: Unified
> Associativity: 8-way Set-associative
> 
> 
> Handle 0x0011, DMI type 127, 4 bytes
> End Of Table
> 
> 
> 
> 
> Thanks 
> 
> 
> ~Brett
> 
> 
> On Wed, Sep 25, 2013 at 1:38 AM, Adam Williamson <awilliam@xxxxxxxxxx>
> wrote:
>         Hi, folks. I'm still trucking with my VPCZ1112GD (alongside
>         its
>         still-inferior-in-some-ways Dell XPS 13 'replacement'), and
>         have been
>         irked for some months with it taking an awfully long time to
>         shut down /
>         reboot. I've noticed two threads in the archive which sound
>         similar:
>         
>         https://lists.launchpad.net/sony-vaio-z-series/msg02964.html
>         https://lists.launchpad.net/sony-vaio-z-series/msg02868.html
>         
>         they all talk about shutdown 'hanging', but I suspect the
>         reporters may
>         not have waited long enough to find out it actually *does*
>         finally shut
>         down successfully, after a wait of two minutes or so.
>         
>         Anyway, this week, I did a bit of poking about, and found out
>         that, for
>         me, shutdown/reboot works perfectly if I pass the kernel
>         parameter
>         'reboot=pci'. I filed a bug upstream:
>         
>         https://bugzilla.kernel.org/show_bug.cgi?id=61721
>         
>         and a kernel dev has proposed a patch which basically
>         special-cases the
>         system to use PCI rebooting. However, the proposed patch uses
>         my precise
>         model name, VPCZ1112GD, so it wouldn't work for any other Z
>         variants: I
>         don't think the dev is familiar with the intricacies of Z
>         model numbers.
>         It would probably be helpful, if others are indeed still
>         having issues
>         with slow shutdown/reboot, if you can test if 'reboot=pci'
>         helps, and if
>         so, post in the bug report and include your precise model
>         number or,
>         better, 'dmidecode' output. I suspect the fix should apply to
>         at least
>         Z11, Z13 and probably just all Z1* models, but it'd be good to
>         have data
>         to confirm that. That might get us an upstream fix. Thanks
>         folks!
>         --
>         Adam Williamson
>         Fedora QA Community Monkey
>         IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT
>         happyassassin . net
>         http://www.happyassassin.net
>         
>         
>         
>         
>         _______________________________________________
>         Mailing list: https://launchpad.net/~sony-vaio-z-series
>         Post to     : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
>         Unsubscribe : https://launchpad.net/~sony-vaio-z-series
>         More help   : https://help.launchpad.net/ListHelp
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~sony-vaio-z-series
> Post to     : sony-vaio-z-series@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~sony-vaio-z-series
> More help   : https://help.launchpad.net/ListHelp

-- 
Regards,

Craig S. Blackie

Attachment: signature.asc
Description: This is a digitally signed message part