Bug#759809: linux-image-3.2.0-4-amd64: USB 3 devices fail, logging xHCI xhci_drop_endpoint called with disabled ep ffff8802165db0c0

On Wed, 10 Sep 2014 09:36:14 +0300 =?UTF-8?B?SmFyaSBKeWxow6Q=?= ja...@iki.fi wrote: 'xHCI xhci_drop_endpoint called with disabled ep' This seems to be fixed in version 3.17-rc5. See patch

Bug#759809: linux-image-3.2.0-4-amd64: USB 3 devices fail, logging xHCI xhci_drop_endpoint called with disabled ep ffff8802165db0c0

Same errormessage here. 'xHCI xhci_drop_endpoint called with disabled ep' Motherboard is Asus P8Z77-V LE PLUS I have tried to compile newer kernels from www.kernel.org but bug is still there. Manual says that USB3 works only in Windows. I have disabled USB3 from bios and used USB3 disks in USB2

Bug#653310: Fix

This bug is in versions 1.13 and 1.14. In the file /usr/share/pyshared/LiveMagic/views/wizard.py change row 199 # Boot parameters data['bootappend_live'] = locale=%s keyb=%s % (locale, keyb) to # Boot parameters data['bootappend_live'] = locales=%s keyboard-layouts=%s % (locale,keyb) --

Bug#635929: Workaround

It was not only with Dropbox. All encfs sessions had same error. Then I found this. http://blog.gmane.org/gmane.comp.file-systems.fuse.encfs.user/month=20100301 Error was just like my. I installed testing versions of openssl, libssl1.0.0 and libssl-dev. After compiling (current source from encfs

Bug#635929: Something to do with processor?

This machinen has VIA C7-M Processor. Another machine with Intel Pentium 4 works fine. Both uses same kernel. Linux version 2.6.32-5-686 (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jun 13 04:13:06 UTC 2011 processor : 0 vendor_id :

Bug#635929: encfs: Memory overflow with Dropbox

Package: encfs Version: 1.7.2-1 Severity: important Dropbox is up and running. Then I mount encrypted directory. jari@hp:~$ encfs -f ~/Dropbox/.encrypted ~/Private EncFS-salasana: After that all seems fine but when I try to open file in Private folder encfs fails and I get messaga to console.

Bug#610371: (no subject)

I have HP 2133 minilaptop. It suspends too after unplugging AC. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org

Bug#497932: linux-image-2.6.26-1-amd64: /dev/pktcdvd/0 is read only device.

Solved! New kernel (linux-image-2.6.26-1-amd64_2.6.26-5_amd64.deb) and all works fine again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#497932: linux-image-2.6.26-1-amd64: /dev/pktcdvd/0 is read only device.

Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-4 Severity: normal # mkudffs --udfrev=0x0150 --spartable=2 --media-type=dvdrw /dev/pktcdvd/0 Error opening device: Read-only file system 2.6.25-2-amd64 works. So there it is something broken in 2.6.26-1-amd64. -- Package-specific info: **

Bug#497932: linux-image-2.6.26-1-amd64: /dev/pktcdvd/0 is read only device.

Bastian Blank kirjoitti: Why do you use /dev/pktcdvd/0 instead of /dev/hdX as the manpage say? My understanding is that the pktcdvd devices needs a valid filesystem/track on the medium. I just followed orders in /usr/share/doc/udftools/README.Debian.gz dvd+rw-format -force /dev/hda growisofs

Bug#494082: Workaround

$_xms = (off) In dosemu.conf makes dosemu working. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#494082: More info.

~/.dosemu/boot.log CONF: config variable parser_version_3 set CONF: config variable c_system set CONF: Parsing built-in dosemu.conf file. CONF: config variable version_3_style_used set CONF: Parsing built-in global.conf file. CONF: config variable version_3_style_used unset CONF: config variable

Bug#494082: dosemu: Dosemu fails when I try to run program.

Package: dosemu Version: 1.4.0+svn.1828-2+b1 Severity: normal I try to run accounting program Ykkönen. Dosemu fails at startup with messages: ERROR: SMALLOC: bad pointer passed to smfree() ERROR: SMALLOC: Out Of Memory on alloc, requested=1521664 -- System Information: Debian Release:

Bug#485141: Same problem here.

Memtest 3.4-2 Memtest+ 2.01-1 Both freezes just like that HP machine. Asus P5B Intel Core Duo E8400 3.00GHz 8 GB memory -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]

Bug#438458: linux-image-2.6.18-5-686-bigmem: All freezes on boot after message agpgart:

dann frazier kirjoitti: Can you test this: http://snapshot.debian.net/2007/04/11/debian/pool/main/l/linux-2.6/linux-image-2.6.20-1-686-bigmem_2.6.20-1_i386.deb and if that doesn't work:

Bug#438458: linux-image-2.6.18-5-686-bigmem: All freezes on boot after message agpgart: Detected an Intel 965G Chipset.

Package: linux-image-2.6.18-5-686-bigmem Version: 2.6.18.dfsg.1-13etch1 Severity: important Mothetboard is Asus P5P. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux

Bug#438458: linux-image-2.6.18-5-686-bigmem: All freezes on boot after message agpgart:

linux-image-2.6.18-4-686-bigmem_2.6.18.dfsg.1-12etch2_i386.deb -- Works linux-image-2.6.18-5-686-bigmem_2.6.18.dfsg.1-13etch1_i386.deb -- Freezes on boot linux-image-2.6.18-4-686_2.6.18.dfsg.1-12etch2_i386.deb -- Works linux-image-2.6.18-5-686_2.6.18.dfsg.1-13etch1_i386.deb -- Works Motherboard

Bug#438458: linux-image-2.6.18-5-686-bigmem: All freezes on boot after message agpgart: Detected an Intel 965G Chipset.

linux-image-2.6.18-5-686-bigmem_2.6.18.dfsg.1-13_i386.deb -- Freezes linux-image-2.6.18-5-686_2.6.18.dfsg.1-13_i386.deb -- Works -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]