[Debian-eeepc-devel] Bug#559578: eeepc-acpi-scripts: EeePC 701 freezes with garbled screen while booting

[Alan Jenkins]

On 12/10/09, Darren Salt <linux at youmustbejoking.demon.co.uk> wrote:
> I demand that Alan Jenkins may or may not have written...
>
>> On 12/9/09, Darren Salt <linux at youmustbejoking.demon.co.uk> wrote:
>>> I demand that Alan Jenkins may or may not have written...
>>> [snip]
>>>> If I repeatedly plug and unplug the power adaptor with
>>>> eeepc-acpi-scripts
>>>> installed  (triggering the switch between "performance" and "normal"), I
>>>> see various kernel messages.  These are the kernel init messages for the
>>>> webcam and cardreader, suggesting that they are disappearing and
>>>> re-appearing.  I wasn't able to reproduce it without eeepc-acpi-scripts
>>>> (either by plugging / unplugging repeatedly, or by toggling the value of
>>>> cpufv in a scripted loop, or by both at the same time).
>>> Strange. Some logging may provide some clue; are ACPI events which would
>>> be used to toggle these being generated?
>
>> I'm not sure what you mean.  There's no code in the eeepc-laptop driver to
>> receive events for these settings.  (And I'm pretty sure that my userspace
>> doesn't touch the "cardr" or "camera" files in /sys).  What am I looking
>> for?
>
> Well... for the camera, it could be eeepc-acpi-scripts which is reacting to
> ACPI events. But the card reader would require that there be local changes
> for its apparent presence to be toggled.
>
> # sh -x /etc/acpi/actions/ac_adapter.sh . . 00000080 00000000
> (fake unplugging)
>
> # sh -x /etc/acpi/actions/ac_adapter.sh . . 00000080 00000001
> (fake plugging in)
>
> ... anything unusual?
>
> (That script ignores the first two parameters.)

Thanks.

Firstly I played with yanking the power cable again.  I got two
spontaneous reboots, but no error messages.  I suspect this is because
the battery was no longer full (i.e. it was being charged at the time,
so the EC was running a different code path).

I then found I was able to repduce the error messages by running the
AC adaptor script in a loop (doing repeated fake plugging in +out with
no delay in between).  Turns out I should have read the error messages
more carefully - this treatment is triggering a failure of the USB
controller:

[ 2187.458888] ehci_hcd 0000:00:1d.7: fatal error
[ 2187.462878] ehci_hcd 0000:00:1d.7: HC died; cleaning up
[ 2187.465903] usb 1-5: USB disconnect, address 2
[ 2187.480014] usb 1-8: USB disconnect, address 3
[ 2187.720095] usb 4-1: new full speed USB device using uhci_hcd and
address 2
[ 2187.864129] usb 4-1: not running at top speed; connect to a high
speed hub
[ 2187.894092] usb 4-1: New USB device found, idVendor=0951,
idProduct=1606
[ 2187.896323] usb 4-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=4
[ 2187.898062] usb 4-1: Product: UB6225
[ 2187.899492] usb 4-1: Manufacturer: ENE
[ 2187.901227] usb 4-1: SerialNumber: 146030377350
[ 2187.904365] usb 4-1: configuration #1 chosen from 1 choice
[ 2187.922780] scsi3 : SCSI emulation for USB Mass Storage devices
[ 2187.926404] usb-storage: device found at 2
[ 2187.926412] usb-storage: waiting for device to settle before
scanning
[ 2188.036065] usb 5-2: new full speed USB device using uhci_hcd and
address 2
[ 2188.180115] usb 5-2: not running at top speed; connect to a high
speed hub
[ 2188.193091] usb 5-2: New USB device found, idVendor=eb1a,
idProduct=2761
[ 2188.195609] usb 5-2: New USB device strings: Mfr=0, Product=0,
SerialNumber=0
[ 2188.200652] usb 5-2: configuration #1 chosen from 1 choice
[ 2188.209258] uvcvideo: Found UVC 1.00 device <unnamed> (eb1a:2761)
[ 2188.386873] uhci_hcd 0000:00:1d.3: host system error, PCI problems?
[ 2188.389629] uhci_hcd 0000:00:1d.3: host controller halted, very
bad!
[ 2188.390859] uhci_hcd 0000:00:1d.3: HC died; cleaning up
[ 2192.925190] usb-storage: device scan complete
[ 2192.928492] scsi 3:0:0:0: Direct-Access     USB2.0   CardReader SD0
  0100 PQ: 0 ANSI: 0
[ 2193.212036] uvcvideo: UVC non compliance - GET_DEF(PROBE) not
supported. Enabling workaround.
[ 2193.215074] uvcvideo: Failed to query (129) UVC probe control : -19
(exp. 26).
[ 2193.216196] uvcvideo: Failed to initialize the device (-5).
[ 2193.220184] usb 5-2: USB disconnect, address 2
[ 2193.319137] sd 3:0:0:0: [sdb] 15660032 512-byte logical blocks:
(8.01 GB/7.46 GiB)
[ 2193.324125] sd 3:0:0:0: [sdb] Write Protect is off
[ 2193.327385] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 2193.327393] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 2193.344120] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 2193.347203]  sdb: sdb1
[ 2193.365631] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[ 2193.368019] sd 3:0:0:0: [sdb] Attached SCSI removable disk
...
[ 2373.514267] sd 3:0:0:0: timing out command, waited 180s
[ 2373.514295] sd 3:0:0:0: [sdb] Unhandled sense code
[ 2373.514302] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2373.514313] sd 3:0:0:0: [sdb] Sense Key : Hardware Error [current]
[ 2373.514328] sd 3:0:0:0: [sdb] Add. Sense: Unrecovered read error
[ 2373.514343] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 ee f3 f0 00 00 08 00
[ 2373.514371] end_request: I/O error, dev sdb, sector 15660016
[ 2373.514382] Buffer I/O error on device sdb, logical block 1957502
[ 2553.522235] sd 3:0:0:0: timing out command, waited 180s
[ 2553.522260] sd 3:0:0:0: [sdb] Unhandled sense code
[ 2553.522267] sd 3:0:0:0: [sdb] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
[ 2553.522279] sd 3:0:0:0: [sdb] Sense Key : Hardware Error [current]
[ 2553.522294] sd 3:0:0:0: [sdb] Add. Sense: Unrecovered read error
[ 2553.522309] sd 3:0:0:0: [sdb] CDB: Read(10): 28 00 00 ee f3 f0 00 00 08 00
[ 2553.522336] end_request: I/O error, dev sdb, sector 15660016
[ 2553.522348] Buffer I/O error on device sdb, logical block 1957502

Regards
Alan