Processed: Re: Bug#765614: initramfs-tools: Missing fsck. should be non-fatal

2014-10-25 Thread Debian Bug Tracking System
Processing control commands:

> affects -1 xen-tools
Bug #765614 [initramfs-tools] Missing fsck. should be non-fatal
Added indication that 765614 affects xen-tools

-- 
765614: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765614
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.b765614.141427919630996.transcr...@bugs.debian.org



Bug#766802: linux-image-amd64: rt2800usb driver does not include 1b75:a200 USB id's as a supported device

2014-10-25 Thread mmokrejs
Package: linux-image-amd64
Version: 3.2+46
Severity: wishlist

Dear Maintainer,

   I tried an old-ish OvisLink WN-200USB WiFi USB dongle but it is not picked up
 by linux kernel (tried initially 3.2+46 provided by Wheezy but later tried even
 3.15.3 with same result. Thanks to Geoff Simmons I got it working. Below is
 whole recipe. Please contact linux kernel maintainers to add the missing id
 numbers.



Hi Martin,

On Fri, Oct 17, 2014 at 11:20:03PM +0200, Martin Mokrejs wrote:
> while reading https://wiki.debian.org/rt2800usb#supported it seems this
> device is not picked up by the rt2800usb.

Your Ovislink Corp. AirLive WN-200USB wireless LAN adapter (USB ID 1b75:a200,
Ralink RT3070 chip) is not currently defined as a supported device in any
version of the rt2800usb Linux kernel driver code [1] at this time.

This would explain the lack of device interface.

> I just cannot force the 3.10.12 kernel to bind the driver to the device
> and therefore, "iwconfig" does not list ra0 interface.

See above; the driver needs to be informed that your device is supported.
Also, Linux 3.10.2 is not a Linux kernel version currently part of any
Debian release.

On Debian systems, the rt2800usb driver will create a wlanX interface (e.g.
wlan0) by default, not ra0.  ra0 was an interface created by earlier Ralink
drivers included in previous Debian releases.

> I created /etc/modprobe.d/ralink.conf file but no luck.

As your device should be supported, you can try using the following commands
(executed as root/superuser) as a workaround to enable device operation:

  # echo rt2800usb >> /etc/modules
  # echo 'install rt2800usb /sbin/modprobe --ignore-install rt2800usb 
$CMDLINE_OPTS && echo 1b75 a200 > /sys/bus/usb/drivers/rt2800usb/new_id' > 
/etc/modprobe.d/ralink.conf
.. then reload the rt2800usb driver:

  # modprobe -r rt2800usb ; modprobe rt2800usb

.. and reconnect this wireless LAN device.

Based on the manufacturing age of your device, this should allow for device
support with the Linux 3.2 kernel included as part of Debian 7 "Wheezy".

If the commands above are successful for enabling device support, please
consider filing a Debian wishlist bug against an installed Debian Linux
kernel package on your system (e.g. "reportbug linux-image-amd64").

When eventually fixed in Debian, your /etc/modprobe.d/ralink.conf file will
no longer be necessary.

Geoff

[1] 
https://github.com/torvalds/linux/blob/master/drivers/net/wireless/rt2x00/rt2800usb.c





# dmesg (from vanilla 3.15.3 kernel)
[10082.528998] usb 1-1: new high-speed USB device number 9 using xhci_hcd
[10082.686052] usb 1-1: New USB device found, idVendor=1b75, idProduct=a200
[10082.686058] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10082.686061] usb 1-1: Product: 802.11 n WLAN
[10082.686064] usb 1-1: Manufacturer: Ralink
[10082.686066] usb 1-1: SerialNumber: 1.0
[10082.859407] usb 1-1: reset high-speed USB device number 9 using xhci_hcd
[10082.859432] xhci_hcd :00:14.0: Setup ERROR: setup context command for 
slot 8.
[10082.859435] usb 1-1: hub failed to enable device, error -22
[10082.979381] usb 1-1: reset high-speed USB device number 9 using xhci_hcd
[10082.979401] xhci_hcd :00:14.0: Setup ERROR: setup context command for 
slot 8.
[10082.979405] usb 1-1: hub failed to enable device, error -22
[10083.099465] usb 1-1: reset high-speed USB device number 9 using xhci_hcd
[10083.130501] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with 
disabled ep 88030e79d448
[10083.130507] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with 
disabled ep 88030e79d400
[10083.130511] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with 
disabled ep 88030e79d490
[10083.130514] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with 
disabled ep 88030e79d4d8
[10083.130517] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with 
disabled ep 88030e79d520
[10083.130520] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with 
disabled ep 88030e79d568
[10083.130523] xhci_hcd :00:14.0: xHCI xhci_drop_endpoint called with 
disabled ep 88030e79d5b0
[10083.131107] ieee80211 phy1: rt2x00_set_rt: Info - RT chipset 3070, rev 0201 
detected
[10083.142952] ieee80211 phy1: rt2x00_set_rf: Info - RF chipset 0005 detected
[10083.144431] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht'
[10083.146537] ieee80211 phy1: rt2x00lib_request_firmware: Info - Loading 
firmware file 'rt2870.bin'
[10083.223515] ieee80211 phy1: rt2x00lib_request_firmware: Info - Firmware 
detected - version: 0.29
[10083.553859] bridge-wlan1: device is wireless, enabling SMAC
[10083.553866] bridge-wlan1: up
[10083.553882] bridge-wlan1: attached
[10083.555421] bridge-wlan1: disabling the bridge
[10083.753880] userif-2: sent link down event.
[10083.753887] userif-2: sent link up event.
[10084.240378] bridge-wlan1: down
[10084.240477] bridge-wlan1: detached
[10094.278447] ieee80211 phy1: rt2800_wait_wpdma_ready: Error 

Bug#765614: initramfs-tools: Missing fsck. should be non-fatal

2014-10-25 Thread Axel Beckert
Control: affects -1 xen-tools

[I initially sent this to the wrong clone (#764596) of this bug
report, so I'm now hopefully resending it to the right bug report.]

Hi,

Ben Hutchings wrote:
> > I just tried to build an image of current sid for running autopkgtests
> > in:
> > 
> >   $ sudo vmdebootstrap --verbose --serial-console --distribution=sid 
> > --user=adt/adt --size=20 --mbr --image=adt-sid.raw
> > 
> > This worked in the past, but now they are stuck in a boot failure
> > loop;
> > 
> >   $ kvm -m 2048 -snapshot -drive file=adt-sid.raw,if=virtio -monitor none 
> > -nographic -serial stdio
> >   [...]
> >   Begin: Loading essential drivers ... done.
> >   Begin: Running /scripts/init-premount ... done.
> >   Begin: Mounting root file system ... Begin: Running /scripts/local-top 
> > ... done.
> >   Begin: Running /scripts/local-premount ... done.
> >   Begin: Checking root file system ... fsck from util-linux 2.25.1
> >   fsck: error 2 (No such file or directory) while executing fsck.ext4 for 
> > /dev/vda1
> >   fsck exited with status code 8
> >   done.
> [...]

Same counts for Sid Xen DomU bootstrapped via xen-tools (at least with
the git version, both with the modification mentioned below as well as
with an unmodified git checkout):

$ xen-create-image --dist sid --hostname domu1 --force --lvm vg0 --dhcp 
--verbose --pygrub --noaccounts --boot; xl console domu1
[...]
Begin: Checking root file system ... fsck from util-linux 2.25.2
fsck: error 2 (No such file or directory) while executing fsck.ext3 for 
/dev/xvda2
fsck exited with status code 8
done.
Failure: An automatic file system check (fsck) of the root filesystem failed.
A manual fsck must be performed, then the system restarted.
The fsck should be performed in maintenance mode with the
root filesystem mounted in read-only mode.
Warning: The root filesystem is currently mounted in read-only mode.
A maintenance shell will now be started.
After performing system maintenance, press CONTROL-D
to terminate the maintenance shell and restart the system.
sulogin: cannot open password database!
[3.510843] sulogin[84]: segfault at 8 ip 004018e0 sp 
7fff8510bce0 error 4 in sulogin[40+3000]
Segment violation
Failure: Attempt to start maintenance shell failed.
Will restart in 5 seconds.
[8.518847] reboot: Restarting system

> > This might be a regression from recent util-linux, or some
> > misconfiguration, or incompatibility with extlinux, not sure.
> > fsck.ext4 definitively exists (i. e. e2fsprogs is installed), and
> > /dev/vda1 also exists; it's also apparently able to map the root UUID
> > to /dev/vda1.
> [...]
> 
> fsck.ext4 is not present in the initramfs, probably because
> initramfs-tools was installed before e2fsprogs.  Unfortunately, we
> cannot simply make initramfs-tools depend on the appropriate package
> because it depends on which filesystem is used for root.
> 
> vmdebootstrap should install the kernel last so that all programs that
> may be wanted in the initramfs will be available when the initramfs is
> built.

I expected that this would count for xen-tools as well and tried to
fix it by explicitly installing e2fsprogs before initramfs-tools and
the kernel. But the above still happens despite I used this code to
install e2fsprogs, initramfs-tools and kernel:

installDebianPackage ${prefix} e2fsprogs
installDebianPackage ${prefix} initramfs-tools
installDebianPackage ${prefix} $KERNEL_PKG

So I doubt that this can be fixed by reordering the package
installations. (Besides: the log said "e2fsprogs is already the newest
version.", so it didn't change anything.)

The following fsck binary is in the initrd:

# lsinitramfs -l /mnt/tmp//boot/initrd.img-3.16-3-amd64  | fgrep fsck
-rwxr-xr-x   1 root root35664 Oct 24 19:02 sbin/fsck
#

Regards, Axel
-- 
 ,''`.  |  Axel Beckert , http://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE
  `-|  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/20141025231953.gr5...@sym.noone.org



Processed: reassign 766793 src:linux

2014-10-25 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 766793 src:linux 3.16.5-1
Bug #766793 [src:kernel] additional udeb packages for hppa arch
Warning: Unknown package 'src:kernel'
Bug reassigned from package 'src:kernel' to 'src:linux'.
No longer marked as found in versions kernel/3.16.5-1.
Ignoring request to alter fixed versions of bug #766793 to the same values 
previously set
Bug #766793 [src:linux] additional udeb packages for hppa arch
Marked as found in versions linux/3.16.5-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
766793: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766793
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/handler.s.c.141427171115337.transcr...@bugs.debian.org



aacraid: Host adapter reset request. SCSI hang ?

2014-10-25 Thread Camaleón
Hello,

Not sure if this the right place for this, but before going to BTS I
better ask here for some advice.

Recently, (since October 8 and not before) some of my servers running an
up-to-date Wheezy with aacraid card (Adaptec 2020SA) are going nuts:

(...)
Oct 12 07:38:34 my_machine kernel: [3007914.062687] aacraid: Host adapter 
abort request (0,0,0,0)
Oct 12 07:38:34 my_machine kernel: [3007914.065137] aacraid: Host adapter reset 
request. SCSI hang ?
Oct 12 07:38:41 my_machine kernel: [3007920.532027] INFO: task kworker/2:1:37 
blocked for more than 120 seconds.
Oct 12 07:38:41 my_machine kernel: [3007920.535101] "echo 0 > 
/proc/sys/kernel/hung_task_timeout_secs" disables this message.
Oct 12 07:38:41 my_machine kernel: [3007920.538765] kworker/2:1 D 
88022fd13780 037  2 0x
Oct 12 07:38:41 my_machine kernel: [3007920.538803]  8802258a3180 
0046  880226cd0780
Oct 12 07:38:41 my_machine kernel: [3007920.538816]  00013780 
88022591bfd8 88022591bfd8 8802258a3180
Oct 12 07:38:41 my_machine kernel: [3007920.538901]  0001 
00010400 0001 8802259c7be8
Oct 12 07:38:41 my_machine kernel: [3007920.538987] Call Trace:
Oct 12 07:38:41 my_machine kernel: [3007920.539003]  [] ? 
__mutex_lock_common.isra.5+0xff/0x164
Oct 12 07:38:41 my_machine kernel: [3007920.539012]  [] ? 
_raw_spin_unlock_irqrestore+0xe/0xf
Oct 12 07:38:41 my_machine kernel: [3007920.539021]  [] ? 
mutex_lock+0x1a/0x2d
Oct 12 07:38:41 my_machine kernel: [3007920.539077]  [] ? 
reiserfs_mutex_lock_safe+0x19/0x24 [reiserfs]
Oct 12 07:38:41 my_machine kernel: [3007920.539096]  [] ? 
flush_commit_list+0x11b/0x4fc [reiserfs]
Oct 12 07:38:41 my_machine kernel: [3007920.539105]  [] ? 
_cond_resched+0x7/0x1c
Oct 12 07:38:41 my_machine kernel: [3007920.539123]  [] ? 
flush_async_commits+0x3b/0x46 [reiserfs]
Oct 12 07:38:41 my_machine kernel: [3007920.539134]  [] ? 
process_one_work+0x161/0x269
Oct 12 07:38:41 my_machine kernel: [3007920.539142]  [] ? 
worker_thread+0xc2/0x145
Oct 12 07:38:41 my_machine kernel: [3007920.539174]  [] ? 
manage_workers.isra.25+0x15b/0x15b
Oct 12 07:38:41 my_machine kernel: [3007920.539183]  [] ? 
kthread+0x76/0x7e
Oct 12 07:38:41 my_machine kernel: [3007920.539216]  [] ? 
kernel_thread_helper+0x4/0x10
Oct 12 07:38:41 my_machine kernel: [3007920.539250]  [] ? 
kthread_worker_fn+0x139/0x139
Oct 12 07:38:41 my_machine kernel: [3007920.539282]  [] ? 
gs_change+0x13/0x13

Systems do not really hang but any operations are carried out slowly
and after some minutes they recover their normal status. I recently
triggered this messages when simply issuing an update (apt-get update
&& apt-get -V dist-upgrade) but given this message can appear again
I'm not sure what would be the best next step.

Adaptec has a KB article¹ about this but looking at the suggested
value for "timeout" they are already set to 45 seconds but the
message comes out. Should I increase the timeout to something else
like 180 or so? Any tips would be appreciated.

¹http://ask.adaptec.com/app/answers/detail/a_id/15357/related/1

Greetings,

-- 
Camaleón


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/pan.2014.10.25.19.35...@gmail.com



Bug#766448: why one would want fstype auto for /

2014-10-25 Thread 積丹尼 Dan Jacobson
You might ask why one would want fstype auto for /.
Well sometimes it is a lifesaver.
E.g., when trying to boot with a older kernel that doesn't understand
newer filesystems. I don't recall the exact details... but it gave me
the flexibility to change something...


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/87tx2sytld@jidanni.org



Bug#711470: ath9k_htc updated firmware for firmware-linux-free

2014-10-25 Thread Paul van der Vlis
There is a Debian source package for ath9k_htc made by Trisquel people:

http://packages.trisquel.info/en/source/toutatis-updates/open-ath9k-htc-firmware

With regards,
Paul van der Vlis.

-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/544bc69a.7000...@vandervlis.nl



Bug#765426: umount; floppy light and humming still present after "umount" and even after "shutdown"

2014-10-25 Thread Ben Hutchings
On Fri, 2014-10-17 at 00:02 +, Bjarni Ingi Gislason wrote:
> On Wed, Oct 15, 2014 at 12:06:06AM +, Debian Bug Tracking System wrote:
> > Thank you for filing a new Bug report with Debian.
> > 
> [...]
> > 
> > -- 
> > 765426: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=765426
> > Debian Bug Tracking System
> > Contact ow...@bugs.debian.org with problems
> 
>   This bug report belongs most probably to the 'udev' package.
> 
>   Changing the group of '/dev/fd0' from 'disk' to 'floppy' causes 'eject'
> to shut off the floppy drive light after a few seconds, although some
> messages are shown.

I believe that a floppy drive activity light is normally connected to
the spindle motor, i.e. it indicates whether the disk is spinning.  It
is supposed to be turned off automatically by the driver when the drive
is idle, and cannot be directly controlled by userland, so this doesn't
make any sense to me.

>   The bug is therefore caused by creating the device with the wrong
> group.
[...]

I think that's a separate bug that exacerbates an underlying driver bug.

Ben.

-- 
Ben Hutchings
Power corrupts.  Absolute power is kind of neat.
   - John Lehman, Secretary of the US Navy 1981-1987


signature.asc
Description: This is a digitally signed message part


Bug#764718: (no subject)

2014-10-25 Thread Raphael Lisicki
No Problem, I am subscribed to this bug.

So, concerning the question:

I just ran "nmap -T4A" as root(essential) against a router and this
bug occurred. The first time I stumbled upon it, wireshark was
running, but later on, if I am not mistaken, it also crashed without
wireshark.
Note that the router has some severely broken network drivers and it
is extremely likely that it sent some invalid/strange packages.


//raphael


On Sat, Oct 25, 2014 at 9:59 AM, Julien Cristau  wrote:
> On Fri, Oct 24, 2014 at 22:04:42 +0200, Pierre Schweitzer wrote:
>
>> Dear Rapahel,
>>
> Note that you didn't send this to Raphael, unless he was Bcc:ed...
>
> Cheers,
> Julien


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/cabvzywacu0ymaghuighpakklhtllftu1_vtcd7b4e-jr6rx...@mail.gmail.com



Bug#711470: ath9k_htc updated firmware for firmware-linux-free

2014-10-25 Thread Paul van der Vlis
Hello,

I think we must really shame our self this software is not in Debian Jessie!

Is there no RFP?

Maybe it cannot be in firmware-linux-free because the code has another
source.

With regards,
Paul van der Vlis.


-- 
Paul van der Vlis Linux systeembeheer, Groningen
http://www.vandervlis.nl


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: https://lists.debian.org/544b8f32.6090...@vandervlis.nl



Bug#766720: linux-image-3.2.0-4-amd64: some error in dmesg while accessing Philips webcam and after that no access to that cam anymore

2014-10-25 Thread treaki
Package: src:linux
Version: 3.2.60-1+deb7u3
Severity: normal

Hi mentainers,

i dont know if i got to the right spot to report this bug... 
Ive tried to use my (old) philips webcam which has worked in debian squeeze 
somehow (not with every program but with some)...
So i plugged it in, got an /dev/video0 and tried to access it using mplayer 
tv:// and vlc. VLC had unfortunately some
repeat feature activated which lead into a lot of errors in vlc and that dmesg 
error you can see down there.
After that i tried to reset the usb bus with some commands like that 
suggestions:

http://askubuntu.com/questions/645/how-do-you-reset-a-usb-device-from-the-command-line
http://ubuntuforums.org/showthread.php?t=2131751

that did result into some unstoppable processes... So i manually unplugged and 
replugged the webcam but nothing relating it in dmesg happened.

greetings treaki

-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-14) ) #1 SMP Debian 3.2.60-1+deb7u3

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=59125ccf-a853-4d06-8329-8b40b01ca469 ro quiet

** Tainted: PDO (4225)
 * Proprietary module has been loaded.
 * Kernel has oopsed before.
 * Out-of-tree module has been loaded.

** Kernel log:
[35519.007880] pwc: Registered as video0.
[35519.008164] input: PWC snapshot button as 
/devices/pci:00/:00:12.2/usb1/1-4/1-4.4/input/input10
[35519.011235] usbcore: registered new interface driver Philips webcam
[35522.151688] usbcore: registered new interface driver snd-usb-audio
[35564.900218] usb 3-2.3: new low-speed USB device number 6 using ohci_hcd
[35565.009205] usb 3-2.3: New USB device found, idVendor=046d, idProduct=c050
[35565.009213] usb 3-2.3: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[35565.009219] usb 3-2.3: Product: USB-PS/2 Optical Mouse
[35565.009224] usb 3-2.3: Manufacturer: Logitech
[35565.017851] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:12.0/usb3/3-2/3-2.3/3-2.3:1.0/input/input11
[35565.018263] generic-usb 0003:046D:C050.0005: input,hidraw2: USB HID v1.10 
Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:12.0-2.3/input0
[35708.740914] Allocated vmalloc buffer of size 462848 at vaddr=c900117d
[35708.741907] Allocated vmalloc buffer of size 462848 at vaddr=c900118b4000
[35708.750703] pwc: Failed to set LED on/off time (-32)
[35708.772803] usb 1-4: clear tt 1 (0060) error -71
[35719.458124] vb2_vmalloc_put: Freeing vmalloc mem at vaddr=c900117d
[35719.458184] vb2_vmalloc_put: Freeing vmalloc mem at vaddr=c900118b4000
[35751.975237] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35752.968609] usb 1-4: clear tt 1 (0060) error -110
[35752.981116] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35753.980386] usb 1-4: clear tt 1 (0060) error -110
[35753.992891] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35754.992896] usb 1-4: clear tt 1 (0060) error -110
[35755.006282] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35755.021526] usb 1-4: clear tt 1 (0060) error -71
[35755.035286] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35756.032417] usb 1-4: clear tt 1 (0060) error -110
[35756.044929] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35756.056818] usb 1-4: clear tt 1 (0060) error -71
[35756.068921] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35756.077668] usb 1-4: clear tt 1 (0060) error -71
[35756.089687] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35756.091107] Allocated vmalloc buffer of size 462848 at vaddr=c90011998000
[35756.092188] Allocated vmalloc buffer of size 462848 at vaddr=c90011a7c000
[35756.093342] Allocated vmalloc buffer of size 462848 at vaddr=c90011b6
[35756.095064] Allocated vmalloc buffer of size 462848 at vaddr=c90011c44000
[35756.100108] usb 1-4: clear tt 1 (0060) error -71
[35756.112183] pwc: Failed to set LED on/off time (-71)
[35756.122396] usb 1-4: clear tt 1 (0060) error -71
[35756.142516] usb 1-4: clear tt 1 (0060) error -71
[35776.233197] vb2_vmalloc_put: Freeing vmalloc mem at vaddr=c90011998000
[35776.233219] vb2_vmalloc_put: Freeing vmalloc mem at vaddr=c90011a7c000
[35776.233243] vb2_vmalloc_put: Freeing vmalloc mem at vaddr=c90011b6
[35776.233265] vb2_vmalloc_put: Freeing vmalloc mem at vaddr=c90011c44000
[35781.452360] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35781.460960] usb 1-4: clear tt 1 (0060) error -71
[35783.441654] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35784.440544] usb 1-4: clear tt 1 (0060) error -110
[35794.460305] pwc: Failed to set video mode VGA@10 fps; return code = -71
[35794.468535] usb 1-4: clear tt 1 (0060) error -71
[35833.152031] usbcore: deregistering interface driver Philips webcam
[35833.152128] general protection fault:  [#1] SMP 
[35833.152140] CPU 1 
[35

Bug#719474: linux-image-3.2.0-4-686-pae: problem with rtl8185l

2014-10-25 Thread Eric Shattow
Upstream bug #86861 filed: https://bugzilla.kernel.org/show_bug.cgi?id=86861
Freeze problem exists on 3.16 kernel. Same system is functional with
ndiswrapper and Windows XP platform driver.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
https://lists.debian.org/CANV2PTOJuhuKK23PQ0JT=ehqkarmr7szv+j7ykdu9jmm-0m...@mail.gmail.com



Bug#764718: (no subject)

2014-10-25 Thread Julien Cristau
On Fri, Oct 24, 2014 at 22:04:42 +0200, Pierre Schweitzer wrote:

> Dear Rapahel,
> 
Note that you didn't send this to Raphael, unless he was Bcc:ed...

Cheers,
Julien


signature.asc
Description: Digital signature