Viestialustana vianhallintajärjestelmät

Just a note about similarity between this and bug #939301

5. huhtikuuta 2013 klo 16.13
Sijainti: Vianhallintajärjestelmät: Launchpad

Just making a note about similarity between this and bug #939301; latter perhaps a duplicate?

Vastaa viestiin sen kontekstissa (Launchpad)

umount.crypt should support lazy unmount (-l option)

4. huhtikuuta 2013 klo 22.27
Sijainti: Vianhallintajärjestelmät: Launchpad

umount.crypt doesn’t support lazy unmounting:

jani@saegusa:~$ sudo mount .Backup
Password:
jani@saegusa:~$ grep Backup /etc/mtab
/dev/sdc1 /home/jani/.Backup crypt rw,nosuid,nodev,noauto 0 0
jani@saegusa:~$ sudo umount -l .Backup
Unknown option: -l
Usage: umount.crypt [-fnrv] [-?|–help] [–usage]
Unknown option: -l
Usage: umount.crypt [-fnrv] [-?|–help] [–usage]

The usefulness of -l is documented in umount(8).

Strangely, the Debian BTS claims this feature has already been implemented ages ago [1].

*[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=370526

Vastaa viestiin sen kontekstissa (Launchpad)

As a workaround for openyahtzee in 12.04, here’s a command

14. maaliskuuta 2013 klo 23.13
Sijainti: Vianhallintajärjestelmät: Launchpad

As a workaround for 12.04, here’s a command that replaces the settings file with an unwritable empty one that seems to prevent the issue from occurring:

$ rm -f ~/.openyahtzee && touch ~/.openyahtzee && chmod -w ~/.openyahtzee

This obviously prevents you from saving any settings, but then again you can’t utilize saved settings with the buggy version anyway.

To revert the workaround, remove the unwritable dummy file with:

$ rm -f ~/.openyahtzee

Vastaa viestiin sen kontekstissa (Launchpad)

”Random” playback order is not truly random

24. tammikuuta 2013 klo 23.52
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: VLC

Steps to reproduce:

1. Load a playlist of N files in VLC
2. Set playback to Random
3. Play or jump (with ”Next” button) the playlist forward for N files and observe the playing order
4. GOTO step 3

What happens:
The order in which the files are played in step 3 always repeats itself.

What I expect to happen:
For the files to be played back in a truly random order, without any perpetually repeating pattern.

Further info:
The playing order seems to get shuffled only at the start, so the playlist isn’t played in order, but the once-shuffled order is repeated over and over. To reshuffle the playlist, VLC has to be restarted, but still then it just plays the newly-shuffled playlist over and over.

To be fair, in practice instead of true randomness I suspect most people prefer something from the way the ”Random” now works: that each file on the playlist is played once and once only in every N plays. AFAICT it is not mutually exclusive with reshuffling the playlist between those N plays; just make sure that the two transitional files (last file of shuffled-playlist-1 vs. first file of shuffled-playlist-2) aren’t the same.

I for one though would still prefer even true random over what it currently is.

Of the half a dozen or so randomness-related bugs in VLC’s tracker I was able to find, Ticket #5730 (”New Feature Request: Shuffle & Random for Playlists”) [1] came closest to what I’m reporting here. In fact, it’s a superset of this one and I’d prefer to have it fixed over just mine.

*[1] http://trac.videolan.org/vlc/ticket/5730#trac-ticket-title

Vastaa viestiin sen kontekstissa (Launchpad)

No problems with 3.5 either, marking as invalid.

21. tammikuuta 2013 klo 11.43
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Linux

No problems with 3.5 either, marking as invalid.

Vastaa viestiin sen kontekstissa (Launchpad)

Sorry, I had forgot about this one after it vanished

16. tammikuuta 2013 klo 9.05
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Linux

Sorry, I had forgot about this one after it vanished and was only reminded by a private email from someone suffering something similar.

I went through my collection of panic photos and (as my recollection also was) there seem to have been none of this ’warn_slowpath_common’ kind since I last commented.

Except for one just a week ago, on completely new hardware: this one with 3.8.0 rc2 when I was testing it wrt Bug #1096802, which turned out to be caused by bad card reader firmware. It was tied to usb-storage as most if not all of the panics caused by the firmware problem, so it was most likely another symptom of that, but I’m posting that one here too just in case it still contains a hint of the conditions under which ’warn_slowpath_common’ can occur.

Meanwhile, I’m marking this as fixed as per Joseph’s request above. For the record, as far as I’m concerned, a installing 3.3 or newer series kernel was a definite fix for this issue.

Vastaa viestiin sen kontekstissa (Launchpad)

I’m happy to report that this seems to have been a firmware issue

14. tammikuuta 2013 klo 19.04
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Akasa, Linux

I’m happy to report that this seems to have been a firmware issue: with a temporary install of MS Windows, which the card reader manufacturer’s firmware upgrading software required [1], I managed to upgrade the card reader’s bought-with firmware version 551 to manufacturer’s current latest version 563 (released just last month). After this there were no more ”disabled ep” messages in any boot, the reader works just fine and there have been no kernel panics of any kind.

This was with the mainline 3.8 kernel so I’m not marking this bug invalid just yet. I’ve now switched back to the Quantal kernel I initially reported this with and will report here next week on how it goes.

*[1] http://www.akasa.com.tw/update.php?tpl=product/cpu.product.tpl&no=181&type=Card%20Reader/Hub&type_sub=Card%20Reader&model=AK-ICR-17

Vastaa viestiin sen kontekstissa (Launchpad)

I’m attaching output of `sudo lsusb -v` here

9. tammikuuta 2013 klo 12.12
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Akasa, Linux

The lsusb listing attached by apport above seems to not list the card reader at all. This did happen on some sessions, IIRC there were no panics or ”disabled ep” messages then either but naturally, the reader also wouldn’t read any cards, it was as if disconnected.

I’m attaching output of `sudo lsusb -v` here, with the card reader (004:002) detected and showing.

Vastaa viestiin sen kontekstissa (Launchpad)

There’s a definite pattern here, and it’s definitely tied to xhci_hcd

9. tammikuuta 2013 klo 12.11
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Akasa, Linux

There’s a definite pattern here, and it’s definitely tied to xhci_hcd, usb-storage and the Akasa/Genesys card reader. Here’s what I’ve done since reporting this:

1) Set ”Legacy USB 3.0” in the BIOS from ”Enabled” to ”Disabled”, and ”Intel xHCI Mode” from ”Smart Auto” to ”Enabled”. I tested briefly with latter set to ”Disabled” and Legacy 3.0 ”Enabled”, but then the card reader wasn’t detected at all and I’d prefer a working XHCI anyway.

2) Switched to mainline kernel 3.8.0-030800rc2-generic #201301022235. With the earlier kernels (3.5 and 3.2 from Precise repo) things have seemed similar to my findings below with mainline, but data with 3.2 and 3.5 are too few to say conclusively there’s no difference at all. I’ve concentrated my testing to mainline just to keep things simpler.

Here’s the pattern with mainline:

1) Cold boot. Early in the boot, the card reader in USB #4 is asked to reset. This results in a flood of ”xHCI xhci_drop_endpoint called with disabled ep ffff880403c8d500”:

Jan 8 10:32:12 saegusa kernel: [ 721.015249] usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd
Jan 8 10:32:12 saegusa kernel: [ 721.032596] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880403c8d500
Jan 8 10:32:12 saegusa kernel: [ 721.032599] xhci_hcd 0000:00:14.0: xHCI xhci_drop_endpoint called with disabled ep ffff880403c8d540

When these messages are there, the session will crash (panic/freeze) at some point; using the card reader isn’t necessary (panics without it eventually too), but it’s easy enough to trigger just by sticking an SD card into the reader. The reader reports buffer errors on the card and then boom.

Jan 8 10:32:13 saegusa kernel: [ 721.713295] sd 8:0:0:2: [sdf] Unhandled error code
Jan 8 10:32:13 saegusa kernel: [ 721.713299] sd 8:0:0:2: [sdf]
Jan 8 10:32:13 saegusa kernel: [ 721.713300] Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK
Jan 8 10:32:13 saegusa kernel: [ 721.713303] sd 8:0:0:2: [sdf] CDB:
Jan 8 10:32:13 saegusa kernel: [ 721.713304] Read(10): 28 00 00 00 20 00 00 00 08 00
Jan 8 10:32:13 saegusa kernel: [ 721.713314] end_request: I/O error, dev sdf, sector 8192
Jan 8 10:32:13 saegusa kernel: [ 721.713318] Buffer I/O error on device sdf1, logical block 0

Another USB #4 -related message often preceding a panic in syslog is this:
Jan 8 17:38:21 saegusa kernel: [ 148.282256] usb 4-4: Disable of device-initiated U1 failed.
Jan 8 17:38:21 saegusa kernel: [ 148.285747] usb 4-4: Disable of device-initiated U2 failed.

The panics, when visible, are always in Pid: usb-storage, and mostly of the ”ring_doorbell_for_active_rings” type (above), but I did have at least one ”warn_slowpath_common” too (will attach a picture if requested).

2) Reboot after the panic, USB #4 doesn’t get reset and no ”disabled ep” or ”Disable of device-initiated …” messages appear in syslog. The card reader works perfectly (i.e. SD card can be inserted and read/written without problems).

3) The panic isn’t necessary to get the card reader working: it’s enough to reboot after one cold boot and the reset signal being sent in that session. Just don’t stay in that cold boot session, because it’ll panic eventually.

I’ll attach a complete syslog from yesterday and today to give context to what I’ve quoted above.

Vastaa viestiin sen kontekstissa (Launchpad)

I don’t see the syslog I mentioned attached above, so I’m attaching it here

7. tammikuuta 2013 klo 11.44
Sijainti: Vianhallintajärjestelmät: Launchpad
Avainsanat: Linux

I don’t see the syslog I mentioned attached above, so I’m attaching it here. Also, the USB-related stuff just preceding the panic starts slightly earlier than what I claimed above, with this reset attempt:

Jan 7 10:45:01 saegusa kernel: [ 413.991127] usb 4-4: reset SuperSpeed USB device number 2 using xhci_hcd

Vastaa viestiin sen kontekstissa (Launchpad)

« Uudempia - Vanhempia »