Re: Turning off camera also kills card reader on EeePC 900

Re: Turning off camera also kills card reader on EeePC 900

[Sitsofe Wheeler]

> Alan Jenkins wrote:
>> Sitsofe Wheeler wrote:
>>>
>>> Alan Jenkins wrote:
>>>
>>>> - It might be necessary to compare with the pre-installed OS
>>>>  - Is the pre-installed kernel any better (files might be under
>>>> /proc/acpi/asus instead)?  I guess you might not have the time or
>>>> resources to test that though.
>>>
>>> The Xandros 2.6.21.4-eeepc install has the following files in 
>>> /proc/acpi/asus/
>>> brn camera cardr cpufv disp hdps init type wlan
>>>
>>> I have no idea what cpufv, disp, hdps, init or type are. Doing echo 1 
>>> > camera && echo 0 > camera under this setup does NOT disappear the 
>>> SD card.
>> Rats.  So there is some secret the mainline driver is missing :-(.

So I got around to downloading those my 4 pieces of rar and poking about 
the source. For those who are curious inside the rars is a tar.bz2 file 
of a tree of .debs. A few hints:

DON'T download the source from China if you aren't in China it's very slow.
The global mirrors are hidden behind javascript for some reason whereas 
the Chinese ones are not. Still don't be tempted if you aren't in Japan 
- the downloads were frequently crawling along at less than 
10Kbyte/second and would periodically disconnect themselves.

The bad news for me is that part4 of the .rar archive was always corrupt 
(I redownloaded it and it was still corrupt). The good news is that I 
was able to extract some of the archive.

Here are the much faster links that worked for me:
http://dlcdnet.asus.com/pub/ASUS/EeePC/EeePC900/Eee_PC_900_source_code_part1.rar
http://dlcdnet.asus.com/pub/ASUS/EeePC/EeePC900/Eee_PC_900_source_code_part2.rar
http://dlcdnet.asus.com/pub/ASUS/EeePC/EeePC900/Eee_PC_900_source_code_part3.rar
http://dlcdnet.asus.com/pub/ASUS/EeePC/EeePC900/Eee_PC_900_source_code_part4.rar

MD5SUMs of the good pieces of the above:
48bf55be427b279abfc641c10fe4b0ef  Eee_PC_900_source_code_part1.rar
56f8f02cf601c6d82fe4ef824e0b5625  Eee_PC_900_source_code_part2.rar
560d151a90b70b5edabdd9f70cfe7567  Eee_PC_900_source_code_part3.rar

SHA1SUMs of the good pieces of the above:
e6983951b556456677b4d5a77608bc117f3ffe91  Eee_PC_900_source_code_part1.rar
04ec1d1af1014f87ad54476882428ed5090f1742  Eee_PC_900_source_code_part2.rar
09d3b4c1f5356b068d4bfdf4c51dc481b53c5661  Eee_PC_900_source_code_part3.rar

In the linux-source deb there is a folder which contains patches against 
2.6.21.4. For short term convenience I have temporarily repackaged the 
patches here: 
http://sucs.org/~sits/test/eeepc-900/eeepc-kernel-patches.tar.gz 
(contains ALSA patches for the realtek intel_hda, the elantech touchpad 
driver, a pci message patch(?), huawei_usb_storage storage patch (?), 
unionfs patches and aufs patches and a kernel config file).

There is also a separate asus-acpi deb which I have temporarily repacked 
on http://sucs.org/~sits/test/eeepc-900/asus-acpi-p9xx_1.2-1_i386.tar.gz 
. Sadly it seems to contain a prebuilt asus_acpi.ko in /lib/modules 
(along with various scripts to respond to hotkeys etc).

Re: Turning off camera also kills card reader on EeePC 900

[Sitsofe Wheeler]

> On Mon, Sep 15, 2008 at 3:37 PM, Alan Jenkins
> wrote:
> > Sitsofe Wheeler wrote:
> > The "HC died" message is interesting.  Sounds like the controller for
> > these two USB devices stops working.  Maybe try unloading and reloading
> > the ehci module?  I don't think I can help any more though.
> 
> The issue also exist on 701 on 2.6.27-rc7 so the regression is in the
> kernel not in the hardware
> 
[snip]
> 
> So it looks like an ehci_hcd issue when the camera is disabled


And of course, having tried Ingo Molnar's linux-tip (whereas before I was using 2.6.27) I have now found a modern kernel that doesn't exhibit the problem...


      

Re: Turning off camera also kills card reader on EeePC 900

[Pascal Terjan]

On Thu, Sep 25, 2008 at 10:49 PM, Sitsofe Wheeler <sitsofe@yahoo.com> wrote:
>> On Mon, Sep 15, 2008 at 3:37 PM, Alan Jenkins
>> wrote:
>> > Sitsofe Wheeler wrote:
>> > The "HC died" message is interesting.  Sounds like the controller for
>> > these two USB devices stops working.  Maybe try unloading and reloading
>> > the ehci module?  I don't think I can help any more though.
>>
>> The issue also exist on 701 on 2.6.27-rc7 so the regression is in the
>> kernel not in the hardware
>>
> [snip]
>>
>> So it looks like an ehci_hcd issue when the camera is disabled
>
>
> And of course, having tried Ingo Molnar's linux-tip (whereas before I was using 2.6.27) I have now found a modern kernel that doesn't exhibit the problem...
>

I have just tried with latest git and it seems to work fine !

Re: Turning off camera also kills card reader on EeePC 900

[Pascal Terjan]

On Fri, Sep 26, 2008 at 12:56 PM, Pascal Terjan <pterjan@gmail.com> wrote:
> I have just tried with latest git and it seems to work fine !

just for information, rc7 + 5257d97a219e17abf8188f136e1189da3b3af33c is OK too

Re: Turning off camera also kills card reader on EeePC 900

[Sitsofe Wheeler]

Alan Jenkins wrote:
> Sitsofe Wheeler wrote:
>>
>> Alan Jenkins wrote:
>>
>>> The "HC died" message is interesting.  Sounds like the controller for
>>> these two USB devices stops working.  Maybe try unloading and reloading
>>> the ehci module?  I don't think I can help any more though.
>>
>> I compiled the kernel without module support so unless there's some 
>> sysfs trick that can be done...
>>
> Well, since you ask :-P.  Here's an equivalent incantation.  I hope it's 
> not too brittle.  Don't forget to unmount the SD card first.
> 
> cd /sys/module/ehci_hcd/drivers/pci:ehci_hcd
> echo -n 0000:00:1d.7 | sudo tee unbind; echo -n 0000:00:1d.7 | sudo tee 
> bind
> 
> The magic number is the PCI ID for the USB Host Controller, taken from 
> your error message.
> 
> If the manual "bind" works you should then see a symlink, "0000:00:1d.7" 
> in that directory.

Unfortunately when the SD card disappears so do the typical shell 
commands (as that's the device I'm booting off). I was left having to 
use source to look at the contents of things in /sys when the SD card died.

>>> - It might be necessary to compare with the pre-installed OS
>>>  - Is the pre-installed kernel any better (files might be under
>>> /proc/acpi/asus instead)?  I guess you might not have the time or
>>> resources to test that though.
>>
>> The Xandros 2.6.21.4-eeepc install has the following files in 
>> /proc/acpi/asus/
>> brn camera cardr cpufv disp hdps init type wlan
>>
>> I have no idea what cpufv, disp, hdps, init or type are. Doing echo 1 
>> > camera && echo 0 > camera under this setup does NOT disappear the SD 
>> card.
> Rats.  So there is some secret the mainline driver is missing :-(.

Looks it.

>> Additionally brn seems to really represent the current LCD brightness 
>> (whereas it does not on a stock kernel and seems to always be set to -19)
> It might have bitrotted on stock kernels?  The newer interface is under 
> /sys/class/backlight.

Ah I see - the stuff in there is correct. Does that mean that brn should 
quietly disappear now this alternative interface is present?

>> and the hotkeys (e.g. for brightness) seem to respond far more quickly 
>> than the stock kernel too.
> Heh heh.  I know all too much about that.  It's a problem with the ACPI 
> Embedded Controller driver, a hardware bug which triggered a regression 
> in 2.6.25.
> 
> I'm currently running... it claims to be 2.6.27-rc4 but it might be 
> 2.6.27-rc5 or something in between... which includes a fix.  I'm not 
> confident that they haven't broken it again since then.  The problem is 
> there are just so many different types of buggy EC's.  "Fixes" for some 
> buggy hardware break other buggy hardware.  Very nasty.

Sigh. I think I've seen those posts ( 
http://thread.gmane.org/gmane.linux.acpi.devel/32779/focus=33442 ? ) and 
hadn't fully comprehended what you were fighting against. Doesn't this 
just lead to DMI based quirks?

>>>  - The source code is... a 2Gb+ rar file someone would have to download
>>> and pick apart.
>>
>> Does anyone know if the archives on
>> http://support.asus.com/download/download_item_4.aspx?product=20&model=Eee%20PC%20900/Linux&SLanguage=en-us&os=5 
>> (release dates appear to be 5th September 2008) are actually any 
>> different?
>>
> Why do you say that?  Are the filesizes suspiciously identical?

I wish I could say - for some reason every option to download the source 
code in the dropdown on http://eeepc.asus.com/global/download.htm goes 
to a 404 page. I can't say I'm looking forward to downloading 2.6Gbytes 
on this network connection regardless.

--
Sitsofe

Re: Turning off camera also kills card reader on EeePC 900

[Sitsofe Wheeler]

Alan Jenkins wrote:
> Ok.  So the platform driver settings do match those in the BIOS.  My
> guess would be the platform driver is fine and the BIOS screws up.

I was afraid you were going to say that.

> The "HC died" message is interesting.  Sounds like the controller for
> these two USB devices stops working.  Maybe try unloading and reloading
> the ehci module?  I don't think I can help any more though.

I compiled the kernel without module support so unless there's some 
sysfs trick that can be done...

> - Are any BIOS upgrades available?  None of them mention this problem,
> but the descriptions often miss out details. [1][2]

For some reason I thought I had once seen an 804 BIOS but I only see 802 
on the EeePC 900 page (link below) and the even older 704 BIOS on 
ftp://ftp.asus.com/pub/ASUS/EeePC/EeePC900/ .

> - It might be necessary to compare with the pre-installed OS
>  - Is the pre-installed kernel any better (files might be under
> /proc/acpi/asus instead)?  I guess you might not have the time or
> resources to test that though.

The Xandros 2.6.21.4-eeepc install has the following files in 
/proc/acpi/asus/
brn camera cardr cpufv disp hdps init type wlan

I have no idea what cpufv, disp, hdps, init or type are. Doing echo 1 > 
camera && echo 0 > camera under this setup does NOT disappear the SD 
card. Additionally brn seems to really represent the current LCD 
brightness (whereas it does not on a stock kernel and seems to always be 
set to -19) and the hotkeys (e.g. for brightness) seem to respond far 
more quickly than the stock kernel too.

>  - The source code is... a 2Gb+ rar file someone would have to download
> and pick apart.

2.6Gbytes of multipart RAR. Joy.

 > [1] Asus downloads <http://eeepc.asus.com/global/download.htm>

This link seems to be for the 701 only.

Does anyone know if the archives on
http://support.asus.com/download/download_item_4.aspx?product=20&model=Eee%20PC%20900/Linux&SLanguage=en-us&os=5 
(release dates appear to be 5th September 2008) are actually any different?

(A brief aside. If you are a company doing seeking to do a source 
release of a Linux distribution, it might be a good idea to go for 
typical Unix formats. It is easier for folks if you package things as 
tar.bz2 or tar.gz files or even .zip rather than going for .rar . 
Additionally it is helpful if you split the just the kernel into an 
archive of its own).

--
Sitsofe

Re: Turning off camera also kills card reader on EeePC 900

[Alan Jenkins]

Sitsofe Wheeler wrote:
>
> Alan Jenkins wrote:
>> Ok.  So the platform driver settings do match those in the BIOS.  My
>> guess would be the platform driver is fine and the BIOS screws up.
>
> I was afraid you were going to say that.
>
>> The "HC died" message is interesting.  Sounds like the controller for
>> these two USB devices stops working.  Maybe try unloading and reloading
>> the ehci module?  I don't think I can help any more though.
>
> I compiled the kernel without module support so unless there's some 
> sysfs trick that can be done...
>
Well, since you ask :-P.  Here's an equivalent incantation.  I hope it's 
not too brittle.  Don't forget to unmount the SD card first.

cd /sys/module/ehci_hcd/drivers/pci:ehci_hcd
echo -n 0000:00:1d.7 | sudo tee unbind; echo -n 0000:00:1d.7 | sudo tee bind

The magic number is the PCI ID for the USB Host Controller, taken from 
your error message.

If the manual "bind" works you should then see a symlink, "0000:00:1d.7" 
in that directory.
>> - Are any BIOS upgrades available?  None of them mention this problem,
>> but the descriptions often miss out details. [1][2]
>
> For some reason I thought I had once seen an 804 BIOS but I only see 
> 802 on the EeePC 900 page (link below) and the even older 704 BIOS on 
> ftp://ftp.asus.com/pub/ASUS/EeePC/EeePC900/ .
>
>> - It might be necessary to compare with the pre-installed OS
>>  - Is the pre-installed kernel any better (files might be under
>> /proc/acpi/asus instead)?  I guess you might not have the time or
>> resources to test that though.
>
> The Xandros 2.6.21.4-eeepc install has the following files in 
> /proc/acpi/asus/
> brn camera cardr cpufv disp hdps init type wlan
>
> I have no idea what cpufv, disp, hdps, init or type are. Doing echo 1 
> > camera && echo 0 > camera under this setup does NOT disappear the SD 
> card.
Rats.  So there is some secret the mainline driver is missing :-(.
> Additionally brn seems to really represent the current LCD brightness 
> (whereas it does not on a stock kernel and seems to always be set to -19)
It might have bitrotted on stock kernels?  The newer interface is under 
/sys/class/backlight.
> and the hotkeys (e.g. for brightness) seem to respond far more quickly 
> than the stock kernel too.
Heh heh.  I know all too much about that.  It's a problem with the ACPI 
Embedded Controller driver, a hardware bug which triggered a regression 
in 2.6.25.

I'm currently running... it claims to be 2.6.27-rc4 but it might be 
2.6.27-rc5 or something in between... which includes a fix.  I'm not 
confident that they haven't broken it again since then.  The problem is 
there are just so many different types of buggy EC's.  "Fixes" for some 
buggy hardware break other buggy hardware.  Very nasty.
>>  - The source code is... a 2Gb+ rar file someone would have to download
>> and pick apart.
>
> 2.6Gbytes of multipart RAR. Joy.
>
> > [1] Asus downloads <http://eeepc.asus.com/global/download.htm>
>
> This link seems to be for the 701 only.
>
> Does anyone know if the archives on
> http://support.asus.com/download/download_item_4.aspx?product=20&model=Eee%20PC%20900/Linux&SLanguage=en-us&os=5 
> (release dates appear to be 5th September 2008) are actually any 
> different?
>
Why do you say that?  Are the filesizes suspiciously identical?

Alan

Re: Turning off camera also kills card reader on EeePC 900

[Alan Jenkins]

Sitsofe Wheeler wrote:

> When running Ubuntu from an SD card issuing
> echo 0 > /sys/devices/platform/eeepc/camera
> as root will cause the camera to be turned off AND the SD card to
> immediately disappear (which is rather fatal when you are using it). It's
> hard to know if this is intended behaviour by the BIOS (given that they
> are both USB devices) or a mistake in the platform driver...

It's a bug either way (a regression from the 701 hardware).  I think you
should be able to isolate it.

Firstly, I understand these kill-switches are supposed to be persistent
over reboots.  You should check that the SD card stays disabled when you
reboot.

Next, these settings are also exposed in the BIOS configuration screen,
right?  If it's the same as my 701 then the BIOS will have a separate
option for disabling the cardreader.  So you could see if the platform
driver "camera" switch is simply disabling and enabling the two switches
together.

Or if there's only a BIOS option for the camera, and not the SD card,
then you should test whether it disables the SD card.

Regards
Alan

Re: Turning off camera also kills card reader on EeePC 900

[Sitsofe Wheeler]

Alan Jenkins wrote:
> Firstly, I understand these kill-switches are supposed to be persistent
> over reboots.  You should check that the SD card stays disabled when you
> reboot.

The settings are persistent (so changing a camera value that is 0 to 1 
will show the camera as being enabled if you go to the BIOS). However 
the SD card will be present at reboot.

> Next, these settings are also exposed in the BIOS configuration screen,
> right?  If it's the same as my 701 then the BIOS will have a separate
> option for disabling the cardreader.  So you could see if the platform
> driver "camera" switch is simply disabling and enabling the two switches
> together.

The option for disabling the cardreader is indeed separate from the one 
to disable the camera. There is, however a switch for disabling USB in 
the BIOS too...

> Or if there's only a BIOS option for the camera, and not the SD card,
> then you should test whether it disables the SD card.

OK there are separate switches in the BIOS for disabling (among other 
things) the Camera, CardReader, and USB Ports.

Doing echo 0 > camera when camera is already 0 does nothing. The value 
in cardr remains 1.
Doing echo 0 > camera when camera is 1 seemingly results in the SD card 
disappearing too (ehci_hcd 0000:00:1d.7: HC died; cleaning up). cardr 
value remains 1. The CardReader and USB Ports options will be in the 
enabled state when looking in the BIOS after rebooting. The Camera 
option will be in the disabled state in the BIOS.
Doing echo 1 > camera after the SD card  has disappeared (but before 
rebooting) in the above step will result in the SD card seemingly coming 
back at a different address and the kernel reporting 'irq 23: nobody 
cared (try booting with the "irqpoll" option)' and a usb_hcd_irq backtrace.
Doing echo 0 > cardr when cardr is 1 results in the SD card disappearing 
and an ext3 error being printed on the console. The CardReader option 
will be in the disabled state in the BIOS after rebooting.
Doing echo 0 > camera after the SD card  has disappeared (but before 
rebooting) in the above step will result in 'ehci_hcd 0000:00:1d.7: HC 
died; cleaning up' being printed.

-- 
Sitsofe | http://sucs.org/~sits/

Re: Turning off camera also kills card reader on EeePC 900

[Alan Jenkins]

Sitsofe Wheeler wrote:
> Alan Jenkins wrote:
>> Firstly, I understand these kill-switches are supposed to be persistent
>> over reboots.  You should check that the SD card stays disabled when you
>> reboot.
>
> The settings are persistent (so changing a camera value that is 0 to 1
> will show the camera as being enabled if you go to the BIOS). However
> the SD card will be present at reboot.
>
>> Next, these settings are also exposed in the BIOS configuration screen,
>> right?  If it's the same as my 701 then the BIOS will have a separate
>> option for disabling the cardreader.  So you could see if the platform
>> driver "camera" switch is simply disabling and enabling the two switches
>> together.
>
> The option for disabling the cardreader is indeed separate from the
> one to disable the camera. There is, however a switch for disabling
> USB in the BIOS too...
>
>> Or if there's only a BIOS option for the camera, and not the SD card,
>> then you should test whether it disables the SD card.
>
> OK there are separate switches in the BIOS for disabling (among other
> things) the Camera, CardReader, and USB Ports.
>
> Doing echo 0 > camera when camera is already 0 does nothing. The value
> in cardr remains 1.
> Doing echo 0 > camera when camera is 1 seemingly results in the SD
> card disappearing too (ehci_hcd 0000:00:1d.7: HC died; cleaning up).
> cardr value remains 1. The CardReader and USB Ports options will be in
> the enabled state when looking in the BIOS after rebooting. The Camera
> option will be in the disabled state in the BIOS.
> Doing echo 1 > camera after the SD card  has disappeared (but before
> rebooting) in the above step will result in the SD card seemingly
> coming back at a different address and the kernel reporting 'irq 23:
> nobody cared (try booting with the "irqpoll" option)' and a
> usb_hcd_irq backtrace.
> Doing echo 0 > cardr when cardr is 1 results in the SD card
> disappearing and an ext3 error being printed on the console. The
> CardReader option will be in the disabled state in the BIOS after
> rebooting.
> Doing echo 0 > camera after the SD card  has disappeared (but before
> rebooting) in the above step will result in 'ehci_hcd 0000:00:1d.7: HC
> died; cleaning up' being printed.
>

Ok.  So the platform driver settings do match those in the BIOS.  My
guess would be the platform driver is fine and the BIOS screws up.

The "HC died" message is interesting.  Sounds like the controller for
these two USB devices stops working.  Maybe try unloading and reloading
the ehci module?  I don't think I can help any more though.

- I CC: the maintainer, maybe Corentin has other reports or ideas

- Are any BIOS upgrades available?  None of them mention this problem,
but the descriptions often miss out details. [1][2]

- It might be necessary to compare with the pre-installed OS
 - Is the pre-installed kernel any better (files might be under
/proc/acpi/asus instead)?  I guess you might not have the time or
resources to test that though.
 - The source code is... a 2Gb+ rar file someone would have to download
and pick apart.

Regards
Alan

[1] Asus downloads <http://eeepc.asus.com/global/download.htm>
[2] BIOS update howto <http://wiki.eeeuser.com/howto:updatebios>

Re: Turning off camera also kills card reader on EeePC 900

[Pascal Terjan]

On Mon, Sep 15, 2008 at 3:37 PM, Alan Jenkins
<alan-jenkins@tuffmail.co.uk> wrote:
> Sitsofe Wheeler wrote:
> The "HC died" message is interesting.  Sounds like the controller for
> these two USB devices stops working.  Maybe try unloading and reloading
> the ehci module?  I don't think I can help any more though.

The issue also exist on 701 on 2.6.27-rc7 so the regression is in the
kernel not in the hardware

Disabling camera :

ehci_hcd 0000:00:1d.7: HC died; cleaning up
hub 1-0:1.0: hub_port_status failed (err = -19)
hub 1-0:1.0: connect-debounce failed, port 8 disabled
usb 1-8: USB disconnect, address 3
usb 1-5: USB disconnect, address 2

Enabling it again :

irq 23: nobody cared (try booting with the "irqpoll" option)
Pid: 0, comm: swapper Not tainted 2.6.27-desktop-0.rc6.3.2mnb #1
 [<c0380022>] ? printk+0x18/0x1e
 [<c016bdc7>] __report_bad_irq+0x27/0x90
 [<c016c08c>] note_interrupt+0x25c/0x290
 [<c016aef9>] ? handle_IRQ_event+0x39/0x70
 [<c016c63b>] handle_fasteoi_irq+0xab/0xd0
 [<c0106eb0>] do_IRQ+0x40/0x80
 [<c01048bf>] common_interrupt+0x23/0x28
 [<c0150eba>] ? tick_nohz_stop_sched_tick+0xca/0x350
 [<c01027aa>] cpu_idle+0x2a/0x130
 [<c0372b3e>] rest_init+0x4e/0x60
 =======================
handlers:
[<e005b800>] (usb_hcd_irq+0x0/0x90 [usbcore])
[<e005b800>] (usb_hcd_irq+0x0/0x90 [usbcore])
Disabling IRQ #23

Reloading ehci_hcd

ehci_hcd 0000:00:1d.7: remove, state 0
usb usb1: USB disconnect, address 1
ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
ehci_hcd 0000:00:1d.7: PCI INT A disabled
usb 4-1: new full speed USB device using uhci_hcd and address 2
usb 4-1: configuration #1 chosen from 1 choice
scsi3 : SCSI emulation for USB Mass Storage devices
usb 4-1: New USB device found, idVendor=0951, idProduct=1606
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
usb 4-1: Product: UB6225
usb 4-1: Manufacturer: ENE
usb 4-1: SerialNumber: 146030377350
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usb 5-2: new full speed USB device using uhci_hcd and address 2
usb 5-2: configuration #1 chosen from 1 choice
uvcvideo: Found UVC 1.00 device <unnamed> (eb1a:2761)
uvcvideo: Using UVC_MAX_ISO_PACKETS=40
input: UVC Camera (eb1a:2761) as /class/input/input10
usb 5-2: New USB device found, idVendor=eb1a, idProduct=2761
usb 5-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
usbcore: registered new interface driver ub
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf7eb7c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
uvcvideo: Non-zero status (-84) in status completion handler.
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.27-desktop-0.rc6.3.2mnb ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
usb 4-1: USB disconnect, address 2
usb 5-2: USB disconnect, address 2
usb 1-5: new high speed USB device using ehci_hcd and address 2
usb 1-5: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb 1-5: New USB device found, idVendor=0951, idProduct=1606
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=4
usb 1-5: Product: UB6225
usb 1-5: Manufacturer: ENE
usb 1-5: SerialNumber: 146030377350
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
usb 1-8: new high speed USB device using ehci_hcd and address 3
usb 1-8: configuration #1 chosen from 1 choice
uvcvideo: Found UVC 1.00 device <unnamed> (eb1a:2761)
uvcvideo: Using UVC_MAX_ISO_PACKETS=40
input: UVC Camera (eb1a:2761) as /class/input/input11
usb 1-8: New USB device found, idVendor=eb1a, idProduct=2761
usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0
scsi 4:0:0:0: Direct-Access     USB2.0   CardReader SD0   0100 PQ: 0 ANSI: 0
sd 4:0:0:0: [sdb] Attached SCSI removable disk
sd 4:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete

Disabling camera:

eeepc: switch_camera from 1
ehci_hcd 0000:00:1d.7: HC died; cleaning up
hub 1-0:1.0: hub_port_status failed (err = -19)
hub 1-0:1.0: connect-debounce failed, port 8 disabled
usb 1-8: USB disconnect, address 3
usb 1-5: USB disconnect, address 2

Reloading ehci_hcd:

ehci_hcd 0000:00:1d.7: remove, state 0
usb usb1: USB disconnect, address 1
ehci_hcd 0000:00:1d.7: USB bus 1 deregistered
ehci_hcd 0000:00:1d.7: PCI INT A disabled
usb 4-1: new full speed USB device using uhci_hcd and address 3
usb 4-1: configuration #1 chosen from 1 choice
scsi5 : SCSI emulation for USB Mass Storage devices
usb 4-1: New USB device found, idVendor=0951, idProduct=1606
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=4
usb 4-1: Product: UB6225
usb 4-1: Manufacturer: ENE
usb 4-1: SerialNumber: 146030377350
usb-storage: device found at 3
usb-storage: waiting for device to settle before scanning
ehci_hcd 0000:00:1d.7: PCI INT A -> GSI 23 (level, low) -> IRQ 23
ehci_hcd 0000:00:1d.7: setting latency timer to 64
ehci_hcd 0000:00:1d.7: EHCI Host Controller
ehci_hcd 0000:00:1d.7: new USB bus registered, assigned bus number 1
ehci_hcd 0000:00:1d.7: debug port 1
ehci_hcd 0000:00:1d.7: cache line size of 32 is not supported
ehci_hcd 0000:00:1d.7: irq 23, io mem 0xf7eb7c00
ehci_hcd 0000:00:1d.7: USB 2.0 started, EHCI 1.00, driver 10 Dec 2004
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 8 ports detected
usb 4-1: USB disconnect, address 3
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 2.6.27-desktop-0.rc6.3.2mnb ehci_hcd
usb usb1: SerialNumber: 0000:00:1d.7
usb 1-5: new high speed USB device using ehci_hcd and address 2
usb 1-5: configuration #1 chosen from 1 choice
scsi6 : SCSI emulation for USB Mass Storage devices
usb 1-5: New USB device found, idVendor=0951, idProduct=1606
usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=4
usb 1-5: Product: UB6225
usb 1-5: Manufacturer: ENE
usb 1-5: SerialNumber: 146030377350
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
scsi 6:0:0:0: Direct-Access     USB2.0   CardReader SD0   0100 PQ: 0 ANSI: 0
sd 6:0:0:0: [sdb] Attached SCSI removable disk
sd 6:0:0:0: Attached scsi generic sg1 type 0
usb-storage: device scan complete

Enabling camera:

eeepc: switch_camera from 0
usb 1-8: new high speed USB device using ehci_hcd and address 3
usb 1-8: configuration #1 chosen from 1 choice
uvcvideo: Found UVC 1.00 device <unnamed> (eb1a:2761)
uvcvideo: Using UVC_MAX_ISO_PACKETS=40
input: UVC Camera (eb1a:2761) as /class/input/input12
usb 1-8: New USB device found, idVendor=eb1a, idProduct=2761
usb 1-8: New USB device strings: Mfr=0, Product=0, SerialNumber=0

So it looks like an ehci_hcd issue when the camera is disabled

Re: Turning off camera also kills card reader on EeePC 900

[Alan Jenkins]

Pascal Terjan wrote:
> On Mon, Sep 15, 2008 at 3:37 PM, Alan Jenkins
> <alan-jenkins@tuffmail.co.uk> wrote:
>   
>> Sitsofe Wheeler wrote:
>> The "HC died" message is interesting.  Sounds like the controller for
>> these two USB devices stops working.  Maybe try unloading and reloading
>> the ehci module?  I don't think I can help any more though.
>>     
>
> The issue also exist on 701 on 2.6.27-rc7 so the regression is in the
> kernel not in the hardware
>   
On the bright side, that means more people should have the hardware to 
test it on (including me :-).

I've certainly used the camera enable/disable at some point.  But I 
could have missed the error message, and frankly I don't use the camera 
or cardreader very often.  I'll have a bash at it tomorrow.

Sitsofe says it reproduced on kernel.org 2.6.21 (presumably with an 
out-of-tree eeepc module).  So I guess this isn't a simple git-bisect 
job - more thinking required...

Thanks
Alan

Re: Turning off camera also kills card reader on EeePC 900

[Karl Kiniger]

On Thu 080925, Pascal Terjan wrote:
> On Mon, Sep 15, 2008 at 3:37 PM, Alan Jenkins
> <alan-jenkins@tuffmail.co.uk> wrote:
> > Sitsofe Wheeler wrote:
> > The "HC died" message is interesting.  Sounds like the controller for
> > these two USB devices stops working.  Maybe try unloading and reloading
> > the ehci module?  I don't think I can help any more though.
> 
> The issue also exist on 701 on 2.6.27-rc7 so the regression is in the
> kernel not in the hardware
> 
[ deleted ]

something like this happened to me on the latest Fedora 9 kernel
when I turned off my USB hard drive. The second USB drive got killed
by this until ehci reload. 
The F9 kernel is reported tainted (dont know the reason), perhaps can
somebody enlighten me:

Sep 23 19:06:12 kipc2 kernel: Modules linked in: vfat fat reiserfs
usb_storage nls_utf8 cifs nfs lockd nfs_acl tun ipt_MASQUERADE
iptable_nat nf_nat bridge bnep rfcomm l2cap bluetooth ib_iser rdma_cm
ib_cm iw_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi
scsi_transport_iscsi fuse sunrpc ipv6 nf_conntrack_netbios_ns
nf_conntrack_ftp ipt_REJECT xt_tcpudp nf_conntrack_ipv4 xt_state
nf_conntrack iptable_filter ip_tables x_tables loop dm_multipath
snd_usb_audio snd_intel8x0 snd_ac97_codec snd_seq_dummy snd_bt87x
ac97_bus snd_seq_oss snd_seq_midi_event snd_seq snd_pcm_oss
snd_mixer_oss snd_pcm sr_mod cdrom tvaudio snd_usb_lib snd_rawmidi
snd_seq_device snd_hwdep bttv videodev v4l1_compat snd_timer i915
firewire_ohci firewire_core snd ir_common compat_ioctl32 v4l2_common
pata_sil680 ppdev crc_itu_t i2c_i801 tg3 parport_pc videobuf_dma_sg
videobuf_core btcx_risc tveeprom drm i2c_algo_bit i2c_core parport
soundcore iTCO_wdt iTCO_vendor_support pcspkr snd_page_alloc sg floppy
dm_snapshot dm_zero dm_mirror dm_log dm_


Sep 23 19:05:31 kipc2 kernel: usb 1-5: USB disconnect, address 22
Sep 23 19:05:31 kipc2 kernel: usb 1-3: reset high speed USB device using ehci_hcd and address 21
Sep 23 19:05:31 kipc2 kernel: usb_storage: can't resubmit intr, 0000:00:1d.7-3/input0, retval -19
Sep 23 19:05:31 kipc2 kernel: ehci_hcd 0000:00:1d.7: HC died; cleaning up
Sep 23 19:05:31 kipc2 kernel: usb 1-3: USB disconnect, address 0
Sep 23 19:05:32 kipc2 kernel: usb 1-3: device not accepting address 21, error -22
Sep 23 19:05:32 kipc2 kernel: hub 1-0:1.0: cannot reset port 3 (err = -19)
Sep 23 19:05:32 kipc2 kernel: sd 24:0:0:0: [sde] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK,SUGGEST_OK
Sep 23 19:05:32 kipc2 kernel: end_request: I/O error, dev sde, sector 452332487

.... lots of reiserfs messages...

Sep 23 19:05:42 kipc2 kernel: irq 23: nobody cared (try booting with the "irqpoll" option)
Sep 23 19:05:42 kipc2 kernel: Pid: 29944, comm: npviewer.bin Tainted: G D   2.6.26.3-29.fc9.i686 #1
Sep 23 19:05:42 kipc2 kernel: [<c045ed60>] __report_bad_irq+0x2e/0x6f
Sep 23 19:05:42 kipc2 kernel: [<c045ef63>] note_interrupt+0x1c2/0x217
Sep 23 19:05:42 kipc2 kernel: [<c045e5b8>] ? handle_IRQ_event+0x2a/0x5a
Sep 23 19:05:42 kipc2 kernel: [<c045f512>] handle_fasteoi_irq+0x8f/0xaf
Sep 23 19:05:42 kipc2 kernel: [<c045f483>] ? handle_fasteoi_irq+0x0/0xaf
Sep 23 19:05:42 kipc2 kernel: [<c0406f08>] do_IRQ+0x98/0xc4
Sep 23 19:05:42 kipc2 kernel: [<c04055eb>] common_interrupt+0x23/0x28
Sep 23 19:05:42 kipc2 kernel: [<c0630000>] ?
__down_interruptible+0x4/0x8d
Sep 23 19:05:42 kipc2 kernel: =======================
Sep 23 19:05:42 kipc2 kernel: handlers:
Sep 23 19:05:42 kipc2 kernel: [<c057afbe>] (usb_hcd_irq+0x0/0x7d)
Sep 23 19:05:42 kipc2 kernel: [<c057afbe>] (usb_hcd_irq+0x0/0x7d)
Sep 23 19:05:42 kipc2 kernel: Disabling IRQ #23

Karl

-- 
D.I. Karl Kiniger     mailto:karl.kiniger@med.ge.com
GE Medical Systems Kretztechnik GmbH & Co OHG
Tiefenbach 15         Tel: (++43) 7682-3800-710  Voip(GE): 1662 710
A-4871 Zipf Austria   Fax: (++43) 7682-3800-47 C: +43 6991 3800 710

Turning off camera also kills card reader on EeePC 900

[Sitsofe Wheeler]

When running Ubuntu from an SD card issuing
echo 0 > /sys/devices/platform/eeepc/camera
as root will cause the camera to be turned off AND the SD card to 
immediately disappear (which is rather fatal when you are using it). It's 
hard to know if this is intended behaviour by the BIOS (given that they 
are both USB devices) or a mistake in the platform driver... 

-- 
Sitsofe | http://sucs.org/~sits/