Send buglog mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.openmoko.org/mailman/listinfo/buglog
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of buglog digest..."
Today's Topics:
1. Openmoko Bug #2278: kernel: g_file_storage fails with usb
1-1: failed to restore interface 0 altsetting 0 (error=-110)
(Openmoko Public Trac)
2. Re: Openmoko Bug #2278: kernel: g_file_storage fails with usb
1-1: failed to restore interface 0 altsetting 0 (error=-110)
(Openmoko Public Trac)
3. Re: Openmoko Bug #2278: kernel: g_file_storage fails with usb
1-1: failed to restore interface 0 altsetting 0 (error=-110)
(Openmoko Public Trac)
4. Re: Openmoko Bug #2277: Wireless does not work with the
2.6.29 kernel (Openmoko Public Trac)
5. Openmoko Bug #2279: toggling backlight very fast blocks reads
of /proc/apm (Openmoko Public Trac)
6. Re: Openmoko Bug #2278: kernel: g_file_storage fails with usb
1-1: failed to restore interface 0 altsetting 0 (error=-110)
(Openmoko Public Trac)
--- Begin Message ---
#2278: kernel: g_file_storage fails with usb 1-1: failed to restore interface 0
altsetting 0 (error=-110)
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: kernel usb gadget
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Steps to reproduce:
1) boot freerunner without loading any usb gadgets (just to prove they
don't cause this problem), connect it to a PC and then type the following
on freerunner:
2) dd if=/dev/urandom of=/tmp/disk bs=4M count=1
3) sudo modprobe g_file_storage file=/tmp/disk
Expected results:
3) freerunner shows up as a USB mass storage device to the PC in /dev
Actual results:
3) No new files are created to /dev on PC side.
More info:
1) The PC starts to log the following repeatedly:
{{{
304.796079] usb 1-1: new full speed USB device using uhci_hcd and address
5
304.988733] usb 1-1: configuration #1 chosen from 1 choice
310.001061] usb 1-1: New USB device found, idVendor=0525, idProduct=a4a5
310.001093] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
310.001108] usb 1-1: Product: File-backed Storage Gadget
310.001120] usb 1-1: Manufacturer: Linux 2.6.29-GTA02_lindi-andy-tracking-
mokodev with s3c2410_udc
310.001134] usb 1-1: SerialNumber: 3230204E6F76
310.342798] Initializing USB Mass Storage driver...
310.343113] scsi0 : SCSI emulation for USB Mass Storage devices
310.343516] usbcore: registered new interface driver usb-storage
310.343535] USB Mass Storage support registered.
310.343568] usb-storage: device found at 5
310.343578] usb-storage: waiting for device to settle before scanning
315.341912] usb-storage: device scan complete
315.345889] scsi 0:0:0:0: Direct-Access Linux File-Stor Gadget 0312
PQ: 0 ANSI: 2
315.624107] Driver 'sd' needs updating - please use bus_type methods
315.635764] sd 0:0:0:0: [sda] 8192 512-byte hardware sectors (4 MB)
315.748080] usb 1-1: reset full speed USB device using uhci_hcd and
address 5
320.901788] usb 1-1: failed to restore interface 0 altsetting 0
(error=-110)
320.902084] sd 0:0:0:0: [sda] Write Protect is off
320.902100] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
320.902113] sd 0:0:0:0: [sda] Assuming drive cache: write through
320.903174] sd 0:0:0:0: [sda] READ CAPACITY failed
320.903187] sd 0:0:0:0: [sda] Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK,SUGGEST_OK
320.903207] sd 0:0:0:0: [sda] Sense not available.
320.903430] sd 0:0:0:0: [sda] Write Protect is off
320.903445] sd 0:0:0:0: [sda] Mode Sense: 00 00 00 00
320.903457] sd 0:0:0:0: [sda] Assuming drive cache: write through
320.903719] sd 0:0:0:0: [sda] Attached SCSI disk
320.905060] usb 1-1: USB disconnect, address 5
}}}
2) freerunner logs
{{{
[21474661.380000] g_file_storage gadget: File-backed Storage Gadget,
version: 20 November 2008
[21474661.400000] g_file_storage gadget: Number of LUNs=1
[21474661.405000] g_file_storage gadget-lun0: ro=0, file: /tmp/disk
[21474661.410000] gta02_udc_command S3C2410_UDC_P_ENABLE
[21474661.865000] g_file_storage gadget: full speed config #1
[21474672.695000] g_file_storage gadget: full speed config #1
[21474677.925000] g_file_storage gadget: full speed config #1
[21474688.140000] g_file_storage gadget: full speed config #1
[21474693.400000] g_file_storage gadget: full speed config #1
[21474703.610000] g_file_storage gadget: full speed config #1
[21474708.840000] g_file_storage gadget: full speed config #1
[21474719.065000] g_file_storage gadget: full speed config #1
[21474724.305000] g_file_storage gadget: full speed config #1
...
}}}
3) freerunner runs andy-tracking 9ecc089861ab238e (2.6.29 from Apr 28)
4) I tested this with two PCs and get the same results.
4.1) 400 MHz fujitsu-siemens laptop with linux 2.6.27.6
4.1) 200 MHz compaq deskpro desktop with linux 2.6.26-2-486
5) I am not using extra USB hubs or "extension cables". The cable I use
works perfectly with g_ether so I don't think this is a hardware issue.
Please test this and let me know if you can reproduce it.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2278>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2278: kernel: g_file_storage fails with usb 1-1: failed to restore interface 0
altsetting 0 (error=-110)
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: kernel usb gadget
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by lindi):
I added
#define DEBUG
#define VERBOSE_DEBUG
#define DUMP_MSGS
to file_storage.c and now the device seems to magically work so I guess
there's some odd timing issue. Laptop prints
{{{
5135.104081] usb 1-1: new full speed USB device using uhci_hcd and address
36
5138.422262] usb 1-1: configuration #1 chosen from 1 choice
5143.732641] scsi33 : SCSI emulation for USB Mass Storage devices
5143.733119] usb-storage: device found at 36
5143.733130] usb-storage: waiting for device to settle before scanning
5144.039013] usb 1-1: New USB device found, idVendor=0525, idProduct=a4a5
5144.039045] usb 1-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=3
5144.039059] usb 1-1: Product: File-backed3 Storage Gadget
5144.039072] usb 1-1: Manufacturer: Linux 2.6.29-GTA02_lindi-andy-
tracking-mokodev with s3c2410_udc
5144.039086] usb 1-1: SerialNumber: 3230204E6F76
5148.863424] usb-storage: device scan complete
5149.631309] scsi 33:0:0:0: Direct-Access Linux File-Stor Gadget
0312 PQ: 0 ANSI: 2
5152.139797] sd 33:0:0:0: [sda] 8192 512-byte hardware sectors (4 MB)
5152.858697] sd 33:0:0:0: [sda] Write Protect is off
5152.858728] sd 33:0:0:0: [sda] Mode Sense: 0f 00 00 00
5152.858741] sd 33:0:0:0: [sda] Assuming drive cache: write through
5153.997484] sd 33:0:0:0: [sda] 8192 512-byte hardware sectors (4 MB)
5154.715390] sd 33:0:0:0: [sda] Write Protect is off
5154.715421] sd 33:0:0:0: [sda] Mode Sense: 0f 00 00 00
5154.715434] sd 33:0:0:0: [sda] Assuming drive cache: write through
5154.715465] sda: unknown partition table
5156.613915] sd 33:0:0:0: [sda] Attached SCSI disk
}}}
and I can read data from the device too. The debug output from freerunner
is attached since its quite long.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2278#comment:1>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2278: kernel: g_file_storage fails with usb 1-1: failed to restore interface 0
altsetting 0 (error=-110)
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: kernel usb gadget
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by lindi):
If I run the debug version but
sudo sh -c 'echo 0 > /proc/sysrq-trigger'
then I hit the bug again so this bug is clearly sensitive to timing.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2278#comment:2>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2277: Wireless does not work with the 2.6.29 kernel
---------------------+------------------------------------------------------
Reporter: arhuaco | Owner: openmoko-devel
Type: defect | Status: new
Priority: normal | Milestone: stable-kernel-2009.1
Component: unknown | Version:
Severity: normal | Keywords:
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: sometimes
---------------------+------------------------------------------------------
Changes (by arhuaco):
* reproducible: => sometimes
Comment:
I tested with recent SHR testing and latest andy-tracking
(4c9a8d5badc466a68d71754d47bbb792a8dc44da).
I killed wpa_supplicant and avahi then turned on WIFI using the GUI.
I'm sure I was not using usb0 also.
First, with open network.
{{{
r...@om-gta02 ~ $ iwlist eth0 scan
eth0 Scan completed :
Cell 01 - Address: 00:22:B0:47:56:F5
ESSID:"LINUX"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=56/94 Signal level=-39 dBm Noise level=-95
dBm
Encryption key:off
Extra:bcn_int=100
Extra:ath_ie=dd0900037f010100600000
}}}
iwconfig eth0 essid LINUX
I set up an IP manually, gateway, etc and it worked.
{{{
r...@om-gta02 ~ $ iwlist eth0 scan
eth0 Scan completed :
Cell 01 - Address: 00:22:B0:47:56:F5
ESSID:"LINUX"
Mode:Master
Frequency:2.437 GHz (Channel 6)
Quality=56/94 Signal level=-39 dBm Noise level=-95
dBm
Encryption key:on
Extra:bcn_int=100
Extra:ath_ie=dd0900037f010100600000
}}}
I also used WEP. The key is not my real key.
iwconfig eth0 key 00005D0005 essid LINUX
{{{
iwconfig eth0
eth0 AR6000 802.11g ESSID:"LINUX"
Mode:Managed Frequency:2.437 GHz Access Point:
00:22:B0:47:56:F5
Bit Rate=54 Mb/s Tx-Power=15 dBm Sensitivity=0/3
Retry:on
Encryption key:0000-5D00-05 Security mode:open
Power Management:off
Link Quality:216/94 Signal level:-135 dBm Noise level:-96 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:6
}}}
udhcpc worked.
{{{
$ udhcpc
udhcpc (v1.13.2) started
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1
Sending discover...
Sending select for 192.168.0.101...
Lease of 192.168.0.101 obtained, lease time 604800
run-parts: /etc/udhcpc.d/00avahi-autoipd exited with code 1
adding dns 192.168.0.1
r...@om-gta02 ~ $ ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:12:CF:8F:01:15
inet addr:192.168.0.101 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:96 errors:0 dropped:0 overruns:0 frame:0
TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:45197 (44.1 KiB) TX bytes:4918 (4.8 KiB)
}}}
One thing to point out is that it did not work for me when I was far.
It worked when I was about 2 meters form the AP with better S/N ratio (I
didn't test with intermediate points and I don't think it is relevant).
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2277#comment:6>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2279: toggling backlight very fast blocks reads of /proc/apm
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version: unspecified
Severity: minor | Keywords: kernel backlight DoS
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Steps to reproduce:
1) Start "while cat /proc/apm; do sleep 1; done" in one terminal
2) Start
while true; do
echo 255 > /sys/class/backlight/gta02-bl/brightness
echo 15 > /sys/class/backlight/gta02-bl/brightness
done
in another terminal
Expected results:
2) backlight brightness changes very fast but cat is still sometimes
scheduled and can read from /proc/apm
Actual results:
2) backlight brightness changes very fast but the read() to /proc/apm
never returns.
More info:
1) I was just trying to make freerunner work as a strobe light when I
noticed that I could not stop the program. This probably happened because
Xorg was stuck reading from some file and would never succeed.
2) I am using andy-tracking 9ecc089861ab238e
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2279>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
--- Begin Message ---
#2278: kernel: g_file_storage fails with usb 1-1: failed to restore interface 0
altsetting 0 (error=-110)
-----------------------------+----------------------------------------------
Reporter: lindi | Owner: openmoko-kernel
Type: defect | Status: new
Priority: normal | Milestone:
Component: System Software | Version:
Severity: normal | Keywords: kernel usb gadget
Haspatch: 0 | Blockedby:
Estimated: | Patchreview:
Blocking: | Reproducible: always
-----------------------------+----------------------------------------------
Comment(by arhuaco):
lindi, it worked for me.
{{{
[ 145.355000] g_file_storage gadget: File-backed Storage Gadget, version:
20 November 2008
[ 145.365000] g_file_storage gadget: Number of LUNs=1
[ 145.365000] g_file_storage gadget-lun0: ro=0, file:
/var/volatile/tmp/disk
[ 145.375000] gta02_udc_command S3C2410_UDC_P_ENABLE
[ 146.160000] g_file_storage gadget: full speed config #1
[ 151.515000] g_file_storage gadget: full speed config #1
}}}
And I could format and mount the raw device in the host.
--
Ticket URL: <https://docs.openmoko.org/trac/ticket/2278#comment:3>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac
--- End Message ---
_______________________________________________
buglog mailing list
[email protected]
http://lists.openmoko.org/mailman/listinfo/buglog