Bug#645589: linux-image-3.0.0-2-amd64: sky2 rx errors on 3.0, 2.6.32 works

[Antti Salmela]

Package: linux-2.6
Version: 3.0.0-5
Severity: normal


sky2 loses packets on 3.0 (-3 and -5) and 3.1-rc7, 2.6.32-38 and setting 
interface to promiscuous works.

[   60.118244] sky2 :02:00.0: eth0: rx error, status 0xb92100 length 185
[   62.664370] sky2 :02:00.0: eth0: rx error, status 0x602100 length 96
[   63.370051] sky2 :02:00.0: eth0: rx error, status 0x422100 length 66
[   63.714672] sky2 :02:00.0: eth0: rx error, status 0x722100 length 114
[   64.513458] device eth0 entered promiscuous mode

-- Package-specific info:
** Version:
Linux version 3.0.0-2-amd64 (Debian 3.0.0-5) (b...@decadent.org.uk) (gcc 
version 4.5.3 (Debian 4.5.3-9) ) #1 SMP Fri Oct 7 20:48:45 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.0.0-2-amd64 root=/dev/mapper/thor-root ro quiet 
elevator=deadline

** Not tainted

** Kernel log:
[2.868856] ACPI: Power Button [PWRF]
[2.894085] input: PC Speaker as /devices/platform/pcspkr/input/input2
[2.902355] ACPI: acpi_idle registered with cpuidle
[2.912736] i801_smbus :00:1f.3: PCI INT B -> GSI 23 (level, low) -> IRQ 
23
[2.947532] intel_rng: FWH not detected
[2.967378] wmi: Mapper loaded
[2.980088] leds_ss4200: no LED devices found
[2.997643] Error: Driver 'pcspkr' is already registered, aborting...
[3.030097] [drm] Initialized drm 1.1.0 20060810
[3.051696] HDA Intel :00:1b.0: PCI INT A -> GSI 19 (level, low) -> IRQ 
19
[3.051751] HDA Intel :00:1b.0: irq 45 for MSI/MSI-X
[3.051781] HDA Intel :00:1b.0: setting latency timer to 64
[3.128882] hda_codec: ALC882: BIOS auto-probing.
[3.129611] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input3
[3.133554] input: HDA Intel Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input4
[3.206734] nouveau :04:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[3.206742] nouveau :04:00.0: setting latency timer to 64
[3.208306] [drm] nouveau :04:00.0: Detected an NV40 generation card 
(0x044300a2)
[3.210790] [drm] nouveau :04:00.0: Attempting to load BIOS image from 
PRAMIN
[3.285326] [drm] nouveau :04:00.0: ... appears to be valid
[3.285332] [drm] nouveau :04:00.0: BIT BIOS found
[3.285335] [drm] nouveau :04:00.0: Bios version 05.44.02.62
[3.285339] [drm] nouveau :04:00.0: TMDS table version 1.1
[3.285342] [drm] nouveau :04:00.0: BIT table 'd' not found
[3.285345] [drm] nouveau :04:00.0: Found Display Configuration Block 
version 3.0
[3.285348] [drm] nouveau :04:00.0: Raw DCB entry 0: 01010310 0028
[3.285352] [drm] nouveau :04:00.0: Raw DCB entry 1: 01001302 
[3.285355] [drm] nouveau :04:00.0: Raw DCB entry 2: 020223f1 0080c020
[3.285358] [drm] nouveau :04:00.0: DCB connector table: VHER 0x30 5 7 2
[3.285362] [drm] nouveau :04:00.0:   0: 0x: type 0x00 idx 0 tag 
0xff
[3.285366] [drm] nouveau :04:00.0:   1: 0x1131: type 0x31 idx 1 tag 
0x07
[3.285369] [drm] nouveau :04:00.0:   2: 0x0210: type 0x10 idx 2 tag 
0xff
[3.285372] [drm] nouveau :04:00.0:   3: 0x0211: type 0x11 idx 3 tag 
0xff
[3.285376] [drm] nouveau :04:00.0:   4: 0x0213: type 0x13 idx 4 tag 
0xff
[3.285383] [drm] nouveau :04:00.0: Parsing VBIOS init table 0 at offset 
0xDF5B
[3.285643] [drm] nouveau :04:00.0: Parsing VBIOS init table 1 at offset 
0xE2B7
[3.298763] [drm] nouveau :04:00.0: Parsing VBIOS init table 2 at offset 
0xE745
[3.298779] [drm] nouveau :04:00.0: Parsing VBIOS init table 3 at offset 
0xE89A
[3.299890] [drm] nouveau :04:00.0: Parsing VBIOS init table 4 at offset 
0xE96D
[3.299894] [drm] nouveau :04:00.0: mem timing table length unknown: 14
[3.299938] [drm] nouveau :04:00.0: timingset 255 does not exist
[3.318898] [drm] nouveau :04:00.0: 1 available performance level(s)
[3.318903] [drm] nouveau :04:00.0: 0: memory 500MHz core 350MHz 
fanspeed 100%
[3.318912] [drm] nouveau :04:00.0: c: memory 401MHz core 200MHz
[3.319007] [TTM] Zone  kernel: Available graphics memory: 1030504 kiB.
[3.319009] [TTM] Initializing pool allocator.
[3.319031] [drm] nouveau :04:00.0: Detected 64MiB VRAM
[3.325620] [drm] nouveau :04:00.0: 512 MiB GART (aperture)
[3.325698] [drm] nouveau :04:00.0: Saving VGA fonts
[3.379957] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[3.379960] [drm] No driver support for vblank timestamp query.
[3.380813] [drm] nouveau :04:00.0: Setting dpms mode 3 on vga encoder 
(output 0)
[3.380817] [drm] nouveau :04:00.0: Setting dpms mode 3 on tmds encoder 
(output 1)
[3.380821] [drm] nouveau :04:00.0: Setting dpms mode 3 on TV encoder 
(output 2)
[3.460030] No connectors reported connected with modes
[3.460035] [drm] Cannot find any crtc or sizes - going 1024x768
[3.460571] [drm] nouveau :04

Bug#587355: i915: X locks up when trying to play DVD on Thinkpad X40

[Jonathan Nieder]

tags 587355 + moreinfo
quit

Hi again,

Jonathan Nieder wrote:
> Petter Reinholdtsen wrote:

>> I ran into this on a freshly installed Thinkpad X40 with todays
>> Debian/Squeeze.  The external VGA connector is connected to a video
>> projector.  I plugged in a USB DVD player, installed libdvdcss2 and
>> tried to play the DVD using vlc.  This caused X to lock up and the
>> kernel to report a crash.
> [...]
>> Before the crash, the VGA output would flicker a lot
[...]
>> [250593.916039] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer 
>> elapsed... GPU hung
>
> Thanks.  I like to imagine this was fixed by (kernel or userspace :/)
> changes in later squeeze point releases.  Do you still experience it?

Ping.  Do you still have this hardware?  (If life is just busy, that's
fine, but if there's not much chance of making progress in the future,
we'd naturally like to know.)



-- 
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/20111017095009.ga22...@elie.hsd1.il.comcast.net

Processed: Re: i915: X locks up when trying to play DVD on Thinkpad X40

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 587355 + moreinfo
Bug #587355 [linux-2.6] i915: X locks up when trying to play DVD on Thinkpad X40
Added tag(s) moreinfo.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
587355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587355
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.131884553325227.transcr...@bugs.debian.org

Bug#587355: i915: X locks up when trying to play DVD on Thinkpad X40

[Petter Reinholdtsen]

[Jonathan Nieder]
> Hi again,

Hi.  Sorry for the lack of response.  Real life kept me busy.

> Ping.  Do you still have this hardware?  (If life is just busy, that's
> fine, but if there's not much chance of making progress in the future,
> we'd naturally like to know.)

I still have the hardware, in fact it is my DVD player, and the problem
is no longer present in my daily use.  I am using the kernel
2.6.35~rc6-1~experimental.1 and the crash do not happen there.  I test
with version 2.6.32-38 from squeeze when I get home.

Now it only crashes when I enable the external VGA output while VLC is
starting, which I try to remember to avoid. :)

Happy hacking,
-- 
Petter Reinholdtsen



-- 
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/2flpqhw7xam@diskless.uio.no

Processed: Re: i915: X locks up when trying to play DVD on Thinkpad X40

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 587355 - moreinfo
Bug #587355 [linux-2.6] i915: X locks up when trying to play DVD on Thinkpad X40
Removed tag(s) moreinfo.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
587355: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=587355
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.131884629329184.transcr...@bugs.debian.org

Bug#587355: i915: X locks up when trying to play DVD on Thinkpad X40

[Jonathan Nieder]

Petter Reinholdtsen wrote:

> I still have the hardware, in fact it is my DVD player, and the problem
> is no longer present in my daily use.  I am using the kernel
> 2.6.35~rc6-1~experimental.1 and the crash do not happen there.  I test
> with version 2.6.32-38 from squeeze when I get home.

Thanks, Petter!  That's good to hear.

> Now it only crashes when I enable the external VGA output while VLC is
> starting, which I try to remember to avoid. :)

Hm.  Are there any GPU hangs, oopses, or other weird symptoms
associated to that?



-- 
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/20111017102000.gd22...@elie.hsd1.il.comcast.net

Bug#594923: noflushd: Noflushd causes flush- processes to eat all CPU

[Jonathan Nieder]

tags 594923 + patch moreinfo
quit

Hi,

Jonathan Nieder wrote:
> Daniel Kobras wrote:

>> now I can
>> reproduce the problem. It's not the fsync(), actually, but but the stopping 
>> of
>> the pdflush daemon that makes the flush-: kernel threads enter 
>> a
>> busy loop (spinning in bdi_writeback_task()). It can be triggered as simple 
>> as:
>>
>>  echo 0 > /proc/sys/vm/dirty_writeback_centisecs
>>
>> (Use echo 500 > /proc/sys/vm/dirty_writeback_centisecs to restore a sane
>> behaviour.) Suspending pdflush activity this way used to work before. Now it
>> seems to be interpreted as a zero wait time between iterations in the flush
>> threads. Thus, I'd say this is a regression in the kernel.
[...]
> It seems to have been fixed in sid by the combination of commits
>
> - v2.6.35-rc1~442^2~17 (writeback: fixups for !dirty_writeback_centisecs,
>   2010-05-21)
> - v2.6.35-rc1~442^2~56 (writeback: disable periodic old data writeback
>   for !dirty_writeback_centisecs, 2010-05-17)
>
> The latter of the two was cherry-picked as part of v2.6.32.16.  (Maybe
> the regression was introduced by v2.6.32-rc1~733^2~4, "writeback:
> switch to per-bdi threads for flushing data", 2009-09-09.)

Ping.  Did you get a chance to try the latest kernel from squeeze?



-- 
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/20111017112117.ga26...@elie.hsd1.il.comcast.net

Processed: Re: noflushd: Noflushd causes flush- processes to eat all CPU

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 594923 + patch moreinfo
Bug #594923 [linux-2.6] Zero writeback interval sends flush processes into busy 
loop
Added tag(s) moreinfo and patch.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
594923: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=594923
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.131885057216952.transcr...@bugs.debian.org

Processed: Re: xserver-xorg-input-synaptics: Touchpad left and right physical buttons send only button2 events instead of left and right clicks as expected

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> # Jonathan Nieder wrote:
> # > Cyril Brulebois wrote:
> #
> # >> Thanks, Tayroni.
> # >>
> # >> As you can see, LeftBtn+RightBtn is sent every time, so that's not a
> # >> bug on the X side, rather on the kernel side. Reassigning there.
> # >
> # > Thanks for a clear report.  Basic questions:
> tags 613074 + moreinfo
Bug #613074 [src:linux-2.6] xserver-xorg-input-synaptics: Touchpad left and 
right physical buttons send only button2 events instead of left and right 
clicks as expected
Added tag(s) moreinfo.
>
End of message, stopping processing here.

Please contact me if you need assistance.
-- 
613074: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613074
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.131885191523674.transcr...@bugs.debian.org

Bug#639505: Samsung N150 can reboot on waking from hibernation unless ath9k unloaded

[Jonathan Nieder]

Hi Sergei,

Jonathan Nieder wrote:

> If you get a chance to test hibernation without unloading the
[ath9k]
> module on the latest kernel from sid or squeeze, that would be
> welcome.

Ping?  It would be nice to get this working reliably out of the
box.

If you can reproduce it with a 3.x kernel from sid or experimental
(the only other packages from outside squeeze that would be needed to
test are linux-base and initramfs-tools), then we can report this
upstream and get help that way; and if this is already fixed in a 3.x
kernel, we can look for the patch that fixed it and try applying it
to squeeze.

Thanks a lot for your help.
Jonathan



-- 
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/20111017114959.ga26...@elie.hsd1.il.comcast.net

Bug#611750: Asus EeePC resume from hibernation fails

[Jonathan Nieder]

tags 611750 + moreinfo
quit

Hi again,

Jonathan Nieder wrote:
> Gerald Turner wrote:

>> I've upgraded to 2.6.32-31 some weeks ago and have noticed that the
>> problem still exists, resume doesn't fail every time, so this afternoon
>> I'm trying a more thorough examination.
> [...]
>>   For the first 10 consecutive suspend/resume cycles I had nothing but
>>   an empty gnome desktop and gnome-terminal running.  Then I added
>>   pidgin and ekiga.  At cycle 15 I fired up emacs.  At cycle 20 I
>>   launched a handful of random gnome utilities (gcalctool, gconf-editor,
>>   gucharmap, nautilus, file-roller, palimpsest, gnome-dictionary).  The
>>   25th resume failed.
>>
>> Could it be memory related?
[...]
>  - Does backing out the patch "x86, hotplug: Use mwait to offline a
>processor, fix the legacy case" that Frédéric mentioned[1] help?

I have no reason to believe it would (except that Frédéric also uses
an EeePC), but just in case, 2.6.32-36 has that patch backed out.  So
results from testing with a recent squeeze kernel would be interesting.



--
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/20111017115438.ga26...@elie.hsd1.il.comcast.net

Processed: Re: Asus EeePC resume from hibernation fails

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 611750 + moreinfo
Bug #611750 [linux-2.6] [regression] Asus EeePC: resume from hibernate fails 
when memory is scarce
Added tag(s) moreinfo.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
611750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=611750
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.131885251227748.transcr...@bugs.debian.org

Bug#618279: linux-image-2.6.32-5-686.deb: WIFI Usb adapter REALTEK RTL8188S not work

[Jonathan Nieder]

tags 618279 + moreinfo
quit

Hi again,

Jonathan Nieder wrote:
> Jean Pierre Hoareau wrote:

>> This week i try this USB Wifi Key under WHEEZE (kernel 2.6.32.5.686.deb)
>> and SID (2.6.37-2.686.deb) and i get the same problem.
[...]
> Do I understand correctly?  If so, please test a recent kernel (ideally
> v3.1-rc2 or later from upstream[1]), get an iw event log[2], and
> describe the symptoms to de...@driverdev.osuosl.org, cc-ing Larry
> Finger  and 618...@bugs.debian.org.

Ping.  Do you still have this hardware?  Were you able to try the
tests described above?

Nowadays the 3.1 rc kernels are available from experimental[3] so
it should be possible to try this with a packaged kernel (no need to
roll your own).

In suspense,
Jonathan

> [1] See 
> http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package
> [2] http://linuxwireless.org/en/users/Documentation/Reporting_bugs
[3] http://wiki.debian.org/DebianExperimental



-- 
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/20111017120851.ga27...@elie.hsd1.il.comcast.net

Processed: Re: linux-image-2.6.32-5-686.deb: WIFI Usb adapter REALTEK RTL8188S not work

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 618279 + moreinfo
Bug #618279 [linux-2.6] linux-image-2.6.32-5-686.deb: WIFI Usb adapter REALTEK 
RTL8188S not work
Added tag(s) moreinfo.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
618279: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=618279
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.13188550966892.transcr...@bugs.debian.org

Bug#619049: i915: Hangcheck timer elapsed... GPU hung

[Jonathan Nieder]

tags 619049 + moreinfo
quit

Jonathan Nieder wrote:

> Sorry for the long silence.  Can you reproduce this with the kernel
> from sid?  If so, please report this upstream, following the
> instructions from ,
> and let us know the bug number so we can track it.

Ping.  There have been a number of possibly relevant changes recently
in the Intel kernel driver, so it would be useful to see how a more
recent kernel behaves.



-- 
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/20111017121821.ga27...@elie.hsd1.il.comcast.net

Processed: Re: i915: Hangcheck timer elapsed... GPU hung

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 619049 + moreinfo
Bug #619049 [linux-2.6] i915: Hangcheck timer elapsed... GPU hung
Added tag(s) moreinfo.
> quit
Stopping processing here.

Please contact me if you need assistance.
-- 
619049: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619049
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.13188553908698.transcr...@bugs.debian.org

Re: Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Otavio Salvador]

On Fri, Oct 14, 2011 at 07:07, Marc Haber
 wrote:
...
> this is a regression from 6.0.2.1 to 6.0.3.
>
> The IBM HS12 blade server has a Broadcom network chip:
>
> 04:04.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme 5714S 
> Gigabit Ethernet [14e4:1669] (rev a3)
> 04:04.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme 5714S 
> Gigabit Ethernet [14e4:1669] (rev a3)
...
>
> Manually running modprobe -r tg3, modprobe tg3 on a shell allows the
> installation to continue. The squeeze OS installed by the installer
> has working network immediaely.
>
> With a 6.0.2.1 amd64 netinstall CD, things are just fine.
...

It does seem to be a kernel issue so I reassigned it according.

-- 
Otavio Salvador                             O.S. Systems
E-mail: ota...@ossystems.com.br  http://www.ossystems.com.br
Mobile: +55 53 9981-7854              http://projetos.ossystems.com.br


--
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/CAP9ODKrtEnWGSYwGE+yB5KHhO2WASyHA2opQVg9aufrR1U=y...@mail.gmail.com

Processed: reassign 645308 to linux-2.6

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 645308 linux-2.6
Bug #645308 [debian-installer] tg3 broken for NetXtreme 5714S in squeeze 6.0.3 
installer
Bug reassigned from package 'debian-installer' to 'linux-2.6'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645308
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.131885731918278.transcr...@bugs.debian.org

Bug#607574: linux-image-2.6.32-5-686: wastes > 8s of boot time on something USB related that fails

[Jonathan Nieder]

Version: 3.1.0~rc4-1~experimental.1

Jonathan Nieder wrote:
> Mario wrote:

>> Version: 2.6.32-29
[...]
>> [7.808651] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on 
>> minor 0
>> [   16.409864] 
>> /build/buildd-linux-2.6_2.6.32-29-i386-Of6Yt1/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/hid/usbhid/hid-core.c:
>>  usb_submit_urb(ctrl) failed
>> [   16.410069] generic-usb 0003:1C4F:0002.0002: timeout initializing reports
> [...]
>> Bus 004 Device 002: ID 1c4f:0002 SiGma Micro 

Should be fixed by v3.1-rc4~47^2^2 (HID: usbhid: Add support for SiGma
Micro chip, 2011-08-23).  Mario, can you confirm[1]?  Greg et al, does
this patch look like a reasonable candidate for the linux-2.6.32.y
tree?

-- >8 --
From: Jeremiah Matthey 
Date: Tue, 23 Aug 2011 09:44:30 +0200
Subject: HID: usbhid: Add support for SiGma Micro chip

commit f5e4282586dc0c9dab8c7d32e6c43aa07f68586b upstream.

Patch to add SiGma Micro-based keyboards (1c4f:0002) to hid-quirks.

These keyboards dont seem to allow the records to be initialized, and hence a
timeout occurs when the usbhid driver attempts to initialize them. The patch
just adds the signature for these keyboards to the hid-quirks list with the
setting HID_QUIRK_NO_INIT_REPORTS. This removes the 5-10 second wait for the
timeout to occur.

Signed-off-by: Jeremiah Matthey 
Signed-off-by: Jiri Kosina 
Signed-off-by: Jonathan Nieder 
---
[1] by testing the kernel from experimental[3], or even better, by building
a 2.6.32.y kernel with this patch applied[2]
[2] 
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-kernel-org-package
[3] http://wiki.debian.org/DebianExperimental

 drivers/hid/hid-ids.h   |3 +++
 drivers/hid/usbhid/hid-quirks.c |1 +
 2 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/drivers/hid/hid-ids.h b/drivers/hid/hid-ids.h
index aef92bbe2cd5..216b285b67f1 100644
--- a/drivers/hid/hid-ids.h
+++ b/drivers/hid/hid-ids.h
@@ -389,6 +389,9 @@
 #define USB_VENDOR_ID_SAMSUNG  0x0419
 #define USB_DEVICE_ID_SAMSUNG_IR_REMOTE0x0001
 
+#define USB_VENDOR_ID_SIGMA_MICRO  0x1c4f
+#define USB_DEVICE_ID_SIGMA_MICRO_KEYBOARD 0x0002
+
 #define USB_VENDOR_ID_SONY 0x054c
 #define USB_DEVICE_ID_SONY_VAIO_VGX_MOUSE  0x024b
 #define USB_DEVICE_ID_SONY_PS3_CONTROLLER  0x0268
diff --git a/drivers/hid/usbhid/hid-quirks.c b/drivers/hid/usbhid/hid-quirks.c
index 64c5dee27106..08a02abfca91 100644
--- a/drivers/hid/usbhid/hid-quirks.c
+++ b/drivers/hid/usbhid/hid-quirks.c
@@ -65,6 +65,7 @@ static const struct hid_blacklist {
{ USB_VENDOR_ID_WISEGROUP_LTD, USB_DEVICE_ID_SMARTJOY_DUAL_PLUS, 
HID_QUIRK_NOGET | HID_QUIRK_MULTI_INPUT },
{ USB_VENDOR_ID_WISEGROUP_LTD2, USB_DEVICE_ID_SMARTJOY_DUAL_PLUS, 
HID_QUIRK_NOGET | HID_QUIRK_MULTI_INPUT },
 
+   { USB_VENDOR_ID_SIGMA_MICRO, USB_DEVICE_ID_SIGMA_MICRO_KEYBOARD, 
HID_QUIRK_NO_INIT_REPORTS },
{ 0, 0 }
 };
 
-- 
1.7.7




-- 
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/20111017125708.ga1...@elie.hsd1.il.comcast.net

Bug#607574: marked as done (linux-image-2.6.32-5-686: wastes > 8s of boot time on something USB related that fails)

[Debian Bug Tracking System]

Your message dated Mon, 17 Oct 2011 07:57:09 -0500
with message-id <20111017125708.ga1...@elie.hsd1.il.comcast.net>
and subject line Re: linux-image-2.6.32-5-686: wastes > 8s of boot time on 
something USB related that fails
has caused the Debian Bug report #607574,
regarding linux-image-2.6.32-5-686: wastes > 8s of boot time on something USB 
related that fails
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
607574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=607574
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.32-29
Severity: normal


[   16.409864] 
/build/buildd-linux-2.6_2.6.32-29-i386-Of6Yt1/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/hid/usbhid/hid-core.c:
 usb_submit_urb(ctrl) failed

note the time on the previous log messages



-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-29) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Dec 10 16:12:40 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 root=UUID- ro quiet

** Not tainted

** Kernel log:
[2.201885] scsi2 : SCSI emulation for USB Mass Storage devices
[2.202131] usbcore: registered new interface driver usb-storage
[2.202136] USB Mass Storage support registered.
[2.202394] usb-storage: device found at 2
[2.202398] usb-storage: waiting for device to settle before scanning
[2.312330] ata1.00: n_sectors mismatch 39062500 != 39102336
[2.312335] ata1.00: new n_sectors matches native, probably late HPA unlock, 
n_sectors updated
[2.329309] ata1.00: configured for UDMA/100
[2.329320] ata1: EH complete
[2.329663] sd 0:0:0:0: [sda] 39102336 512-byte logical blocks: (20.0 
GB/18.6 GiB)
[2.329933] sda: detected capacity change from 200 to 20020396032
[2.329942]  sda: sda1 sda2
[2.372787] sd 0:0:0:0: [sda] Attached SCSI disk
[2.432691] sr0: scsi3-mmc drive: 24x/24x cd/rw xa/form2 cdda tray
[2.432699] Uniform CD-ROM driver Revision: 3.20
[2.432895] sr 1:0:0:0: Attached scsi CD-ROM sr0
[2.447078] sd 0:0:0:0: Attached scsi generic sg0 type 0
[2.448100] sr 1:0:0:0: Attached scsi generic sg1 type 5
[2.624034] usb 4-1: new low speed USB device using uhci_hcd and address 2
[2.682281] PM: Starting manual resume from disk
[2.682289] PM: Resume from partition 8:2
[2.682292] PM: Checking hibernation image.
[2.682543] PM: Error -22 checking image file
[2.682547] PM: Resume from disk failed.
[2.724026] kjournald starting.  Commit interval 5 seconds
[2.724046] EXT3-fs: mounted filesystem with ordered data mode.
[2.840323] usb 4-1: New USB device found, idVendor=1c4f, idProduct=0002
[2.840330] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[2.840336] usb 4-1: Product: USB Keykoard
[2.840340] usb 4-1: Manufacturer: USB
[2.840525] usb 4-1: configuration #1 chosen from 1 choice
[3.080022] usb 4-2: new low speed USB device using uhci_hcd and address 3
[3.255274] usb 4-2: New USB device found, idVendor=046d, idProduct=c016
[3.255281] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[3.255286] usb 4-2: Product: Optical USB Mouse
[3.255290] usb 4-2: Manufacturer: Logitech
[3.255461] usb 4-2: configuration #1 chosen from 1 choice
[5.037672] udev[240]: starting version 164
[5.565664] input: PC Speaker as /devices/platform/pcspkr/input/input0
[5.642637] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[5.751548] processor LNXCPU:00: registered as cooling_device0
[5.855502] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1
[5.855526] ACPI: Power Button [VBTN]
[5.855803] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[5.855812] ACPI: Power Button [PWRF]
[5.862743] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[5.914946] intel_rng: FWH not detected
[5.987405] parport_pc 00:08: reported by Plug and Play ACPI
[5.987463] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE]
[6.252700] dcdbas dcdbas: Dell Systems Management Base Driver (version 
5.6.0-3.2)
[6.381631] usbcore: registered new interface driver hiddev
[6.396638] input: USB USB Keykoard as 
/devices/pci:00/:00:1d.2/usb4/4-1/4-1:1.0/input/input3
[6.397771] generic-usb 0003:1C4F:0002.0001: input,hidraw0: USB HID v1.10 
Keyboard [USB USB Keykoard] on usb-:00:1d.2-1/input0
[6.685861] i801_smbus :00:1f.3: PCI INT B -> GSI 17 (level, low) -> IRQ 
17

Bug#644948: nfs-common: Wrong uid/gid with latest version using NFSv4

[Stephan Windmüller]

> After upgrade to nfs-common 1:1.2.5-2 I noticed that uid/gid's are 
> displayed as 'nobody' and 'nogroup' respectively. This is the case 
> checking with both Nautilus and terminal. Downgrading to 1:1.2.4-1
> from Testing fixes the problem.

Same problem here, but with 1:1.2.2-4 from squeeze.

- Stephan



signature.asc
Description: OpenPGP digital signature

Bug#625727: linux-image-2.6.38-2-amd64: Console turns black during boot, backlight turns off

[Jonathan Nieder]

Hi Andreas,

Andreas Horter wrote:

> dist-upgrading testing installed
> linux-image-2.6.38-2-amd64_2.6.38-3_amd64.deb. Now when I boot up the
> system the screen turns black after the initial 6 lines 
[...]
> and I can log into gdm 'in the dark' but the screen stays black. Even
> switching to a different console via Ctrl-Alt-F1 doesn't change
> anything. 
> When I reboot into the old linux-image-2.6.32-5-amd64 everything works
> again.

Sorry for the very slow response.

> So I tried different kernel versions from snapshot.debian.org and the
> last one working is
> linux-image-2.6.35-trunk-amd64_2.6.35-1~experimental.3_amd64.deb. The
> kernel versions linux-image-2.6.36-trunk-amd64 and
> linux-image-2.6.37-2-amd64 show the same behaviour as 2.6.38. 

Very nice.  One option would be to bisect[1] between those to find the
individual patch that caused the problem.

But first, let's get this upstream.  That means:

 1. Test a 3.x kernel, from sid or experimental
 2. Follow instructions at
http://intellinuxgraphics.org/how_to_report_bug.html
 3. Let us know the bug number so we can track it

Thanks much!
Jonathan

[1] http://git-core.googlecode.com/git-history/html/git-bisect-lk2009.html



-- 
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/20111017123109.ga32...@elie.hsd1.il.comcast.net

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Marc Haber]

On Mon, Oct 17, 2011 at 10:53:51AM -0200, Otavio Salvador wrote:
> On Fri, Oct 14, 2011 at 07:07, Marc Haber
>  wrote:
> ...
> > this is a regression from 6.0.2.1 to 6.0.3.
> >
> > The IBM HS12 blade server has a Broadcom network chip:
> >
> > 04:04.0 Ethernet controller [0200]: Broadcom Corporation NetXtreme 5714S 
> > Gigabit Ethernet [14e4:1669] (rev a3)
> > 04:04.1 Ethernet controller [0200]: Broadcom Corporation NetXtreme 5714S 
> > Gigabit Ethernet [14e4:1669] (rev a3)
> ...
> >
> > Manually running modprobe -r tg3, modprobe tg3 on a shell allows the
> > installation to continue. The squeeze OS installed by the installer
> > has working network immediaely.
> >
> > With a 6.0.2.1 amd64 netinstall CD, things are just fine.
> ...
> 
> It does seem to be a kernel issue so I reassigned it according.

Does the installer use a different kernel from what actually gets used
in the installed system?

Why was a new tg3 introduced in a point release kernel in the first
place?

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062



-- 
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/20111017134430.gj22...@torres.zugschlus.de

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Jonathan Nieder]

Marc Haber wrote:

> Why was a new tg3 introduced in a point release kernel in the first
> place?

  * tg3,broadcom: Backport changes up to Linux 2.6.38 (Closes: #627705)
- Add support for BCM5717, BCM5719, BCM57765
- Add support for BCM50610M and BCM5241 PHYs
- Fix support for BCM5755



-- 
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/20111017135137.gb4...@elie.hsd1.il.comcast.net

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Marc Haber]

[keeping debian-kernel]

On Mon, Oct 17, 2011 at 08:51:37AM -0500, Jonathan Nieder wrote:
> Marc Haber wrote:
> 
> > Why was a new tg3 introduced in a point release kernel in the first
> > place?
> 
>   * tg3,broadcom: Backport changes up to Linux 2.6.38 (Closes: #627705)
> - Add support for BCM5717, BCM5719, BCM57765
> - Add support for BCM50610M and BCM5241 PHYs
> - Fix support for BCM5755

Why was this done in a point release? I always thought that Debian
stable means Debian stable. Other packages are forbidden to introduce
new functionality into a stable release as well.

In this case, the change has introduced a (bad!) regression. This must
not happen.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062



-- 
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/20111017135457.gl22...@torres.zugschlus.de

Bug#645366: [fuse-devel] Hang and suspend failure after FUSE server killed (3.1-rc7)

[Miklos Szeredi]

Ben Hutchings  writes:

> On Fri, 2011-10-14 at 22:52 +, brian m. carlson wrote:
>> Package: linux-2.6
>> Version: 3.1.0~rc7-1~experimental.1
>> Severity: normal
>> 
>> This morning I was backing up my laptop to another computer via sshfs
>> (and fuse).  The afio archiver was writing to this sshfs-mounted
>> location.  I decided to abort the operation with Ctrl-C, which caused
>> the sshfs mount to become unmounted; however, afio was apparently not
>> affected by the SIGINT (probably because processes in disk IO are
>> unkillable).
>> 
>> Several hours later, I attempted to suspend my computer and it failed to
>> do so. The kernel log (attached) indicated that the afio process from
>> hours before was preventing the suspend.  Since processes waiting on
>> disk IO are unkillable (IMO a bug) and the underlying device to which
>> afio was writing was long gone, I was forced to reboot the machine in
>> order to get it to suspend.  If I had not noticed that the machine had
>> failed to suspend, it could have stayed running in my bag and seriously
>> overheated.
>
> This seems to be a bug in FUSE.  Is this known about?  If not, could
> someone look into this?

It's a bug in the fuse-freezer interaction.  Yes, it is known.

Before suspending the machine all userspace task are frozen, which means
the freezer will wait until they exit the kernel (i.e. finish any system
calls).  If some task does not exit the kernel within a predefined time
then the freezer will give up and not let the machine be suspended.

Lets say task A is executing a system call that depends on task B to
finish.  In this case task B must not be frozen until task A is frozen
otherwise the suspend will be unsuccessful.

One often proposed solution is to try to order the freezing of userspace
tasks and leave "task B's" last.  The problem is that it's impossible to
know which task depends on which other task to be able to make progress.
For example the kernel could guess that "sshfs" is probably "task B"
type because it's reading and writing /dev/fuse.  But it's not going to
guess that a certain "ssh" process is also a "task B".  This is also
complicated by the fact that a task could be "task A" and "task B" at
the same time...

Another suggested solution is to allow freezing of tasks that are
waiting for a fuse reply.  E.g:

  http://thread.gmane.org/gmane.linux.power-management.general/25926

However that would only fix a subset of the problems as described in
that thread.  Also it would disrupt the operation of the freezer in
cases where it actually needs the userspace task to be out of the kernel
(cgroup freezer).

We discussed this issue recently with Rafael Wysocki, the power
management maintainer, and came to the conclusion that the best solution
is to allow suspend to go ahead even if some tasks are not frozen.  But
we need to be careful about only allowing tasks to remain unfrozen if
they are known to be outside of driver code.  For example we can mark
the task safe to suspend if it's inside any "well behaved" filesystem
(block filesystems, fuse, NFS, etc).

One important implementation question is: how to do this marking of
"safe" tasks without adding too much runtime and maintenance overhead to
the kernel.

Ideas, patches are welcome.

Thanks,
Miklos

>
> Ben.
>
> [...]
>> Oct 14 12:50:07 lakeview kernel: [129960.588174] INFO: task afio:22818 
>> blocked for more than 120 seconds.
>> Oct 14 12:50:07 lakeview kernel: [129960.588182] "echo 0 > 
>> /proc/sys/kernel/hung_task_timeout_secs" disables this message.
>> Oct 14 12:50:07 lakeview kernel: [129960.588188] afioD 
>> 880086e20300 0 22818  1 0x0084
>> Oct 14 12:50:07 lakeview kernel: [129960.588199]  880086e20300 
>> 0086 8800065c1848 81037a71
>> Oct 14 12:50:07 lakeview kernel: [129960.588210]  88003687f120 
>> 00012f00 881effd8 881effd8
>> Oct 14 12:50:07 lakeview kernel: [129960.588220]  00012f00 
>> 880086e20300 00012f00 00012f00
>> Oct 14 12:50:07 lakeview kernel: [129960.588231] Call Trace:
>> Oct 14 12:50:07 lakeview kernel: [129960.588246]  [] ? 
>> __wake_up_common+0x41/0x78
>> Oct 14 12:50:07 lakeview kernel: [129960.588257]  [] ? 
>> _raw_spin_lock_irqsave+0x9/0x25
>> Oct 14 12:50:07 lakeview kernel: [129960.588282]  [] ? 
>> fuse_request_send+0x1a2/0x251 [fuse]
>> Oct 14 12:50:07 lakeview kernel: [129960.588291]  [] ? 
>> wake_up_bit+0x23/0x23
>> Oct 14 12:50:07 lakeview kernel: [129960.588316]  [] ? 
>> fuse_flush+0xca/0xfe [fuse]
>> Oct 14 12:50:07 lakeview kernel: [129960.588322]  [] ? 
>> filp_close+0x3b/0x6a
>> Oct 14 12:50:07 lakeview kernel: [129960.588326]  [] ? 
>> sys_close+0x87/0xc4
>> Oct 14 12:50:07 lakeview kernel: [129960.588331]  [] ? 
>> system_call_fastpath+0x16/0x1b
> [...]



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

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Ben Hutchings]

On Mon, 2011-10-17 at 15:54 +0200, Marc Haber wrote:
> [keeping debian-kernel]
> 
> On Mon, Oct 17, 2011 at 08:51:37AM -0500, Jonathan Nieder wrote:
> > Marc Haber wrote:
> > 
> > > Why was a new tg3 introduced in a point release kernel in the first
> > > place?
> > 
> >   * tg3,broadcom: Backport changes up to Linux 2.6.38 (Closes: #627705)
> > - Add support for BCM5717, BCM5719, BCM57765
> > - Add support for BCM50610M and BCM5241 PHYs
> > - Fix support for BCM5755
> 
> Why was this done in a point release? I always thought that Debian
> stable means Debian stable. Other packages are forbidden to introduce
> new functionality into a stable release as well.

Wrong, new hardware support has been allowed for many releases.

> In this case, the change has introduced a (bad!) regression. This must
> not happen.

I didn't see any report from you after the (repeated) calls for testing
the point release.

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Bug#645366: [fuse-devel] Hang and suspend failure after FUSE server killed (3.1-rc7)

[Ben Hutchings]

On Mon, 2011-10-17 at 16:22 +0200, Miklos Szeredi wrote:
> Ben Hutchings  writes:
> 
> > On Fri, 2011-10-14 at 22:52 +, brian m. carlson wrote:
> >> Package: linux-2.6
> >> Version: 3.1.0~rc7-1~experimental.1
> >> Severity: normal
> >> 
> >> This morning I was backing up my laptop to another computer via sshfs
> >> (and fuse).  The afio archiver was writing to this sshfs-mounted
> >> location.  I decided to abort the operation with Ctrl-C, which caused
> >> the sshfs mount to become unmounted; however, afio was apparently not
> >> affected by the SIGINT (probably because processes in disk IO are
> >> unkillable).
> >> 
> >> Several hours later, I attempted to suspend my computer and it failed to
> >> do so. The kernel log (attached) indicated that the afio process from
> >> hours before was preventing the suspend.  Since processes waiting on
> >> disk IO are unkillable (IMO a bug) and the underlying device to which
> >> afio was writing was long gone, I was forced to reboot the machine in
> >> order to get it to suspend.  If I had not noticed that the machine had
> >> failed to suspend, it could have stayed running in my bag and seriously
> >> overheated.
> >
> > This seems to be a bug in FUSE.  Is this known about?  If not, could
> > someone look into this?
> 
> It's a bug in the fuse-freezer interaction.  Yes, it is known.
[...]

But the FUSE server was already killed; shouldn't that cause outstanding
requests to fail immediately?

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Bug#645366: [fuse-devel] Hang and suspend failure after FUSE server killed (3.1-rc7)

[Miklos Szeredi]

Ben Hutchings  writes:

> On Mon, 2011-10-17 at 16:22 +0200, Miklos Szeredi wrote:
>> Ben Hutchings  writes:
>> 
>> > On Fri, 2011-10-14 at 22:52 +, brian m. carlson wrote:
>> >> Package: linux-2.6
>> >> Version: 3.1.0~rc7-1~experimental.1
>> >> Severity: normal
>> >> 
>> >> This morning I was backing up my laptop to another computer via sshfs
>> >> (and fuse).  The afio archiver was writing to this sshfs-mounted
>> >> location.  I decided to abort the operation with Ctrl-C, which caused
>> >> the sshfs mount to become unmounted; however, afio was apparently not
>> >> affected by the SIGINT (probably because processes in disk IO are
>> >> unkillable).
>> >> 
>> >> Several hours later, I attempted to suspend my computer and it failed to
>> >> do so. The kernel log (attached) indicated that the afio process from
>> >> hours before was preventing the suspend.  Since processes waiting on
>> >> disk IO are unkillable (IMO a bug) and the underlying device to which
>> >> afio was writing was long gone, I was forced to reboot the machine in
>> >> order to get it to suspend.  If I had not noticed that the machine had
>> >> failed to suspend, it could have stayed running in my bag and seriously
>> >> overheated.
>> >
>> > This seems to be a bug in FUSE.  Is this known about?  If not, could
>> > someone look into this?
>> 
>> It's a bug in the fuse-freezer interaction.  Yes, it is known.
> [...]
>
> But the FUSE server was already killed; shouldn't that cause outstanding
> requests to fail immediately?

Yes it should.

But my guess is that the server wasn't actually killed, otherwise the
archiver program would have just gotten ENOTCONN errors and exited.  The
fact that "afio" had hung means that sshfs also hung.  We can't prove or
disprove this without a process listing.

The reason for sshfs hanging could be due to one of the bugs that were
fixed in the sshfs-2.3 version.  E.g.:

* Fix cleanup when ssh connection is terminated.  This prevents
sshfs hanging when the server is rebooted, for example.

Thanks,
Miklos



-- 
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/87obxfllrs@tucsk.pomaz.szeredi.hu

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Marc Haber]

On Mon, Oct 17, 2011 at 03:29:53PM +0100, Ben Hutchings wrote:
> I didn't see any report from you after the (repeated) calls for testing
> the point release.

Why should I be doing your job? Making sure that features added during
a stable release don't break existing stuff is a package maintainers'
job.

Greetings
Marc

-- 
-
Marc Haber | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."Winona Ryder | Fon: *49 621 31958061
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 31958062



-- 
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/20111017144825.gm22...@torres.zugschlus.de

Bug#639505: Samsung N150 can reboot on waking from hibernation unless ath9k unloaded

[Jonathan Nieder]

Sergei Stolyarov wrote:

> Hi, I almost forgot about this bug.
>
> I've installed latest sid 3.0 kernel (linux-image-3.0.0-2-686-pae
> 3.0.0-5) and it's working fine without the module unload workaround,
> no reboot after resume for 10 hibernate-resume cycles.

Thanks, Sergei.  Weird --- so this means

2.6.32-31:  intermittent reboots on resume
3.0.0-1 (?):intermittent reboots on resume, unless
module unload workaround applied
3.0.0-5:no problem

There were some ath9k fixes in the 3.0.y stable series, but it's not
obvious which would have cured these symptoms.  The most dramatic
change (ath9k: skip ->config_pci_powersave() if PCIe port has ASPM
disabled, 2011-07-29) is supposed to have fixed a regression
introduced in v2.6.35, which is way later than v2.6.32 (and the patch
causing it does not seem to have been backported).  I guess it would
be useful to know what chipset you use.

Please attach output from

/usr/share/bug/linux-image-$(uname -r)/script 3>&1

and "dmesg" output from right after booting.



-- 
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/20111017145850.gc5...@elie.hsd1.il.comcast.net

Bug#639505: Samsung N150 can reboot on waking from hibernation unless ath9k unloaded

[Sergei Stolyarov]

Hi, I almost forgot about this bug.

I've installed latest sid 3.0 kernel (linux-image-3.0.0-2-686-pae
3.0.0-5) and it's working fine without the module unload workaround,
no reboot after resume for 10 hibernate-resume cycles.

On Mon, Oct 17, 2011 at 6:49 PM, Jonathan Nieder  wrote:
> Hi Sergei,
>
> Jonathan Nieder wrote:
>
>> If you get a chance to test hibernation without unloading the
> [ath9k]
>> module on the latest kernel from sid or squeeze, that would be
>> welcome.
>
> Ping?  It would be nice to get this working reliably out of the
> box.
>
> If you can reproduce it with a 3.x kernel from sid or experimental
> (the only other packages from outside squeeze that would be needed to
> test are linux-base and initramfs-tools), then we can report this
> upstream and get help that way; and if this is already fixed in a 3.x
> kernel, we can look for the patch that fixed it and try applying it
> to squeeze.
>
> Thanks a lot for your help.
> Jonathan
>



-- 
Sergei Stolyarov



--
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/CA+dMb88xNC7iwT3r9qW1329ocJcOn=0z93g008vffiud5uh...@mail.gmail.com

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Ben Hutchings]

On Mon, Oct 17, 2011 at 04:48:25PM +0200, Marc Haber wrote:
> On Mon, Oct 17, 2011 at 03:29:53PM +0100, Ben Hutchings wrote:
> > I didn't see any report from you after the (repeated) calls for testing
> > the point release.
> 
> Why should I be doing your job? Making sure that features added during
> a stable release don't break existing stuff is a package maintainers'
> job.
 
You seem to have forgotten that Debian is a community distribution,
lacking a hardware compatibility test lab.  I personally don't own
*any* devices supported by the tg3 driver.

I did also request help from the upstream driver developers at
Broadcom, but didn't hear anything back.

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/20111017160812.gl3...@decadent.org.uk

Processed: Re: [pkg-cryptsetup-devel] Bug#639876: cryptsetup: add usb modules to initramfs

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reassign 639876 initramfs-tools
Bug #639876 [cryptsetup] cryptsetup: add usb modules to initramfs
Bug reassigned from package 'cryptsetup' to 'initramfs-tools'.
Bug No longer marked as found in versions cryptsetup/2:1.3.0-3.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
639876: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639876
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.1318870921750.transcr...@bugs.debian.org

Bug#607574: linux-image-2.6.32-5-686: wastes > 8s of boot time on something USB related that fails

[Greg KH]

On Mon, Oct 17, 2011 at 07:57:09AM -0500, Jonathan Nieder wrote:
> Version: 3.1.0~rc4-1~experimental.1
> 
> Jonathan Nieder wrote:
> > Mario wrote:
> 
> >> Version: 2.6.32-29
> [...]
> >> [7.808651] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on 
> >> minor 0
> >> [   16.409864] 
> >> /build/buildd-linux-2.6_2.6.32-29-i386-Of6Yt1/linux-2.6-2.6.32/debian/build/source_i386_none/drivers/hid/usbhid/hid-core.c:
> >>  usb_submit_urb(ctrl) failed
> >> [   16.410069] generic-usb 0003:1C4F:0002.0002: timeout initializing 
> >> reports
> > [...]
> >> Bus 004 Device 002: ID 1c4f:0002 SiGma Micro 
> 
> Should be fixed by v3.1-rc4~47^2^2 (HID: usbhid: Add support for SiGma
> Micro chip, 2011-08-23).  Mario, can you confirm[1]?  Greg et al, does
> this patch look like a reasonable candidate for the linux-2.6.32.y
> tree?

Why wouldn't it also go into the 3.0-stable tree?

thanks,

greg k-h



-- 
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/20111017183023.gc14...@suse.de

Bug#645695: linux-image-3.0.0-1-amd64: Oops with Linux 3.0.0 and radeon driver: shmem_truncate_range

[Paul Menzel]

Package: linux-2.6
Version: 3.0.0-3
Severity: normal
Forwarded: https://bugs.freedesktop.org/show_bug.cgi?id=41503


Dear Debian folks,


having a lot of windows open using the Awesome window manager [4] the X
server crashed printing the following to the monitor. Please see the
image [7] for the complete message.

Pid: 1503, comm: Xorg Tainted: G   C 3.0.0-1-amd64 #1 LENOVO 
INVALID/Bali

[…]

Process Xorg (pid: 1503, threadinfo 88010c208000, task 
88011950d790
Stack:
[…]
Call Trace:
pagevec_move_tail+0x30/0x30
shmem_evict_inode+0x58/0xea
evict+0x7b/0x119
dentry_kill+0x136/0x155
dput+0xdb/0xea
fput+0x17b/0x1a2
remove_vma+0x3d/0x71
do_munmap+0x2da/0x2f3
sys_shmdt+0x9a/0x127
system_call_fastpath+0x16/0x1b

Code: 00 00 00 00 00 48 8b 94 24 a0 00 00 00 48 8d 45 28 48 ff 44 24 10 
48 c7 44 24 50 00 00 …
RIP […] shmem_truncate_range+0x45c/0x6a1
 RSP 

Unfortunately for debugging this issue this is the first time it
happened and the issue is not reproducible.

Debian Wheezy/testing is running on this system with Linux 3.0.0-3 [5]
and the (non-free) firmware for the graphics card.

I had reported that message to the list dri-devel [1] and because of the
Linux Kernel Bugzilla [2] being down I reported it to freedesktop.org’s
Bugzilla as #41503 [3]. Michael Dänzer suggests that nothing points to
drm/radeon as the cause and therefore I am assigning this issue to the
Linux kernel package.

Please note that the report is written after a restart so the Linux
kernel log and other information probably do not contain any information
regarding the crash and the screenshot taken from the Linux kernel dump
is the only thing available [7].

Suggestions on how to debug this issue or going forward with this bug
would be greatly appreciated.


Thanks,

Paul


[1] http://lists.freedesktop.org/archives/dri-devel/2011-October/015011.html
[2] https://bugzilla.kernel.org/
[3] https://bugs.freedesktop.org/show_bug.cgi?id=41503
[4] http://awesome.naquadah.org/
[5] 
http://packages.debian.org/changelogs/pool/main/l/linux-2.6/linux-2.6_3.0.0-3/changelog#version3.0.0-3
[6] 
http://packages.debian.org/changelogs/pool/non-free/f/firmware-nonfree/firmware-nonfree_0.33/changelog#version0.33
[7] https://bugs.freedesktop.org/attachment.cgi?id=52032

-- Package-specific info:
** Version:
Linux version 3.0.0-1-amd64 (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc 
version4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:21:11 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-3.0.0-1-amd64 root=/dev/mapper/levi--civita--1-root ro quiet

** Tainted: C (1024)
 * Module from drivers/staging has been loaded.

** Kernel log:
[   41.860123] [drm]   DDC: 0x7f68 0x7f68 0x7f6c 0x7f6c 0x7f70 0x7f70 0x7f74 
0x7f74
[   41.860125] [drm]   Encoders:
[   41.860127] [drm] LCD1: INTERNAL_UNIPHY2
[   41.860129] [drm] Connector 1:
[   41.860130] [drm]   VGA
[   41.860132] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 
0x7e4c
[   41.860134] [drm]   Encoders:
[   41.860135] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[   41.880048] usb 2-2: new high speed USB device number 2 using ehci_hcd
[   41.915318] [drm] Radeon display connector LVDS-1: Found valid EDID
[   41.925560] [drm] Radeon display connector VGA-1: No monitor connected or 
invalid EDID
[   41.925606] [drm] radeon: power management initialized
[   42.017421] usb 2-2: New USB device found, idVendor=090c, idProduct=37b1
[   42.017425] usb 2-2: New USB device strings: Mfr=1, Product=2, SerialNumber=2
[   42.017428] usb 2-2: Product: Lenovo EasyCamera
[   42.017430] usb 2-2: Manufacturer: Image Processor
[   42.017432] usb 2-2: SerialNumber: Lenovo EasyCamera
[   42.232943] usbcore: registered new interface driver uas
[   42.295437] Linux media interface: v0.10
[   42.326684] Linux video capture interface: v2.00
[   42.337509] Initializing USB Mass Storage driver...
[   42.337596] usbcore: registered new interface driver usb-storage
[   42.337598] USB Mass Storage support registered.
[   42.354956] uvcvideo: Found UVC 1.00 device Lenovo EasyCamera (090c:37b1)
[   42.361496] input: Lenovo EasyCamera as 
/devices/pci:00/:00:13.2/usb2/2-2/2-2:1.0/input/input10
[   42.361552] usbcore: registered new interface driver uvcvideo
[   42.361554] USB Video Class driver (v1.1.0)
[   42.383187] [drm] fb mappable at 0xE0142000
[   42.383190] [drm] vram apper at 0xE000
[   42.383192] [drm] size 4325376
[   42.383194] [drm] fb depth is 24
[   42.383195] [drm]pitch is 5632
[   42.383286] fbcon: radeondrmfb (fb0) is primary device
[   42.383657] scsi2 : usb-storage 1-3:1.0
[   42.383785] usbcore: registered new interface driver ums-realtek
[   42.392136] usb 5-3: new full speed USB device number 2 using ohci_hcd
[   42.583164] usb 5-3: New USB device found, idVendor=0a5c, idProduct=2150
[   42.583168] usb 5-3: New USB device strings: Mfr=1, Prod

Bug#625922: SATA devices get reset without real hardware failure

[Javier Ortega Conde (Malkavian)]

This bug (in general, not just this on this web) have been in GNU/Linux since 
a long time with various disks, mainboards, SATA controllers, distros and 
kernels (maybe since changes after 2.6.24).

In https://bugzilla.redhat.com/show_bug.cgi?id=684599  David Zeuthen says 
"it's most probably caused by this commit 
http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=560de575148b7efda3b34a7f7073abd483c5f08e
 
"

Possible workarounds readed to this bug: 
-1: Add "libata.atapi_passthru16=0" to the kernel boot options (because some 
devices may not support 16-byte ATA commands) ( 
https://bugzilla.redhat.com/show_bug.cgi?id=684599 )
-2: (Same as 1) Add options libata atapi_passthru16=0 to 
/etc/modprobe.d/modprobe.conf and add FILES="/etc/modprobe.d/modprobe.conf" to 
/etc/mkinitcpio.conf ( https://bbs.archlinux.org/viewtopic.php?pid=895404 )
-3: Somebody called Fujisan said in 2009 "adding 'acpi=off noapic' to the 
kernel in /etc.grub.conf seems to have solved the problem for me"  ( 
https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=462425 ).  Raman 
Gupta  and Andreas M. Kirchwitz say in other forums that adding 'acpi=off' 
doesn't work ( https://bugzilla.redhat.com/show_bug.cgi?id=549981 )
-4: (Similar to 3) Completely disable ACPI in mainboard BIOS. ( 
http://lists.debian.org/debian-user/2010/01/msg00023.html )
-5: Gaetan Cambier says "add the option line to grub to disable ncq : 
'libata.force=noncq' for me, with this, i have no froze". ( 
https://bugzilla.redhat.com/show_bug.cgi?id=549981 ). Others reply that it 
doesn't work for them. PsYcHoK9 sys it works for him but John Doe replies that 
not for him ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285892 ).
-6: Reartes Guillermo says "booting with the kernel parameter: pcie_aspm=off ? 
For me it worked (nvidia)". Raman Gupta replies that "I tried this and it did 
not fix the problem." ( https://bugzilla.redhat.com/show_bug.cgi?id=549981 )
-7: A. Mani says "For the SB600 controller, the right thing to do is to 
restrict all drives to 1.5Gbps by jumpers or with a boot option."  Raman Gupta 
replies "I also tried this -- but with this setting all drives attached to my 
Marvell controller could not even be started by the kernel -- permanent 
"failed to IDENTIFY" errors." ( 
https://bugzilla.redhat.com/show_bug.cgi?id=549981 )
-8: DjznBR (djzn-br) says he have trying some things WITHOUT success it and 
finally one that works. Doesn't work: TURNED HDPARM OFF, CHANGED CABLE, 
EXPERIMENTED AHCI & RAID MODES, DISABLED NCQ, COMPILED KERNEL WITH 
CONFIG_SATA_PMP DISABLED, TRYING NOW LIBATA.FORCE=1.5GBPS, changed the cables 
to different routes... SATA1 -> SATA2 SATA2 -> SATA3  Works (but still 
gives "softreset failed (device not ready)"  messages in dmesg and afterwards 
recover without data loss) :  Added option for kernel in grub configuration 
"libata.noacpi=1". Also says "libata.force=norst ... prevents soft and hard 
link resettings. If you have that switch on, when this bug comes up, there is 
a system lock down (because obviously the kernel prevented the soft & hard 
resetting." ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285892 )


Same problem in my old PC/Server Pentium II MMX with Debian 6.0.3 (stable) 
with kernel 2.6.32-5-686 and libata version 3.00 in an "IBM-DTLA-305010" 10Gb 
IDE disk (configured by debian as sda) in an old mainboard . No RAID used, but 
only soft reset, and no hard reset, so I don't lose data. Could send logs, but 
I think they wouldn't give any more info.

Same problem in my desktop PC every 2 or 3 months in Debian testing with 
kernels 3.0.0-1-amd64, 3.0.0-rc2-amd64, 2.6.39-2-amd64, 2.6.39-amd64, 
2.6.38-2-amd64, 2.6.38-amd64 and maybe others older, and libata 3.00 in two 
Seagate 7200.11 "ST3500320AS" 500Gb SATA2 disks (with last firmware) from a 
RAID10. Fortunately the other two Western Digital "WDC WD1002FAEX-00Z3A0" 1Tb 
SATA3 disks don't fail, but I have to reboot and re-add disk to reconstruct 
raid. Could send logs, but I think they wouldn't give any more info.

Possibly these are the same bug: #539059, #603061, #524876

Same bug in other distros and kernels:
-Archlinux with udev-165 and udev-166: 
https://bbs.archlinux.org/viewtopic.php?pid=895404
-Fedora with kernel 2.6.38-0.rc8.git0.1.fc15.x86_64 and udev-166 in a DVD 
reader: https://bugzilla.redhat.com/show_bug.cgi?id=684599
-Fedora 13 with kernel 2.6.33.8-149.fc13.i686.PAE or Fedora 13 64bit on a Mac 
Mini
-Fedora 14 with kernels 2.6.31.6-166.fc12@x86_64, 2.6.32.11-99.fc12.x86_64, 
2.6.35.9-64.fc14.x86_64, 2.6.35.10-72.fc14.i686 and 2.6.35.10-74.fc14.x86_64 
and 2.6.35.11-83.fc14.x86_64 and 2.6.35.14-95.fc14.x86_64: 
https://bugzilla.redhat.com/show_bug.cgi?id=549981
-Fedora 15 (updated from Fedora 14): 
https://bugzilla.redhat.com/show_bug.cgi?id=549981
-Centos5.5-x64 with kernel 2.6.18-194-x64: 
https://bugzilla.redhat.com/show_bug.cgi?id=549981
-RHEL5 with vanilla kernel 2.6.37.3: 
https://bugzilla.redhat.com/show_bu

Bug#645308: tg3 broken for NetXtreme 5714S in squeeze 6.0.3 installer

[Ben Hutchings]

Now, let me try to understand this regression.

The kernel log you sent shows the interface being brought up and down
several times in quick succession:

First time:
[  224.139579] tg3 :04:04.0: irq 30 for MSI/MSI-X
[  224.174436] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  224.185365] tg3 :04:04.0: eth0: Link is up at 1000 Mbps, full duplex
[  224.185367] tg3 :04:04.0: eth0: Flow control is off for TX and off for RX
[  224.194074] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[  224.226364] tg3 :04:04.0: PME# enabled

Second time:
[  225.417581] tg3 :04:04.0: irq 30 for MSI/MSI-X
[  225.451422] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  225.463365] tg3 :04:04.0: eth0: Link is up at 1000 Mbps, full duplex
[  225.463368] tg3 :04:04.0: eth0: Flow control is off for TX and off for RX

Third time:
[  227.045107] tg3 :04:04.0: irq 30 for MSI/MSI-X
[  227.062399] ADDRCONF(NETDEV_UP): eth0: link is not ready
[  227.091050] tg3 :04:04.0: eth0: Link is up at 1000 Mbps, full duplex
[  227.091053] tg3 :04:04.0: eth0: Flow control is off for TX and off for RX
[  227.092177] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Could you test whether the same problem occurs if you do something
similar after reloading the driver:

rmmod tg3
modprobe tg3
ip link set eth0 up ; sleep 0.1 ; ip link set eth0 down
ip link set eth0 up ; sleep 0.1 ; ip link set eth0 down
ip link set eth0 up

If that does reproduce the problem, could you also try the same with
Linux 3.0 on this system?

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Processed: found 645308 in 2.6.32-38

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> found 645308 2.6.32-38
Bug #645308 [linux-2.6] tg3 broken for NetXtreme 5714S in squeeze 6.0.3 
installer
There is no source info for the package 'linux-2.6' at version '2.6.32-38' with 
architecture ''
Unable to make a source version for version '2.6.32-38'
Bug Marked as found in versions 2.6.32-38.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645308
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.131890114721215.transcr...@bugs.debian.org

Processed: forcibly merging 641243 645071

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forcemerge 641243 645071
Bug#641243: linux: kernel failure at startup, but boots
Bug#645071: linux-image-2.6.32-5-686-bigmem: init crashes during runlevel switch
Forcibly Merged 641243 645071.

> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645071
641243: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641243
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.131890150623250.transcr...@bugs.debian.org

Bug#645071: WARNING in tty_ldisc_reinit

[Ben Hutchings]

Дмитрий Матросов wrote:
> I try to compile with printk() instead of printk_ratelimited() in your
> patch, and it's succeeded. Then i install it with

Sorry, I didn't notice that would need to be changed.  Thanks for fixing
that yourself!

> # dpkg -i   ./linux-image-2.6.32-5-686-bigmem_2.6.32-38a~test_i386.deb
> # dpkg --configure --force-depends-version  linux-image-2.6.32-5-686-bigmem
> 
> and then try to reproduce this bug. Here is the result:
> 
> [   65.162361] apm: BIOS not found.
> [   65.276280] [drm] nouveau :01:00.0: nouveau_channel_free: freeing fifo 
> 2
> [   84.368180] tty_ldisc_reinit: refcount of  is still 2
[...]
> I suppose, that result of previous attempt is not very useful, because
> something is missed in the output (after "of" word). So, i rewrite
> your patch a little:
> [..]
> +   printk(KERN_DEBUG "%s: refcount of %p (%s, num=%d, mag=%d,
> flags=%d) is still %d\n",
> +   __func__,
> +   tty->ldisc->ops, tty->ldisc->ops->name, 
> tty->ldisc->ops->num,
> tty->ldisc->ops->magic, tty->ldisc->ops->flags,
> +   atomic_read(&tty->ldisc->users));
> [..]

"%ps" should have resulted in printing the symbol name for the structure
that the argument points to.  I don't know why that didn't work.

Anyway, Jiri, this should be the information you wanted way back in
:

> [   83.736104] tty_ldisc_reinit: refcount of c13c7878 (n_tty, num=0, 
> mag=21507, flags=0) is still 2

You can find more explanation of when this happens in the bug log at
.

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Processed: tagging 645071

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 645071 - moreinfo
Bug #645071 [linux-2.6] linux-image-2.6.32-5-686-bigmem: init crashes during 
runlevel switch
Bug #641243 [linux-2.6] linux: kernel failure at startup, but boots
Removed tag(s) moreinfo.
Removed tag(s) moreinfo.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645071: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645071
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.131890182924486.transcr...@bugs.debian.org

Bug#625922: SATA devices get reset without real hardware failure

[Ben Hutchings]

On Tue, 2011-10-18 at 00:37 +0200, Javier Ortega Conde (Malkavian)
wrote:
> This bug (in general, not just this on this web) have been in GNU/Linux since 
> a long time with various disks, mainboards, SATA controllers, distros and 
> kernels (maybe since changes after 2.6.24).

Just because you see the same error messages, that does not mean you are
seeing the same bug.

> In https://bugzilla.redhat.com/show_bug.cgi?id=684599  David Zeuthen says 
> "it's most probably caused by this commit 
> http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h=560de575148b7efda3b34a7f7073abd483c5f08e
>  
> "

So that's a bug in some drives, though we need to work around it.

> Possible workarounds readed to this bug: 
> -1: Add "libata.atapi_passthru16=0" to the kernel boot options (because some 
> devices may not support 16-byte ATA commands) ( 
> https://bugzilla.redhat.com/show_bug.cgi?id=684599 )
> -2: (Same as 1) Add options libata atapi_passthru16=0 to 
> /etc/modprobe.d/modprobe.conf and add FILES="/etc/modprobe.d/modprobe.conf" 
> to 
> /etc/mkinitcpio.conf ( https://bbs.archlinux.org/viewtopic.php?pid=895404 )

OK.

> -3: Somebody called Fujisan said in 2009 "adding 'acpi=off noapic' to the 
> kernel in /etc.grub.conf seems to have solved the problem for me"  ( 
> https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=462425 ).  Raman 
> Gupta  and Andreas M. Kirchwitz say in other forums that adding 'acpi=off' 
> doesn't work ( https://bugzilla.redhat.com/show_bug.cgi?id=549981 )
> -4: (Similar to 3) Completely disable ACPI in mainboard BIOS. ( 
> http://lists.debian.org/debian-user/2010/01/msg00023.html )

These are workarounds for bugs in IRQ routing on some motherboards.

They are also outdated advice.  10 years ago when both ACPI and the APIC
architecture were quite new, there were a lot of bugs in both BIOS and
kernel support for them.  It was therefore sensible to try disabling it
when a new system seemed unstable.  Today, this is not the case.

> -5: Gaetan Cambier says "add the option line to grub to disable ncq : 
> 'libata.force=noncq' for me, with this, i have no froze". ( 
> https://bugzilla.redhat.com/show_bug.cgi?id=549981 ). Others reply that it 
> doesn't work for them. PsYcHoK9 sys it works for him but John Doe replies 
> that 
> not for him ( https://bugs.launchpad.net/ubuntu/+source/linux/+bug/285892 ).

Not even the same symptoms.

> -6: Reartes Guillermo says "booting with the kernel parameter: pcie_aspm=off 
> ? 
> For me it worked (nvidia)". Raman Gupta replies that "I tried this and it did 
> not fix the problem." ( https://bugzilla.redhat.com/show_bug.cgi?id=549981 )

This is a workaround for a controller or chipset bug.

[...]
> Same problem in my old PC/Server Pentium II MMX with Debian 6.0.3 (stable) 
> with kernel 2.6.32-5-686 and libata version 3.00 in an "IBM-DTLA-305010" 10Gb 
> IDE disk (configured by debian as sda) in an old mainboard . No RAID used, 
> but 
> only soft reset, and no hard reset, so I don't lose data. Could send logs, 
> but 
> I think they wouldn't give any more info.
> 
> Same problem in my desktop PC every 2 or 3 months in Debian testing with 
> kernels 3.0.0-1-amd64, 3.0.0-rc2-amd64, 2.6.39-2-amd64, 2.6.39-amd64, 
> 2.6.38-2-amd64, 2.6.38-amd64 and maybe others older, and libata 3.00 in two 
> Seagate 7200.11 "ST3500320AS" 500Gb SATA2 disks (with last firmware) from a 
> RAID10. Fortunately the other two Western Digital "WDC WD1002FAEX-00Z3A0" 1Tb 
> SATA3 disks don't fail, but I have to reboot and re-add disk to reconstruct 
> raid. Could send logs, but I think they wouldn't give any more info.
[...]

Use reportbug to open a *separate* bug report for *each* of these
systems.  Do send the logs.  Please do not try to find connections with
other bug reports.

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Processed: tagging 645695

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> tags 645695 + unreproducible
Bug #645695 [linux-2.6] linux-image-3.0.0-1-amd64: Oops with Linux 3.0.0 and 
radeon driver: shmem_truncate_range
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645695: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645695
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.131890676514136.transcr...@bugs.debian.org

Bug#645695: linux-image-3.0.0-1-amd64: Oops with Linux 3.0.0 and radeon driver: shmem_truncate_range

[Ben Hutchings]

On Mon, 2011-10-17 at 22:57 +0200, Paul Menzel wrote:
[...]
> having a lot of windows open using the Awesome window manager [4] the X
> server crashed printing the following to the monitor. Please see the
> image [7] for the complete message.
[...]
> Unfortunately for debugging this issue this is the first time it
> happened and the issue is not reproducible.
> 
> Debian Wheezy/testing is running on this system with Linux 3.0.0-3 [5]
> and the (non-free) firmware for the graphics card.
> 
> I had reported that message to the list dri-devel [1] and because of the
> Linux Kernel Bugzilla [2] being down I reported it to freedesktop.org’s
> Bugzilla as #41503 [3]. Michael Dänzer suggests that nothing points to
> drm/radeon as the cause and therefore I am assigning this issue to the
> Linux kernel package.

It is certainly a kernel bug, whether it is related to the radeon driver
or not.

> Please note that the report is written after a restart so the Linux
> kernel log and other information probably do not contain any information
> regarding the crash and the screenshot taken from the Linux kernel dump
> is the only thing available [7].
> 
> Suggestions on how to debug this issue or going forward with this bug
> would be greatly appreciated.

The function in which the crash occurred has been largely rewritten for
Linux 3.1, so if the bug is there then it has quite possible been fixed
by that.  Since you say this is not reproducible, I don't think there's
much point bothering the upstream maintainers to chase this down now.

I'll leave the bug report open in case you or anyone else finds a way to
reproduce it.

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Bug#645695: linux-image-3.0.0-1-amd64: Oops with Linux 3.0.0 and radeon driver: shmem_truncate_range

[Ben Hutchings]

For future reference, here's what I got from the oops message.

The IP is in the inlined call to list_add() in this block:

if (subdir && !offset && upper_limit-idx >= ENTRIES_PER_PAGE) {
if (needs_lock) {
spin_lock(needs_lock);
dir[diroff] = NULL;
spin_unlock(needs_lock);
punch_lock = NULL;
} else
dir[diroff] = NULL;
nr_pages_to_free++;
list_add(&subdir->lru, &pages_to_free);
}

The register and stack dump shows:

needs_lock = 0
diroff = 0
nr_pages_to_free = 2
subdir = 0x010101500149447c

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Bug#645589: linux-image-3.0.0-2-amd64: sky2 rx errors on 3.0, 2.6.32 works

[Ben Hutchings]

On Mon, 2011-10-17 at 10:40 +0300, Antti Salmela wrote:
> Package: linux-2.6
> Version: 3.0.0-5
> Severity: normal
> 
> 
> sky2 loses packets on 3.0 (-3 and -5) and 3.1-rc7, 2.6.32-38 and
> setting interface to promiscuous works.
> 
> [   60.118244] sky2 :02:00.0: eth0: rx error, status 0xb92100 length 185
> [   62.664370] sky2 :02:00.0: eth0: rx error, status 0x602100 length 96
> [   63.370051] sky2 :02:00.0: eth0: rx error, status 0x422100 length 66
> [   63.714672] sky2 :02:00.0: eth0: rx error, status 0x722100 length 114
> [   64.513458] device eth0 entered promiscuous mode

It looks like this is a bug in accounting of VLAN tags, though I don't
see what difference promiscuous mode should make.

The log messages show that status has the VLAN flag (bit 13) set and the
length field (bits 16:28) equals the length passed into sky2_receive(),
but that function expects the length field to be greater by VLAN_HLEN.

This device is:

[...]
> 02:00.0 Ethernet controller [0200]: Marvell Technology Group Ltd. 88E8053 
> PCI-E Gigabit Ethernet Controller [11ab:4362] (rev 19)
>   Subsystem: ASUSTeK Computer Inc. Marvell 88E8053 Gigabit Ethernet 
> controller PCIe (Asus) [1043:8142]
>   Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
> Stepping- SERR- FastB2B- DisINTx+
>   Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-  SERR-Latency: 0, Cache Line Size: 16 bytes
>   Interrupt: pin A routed to IRQ 43
>   Region 0: Memory at cdefc000 (64-bit, non-prefetchable) [size=16K]
>   Region 2: I/O ports at c800 [size=256]
>   Expansion ROM at cdec [disabled] [size=128K]
>   Capabilities: 
>   Kernel driver in use: sky2
[...]

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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

Processed: bug 645589 is forwarded to net...@vger.kernel.org

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> forwarded 645589 net...@vger.kernel.org
Bug #645589 [linux-2.6] linux-image-3.0.0-2-amd64: sky2 rx errors on 3.0, 
2.6.32 works
Set Bug forwarded-to-address to 'net...@vger.kernel.org'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
645589: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=645589
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.131890851423375.transcr...@bugs.debian.org

Bug#645052: kernel only recognizes 32G of memory

[Ben Hutchings]

On Thu, 2011-10-13 at 07:05 +0100, Ian Campbell wrote:
> On Thu, 2011-10-13 at 03:27 +0100, Ben Hutchings wrote:
> > On Wed, 2011-10-12 at 14:58 +0100, Ian Campbell wrote:
> > > On Wed, 2011-10-12 at 14:11 +0100, Ben Hutchings wrote:
> > > > On Wed, 2011-10-12 at 08:26 +0100, Ian Campbell wrote:
> > > > > On Wed, 2011-10-12 at 08:46 +0300, Dmitry Musatov wrote:
> > > > > >  The config option XEN_MAX_DOMAIN_MEMORY controls how much memory a
> > > > > > Xen instance is seeing. The default for 64bit is 32GB, which is the
> > > > > > reason that m2.4xlarge Amazon EC2 instances only report this amount 
> > > > > > of
> > > > > > memory.
> > > > > >  Please set this limit to 70GB as there is a known restriction for
> > > > > > t1.micro instances at about 80GB.
> > > > > >  Similar bug exists and Ubuntu where it's already fixed
> > > > > > (https://bugs.launchpad.net/ubuntu/+source/linux-ec2/+bug/667796)
> > > > > 
> > > > > Is this the sort of change we can consider making in a stable update?
> > > > > I'm not at all sure, although my gut feeling is that it would be safe.
> > > > [...]
> > > > 
> > > > I think so.  But what is the trade-off?  There must be some reason why
> > > > this isn't set to however many TB the kernel can support.
> > > 
> > > It effects the amount of space set aside for the P2M table (the mapping
> > > of physical to machine addresses). In the kernel in Squeeze this space
> > > is statically reserved in BSS so increasing it will waste some more
> > > memory, according to the Kconfig comment it is 1 page per GB.
> > > 
> > > In a more up to date kernel the space comes from BRK and is reclaimed if
> > > it is not used, MAX_DOMAIN_MEMORY was bumped to default to 128G in the
> > > same change.
> > 
> > How intrusive is the change?  Could we reasonably backport it?
> 
> It was 58e05027b530 "xen: convert p2m to a 3 level tree" which I think
> is too big. IIRC there was a bunch of subsequent fixups to it as well,
> it was quite a subtle change.

You didn't directly answer the questions, but that sounds like 'fairly'
and 'no'.

If I understand correctly, the memory cost of expanding the table to
cover 70GB is (70GB - 32GB) * 4KB / 1GB = 156KB.  Is that right?

Since we don't have a specific flavour to support EC2, and since some
people like to run domains with much less memory, I'm inclined to say
that this is 'wontfix' for squeeze.  But I'm not sure just how small
they are likely to be (while still running Debian).  Maybe the cost
isn't that significant.

Ben.

-- 
Ben Hutchings
No political challenge can be met by shopping. - George Monbiot


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