Bug#705586: linux-image-3.2.0-4-amd64: ath9k_htc fails to initialize with tl-wn722n; regression vs sqeeze backport

2013-04-17 Thread Steven Hystad 
Package: src:linux
Version: 3.2.41-2
Severity: normal
Tags: lfs

Dear Maintainer,

I have a few TL-WN722N usb wireless networking devices that I use on a few
systems running Dabian Sqweeze backports. On testing Weezy the driver
encounters an error and doesn't complete setting up the wlan interface.

I did try compiling and installing a standard kernel bassed on the config
included in Debian, however I encountered issues with the graphics and didn't
test the networking.

In the data below you'll see that the builtin wireless device does startup
correctly, but the usb wireless device, while it is recognised correctly, fails
after inserting firmware.



-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-4-amd64 
root=UUID=73b6745d-4f8c-4a0d-99d9-daf57a03d58c ro quiet

** Not tainted

** Kernel log:
[6.246762] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[6.246767] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.246771] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[6.246775] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[6.246779] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.246783] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.363416] Console: switching to colour frame buffer device 170x48
[6.375744] fb0: inteldrmfb frame buffer device
[6.375748] drm: registered panic notifier
[6.399125] ACPI Warning: _BQC returned an invalid level (20110623/video-486)
[6.399958] acpi device:43: registered as cooling_device2
[6.419734] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
[6.419854] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[6.419893] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[6.420417] xhci_hcd :00:14.0: setting latency timer to 64
[6.420427] xhci_hcd :00:14.0: xHCI Host Controller
[6.420448] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 3
[6.420575] xhci_hcd :00:14.0: cache line size of 64 is not supported
[6.420590] xhci_hcd :00:14.0: irq 16, io mem 0xf7e0
[6.420681] xhci_hcd :00:14.0: irq 43 for MSI/MSI-X
[6.420770] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[6.420775] usb usb3: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[6.420779] usb usb3: Product: xHCI Host Controller
[6.420783] usb usb3: Manufacturer: Linux 3.2.0-4-amd64 xhci_hcd
[6.420787] usb usb3: SerialNumber: :00:14.0
[6.423064] xHCI xhci_add_endpoint called for root hub
[6.423070] xHCI xhci_check_bandwidth called for root hub
[6.423140] hub 3-0:1.0: USB hub found
[6.423153] hub 3-0:1.0: 4 ports detected
[6.423294] xhci_hcd :00:14.0: xHCI Host Controller
[6.423309] xhci_hcd :00:14.0: new USB bus registered, assigned bus 
number 4
[6.423345] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[6.423350] usb usb4: New USB device strings: Mfr=3, Product=2, 
SerialNumber=1
[6.423354] usb usb4: Product: xHCI Host Controller
[6.423358] usb usb4: Manufacturer: Linux 3.2.0-4-amd64 xhci_hcd
[6.423362] usb usb4: SerialNumber: :00:14.0
[6.423816] xHCI xhci_add_endpoint called for root hub
[6.423820] xHCI xhci_check_bandwidth called for root hub
[6.423882] hub 4-0:1.0: USB hub found
[6.423894] hub 4-0:1.0: 4 ports detected
[6.439650] snd_hda_intel :00:1b.0: irq 44 for MSI/MSI-X
[6.439677] snd_hda_intel :00:1b.0: setting latency timer to 64
[6.520314] Linux media interface: v0.10
[6.546460] Linux video capture interface: v2.00
[6.552987] uvcvideo: Found UVC 1.00 device ASUS USB2.0 WebCam (058f:a014)
[6.556181] input: ASUS USB2.0 WebCam as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/input/input8
[6.556452] usbcore: registered new interface driver uvcvideo
[6.556457] USB Video Class driver (1.1.1)
[7.163293] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
[7.163449] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input9
[7.163697] input: HDA Intel PCH Headphone as 
/devices/pci:00/:00:1b.0/sound/card0/input10
[9.041112] Adding 4076540k swap on /dev/sda3.  Priority:-1 extents:1 
across:4076540k 
[9.070759] EXT4-fs (sda2): re-mounted. Opts: (null)
[9.390715] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[9.690382] loop: module loaded
[   10.330795] FAT-fs (sda1): utf8 is not a recommended IO charset for FAT 
filesystems, filesystem will be case sensitive!
[   11.535254] RPC: Registered named UNIX socket transport module.
[   11.535259]

Bug#705586: Acknowledgement (linux-image-3.2.0-4-amd64: ath9k_htc fails to initialize with tl-wn722n; regression vs sqeeze backport)

2013-04-17 Thread Steven Hystad 
On Wed, 2013-04-17 at 08:36 +, Debian Bug Tracking System wrote:
> Thank you for filing a new Bug report with Debian.
> 
> This is an automatically generated reply to let you know your message
> has been received.
> 
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
> 
> As you requested using X-Debbugs-CC, your message was also forwarded to
>   steven.hys...@gmail.com
> (after having been given a Bug report number, if it did not have one).
> 
> Your message has been sent to the package maintainer(s):
>  Debian Kernel Team 
> 
> If you wish to submit further information on this problem, please
> send it to 705...@bugs.debian.org.
> 
> Please do not send mail to ow...@bugs.debian.org unless you wish
> to report a problem with the Bug-tracking system.
> 

Making a second attempt to use the kernel I compiled myself (linux
3.2.41) I can see that the same error occurs. I may test older versions
to see if I can get it to work.


-- 
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/1366188943.5160.6.camel@destruction.l

Bug#705336: linux - kvm clock wrong after resume from disk

2013-04-17 Thread Bastian Blank 
On Sun, Apr 14, 2013 at 10:02:23PM +0100, Ben Hutchings wrote:
> On Sat, 2013-04-13 at 11:24 +0200, Bastian Blank wrote:
> > Within kvm the clock is wrong after a resume from disk. This should be
> > fixed with b74f05d61b73af584d0c39121980171389ecfaaa.
> Looks like a more-or-less clean cherry-pick.  Please test and then
> commit it if it works.

Does not work.  Linux seems to not even detect it got suspended in any
way. At least there is nothing in the log about it, except for the
unstable tsc.  The patched function is only called from apm, acpi or
kexec wakeup.

Bastian

-- 
Change is the essential process of all existence.
-- Spock, "Let That Be Your Last Battlefield", stardate 5730.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/20130417090527.ga5...@waldi.eu.org

Bug#702880: Acknowledgement (linux-image-3.8-trunk-amd64: Suspend locks when the laptop lid is closed)

2013-04-17 Thread Fabian Greffrath 
I should add to that bug report that suspending and waking up works
perfectly fine if I manually invoke "sudo sudo pm-suspend
--quirk-s3-bios --quirk-s3-mode". The phrase "text mode" in PM-ACTION(8)
gave the final hint. However, I have no idea how the Gnome menu knew how
to invoke it with the right quirks, whereas the kernel had no idea when
I just closed the Lid...

 - Fabian


> when I am logged in into a Gnome session and close the lid of my
> laptop, the
> suspend process somehow hangs. It looks like it switched to VC1,
> because I can
> see some part of the boot log, but the computer is still on but
> unresponsive
> and the fan turns on high speed. However, when I suspend the system
> via the
> personal menu in the right corner of gnome-shell (hit Alt and click on
> "Switch
> off"), the system suspends and wakes up perfectly. I have to admit I
> am not
> perfectly sure where to file this bug, but since I am sure the kernel
> is
> involved, I am filing it here. ;)


-- 
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/1366194281.8788.6.camel@debian

Bug#704987: system freezes after hibernate/suspend

2013-04-17 Thread colliar 
On 16.04.2013 18:38, Ingo wrote:
> @ colliar
> 
> I just checked with your syslog and found that system has resumed from
> hibernate just a few minutes before the crash happened.
> 
> I did see also random cashes/freezes in Wheezy when system was suspended
> before (s2ram). Since I no longer use suspend all the troubles have gone
> away.
> 
> I must admit that this did not happen with early Wheezy kernels, but it
> shows up with latest kernels and also with any vanilla 3.4 kernel.
> 
> I really cannot decide the root cause of this observation, but I feel
> it's worth to test on your hardware without suspend/hibernate. My
> hardware is Ivy Bridge i5-3570k.


No, this was after a reboot !

> Apr 12 12:24:48 chaos kernel: [1.189157] PM: Hibernation image
> not present or could not be loaded.

> Apr 12 12:24:48 chaos kernel: [2.180228] device-mapper: ioctl:
> 4.22.0-ioctl (2011-10-19) initialised: dm-de...@redhat.com
> Apr 12 12:24:48 chaos kernel: [   18.393012] PM: Starting manual
> resume from disk
> Apr 12 12:24:48 chaos kernel: [   18.393090] PM: Hibernation image
> partition 254:2 present
> Apr 12 12:24:48 chaos kernel: [   18.393092] PM: Looking for
> hibernation image.
> Apr 12 12:24:48 chaos kernel: [   18.393453] PM: Image not found
> (code -22)
> Apr 12 12:24:48 chaos kernel: [   18.393455] PM: Hibernation image not
present or could not be loaded.

Mmh, the gap is strange. Have to recheck.

Any way, I did reproduce this several times in a row (e.g. reboot after
crash and crash again.

I have problems after suspend and hibernate from time to time but then
usually a restart of X (shortcut or restart of gdm3) solves the problem.

cu
Colliar




signature.asc
Description: OpenPGP digital signature

Bug#705579: please consider the kernel module dependencies

2013-04-17 Thread Bjørn Mork 
Harald Dunkel  writes:

> Package: initramfs-tools
> Version: 0.110
> Severity: wishlist
>
> It would be very nice if mkinitramfs considers the kernel
> module dependencies when creating the initrd. /lib/modules/\
> 3.8.?/modules.dep shows pretty clear that ehci-hcd depends
> upon ehci-pci, for example. See #700572.
>
> This would make initramfs-tools much more insusceptible to
> future changes in the module dependencies.

The idea is good, but the example is bad.  ehci-pci depends on ehci-hcd,
not the other way round.  So automatic dependency tracking would not
have bought you anything in this case.


bjorn@nemi:/tmp$ modinfo ehci-hcd ehci-pci
filename:   /lib/modules/3.9.0-rc5+/kernel/drivers/usb/host/ehci-hcd.ko
license:GPL
author: David Brownell
description:USB 2.0 'Enhanced' Host Controller (EHCI) Driver
depends:usbcore
intree: Y
vermagic:   3.9.0-rc5+ SMP mod_unload modversions 
parm:   log2_irq_thresh:log2 IRQ latency, 1-64 microframes (int)
parm:   park:park setting; 1-3 back-to-back async packets (uint)
parm:   ignore_oc:ignore bogus hardware overcurrent indications (bool)
filename:   /lib/modules/3.9.0-rc5+/kernel/drivers/usb/host/ehci-pci.ko
license:GPL
author: Alan Stern
author: David Brownell
description:EHCI PCI platform driver
alias:  pci:v104AdCC00sv*sd*bc*sc*i*
alias:  pci:v*d*sv*sd*bc0Csc03i20*
depends:usbcore,ehci-hcd
intree: Y
vermagic:   3.9.0-rc5+ SMP mod_unload modversions 



Bjørn


--
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/87zjwxuyqu@nemi.mork.no

Bug#705124: Info received (base: Filesystem corruption issue)

2013-04-17 Thread Ian Campbell 
On Tue, 2013-04-16 at 09:39 -0400, Anthony Sheetz wrote:
> 
> What does dom0 dmesg say about barriers on that
> device/filesystem?

> Nothing in dmesg about barriers on any file system. 'dmesg|grep
> barrier' returns nothing.  

I've just realised that the message in domU is from the blkfront driver,
so you wouldn't expect to see it in dom0. Also since it is not from the
filesystem it will not necessarily coincide with the filesystems use of
barriers, it'll just reflect that the device *could* do barriers.

To know if the filesystem is using barriers I think you have to look
in /proc/mounts.

Ian.


-- 
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/1366203424.25579.21.ca...@zakaz.uk.xensource.com

Bug#704242: Driver for PL-2303 HX not working

2013-04-17 Thread Johan Hovold 
On Wed, Apr 17, 2013 at 02:46:23PM +0200, Karsten Malcher wrote:
> Am 17.04.2013 13:31, schrieb Johan Hovold:
> > The logs there appear not to have debugging enabled in usb-serial core.
> > Please post the logs with debugging enabled in both modules to this
> > thread as well.
> 
> O.K. Nobody has requested this so far.
> So this time with both modules in debug-mode:
> 
> root@PC:# lsmod | grep usb
> usb_storage43870  0
> usbserial  32061  1 pl2303
> usbhid 36379  0
> hid81288  1 usbhid
> usbcore   128498  8 
> ehci_hcd,ohci_hcd,usbhid,usbserial,uas,usb_storage,pl2303
> usb_common 12354  1 usbcore
> scsi_mod  162372  6 libata,sd_mod,sr_mod,sg,uas,usb_storage
> 
> root@PC:# rmmod pl2303
> root@PC:# rmmod usbserial
> root@PC:# modprobe usbserial debug=1
> root@PC:# modprobe pl2303 debug=1
> 
> * Then i connected the adapter.
> * Connect with cutecom and a wired loop with 9600 baud.
> * Write "Test"
> * Close connection
> * Remove adapter
> 
> Logs attached.

The logs look incomplete. It's probably because they're flooded with
serial_write_room and chars_in_buffer messages.

Can you try to reproduce this on a later kernel (e.g. 3.8) which uses
dynamic debugging?

Can you minimise your test setup using a custom program which only opens
the device, initialises it, writes the four characters (e.g. "test")
and reads them back (over you hardwired loop) before closing the device
again? Make sure to verify it using a working device first.

Thanks,
Johan


-- 
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/20130417131343.GC25860@localhost

Bug#705618: flood of INFO: rcu_bh detected stall on CPU XX (t=0 jiffies)

2013-04-17 Thread Yaroslav Halchenko 
Package: src:linux
Version: 3.2.41-2
Severity: important

I have upgraded our nodes to wheezy recently and since then one of the
nodes periodically dumps to the log lengthy 

Apr 17 07:12:55 head8 kernel: [587397.860028] INFO: rcu_bh detected stall on 
CPU 26 (t=0 jiffies)
Apr 17 07:12:55 head8 kernel: [587397.860028] sending NMI to all CPUs:
Apr 17 07:12:55 head8 kernel: [587397.869946] NMI backtrace for cpu 1
...
Apr 17 07:12:57 head8 kernel: [587397.860028] NMI backtrace for cpu 26
Apr 17 07:13:02 head8 kernel: [587397.860028] CPU 26
Apr 17 07:13:02 head8 kernel: [587397.860028] Modules linked in: parport_pc 
ppdev lp parport bnep rfcomm bluetooth rfkill binfmt_misc fuse nfsd nfs nfs_acl 
auth_rpcgss fscache lockd sunrpc ipmi_si ipmi_devintf ipmi_msghandler 
e752x_edac loop bonding forcedeth sp5100_tco powernow_k8 mperf crc32c_intel 
ghash_clmulni_intel joydev evdev aesni_intel psmouse aes_x86_64 serio_raw 
aes_generic cryptd pcspkr i2c_piix4 amd64_edac_mod edac_mce_amd i2c_core 
k10temp edac_core fam15h_power button processor thermal_sys ext4 crc16 jbd2 
mbcache dm_mod usbhid hid sg sd_mod ata_generic crc_t10dif ohci_hcd ahci 
pata_atiixp libahci ehci_hcd libata usbcore igb scsi_mod usb_common dca [last 
unloaded: scsi_wait_scan]
Apr 17 07:13:02 head8 kernel: [587397.860028]
Apr 17 07:13:02 head8 kernel: [587397.860028] Pid: 306, comm: python /data/ac 
Not tainted 3.2.0-4-amd64 #1 Debian 3.2.41-2 Supermicro H8QG6/H8QG6
Apr 17 07:13:02 head8 kernel: [587397.860028] RIP: 0010:[]  
[] default_send_IPI_mask_sequence_phys+0x2b/0x6a
Apr 17 07:13:02 head8 kernel: [587397.860028] RSP: :884027c83df8  
EFLAGS: 0087
Apr 17 07:13:02 head8 kernel: [587397.860028] RAX: 884027cc RBX: 
0086 RCX: 001b
Apr 17 07:13:02 head8 kernel: [587397.860028] RDX: 001b RSI: 
0200 RDI: 0200
Apr 17 07:13:02 head8 kernel: [587397.860028] RBP: dc42 R08: 
 R09: 8168ef00
Apr 17 07:13:02 head8 kernel: [587397.860028] R10: 8880200978c0 R11: 
8880200978c0 R12: 0002
Apr 17 07:13:02 head8 kernel: [587397.860028] R13: 8168ef00 R14: 
001b R15: 8106bf3c
Apr 17 07:13:02 head8 kernel: [587397.860028] FS:  2b89229e70e0() 
GS:884027c8() knlGS:
Apr 17 07:13:02 head8 kernel: [587397.860028] CS:  0010 DS:  ES:  CR0: 
80050033
Apr 17 07:13:02 head8 kernel: [587397.860028] CR2: 15db1608 CR3: 
007020a29000 CR4: 000406e0
Apr 17 07:13:02 head8 kernel: [587397.860028] DR0:  DR1: 
 DR2: 
Apr 17 07:13:02 head8 kernel: [587397.860028] DR3:  DR6: 
0ff0 DR7: 0400
Apr 17 07:13:02 head8 kernel: [587397.860028] Process python /data/ac (pid: 
306, threadinfo 881020d8a000, task 880fe77ab7d0)
Apr 17 07:13:02 head8 kernel: [587397.860028] Stack:
Apr 17 07:13:02 head8 kernel: [587397.860028]  2710 
81620080 81620280 884027c83f50
Apr 17 07:13:02 head8 kernel: [587397.860028]  884027c8ea78 
81024bd2 884027c8ecb0 81095a94
Apr 17 07:13:02 head8 kernel: [587397.860028]  8880200978c0 
8880200978c0 0082 001a
Apr 17 07:13:02 head8 kernel: [587397.860028] Call Trace:
Apr 17 07:13:02 head8 kernel: [587397.860028]  
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
arch_trigger_all_cpu_backtrace+0x4d/0x7b
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
__rcu_pending+0x82/0x358
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
tick_nohz_handler+0xd0/0xd0
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
rcu_check_callbacks+0xaf/0xcc
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
update_process_times+0x31/0x63
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
tick_sched_timer+0x6a/0x90
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
__run_hrtimer+0xac/0x135
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
hrtimer_interrupt+0xd5/0x1af
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
call_softirq+0x1c/0x30
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
smp_apic_timer_interrupt+0x6f/0x82
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
apic_timer_interrupt+0x6e/0x80
Apr 17 07:13:02 head8 kernel: [587397.860028]  
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
system_call_fastpath+0x16/0x1b
Apr 17 07:13:02 head8 kernel: [587397.860028] Code: 41 56 49 83 ce ff 41 55 49 
89 fd 41 54 41 89 f4 55 48 c7 c5 42 dc 00 00 53 e8 77 ff ff ff 48 89 c3 eb 15 
4a 8b 04 f5 60 d9 68 81 <44> 89 e6 0f b7 7c 05 00 e8 7b ff ff ff 41 ff c6 be 00 
02 00 00
Apr 17 07:13:02 head8 kernel: [587397.860028] Call Trace:
Apr 17 07:13:02 head8 kernel: [587397.860028][] ? 
arch_trigger_all_cpu_backtrace+0x4d/0x7b
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
__rcu_pending+0x82/0x358
Apr 17 07:13:02 head8 kernel: [587397.860028]  [] ? 
tick_nohz_

Bug#705619: The package bug script ... exited with an error status (probably due to 'cat: /proc/asound/cards: No such file or directory')

2013-04-17 Thread Yaroslav Halchenko 
Package: src:linux
Version: 3.2.41-2
Severity: normal


while filing a previous (and this) bug report, reportbug puked me:

Include network configuration and status from this computer? n
cat: /proc/asound/cards: No such file or directory
oThe package bug script /usr/share/bug/linux-image-3.2.0-4-amd64/script exited 
with an error status (return code = 256). D you still want to file a report? 
[y|N|q|?]?

so you might like to have that addressed so users could still provide all the
useful information.


-- Package-specific info:
** Version:
Linux version 3.2.0-4-amd64 (debian-kernel@lists.debian.org) (gcc version 4.6.3 
(Debian 4.6.3-15) ) #1 SMP Debian 3.2.41-2

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 
root=UUID=5f04f20a-cd3b-4e39-911e-e6d32aa44a12 ro console=ttyS2,115200n8 
console=tty1

** Not tainted

** Kernel log:
[600462.264008] NMI backtrace for cpu 56
[600462.264008] CPU 56 
[600462.264008] Modules linked in: tcp_diag inet_diag parport_pc ppdev lp 
parport bnep rfcomm bluetooth rfkill binfmt_misc fuse nfsd nfs nfs_acl 
auth_rpcgss fscache lockd sunrpc ipmi_si ipmi_devintf ipmi_msghandler 
e752x_edac loop bonding forcedeth sp5100_tco powernow_k8 mperf crc32c_intel 
ghash_clmulni_intel joydev evdev aesni_intel psmouse aes_x86_64 serio_raw 
aes_generic cryptd pcspkr i2c_piix4 amd64_edac_mod edac_mce_amd i2c_core 
k10temp edac_core fam15h_power button processor thermal_sys ext4 crc16 jbd2 
mbcache dm_mod usbhid hid sg sd_mod ata_generic crc_t10dif ohci_hcd ahci 
pata_atiixp libahci ehci_hcd libata usbcore igb scsi_mod usb_common dca [last 
unloaded: scsi_wait_scan]
[600462.264008] 
[600462.264008] Pid: 9908, comm: /usr/bin/python Not tainted 3.2.0-4-amd64 #1 
Debian 3.2.41-2 Supermicro H8QG6/H8QG6
[600462.264008] RIP: 0033:[<2ad2e73dc957>]  [<2ad2e73dc957>] 
0x2ad2e73dc956
[600462.264008] RSP: 002b:7fffb16eced8  EFLAGS: 0217
[600462.264008] RAX: 0270 RBX: 09d0 RCX: 
697c
[600462.264008] RDX: 0270 RSI: 085a6580 RDI: 
24e904a0
[600462.264008] RBP: 24e8dda0 R08: 21598350 R09: 
0100
[600462.264008] R10: 0100 R11: 2ad2e719c8a4 R12: 
0200
[600462.264008] R13: 21598360 R14: 0006 R15: 
05879cd0
[600462.264008] FS:  2ad2d1c170e0() GS:888026c0() 
knlGS:
[600462.264008] CS:  0010 DS:  ES:  CR0: 80050033
[600462.264008] CR2: 07a99410 CR3: 001144b32000 CR4: 
000406e0
[600462.264008] DR0:  DR1:  DR2: 

[600462.264008] DR3:  DR6: 0ff0 DR7: 
0400
[600462.264008] Process /usr/bin/python (pid: 9908, threadinfo 
881144b3a000, task 8800c6a9c280)
[600462.264008] 
[600462.264008] Call Trace:
[600462.264018] NMI backtrace for cpu 58
[600462.264018] CPU 58 
[600462.264018] Modules linked in: tcp_diag inet_diag parport_pc ppdev lp 
parport bnep rfcomm bluetooth rfkill binfmt_misc fuse nfsd nfs nfs_acl 
auth_rpcgss fscache lockd sunrpc ipmi_si ipmi_devintf ipmi_msghandler 
e752x_edac loop bonding forcedeth sp5100_tco powernow_k8 mperf crc32c_intel 
ghash_clmulni_intel joydev evdev aesni_intel psmouse aes_x86_64 serio_raw 
aes_generic cryptd pcspkr i2c_piix4 amd64_edac_mod edac_mce_amd i2c_core 
k10temp edac_core fam15h_power button processor thermal_sys ext4 crc16 jbd2 
mbcache dm_mod usbhid hid sg sd_mod ata_generic crc_t10dif ohci_hcd ahci 
pata_atiixp libahci ehci_hcd libata usbcore igb scsi_mod usb_common dca [last 
unloaded: scsi_wait_scan]
[600462.264018] 
[600462.264018] Pid: 9827, comm: /usr/bin/python Not tainted 3.2.0-4-amd64 #1 
Debian 3.2.41-2 Supermicro H8QG6/H8QG6
[600462.264018] RIP: 0033:[<2ad2e73dc999>]  [<2ad2e73dc999>] 
0x2ad2e73dc998
[600462.264018] RSP: 002b:7fffb16ec968  EFLAGS: 0202
[600462.264018] RAX: 0185 RBX: 09c8 RCX: 
697c
[600462.264018] RDX: 0184 RSI: 35820080 RDI: 
24e9bfb0
[600462.264018] RBP: 24e9a760 R08: 21599870 R09: 
0100
[600462.264018] R10: 0100 R11: 2ad2e719c8a4 R12: 
03c0
[600462.264018] R13: 21599880 R14: 0006 R15: 
356603d0
[600462.264018] FS:  2ad2d1c170e0() GS:888026c8() 
knlGS:
[600462.264018] CS:  0010 DS:  ES:  CR0: 80050033
[600462.264018] CR2: 01d51000 CR3: 00113ea2a000 CR4: 
000406e0
[600462.264018] DR0:  DR1:  DR2: 

[600462.264018] DR3:  DR6: 0ff0 DR7: 
0400
[600462.264018] Process /usr/bin/python (pid: 9827, threadinfo 
88113ea3c000, task 881020bbaf60)
[600462.264018] 
[600462.264018] Call Trace:
[600462.264014] NMI backtrace for cpu 54
[600462.264014] CPU 54 
[600462.264014] Modules linked in: tcp_diag inet_dia

Processed: bug 705124 is forwarded to http://lists.xen.org/archives/html/xen-devel/2013-04/msg01493.html

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> forwarded 705124 
> http://lists.xen.org/archives/html/xen-devel/2013-04/msg01493.html
Bug #705124 [linux-image-2.6.32-5-xen-amd64] ext3 fs corruption in squeeze PV 
domain under wheezy Xen
Set Bug forwarded-to-address to 
'http://lists.xen.org/archives/html/xen-devel/2013-04/msg01493.html'.
> thanks
Stopping processing here.

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

Bug#705627: linux-image-3.2.0-4-486: wheezy installer fails to boot on Lenovo S10e

2013-04-17 Thread Hans-Christoph Steiner 
Package: linux-image-3.2.0-4-486
Version: 3.2.35-2
Severity: grave
Tags: d-i patch
Justification: renders package unusable


I've just installed the debian-wheezy-DI-rc1-i386-netinst.iso installer on a
Lenovo S10e netbook with a Intel Atom N270 1.60GHz by doing this onto a USB
thumb drive:

dd if=debian-wheezy-DI-rc1-i386-netinst.iso of=/dev/sdb

It does show the splash screen, but when I select "Install", it just hangs
there, and never boots. Running "install intel_idle.max_cstate=0" boots, and
that's how I was able to run the install. Otherwise the install process worked
perfectly.  Apparently its an old bug, I found a discussion of the issue and
the workaround that I used here:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/634702

After the install, I tried installing the same kernel that the installer uses
(linux-image-3.2.0-4-486) and rebooting to it.  That worked fine.  It seems
that is a different version than the version the installer uses:

$ file /mnt/install.386/vmlinuz 
/mnt/install.386/vmlinuz: Linux kernel x86 boot executable bzImage, version
3.2.0-4-486 (debian-kernel@lists.debian.org) #1 Debian 3.2.35-2, RO-rootFS,
swap_dev 0x2, Normal VGA

$ file /boot/vmlinuz-3.2.0-4-486
/boot/vmlinuz-3.2.0-4-486: Linux kernel x86 boot executable bzImage, version
3.2.0-4-486 (debian-kernel@lists.debian.org) #1 Debian 3.2.41-2, RO-rootFS,
swap_dev 0x2, Normal VGA


-- System Information:
Debian Release: 7.0 DI-rc1
Architecture: i386 (i686)

Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (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/20130417161821.2004.57521.report...@blinky.at.or.at

Bug#705627: nightly build still affected

2013-04-17 Thread Hans-Christoph Steiner 

I just downloaded and tried this:
http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso

from 2013-04-17 11:11

It is also affected.


-- 
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/516ed982.4060...@eds.org

Processed: tagging 705336

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 705336 - patch
Bug #705336 [src:linux] linux - kvm clock wrong after resume from disk
Removed tag(s) patch.
> thanks
Stopping processing here.

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

Bug#705627: linux-image-3.2.0-4-486: wheezy installer fails to boot on Lenovo S10e

2013-04-17 Thread John Paul Adrian Glaubitz 
This bug is supposed to have been fixed in the upstream kernel source 
long time ago, see [1] and [2].


We should verify whether linux-image-3.2.0-4-486 contains the quirk or not.

Adrian

> [1] http://lkml.indiana.edu/hypermail/linux/kernel/1101.0/00124.html
> [2] https://bugs.meego.com/show_bug.cgi?id=7093

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


--
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/516edebe.1040...@physik.fu-berlin.de

Bug#704242: Driver for PL-2303 HX not working

2013-04-17 Thread Karsten Malcher 

Am 17.04.2013 15:13, schrieb Johan Hovold:

The logs look incomplete. It's probably because they're flooded with
serial_write_room and chars_in_buffer messages.


Hmmm - i feared that this happens - the logs where to big.



Can you try to reproduce this on a later kernel (e.g. 3.8) which uses
dynamic debugging?


I will try to compile a kernel 3.8.5 like this way:
http://verahill.blogspot.de/2013/02/342-compiling-kernel-38-on-debian.html
But this will take some time ...



Can you minimise your test setup using a custom program which only opens
the device, initialises it, writes the four characters (e.g. "test")
and reads them back (over you hardwired loop) before closing the device
again?


I have used a little perl program that opens the port and send "Test" to the 
looped back device.
The length of the log looks good.


  Make sure to verify it using a working device first.


I use this script with a ch341 adapter and it works.



Thanks,
Johan


Cheers
Karsten

[ 1714.545685] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/usb-serial.c: serial_install
[ 1714.545704] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/usb-serial.c: serial_open - port 0
[ 1714.545708] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_open -  port 0
[ 1714.546283] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x8:0x0  0
[ 1714.548272] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x9:0x0  0
[ 1714.548276] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_set_termios -  port 0
[ 1714.550281] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xa1:0x21:0:0  7 - 80 25 0 0 0 0 8
[ 1714.550284] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_set_termios - data bits = 8
[ 1714.550287] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_set_termios - baud requested = 9600
[ 1714.550289] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_set_termios - baud set = 9600
[ 1714.550291] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_set_termios - stop bits = 1
[ 1714.550292] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_set_termios - parity = none
[ 1714.552272] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x21:0x20:0:0  7
[ 1714.554290] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0xa1:0x21:0:0  7 - 80 25 0 0 0 0 8
[ 1714.556270] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: 0x40:0x1:0x0:0x0  0
[ 1714.556283] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_open - submitting read urb
[ 1714.556305] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_open - submitting interrupt urb
[ 1714.557255] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_read_int_callback (0)
[ 1714.557261] pl2303 ttyUSB0: pl2303_read_int_callback - length = 10, data = a1 20 00 00 00 00 02 00 8b 00 
[ 1714.557271] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/generic.c: usb_serial_handle_dcd_change - port 0, status 1
[ 1714.558284] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: set_control_lines - value = 3, retval = 0
[ 1714.558522] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5401
[ 1714.558534] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_ioctl (0) cmd = 0x5401
[ 1714.558543] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_ioctl not supported = 0x5401
[ 1714.558604] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5401
[ 1714.558613] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_ioctl (0) cmd = 0x5401
[ 1714.558622] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_ioctl not supported = 0x5401
[ 1714.558856] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/usb-serial.c: serial_ioctl - port 0, cmd 0x5401
[ 1714.558866] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_ioctl (0) cmd = 0x5401
[ 1714.558875] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/pl2303.c: pl2303_ioctl not supported = 0x5401
[ 1714.558886] /build/buildd-linux_3.2.23-1-amd64-zj7gxu/linux-3.2.23/drivers/usb/serial/usb-serial.c: se

Processed: tagging 705586

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 705586 - lfs
Bug #705586 [src:linux] linux-image-3.2.0-4-amd64: ath9k_htc fails to 
initialize with tl-wn722n; regression vs sqeeze backport
Removed tag(s) lfs.
> thanks
Stopping processing here.

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

Bug#705579: marked as done (please consider the kernel module dependencies)

2013-04-17 Thread Debian Bug Tracking System 
Your message dated Wed, 17 Apr 2013 19:30:13 +0100
with message-id <20130417183013.gr2...@decadent.org.uk>
and subject line Re: Bug#705579: please consider the kernel module dependencies
has caused the Debian Bug report #705579,
regarding please consider the kernel module dependencies
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.)


-- 
705579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705579
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: initramfs-tools
Version: 0.110
Severity: wishlist

It would be very nice if mkinitramfs considers the kernel
module dependencies when creating the initrd. /lib/modules/\
3.8.?/modules.dep shows pretty clear that ehci-hcd depends
upon ehci-pci, for example. See #700572.

This would make initramfs-tools much more insusceptible to
future changes in the module dependencies.


Many thanx
Harri
--- End Message ---
--- Begin Message ---
On Wed, Apr 17, 2013 at 08:40:13AM +0200, Harald Dunkel wrote:
> Package: initramfs-tools
> Version: 0.110
> Severity: wishlist
> 
> It would be very nice if mkinitramfs considers the kernel
> module dependencies when creating the initrd.

It does.

> /lib/modules/\
> 3.8.?/modules.dep shows pretty clear that ehci-hcd depends
> upon ehci-pci, for example. See #700572.

Wrong, ehci-pci depends on ehci-hcd.

> This would make initramfs-tools much more insusceptible to
> future changes in the module dependencies.
 
Ben.

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

Bug#705586: linux-image-3.2.0-4-amd64: ath9k_htc fails to initialize with tl-wn722n; regression vs sqeeze backport

2013-04-17 Thread Ben Hutchings 
This is unlikely to be a regression between squeeze-backports
and wheezy, because they should be functionally the same
(aside from some ARM configurations).

What was the previous working kernel package version, as shown by
'dpkg -s linux-image-3.2.0-0.bpo.4-amd64' ?

On Wed, Apr 17, 2013 at 02:33:17AM -0600, Steven Hystad wrote:
> Package: src:linux
> Version: 3.2.41-2
> Severity: normal
> Tags: lfs
> 
> Dear Maintainer,
> 
> I have a few TL-WN722N usb wireless networking devices that I use on a few
> systems running Dabian Sqweeze backports. On testing Weezy the driver
> encounters an error and doesn't complete setting up the wlan interface.
> 
> I did try compiling and installing a standard kernel bassed on the config
> included in Debian, however I encountered issues with the graphics and didn't
> test the networking.
> 
> In the data below you'll see that the builtin wireless device does startup
> correctly, but the usb wireless device, while it is recognised correctly, 
> fails
> after inserting firmware.
[...]
> [  388.299820] usb 3-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> [  388.300155] xhci_hcd :00:14.0: ERROR no room on ep ring
> [  388.303268] usb 3-1: ath9k_htc: Unable to allocate URBs
[...]

This seems to indicate a problem (maybe a bug) in allocation of USB
bandwidth.  Is this device connected directly to the USB port, or
through a hub?

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/20130417183626.gs2...@decadent.org.uk

Processed: tagging 705586

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 705586 + moreinfo
Bug #705586 [src:linux] linux-image-3.2.0-4-amd64: ath9k_htc fails to 
initialize with tl-wn722n; regression vs sqeeze backport
Added tag(s) moreinfo.
> thanks
Stopping processing here.

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

Processed: severity of 705627 is important

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> severity 705627 important
Bug #705627 [linux-image-3.2.0-4-486] linux-image-3.2.0-4-486: wheezy installer 
fails to boot on Lenovo S10e
Severity set to 'important' from 'grave'
> thanks
Stopping processing here.

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

Bug#705627: linux-image-3.2.0-4-486: wheezy installer fails to boot on Lenovo S10e

2013-04-17 Thread Ben Hutchings 
On Wed, Apr 17, 2013 at 07:41:18PM +0200, John Paul Adrian Glaubitz wrote:
> This bug is supposed to have been fixed in the upstream kernel
> source long time ago, see [1] and [2].
> 
> We should verify whether linux-image-3.2.0-4-486 contains the quirk or not.
 
Oh, come on, you can see that was applied years ago.  This is a
different bug, or possibly a regression.

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/20130417184130.gt2...@decadent.org.uk

Bug#705635: [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... GPU hung

2013-04-17 Thread tuXXer 
Package: linux-image-3.2.0-4-amd64
Version: 3.2.41-2

After enabling VAAPI driver for my Intel HD GPU the GPU hungs on every new 
chromium tab, watching movies etc.
It's seems that other distributions had the same error: 
https://bugzilla.redhat.com/show_bug.cgi?id=879823

dmesg:
[ 2698.826719] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... 
GPU hung
[ 2698.826731] [drm] capturing error event; look for more information in 
/debug/dri/0/i915_error_state
[ 2711.981699] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... 
GPU hung

packages:
ii  libva-glx1:amd64  1.0.15-4  
amd64Video Acceleration (VA) API for Linux -- GLX runtime
ii  libva-x11-1:amd64 1.0.15-4  
amd64Video Acceleration (VA) API for Linux -- X11 runtime
ii  libva1:amd64  1.0.15-4  
amd64Video Acceleration (VA) API for Linux -- runtime
ii  i965-va-driver:amd64  1.0.17-1  
amd64VAAPI driver for Intel G45 & HD Graphics family
ii  xserver-xorg-video-intel  2:2.19.0-6
amd64X.Org X server -- Intel i8xx, i9xx display driver

The GPU hungs are very annoying. Disabling the video accelaration IMHO is no 
option.


-- 
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/trinity-fb120fc4-429b-48d2-9e0c-fd0029c07af8-1366224688876@3capp-gmx-bs54

Bug#705627: linux-image-3.2.0-4-486: wheezy installer fails to boot on Lenovo S10e

2013-04-17 Thread John Paul Adrian Glaubitz 

On 04/17/2013 08:41 PM, Ben Hutchings wrote:

On Wed, Apr 17, 2013 at 07:41:18PM +0200, John Paul Adrian Glaubitz wrote:

This bug is supposed to have been fixed in the upstream kernel
source long time ago, see [1] and [2].

We should verify whether linux-image-3.2.0-4-486 contains the quirk or not.


Oh, come on, you can see that was applied years ago.  This is a
different bug, or possibly a regression.


Yes, I verified that it got applied, I forgot to reply here. I was just 
digging through the bug report that Hans linked and the aforementioned 
fixes have been linked there.


I don't have said hardware, so I can't really help to debug the problem.

Adrian

--
 .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaub...@debian.org
`. `'   Freie Universitaet Berlin - glaub...@physik.fu-berlin.de
  `-GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913


--
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/516eefb3.3050...@physik.fu-berlin.de

Bug#696059: linux: PATCH required for server interrupt load balancing/irqbalance (tested)

2013-04-17 Thread Faustin Lammler 
Dear maintainer,

I must agree with Sebastian Kutsch.

irqbalance may not be the better way to treat interruption problem but it
is doing is job quite good on a (squeeze - 3.2.0-0.bpo.4-amd64).

Regards,
Faustin LAMMLER

Bug#705586: linux-image-3.2.0-4-amd64: ath9k_htc fails to initialize with tl-wn722n; regression vs sqeeze backport

2013-04-17 Thread Steven Hystad 
On Wed, 2013-04-17 at 19:36 +0100, Ben Hutchings wrote:
> This is unlikely to be a regression between squeeze-backports
> and wheezy, because they should be functionally the same
> (aside from some ARM configurations).
> 
> What was the previous working kernel package version, as shown by
> 'dpkg -s linux-image-3.2.0-0.bpo.4-amd64' ?
It appears to work just fine on my desktop running Sqeeze with
backports. Even just updated it.
$ dpkg -s linux-image-3.2.0-0.bpo.4-amd64
Package: linux-image-3.2.0-0.bpo.4-amd64
Status: install ok installed
Priority: optional
Section: kernel
Installed-Size: 114460
Maintainer: Debian Kernel Team 
Architecture: amd64
Source: linux
Version: 3.2.41-2~bpo60+1
Provides: linux-image, linux-modules-3.2.0-0.bpo.4-amd64
Depends: kmod | module-init-tools, linux-base (>= 3~), initramfs-tools
(>= 0.99~) | linux-initramfs-tool
Pre-Depends: debconf | debconf-2.0
Recommends: firmware-linux-free (>= 3~)
Suggests: linux-doc-3.2, debian-kernel-handbook, grub-pc | extlinux |
lilo
Breaks: at (<< 3.1.12-1+squeeze1), initramfs-tools (<< 0.99~)
Description: Linux 3.2 for 64-bit PCs
 The Linux kernel 3.2 and modules for use on PCs with AMD64, Intel 64 or
 VIA Nano processors.
 .
 This kernel also runs on a Xen hypervisor.  It supports both privileged
 (dom0) and unprivileged (domU) operation.

And dmesg shows it initialize without errors.
[   50.352145] usb 4-5: new high-speed USB device number 2 using
ehci_hcd
[   50.501338] usb 4-5: New USB device found, idVendor=0cf3,
idProduct=9271
[   50.501347] usb 4-5: New USB device strings: Mfr=16, Product=32,
SerialNumber=48
[   50.501355] usb 4-5: Product: USB2.0 WLAN
[   50.501360] usb 4-5: Manufacturer: ATHEROS
[   50.501365] usb 4-5: SerialNumber: 12345
[   50.556687] cfg80211: Calling CRDA to update world regulatory domain
[   50.660211] usb 4-5: firmware: agent loaded htc_9271.fw into memory
[   50.943846] usb 4-5: ath9k_htc: Transferred FW: htc_9271.fw, size:
51272
[   51.178754] ath9k_htc 4-5:1.0: ath9k_htc: HTC initialized with 33
credits
[   51.369986] ath9k_htc 4-5:1.0: ath9k_htc: FW Version: 1.3
[   51.369993] ath: EEPROM regdomain: 0x809c
[   51.369998] ath: EEPROM indicates we should expect a country code
[   51.370004] ath: doing EEPROM country->regdmn map search
[   51.370009] ath: country maps to regdmn code: 0x52
[   51.370014] ath: Country alpha2 being used: CN
[   51.370018] ath: Regpair used: 0x52
[   51.383550] ieee80211 phy0: Atheros AR9271 Rev:1
[   51.384420] Registered led device: ath9k_htc-phy0
[   51.384427] usb 4-5: ath9k_htc: USB layer initialized
[   51.384475] usbcore: registered new interface driver ath9k_htc

I guess this could also be an issue with the laptop I'm trying to get
this to work on. Would it be helpful if I were to install Sqeeze on my
laptop and see if it works that way?
> 
> On Wed, Apr 17, 2013 at 02:33:17AM -0600, Steven Hystad wrote:
> > Package: src:linux
> > Version: 3.2.41-2
> > Severity: normal
> > Tags: lfs
> > 
> > Dear Maintainer,
> > 
> > I have a few TL-WN722N usb wireless networking devices that I use on a few
> > systems running Dabian Sqweeze backports. On testing Weezy the driver
> > encounters an error and doesn't complete setting up the wlan interface.
> > 
> > I did try compiling and installing a standard kernel bassed on the config
> > included in Debian, however I encountered issues with the graphics and 
> > didn't
> > test the networking.
> > 
> > In the data below you'll see that the builtin wireless device does startup
> > correctly, but the usb wireless device, while it is recognised correctly, 
> > fails
> > after inserting firmware.
> [...]
> > [  388.299820] usb 3-1: ath9k_htc: Transferred FW: htc_9271.fw, size: 51272
> > [  388.300155] xhci_hcd :00:14.0: ERROR no room on ep ring
> > [  388.303268] usb 3-1: ath9k_htc: Unable to allocate URBs
> [...]
> 
> This seems to indicate a problem (maybe a bug) in allocation of USB
> bandwidth.  Is this device connected directly to the USB port, or
> through a hub?
> 
> Ben.
> 
Direct connection; no hubs are used.


-- 
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/1366250757.2495.9.camel@destruction.l

Re: Firmware versions for Intel Wireless 6005/6205

2013-04-17 Thread Ben Hutchings 
On Wed, 2013-04-17 at 03:19 +0100, Ben Hutchings wrote:
> There's an error message that's bugging me at every boot:
> 
> [5.178355] iwlwifi :03:00.0: firmware: agent aborted loading 
> iwlwifi-6000g2a-6.ucode (not found?)
> 
> Indeed, it's not installed; firmware-iwlwifi in testing/unstable has an
> older version, and the driver does fall back to that:
[...]
> More importantly, will the installer complain about this unavailable
> firmware file (as in #689416)?

I've now tested this, and unfortunately the installer does complain.  I
put firmware-iwlwifi 0.36+wheezy.1 on a separate memory card, and when
prompted for the missing file (under the new filename) I answered yes.
Looking at the kernel log, the driver loaded the older firmware
successfully.  (In fact, I think the installer must have installed
firmware-iwlwifi even before asking me this question.  Otherwise it
would have listed the older filenames too.)

It then asked the same question again, and I had to answer no to
progress.

I see three options:

(a) Update firmware-iwlwifi to include the new firmware.  Slightly risky
as our users haven't been testing it.

(b Change the driver to request firmware ABI 5 then 4.  Trivial code
change, and only has a negative effect for users that installed
firmware-iwlwifi from experimental.

(c) Change the driver to request firmware ABI 5, then 6, then 4.  Bigger
code change; allows people to use the new firmware if they want it but
not if they install the firmware-iwlwifi package (as that will have both
ABI 5 and ABI 6 until post-jessie).

I think (b) looks like the only viable option.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


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

Processed: cloning 697473, tagging 697473, closing 697473, submitter -1, tagging -1, reassign -1 to src:linux ...

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> # This will have to be handled differently in wheezy
> clone 697473 -1
Bug #697473 [firmware-iwlwifi] firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Bug 697473 cloned as bug 705655
> tags 697473 + experimental
Bug #697473 [firmware-iwlwifi] firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Added tag(s) experimental.
> close 697473
Bug #697473 [firmware-iwlwifi] firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Marked Bug as done
> submitter -1 b...@decadent.org.uk
Bug #705655 [firmware-iwlwifi] firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Changed Bug submitter to 'b...@decadent.org.uk' from 'Andreas Kloeckner 
'
> tags -1 + wheezy sid
Bug #705655 [firmware-iwlwifi] firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Added tag(s) sid and wheezy.
> reassign -1 src:linux 3.2.41-2
Bug #705655 [firmware-iwlwifi] firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Bug reassigned from package 'firmware-iwlwifi' to 'src:linux'.
No longer marked as found in versions firmware-nonfree/0.36.
No longer marked as fixed in versions firmware-nonfree/0.37.
Bug #705655 [src:linux] firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Marked as found in versions linux/3.2.41-2.
> retitle -1 iwlwifi requests unpackaged firmware blob iwlwifi-6000g2a-6.ucode
Bug #705655 [src:linux] firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Changed Bug title to 'iwlwifi requests unpackaged firmware blob 
iwlwifi-6000g2a-6.ucode' from 'firmware-iwlwifi: Missing 
iwlwifi-6000g2a-6.ucode'
> thanks
Stopping processing here.

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

Processed: tagging 697473

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 697473 - pending
Bug #697473 {Done: Ben Hutchings } [firmware-iwlwifi] 
firmware-iwlwifi: Missing iwlwifi-6000g2a-6.ucode
Removed tag(s) pending.
> thanks
Stopping processing here.

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

Processed: tagging 705655, severity of 705655 is important

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 705655 + d-i
Bug #705655 [src:linux] iwlwifi requests unpackaged firmware blob 
iwlwifi-6000g2a-6.ucode
Added tag(s) d-i.
> severity 705655 important
Bug #705655 [src:linux] iwlwifi requests unpackaged firmware blob 
iwlwifi-6000g2a-6.ucode
Severity set to 'important' from 'normal'
> thanks
Stopping processing here.

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

Bug#705655: Firmware versions for Intel Wireless 6005/6205

2013-04-17 Thread Ben Hutchings 
 Forwarded Message 
From: Ben Hutchings 
To: debian-rele...@lists.debian.org
Cc: Debian installer maintainers , Debian kernel 
maintainers 
Subject: Re: Firmware versions for Intel Wireless 6005/6205
Date: Thu, 18 Apr 2013 04:29:15 +0100

On Wed, 2013-04-17 at 03:19 +0100, Ben Hutchings wrote:
> There's an error message that's bugging me at every boot:
> 
> [5.178355] iwlwifi :03:00.0: firmware: agent aborted loading 
> iwlwifi-6000g2a-6.ucode (not found?)
> 
> Indeed, it's not installed; firmware-iwlwifi in testing/unstable has an
> older version, and the driver does fall back to that:
[...]
> More importantly, will the installer complain about this unavailable
> firmware file (as in #689416)?

I've now tested this, and unfortunately the installer does complain.  I
put firmware-iwlwifi 0.36+wheezy.1 on a separate memory card, and when
prompted for the missing file (under the new filename) I answered yes.
Looking at the kernel log, the driver loaded the older firmware
successfully.  (In fact, I think the installer must have installed
firmware-iwlwifi even before asking me this question.  Otherwise it
would have listed the older filenames too.)

It then asked the same question again, and I had to answer no to
progress.

I see three options:

(a) Update firmware-iwlwifi to include the new firmware.  Slightly risky
as our users haven't been testing it.

(b Change the driver to request firmware ABI 5 then 4.  Trivial code
change, and only has a negative effect for users that installed
firmware-iwlwifi from experimental.

(c) Change the driver to request firmware ABI 5, then 6, then 4.  Bigger
code change; allows people to use the new firmware if they want it but
not if they install the firmware-iwlwifi package (as that will have both
ABI 5 and ABI 6 until post-jessie).

I think (b) looks like the only viable option.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.



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

Processed: tagging 705655

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 705655 + pending
Bug #705655 [src:linux] iwlwifi requests unpackaged firmware blob 
iwlwifi-6000g2a-6.ucode
Ignoring request to alter tags of bug #705655 to the same tags previously set
> thanks
Stopping processing here.

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

Processed: tagging 705619

2013-04-17 Thread Debian Bug Tracking System 
Processing commands for cont...@bugs.debian.org:

> tags 705619 + pending
Bug #705619 [src:linux] The package bug script ... exited with an error status 
(probably due to 'cat: /proc/asound/cards: No such file or directory')
Added tag(s) pending.
> thanks
Stopping processing here.

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

Bug#698829: kernel swap after upgrade to 3.2.23-1~bpo60+2

2013-04-17 Thread Ben Hutchings 
On Tue, 2013-04-02 at 10:59 +0200, Sandro Tosi wrote:
> Hello Ben,
> i'm a collegue of Daniele and I'd like to add some more information on
> this issue, which we're still facing with 3.2.35-2~bpo60+1 .
[...]
> Please let us know if you need more information, if we can run some
> diagnostics or try some solutions, it's really important for us to get
> that fixed.

Sorry, I can't afford to spend any more time on this bug.

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


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

Bug#704767: linux-image-2.6.32-5-amd64: kernel crashes when task block for more than 120 seconds

2013-04-17 Thread Ben Hutchings 
On Mon, 2013-04-08 at 11:15 -0400, Olivier Diotte wrote:
> Hi Ben,
> 
> I just arrived at the machine this morning and it seems the
> system is responsive: gdm, my gnome-session,
> even gnome-screensaver were still running
>  (the other two times, I had been kicked back
>  to tty1 and the system was totally unresponsive).
> 
> On the other hand, the doxygen process
>  terminated (with a segfault though).
> The logs seem to indicate "page allocation failure"
>  crashes

A page allocation failure is not a crash.

>  and there are also errors that may
>  indicate my USB dongle is at fault (at some point
>  during the weekend, exim was unable to connect
>  to localhost and there are a lot of errors related
>  to wifi/networking).
> 
> It also seems weird to me that /var/log/debug
>  skips from April 6th 19h02 to April 8th 09h41

I don't think that's so weird.

> Crashes also seems to say my kernel is tainted
>  which I am not sure why as the closest thing
>  I have to a taint would be
>  firmware-realtek (for the USB dongle).

No, the wireless driver taints the kernel because it comes from the
staging area of the kernel source.  The staging drivers have not been
thoroughly reviewed and are assumed (usually correctly) to be quite
buggy.

> I am unsure what to try next except another
> doxygen run friday, except this time I will
>  deactivate/remove the USB dongle and reboot
>  beforehand. Let me know if you have
> a better idea for tests, would like other infos, etc.
> 
> Attached are all logs that seemed
>  relevant (as a .tar.bz2 archive), edited to remove my
>  MAC address (replaced with MY:MA:Ca:dr:es:s0,
>  yeah, I forgot a d, but I am too lazy
>  to edit now). I also removed all entries predating
>  April 5th at around 17h00.
> I also attached /proc/meminfo from this morning, in case that is relevant.

OK, there's nothing weird in meminfo.

I think the basic problem is that doxygen is allocating more memory than
can be provided on this computer.  If the working set (the set of data
that's regularly accessed) for all running programs adds up to more than
the size of physical memory then the kernel will be continuously
swapping data to and from the swap partition, and the larger programs
will become unresponsive.

The wireless networking failure is just a symptom of the shortage of
free memory.

Changing the I/O class, as you originally attempted, doesn't affect
swapping, so far as I know.

Are you running doxygen over a particularly large set of sources?  I ask
because I want to know whether this could be a bug in doxygen (use of
excessive memory).

Ben.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


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

Bug#705586: linux-image-3.2.0-4-amd64: ath9k_htc fails to initialize with tl-wn722n; regression vs sqeeze backport

2013-04-17 Thread Steven Hystad 
On Wed, 2013-04-17 at 20:05 -0600, Steven Hystad wrote:
> > This seems to indicate a problem (maybe a bug) in allocation of USB
> > bandwidth.  Is this device connected directly to the USB port, or
> > through a hub?
> > 
> > Ben.
> > 
> Direct connection; no hubs are used.
> 
> 
I should note that the issue occurs with or without the use of a hub,
and of the usb devices I have only the TL-WN722N has this issue.


-- 
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/1366264169.3509.13.camel@destruction.l

Bug#704767: linux-image-2.6.32-5-amd64: kernel crashes when task block for more than 120 seconds

2013-04-17 Thread Ben Hutchings 
On Mon, 2013-04-15 at 10:22 -0400, Olivier Diotte wrote:
> Hi Ben,
> 
> I did the following test this weekend:
> -Power off the machine
> -Remove the USB dongle (taint?)
> -Power up the machine
> -Log in and run doxygen as before
> 
> It still crashes. This is, seemingly, the related message:
> Apr 14 06:37:59 Debianosaur kernel: [137278.487402] doxygen[2535]:
> segfault at 0 ip 0065638c sp 7fffa65be680 error 4 in
> doxygen[40+4f]

Maybe this is what happens after the kernel refuses to allocate more
memory to it.

> Then again, the machine is still responsive, so this looks like it may
> be more of a bug in doxygen than in the kernel.

It does depend on how large a job you're giving to doxygen.  It
presumably needs to hold a lot of information about the source code it
scans in memory, so that it can generate cross-references.

Ben.

> Thanks for your help nonetheless.

-- 
Ben Hutchings
The first rule of tautology club is the first rule of tautology club.


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