Bug#651382: linux-image-3.2.0-rc4-amd64: webcam stops working

2011-12-08 Thread Reinhard Karcher
Package: linux-2.6
Version: 3.2~rc4-1~experimental.1
Severity: normal

Dear Maintainer,
 
My webcam doesn't work any longer, neither vlc nor guvcview nor cheese can use
it any longer. The error message from cheese:
libv4l2: error turning on stream: Auf dem Gerät ist kein Speicherplatz mehr 
verfügbar (That means: no space left on device)

The webcam is connected via usb
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 0409:005a NEC Corp. HighSpeed Hub
Bus 006 Device 003: ID 0ac8:3343 Z-Star Microelectronics Corp. Sirius USB 2.0 
Camera
Bus 004 Device 002: ID 08ff:2580 AuthenTec, Inc. AES2501 Fingerprint Sensor

linux-image 3.1 and before are OK.

Reinhard

-- Package-specific info:
** Version:
Linux version 3.2.0-rc4-amd64 (Debian 3.2~rc4-1~experimental.1) 
(b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-5) ) #1 SMP Sun Dec 4 
18:38:24 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-rc4-amd64 
root=UUID=9bb56ba6-3117-47d6-b07c-2cca477643e9 ro quiet cgroup_enable=memory 
pcie_aspm=force i915.i915_enable_rc6=1

** Not tainted

** Kernel log:
[   10.678572] input: Fujitsu FUJ02E3 as 
/devices/LNXSYSTM:00/device:00/FUJ02E3:00/input/input8
[   10.678649] fujitsu_laptop: ACPI: Fujitsu FUJ02E3 [FEXT] (on)
[   10.679350] fujitsu_laptop: BTNI: [0xf0101]
[   10.683650] Registered led device: fujitsu::logolamp
[   10.683798] fujitsu_laptop: driver 0.6.0 successfully loaded
[   10.972699] iwl4965: Intel(R) Wireless WiFi 4965 driver for Linux, in-tree:
[   10.972704] iwl4965: Copyright(c) 2003-2011 Intel Corporation
[   10.972851] iwl4965 :14:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[   10.972864] iwl4965 :14:00.0: setting latency timer to 64
[   10.972904] iwl4965 :14:00.0: Detected Intel(R) Wireless WiFi Link 
4965AGN, REV=0x4
[   11.011783] iwl4965 :14:00.0: device EEPROM VER=0x36, CALIB=0x5
[   11.011808] iwl4965 :14:00.0: Tunable channels: 13 802.11bg, 19 802.11a 
channels
[   11.011898] iwl4965 :14:00.0: irq 45 for MSI/MSI-X
[   11.459532] iwl4965 :14:00.0: loaded firmware version 228.61.2.24
[   11.459897] Registered led device: phy0-led
[   11.518755] psmouse serio4: synaptics: Touchpad model: 1, fw: 6.5, id: 
0x1c0b1, caps: 0xa04711/0xa02000/0x0
[   11.557495] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio4/input/input9
[   11.970883] Linux media interface: v0.10
[   11.991754] Linux video capture interface: v2.00
[   12.022424] snd_hda_intel :00:1b.0: power state changed by ACPI to D0
[   12.022581] snd_hda_intel :00:1b.0: power state changed by ACPI to D0
[   12.022596] snd_hda_intel :00:1b.0: PCI INT A -> GSI 21 (level, low) -> 
IRQ 21
[   12.022690] snd_hda_intel :00:1b.0: irq 46 for MSI/MSI-X
[   12.022735] snd_hda_intel :00:1b.0: setting latency timer to 64
[   12.573043] ieee80211 phy0: Selected rate control algorithm 'iwl-4965-rs'
[   12.886606] hda_codec: ALC262: SKU not ready 0x90970130
[   12.887805] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input10
[   12.951590] uvcvideo: Found UVC 1.00 device Sirius USB2.0 Camera (0ac8:3343)
[   12.955213] input: Sirius USB2.0 Camera as 
/devices/pci:00/:00:1d.7/usb6/6-4/6-4:1.0/input/input11
[   12.955399] usbcore: registered new interface driver uvcvideo
[   12.955403] USB Video Class driver (1.1.1)
[   13.771312] cfg80211: World regulatory domain updated:
[   13.771317] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   13.771323] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   13.771329] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   13.771334] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   13.771340] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   13.771345] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   13.771876] cfg80211: Calling CRDA for country: DE
[   13.777617] cfg80211: Regulatory domain changed to country: DE
[   13.777622] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   13.777628] cfg80211: (240 KHz - 2483500 KHz @ 4 KHz), (N/A, 
2000 mBm)
[   13.777633] cfg80211: (515 KHz - 525 KHz @ 4 KHz), (N/A, 
2000 mBm)
[   13.777639] cfg80211: (525 KHz - 535 KHz @ 4 KHz), (N/A, 
2000 mBm)
[   13.777643] cfg80211: (547 KHz - 5725000 KHz @ 4 KHz), (N/A, 
2698 mBm)
[   13.894573] input: HDA Intel Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input12
[   16.007613] Adding 4803396k swap 

Re: [PATCH] lockdep, bug: Exclude TAINT_OOT_MODULE from disabling lock debugging

2011-12-08 Thread Rusty Russell
On Wed, 07 Dec 2011 14:30:58 +, Ben Hutchings  wrote:
> We do want to allow lock debugging for GPL-compatible modules that are
> not (yet) built in-tree.  This was disabled as a side-effect of commit
> 2449b8ba0745327c5fa49a8d9acffe03b2eded69 ('module,bug: Add
> TAINT_OOT_MODULE flag for modules not built in-tree').  Lock debug
> warnings now include taint flags, so kernel developers should still
> be able to deflect warnings caused by out-of-tree modules.
> 
> The TAINT_PROPRIETARY_MODULE flag for non-GPL-compatible modules will
> still disable lock debugging.
> 
> Signed-off-by: Ben Hutchings 

Meh.  Disabling lock debugging was always a weird thing to do, IMHO.
Taint flags should be used for warnings to developers, not these strange
side-effects.

Cheers,
Rusty.


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/8762hrit26@rustcorp.com.au



Bug#651382: linux-image-3.2.0-rc4-amd64: webcam stops working

2011-12-08 Thread Reinhard Karcher

It's a kernel bug, that vanished with the latest git from kernel.org.
The bugs exists in the 3.2-rc4 revision at git.kernel.org.

Reinhard



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ee09045.8040...@gmx.net



Bug#651440: Missing et131x module in installer

2011-12-08 Thread Ben Hutchings
Source: linux-2.6
Version: 3.1.4-1
Severity: important
Tags: d-i

According to  this module should be
available in the installer.  However, it seems to have been dropped
when et131x moved from linux-modules-extra-2.6 into linux-2.6.

Ben.

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (x86_64)

Kernel: Linux 3.1.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111208161433.20916.39007.reportbug@deadeye



Bug#651443: Firmware for Adaptec Starfire missing in Squeeze

2011-12-08 Thread Peter Nelson
Package: linux-image-2.6.32-5-amd64
Version: 2.6.32-38

The firmware files required when using an Adaptec Starfire-based network
card using the kernel driver starfire.ko are missing. They are in
neither the linux-image package, nor firmware-linux-free or
firmware-linux-nonfree.

Without the firmware the card is detected but attempting to bring it up
fails:

[  354.472460] starfire :0b:04.0: firmware: requesting 
adaptec/starfire_rx.bin
[  354.475973] starfire: Failed to load firmware "adaptec/starfire_rx.bin"

Additionally I used apt-get source to on linux-source-2.6,
firmware-linux-free and firmware-linux-nonfree, and none of the source
packages contained the firmware source.

Finally I downloaded vanilla source of linux-2.6.32.27.tar.bz2 from
ftp.kernel.org, and the source for this firmware IS contained there.

-- 
Peter Nelson 




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


[bts-link] source package linux-2.6

2011-12-08 Thread bts-link-upstream
#
# bts-link upstream status pull for source package linux-2.6
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#

user bts-link-upstr...@lists.alioth.debian.org

# remote status report for #604459 (http://bugs.debian.org/604459)
# Bug title: libdrm-nouveau1: fresh install with Squeeze Beta 1 netinst-amd64 
results in hang on boot on MacBook 5, 3
#  * https://bugs.freedesktop.org/show_bug.cgi?id=27501
#  * remote status changed: (?) -> NEW
usertags 604459 + status-NEW

thanks


--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: 
http://lists.debian.org/20111208163938.23716.48724.btsl...@busoni.debian.org



Re: Firmware for Adaptec Starfire missing in Squeeze

2011-12-08 Thread Jonathan Nieder
reassign 651443 src:firmware-nonfree 0.28+squeeze1
quit

Hi,

Peter Nelson wrote:

> The firmware files required when using an Adaptec Starfire-based network
> card using the kernel driver starfire.ko are missing. They are in
> neither the linux-image package, nor firmware-linux-free or
> firmware-linux-nonfree.

Hmm.  

>From WHENCE in the linux-firmware repository[1]:

| Driver: starfire - Adaptec Starfire/DuraLAN support
|
| File: adaptec/starfire_rx.bin
| File: adaptec/starfire_tx.bin
|
| Licence: Allegedly GPLv2, but no source visible.

Which means we do not have permission to distribute that version without
source.  However, at [2], I see:

| FreeBSD appears to have copied the proper copyright notices into their
| versions of the firmware:
| http://fxr.watson.org/fxr/source/dev/sf/starfire_rx.h
| http://fxr.watson.org/fxr/source/dev/sf/starfire_tx.h
|
| "(c)2001 Adaptec, Inc. By using this software you agree that it is
| licensed to you "AS IS" and that Adaptec makes no warranties,
| express or implied, regarding the Software.
| Any redistribution of this Software must include this disclaimer and
| copyright notice."

That doesn't actually say that redistribution is allowed, either. :/

FreeBSD's changelog for these files says

| Import AIC-6915 firmware for GFP from Adaptec.
| Special thanks to bruffer to send the firmware image to me.
|
| Submitted by: gibbs via bruffer

which sounds legit to me.  What's the next step?

Thanks and hope that helps,
Jonathan

[1] git://git.kernel.org/pub/scm/linux/kernel/git/dwmw2/linux-firmware.git
[2] http://bugs.debian.org/501152#20


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111208175740.gj2...@elie.hsd1.il.comcast.net



Processed: Re: Firmware for Adaptec Starfire missing in Squeeze

2011-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> reassign 651443 src:firmware-nonfree 0.28+squeeze1
Bug #651443 [linux-image-2.6.32-5-amd64] Firmware for Adaptec Starfire missing 
in Squeeze
Bug reassigned from package 'linux-image-2.6.32-5-amd64' to 
'src:firmware-nonfree'.
Bug No longer marked as found in versions linux-2.6/2.6.32-38.
Bug #651443 [src:firmware-nonfree] Firmware for Adaptec Starfire missing in 
Squeeze
The source firmware-nonfree and version  do not appear to match any binary 
packages
Bug Marked as found in versions firmware-nonfree/0.28+squeeze1.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
651443: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651443
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: 
http://lists.debian.org/handler.s.c.132336707329383.transcr...@bugs.debian.org



Bug#651382: webcam stops working

2011-12-08 Thread Jonathan Nieder
tags 651382 + upstream patch fixed-upstream
quit

Reinhard Karcher wrote:

> It's a kernel bug, that vanished with the latest git from kernel.org.
> The bugs exists in the 3.2-rc4 revision at git.kernel.org.

Thanks.  I guess the fix is e3420901eba6 ("EHCI : Fix a regression in
the ISO scheduler", 2011-11-28).

Luckily the commit introducing the regression (811c926c538f,
"USB: EHCI: fix HUB TT scheduling issue with iso transfer", 2011-10-27)
never hit sid.  (It entered the linux-3.1.y tree in v3.1.3 but was
reverted before the v3.1.4 release.)



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111208181325.ga3...@elie.hsd1.il.comcast.net



Processed: Re: webcam stops working

2011-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 651382 + upstream patch fixed-upstream
Bug #651382 [linux-2.6] linux-image-3.2.0-rc4-amd64: webcam stops working
Added tag(s) upstream, fixed-upstream, and patch.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
651382: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651382
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: 
http://lists.debian.org/handler.s.c.13233680202105.transcr...@bugs.debian.org



Bug#651382: webcam stops working

2011-12-08 Thread Ben Hutchings
On Thu, Dec 08, 2011 at 12:13:25PM -0600, Jonathan Nieder wrote:
> tags 651382 + upstream patch fixed-upstream
> quit
> 
> Reinhard Karcher wrote:
> 
> > It's a kernel bug, that vanished with the latest git from kernel.org.
> > The bugs exists in the 3.2-rc4 revision at git.kernel.org.
> 
> Thanks.  I guess the fix is e3420901eba6 ("EHCI : Fix a regression in
> the ISO scheduler", 2011-11-28).
> 
> Luckily the commit introducing the regression (811c926c538f,
> "USB: EHCI: fix HUB TT scheduling issue with iso transfer", 2011-10-27)
> never hit sid.  (It entered the linux-3.1.y tree in v3.1.3 but was
> reverted before the v3.1.4 release.)
 
I've cherry-picked both those fixes for 3.1.4-2; I assume this is OK.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111208184844.gm3...@decadent.org.uk



Bug#651382: webcam stops working

2011-12-08 Thread Jonathan Nieder
Ben Hutchings wrote:
> On Thu, Dec 08, 2011 at 12:13:25PM -0600, Jonathan Nieder wrote:

>> I guess the fix is e3420901eba6 ("EHCI : Fix a regression in
>> the ISO scheduler", 2011-11-28).
>>
>> Luckily the commit introducing the regression (811c926c538f,
>> "USB: EHCI: fix HUB TT scheduling issue with iso transfer", 2011-10-27)
>> never hit sid.  (It entered the linux-3.1.y tree in v3.1.3 but was
>> reverted before the v3.1.4 release.)
>
> I've cherry-picked both those fixes for 3.1.4-2; I assume this is OK.

Thanks for the pointer.  Yep, looks good.

Just curious: why are the patches listed in debian/patches/series/base
instead of .../2?



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111208191746.gb3...@elie.hsd1.il.comcast.net



Bug#651382: webcam stops working

2011-12-08 Thread Ben Hutchings
On Thu, Dec 08, 2011 at 01:17:46PM -0600, Jonathan Nieder wrote:
> Ben Hutchings wrote:
> > On Thu, Dec 08, 2011 at 12:13:25PM -0600, Jonathan Nieder wrote:
> 
> >> I guess the fix is e3420901eba6 ("EHCI : Fix a regression in
> >> the ISO scheduler", 2011-11-28).
> >>
> >> Luckily the commit introducing the regression (811c926c538f,
> >> "USB: EHCI: fix HUB TT scheduling issue with iso transfer", 2011-10-27)
> >> never hit sid.  (It entered the linux-3.1.y tree in v3.1.3 but was
> >> reverted before the v3.1.4 release.)
> >
> > I've cherry-picked both those fixes for 3.1.4-2; I assume this is OK.
> 
> Thanks for the pointer.  Yep, looks good.
> 
> Just curious: why are the patches listed in debian/patches/series/base
> instead of .../2?

Now that the linux-2.6 source package builds its own udebs, the
standard constraints of the archive software are sufficient to comply
with the GPL source distribution requirements.  There is no need for
us to split the patch series to allow reconstruction of the sources
for outdated kernel udebs.

Ben.

-- 
Ben Hutchings
We get into the habit of living before acquiring the habit of thinking.
  - Albert Camus



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111208202052.go3...@decadent.org.uk



Bug#651199: Info received (Bug#651199: Acknowledgement (linux-image-3.1.0-1-amd64: Connection lost on WPA: Group rekeying))

2011-12-08 Thread Andreas Gustafsson
I've further noticed that the rekeying works while on heavy network
load. It more or less only breaks on idle connection.

Best regards,
Andreas




-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1323376797.5282.8.camel@neith



Bug#651467: kernel-handbook: patches are not split by patchlevel any more

2011-12-08 Thread Jonathan Nieder
Package: debian-kernel-handbook
Version: 1.0.12

Ben Hutchings wrote[1]:

> Now that the linux-2.6 source package builds its own udebs, the
> standard constraints of the archive software are sufficient to comply
> with the GPL source distribution requirements.  There is no need for
> us to split the patch series to allow reconstruction of the sources
> for outdated kernel udebs.

Oh, nice.  Thanks.

Before I forget, here are sections of the kernel-handbook that do not
reflect this yet.

 chapter-scope.sgml: §1.1 "Scope"

replace "Lenny release of Debian (version 5.0)", by "Wheezy
release of Debian (version 7.0)"

 chapter-common-tasks.sgml: §4.1 "Obtaining the Debian kernel source"

remove the paragraph starting with "In order to get the
Debian kernel source at a patchlevel different from
the one provided by the current linux-source-version
package".

in the next paragraph, remove "to achieve any patchlevel up to
N (e.g. patch level 8 for 2.6.18-8)".

 chapter-packaging.sgml: §3.2 "Architecture-independent packages"

remove the phrase ", bringing the source to the desired
patchlevel".

the paragraph on kernel-patches/all/version/debian/series
probably needs to be rewritten.

remove the note starting "Note that there is currently a bug
in the script"

Since the online copy of the kernel handbook is often used by people
working with squeeze, this should probably be done as two patches ---
one to add a note to the relevant sections that this detail is
different between squeeze and wheezy, and another to remove the old
details once we no longer care about them.

[1] http://bugs.debian.org/651382



--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111208204516.ga5...@elie.hsd1.il.comcast.net



Bug#598144: rt2500pci: very low transfers and link quality

2011-12-08 Thread David Sanchez Herrero
Hi again,

Finally, after analyzing my laptop's hard disk, I have remembered the final
solution, that was using Ndiswrapper with rt2500 Windows drivers. It was
the only way...

Greetings, David.

2011/12/5 David Sanchez Herrero 

> Hi Jonathan,
>
> Thanks for reply about this problem, but the laptop with rt2500 wireless
> card died 6 or 7 months ago (a graphic card crash), so I can't try the 3.1
> kernel version. I think that after a lot of tests (compiling a new module
> version using compat-wireless project, compiling the drivers from Ralink,
> updating the kernel version, disabling Network-Manager to manually
> configure the card, ...), I finally got the wireless card working fine, but
> now I can't remember which was the final solution to the problem.
>
> I'm sure that there was something bad with the rt2500pci module because I
> found a lot of information about the problem, associated to different
> distros, and I could verify with a Live CD that the problem was in Ubuntu
> too.
>
> I'm thinking about analyze the laptop hard disk this Christmas to recover
> some files to my new computer, so if I find some information about the
> solutión that I applied, I promise to write again to tell you.
>
> Meanwhile, I think that you can mark this bug as solved if you want.
>
> Greetings, David.
>
> El 3 de diciembre de 2011 08:19, Jonathan Nieder escribió:
>
> # forwarded last year:
>> #  http://thread.gmane.org/gmane.linux.kernel.wireless.general/56714
>> # no response, so let's try again.
>> notforwarded 598144
>> quit
>>
>> Heya,
>>
>> Regarding version 2.6.32-20, David Sánchez Herrero wrote:
>>
>> > I have been using rt2500pci since rt2500 legacy drivers source package
>> > dissapeared from the repository, and I have had this problems from the
>> first
>> > time until now. The legacy drivers worked fine, but with the new ones I
>> have
>> > very low transfers and poor link quality.
>>
>> That's no good.  So let's see.
>>
>> [...]
>> > it's
>> > impossible to make anything because in all terminals appears one message
>> > continously:
>> >
>> > cfg80211: Calling CRDA to update world regulatory domain.
>> >
>> > I can see that I lose the connection, probably because this message.
>> This
>> > happens with 2.6.36-rc5-686 kernel. Any idea about solving this problem?
>>
>> Very odd.  Does it still happen?
>>
>> [...]
>> > This problem doesn't exists with 2.6.32-5-686 kernel, but with it, I
>> > have again the error message that appears in my first report:
>> >
>> > phy0 -> rt2500pci_set_device_state: Error - Device failed to enter
>> state 1 (-16).
>>
>> Which kernel version is that?  You can get the currently running
>> kernel version by running "cat /proc/version" and looking for the
>> string in parentheses.
>>
>> I don't see any relevant fixes upstream (amazingly, since the driver
>> has had a lot of work done).  If you can get a chance to test a 3.1.y
>> or later kernel from sid, that would be very helpful.  (Then we can
>> get help from upstream.)  For graphics, while testing you can use the
>> vesa driver or nouveau.
>>
>> Thanks for writing and hope that helps,
>> Jonathan
>>
>> [...]
>> > 01:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
>> RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 01)
>> >   Subsystem: Micro-Star International Co., Ltd. Device [1462:3fcc]
>>
>
>


Bug#651469: linux-image-3.1.0-1-amd64: sky2 rx checksum failures on linux-image 3.1 with xen

2011-12-08 Thread Krzysztof Cybulski
Package: linux-2.6

Version: 3.1.1-1
Severity: normal

rx checksum failure occurs on sky2 module on 3.1.0-1, when I boot to kernel
3.0.0-3 there is no errors. Both kernels run with xen



-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.1-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-4) ) #1 SMP Mon Nov 14 08:02:25 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-amd64 
root=UUID=28ddd811-92e6-41c7-9711-9f951b73bce2 ro quiet

** Tainted: PO (4097)
 * Proprietary module has been loaded.
 * Out-of-tree module has been loaded.

** Kernel log:
[12084.877570]  [] ? br_multicast_rcv+0x7e8/0xca1 [bridge]
[12084.877573]  [] ? send_sigio_to_task+0xb0/0xbd
[12084.877576]  [] ? number.isra.3+0x10e/0x218
[12084.877579]  [] ? timekeeping_get_ns+0xd/0x2a
[12084.877583]  [] ? arch_local_irq_save+0x11/0x17
[12084.877586]  [] ? _raw_spin_lock_irqsave+0x9/0x25
[12084.877591]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877594]  [] ? nf_hook_slow+0x73/0x111
[12084.877599]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877604]  [] ? br_nf_forward_finish+0x95/0x95 [bridge]
[12084.877610]  [] ? br_handle_frame_finish+0x90/0x20f 
[bridge]
[12084.877615]  [] ? br_nf_pre_routing_finish_ipv6+0x89/0x92 
[bridge]
[12084.877620]  [] ? setup_pre_routing+0x38/0x5d [bridge]
[12084.877625]  [] ? br_nf_pre_routing+0x3e8/0x3f5 [bridge]
[12084.877629]  [] ? find_busiest_group+0x202/0x819
[12084.877632]  [] ? nf_iterate+0x41/0x77
[12084.877637]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877642]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877645]  [] ? nf_hook_slow+0x73/0x111
[12084.877649]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877655]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877660]  [] ? NF_HOOK.constprop.4+0x3c/0x56 [bridge]
[12084.877663]  [] ? ipv6_gro_receive+0xf2/0x265
[12084.877668]  [] ? br_handle_frame+0x1a4/0x1bb [bridge]
[12084.877673]  [] ? br_handle_frame_finish+0x20f/0x20f 
[bridge]
[12084.877676]  [] ? __netif_receive_skb+0x2d6/0x415
[12084.877679]  [] ? netif_receive_skb+0x63/0x69
[12084.877682]  [] ? napi_gro_receive+0x1d/0x2b
[12084.877684]  [] ? napi_skb_finish+0x1c/0x31
[12084.877690]  [] ? sky2_poll+0x782/0x9a0 [sky2]
[12084.877693]  [] ? enqueue_task_fair+0x7f/0x175
[12084.877696]  [] ? test_tsk_need_resched+0xa/0x13
[12084.877699]  [] ? check_preempt_curr+0x36/0x5f
[12084.877702]  [] ? net_rx_action+0xa1/0x1af
[12084.877705]  [] ? hrtimer_get_next_event+0x79/0x8f
[12084.877709]  [] ? __do_softirq+0xb9/0x177
[12084.877712]  [] ? timekeeping_get_ns+0xd/0x2a
[12084.877715]  [] ? call_softirq+0x1c/0x30
[12084.877718]  [] ? do_softirq+0x3c/0x7b
[12084.877721]  [] ? irq_exit+0x3c/0x9a
[12084.877724]  [] ? do_IRQ+0x82/0x98
[12084.877727]  [] ? common_interrupt+0x6e/0x6e
[12084.877728][] ? mwait_idle+0x7f/0xac
[12084.877733]  [] ? mwait_idle+0x72/0xac
[12084.877736]  [] ? cpu_idle+0xa6/0xe0
[12084.877739]  [] ? arch_local_irq_restore+0x2/0x8
[12084.877742]  [] ? start_secondary+0x1d5/0x1db
[12084.877747] eth0: hw csum failure.
[12084.877749] Pid: 0, comm: kworker/0:1 Tainted: P   O 3.1.0-1-amd64 #1
[12084.877751] Call Trace:
[12084.877752][] ? netdev_rx_csum_fault+0x29/0x31
[12084.877758]  [] ? __skb_checksum_complete_head+0x41/0x53
[12084.877764]  [] ? br_multicast_rcv+0x7e8/0xca1 [bridge]
[12084.877767]  [] ? send_sigio_to_task+0xb0/0xbd
[12084.80]  [] ? number.isra.3+0x10e/0x218
[12084.83]  [] ? timekeeping_get_ns+0xd/0x2a
[12084.86]  [] ? arch_local_irq_save+0x11/0x17
[12084.877780]  [] ? _raw_spin_lock_irqsave+0x9/0x25
[12084.877785]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877788]  [] ? nf_hook_slow+0x73/0x111
[12084.877793]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877798]  [] ? br_nf_forward_finish+0x95/0x95 [bridge]
[12084.877803]  [] ? br_handle_frame_finish+0x90/0x20f 
[bridge]
[12084.877808]  [] ? br_nf_pre_routing_finish_ipv6+0x89/0x92 
[bridge]
[12084.877814]  [] ? setup_pre_routing+0x38/0x5d [bridge]
[12084.877819]  [] ? br_nf_pre_routing+0x3e8/0x3f5 [bridge]
[12084.877822]  [] ? find_busiest_group+0x202/0x819
[12084.877825]  [] ? nf_iterate+0x41/0x77
[12084.877830]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877835]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877838]  [] ? nf_hook_slow+0x73/0x111
[12084.877843]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877848]  [] ? NF_HOOK.constprop.4+0x56/0x56 [bridge]
[12084.877853]  [] ? NF_HOOK.constprop.4+0x3c/0x56 [bridge]
[12084.877856]  [] ? ipv6_gro_receive+0xf2/0x265
[12084.877861]  [] ? br_handle_frame+0x1a4/0x1bb [bridge]
[12084.877866]  [] ? br_handle_frame_finish+0x20f/0x20f 
[bridge]
[12084.877869]  [] ? __netif_receive_skb+0x2d6/0x415
[12084.877872]  [] ? netif_receive_skb+0x63/0x69
[12084.877875]  [] ? napi_gro_receive+0x1d/0x2b
[12084.877878]  [] ? napi_skb_finish+0x1c/0x31
[12084.877883]  [] ? sky2_poll+0x782/0x9a0 [sky2]
[12084.877886]  [] ? enqueue_task_fair+0x7f/0x175
[12084.8

Bug#651199: iwlwifi: Connection lost on "WPA: Group rekeying"

2011-12-08 Thread Jonathan Nieder
Andreas Gustafsson wrote:

> I've further noticed that the rekeying works while on heavy network
> load. It more or less only breaks on idle connection.

Was this a regression?  What is the last kernel version you tried
that worked?

Can we take a peek at the relevant portion of syslog?

Please test v3.2-rc4 from experimental or a newer kernel.  If it is
still reproducible, please write a summary of your findings to
i...@linux.intel.com, cc-ing Wey-Yi Guy ,
linux-wirel...@vger.kernel.org, linux-ker...@vger.kernel.org, and
either me or this bug log so we can track it.

Be sure to include:

 - steps to reproduce and the resulting symptoms

 - full "dmesg" output from booting the affected kernel and
   reproducing trouble

 - an event log from reproducing it without NetworkManager, if
   possible[*]

 - which kernel versions you've tested, and what happened with
   each

 - any other weird symptoms or observations

 - a link to this bug log, in case the reader wants the full
   story

Hope that helps,
Jonathan

[*] instructions here:
http://linuxwireless.org/en/users/Documentation/Reporting_bugs



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20111208211229.ga6...@elie.hsd1.il.comcast.net



Bug#651469: linux-image-3.1.0-1-amd64: sky2 rx checksum failures on linux-image 3.1 with xen

2011-12-08 Thread Ben Hutchings
On Thu, 2011-12-08 at 22:11 +0100, Krzysztof Cybulski wrote:
> Package: linux-2.6
> 
> Version: 3.1.1-1
> Severity: normal
> 
> rx checksum failure occurs on sky2 module on 3.1.0-1, when I boot to kernel
> 3.0.0-3 there is no errors. Both kernels run with xen
[...]

This is a bug in the bridge module (though it particularly affects
interaction with sky2 and not many other drivers).  It is due to be
fixed in Linux 3.1.5.

Ben.

-- 
Ben Hutchings
In a hierarchy, every employee tends to rise to his level of incompetence.


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


Processed: tagging 651440

2011-12-08 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 651440 + pending
Bug #651440 [src:linux-2.6] Missing et131x module in installer
Added tag(s) pending.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
651440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=651440
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: 
http://lists.debian.org/handler.s.c.132339113121572.transcr...@bugs.debian.org



Bug#613321: linux-image-amd64: Please enable 'memtest' option for all linux kernels

2011-12-08 Thread Carlos Alberto Lopez Perez
On 05/12/11 06:53, Ben Hutchings wrote:
> Since this feature requires almost no extra memory (the code is all
> discardable after boot) I'm prepared to enable it.  However, I will
> modify it to taint the kernel if any memory fault is detected, on the
> basis that there are likely to be other undetected faults.

Indeed good idea. I think you should submit this patch upstream.


Regards!

-- 
~~~
Carlos Alberto Lopez Perez   http://neutrino.es
Igalia - Free Software Engineeringhttp://www.igalia.com
~~~



-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4ee18871.8020...@igalia.com



Re: Increasing minimum 'i386' processor

2011-12-08 Thread Miles Bader
Ian Jackson  writes:
>> The 486-class processors that would no longer be supported are:
>> 1. All x86 processors with names including '486'
>
> I'm still running the machine below, and it would be irritating to
> have to replace it.
...
> vendor_id : CentaurHauls
> cpu family: 6
> model : 7
> model name: VIA Samuel 2

AFAICT, the above would be considered a 586-class CPU... so no prob!

-Miles

-- 
A zen-buddhist walked into a pizza shop and
said, "Make me one with everything."


-- 
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/buor50e1eo5@dhlpc061.dev.necel.com