date:20130627

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

 reassign 714155 mdadm
Bug #714155 [initramfs-tools] initramfs-tools: mdadm starts up before all 
needed devices are available
Bug reassigned from package 'initramfs-tools' to 'mdadm'.
No longer marked as found in versions initramfs-tools/0.113.
Ignoring request to alter fixed versions of bug #714155 to the same values 
previously set
 thanks
Stopping processing here.

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

Bug#714155: initramfs-tools: mdadm starts up before all needed devices are available

2013-06-27 Thread Michael Prokop

reassign 714155 mdadm
thanks

* Brian Minton [Wed Jun 26, 2013 at 08:59:06AM -0400]:
 Package: initramfs-tools
 Version: 0.113
 Severity: normal

 Dear Maintainer,

 bminton@bminton:~$ dmesg|grep sde
 [3.114799] sd 8:0:0:0: [sde] 2930277168 512-byte logical blocks: (1.50 
 TB/1.36 TiB)
 [3.115888] sd 8:0:0:0: [sde] Write Protect is off
 [3.119758] sd 8:0:0:0: [sde] Mode Sense: 00 3a 00 00
 [3.119808] sd 8:0:0:0: [sde] Write cache: enabled, read cache: enabled, 
 doesn't support DPO or FUA
 [3.134660]  sde: unknown partition table
 [3.135237] sd 8:0:0:0: [sde] Attached SCSI disk
 [45018.662644] md: export_rdev(sde)
 [45018.748222] md: bindsde
 [45018.772292]  disk 2, o:1, dev:sde
 bminton@bminton:~$ dmesg|grep md1
 [2.164616] md: md1 stopped.
 [2.171754] md/raid:md1: device sdc operational as raid disk 0
 [2.172104] md/raid:md1: device sda2 operational as raid disk 1
 [2.173021] md/raid:md1: allocated 3282kB
 [2.173416] md/raid:md1: raid level 5 active with 2 out of 3 devices, 
 algorithm 5
 [2.174093] md1: detected capacity change from 0 to 3000603639808
 [2.177433]  md1: unknown partition table
 [45018.773937] md: recovery of RAID array md1

 Here's some info about my RAID setup:

 Personalities : [raid6] [raid5] [raid4]
 md1 : active raid5 sde[3] sdc[0] sda2[1]
   2930276992 blocks level 5, 64k chunk, algorithm 5 [3/2] [UU_]
   [===.]  recovery = 19.4% (285554336/1465138496) 
 finish=684.0min speed=28741K/sec

 unused devices: none
 /dev/md1:
 Version : 0.90
   Creation Time : Wed Jun  3 09:16:22 2009
  Raid Level : raid5
  Array Size : 2930276992 (2794.53 GiB 3000.60 GB)
   Used Dev Size : 1465138496 (1397.26 GiB 1500.30 GB)
Raid Devices : 3
   Total Devices : 3
 Preferred Minor : 1
 Persistence : Superblock is persistent

 Update Time : Wed Jun 19 11:22:09 2013
   State : clean, degraded, recovering
  Active Devices : 2
 Working Devices : 3
  Failed Devices : 0
   Spare Devices : 1

  Layout : parity-last
  Chunk Size : 64K

  Rebuild Status : 19% complete

UUID : bfa46bf0:67d6e997:e473ac2a:9f2b3a7b
  Events : 0.2609536

 Number   Major   Minor   RaidDevice State
0   8   320  active sync   /dev/sdc
1   821  active sync   /dev/sda2
3   8   642  spare rebuilding   /dev/sde

[snip package information]

I'm not sure what initramfs-tools could do about that, AFAICS it's
an issue with mdadm's i-t hook, so reassigning to mdadm.

PS: It would be nice to write a few more words about
misbehaviour/expected behaviour and not just c/p some logs into a
bug report.

regards,
-mika-


signature.asc
Description: Digital signature

Bug#714092: installation-reports: wheezy install on QNAP TS-212 fails to write to flash

2013-06-27 Thread Mike Miller

On Wed, Jun 26, 2013 at 01:13:58 +0100, Ben Hutchings wrote:
 My reading of the m25p_probe() function is that if the named chip has a
 JEDEC ID, and the chip it finds has a different JEDEC ID that's also in
 the device ID table, it will then automatically adapt (but will warn).
 
 So long as the same partition map is used for the two chips, I think the
 platform code should just probe once as now, though the warning is
 annoying.  It seems like there ought to be a way to tell m25p80 to
 auto-detect and warn only if the size doesn't match the partition map.

FWIW, I successfully installed on this QNAP using a daily installer [1]
running 3.9-1-kirkwood. Here is the dmesg snippet probing the flash,
looks exactly like what you describe:

[8.328203] m25p80 spi0.0: found n25q128a13, expected m25p128
[8.334003] m25p80 spi0.0: n25q128a13 (16384 Kbytes)
[8.338989] Creating 6 MTD partitions on spi_flash:
[8.344074] 0x-0x0008 : U-Boot
[8.349708] 0x0020-0x0040 : Kernel
[8.355309] 0x0040-0x00d0 : RootFS1
[8.360987] 0x00d0-0x0100 : RootFS2
[8.366689] 0x0008-0x000c : U-Boot Config
[8.372895] 0x000c-0x0020 : NAS Config

[1] 
http://d-i.debian.org/daily-images/armel/20130625-08:44/kirkwood/network-console/qnap/ts-219/

-- 
mike


-- 
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/20130627131554.ga12...@xps14z.home.local

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with entry failed, hardware error 0x80000021

2013-06-27 Thread Stefan Pietsch

On 26.06.2013 12:47, Gleb Natapov wrote:
 On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
 On 24.06.2013 14:30, Gleb Natapov wrote:
 On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
 As soon as I remove kvmvapic.bin the virtual machine boots with
 qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
 emulate_invalid_guest_state=0 or emulate_invalid_guest_state=1 make
 no difference.

 Please send your patches.
 Here it is, run with it and kvmvapic.bin present. See what is printed in
 dmesg after the failure.


 diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
 index f4a5b3f..65488a4 100644
 --- a/arch/x86/kvm/vmx.c
 +++ b/arch/x86/kvm/vmx.c
 @@ -3385,6 +3385,7 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
  {
 struct vcpu_vmx *vmx = to_vmx(vcpu);
 u32 ar;
 +   unsigned long rip;
  
 if (vmx-rmode.vm86_active  seg != VCPU_SREG_LDTR) {
 *var = vmx-rmode.segs[seg];
 @@ -3408,6 +3409,9 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
 var-db = (ar  14)  1;
 var-g = (ar  15)  1;
 var-unusable = (ar  16)  1;
 +   rip = kvm_rip_read(vcpu);
 +   if ((rip == 0xc101611c || rip == 0xc101611a)  seg == VCPU_SREG_FS)
 +   printk(base=%p limit=%p selector=%x ar=%x\n, var-base, 
 var-limit, var-selector, ar);
  }
  
  static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)


 Booting kernel Linux 3.10-rc5 with your patch applied produces these
 messages in dmesg when starting a virtual machine:

 emulate_invalid_guest_state=0
 [  118.732151] base= limit=  (null) selector=ffff ar=0
 [  118.732341] base= limit=  (null) selector=ffff ar=0

 I've butchered printk format, but it gives me the idea of what is going
 on anyway. Can you try the patch below with
 emulate_invalid_guest_state=0|1?
 
 
 diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
 index f4a5b3f..eb062ce 100644
 --- a/arch/x86/kvm/vmx.c
 +++ b/arch/x86/kvm/vmx.c
 @@ -3395,19 +3395,20 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
   var-selector = vmx_read_guest_seg_selector(vmx, seg);
   return;
   }
 +
   var-base = vmx_read_guest_seg_base(vmx, seg);
   var-limit = vmx_read_guest_seg_limit(vmx, seg);
   var-selector = vmx_read_guest_seg_selector(vmx, seg);
   ar = vmx_read_guest_seg_ar(vmx, seg);
 + var-unusable = (ar  16)  1;
   var-type = ar  15;
   var-s = (ar  4)  1;
   var-dpl = (ar  5)  3;
 - var-present = (ar  7)  1;
 + var-present = !var-unusable;
   var-avl = (ar  12)  1;
   var-l = (ar  13)  1;
   var-db = (ar  14)  1;
   var-g = (ar  15)  1;
 - var-unusable = (ar  16)  1;
  }
  
  static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)


Kernel 3.10-rc5 with your latest patch applied can successfully boot the
virtual machine with emulate_invalid_guest_state 0 or 1.


-- 
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/51cc47ae.20...@sp.consulting.lsexperts.de

Bug#714287: linux-image-3.2.0-4-amd64: Add Support for Cirrus Logic 4213 Audio Chipset

2013-06-27 Thread Andrew Dorney

Package: src:linux
Version: 3.2.46-1
Severity: normal
Tags: patch

Dear Maintainer,

I recently purchased a Dell Insprion 13z laptop with a built-in Intel HDA sound
card. It was detected and works great, except for one issue - the automuting of
speakers when plugging in headphones doesn't work. Turns out that's because
Kernel 3.2 doesn't know about the 4213 chipset and treats it like its 4210
sibling (which doesn't quite work the same way).

This upstream patch added support for the 4213 chipset and was included in
Kernel 3.3:

http://git.kernel.org/cgit/linux/kernel/git/stable/linux-
stable.git/commit/?id=5660ffd06935e564404412997a703279e325fa64


After compiling and booting the 3.9 kernel from wheezy-backports, I can confirm
that my laptop automutes properly. Please consider backporting this upstream
patch to the 3.2 kernel.



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

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-4-amd64 root=/dev/mapper/prism-root ro quiet

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

** Kernel log:
[5.043771] Bluetooth: Core ver 2.16
[5.043786] NET: Registered protocol family 31
[5.043788] Bluetooth: HCI device and connection manager initialized
[5.043791] Bluetooth: HCI socket layer initialized
[5.043793] Bluetooth: L2CAP socket layer initialized
[5.043797] Bluetooth: SCO socket layer initialized
[5.061468] Bluetooth: Generic Bluetooth USB driver ver 0.6
[5.061612] usbcore: registered new interface driver btusb
[5.100071] input: Dell WMI hotkeys as /devices/virtual/input/input5
[5.150769] cfg80211: Calling CRDA to update world regulatory domain
[5.193578] snd_hda_intel :00:1b.0: irq 43 for MSI/MSI-X
[5.193620] snd_hda_intel :00:1b.0: setting latency timer to 64
[5.286050] [drm] Initialized drm 1.1.0 20060810
[5.551089] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:
[5.551094] Copyright(c) 2003-2011 Intel Corporation
[5.551227] iwlwifi :01:00.0: setting latency timer to 64
[5.551285] iwlwifi :01:00.0: pci_resource_len = 0x2000
[5.551290] iwlwifi :01:00.0: pci_resource_base = c967
[5.551295] iwlwifi :01:00.0: HW Revision ID = 0xC4
[5.551444] iwlwifi :01:00.0: irq 44 for MSI/MSI-X
[5.551525] iwlwifi :01:00.0: Detected 2000 Series 2x2 BGN/BT, REV=0xC8
[5.551637] iwlwifi :01:00.0: L1 Enabled; Disabling L0S
[5.568274] iwlwifi :01:00.0: device EEPROM VER=0x81c, CALIB=0x6
[5.568277] iwlwifi :01:00.0: Device SKU: 0X150
[5.568280] iwlwifi :01:00.0: Valid Tx ant: 0X3, Valid Rx ant: 0X3
[5.568315] iwlwifi :01:00.0: Tunable channels: 13 802.11bg, 0 802.11a 
channels
[5.681410] input: PS/2 Generic Mouse as 
/devices/platform/i8042/serio1/input/input6
[5.980141] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
[5.980330] input: HDA Intel PCH HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input7
[5.981019] i915 :00:02.0: setting latency timer to 64
[6.004694] iwlwifi :01:00.0: firmware: agent loaded 
iwlwifi-2030-6.ucode into memory
[6.004702] iwlwifi :01:00.0: loaded firmware version 18.168.6.1
[6.004972] Registered led device: phy0-led
[6.026193] i915 :00:02.0: irq 45 for MSI/MSI-X
[6.026201] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[6.026203] [drm] Driver supports precise vblank timestamp query.
[6.026749] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[6.050116] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[6.436994] [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off
[6.506192] cfg80211: World regulatory domain updated:
[6.506196] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[6.506199] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.506202] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[6.506205] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[6.506207] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.506210] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[6.701840] fbcon: inteldrmfb (fb0) is primary device
[6.754636] Linux media interface: v0.10
[6.830538] rts5139: module is from the staging directory, the quality is 
unknown, you have been warned.
[6.831724] Initializing rts5139 USB card reader driver...
[6.834869] scsi6 : SCSI emulation for RTS5139 USB card reader
[6.835161] usbcore: registered new interface driver rts5139
[6.835165] Realtek rts5139 USB card reader support registered.
[6.835242] scsi 6:0:0:0: Direct-Access Generic- xD/SD/M.S.

Bug#714295: linux-image-3.2.0-4-686-pae: ext4 on top of raid1. Frequent and serious data corruption issues

Package: src:linux
Version: 3.2.46-1
Severity: critical
Tags: upstream
Justification: causes serious data loss

Hi,

I'm experiencing frequent data corruption on my raid1 ext4 fs.
The error is not always the same.

I first thought it was due to a previous resize of the FS I've done.
I had multiple times some message about huge amount of multiply claimed blocks 
in inode .
fsck.ext4 was not working fully and was always ending with a message like FS 
still have error.
I was unable to copy all the files to another FS to save it.
So I end up checking the badblocks (that's where I've been dumb, I choose a non 
data conservative way).
However, badblock was succesful without errors.
So in the end I lost some data, however, I don't know if it's due to the bug or 
the the badblocks check. So feel free to readjust severity.

Since theni, I have bought two brand new disks, created a completly new ext4 
FS, and copied the files that I had succesfully recovered.
Then I run fsck.ext4 on the FS... it seems it is almost working.
I'm remounting the /dev/md0... And each time I start using the system 
seriously, I have new errors, like the one I had today:
(I was just copying files on it)

I'm currently going to move the remaining data I have to an ext3 FS.
However I'm leaving my one of my disks as it is so that we can debug it :)

I don't really know if it could be related to 
https://lkml.org/lkml/2012/10/23/690 or 
http://www.phoronix.com/scan.php?page=news_itempx=MTIxNDQ.

Let me know how I can help more.

[1374596.124050] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 5921)
[1374596.125031] CPU0: Core temperature/speed normal
[1374825.38] [Hardware Error]: Machine check events logged
[1374896.128061] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 8319)
[1374896.129092] CPU0: Core temperature/speed normal
[1374975.48] [Hardware Error]: Machine check events logged
[1375196.180050] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 13674)
[1375196.180960] CPU0: Core temperature/speed normal
[1375200.37] [Hardware Error]: Machine check events logged
[1375588.276057] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 16548)
[1375588.276909] CPU0: Core temperature/speed normal
[1375725.40] [Hardware Error]: Machine check events logged
[1375888.280046] CPU0: Core temperature above threshold, cpu clock throttled 
(total events = 23033)
[1375888.281129] CPU0: Core temperature/speed normal
[1376175.52] [Hardware Error]: Machine check events logged
[1436849.120036] EXT4-fs (md0): error count: 6
[1436849.120044] EXT4-fs (md0): initial error at 1371763084: 
htree_dirblock_to_tree:587: inode 20971803: block 83894316
[1436849.120054] EXT4-fs (md0): last error at 1371765809: 
htree_dirblock_to_tree:587: inode 41813096: block 167256110
[1446656.923648] EXT4-fs error (device md0): htree_dirblock_to_tree:587: inode 
#52698372: block 210773049: comm smbd: bad entry in directory: directory entry 
across blocks - offset=1052(9244), inode=1949184565, rec_len=29816, name_len=24
[1446692.729694] EXT4-fs error (device md0): htree_dirblock_to_tree:587: inode 
#59514149: block 238036040: comm smbd: bad entry in directory: directory entry 
across blocks - offset=1416(17800), inode=59514502, rec_len=29816, name_len=0
[1446733.264104] EXT4-fs error (device md0): htree_dirblock_to_tree:587: inode 
#51126667: block 204481618: comm find: bad entry in directory: directory entry 
across blocks - offset=2588(14876), inode=1949185078, rec_len=29816, 
name_len=232
[1446733.360346] EXT4-fs error (device md0): htree_dirblock_to_tree:587: inode 
#52168818: block 208675851: comm smbd: bad entry in directory: directory entry 
across blocks - offset=2588(6684), inode=1949185587, rec_len=29816, name_len=46
[1446738.872118] EXT4-fs error (device md0): htree_dirblock_to_tree:587: inode 
#52168818: block 208675851: comm find: bad entry in directory: directory entry 
across blocks - offset=2588(6684), inode=1949185587, rec_len=29816, name_len=46
[1446741.036110] EXT4-fs error (device md0): ext4_lookup:1050: inode #52436122: 
comm smbd: deleted inode referenced: 52436608
[1446741.048313] EXT4-fs error (device md0): ext4_lookup:1050: inode #52436122: 
comm smbd: deleted inode referenced: 52436607
[1446743.740081] EXT4-fs error (device md0): htree_dirblock_to_tree:587: inode 
#59514149: block 238036040: comm find: bad entry in directory: directory entry 
across blocks - offset=1416(17800), inode=59514502, rec_len=29816, name_len=0
[1446745.511445] EXT4-fs error (device md0): htree_dirblock_to_tree:587: inode 
#52698372: block 210773049: comm find: bad entry in directory: directory entry 
across blocks - offset=1052(9244), inode=1949184565, rec_len=29816, name_len=24
[1446770.143364] EXT4-fs error (device md0): htree_dirblock_to_tree:587: inode 
#51126667: block 204481618: comm find: bad entry in directory: directory entry 
across blocks

Processed: Re: Bug#714295: linux-image-3.2.0-4-686-pae: ext4 on top of raid1. Frequent and serious data corruption issues

Processing control commands:

 tag -1 moreinfo
Bug #714295 [src:linux] linux-image-3.2.0-4-686-pae: ext4 on top of raid1. 
Frequent and serious data corruption issues
Added tag(s) moreinfo.

-- 
714295: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714295
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.b714295.137235188118398.transcr...@bugs.debian.org

Bug#714295: linux-image-3.2.0-4-686-pae: ext4 on top of raid1. Frequent and serious data corruption issues

Control: tag -1 moreinfo

On Thu, Jun 27, 2013 at 06:06:06PM +0200, Martin Braure de Calignon wrote:
 Package: src:linux
 Version: 3.2.46-1
 Severity: critical
 Tags: upstream
 Justification: causes serious data loss
 
 Hi,
 
 I'm experiencing frequent data corruption on my raid1 ext4 fs.
 The error is not always the same.
[...]
 [1374596.124050] CPU0: Core temperature above threshold, cpu clock throttled 
 (total events = 5921)
 [1374596.125031] CPU0: Core temperature/speed normal
 [1374825.38] [Hardware Error]: Machine check events logged
[...]

This looks like a hardware fault.  If you install mcelog it will
decode these MCEs (machine check events) into /var/log/messages
which may provide a clue about what's going wrong.

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/20130627165114.gk4...@decadent.org.uk

Re: Bug report on nfs-common: nfsidmap crashes with exit status 139

2013-06-27 Thread Alexandre Rebert

Hi Ben,

On Wed, Jun 26, 2013 at 9:40 PM, Ben Hutchings b...@decadent.org.uk wrote:
 It's a bit late for that, as you sent mail to a public mailing list.

As I mentioned in the debian-devel thread, I realize only now that
many emails (about 20% in our case), that are listed as package
maintainers, are public mailing lists. That's unfortunate, but
hopefully most reported bugs will not be security critical.

 There does not seem to be any way to make the kernel invoke nfsidmap
 with an invalid option as used in the test case, and I don't see any
 reason for a user to invoke it directly with untrusted input.  So I
 don't think there is any security issue here.

That's a good point, and it looks like a majority of the crashes have
little security implications. The security tags will be removed before
submitting the report, unless advised otherwise by the package
maintainers.

Thanks,
Alex


-- 
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/CAF1AS2hHdOc+PT=OP4oDiiCcdGqBq25JTXua=g9-4sufelm...@mail.gmail.com

Bug#714295: linux-image-3.2.0-4-686-pae: ext4 on top of raid1. Frequent and serious data corruption issues

Le jeudi 27 juin 2013 à 17:51 +0100, Ben Hutchings a écrit :
 [...]
  [1374596.124050] CPU0: Core temperature above threshold, cpu clock 
  throttled (total events = 5921)
  [1374596.125031] CPU0: Core temperature/speed normal
  [1374825.38] [Hardware Error]: Machine check events logged
 [...]
 
 This looks like a hardware fault.  If you install mcelog it will
 decode these MCEs (machine check events) into /var/log/messages
 which may provide a clue about what's going wrong.

Thank you Ben,

So you think that this temperature stuff could be related to my ext4
problems?

Maybe I should just  clean the fan, and add another one, it's a pretty
old PC.

Here's the /var/log/mcelog content:


mcelog: failed to prefill DIMM database from DMI data
Kernel does not support page offline interface
mcelog: mcelog read: No such device
Hardware event. This is not a software error.
MCE 0
CPU 0 THERMAL EVENT TSC 89103c9e1e5ac 
TIME 1372136129 Tue Jun 25 06:55:29 2013
Processor 0 heated above trip temperature. Throttling enabled.
Please check your system cooling. Performance will be impacted
STATUS 3 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 1
CPU 0 THERMAL EVENT TSC 89103c9ff355e 
TIME 1372136129 Tue Jun 25 06:55:29 2013
Processor 0 below trip temperature. Throttling disabled
STATUS 2 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 2
CPU 0 THERMAL EVENT TSC 89186467abf3c 
TIME 1372136429 Tue Jun 25 07:00:29 2013
Processor 0 heated above trip temperature. Throttling enabled.
Please check your system cooling. Performance will be impacted
STATUS 3 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 3
CPU 0 THERMAL EVENT TSC 89186469938b8 
TIME 1372136429 Tue Jun 25 07:00:29 2013
Processor 0 below trip temperature. Throttling disabled
STATUS 2 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 4
CPU 0 THERMAL EVENT TSC 89208caa630a8 
TIME 1372136729 Tue Jun 25 07:05:29 2013
Processor 0 heated above trip temperature. Throttling enabled.
Please check your system cooling. Performance will be impacted
STATUS 3 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 5
CPU 0 THERMAL EVENT TSC 89208cac53248 
TIME 1372136729 Tue Jun 25 07:05:29 2013
Processor 0 below trip temperature. Throttling disabled
STATUS 2 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 6
CPU 0 THERMAL EVENT TSC 91f72ff7d78b0 
TIME 1372219966 Wed Jun 26 06:12:46 2013
Processor 0 heated above trip temperature. Throttling enabled.
Please check your system cooling. Performance will be impacted
STATUS 3 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 7
CPU 0 THERMAL EVENT TSC 91f72ff983458 
TIME 1372219966 Wed Jun 26 06:12:46 2013
Processor 0 below trip temperature. Throttling disabled
STATUS 2 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 8
CPU 0 THERMAL EVENT TSC 91ff57ab10e84 
TIME 1372220266 Wed Jun 26 06:17:46 2013
Processor 0 heated above trip temperature. Throttling enabled.
Please check your system cooling. Performance will be impacted
STATUS 3 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 9
CPU 0 THERMAL EVENT TSC 91ff57acd320e 
TIME 1372220266 Wed Jun 26 06:17:46 2013
Processor 0 below trip temperature. Throttling disabled
STATUS 2 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 10
CPU 0 THERMAL EVENT TSC 92077fb398eac 
TIME 1372220566 Wed Jun 26 06:22:46 2013
Processor 0 heated above trip temperature. Throttling enabled.
Please check your system cooling. Performance will be impacted
STATUS 3 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 11
CPU 0 THERMAL EVENT TSC 92077fb523454 
TIME 1372220566 Wed Jun 26 06:22:46 2013
Processor 0 below trip temperature. Throttling disabled
STATUS 2 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a software error.
MCE 12
CPU 0 THERMAL EVENT TSC 9212284292302 
TIME 1372220958 Wed Jun 26 06:29:18 2013
Processor 0 heated above trip temperature. Throttling enabled.
Please check your system cooling. Performance will be impacted
STATUS 3 MCGSTATUS 0
MCGCAP c0204 APICID 0 SOCKETID 0 
CPUID Vendor Intel Family 15 Model 1
Hardware event. This is not a

Re: Dropping support for the smallest armel machines

On Wed, Jun 26, 2013 at 04:39:15PM +0100, Ben Hutchings wrote:
 On Wed, Jun 26, 2013 at 03:13:48PM +0200, Arnaud Patard wrote:
  Ben Hutchings b...@decadent.org.uk writes:
  
   We have a recurring problem with building kernels for armel: three
   flavours (iop32x, ixp4xx, orion5x) require the kernel image size to be
   less than 1.4-1.5 MB in order to fit into a fixed flash partition.
  
   As more features continue to be added to Linux and cannot always
   configurable as a module, it is necessary to override and disable them
   on these three configurations[1].  I don't think this is sustainable
   unless someone who particularly cares about these older platforms steps
   up to take on this task.
  
   The iop32x and ixp4xx hardware appears to been discontinued in 2008.  If
   we remove these flavours now, they will still be supported in Debian 7
   until 2016.  I think 8 years of support is pretty good.
  
  btw, iop32x is used on n2100 which are used on buildd/porter boxes. If
  we stop supporting it, I'm not sure how the DSA people will react about
  that.
 [...]

Currently only 3 out of 10 are N2100s; the remainder are Marvell
development boards running the mv78xx0 flavour.

 Bet they're slower than QEMU versatile emulation on an x86.  And DSA
 loves virtual machines. :-)

This speed comparison might not be true, and I know people worry about
accuracy of emulation and being able to reproduce architecture-
specific bugs.

The other option that has been suggested repeatedly is to put armel
chroots on ARMv7 hardware.  Unaligned accesses behave differently on
v7, but they weren't consistent between different v5 implementations
(http://www.heyrick.co.uk/armwiki/Unaligned_data_access) so I don't
think this is critical.

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/20130627172205.gl4...@decadent.org.uk

Bug#709647: linux-source-3.2: USB 1.1 no longer works

2013-06-27 Thread Bjarni Ingi Gislason

  Your patch fixed the problem.  Thank you very mutch

-- 
Bjarni I. Gislason


-- 
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/20130627173042.ga7...@rhi.hi.is

Bug#714295: linux-image-3.2.0-4-686-pae: ext4 on top of raid1. Frequent and serious data corruption issues

On Thu, Jun 27, 2013 at 07:14:57PM +0200, Martin Braure de Calignon wrote:
[...]
 So you think that this temperature stuff could be related to my ext4
 problems?
[...]

Potentially.  As I understand it, current Intel desktop and mobile
processors may not be able to run all cores at full speed continuously
with a standard cooler.  The embedded controller can quickly adjust
the CPU frequency and voltage to keep it from overheating, but it
still depends on a properly functioning cooler.  If it does overheat
then this can certainly result in data corruption.

Are you overclocking the processor?

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/20130627173142.gm4...@decadent.org.uk

Bug#605275: marked as done (EeePC 1005HAG freezes briefly after resuming)

Your message dated Thu, 27 Jun 2013 19:42:18 +0200
with message-id 20130627174218.GC4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #605275,
regarding EeePC 1005HAG freezes briefly after resuming
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.)


-- 
605275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: eeepc-acpi-scripts
Version: 1.1.11

On the EeePC 1005HAG, the builtin 3G modem (12d1:1001 Huawei
Technologies Co., Ltd. E620 USB Modem) prevents the device from
staying in sleep mode. It goes to sleep fine, according to the logs,
but immediately wakes up. I suspected that the 3G modem is causing
this, because it seems to work for the models without built-in 3G,
according to various reports out there.

I tried putting the device to sleep after telling the kernel to ignore
USB wakeup requests from the 3G modem, and it works, apparently
without nasty side effects, the 3G still works after. I think
eeepc-acpi-scripts should include a sleep.d hook to do this. It's not
enough to set this once at boot, the flag resets itself when returning
from sleep mode. I've attached my own quick-hack attempt at doing
this, feel free to use it, use it as a template, or discard it and
write your own.


80_3Gmodem
Description: Binary data
---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older 
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with 
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by 
sending
a mail to cont...@bugs.debian.org with the following three commands included in 
the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
Moritz---End Message---

Bug#606250: marked as done (Architectures with frame pointers disabled have meaningless /proc//wchan, /proc//stack)

Your message dated Thu, 27 Jun 2013 19:42:18 +0200
with message-id 20130627174218.GC4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #606250,
regarding Architectures with frame pointers disabled have meaningless 
/proc/*/wchan, /proc/*/stack
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.)


-- 
606250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606250
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image
Version: 2.6.32-5-amd64

Hi,  Trying to debug ocfs2 issues, I noticed that the system.map file
doesn't match the kernel in the latest Squeeze version.  Here are my
findings:

# dpkg -S /boot/System.map-2.6.32-5-amd64 
linux-image-2.6.32-5-amd64: /boot/System.map-2.6.32-5-amd64
# dpkg -S /boot/vmlinuz-2.6.32-5-amd64 
linux-image-2.6.32-5-amd64: /boot/vmlinuz-2.6.32-5-amd64

So, both come from the same package.  The (2) machines have been
rebooted after the last kernel upgrade.  But ps -o
pid,wchan=WIDE-WCHAN-COLUMN only gives - or ? as wchan.  Telling
it explicitly which map to use gives:

# PS_SYSTEM_MAP=/boot/System.map-2.6.32-5-amd64 ps -o
pid,wchan=WIDE-WCHAN-COLUMN
Warning: /boot/System.map-2.6.32-5-amd64 has an incorrect kernel
version.
  PID WIDE-WCHAN-COLUMN
18887 -

Looks like a trivial bug, but I cannot find a report that indicates
it has been filed before.  Is there a way to fix this without
recompiling the kernel from scratch myself?

Thanks --- Jan



---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older 
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with 
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by 
sending
a mail to cont...@bugs.debian.org with the following three commands included in 
the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
Moritz---End Message---

Bug#607212: marked as done (uvcvideo webcam 174f:5a35 works randomly)

Your message dated Thu, 27 Jun 2013 19:42:51 +0200
with message-id 20130627174251.GD4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #607212,
regarding uvcvideo webcam 174f:5a35 works randomly
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.)


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

Subject: uvcvideo webcam 174f:5a35 works randomly
Package: uvcvideo
Severity: normal
Tags: upstream

My webcam, listed as ID 174f:5a35 Syntek Sonix 1.3MPixel USB 2.0 Camera, 
using

uvcvideo, does not work very well.

The behavior is really random:
- Show a green image at high resolution (640x480)
- Does not initialize at all
- Sometime, the image work but is not fluid at all

However, the webcam sometimes works good at 320x240 res and correctly at
640x480.
It worked OK when i was on Ubuntu 9.10 but the problem appeared on 
Ubuntu 10.04

(the same kernel as Debian 6.0).

How can i report more informations ?



-- System Information:
Debian Release: 6.0
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

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


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older 
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with 
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by 
sending
a mail to cont...@bugs.debian.org with the following three commands included in 
the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
Moritz---End Message---

Bug#605496: marked as done (linux-image-2.6.32-5-amd64: ipmi_si fails to load and block boot)

Your message dated Thu, 27 Jun 2013 19:42:18 +0200
with message-id 20130627174218.GC4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #605496,
regarding linux-image-2.6.32-5-amd64: ipmi_si fails to load and block boot
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.)


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

Coin,

My box was running 2.6.32-3-amd64 (2.6.32-9) when today a power outage
happened. Later, the boot blocked at the Loading kernel modules stage
with the modprobe command blocked when loading ipmi_si (i still could see
the blocked process after a Ctrl-C and having back a shell). It waited
more than an hour on this stage without any better result.

In the kernel logs i found:
Nov 30 13:34:14 Orfeo kernel: [   65.944753] ipmi message handler version 39.2
Nov 30 13:34:14 Orfeo kernel: [   65.947138] ipmi_si: Trying SMBIOS-specified 
kcs state machine at i/o address 0xca2, slave address 0x20, irq 0
Nov 30 13:34:14 Orfeo kernel: [  506.440019] ipmi_si: There appears to be no 
BMC at this location
Nov 30 13:36:09 Orfeo kernel: [  947.045526] ipmi_smic_drv: smic hosed: state = 
SMIC_OP_OK, status != SMIC_SC_SMS_READY
Nov 30 13:36:09 Orfeo kernel: [  947.097592] ipmi_si: Unable to find any System 
Interface(s)
Nov 30 13:36:09 Orfeo kernel: [  947.173857] ipmi device interface
Nov 30 15:59:16 Orfeo kernel: [   17.428166] ipmi message handler version 39.2
Nov 30 15:59:16 Orfeo kernel: [   17.430656] ipmi_si: Trying SMBIOS-specified 
kcs state machine at i/o address 0xca2, slave address 0x20, irq 0

dmidecode gives the following info on IPMI:
Handle 0x003F, DMI type 38, 16 bytes
IPMI Device Information
Interface Type: KCS (Keyboard Control Style)
Specification Version: 2.0
I2C Slave Address: 0x10
NV Storage Device Address: 0
Base Address: 0x0CA2 (I/O)

Even if a hardware problem is perhaps the cause, the module should not
block after not finding any device. Moreover, it looks at address 0x20,
while the SMBIOS reports 0x10 (via dmidecode), so the problem perhaps
lies here.

I may be able to test this module again using 2.6.32-3-amd64 in a few
weeks, but i had to restore services ASAP.

Regards.


-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-28) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 25 18:02:11 UTC 2010

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=b80fd3ab-f96b-4dec-b4d6-eab0551356fb ro

** Not tainted

** Kernel log:
[3.211052] usb-storage: device found at 3
[3.211054] usb-storage: waiting for device to settle before scanning
[7.826013] usb-storage: device scan complete
[7.832993] scsi 2:0:0:0: CD-ROMAMI  Virtual CDROM1.00 
PQ: 0 ANSI: 0 CCS
[7.899957] sr1: scsi-1 drive
[7.900247] sr 2:0:0:0: Attached scsi CD-ROM sr1
[7.900395] sr 2:0:0:0: Attached scsi generic sg1 type 5
[8.208081] usb-storage: device scan complete
[8.242922] scsi 3:0:0:0: Direct-Access AMI  Virtual Floppy   1.00 
PQ: 0 ANSI: 0 CCS
[8.243572] scsi 3:0:0:0: Attached scsi generic sg2 type 0
[8.677464] scsi4 : ioc0: LSISAS1064 A3, FwRev=0104h, Ports=1, MaxQ=511, 
IRQ=28
[8.702960] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 4, phy 
2, sas_addr 0x5000c527f4a1
[8.704769] scsi 4:0:0:0: Direct-Access SEAGATE  ST973401LSUN72G  0556 
PQ: 0 ANSI: 3
[8.707715] scsi 4:0:0:0: Attached scsi generic sg3 type 0
[8.710077] mptsas: ioc0: attaching ssp device: fw_channel 0, fw_id 3, phy 
3, sas_addr 0x5000c527f2b9
[8.711769] scsi 4:0:1:0: Direct-Access SEAGATE  ST973401LSUN72G  0556 
PQ: 0 ANSI: 3
[8.714672] scsi 4:0:1:0: Attached scsi generic sg4 type 0
[8.716977] mptsas: ioc0: attaching raid volume, channel 1, id 2
[8.718186] scsi 4:1:2:0: Direct-Access LSILOGIC Logical Volume   3000 
PQ: 0 ANSI: 2
[8.727166] sd 4:1:2:0: Attached scsi generic sg5 type 0
[8.727700] sd 4:1:2:0: [sdb] 142577664 512-byte logical blocks: (72.9 
GB/67.9 GiB)
[8.728148] sd 4:1:2:0: [sdb] Write Protect is off
[8.728259] sd 4:1:2:0: [sdb] Mode Sense: 03 00 00 08
[8.728746] sd 4:1:2:0: [sdb] Write cache: disabled, read cache: enabled, 
doesn't support DPO or FUA
[8.730205]  sdb: sdb1 sdb2 sdb3  sdb5 sdb6 sdb7 sdb8 sdb9 
[8.772689] sd 4:1:2:0: [sdb] Attached SCSI disk
[   11.986283] sd 3:0:0:0:

Bug#606889: marked as done (linux-2.6: Failed to load ngene (v4l driver) with error -5)

Your message dated Thu, 27 Jun 2013 19:42:18 +0200
with message-id 20130627174218.GC4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #606889,
regarding linux-2.6: Failed to load ngene (v4l driver) with error -5
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.)


-- 
606889: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606889
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: linux-image-2.6.32-5-xen-amd64
Severity: normal

The compiling of the v4l ngene driver is working without any problems, but 
loading the new module won't work. In dmesg i get the error -5.
[   22.641167] nGene PCIE bridge driver, Copyright (C) 2005-2007 Micronas
[   22.641336] ngene :00:01.0: enabling device ( - 0002)
[   22.641450] ngene :00:01.0: Xen PCI enabling IRQ: 16
[   22.641462]   alloc irq_desc for 16 on node 0
[   22.641467]   alloc kstat_irqs on node 0
[   22.641492] ngene: Found Linux4Media cineS2 DVB-S2 Twin Tuner (v5)
[   22.642176] ngene :00:01.0: setting latency timer to 64
[   22.642276] ngene: Device version 1
[   22.642333] ngene :00:01.0: firmware: requesting ngene_15.fw
[   22.682246] ngene: Loading firmware file ngene_15.fw.
[   24.692038] ngene: Command timeout cmd=11 prev=02
[   24.692055] host_to_ngene (c000): 01 f8 0e 00 00 00 00 00
[   24.692067] ngene_to_host (c100): 00 00 00 00 00 00 00 00
[   24.692078] dev-hosttongene (88003e88d000): 11 01 00 d0 00 04 00 00
[   24.692088] dev-ngenetohost (88003e88d100): 00 00 00 00 00 00 00 00
[   24.692249] ngene: probe of :00:01.0 failed with error -5


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-xen-amd64 (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older 
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with 
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by 
sending
a mail to cont...@bugs.debian.org with the following three commands included in 
the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
Moritz---End Message---

Bug#639618: marked as done (linux-image-2.6.32-5-686: events/0 using 33-66% cpu (system), missing keystrokes before or after gdm loads)

Your message dated Thu, 27 Jun 2013 19:41:22 +0200
with message-id 20130627174122.GA4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #639618,
regarding linux-image-2.6.32-5-686: events/0 using 33-66% cpu (system), 
missing keystrokes before or after gdm loads
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.)


-- 
639618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-35
Severity: important


Starting in the last day or so, events/0 has been using 33-66% cpu
as system activity.  The keyboard is missing keystrokes if I type
too many at one time and don't pause every few seconds for it to
catch up.  This happens even before I log into gdm, if I go to a
console with ctl-alt-F1 and log in as root after reboot, events is
already eating cpu and keystrokes are lost.  What's going on?

There was also a regression in squeeze recently with gnome-panel
with a bug where gnome panel fails to start or starts offscreen,
probably not related but thought I would mention it since this
but is so severe.

Thank you.

-Mark

-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-35) (da...@debian.org) (gcc version 
4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jun 13 04:13:06 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/sda7_crypt ro 
root=/dev/mapper/sda7_crypt ro heartbeat=300 rootdelay=4 quiet

** Not tainted

** Kernel log:
[   48.293940] apm: BIOS not found.
[   49.302982] Bluetooth: Core ver 2.15
[   49.303026] NET: Registered protocol family 31
[   49.303028] Bluetooth: HCI device and connection manager initialized
[   49.303030] Bluetooth: HCI socket layer initialized
[   49.502844] Bluetooth: L2CAP ver 2.14
[   49.502847] Bluetooth: L2CAP socket layer initialized
[   49.852236] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   49.852239] Bluetooth: BNEP filters: protocol multicast
[   50.079414] Bridge firewalling registered
[   50.179023] Bluetooth: SCO (Voice Link) ver 0.6
[   50.179026] Bluetooth: SCO socket layer initialized
[   52.471958] lp: driver loaded but no devices found
[   52.588934] ppdev: user-space parallel port driver
[   57.141392] thinkpad_acpi: setting the hotkey mask to 0x00ff is likely 
not the best way to go about it
[   57.141400] thinkpad_acpi: please consider using the driver defaults, and 
refer to up-to-date thinkpad-acpi documentation
[   57.245510] input: /usr/sbin/thinkpad-keys as /devices/virtual/input/input10
[  273.169737] wlan0: direct probe to AP 00:02:6f:68:e0:0b (try 1)
[  273.176377] wlan0: direct probe responded
[  273.176385] wlan0: authenticate with AP 00:02:6f:68:e0:0b (try 1)
[  273.179560] wlan0: authenticated
[  273.179598] wlan0: associate with AP 00:02:6f:68:e0:0b (try 1)
[  273.184137] wlan0: RX AssocResp from 00:02:6f:68:e0:0b (capab=0x421 status=0 
aid=1)
[  273.184144] wlan0: associated
[  273.188547] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[  283.520007] wlan0: no IPv6 routers present
[  306.238000] IPTLOG: IN=wlan0 OUT= 
MAC=ff:ff:ff:ff:ff:ff:e0:f8:47:14:a7:7e:08:00 SRC=192.168.1.78 
DST=255.255.255.255 LEN=160 TOS=0x00 PREC=0x00 TTL=64 ID=38184 PROTO=UDP 
SPT=17500 DPT=17500 LEN=140 
[  306.240288] IPTLOG: IN=wlan0 OUT= 
MAC=ff:ff:ff:ff:ff:ff:e0:f8:47:14:a7:7e:08:00 SRC=192.168.1.78 
DST=192.168.1.255 LEN=160 TOS=0x00 PREC=0x00 TTL=64 ID=6758 PROTO=UDP SPT=17500 
DPT=17500 LEN=140 
[  336.224948] IPTLOG: IN=wlan0 OUT= 
MAC=ff:ff:ff:ff:ff:ff:e0:f8:47:14:a7:7e:08:00 SRC=192.168.1.78 
DST=255.255.255.255 LEN=160 TOS=0x00 PREC=0x00 TTL=64 ID=45411 PROTO=UDP 
SPT=17500 DPT=17500 LEN=140 
[  336.226816] IPTLOG: IN=wlan0 OUT= 
MAC=ff:ff:ff:ff:ff:ff:e0:f8:47:14:a7:7e:08:00 SRC=192.168.1.78 
DST=192.168.1.255 LEN=160 TOS=0x00 PREC=0x00 TTL=64 ID=50283 PROTO=UDP 
SPT=17500 DPT=17500 LEN=140 
[  348.505046] wlan0: deauthenticating from 00:02:6f:68:e0:0b by local choice 
(reason=3)
[  348.519034] wlan0: direct probe to AP 00:02:6f:68:df:fb (try 1)
[  348.524332] wlan0: direct probe responded
[  348.524336] wlan0: authenticate with AP 00:02:6f:68:df:fb (try 1)
[  348.527408] wlan0: authenticated
[  348.527423] wlan0: associate with AP 00:02:6f:68:df:fb (try 1)
[  348.530412] wlan0: RX AssocResp from 00:02:6f:68:df:fb (capab=0x421 status=0 
aid=2)
[  348.530425] wlan0: associated
[  366.227231] IPTLOG: IN=wlan0 OUT= 
MAC=ff:ff:ff:ff:ff:ff:e0:f8:47:14:a7:7e:08:00 SRC=192.168.1.78 
DST=255.255.255.255 LEN=160 TOS=0x00 PREC=0x00 TTL=64 ID=2344 PROTO=UDP 
SPT=17500 DPT=17500 LEN=140 
[

Bug#639861: marked as done (xserver-xorg-video-nouveau: no backlight control for NV34 (GeForce 5200) on PPC)

Your message dated Thu, 27 Jun 2013 19:41:22 +0200
with message-id 20130627174122.GA4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #639861,
regarding xserver-xorg-video-nouveau: no backlight control for NV34 (GeForce 
5200) on PPC
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.)


-- 
639861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: xserver-xorg-video-nouveau
Version: 1:0.0.16+git20110411+8378443-1+b1
Severity: normal


There is no control of the backlight with the nouveau drivers on a 12
Aluminium G4 PowerBook (PPC). /sys/class/backlight/ is empty. I believe
this is why hibernation using the kernel's built-in facility isn't
working for me - the laptop does resume but the backlight, which is
switched off before shutdown, cannot be restarted and there is no manual
control of this, brightness etc. 

Before switching to nouveau, I did have control of the backlight.
(Unusable graphics but I could display them at any brightness!) That was
with an earlier kernel but makes me think this is specific to nouveau.
(Definitely not a hardware issue as works under OS X.)

This machine has a nVIDIA GeForce FX Go5200 graphics card with AGP bus,
64MB vram and 32 bit colour.

-- Package-specific info:
X server symlink status:

lrwxrwxrwx 1 root root 13 Apr 25 00:39 /etc/X11/X - /usr/bin/Xorg
-rwxr-xr-x 1 root root 1876124 Aug 24 10:56 /usr/bin/Xorg

VGA-compatible devices on PCI bus:
--
:00:10.0 VGA compatible controller [0300]: nVidia Corporation NV34M 
[GeForce FX Go5200] [10de:0329] (rev a1)

/etc/X11/xorg.conf does not exist.

/etc/X11/xorg.conf.d does not exist.

/etc/modprobe.d contains no KMS configuration files.

Kernel version (/proc/version):
---
Linux version 3.0.0-1-powerpc (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc 
version 4.5.3 (Debian 4.5.3-3) ) #1 Sun Jul 24 13:59:10 UTC 2011

Xorg X server log files on system:
--
-rw-r--r-- 1 root root 28135 Jul  5 23:11 /var/log/Xorg.1.log
-rw-r--r-- 1 root root 28992 Aug 30 23:21 /var/log/Xorg.0.log

Contents of most recent Xorg X server log file (/var/log/Xorg.0.log):
-
[24.932] 
X.Org X Server 1.10.4
Release Date: 2011-08-19
[24.932] X Protocol Version 11, Revision 0
[24.932] Build Operating System: Linux 2.6.32-5-powerpc64 ppc Debian
[24.932] Current Operating System: Linux CyfrifiadurCFR 3.0.0-1-powerpc #1 
Sun Jul 24 13:59:10 UTC 2011 ppc
[24.932] Kernel command line: 
root=UUID=18970ccd-6bfd-482f-9474-e15f7894edf4 ro video=nvidiafb:off 
[24.932] Build Date: 24 August 2011  09:38:35AM
[24.932] xorg-server 2:1.10.4-1 (Cyril Brulebois k...@debian.org) 
[24.932] Current version of pixman: 0.22.2
[24.932]Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
[24.932] Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[24.933] (==) Log file: /var/log/Xorg.0.log, Time: Tue Aug 30 23:06:14 
2011
[24.966] (==) Using system config directory /usr/share/X11/xorg.conf.d
[24.989] (==) No Layout section.  Using the first Screen section.
[24.989] (==) No screen section available. Using defaults.
[24.989] (**) |--Screen Default Screen Section (0)
[24.989] (**) |   |--Monitor default monitor
[24.989] (==) No monitor specified for screen Default Screen Section.
Using a default monitor configuration.
[24.989] (==) Automatically adding devices
[24.990] (==) Automatically enabling devices
[25.057] (WW) The directory /usr/share/fonts/X11/cyrillic does not exist.
[25.057]Entry deleted from font path.
[25.149] (==) FontPath set to:
/usr/share/fonts/X11/misc,
/usr/share/fonts/X11/100dpi/:unscaled,
/usr/share/fonts/X11/75dpi/:unscaled,
/usr/share/fonts/X11/Type1,
/usr/share/fonts/X11/100dpi,
/usr/share/fonts/X11/75dpi,
/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,
built-ins
[25.149] (==) ModulePath set to /usr/lib/xorg/modules
[25.149] (II) The server relies on udev to provide the list of input 
devices.
If no devices become available, reconfigure udev or disable 
AutoAddDevices.
[25.149] (II)

Bug#641288: marked as done (linux-image-2.6.32-5-686: Can not read appendable cdroms/dvds.)

Your message dated Thu, 27 Jun 2013 19:41:49 +0200
with message-id 20130627174149.GB4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #641288,
regarding linux-image-2.6.32-5-686: Can not read appendable cdroms/dvds.
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.)


-- 
641288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-35squeeze2
Severity: normal


Hi.
This bug continues bug 583949
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583949

I open a new bug report, as suggested there.

appendable cdroms/dvds can not be read.
Checked in 2.6.32-35squeeze2 and 2.6.39-bpo.2-686-pae (i686).

It is an external usb drive, so I tried to plug it in a different hole.
Last message is when I decided to put there a blank dvd.

Thanks.

[   16.314596] ip_tables: (C) 2000-2006 Netfilter Core Team
[   16.767449] cdrom: This disc doesn't have any tracks I recognize!
[   19.916303] sr 4:0:0:0: [sr1] Unhandled sense code
[   19.916309] sr 4:0:0:0: [sr1]  Result: hostbyte=invalid 
driverbyte=DRIVER_SENSE
[   19.916316] sr 4:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   19.916324] Info fld=0x0
[   19.916327] sr 4:0:0:0: [sr1]  vendor ASC=0xab ASCQ=0x80ASC=0xab 
vendor ASCQ=0x80
[   19.916339] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
[   19.916354] end_request: critical target error, dev sr1, sector 0
[   19.922336] Buffer I/O error on device sr1, logical block 0
[   19.928610] Buffer I/O error on device sr1, logical block 1
[   21.084109] sr 4:0:0:0: [sr1] Unhandled sense code
[   21.084115] sr 4:0:0:0: [sr1]  Result: hostbyte=invalid 
driverbyte=DRIVER_SENSE
[   21.084122] sr 4:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   21.084130] Info fld=0x0
[   21.084133] sr 4:0:0:0: [sr1]  vendor ASC=0xab ASCQ=0x80ASC=0xab 
vendor ASCQ=0x80
[   21.084145] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
[   21.084160] end_request: critical target error, dev sr1, sector 0
[   21.090334] Buffer I/O error on device sr1, logical block 0
[   21.096553] Buffer I/O error on device sr1, logical block 1
[   22.262538] sr 4:0:0:0: [sr1] Unhandled sense code
[   22.262545] sr 4:0:0:0: [sr1]  Result: hostbyte=invalid 
driverbyte=DRIVER_SENSE
[   22.262551] sr 4:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   22.262559] Info fld=0x2
[   22.262563] sr 4:0:0:0: [sr1]  vendor ASC=0xab ASCQ=0x80ASC=0xab 
vendor ASCQ=0x80
[   22.262575] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 02 00 00 02 00
[   22.262592] end_request: critical target error, dev sr1, sector 8
[   22.268897] Buffer I/O error on device sr1, logical block 2
[   22.275134] Buffer I/O error on device sr1, logical block 3
[   23.441082] sr 4:0:0:0: [sr1] Unhandled sense code
[   23.441087] sr 4:0:0:0: [sr1]  Result: hostbyte=invalid 
driverbyte=DRIVER_SENSE
[   23.441092] sr 4:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   23.441098] Info fld=0x2
[   23.441101] sr 4:0:0:0: [sr1]  vendor ASC=0xab ASCQ=0x80ASC=0xab 
vendor ASCQ=0x80
[   23.441110] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 02 00 00 02 00
[   23.441122] end_request: critical target error, dev sr1, sector 8
[   23.447200] Buffer I/O error on device sr1, logical block 2
[   23.453489] Buffer I/O error on device sr1, logical block 3
[   25.148170] cdrom: This disc doesn't have any tracks I recognize!
[   27.948827] sr 4:0:0:0: [sr1] Unhandled sense code
[   27.948832] sr 4:0:0:0: [sr1]  Result: hostbyte=invalid 
driverbyte=DRIVER_SENSE
[   27.948837] sr 4:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   27.948844] Info fld=0x0
[   27.948847] sr 4:0:0:0: [sr1]  vendor ASC=0xab ASCQ=0x80ASC=0xab 
vendor ASCQ=0x80
[   27.948856] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
[   27.948868] end_request: critical target error, dev sr1, sector 0
[   27.953782] Buffer I/O error on device sr1, logical block 0
[   27.958870] Buffer I/O error on device sr1, logical block 1
[   29.127272] sr 4:0:0:0: [sr1] Unhandled sense code
[   29.127277] sr 4:0:0:0: [sr1]  Result: hostbyte=invalid 
driverbyte=DRIVER_SENSE
[   29.127282] sr 4:0:0:0: [sr1]  Sense Key : Blank Check [current] 
[   29.127289] Info fld=0x0
[   29.127291] sr 4:0:0:0: [sr1]  vendor ASC=0xab ASCQ=0x80ASC=0xab 
vendor ASCQ=0x80
[   29.127301] sr 4:0:0:0: [sr1] CDB: Read(10): 28 00 00 00 00 00 00 00 02 00
[   29.127313] end_request: critical target error, dev sr1, sector 0
[   29.132203] Buffer I/O error on device sr1, logical block 0
[   29.137164]

Bug#641181: marked as done ([linux-2.6] black screen shortly after starting boot)

Your message dated Thu, 27 Jun 2013 19:41:49 +0200
with message-id 20130627174149.GB4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #641181,
regarding [linux-2.6] black screen shortly after starting boot
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.)


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

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

Hello,

I freshly installed wheezy with kernel linux 3.0.0-1-amd64 on my
Lenovo Thinkpad T400.
During boot, after the message Waiting for /dev being fully populated
is displayed, my screen turns first into flickery white lines
in the upper third of my screen and then (I bet after switching
to graphic mode) the screen is fully black. I tried several boot options
like fb=false and/or vga= ... with several modes but this didn't
helped. But my computer is running without screen because I can
remotely log in using ssh. Luckily, I installed the ssh-server during 
installation.

During the boot of the installation CD-ROM I had no problems.

Now, strange thing: I was playing a bit around after remote log in
and it turned out, that after installing the package 
firmware-linux-nonfree
from the non-free section, booting now works fine. I.e., I see all boot 
messages,

it switches to framebuffer mode and also switching to graphical mode at
the end of the boot sequence works. Thus I can work with my laptop again.

Btw., I verified by another fresh installation, that I only need the 
additional

package firmware-linux-nonfree from non-free.

My graphic hardware is (from lscpi -v):

01:00.0 VGA compatible controller: ATI Technologies Inc Mobility Radeon 
HD 3400 Series (prog-if 00 [VGA controller])

Subsystem: Lenovo Device 210e
Flags: bus master, fast devsel, latency 0, IRQ 48
Memory at d000 (32-bit, prefetchable) [size=256M]
I/O ports at 2000 [size=256]
Memory at cfff (32-bit, non-prefetchable) [size=64K]
[virtual] Expansion ROM at cff0 [disabled] [size=128K]
Capabilities: access denied
Kernel driver in use: fglrx_pci

remarks:
1. the Kernel driver fglrx_pci I installed later!
2. Also the (recovery mode) in the grub chooser showed the same behavior.

Bye

Ralf


--- System information. ---
Architecture: amd64
Kernel:   Linux 3.0.0-1-amd64

Debian Release: wheezy/sid
  500 testing security.debian.org
  500 testing ftp.uni-kl.de
  500 testing debian.uni-duisburg-essen.de

--- Package information. ---
Package's Depends field is empty.

Package's Recommends field is empty.

Package's Suggests field is empty.




---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older 
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with 
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by 
sending
a mail to cont...@bugs.debian.org with the following three commands included in 
the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
Moritz---End Message---

Bug#639438: marked as done (heavy NFS client usage triggers kernel BUGG on s390 (s390x))

Your message dated Thu, 27 Jun 2013 19:41:22 +0200
with message-id 20130627174122.GA4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #639438,
regarding heavy NFS client usage triggers kernel BUGG on s390 (s390x)
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.)


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

Hi,

heavy NFS client usage seems to trigger the kernel BUG below.  Fedora
seems to have encountered the same on s390x, and there's even a code
snippet identified, but the report timed out:
https://bugzilla.redhat.com/show_bug.cgi?id=508916

Kind regards
Philipp Kern

-- Package-specific info:
** Version:
Linux version 2.6.32-5-s390x (Debian 2.6.32-35) (da...@debian.org) (gcc version 
4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:22:54 UTC 2011

** Command line:
root=/dev/disk/by-path/ccw-0.0.5204-part2 BOOT_IMAGE=0

** Tainted: D (128)
 * Kernel has oopsed before.

** Kernel log:
[619921.521773] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[619921.521779] ffsb  D 00362ea4 0  3090   3060 0x0004
[619921.521787]    
 
[619921.521792] 0001 0001 
c9bcfc60 
[619921.521799]0001  fac9c830 
 
[619921.521806]0003 83897300 ffe40e70 
00368fd0 
[619921.521813]00368c20 00362090 c9bcfc60 
c9bcfd68 
[619921.521821] Call Trace:
[619921.521823] ([00362090] schedule+0xb0c/0xc30)
[619921.521836]  [00362ea4] __mutex_lock_slowpath+0xd4/0x14c
[619921.521844]  [003633a2] mutex_lock+0x4e/0x6c
[619921.521849]  [0012f54a] generic_file_llseek+0x36/0x74
[619921.521856]  [0012de98] SyS_llseek+0x68/0xd4
[619921.521864]  [000299e6] sysc_noemu+0x10/0x16
[619921.521872]  [77fca9ce] 0x77fca9ce
[622081.545953] INFO: task ffsb:3694 blocked for more than 120 seconds.
[622081.545961] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[622081.545967] ffsb  D 00362ea4 0  3694   3671 0x0004
[622081.545975] 83897368 003685d8 0003e60a 
018dbc20 
[622081.545981]018dbc20 ffcd0770 ffcd0770 
018dbc60 
[622081.545988]003685d8  fac9f380 
feebd238 
[622081.545995]0003 83897300 ffcd0738 
fac9f7a8 
[622081.546002]00368c20 00362090 018dbc60 
018dbd68 
[622081.546009] Call Trace:
[622081.546012] ([00362090] schedule+0xb0c/0xc30)
[622081.546025]  [00362ea4] __mutex_lock_slowpath+0xd4/0x14c
[622081.546032]  [003633a2] mutex_lock+0x4e/0x6c
[622081.546038]  [0012f54a] generic_file_llseek+0x36/0x74
[622081.546045]  [0012de98] SyS_llseek+0x68/0xd4
[622081.546052]  [000299e6] sysc_noemu+0x10/0x16
[622081.546061]  [77fca9ce] 0x77fca9ce
[622081.546083] INFO: task ffsb:3706 blocked for more than 120 seconds.
[622081.546086] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[622081.546091] ffsb  D 00362ea4 0  3706   3671 0x0004
[622081.546098] 83887368 003685d8 0003e60a 
3954bc20 
[622081.546104]3954bc20 ffcd0038 ffcd0038 
3954bc60 
[622081.546111]003685d8  fa9f40f8 
feebd238 
[622081.546118]0002 83887300 ffcd 
fa9f4520 
[622081.546125]00368c20 00362090 3954bc60 
3954bd68 
[622081.546132] Call Trace:
[622081.546134] ([00362090] schedule+0xb0c/0xc30)
[622081.546140]  [00362ea4] __mutex_lock_slowpath+0xd4/0x14c
[622081.546146]  [003633a2] mutex_lock+0x4e/0x6c
[622081.546152]  [0012f54a] generic_file_llseek+0x36/0x74
[622081.546157]  [0012de98] SyS_llseek+0x68/0xd4
[622081.546163]  [000299e6] sysc_noemu+0x10/0x16
[622081.546169]  [77fca9ce] 0x77fca9ce
[622081.546178] INFO: task ffsb:3729 blocked for more than 120 seconds.
[622081.546182] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables 
this message.
[622081.546187] ffsb

Bug#641008: marked as done (linux-image-2.6.32-5-amd64: X11 mouse dropping left on text console when switching VTs; doesn't go away )

Your message dated Thu, 27 Jun 2013 19:41:49 +0200
with message-id 20130627174149.GB4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #641008,
regarding linux-image-2.6.32-5-amd64: X11 mouse dropping left on text console 
when switching VTs; doesn't go away 
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.)


-- 
641008: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641008
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-35squeeze1
Severity: important

Switch away from Xorg when switched to use external monitor of
Arrandale.  X11 graphical mouse pointer left painted on text console no
matter which text VT you switch to.  Also, second montior left with X11
screen painted on it; console only appears on primary (closed laptop)
screen (when switching away in any other configuration leaves console on
both screens).  Switching to other (non-X) VTs does not remove the X
mouse pointer from screen.  Moving the mouse causes GPM mouse pointer to
do what it normally does, but X11 pointer still painted on text console
as well.  Happens every time when switching with second monitor in use
in a non-mirroring mode.  Will appear in a different place if you switch
back to X11 VT, move mouse, and switch back to console VT.

Having a pointer glued on your text console is a major distraction/
source of confusion for all users.


-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-35squeeze1) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Aug 31 16:50:35 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=b192ca9c-0897-46ac-9716-6da5f370e651 ro quiet

** Not tainted

** Kernel log:
[5.324665] loop: module loaded
[5.452782] ip_tables: (C) 2000-2006 Netfilter Core Team
[5.465727] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[5.465985] CONFIG_NF_CT_ACCT is deprecated and will be removed soon. Please 
use
[5.465987] nf_conntrack.acct=1 kernel parameter, acct=1 nf_conntrack module 
option or
[5.465989] sysctl net.netfilter.nf_conntrack_acct=1 to enable it.
[5.488561] ip6_tables: (C) 2000-2006 Netfilter Core Team
[5.491937] fuse init (API version 7.13)
[5.898449] lp: driver loaded but no devices found
[5.907428] ppdev: user-space parallel port driver
[6.096601] Bluetooth: L2CAP ver 2.14
[6.096603] Bluetooth: L2CAP socket layer initialized
[6.108987] Bluetooth: RFCOMM TTY layer initialized
[6.108994] Bluetooth: RFCOMM socket layer initialized
[6.108997] Bluetooth: RFCOMM ver 1.11
[6.111084] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[6.111088] Bluetooth: BNEP filters: protocol multicast
[6.122681] Bridge firewalling registered
[6.134260] Bluetooth: SCO (Voice Link) ver 0.6
[6.134262] Bluetooth: SCO socket layer initialized
[6.183517] iwlagn :03:00.0: firmware: requesting iwlwifi-1000-3.ucode
[6.196926] iwlagn :03:00.0: loaded firmware version 128.50.3.1
[6.282722] Registered led device: iwl-phy0::radio
[6.282744] Registered led device: iwl-phy0::assoc
[6.282760] Registered led device: iwl-phy0::RX
[6.282776] Registered led device: iwl-phy0::TX
[6.303304] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[6.305069] r8169: eth0: link down
[6.305600] ADDRCONF(NETDEV_UP): eth0: link is not ready
[6.334132] Ebtables v2.0 registered
[6.828775] input: ACPI Virtual Keyboard Device as 
/devices/virtual/input/input10
[7.022786] usb-storage: device scan complete
[7.025183] scsi 6:0:0:0: Direct-Access Generic- Multi-Card   1.00 
PQ: 0 ANSI: 0 CCS
[7.026034] sd 6:0:0:0: Attached scsi generic sg2 type 0
[7.031594] sd 6:0:0:0: [sdb] Attached SCSI removable disk
[7.425475] wlan0: direct probe to AP 00:1c:57:e3:be:d4 (try 1)
[7.427000] wlan0: direct probe responded
[7.427006] wlan0: authenticate with AP 00:1c:57:e3:be:d4 (try 1)
[7.428289] wlan0: authenticated
[7.428322] wlan0: associate with AP 00:1c:57:e3:be:d4 (try 1)
[7.430702] wlan0: RX AssocResp from 00:1c:57:e3:be:d4 (capab=0x31 status=0 
aid=6)
[7.430708] wlan0: associated
[7.433232] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[7.433324] cfg80211: Calling CRDA for country: US
[7.664841] padlock: VIA PadLock not detected.
[   10.654336] CPU0 attaching NULL sched-domain.
[   10.654343] CPU1 attaching NULL sched-domain.
[   10.654346] CPU2 attaching NULL sched-domain.
[   10.654349] CPU3 attaching NULL sched-domain.
[   10.684115]

Bug#640397: marked as done (linux-image-3.0.0-1-powerpc: No control of backlight (NV34, using nouveau))

Your message dated Thu, 27 Jun 2013 19:41:22 +0200
with message-id 20130627174122.GA4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #639861,
regarding linux-image-3.0.0-1-powerpc: No control of backlight (NV34, using 
nouveau)
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.)


-- 
639861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.0.0-3
Severity: normal


There is no backlight control. /sys/class/backlight is empty.

/sbin/fblevel reports:

ioctl PMU_IOC_GET_BACKLIGHT: Invalid argument
0

I *did* have backlight control in an earlier version but I am not sure
when I lost it. It might also be that I had not figured out how to get
nouveau loading correctly at the time. (Disabling nvidiafb via the
kernel command line configured via yaboot.conf proved necessary to
getting this working.)

I hope that I am finally filing this against the correct thing! 

Would be happy to provide any further information which might prove
useful.

-- Package-specific info:
** Version:
Linux version 3.0.0-1-powerpc (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc 
version 4.5.3 (Debian 4.5.3-8) ) #1 Sat Aug 27 17:07:06 UTC 2011

** Command line:
root=UUID=18970ccd-6bfd-482f-9474-e15f7894edf4 ro video=nvidiafb:off 

** Not tainted

** Kernel log:
[8.624803] [drm] No driver support for vblank timestamp query.
[8.625446] [drm] nouveau :00:10.0: Setting dpms mode 3 on lvds encoder 
(output 0)
[8.625467] [drm] nouveau :00:10.0: Calling LVDS script 1:
[8.625479] [drm] nouveau :00:10.0: 0x09F2: Parsing digital output 
script table
[8.625500] [drm] nouveau :00:10.0: Calling LVDS script 6:
[8.625511] [drm] nouveau :00:10.0: 0x0A6B: Parsing digital output 
script table
[9.113833] [drm] nouveau :00:10.0: Setting dpms mode 3 on tmds encoder 
(output 1)
[9.113854] [drm] nouveau :00:10.0: Setting dpms mode 3 on vga encoder 
(output 2)
[9.113870] [drm] nouveau :00:10.0: Setting dpms mode 3 on TV encoder 
(output 3)
[9.137871] irq: irq 30 on host 
/pci@f200/mac-io@17/interrupt-controller@4 mapped to virtual irq 30
[9.137908] irq: irq 1 on host 
/pci@f200/mac-io@17/interrupt-controller@4 mapped to virtual irq 21
[9.137925] irq: irq 2 on host 
/pci@f200/mac-io@17/interrupt-controller@4 mapped to virtual irq 31
[9.305419] usb 2-1: New USB device found, idVendor=05ac, idProduct=8205
[9.305449] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[9.319232] [drm] nouveau :00:10.0: allocated 1024x768 fb: 0x49000, bo 
c1999e00
[9.330205] [drm] nouveau :00:10.0: Calling LVDS script 2:
[9.330212] [drm] nouveau :00:10.0: 0x09F3: Parsing digital output 
script table
[9.345871] [drm] nouveau :00:10.0: Setting dpms mode 0 on lvds encoder 
(output 0)
[9.345876] [drm] nouveau :00:10.0: Calling LVDS script 5:
[9.345880] [drm] nouveau :00:10.0: 0x0A54: Parsing digital output 
script table
[9.345895] [drm] nouveau :00:10.0: Output LVDS-1 is running on CRTC 1 
using output C
[9.388647] Console: switching to colour frame buffer device 128x48
[9.390752] fb0: nouveaufb frame buffer device
[9.390765] drm: registered panic notifier
[9.390795] [drm] Initialized nouveau 0.0.16 20090420 for :00:10.0 on 
minor 0
[9.397111] snd-aoa-fabric-layout: Using PMF GPIOs
[9.535118] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
[9.589451] i2c i2c-0: aoa_codec_tas: attach_adapter method is deprecated
[9.589502] i2c i2c-0: Please use another way to instantiate your i2c_client
[9.589527] i2c i2c-1: aoa_codec_tas: attach_adapter method is deprecated
[9.589548] i2c i2c-1: Please use another way to instantiate your i2c_client
[9.589591] i2c i2c-2: aoa_codec_tas: attach_adapter method is deprecated
[9.589613] i2c i2c-2: Please use another way to instantiate your i2c_client
[9.589637] snd-aoa-codec-tas: found tas3004
[9.619597] snd-aoa-fabric-layout: can use this codec
[9.686674] irq: irq 61 on host 
/pci@f200/mac-io@17/interrupt-controller@4 mapped to virtual irq 61
[9.686713] snd-aoa-codec-tas: tas found, addr 0x35 on 
/pci@f200/mac-io@17/i2c@18000/i2c-bus@0/codec@6a
[9.686732] i2c i2c-3: aoa_codec_tas: attach_adapter method is deprecated
[9.686779] i2c i2c-3: Please use another way to instantiate your i2c_client
[9.686810] i2c i2c-4: aoa_codec_tas: attach_adapter method is

Bug#640972: marked as done (linux-image-2.6.32-5-amd64: SATA errors every ~30sec ata##: hard resetting link... SATA link down (SStatus 0 SControl 300/310)... EH Complete)

Your message dated Thu, 27 Jun 2013 19:41:49 +0200
with message-id 20130627174149.GB4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #640972,
regarding linux-image-2.6.32-5-amd64: SATA errors every ~30sec ata##: hard 
resetting link... SATA link down (SStatus 0 SControl 300/310)... EH Complete
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.)


-- 
640972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-35squeeze1
Severity: normal



-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-35squeeze1) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed Aug 31 16:50:35 UTC 2011

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=b192ca9c-0897-46ac-9716-6da5f370e651 ro quiet

** Not tainted

** Kernel log:
[ 2411.101196] ata10: SATA link down (SStatus 0 SControl 310)
[ 2411.101209] ata10: EH complete
[ 2411.718853] ata10: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[ 2411.718857] ata10: irq_stat 0x0040, connection status changed
[ 2411.718862] ata10: SError: { CommWake DevExch }
[ 2411.718873] ata10: limiting SATA link speed to 1.5 Gbps
[ 2411.718876] ata10: hard resetting link
[ 2412.950097] ata10: SATA link down (SStatus 0 SControl 310)
[ 2412.950112] ata10: EH complete
[ 2413.857351] ata10: exception Emask 0x10 SAct 0x0 SErr 0x404 action 0xe 
frozen
[ 2413.857356] ata10: irq_stat 0x0040, connection status changed
[ 2413.857361] ata10: SError: { CommWake DevExch }
[ 2413.857373] ata10: limiting SATA link speed to 1.5 Gbps
[ 2413.857378] ata10: hard resetting link
[ 2414.579372] ata10: SATA link down (SStatus 0 SControl 310)
[ 2414.579386] ata10: EH complete
[ 2415.807394] ata10: exception Emask 0x10 SAct 0x0 SErr 0x406 action 0xe 
frozen
[ 2415.807399] ata10: irq_stat 0x0040, connection status changed
[ 2415.807404] ata10: SError: { PHYInt CommWake DevExch }
[ 2415.807415] ata10: limiting SATA link speed to 1.5 Gbps
[ 2415.807420] ata10: hard resetting link
[ 2416.528134] ata10: SATA link down (SStatus 0 SControl 310)
[ 2416.528147] ata10: EH complete
[ 2418.224551] ata10: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe 
frozen
[ 2418.224556] ata10: irq_stat 0x0040, connection status changed
[ 2418.224560] ata10: SError: { DevExch }
[ 2418.224572] ata10: limiting SATA link speed to 1.5 Gbps
[ 2418.224576] ata10: hard resetting link
[ 2418.944101] ata10: SATA link down (SStatus 0 SControl 310)
[ 2418.944114] ata10: EH complete
[ 2421.490645] ata10: exception Emask 0x10 SAct 0x0 SErr 0x400 action 0xe 
frozen
[ 2421.490653] ata10: irq_stat 0x0040, connection status changed
[ 2421.490659] ata10: SError: { DevExch }
[ 2421.490675] ata10: limiting SATA link speed to 1.5 Gbps
[ 2421.490682] ata10: hard resetting link
[ 2423.748004] ata10: COMRESET failed (errno=-32)
[ 2423.748017] ata10: reset failed (errno=-32), retrying in 8 secs
[ 2431.471110] ata10: hard resetting link
[ 2433.920030] ata10: COMRESET failed (errno=-32)
[ 2433.920046] ata10: reset failed (errno=-32), retrying in 8 secs
[ 2441.455447] ata10: hard resetting link
[ 2444.158959] ata10: SATA link down (SStatus 0 SControl 310)
[ 2444.158977] ata10: EH complete
[ 2444.189028] ata10: exception Emask 0x10 SAct 0x0 SErr 0x406 action 0xe 
frozen
[ 2444.189035] ata10: irq_stat 0x0040, connection status changed
[ 2444.189042] ata10: SError: { PHYInt CommWake DevExch }
[ 2444.189058] ata10: limiting SATA link speed to 1.5 Gbps
[ 2444.189064] ata10: hard resetting link
[ 2446.446609] ata10: COMRESET failed (errno=-32)
[ 2446.446625] ata10: reset failed (errno=-32), retrying in 8 secs
[ 2454.170709] ata10: hard resetting link
[ 2455.727137] ata10: SATA link down (SStatus 0 SControl 310)
[ 2455.727155] ata10: EH complete
[ 2455.727515] ata10: exception Emask 0x10 SAct 0x0 SErr 0x406 action 0xe 
frozen
[ 2455.727522] ata10: irq_stat 0x0040, connection status changed
[ 2455.727529] ata10: SError: { PHYInt CommWake DevExch }
[ 2455.727546] ata10: limiting SATA link speed to 1.5 Gbps
[ 2455.727552] ata10: hard resetting link
[ 2457.947912] ata10: COMRESET failed (errno=-32)
[ 2457.947927] ata10: reset failed (errno=-32), retrying in 8 secs
[ 2465.706954] ata10: hard resetting link
[ 2467.995139] ata10: COMRESET failed (errno=-32)
[ 2467.995154] ata10: reset failed (errno=-32), retrying in 8 secs
[ 2475.690283] ata10: hard resetting link
[ 2478.042385] ata10: COMRESET failed (errno=-32)
[

Bug#643629: marked as done (linux-image-2.6.39-bpo.2-amd64: in syslog is a kernel BUG reported)

Your message dated Thu, 27 Jun 2013 19:42:18 +0200
with message-id 20130627174218.GC4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #643629,
regarding linux-image-2.6.39-bpo.2-amd64: in syslog is a kernel BUG reported
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.)


-- 
643629: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643629
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.39-3~bpo60+1
Severity: normal

This kernel BUG shown in the syslog, and i don't know how critical it is for my 
file server.
google also don't know anything about this bug.


-- Package-specific info:
** Version:
Linux version 2.6.39-bpo.2-amd64 (Debian 2.6.39-3~bpo60+1) 
(norb...@tretkowski.de) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Tue Jul 26 
10:35:23 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.39-bpo.2-amd64 root=/dev/mapper/atsambas1hg-root ro 
quiet

** Tainted: D (128)
 * Kernel has oopsed before.

** Kernel log:
[345440.323118] ocfs2: Unmounting device (147,1) on (node 0)
[345552.315417] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 
[345552.557444] ocfs2: Mounting device (147,1) on (node 0, slot 0) with 
writeback data mode.
[345570.309183] ocfs2: Unmounting device (147,1) on (node 0)
[345596.619186] ocfs2: Unregistered cluster interface o2cb
[345622.701066] OCFS2 Node Manager 1.5.0
[345622.769391] OCFS2 DLM 1.5.0
[345622.771106] ocfs2: Registered cluster interface o2cb
[345622.780612] OCFS2 DLMFS 1.5.0
[345622.780750] OCFS2 User DLM kernel interface loaded
[345632.645613] OCFS2 1.5.0
[345632.728529] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 
[345632.811743] ocfs2: Mounting device (147,1) on (node 0, slot 0) with 
writeback data mode.
[345849.580515] o2net: accepted connection from node atsambas1umb (num 1) at 
10.43.202.57:
[345853.728557] o2dlm: Node 1 joins domain B5E583B70A5F4EB4AA24A21924F31D25
[345853.728561] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 1 
[349851.770879] svc: failed to register lockdv1 RPC service (errno 97).
[349851.770923] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery 
directory
[349851.777649] NFSD: starting 90-second grace period
[502217.997960] o2dlm: Node 1 leaves domain B5E583B70A5F4EB4AA24A21924F31D25
[502218.005748] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 
[502219.633035] o2net: connection to node atsambas1umb (num 1) at 
10.43.202.57: shutdown, state 8
[502219.633069] o2net: no longer connected to node atsambas1umb (num 1) at 
10.43.202.57:
[502401.628983] nfsd: last server has exited, flushing export cache
[502413.189084] ocfs2: Unmounting device (147,1) on (node 0)
[502465.599503] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 
[517372.514655] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 
[517372.629262] ocfs2: Mounting device (147,1) on (node 0, slot 0) with 
writeback data mode.
[517386.090971] o2net: accepted connection from node atsambas1umb (num 1) at 
10.43.202.57:
[517390.137223] o2dlm: Node 1 joins domain B5E583B70A5F4EB4AA24A21924F31D25
[517390.137226] o2dlm: Nodes in domain B5E583B70A5F4EB4AA24A21924F31D25: 0 1 
[517436.066849] svc: failed to register lockdv1 RPC service (errno 97).
[517436.066956] NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery 
directory
[517436.074355] NFSD: starting 90-second grace period
[606232.120297] usb 2-1: USB disconnect, device number 2
[673265.851132] CIFS VFS: Server 10.43.28.102 has not responded in 300 seconds. 
Reconnecting...
[673265.851226] CIFS VFS: Unexpected lookup error -112
[673285.841033] CIFS VFS: Unexpected lookup error -112
[673305.830989] CIFS VFS: Unexpected lookup error -112
[673325.820957] CIFS VFS: Unexpected lookup error -112
[673345.810915] CIFS VFS: Unexpected lookup error -112
[673365.800912] CIFS VFS: Unexpected lookup error -112
[673385.790844] CIFS VFS: Unexpected lookup error -112
[673405.780807] CIFS VFS: Unexpected lookup error -112
[673425.770768] CIFS VFS: Unexpected lookup error -112
[673445.760736] CIFS VFS: Unexpected lookup error -112
[673465.750691] CIFS VFS: Unexpected lookup error -112
[673485.740683] CIFS VFS: Unexpected lookup error -112
[942581.750153] CIFS VFS: Unexpected lookup error -112
[942611.791039] CIFS VFS: Unexpected lookup error -112
[942621.899688] CIFS VFS: Unexpected lookup error -112
[942651.883038] CIFS VFS: Unexpected lookup error -112
[942681.867940] CIFS VFS: Unexpected lookup error -112
[942711.852940] CIFS VFS: Unexpected lookup error -112
[944538.385523]

Bug#641429: marked as done (/usr/bin/sensors: sensors report the wrong cpu temperature on intel atom 330)

Your message dated Thu, 27 Jun 2013 19:41:49 +0200
with message-id 20130627174149.GB4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #641429,
regarding /usr/bin/sensors: sensors report the wrong cpu temperature on intel 
atom 330
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.)


-- 
641429: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641429
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: lm-sensors
Version: 1:3.1.2-6
Severity: normal
File: /usr/bin/sensors

on my intel atom 330 system sensors always reports the cpu temp as +1.0 C, and 
it never changes.
This problem only occurred when I upgraded to squeeze, on the previous stable 
version the temps
 reported correctly.

I'm not sure if this is a kernel isssue or just sensors. 

-- System Information:
Debian Release: 6.0.2
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages lm-sensors depends on:
ii  libc6  2.11.2-10 Embedded GNU C Library: Shared lib
ii  libsensors41:3.1.2-6 library to read temperature/voltag
ii  lsb-base   3.2-23.2squeeze1  Linux Standard Base 3.2 init scrip
ii  perl   5.10.1-17squeeze2 Larry Wall's Practical Extraction 
ii  sed4.2.1-7   The GNU sed stream editor

Versions of packages lm-sensors recommends:
ii  fancontrol1:3.1.2-6  utilities to read temperature/volt

Versions of packages lm-sensors suggests:
pn  i2c-tools none (no description available)
pn  read-edid none (no description available)
pn  sensord   none (no description available)

-- no debconf information


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older 
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with 
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by 
sending
a mail to cont...@bugs.debian.org with the following three commands included in 
the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
Moritz---End Message---

Bug#656636: marked as done (linux-image-3.2.0-1-686-pae: alsa Master channel doesn't change volume)

Your message dated Thu, 27 Jun 2013 19:42:51 +0200
with message-id 20130627174251.GD4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #656636,
regarding linux-image-3.2.0-1-686-pae: alsa Master channel doesn't change volume
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.)


-- 
656636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.1-1
Severity: normal



-- Package-specific info:
** Version:
Linux version 3.2.0-1-686-pae (Debian 3.2.1-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Thu Jan 19 10:56:51 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-1-686-pae 
root=UUID=964dc7d2-0272-46b9-833e-25b718674046 ro quiet

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

** Kernel log:
[   12.039833] hda_intel: msi for device 1043:81f2 set to 0
[   12.039855] snd_hda_intel :00:0f.1: setting latency timer to 64
[   12.207553] 3:3:1: cannot get freq at ep 0x84
[   12.209080] usbcore: registered new interface driver snd-usb-audio
[   12.942083] hda_codec: AD1988B: BIOS auto-probing.
[   12.942187] input: HDA Digital PCBeep as 
/devices/pci:00/:00:0f.1/input/input7
[   13.826836] Disabling lock debugging due to kernel taint
[   13.826842] nvidia: module license 'NVIDIA' taints kernel.
[   14.177299] ACPI: PCI Interrupt Link [APC5] enabled at IRQ 16
[   14.177305] nvidia :01:00.0: PCI INT A - Link[APC5] - GSI 16 (level, 
low) - IRQ 16
[   14.177312] nvidia :01:00.0: setting latency timer to 64
[   14.177317] vgaarb: device changed decodes: 
PCI::01:00.0,olddecodes=io+mem,decodes=none:owns=io+mem
[   14.177500] NVRM: loading NVIDIA UNIX x86 Kernel Module  290.10  Wed Nov 16 
19:27:25 PST 2011
[   15.378447] Adding 1054804k swap on /dev/sda4.  Priority:-1 extents:1 
across:1054804k 
[   15.381800] EXT4-fs (sda2): re-mounted. Opts: (null)
[   15.986045] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[   16.138480] device-mapper: uevent: version 1.0.3
[   16.138556] device-mapper: ioctl: 4.22.0-ioctl (2011-10-19) initialised: 
dm-de...@redhat.com
[   20.707801] loop: module loaded
[   22.223516] EXT4-fs (sda6): mounted filesystem with ordered data mode. Opts: 
(null)
[   22.270150] EXT4-fs (sda5): mounted filesystem with ordered data mode. Opts: 
(null)
[   22.385649] fuse init (API version 7.17)
[   22.686601] EXT4-fs (sda7): mounted filesystem with ordered data mode. Opts: 
(null)
[   22.798422] EXT4-fs (sda8): mounted filesystem with ordered data mode. Opts: 
(null)
[   26.388354] ip_tables: (C) 2000-2006 Netfilter Core Team
[   26.429801] nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
[   26.557767] forcedeth :00:11.0: irq 43 for MSI/MSI-X
[   26.559468] forcedeth :00:12.0: irq 44 for MSI/MSI-X
[   26.559662] forcedeth :00:12.0: eth1: no link during initialization
[   26.560209] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   27.103047] RPC: Registered named UNIX socket transport module.
[   27.103049] RPC: Registered udp transport module.
[   27.103051] RPC: Registered tcp transport module.
[   27.103053] RPC: Registered tcp NFSv4.1 backchannel transport module.
[   27.148083] FS-Cache: Loaded
[   27.193979] FS-Cache: Netfs 'nfs' registered for caching
[   27.216750] Installing knfsd (copyright (C) 1996 o...@monad.swb.de).
[   35.233177] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   35.233180] Bluetooth: BNEP filters: protocol multicast
[   35.279002] Bluetooth: RFCOMM TTY layer initialized
[   35.279009] Bluetooth: RFCOMM socket layer initialized
[   35.279011] Bluetooth: RFCOMM ver 1.11
[   36.384205] lp: driver loaded but no devices found
[   36.394562] ppdev: user-space parallel port driver
[   37.040004] eth0: no IPv6 routers present
[   50.854445] 3:3:1: cannot get freq at ep 0x84
[   50.884571] 3:3:1: cannot get freq at ep 0x84
[   66.379650] 3:3:1: cannot get freq at ep 0x84
[   66.409789] 3:3:1: cannot get freq at ep 0x84
[   95.383256] Bluetooth: HIDP (Human Interface Emulation) ver 1.2

** Model information
not available

** Loaded modules:
hidp
parport_pc
ppdev
lp
parport
cpufreq_userspace
cpufreq_powersave
cpufreq_conservative
cpufreq_stats
rfcomm
bnep
binfmt_misc
xt_limit
xt_tcpudp
nfsd
nfs
lockd
fscache
auth_rpcgss
nfs_acl
sunrpc
ipt_LOG
ipt_MASQUERADE
xt_DSCP
ipt_REJECT
nf_conntrack_irc
nf_conntrack_ftp
xt_state
iptable_nat
nf_nat
nf_conntrack_ipv4
nf_conntrack
nf_defrag_ipv4
iptable_mangle
iptable_filter
ip_tables
x_tables
fuse
mperf

Bug#642025: marked as done ((r8169): transmit queue 0 timed out)

Your message dated Thu, 27 Jun 2013 19:41:49 +0200
with message-id 20130627174149.GB4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #642025,
regarding (r8169): transmit queue 0 timed out
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.)


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

Package: linux-image-3.0.0-1-amd64
Version: 3.0.0-2

Sep 18 19:47:12 localhost kernel: [949402.396510] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:13 localhost kernel: [949403.402626] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:14 localhost kernel: [949404.340850] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:15 localhost kernel: [949405.287085] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:16 localhost kernel: [949406.492816] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:18 localhost kernel: [949408.620813] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:19 localhost kernel: [949410.078073] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:22 localhost kernel: [949412.345802] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:24 localhost kernel: [949414.745190] [ cut here 
]
Sep 18 19:47:24 localhost kernel: [949414.745200] WARNING: at 
/build/buildd-linux-2.6_3.0.0-2-amd64-9iQzxp/linux-2.6-3.0.0/debian/build/source_amd64_none/net/

sched/sch_generic.c:255 dev_watchdog+0xe9/0x148()
Sep 18 19:47:24 localhost kernel: [949414.745204] Hardware name: Z68P-DS3
Sep 18 19:47:24 localhost kernel: [949414.745206] NETDEV WATCHDOG: eth0 
(r8169): transmit queue 0 timed out
Sep 18 19:47:24 localhost kernel: [949414.745208] Modules linked in: xfs 
netconsole configfs aufs(C) loop i915 drm_kms_helper drm evdev snd_pcm 
i2c_i801 i2c_a
lgo_bit video processor snd_timer shpchp pci_hotplug serio_raw i2c_core 
thermal_sys button snd soundcore snd_page_alloc pcspkr ext4 mbcache jbd2 
crc16 raid1 m
d_mod sg sd_mod crc_t10dif ehci_hcd usbcore ahci libahci r8169 mii 
libata scsi_mod [last unloaded: scsi_wait_scan]
Sep 18 19:47:24 localhost kernel: [949414.745250] Pid: 0, comm: swapper 
Tainted: G C   3.0.0-1-amd64 #1

Sep 18 19:47:24 localhost kernel: [949414.745252] Call Trace:
Sep 18 19:47:24 localhost kernel: [949414.745253]  IRQ 
[81046521] ? warn_slowpath_common+0x78/0x8c
Sep 18 19:47:24 localhost kernel: [949414.745261]  [810465d6] 
? warn_slowpath_fmt+0x45/0x4a
Sep 18 19:47:24 localhost kernel: [949414.745263]  [812953d4] 
? netif_tx_lock+0x43/0x77
Sep 18 19:47:24 localhost kernel: [949414.745266]  [8129553d] 
? dev_watchdog+0xe9/0x148
Sep 18 19:47:24 localhost kernel: [949414.745269]  [81052b04] 
? run_timer_softirq+0x1bf/0x28a
Sep 18 19:47:24 localhost kernel: [949414.745272]  [8104c0ad] 
? raise_softirq_irqoff+0x9/0x2e
Sep 18 19:47:24 localhost kernel: [949414.745275]  [81295454] 
? netif_tx_unlock+0x4c/0x4c
Sep 18 19:47:24 localhost kernel: [949414.745278]  [81066feb] 
? timekeeping_get_ns+0xd/0x2a
Sep 18 19:47:24 localhost kernel: [949414.745281]  [8104bdd4] 
? __do_softirq+0xb9/0x178
Sep 18 19:47:24 localhost kernel: [949414.745284]  [8133cf1c] 
? call_softirq+0x1c/0x30
Sep 18 19:47:24 localhost kernel: [949414.745287]  [8100a9ef] 
? do_softirq+0x3f/0x84
Sep 18 19:47:24 localhost kernel: [949414.745289]  [8104c040] 
? irq_exit+0x3f/0xa3
Sep 18 19:47:24 localhost kernel: [949414.745293]  [8101f51e] 
? smp_apic_timer_interrupt+0x76/0x86
Sep 18 19:47:24 localhost kernel: [949414.745296]  [8133c6d3] 
? apic_timer_interrupt+0x13/0x20
Sep 18 19:47:24 localhost kernel: [949414.745297]  EOI 
[810632f9] ? hrtimer_get_next_event+0x7b/0x93
Sep 18 19:47:24 localhost kernel: [949414.745304]  [a01a1400] 
? arch_local_irq_enable+0x4/0x8 [processor]
Sep 18 19:47:24 localhost kernel: [949414.745307]  [a01a1fcb] 
? acpi_idle_enter_bm+0x218/0x250 [processor]
Sep 18 19:47:24 localhost kernel: [949414.745311]  [812658b4] 
? cpuidle_idle_call+0xf5/0x180
Sep 18 19:47:24 localhost kernel: [949414.745313]  [8100827e] 
? cpu_idle+0xa2/0xc4
Sep 18 19:47:24 localhost kernel: [949414.745316]  [8169fb65] 
? start_kernel+0x3bd/0x3c8
Sep 18 19:47:24 localhost kernel: [949414.745319]  [8169f3c6] 
? x86_64_start_kernel+0x102/0x10f
Sep 18 19:47:24 localhost kernel: [949414.745321] ---[ end trace 
1225d595a5acca84 ]---
Sep 18 19:47:24 localhost kernel: [949414.753274] r8169 :02:00.0: 
eth0: link up
Sep 18 19:47:26 localhost kernel:

Bug#655944: marked as done (linux-image-3.1.0-1-amd64: Kernel threads use significant amount of CPU)

Your message dated Thu, 27 Jun 2013 19:42:51 +0200
with message-id 20130627174251.GD4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #655944,
regarding linux-image-3.1.0-1-amd64: Kernel threads use significant amount of 
CPU
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.)


-- 
655944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655944
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.1.8-2
Severity: normal

On my laptop, kernel threads use somewhere between 25% - 80% of one of the
CPUs, even on idle.
At the suggestion of a friend, I looked at the contents of
/sys/firmware/acpi/interrupts/, and noticed that gpe18 was rising at about
10 a second.
Searching through the standard logfiles didn't show anything related to gpe18,
however looking through the installation logs, I found this line
  ACPI Error: No handler or method for GPE[18], disabling event
(20090903/evgpe-706)
which suggested that the issue was with ACPI.

Decompiling the dsdt table and then recompiling according to http://en.gentoo-
wiki.com/wiki/ACPI/Fix_common_problems in order to try to guess what hardware
was the issue, gave me the three following errors:

dsdt.dsl  2124: 0x, // Length
Error4122 -  ^ Invalid combination of Length
and Min/Max fixed flags

dsdt.dsl  2131: 0x07E0, // Length
Error4118 -  ^ Length is not equal to fixed
Min/Max window

dsdt.dsl  2138: 0x0F00, // Length
Error4118 -  ^ Length is not equal to fixed
Min/Max window

Is there any other information that would be useful in finding out why the CPU
usage is so high?

-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.1.0-1-amd64 root=/dev/mapper/pandora-root ro quiet

** Not tainted

** Kernel log:
[5.369898] ATOM BIOS: Lenovo
[5.369958] radeon :01:00.0: VRAM: 1024M 0x - 
0x3FFF (1024M used)
[5.369962] radeon :01:00.0: GTT: 512M 0x4000 - 
0x5FFF
[5.377902] iwlagn :03:00.0: device EEPROM VER=0x15d, CALIB=0x6
[5.377906] iwlagn :03:00.0: Device SKU: 0X50
[5.377909] iwlagn :03:00.0: Valid Tx ant: 0X1, Valid Rx ant: 0X3
[5.381232] iwlagn :03:00.0: Tunable channels: 13 802.11bg, 0 802.11a 
channels
[5.381236] [drm] Detected VRAM RAM=1024M, BAR=256M
[5.381239] [drm] RAM width 128bits DDR
[5.381294] [TTM] Zone  kernel: Available graphics memory: 4089264 kiB.
[5.381296] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB.
[5.381298] [TTM] Initializing pool allocator.
[5.381323] [drm] radeon: 1024M of VRAM memory ready
[5.381325] [drm] radeon: 512M of GTT memory ready.
[5.381342] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[5.381344] [drm] Driver supports precise vblank timestamp query.
[5.381355] iwlagn :03:00.0: RF_KILL bit toggled to disable radio.
[5.381434] radeon :01:00.0: irq 44 for MSI/MSI-X
[5.381442] radeon :01:00.0: radeon: using MSI.
[5.381489] [drm] radeon: irq initialized.
[5.381495] [drm] GART: num cpu pages 131072, num gpu pages 131072
[5.382093] [drm] Loading REDWOOD Microcode
[5.386113] iwlagn :03:00.0: loaded firmware version 39.31.5.1 build 
35138
[5.386225] Registered led device: phy0-led
[5.389763] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs'
[5.393030] radeon :01:00.0: WB enabled
[5.398958] input: Ideapad extra buttons as 
/devices/platform/ideapad/input/input8
[5.409318] [drm] ring test succeeded in 1 usecs
[5.409449] [drm] radeon: ib pool ready.
[5.409515] [drm] ib test succeeded in 0 usecs
[5.409521] failed to evaluate ATIF got AE_BAD_PARAMETER
[5.409913] [drm] Radeon Display Connectors
[5.409916] [drm] Connector 0:
[5.409918] [drm]   LVDS
[5.409921] [drm]   DDC: 0x6560 0x6560 0x6564 0x6564 0x6568 0x6568 0x656c 
0x656c
[5.409923] [drm]   Encoders:
[5.409925] [drm] LCD1: INTERNAL_UNIPHY
[5.409927] [drm] Connector 1:
[5.409929] [drm]   HDMI-A
[5.409931] [drm]   HPD1
[5.409934] [drm]   DDC: 0x6430 0x6430 0x6434 0x6434 0x6438 0x6438 0x643c 
0x643c
[5.409936] [drm]   Encoders:
[5.409938] [drm] DFP1:

Bug#655716: marked as done (linux-image-3.1.0-1-686-pae: Xine-based player (e.g. Kaffeine) crash)

Your message dated Thu, 27 Jun 2013 19:42:51 +0200
with message-id 20130627174251.GD4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #655716,
regarding linux-image-3.1.0-1-686-pae: Xine-based player (e.g. Kaffeine) crash
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.)


-- 
655716: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=655716
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.1.8-2
Severity: important

Dear Maintainer,
   * What led up to the situation?
Every time I try to use a xine-based player (for playing sound), I get a crash
reported by KDE. In /var/log/messages I find the following stack trace:

Jan 13 13:23:09 grzes kernel: [  775.699509] WARNING: at /build/buildd-
linux-2.6_3.1.8-2-i386-3fqT1n/linux-2.6-3.1.8/debian/build/source_i386_none/include/ne
t/dst.h:178 dst_metric+0x2d/0x41 [decnet]()
Jan 13 13:23:09 grzes kernel: [  775.699512] Hardware name: P5QL-E
Jan 13 13:23:09 grzes kernel: [  775.699513] Modules linked in: acpi_cpufreq
mperf cpufreq_userspace cpufreq_conservative cpufreq_powersave cpufreq_stats
par
port_pc ppdev lp parport rfcomm bnep bluetooth rfkill snd_hrtimer binfmt_misc
decnet fuse ext3 jbd w83627ehf hwmon_vid coretemp loop firewire_sbp2 snd_hda_co
dec_realtek snd_usb_audio uvcvideo snd_hda_intel snd_hda_codec videodev
snd_pcm_oss snd_mixer_oss snd_pcm snd_hwdep snd_usbmidi_lib snd_seq_midi media
snd_ra
wmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd i2c_i801
soundcore iTCO_wdt iTCO_vendor_support nvidia(P) snd_page_alloc processor
button asus_
atk0110 evdev thermal_sys pcspkr i2c_core ext4 mbcache jbd2 crc16 usbhid hid
firewire_ohci sd_mod sr_mod cdrom crc_t10dif ahci firewire_core libahci
ata_gene
ric uhci_hcd crc_itu_t ata_piix pata_jmicron ehci_hcd libata scsi_mod atl1e
usbcore [last unloaded: scsi_wait_scan]
Jan 13 13:23:09 grzes kernel: [  775.699555] Pid: 2839, comm: kaffeine-xbu
Tainted: P   O 3.1.0-1-686-pae #1
Jan 13 13:23:09 grzes kernel: [  775.699557] Call Trace:
Jan 13 13:23:09 grzes kernel: [  775.699562]  [c1037698] ?
warn_slowpath_common+0x68/0x79
Jan 13 13:23:09 grzes kernel: [  775.699565]  [f891eefd] ?
dst_metric+0x2d/0x41 [decnet]
Jan 13 13:23:09 grzes kernel: [  775.699568]  [c10376b6] ?
warn_slowpath_null+0xd/0x10
Jan 13 13:23:09 grzes kernel: [  775.699571]  [f891eefd] ?
dst_metric+0x2d/0x41 [decnet]
Jan 13 13:23:09 grzes kernel: [  775.699574]  [f891f3b2] ?
dn_rt_set_next_hop+0x80/0xdb [decnet]
Jan 13 13:23:09 grzes kernel: [  775.699578]  [f891fd1b] ?
__dn_route_output_key+0x4e6/0x55b [decnet]
Jan 13 13:23:09 grzes kernel: [  775.699580]  [c1023dd1] ?
arch_flush_lazy_mmu_mode+0x5/0x14
Jan 13 13:23:09 grzes kernel: [  775.699584]  [f8920b41] ?
dn_route_output_sock+0x16/0x59 [decnet]
Jan 13 13:23:09 grzes kernel: [  775.699587]  [f891c5ef] ?
__dn_connect+0x1ba/0x23b [decnet]
Jan 13 13:23:09 grzes kernel: [  775.699590]  [f891cab3] ?
dn_connect+0x42/0x53 [decnet]
Jan 13 13:23:09 grzes kernel: [  775.699593]  [c12004f3] ?
sys_connect+0x7a/0xad
Jan 13 13:23:09 grzes kernel: [  775.699595]  [c120040a] ?
sys_accept4+0x119/0x171
Jan 13 13:23:09 grzes kernel: [  775.699597]  [c120097a] ?
sys_setsockopt+0x80/0x8b
Jan 13 13:23:09 grzes kernel: [  775.699599]  [c1200e75] ?
sys_socketcall+0xa0/0x1da
Jan 13 13:23:09 grzes kernel: [  775.699602]  [c12b2ddf] ?
sysenter_do_call+0x12/0x28
Jan 13 13:23:09 grzes kernel: [  775.699603] ---[ end trace a3010127d0818b70
]---



-- Package-specific info:
** Version:
Linux version 3.1.0-1-686-pae (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:42:54 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.1.0-1-686-pae 
root=UUID=c2612767-032d-43a2-b414-aac0a0f7d5f5 ro quiet

** Tainted: PWO (4609)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
[2.116057] firewire_ohci: Added fw-ohci device :05:03.0, OHCI v1.0, 8 
IR + 8 IT contexts, quirks 0x0
[2.136096] usb 8-1: New USB device found, idVendor=046d, idProduct=c03e
[2.136099] usb 8-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[2.136100] usb 8-1: Product: USB-PS/2 Optical Mouse
[2.136102] usb 8-1: Manufacturer: Logitech
[2.153479] input: Logitech USB-PS/2 Optical Mouse as 
/devices/pci:00/:00:1d.2/usb8/8-1/8-1:1.0/input/input1
[2.153551] generic-usb 0003:046D:C03E.0001: input,hidraw0: USB HID v1.10 
Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.2-1/input0
[2.153561] usbcore: registered

Bug#656331: marked as done (r8169 with ASUS M2A-VM (SB600): Network device stays down after resume)

Your message dated Thu, 27 Jun 2013 19:42:51 +0200
with message-id 20130627174251.GD4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #656331,
regarding r8169 with ASUS M2A-VM (SB600): Network device stays down after resume
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.)


-- 
656331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656331
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.1.8-2
Severity: normal

Dear Debian folks,


suspending and resuming a lot, it happens once to me, that the network
device did not come back correctly.

[55463.662649] r8169 :02:00.0: eth0: link down
[55463.662669] r8169 :02:00.0: eth0: link down
[55463.663980] ADDRCONF(NETDEV_UP): eth0: link is not ready

I had to unplug the network cable and plug it in again.

[55579.968121] r8169 :02:00.0: eth0: link down
[55581.637656] r8169 :02:00.0: eth0: link up
[55581.638481] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Normally the resume process looks like this, that means the link is
*automatically* up after two seconds.

[69302.909251] r8169 :02:00.0: eth0: link down
[69302.909270] r8169 :02:00.0: eth0: link down
[69302.910529] ADDRCONF(NETDEV_UP): eth0: link is not ready
[69304.585998] r8169 :02:00.0: eth0: link up
[69304.586445] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

Hints for debugging would be great.


Thanks,

Paul


$ dmesg # after resume
[…]
[44540.458145] i2c i2c-4: sendbytes: NAK bailout.
[55413.314370] ata1: exception Emask 0x40 SAct 0x0 SErr 0x800 action 0x7
[55413.314378] ata1: SError: { HostInt }
[55413.314385] ata1: hard resetting link
[55413.804040] ata1: softreset failed (device not ready)
[55413.804054] ata1: applying PMP SRST workaround and retrying
[55413.976119] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[55413.982660] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[55413.988624] ata1.00: SB600 AHCI: limiting to 255 sectors per cmd
[55413.988631] ata1.00: configured for UDMA/100
[55414.004055] ata1: EH complete
[55417.669609] PM: Syncing filesystems ... done.
[55418.038042] PM: Preparing system for mem sleep
[55418.241813] Freezing user space processes ... (elapsed 0.27 seconds) done.
[55418.512040] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) 
done.
[55418.528037] PM: Entering mem sleep
[55418.528062] Suspending console(s) (use no_console_suspend to debug)
[55418.528498] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[55418.528660] sd 0:0:0:0: [sda] Stopping disk
[55418.538829] i8042 aux 00:0a: wake-up capability disabled by ACPI
[55418.538912] parport_pc 00:09: disabled
[55418.538986] serial 00:08: disabled
[55418.539011] serial 00:08: wake-up capability disabled by ACPI
[55418.540082] ehci_hcd :00:13.5: PCI INT D disabled
[55418.540094] ohci_hcd :00:13.4: PCI INT C disabled
[55418.540106] ohci_hcd :00:13.3: PCI INT B disabled
[55418.540117] ohci_hcd :00:13.2: PCI INT C disabled
[55418.540128] ohci_hcd :00:13.1: PCI INT B disabled
[55418.540254] pata_atiixp :00:14.1: PCI INT A disabled
[55418.604094] ohci_hcd :00:13.0: PCI INT A disabled
[55418.640114] snd_hda_intel :00:14.2: PCI INT A disabled
[55418.799155] radeon :01:05.0: PCI INT A disabled
[55418.966650] ahci :00:12.0: PCI INT A disabled
[55418.966679] PM: suspend of devices complete after 438.412 msecs
[55418.966878] r8169 :02:00.0: PME# enabled
[55418.966894] pcieport :00:07.0: wake-up capability enabled by ACPI
[55418.996204] PM: late suspend of devices complete after 29.519 msecs
[55418.996289] ACPI: Preparing to enter system sleep state S3
[55418.996393] PM: Saving platform NVS memory
[55418.996448] Disabling non-boot CPUs ...
[55419.184016] CPU 1 is now offline
[55419.184831] ACPI: Low-level resume complete
[55419.184831] PM: Restoring platform NVS memory
[55419.184831] Enabling non-boot CPUs ...
[55419.184831] Booting Node 0 Processor 1 APIC 0x1
[55419.184831] smpboot cpu 1: start_ip = 9a000
[55419.082905] Calibrating delay loop (skipped) already calibrated this CPU
[55419.196721] NMI watchdog enabled, takes one hw-pmu counter.
[55419.196914] CPU1 is up
[55419.197227] ACPI: Waking up from system sleep state S3
[55419.197384] pci :00:00.0: restoring config space at offset 0x3 (was 0x0, 
writing 0x4000)
[55419.197419] pcieport :00:07.0: restoring config space at offset 0x1 (was 
0x17, writing 0x100407)
[55419.197463] ahci :00:12.0: restoring

Bug#658142: marked as done (linux-image-2.6.32-5-amd64: kernel oops in __mark_inode_dirty)

Your message dated Thu, 27 Jun 2013 19:43:19 +0200
with message-id 20130627174319.GE4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #658142,
regarding linux-image-2.6.32-5-amd64: kernel oops in __mark_inode_dirty
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.)


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

I got the following with the kernel from 6.0.3 (the last boot before
upgrading to 6.0.4):

Jan 31 14:16:33 snowbell kernel: [   34.117665] [ cut here
]
Jan 31 14:16:33 snowbell kernel: [   34.117686] WARNING: at
/tmp/buildd/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/fs-writeback.c:1122
__mark_inode_dirty+0xe7/0x14a()
Jan 31 14:16:33 snowbell kernel: [   34.117696] Hardware name: 1005PE
Jan 31 14:16:33 snowbell kernel: [   34.117701] Modules linked in:
loop(+) snd_hda_codec_realtek joydev arc4 ecb snd_hda_intel ath9k
snd_hda_codec mac80211 snd_hwdep ath uvcvideo i915 snd_pcm videodev
snd_seq drm_kms_helper snd_timer v4l1_compat cfg80211 drm
snd_seq_device v4l2_compat_ioctl32 eeepc_laptop rfkill i2c_algo_bit
snd psmouse pci_hotplug i2c_core led_class serio_raw wmi evdev
soundcore video output battery processor snd_page_alloc ac button ext3
jbd mbcache sha256_generic aes_x86_64 aes_generic cbc dm_crypt dm_mod
sd_mod crc_t10dif ahci libata uhci_hcd thermal atl1c ehci_hcd scsi_mod
usbcore nls_base thermal_sys [last unloaded: scsi_wait_scan]
Jan 31 14:16:33 snowbell kernel: [   34.117837] Pid: 831, comm:
udisks-part-id Not tainted 2.6.32-5-amd64 #1
Jan 31 14:16:33 snowbell kernel: [   34.117843] Call Trace:
Jan 31 14:16:33 snowbell kernel: [   34.117857]  [8110872f]
? __mark_inode_dirty+0xe7/0x14a
Jan 31 14:16:33 snowbell kernel: [   34.117868]  [8110872f]
? __mark_inode_dirty+0xe7/0x14a
Jan 31 14:16:33 snowbell kernel: [   34.117878]  [8104df9c]
? warn_slowpath_common+0x77/0xa3
Jan 31 14:16:33 snowbell kernel: [   34.117890]  [8110872f]
? __mark_inode_dirty+0xe7/0x14a
Jan 31 14:16:33 snowbell kernel: [   34.117901]  [810ffc78]
? touch_atime+0xfe/0x127
Jan 31 14:16:33 snowbell kernel: [   34.117912]  [810b5a4d]
? generic_file_aio_read+0x499/0x536
Jan 31 14:16:33 snowbell kernel: [   34.117926]  [810eed05]
? do_sync_read+0xce/0x113
Jan 31 14:16:33 snowbell kernel: [   34.117938]  [81064f92]
? autoremove_wake_function+0x0/0x2e
Jan 31 14:16:33 snowbell kernel: [   34.117950]  [810ccd36]
? handle_mm_fault+0x3b8/0x80f
Jan 31 14:16:33 snowbell kernel: [   34.117961]  [810ef728]
? vfs_read+0xa6/0xff
Jan 31 14:16:33 snowbell kernel: [   34.117971]  [810ef83d]
? sys_read+0x45/0x6e
Jan 31 14:16:33 snowbell kernel: [   34.117981]  [81010b42]
? system_call_fastpath+0x16/0x1b
Jan 31 14:16:33 snowbell kernel: [   34.117989] ---[ end trace
5132e90d34f21d4f ]---

It's the first time I see this in 2+ years since I have the netbook
(Asus EeePC 1005PE). e2fsck found nothing bad, but I didn't run
badblocks yet. The S.M.A.R.T. status is ok (smartctl -A /dev/sda), and I
ran a short and a long selftest with smartctl, which found nothing
wrong. Any ideas?

Thanks,
  Laurentiu

P.S. kerneloops.org seems to be down.

-- Package-specific info:
#part type=text/plain disposition=attachment description=Bug script output
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-41) (b...@decadent.org.uk)
(gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 16 16:22:28 UTC
2012

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64
root=/dev/mapper/VG_snowbell-LV_root ro acpi_osi=Linux quiet

** Not tainted

** Kernel log:
[   46.927231] Bluetooth: RFCOMM ver 1.11
[   47.118454] Bridge firewalling registered
[   47.225327] Bluetooth: SCO (Voice Link) ver 0.6
[   47.225334] Bluetooth: SCO socket layer initialized
[   48.041185] lp: driver loaded but no devices found
[   48.173327] ppdev: user-space parallel port driver
[   48.888742] composite sync not supported
[   49.023887] composite sync not supported
[   56.555634] composite sync not supported
[   56.696334] composite sync not supported
[   56.860854] composite sync not supported
[   61.005980] CPU0 attaching NULL sched-domain.
[   61.005995] CPU1 attaching NULL sched-domain.
[   61.041291] CPU0 attaching sched-domain:
[   61.041301]  domain 0: span 0-1 level SIBLING
[   61.041309]   groups: group 88000180fae0 cpus 0 (cpu_power =
589) group 88000190fae0 cpus 1 (cpu_power = 589)
[

Bug#656952: marked as done (The keyboard suddenly froze)

Your message dated Thu, 27 Jun 2013 19:42:51 +0200
with message-id 20130627174251.GD4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #656952,
regarding The keyboard suddenly froze
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.)


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

Package: linux-2.6
Version: 3.2.1-1
Severity: normal

I decided to upgrade the kernel from sid in order to improve the
wireless driver. Unfortunately, when having started the computer and
browsing the Internet, the keyboard and the touchpad suddenly froze. I
saw the rate of CPU increasing to 100%. I pressed the power button to
suspend, and when resuming, the keyboard was OK.
I thought it must have been a kernel bug.


-- Package-specific info:
** Version:
Linux version 3.2.0-1-686-pae (Debian 3.2.1-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Thu Jan 19 10:56:51 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-1-686-pae 
root=UUID=4a6467bf-103c-4dd5-b8dc-bde482eb469f ro quiet

** Not tainted

** Kernel log:
[  493.864220] pcieport :00:1c.0: restoring config space at offset 0x9 (was 
0x10001, writing 0xd3f1d001)
[  493.864227] pcieport :00:1c.0: restoring config space at offset 0x8 (was 
0x0, writing 0xb7f0b400)
[  493.864233] pcieport :00:1c.0: restoring config space at offset 0x7 (was 
0x0, writing 0x2020)
[  493.864243] pcieport :00:1c.0: restoring config space at offset 0x3 (was 
0x81, writing 0x810008)
[  493.864251] pcieport :00:1c.0: restoring config space at offset 0x1 (was 
0x10, writing 0x100507)
[  493.864309] uhci_hcd :00:1d.0: restoring config space at offset 0x1 (was 
0x285, writing 0x281)
[  493.864339] uhci_hcd :00:1d.1: restoring config space at offset 0x1 (was 
0x285, writing 0x281)
[  493.864370] uhci_hcd :00:1d.2: restoring config space at offset 0x1 (was 
0x285, writing 0x281)
[  493.864400] uhci_hcd :00:1d.3: restoring config space at offset 0x1 (was 
0x285, writing 0x281)
[  493.864439] ehci_hcd :00:1d.7: restoring config space at offset 0x1 (was 
0x2900106, writing 0x2900102)
[  493.864457] ehci_hcd :00:1d.7: PME# disabled
[  493.864469] pci :00:1e.0: restoring config space at offset 0xf (was 
0x4, writing 0x400ff)
[  493.864481] pci :00:1e.0: restoring config space at offset 0x9 (was 
0x10001, writing 0x29f12401)
[  493.864488] pci :00:1e.0: restoring config space at offset 0x8 (was 0x0, 
writing 0xb800b800)
[  493.864494] pci :00:1e.0: restoring config space at offset 0x7 (was 
0x22800010, writing 0x22803030)
[  493.864500] pci :00:1e.0: restoring config space at offset 0x6 (was 
0x20060600, writing 0x200a0600)
[  493.864512] pci :00:1e.0: restoring config space at offset 0x1 (was 
0x15, writing 0x8100107)
[  493.864553] pci :00:1f.0: restoring config space at offset 0x1 (was 
0x207, writing 0x2000107)
[  493.864566] ata_piix :00:1f.1: restoring config space at offset 0xf (was 
0x100, writing 0x1ff)
[  493.864589] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 
0x280, writing 0x2880005)
[  493.864640] b44 :06:05.0: restoring config space at offset 0xf (was 
0x100, writing 0x105)
[  493.864661] b44 :06:05.0: restoring config space at offset 0x4 (was 0x0, 
writing 0xb800)
[  493.864667] b44 :06:05.0: restoring config space at offset 0x3 (was 0x0, 
writing 0x2000)
[  493.864675] b44 :06:05.0: restoring config space at offset 0x1 (was 
0x10, writing 0x8100106)
[  493.864698] ipw2200 :06:07.0: restoring config space at offset 0xf (was 
0x18030100, writing 0x1803010b)
[  493.864722] ipw2200 :06:07.0: restoring config space at offset 0x4 (was 
0x0, writing 0xb8002000)
[  493.864729] ipw2200 :06:07.0: restoring config space at offset 0x3 (was 
0x0, writing 0x2008)
[  493.864738] ipw2200 :06:07.0: restoring config space at offset 0x1 (was 
0x290, writing 0x2900116)
[  493.864762] yenta_cardbus :06:09.0: restoring config space at offset 0xf 
(was 0x7000100, writing 0x5800100)
[  493.864768] yenta_cardbus :06:09.0: restoring config space at offset 0xe 
(was 0x0, writing 0x30fc)
[  493.864775] yenta_cardbus :06:09.0: restoring config space at offset 0xd 
(was 0x0, writing 0x3000)
[  493.864782] yenta_cardbus :06:09.0: restoring config space at offset 0xc 
(was 0x0, writing 0x34fc)
[  493.864788] yenta_cardbus :06:09.0: restoring config space at offset 0xb 
(was

Bug#658618: marked as done (3c589_cs: media types 10base2 and 10baseT are switched)

Your message dated Thu, 27 Jun 2013 19:43:19 +0200
with message-id 20130627174319.GE4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #658618,
regarding 3c589_cs: media types 10base2 and 10baseT are switched
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.)


-- 
658618: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658618
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.1.8-2
Severity: normal

When using /sbin/ifconfig to configure the media type of a 3Com PCMCIA network
device, the parameters are switched around.

ifconfig eth1 media 10base2 selects 10baseT while
ifconfig eth1 media 10baseT selects 10base2.

The driver prints out the correct interface in dmesg after running these 
commands.


-- Package-specific info:
** Version:
Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012

** Command line:
initrd=/initrd.img root=LABEL=ROOT quiet BOOT_IMAGE=/vmlinuz 

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[720827.368056] 3c589_cs 0.0: eth1: coax cable ok
[720828.368065] 3c589_cs 0.0: eth1: coax cable problem
[720834.368051] 3c589_cs 0.0: eth1: coax cable ok
[720835.368075] 3c589_cs 0.0: eth1: coax cable problem
[720836.368045] 3c589_cs 0.0: eth1: coax cable ok
[720838.368068] 3c589_cs 0.0: eth1: coax cable problem
[720842.368062] 3c589_cs 0.0: eth1: coax cable ok
[720851.368095] 3c589_cs 0.0: eth1: coax cable problem
[720852.370435] 3c589_cs 0.0: eth1: coax cable ok
[720856.368076] 3c589_cs 0.0: eth1: coax cable problem
[720857.368060] 3c589_cs 0.0: eth1: coax cable ok
[720860.368074] 3c589_cs 0.0: eth1: coax cable problem
[720861.368064] 3c589_cs 0.0: eth1: coax cable ok
[720862.368069] 3c589_cs 0.0: eth1: coax cable problem
[720864.368062] 3c589_cs 0.0: eth1: coax cable ok
[720874.368100] 3c589_cs 0.0: eth1: coax cable problem
[720877.368070] 3c589_cs 0.0: eth1: coax cable ok
[720878.368100] 3c589_cs 0.0: eth1: coax cable problem
[720902.368055] 3c589_cs 0.0: eth1: coax cable ok
[720916.368076] 3c589_cs 0.0: eth1: coax cable problem
[720925.368066] 3c589_cs 0.0: eth1: coax cable ok
[720992.376075] 3c589_cs 0.0: eth1: coax cable problem
[720993.376063] 3c589_cs 0.0: eth1: coax cable ok
[721000.376060] 3c589_cs 0.0: eth1: coax cable problem
[721002.376055] 3c589_cs 0.0: eth1: coax cable ok
[721007.376050] 3c589_cs 0.0: eth1: coax cable problem
[721008.376075] 3c589_cs 0.0: eth1: coax cable ok
[721009.376095] 3c589_cs 0.0: eth1: coax cable problem
[721026.376062] 3c589_cs 0.0: eth1: coax cable ok
[721029.376060] 3c589_cs 0.0: eth1: coax cable problem
[721030.376055] 3c589_cs 0.0: eth1: coax cable ok
[721039.376062] 3c589_cs 0.0: eth1: coax cable problem
[721041.376068] 3c589_cs 0.0: eth1: coax cable ok
[721046.376061] 3c589_cs 0.0: eth1: coax cable problem
[721047.376057] 3c589_cs 0.0: eth1: coax cable ok
[721049.376069] 3c589_cs 0.0: eth1: coax cable problem
[721051.376061] 3c589_cs 0.0: eth1: coax cable ok
[721052.376072] 3c589_cs 0.0: eth1: coax cable problem
[721056.376049] 3c589_cs 0.0: eth1: coax cable ok
[721058.376069] 3c589_cs 0.0: eth1: coax cable problem
[721061.376048] 3c589_cs 0.0: eth1: coax cable ok
[721064.376066] 3c589_cs 0.0: eth1: coax cable problem
[721065.376070] 3c589_cs 0.0: eth1: coax cable ok
[721069.376097] 3c589_cs 0.0: eth1: coax cable problem
[721070.376087] 3c589_cs 0.0: eth1: coax cable ok
[721079.376080] 3c589_cs 0.0: eth1: coax cable problem
[721083.376059] 3c589_cs 0.0: eth1: coax cable ok
[721085.376069] 3c589_cs 0.0: eth1: coax cable problem
[721092.376050] 3c589_cs 0.0: eth1: coax cable ok
[721097.376059] 3c589_cs 0.0: eth1: coax cable problem
[721101.376056] 3c589_cs 0.0: eth1: coax cable ok
[721105.376065] 3c589_cs 0.0: eth1: coax cable problem
[721106.376044] 3c589_cs 0.0: eth1: coax cable ok
[721107.376072] 3c589_cs 0.0: eth1: coax cable problem
[721108.376066] 3c589_cs 0.0: eth1: coax cable ok
[72.376073] 3c589_cs 0.0: eth1: coax cable problem
[721113.376036] 3c589_cs 0.0: eth1: coax cable ok
[721115.376077] 3c589_cs 0.0: eth1: coax cable problem
[721117.376056] 3c589_cs 0.0: eth1: coax cable ok
[721120.376060] 3c589_cs 0.0: eth1: coax cable problem
[721121.376038] 3c589_cs 0.0: eth1: coax cable ok
[721127.376084] 3c589_cs 0.0: eth1: coax cable problem
[721128.376080] 3c589_cs 0.0: eth1: coax cable ok
[721130.376075] 3c589_cs 0.0: eth1: coax cable problem
[721131.376052] 3c589_cs 0.0: eth1: coax cable ok
[721137.376068] 3c589_cs 0.0: eth1: coax cable problem
[721138.376045] 3c589_cs

Bug#658697: marked as done (linux: Tasks hungs for more than 2 mins and getting blocked by kernel as in result)

Your message dated Thu, 27 Jun 2013 19:43:19 +0200
with message-id 20130627174319.GE4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #658697,
regarding linux: Tasks hungs for more than 2 mins and getting blocked by kernel 
as in result
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.)


-- 
658697: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658697
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-41
Severity: normal
File: linux

Hello,
I'm having trouble with my debian server for last two months: tasks under high 
load (such
as apache, mysql) hungs and kernel blocks them, sending thousands of report to 
dmesg:
[ 2160.503948] INFO: task apache2:10350 blocked for more than 120 seconds.
[ 2160.503956] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables this 
message.
[ 2160.503967] apache2   D  0 10350   9695 0x
[ 2160.503976]  ea16fb40 00200082    c141d100 c141d100 
ea486198
[ 2160.504013]  ea16fcfc c3408100  6a73887e 01cd bd0bba94 cdd0f017 
e8aa3f00
[ 2160.504036]  ea486198 ea16fcfc ef41d89c ef4bc660 e8aa3ea8 ea5d489c c10c1453 
e8aa3f00
[ 2160.504064] Call Trace:
[ 2160.504074]  [c10c1453] ? dput+0x22/0x105
[ 2160.504083]  [c126dde7] ? __mutex_lock_common+0xe8/0x13b
[ 2160.504093]  [c126de49] ? __mutex_lock_slowpath+0xf/0x11
[ 2160.504103]  [c126deda] ? mutex_lock+0x17/0x24
[ 2160.504112]  [c126deda] ? mutex_lock+0x17/0x24
[ 2160.504121]  [c10bbdf7] ? do_filp_open+0x1e6/0x802
[ 2160.504130]  [c10c3d6d] ? alloc_fd+0x52/0xb7
[ 2160.504138]  [c10b1bef] ? do_sys_open+0x4c/0xdf
[ 2160.504145]  [c10b1cc6] ? sys_open+0x1e/0x23
[ 2160.504153]  [c10030fb] ? sysenter_do_call+0x12/0x28

I'm not 100% sure that this is software bug, it's can be a problem with disk 
too. But
I did a full disk check with smartctl and it reported no problems. I also did 
read/write disk benchmark with hdparm, results looks good again.

Sorry for my english :) 

-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-38) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Oct 3 04:15:24 UTC 2011

** Command line:
ro root=/dev/sda1 --verbose

** Not tainted

** Kernel log:
[ 2160.502429]  [c108bcf1] ? get_page_from_freelist+0xc0/0x3c7
[ 2160.502438]  [c126d73a] ? io_schedule+0x5f/0x98
[ 2160.502445]  [c10ce76e] ? sync_buffer+0x30/0x33
[ 2160.502452]  [c126da98] ? __wait_on_bit_lock+0x31/0x6a
[ 2160.502460]  [c10ce73e] ? sync_buffer+0x0/0x33
[ 2160.502468]  [c126db86] ? out_of_line_wait_on_bit_lock+0xb5/0xbd
[ 2160.502475]  [c10ce73e] ? sync_buffer+0x0/0x33
[ 2160.502483]  [c104405b] ? wake_bit_function+0x0/0x3c
[ 2160.502490]  [c10cea87] ? __lock_buffer+0x21/0x24
[ 2160.502498]  [c10ceaf1] ? sync_dirty_buffer+0x21/0x83
[ 2160.502506]  [f7ef7ce9] ? journal_dirty_data+0xc6/0x191 [jbd]
[ 2160.502516]  [f7f31651] ? ext3_journal_dirty_data+0xc/0x2a [ext3]
[ 2160.502526]  [f7f2fe4c] ? walk_page_buffers+0x4c/0x65 [ext3]
[ 2160.502536]  [f7f32f45] ? ext3_ordered_write_end+0x79/0x141 [ext3]
[ 2160.502545]  [f7f3166f] ? journal_dirty_data_fn+0x0/0x14 [ext3]
[ 2160.502554]  [c10885ce] ? generic_file_buffered_write+0x12f/0x21d
[ 2160.502561]  [c10c951c] ? __mark_inode_dirty+0x20/0x10b
[ 2160.502569]  [c10c951c] ? __mark_inode_dirty+0x20/0x10b
[ 2160.502577]  [c1088ab9] ? __generic_file_aio_write+0x265/0x28d
[ 2160.502585]  [c1089074] ? generic_file_aio_read+0x500/0x57b
[ 2160.503354]  [c1088b32] ? generic_file_aio_write+0x51/0x93
[ 2160.503363]  [c10b335e] ? do_sync_write+0xc0/0x107
[ 2160.503370]  [c104402e] ? autoremove_wake_function+0x0/0x2d
[ 2160.503378]  [c104402e] ? autoremove_wake_function+0x0/0x2d
[ 2160.503386]  [c10b30aa] ? fsnotify_modify+0x5a/0x61
[ 2160.503394]  [c1102ae4] ? security_file_permission+0xc/0xd
[ 2160.503402]  [c10b329e] ? do_sync_write+0x0/0x107
[ 2160.503410]  [c10b3c68] ? vfs_write+0x7e/0xd6
[ 2160.503417]  [c10b3d06] ? sys_pwrite64+0x46/0x5c
[ 2160.503425]  [c10030fb] ? sysenter_do_call+0x12/0x28
[ 2160.503451] INFO: task apache2:10085 blocked for more than 120 seconds.
[ 2160.503458] echo 0  /proc/sys/kernel/hung_task_timeout_secs disables this 
message.
[ 2160.503469] apache2   D c108bcf1 0 10085   9695 0x
[ 2160.503479]  ea168880 00200086 f6b66200 c108bcf1 0001 c141d100 c141d100 

[ 2160.503497]  ea168a3c c3508100 0001  00020050 c13b74ec c153d440 
c13b5ba0
[ 2160.503516]  02e80c18 ea168a3c 394fe7a0  02e80c18  e9ca1e18 
000c59d8
[ 2160.503535] Call Trace:
[ 2160.503542]

Bug#659979: marked as done (ath9k AR9285: Excessive packet loss with 3.2 (worked under 3.1))

Your message dated Thu, 27 Jun 2013 19:41:22 +0200
with message-id 20130627174122.GA4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #659979,
regarding ath9k AR9285: Excessive packet loss with 3.2 (worked under 3.1)
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.)


-- 
659979: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659979
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.4-1
Severity: normal
File: /lib/modules/3.2.0-1-amd64/kernel/drivers/net/wireless/ath/ath9k/ath9k.ko

Under 3.1, the wirless works fine (0% packet loss). Under 3.2, ping
shows 25% packet loss pinging the local gateway. This is repeatable;
each time I boot 3.1, it works, each time I boot 3.2 it doesn't. I have
tried each immediately after the other. Several times over.

iw station dump shows an excessive amount of tx retries (and tx failed)
under 3.2, but not 3.1. Also, under 3.2, the TX bitrate jumps all over
the place; umder 3.1 it stays at 65mbps. 

I am attaching the output of
- iw link
- iw station dump
- iw phy
under both 3.1 and 3.2

-- Package-specific info:
** Version:
Linux version 3.2.0-1-amd64 (Debian 3.2.4-1) (wa...@debian.org) (gcc version 
4.6.2 (Debian 4.6.2-12) ) #1 SMP Sun Feb 5 15:17:15 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-1-amd64 root=/dev/mapper/Heisenberg-root ro 
enable_mtrr_cleanup

** Not tainted

** Kernel log:
[   20.866445] iTCO_wdt: Found a ICH9M-E TCO device (Version=2, TCOBASE=0x0860)
[   20.866920] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[   20.873141] asus_laptop: Asus Laptop Support version 0.42
[   20.873457] asus_laptop:   UL30A model detected
[   20.874232] asus_laptop: Backlight controlled by ACPI video driver
[   20.874402] input: Asus Laptop extra buttons as 
/devices/platform/asus_laptop/input/input5
[   21.038283] [drm] Initialized drm 1.1.0 20060810
[   21.053866] psmouse serio4: elantech: assuming hardware version 2 (with 
firmware version 0x040101)
[   21.090721] psmouse serio4: elantech: Synaptics capabilities query result 
0x7e, 0x13, 0x0d.
[   21.229015] input: ETPS/2 Elantech Touchpad as 
/devices/platform/i8042/serio4/input/input6
[   21.249614] Linux media interface: v0.10
[   21.264967] Linux video capture interface: v2.00
[   21.287019] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[   21.287095] i915 :00:02.0: setting latency timer to 64
[   21.334913] uvcvideo: Found UVC 1.00 device USB2.0 0.3M UVC WebCam 
(04f2:b036)
[   21.343141] i915 :00:02.0: irq 44 for MSI/MSI-X
[   21.343151] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   21.343194] input: USB2.0 0.3M UVC WebCam as 
/devices/pci:00/:00:1a.7/usb1/1-3/1-3:1.0/input/input7
[   21.343308] [drm] Driver supports precise vblank timestamp query.
[   21.343437] vgaarb: device changed decodes: 
PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem
[   21.343676] usbcore: registered new interface driver uvcvideo
[   21.343745] USB Video Class driver (1.1.1)
[   21.542033] ath9k :02:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[   21.542121] ath9k :02:00.0: setting latency timer to 64
[   21.555014] cfg80211: World regulatory domain updated:
[   21.555090] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   21.555184] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   21.555282] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   21.555375] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   21.555473] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   21.67] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   21.592273] ath: EEPROM regdomain: 0x60
[   21.592276] ath: EEPROM indicates we should expect a direct regpair map
[   21.592282] ath: Country alpha2 being used: 00
[   21.592285] ath: Regpair used: 0x60
[   21.715124] ieee80211 phy0: Selected rate control algorithm 
'ath9k_rate_control'
[   21.716046] Registered led device: ath9k-phy0
[   21.716058] ieee80211 phy0: Atheros AR9285 Rev:2 mem=0xc900110a, 
irq=17
[   21.743839] fbcon: inteldrmfb (fb0) is primary device
[   22.127690] Console: switching to colour frame buffer device 170x48
[   22.135198] fb0: inteldrmfb frame buffer device
[   22.135200] drm: registered panic notifier
[   22.139481] acpi device:36: registered as cooling_device2
[   22.139710] input: Video Bus as

Bug#663164: marked as done (linux-image-3.2.0-1-amd64: unable to mount a filesystem on a known working sata drive in an external usb enclosure.)

Your message dated Thu, 27 Jun 2013 19:43:45 +0200
with message-id 20130627174345.GF4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #663164,
regarding linux-image-3.2.0-1-amd64: unable to mount a filesystem on a known 
working sata drive in an external usb enclosure.
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.)


-- 
663164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663164
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.6-1
Severity: normal

Dear Maintainer,
i am unable to mount a filesystem on a known working sata drive in an external 
usb enclosure. enclosure is newegg item # N82E16817392032. this is the second 
enclosure that i've tried, as i RMA'd the first one thinking it was just 
defective. the first one exhibited the same behavior.

i can make a partition label and filesystem using parted (i also tried with 
fdisk and mkfs.ext4), but i cannot mount filesystem. i have tried both gpt and 
msdos partition layouts, with several different filesystems, but no luck.

xfce does not show the drive when plugged in, nor can i manually mount the 
disk. i can list the disk layout with parted or fdisk though.


-- Package-specific info:
** Version:
Linux version 3.2.0-1-amd64 (Debian 3.2.6-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-14) ) #1 SMP Fri Feb 17 05:17:36 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64 
root=UUID=4420abab-3a68-4a9c-9f6b-8628005276c5 ro quiet

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

** Kernel log:
[   83.560958] scsi2 : usb-storage 1-3:1.0
[   83.584589] ehci_hcd :00:13.2: BAR 0: set to [mem 0x9024a400-0x9024a4ff] 
(PCI address [0x9024a400-0x9024a4ff])
[   83.584744] ehci_hcd :00:13.2: restoring config space at offset 0x1 (was 
0x2b0, writing 0x2b00013)
[   83.584992] ehci_hcd :00:13.2: PME# disabled
[   83.585020] ehci_hcd :00:13.2: PCI INT B - GSI 17 (level, low) - IRQ 17
[   84.562987] scsi 2:0:0:0: Direct-AccessMass  Storage Device
PQ: 0 ANSI: 0
[   84.568397] sd 2:0:0:0: [sdb] 488397166 512-byte logical blocks: (250 GB/232 
GiB)
[   84.569190] sd 2:0:0:0: [sdb] Write Protect is off
[   84.569208] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
[   84.569949] sd 2:0:0:0: [sdb] No Caching mode page present
[   84.569962] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[   84.582615] sd 2:0:0:0: [sdb] No Caching mode page present
[   84.582633] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[   84.597576]  sdb: sdb1
[   84.603530] sd 2:0:0:0: [sdb] No Caching mode page present
[   84.603550] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[   84.603562] sd 2:0:0:0: [sdb] Attached SCSI disk
[   87.840300] ehci_hcd :00:13.2: PCI INT B disabled
[   87.840372] ehci_hcd :00:13.2: PME# enabled
[  103.920236] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  271.952323] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  321.936632] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  348.944653] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  371.920287] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  411.920231] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  435.952371] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  533.936471] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  555.952493] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  700.944314] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  704.352642] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  723.920649] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  746.944509] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  773.936124] usb 1-3: reset high-speed USB device number 3 using ehci_hcd
[  838.115182] usb 1-3: USB disconnect, device number 3
[  844.124630] usb 1-3: new high-speed USB device number 4 using ehci_hcd
[  844.258439] usb 1-3: New USB device found, idVendor=14cd, idProduct=6116
[  844.258454] usb 1-3: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[  844.258464] usb 1-3: Product: USB Mass Storage Device
[  844.258472] usb 1-3: Manufacturer: Generic 
[  844.258480] usb 1-3: SerialNumber: 116AC2101219
[  844.260415] scsi3 : usb-storage 1-3:1.0
[  844.284086] ehci_hcd :00:13.2: BAR 0: set to [mem 0x9024a400-0x9024a4ff] 
(PCI address [0x9024a400-0x9024a4ff])
[  844.284242]

Bug#661162: marked as done (iwl wifi hangs on lots of traffic)

Your message dated Thu, 27 Jun 2013 19:43:19 +0200
with message-id 20130627174319.GE4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #661162,
regarding iwl wifi hangs on lots of traffic
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.)


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

iwl wifi hangs on heavy traffic. Mounting an nfs server via wifi
and untarring linux kernel gives a reproducible hang 1 out of 4 
times or so.

At the same time if the traffic is light it can work for days
with no problem.

-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-41) (b...@decadent.org.uk) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Jan 16 16:22:28 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=8aa6c209-ca56-4f03-a332-97c130d8cbf8 ro quiet

** Tainted: W (512)
 * Taint on warning.

** Kernel log:
[18243.724048] wlan0: associated
[18304.830702] wlan0: deauthenticated from 28:94:0f:75:75:f0 (Reason: 1)
[18308.103844] wlan0: direct probe to AP 28:94:0f:75:75:e0 (try 1)
[18308.107980] wlan0: direct probe responded
[18308.107987] wlan0: authenticate with AP 28:94:0f:75:75:e0 (try 1)
[18308.109739] wlan0: authenticated
[18308.109776] wlan0: associate with AP 28:94:0f:75:75:e0 (try 1)
[18308.113929] wlan0: RX AssocResp from 28:94:0f:75:75:e0 (capab=0x431 status=0 
aid=1)
[18308.113933] wlan0: associated
[18318.117506] wlan0: deauthenticating from 28:94:0f:75:75:e0 by local choice 
(reason=3)
[18321.397240] wlan0: direct probe to AP 28:94:0f:75:75:e0 (try 1)
[18321.402371] wlan0: direct probe responded
[18321.402377] wlan0: authenticate with AP 28:94:0f:75:75:e0 (try 1)
[18321.405751] wlan0: authenticated
[18321.405781] wlan0: associate with AP 28:94:0f:75:75:e0 (try 1)
[18321.408651] wlan0: RX AssocResp from 28:94:0f:75:75:e0 (capab=0x431 status=0 
aid=1)
[18321.408656] wlan0: associated
[18904.803655] wlan0: deauthenticated from 28:94:0f:75:75:e0 (Reason: 1)
[18908.156216] wlan0: direct probe to AP 28:94:0f:75:75:f0 (try 1)
[18908.355928] wlan0: direct probe to AP 28:94:0f:75:75:f0 (try 2)
[18908.356458] wlan0: direct probe responded
[18908.356463] wlan0: authenticate with AP 28:94:0f:75:75:f0 (try 1)
[18908.357216] wlan0: authenticated
[18908.357240] wlan0: associate with AP 28:94:0f:75:75:f0 (try 1)
[18908.555631] wlan0: associate with AP 28:94:0f:75:75:f0 (try 2)
[18908.556893] wlan0: RX AssocResp from 28:94:0f:75:75:f0 (capab=0x111 status=0 
aid=1)
[18908.556897] wlan0: associated
[19504.521603] wlan0: deauthenticating from 28:94:0f:75:75:f0 by local choice 
(reason=3)
[19504.561894] wlan0: direct probe to AP 28:94:0f:75:75:f0 (try 1)
[19504.562363] wlan0: direct probe responded
[19504.562366] wlan0: authenticate with AP 28:94:0f:75:75:f0 (try 1)
[19504.563622] wlan0: authenticated
[19504.563640] wlan0: associate with AP 28:94:0f:75:75:f0 (try 1)
[19504.759735] wlan0: associate with AP 28:94:0f:75:75:f0 (try 2)
[19504.762632] wlan0: deauthenticated from 28:94:0f:75:75:f0 (Reason: 6)
[19517.708072] wlan0: direct probe to AP 28:94:0f:75:75:f0 (try 1)
[19517.709101] wlan0: direct probe responded
[19517.709105] wlan0: authenticate with AP 28:94:0f:75:75:f0 (try 1)
[19517.904967] wlan0: authenticate with AP 28:94:0f:75:75:f0 (try 2)
[19517.905550] wlan0: authenticated
[19517.905581] wlan0: associate with AP 28:94:0f:75:75:f0 (try 1)
[19517.906740] wlan0: RX AssocResp from 28:94:0f:75:75:f0 (capab=0x111 status=0 
aid=1)
[19517.906744] wlan0: associated
[19560.702855] wlan0: deauthenticating from 28:94:0f:75:75:f0 by local choice 
(reason=3)
[19560.733096] wlan0: direct probe to AP 28:94:0f:75:75:e0 (try 1)
[19560.739341] wlan0: direct probe responded
[19560.739347] wlan0: authenticate with AP 28:94:0f:75:75:e0 (try 1)
[19560.741039] wlan0: authenticated
[19560.741071] wlan0: associate with AP 28:94:0f:75:75:e0 (try 1)
[19560.744230] wlan0: RX AssocResp from 28:94:0f:75:75:e0 (capab=0x431 status=0 
aid=1)
[19560.744236] wlan0: associated
[19644.170131] svc: failed to register lockdv1 RPC service (errno 97).
[20104.699514] wlan0: deauthenticated from 28:94:0f:75:75:e0 (Reason: 1)
[20107.943709] wlan0: direct probe to AP 28:94:0f:75:75:e0 (try 1)
[20107.947453] wlan0: direct probe responded
[20107.947460] wlan0: authenticate with AP 28:94:0f:75:75:e0 (try 1)
[20107.949211] wlan0: authenticated
[20107.949244] wlan0: associate with AP 28:94:0f:75:75:e0 (try 1)
[20107.961955] wlan0: RX

Bug#661920: marked as done (linux-image-2.6.32-5-amd64: mounting some CDs lead to Unhandled sense codes which make autodetection fail)

Your message dated Thu, 27 Jun 2013 19:43:45 +0200
with message-id 20130627174345.GF4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #661920,
regarding linux-image-2.6.32-5-amd64: mounting some CDs lead to Unhandled 
sense codes which make autodetection fail
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.)


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


When using some CDs there are Unhandled sense code messges for
the device. This leads to Plasma's autodetection of the device to fail
and does not display the device.
There is a very good chance the CD can still be mounted manually.

I am opening this report, because in #583949 Ben Hutchings recommend it.
Also because I believe this is related to software somehow and not gone.
It probably will take some effort by the Debian, kernel and Free Software
communities to get a closer grip on this defect.

Any hints towards further analysis are highly appreciated!
Bernhard

Details:
I have two drives available for the testing on an amd machine,
running an amd kernel with 32bit userspace.
One drive is build in, the other is usb.
Both show the symptoms.
If I have a CD that is affected, it will have problems in both drives.
Booting into windows XP, there is no issue.
Running grml96_2011.12.iso from an usb stick there is no
issue, it has linux-image-3.1.0-3-grml-amd64, but has not autodetection anyway.

The symptoms: 
Putting the CD in the drive, it will take some time, more than usual
a few seconds more. Then the syslog shows a number of blocks like:

sr 6:0:0:0: [sr1] Unhandled sense code
sr 6:0:0:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 6:0:0:0: [sr1] Sense Key : Medium Error [current] 
sr 6:0:0:0: [sr1] Add. Sense: L-EC uncorrectable error
sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 02 55 a0 00 00 02 00 00 00
end_request: I/O error, dev sr1, sector 611968
Buffer I/O error on device sr1, logical block 76496

sr 6:0:0:0: [sr1] Unhandled sense code
sr 6:0:0:0: [sr1] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
sr 6:0:0:0: [sr1] Sense Key : Medium Error [current] 
sr 6:0:0:0: [sr1] Add. Sense: L-EC uncorrectable error
sr 6:0:0:0: [sr1] CDB: Read(10): 28 00 00 02 55 a0 00 00 02 00 00 00
end_request: I/O error, dev sr1, sector 611968
Buffer I/O error on device sr1, logical block 76496

Maybe 3 or more. No device appears in the Plasma gui.
A manual mount /mnt/cdrom usually succeeds.

Expected would be that there are no messages and the device is coming up
(fast) in the gui and can be mounted from there.

Further details: I had problems with burned CDs from both drives.
However it is also possible to burn CDs which are accepted fine 
(which I did today twice).
It is unclear which CDs have this issue.
And it is strange that the data can still be read manually 
and read by windows xp.

I've tried linux-image-3.2.0-0.bpo.1-amd64 
(3.2.4-1~bpo60+1 Debian Backports:squeeze-backports)
which did not help.

Given the number of issues that are related to this,
it seems less likely that I really got unlucky with a number of suboptimal
CD media. Even if so, there still is an issue as windows XP and
manual mount read the CD fine.

Infos about the two drives:
cdrdao drive-info --device /dev/sr0
Cdrdao version 1.2.3 - (C) Andreas Mueller andr...@daneb.de
/dev/sr0: TSSTcorp CDDVDW SH-S203D  Rev: SB00
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x)

Maximum reading speed: 8468 kB/s
Current reading speed: 8468 kB/s
Maximum writing speed: 8468 kB/s
Current writing speed: 8468 kB/s
BurnProof supported: yes
JustLink supported: yes
JustSpeed supported: no


cdrdao drive-info --device /dev/sr1
Cdrdao version 1.2.3 - (C) Andreas Mueller andr...@daneb.de
/dev/sr1: TSSTcorp CDDVDW SE-S204N  Rev: TS00
Using driver: Generic SCSI-3/MMC - Version 2.0 (options 0x)

Maximum reading speed: 8468 kB/s
Current reading speed: 8468 kB/s
Maximum writing speed: 8468 kB/s
Current writing speed: 8468 kB/s
BurnProof supported: yes
JustLink supported: yes
JustSpeed supported: no


Here are related issue reports:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=583949
2.6.32-3-amd64 can't read DVDs/CDs (sometimes)
  From: Ben Hutchings b...@decadent.org.uk

  If anyone is still having trouble reading CDs or DVDs in the current
kernel version in stable (2.6.32-35) or unstable (3.0.0-1), please open
a *new* bug report.

There is a new one:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=641288

Bug#665835: marked as done (linux-image-3.2.0-1-amd64: copying huge file to a slow USB flash disk stalls the system)

Your message dated Thu, 27 Jun 2013 19:43:45 +0200
with message-id 20130627174345.GF4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #665835,
regarding linux-image-3.2.0-1-amd64: copying huge file to a slow USB flash disk 
stalls the system
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.)


-- 
665835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665835
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.6-1
Severity: normal


Hello,

I was trying to copy an iso image to a rather lame Emgeton brand USB
stick (using factory FAT format on the stick).

While doing so after some time most applications become unresponsive.

I can log in on the console, local xterms work, xscreensaver and window
manager works, xterms showing remote session and firefox are stalled (no
screen updates), and so is gkrellm and kvm.

I don't see anything releavant in the log.

The load on the system as shown with atop is very light except for the
flash drive which is 100% busy.


-- Package-specific info:
** Version:
Linux version 3.2.0-1-amd64 (Debian 3.2.2-1) (b...@decadent.org.uk) (gcc 
version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Wed Feb 1 08:56:58 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-1-amd64 
root=UUID=3b8f6a64-5899-462a-aec0-6ddefd878ecf ro fbcon=rotate:3 quiet

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[4140240.021049] usb 3-2.1: New USB device strings: Mfr=1, Product=3, 
SerialNumber=0
[4140240.021052] usb 3-2.1: Product: USB Productivity Option Keyboard( has the 
hub in # 1 )
[4140240.021054] usb 3-2.1: Manufacturer: Lite-On Technology
[4140240.031290] input: Lite-On Technology USB Productivity Option Keyboard( 
has the hub in # 1 ) as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2.1/3-2.1:1.0/input/input892
[4140240.031446] generic-usb 0003:04B3:301B.037B: input,hidraw0: USB HID v1.10 
Keyboard [Lite-On Technology USB Productivity Option Keyboard( has the hub in # 
1 )] on usb-:00:1a.0-2.1/input0
[4140240.036094] input: Lite-On Technology USB Productivity Option Keyboard( 
has the hub in # 1 ) as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2.1/3-2.1:1.1/input/input893
[4140240.036200] generic-usb 0003:04B3:301B.037C: input,hidraw1: USB HID v1.10 
Device [Lite-On Technology USB Productivity Option Keyboard( has the hub in # 1 
)] on usb-:00:1a.0-2.1/input1
[4140240.109047] usb 3-2.2: new low-speed USB device number 92 using uhci_hcd
[4140240.247043] usb 3-2.2: New USB device found, idVendor=046d, idProduct=c063
[4140240.247047] usb 3-2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[4140240.247050] usb 3-2.2: Product: DELL USB Laser Mouse
[4140240.247053] usb 3-2.2: Manufacturer: DELL
[4140240.265276] input: DELL DELL USB Laser Mouse as 
/devices/pci:00/:00:1a.0/usb3/3-2/3-2.2/3-2.2:1.0/input/input894
[4140240.265476] generic-usb 0003:046D:C063.037D: input,hidraw2: USB HID v1.10 
Mouse [DELL DELL USB Laser Mouse] on usb-:00:1a.0-2.2/input0
[4140272.360038] usb 3-2: USB disconnect, device number 90
[4140272.360042] usb 3-2.1: USB disconnect, device number 91
[4140272.492114] usb 3-2.2: USB disconnect, device number 92
[4140272.832021] usb 3-2: new full-speed USB device number 93 using uhci_hcd
[4140272.992050] usb 3-2: unable to read config index 0 descriptor/all
[4140272.992056] usb 3-2: can't read configurations, error -71
[4140273.048043] hub 3-0:1.0: unable to enumerate USB device on port 2
[4140273.584026] usb 3-2: new full-speed USB device number 95 using uhci_hcd
[4140273.648041] hub 3-0:1.0: unable to enumerate USB device on port 2
[4140274.128014] usb 3-2: new full-speed USB device number 96 using uhci_hcd
[4140274.305051] usb 3-2: New USB device found, idVendor=04b3, idProduct=301a
[4140274.305054] usb 3-2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[4140274.305056] usb 3-2: Product: USB 1.1 2port downstream low power hub
[4140274.305058] usb 3-2: Manufacturer: Lite-On Technology
[4140274.313073] hub 3-2:1.0: USB hub found
[4140274.314047] hub 3-2:1.0: 3 ports detected
[4140274.593055] usb 3-2.1: new full-speed USB device number 97 using uhci_hcd
[4140274.741051] usb 3-2.1: New USB device found, idVendor=04b3, idProduct=301b
[4140274.741055] usb 3-2.1: New USB device strings: Mfr=1, Product=3, 
SerialNumber=0
[4140274.741058] usb 3-2.1: Product: USB Productivity Option Keyboard( has the 
hub in # 1 )
[4140274.741061] usb 3-2.1: Manufacturer: Lite-On Technology
[4140274.751301] input: Lite-On Technology USB Productivity Option Keyboard(

Bug#668324: marked as done (linux-image-3.2.0-2-amd64: Module atl1c fails to recreate eth? interface)

Your message dated Thu, 27 Jun 2013 19:44:13 +0200
with message-id 20130627174413.GG4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #668324,
regarding linux-image-3.2.0-2-amd64: Module atl1c fails to recreate eth? 
interface
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.)


-- 
668324: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668324
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.9-1
Severity: normal

After using Internet connection through a USB ID 12d1:1436 device and sharing
the connection to eth0/atl1c interface for tens of minutes, I removed the USB
device. A few seconds later I noticed the eth0/atl1c interface hung. I
unplugged and plugged back the cable with no success on recovering the link.
Then I removed the driver with 'rmmod' and reloaded it with 'modprobe', twice
-- with cable plugged and unplugged. Here is the syslog info from that:

Apr 11 02:33:11 Netbook kernel: [207244.329454] atl1c :08:00.0: Refused to
change power state, currently in D3
Apr 11 02:33:11 Netbook kernel: [207244.329479] atl1c :08:00.0: PCI INT A
- GSI 18 (level, low) - IRQ 18
Apr 11 02:33:11 Netbook kernel: [207244.656073] atl1c :08:00.0: MAC state
machine can't be idle since disabled for 10ms second
Apr 11 02:33:11 Netbook kernel: [207244.656149] atl1c :08:00.0: PCI INT A
disabled
Apr 11 02:33:11 Netbook kernel: [207244.656228] atl1c: probe of :08:00.0
failed with error -5
Apr 11 02:33:28 Netbook kernel: [207261.769136] atl1c :08:00.0: Refused to
change power state, currently in D3
Apr 11 02:33:28 Netbook kernel: [207261.769161] atl1c :08:00.0: PCI INT A
- GSI 18 (level, low) - IRQ 18
Apr 11 02:33:28 Netbook kernel: [207262.100071] atl1c :08:00.0: MAC state
machine can't be idle since disabled for 10ms second
Apr 11 02:33:28 Netbook kernel: [207262.100144] atl1c :08:00.0: PCI INT A
disabled
Apr 11 02:33:28 Netbook kernel: [207262.100223] atl1c: probe of :08:00.0
failed with error -5

I rebooted the machine and the eth0/atl1c interface worked as usual.



-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.9-1) (debian-kernel@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Sun Mar 4 22:48:17 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 root=UUID=79faec86-032e-48d1-a1cf-
c17cb76e6fe2 ro quiet

** Not tainted

** Kernel log:
[6.421792] radeon :01:05.0: GTT: 512M 0xA000 -
0xBFFF
[6.426855] [drm] Detected VRAM RAM=336M, BAR=256M
[6.426861] [drm] RAM width 32bits DDR
[6.427063] [TTM] Zone  kernel: Available graphics memory: 1383208 kiB.
[6.427068] [TTM] Initializing pool allocator.
[6.427121] [drm] radeon: 336M of VRAM memory ready
[6.427125] [drm] radeon: 512M of GTT memory ready.
[6.427158] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[6.427162] [drm] Driver supports precise vblank timestamp query.
[6.427230] [drm] radeon: irq initialized.
[6.427240] [drm] GART: num cpu pages 131072, num gpu pages 131072
[6.431210] [drm] Loading RS780 Microcode
[6.463678] ieee80211 phy0: Selected rate control algorithm
'ath9k_rate_control'
[6.464786] Registered led device: ath9k-phy0
[6.464799] ieee80211 phy0: Atheros AR9280 Rev:2 mem=0xc966,
irq=19
[6.595202] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[6.595387] SP5100 TCO timer: mmio address 0xfec000f0 already in use
[6.658673] snd_hda_intel :00:14.2: PCI INT A - GSI 16 (level, low) -
IRQ 16
[6.669279] [drm] PCIE GART of 512M enabled (table at 0xC004).
[6.669586] radeon :01:05.0: WB enabled
[6.702591] [drm] ring test succeeded in 0 usecs
[6.702861] [drm] radeon: ib pool ready.
[6.702994] [drm] ib test succeeded in 0 usecs
[6.703637] [drm] Radeon Display Connectors
[6.703641] [drm] Connector 0:
[6.703644] [drm]   LVDS
[6.703649] [drm]   DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c
0x7e5c
[6.703653] [drm]   Encoders:
[6.703656] [drm] LCD1: INTERNAL_KLDSCP_LVTMA
[6.703659] [drm] Connector 1:
[6.703662] [drm]   VGA
[6.703667] [drm]   DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c
0x7e4c
[6.703670] [drm]   Encoders:
[6.703674] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[6.703715] [drm] radeon: power management initialized
[6.768076] psmouse serio2: synaptics: Touchpad model: 1, fw: 7.2, id:
0x1c0b1, caps: 0xd04733/0xa4/0xa
[6.812736] input: SynPS/2

Bug#667567: marked as done (linux: When connecting to external monitor, screen is jerky as soon as X loads.)

Your message dated Thu, 27 Jun 2013 19:44:13 +0200
with message-id 20130627174413.GG4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #667567,
regarding linux: When connecting to external monitor, screen is jerky as soon 
as X loads.
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.)


-- 
667567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667567
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-41squeeze2
Severity: normal
File: linux


Whenever I connect to an external monitor, the image jerks around and 
flickers as soon as X starts to load.  The pre-boot looks fine including 
picking a kernel to load.  As soon as X loads is where the trouble starts.

If I use a different kernel, 2.6.38 (compiled from kernel.org) then the 
problem goes away.  This only happens with the stock kernel (2.6.32-5-686)
 

-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 26 05:20:33 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-686 
root=UUID=c12d7448-3eb9-4c84-b82b-442573f5ac9e ro quiet

** Not tainted

** Kernel log:
[5.784176] ACPI: Battery Slot [BAT0] (battery present)
[5.784304] ACPI: WMI: Mapper loaded
[5.786326] input: Lid Switch as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0D:00/input/input4
[5.786501] ACPI: Lid Switch [LID0]
[5.786595] input: Power Button as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input5
[5.786639] ACPI: Power Button [PWRB]
[5.786750] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input6
[5.786786] ACPI: Power Button [PWRF]
[5.874096] i801_smbus :00:1f.3: PCI INT B - Link[LNKB] - GSI 5 
(level, low) - IRQ 5
[5.909873] intel_rng: FWH not detected
[5.953273] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[6.356830] [drm] Initialized drm 1.1.0 20060810
[6.432581] yenta_cardbus :02:05.0: CardBus bridge found [103c:3084]
[6.432603] yenta_cardbus :02:05.0: Using CSCINT to route CSC interrupts 
to PCI
[6.432607] yenta_cardbus :02:05.0: Routing CardBus interrupts to PCI
[6.432612] yenta_cardbus :02:05.0: TI: mfunc 0x0112, devctl 0x64
[6.563489] i915 :00:02.0: PCI INT A - Link[LNKA] - GSI 10 (level, 
low) - IRQ 10
[6.563497] i915 :00:02.0: setting latency timer to 64
[6.573198] [drm] set up 31M of stolen space
[6.711428] [drm] initialized overlay support
[6.962455] yenta_cardbus :02:05.0: ISA IRQ mask 0x00d8, PCI irq 11
[6.962461] yenta_cardbus :02:05.0: Socket status: 3006
[6.962467] pci_bus :02: Raising subordinate bus# of parent bus (#02) 
from #02 to #06
[6.962482] yenta_cardbus :02:05.0: pcmcia: parent PCI bridge I/O 
window: 0x3000 - 0x3fff
[6.962487] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3000-0x3fff: 
clean.
[6.962856] yenta_cardbus :02:05.0: pcmcia: parent PCI bridge Memory 
window: 0xe020 - 0xe02f
[6.962860] yenta_cardbus :02:05.0: pcmcia: parent PCI bridge Memory 
window: 0x2000 - 0x23ff
[7.639745] cfg80211: Using static regulatory domain info
[7.639750] cfg80211: Regulatory domain: US
[7.639752]  (start_freq - end_freq @ bandwidth), (max_antenna_gain, 
max_eirp)
[7.639757]  (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm)
[7.639762]  (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[7.639766]  (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[7.639770]  (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[7.639775]  (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm)
[7.639779]  (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm)
[7.640236] cfg80211: Calling CRDA for country: US
[7.715811] Console: switching to colour frame buffer device 128x48
[7.723763] fb0: inteldrmfb frame buffer device
[7.723767] registered panic notifier
[7.749061] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[7.859278] b43-phy0: Broadcom 4306 WLAN found (core revision 5)
[7.907109] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: 
clean.
[7.909215] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: 
excluding 0x4d0-0x4d7
[7.909930] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: 
clean.
[7.910522] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: 
clean.
[7.911298] pcmcia_socket

Bug#669894: marked as done (linux-image-3.2.0-2-amd64: Webcam (ov519) only works after replugging it several times)

Your message dated Thu, 27 Jun 2013 19:44:13 +0200
with message-id 20130627174413.GG4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #669894,
regarding linux-image-3.2.0-2-amd64: Webcam (ov519) only works after replugging 
it several times
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.)


-- 
669894: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669894
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.15-1
Severity: normal

I have a Trust 320 Spacecam webcam here, which works fine, but only
after I replug it several times.

At boot time it fails to get initialized:

[2.068557] usbcore: registered new interface driver usbhid
[2.068558] usbhid: USB HID core driver
[2.152152] usb 1-2.2: new full-speed USB device number 5 using ehci_hcd
[2.240152] usb 1-2.2: device descriptor read/64, error 8
[2.432150] usb 1-2.2: device descriptor read/64, error 8
[2.624153] usb 1-2.2: new full-speed USB device number 6 using ehci_hcd
[2.712149] usb 1-2.2: device descriptor read/64, error 8
other stuff
[2.904149] usb 1-2.2: device descriptor read/64, error 8
[3.096152] usb 1-2.2: new full-speed USB device number 7 using ehci_hcd
[3.116523] usb 1-2.2: device descriptor read/8, error -61
[3.236522] usb 1-2.2: device descriptor read/8, error -61
[3.428150] usb 1-2.2: new full-speed USB device number 8 using ehci_hcd
[3.448523] usb 1-2.2: device descriptor read/8, error -61
[3.568523] usb 1-2.2: device descriptor read/8, error -61
[3.672157] hub 1-2:1.0: unable to enumerate USB device on port 2

when I replug it, it still fails:

[20206.700129] usb 1-2.2: new full-speed USB device number 9 using ehci_hcd
[20206.788133] usb 1-2.2: device descriptor read/64, error 8
[20206.980147] usb 1-2.2: device descriptor read/64, error 8
[20207.172135] usb 1-2.2: new full-speed USB device number 10 using ehci_hcd
[20207.260131] usb 1-2.2: device descriptor read/64, error 8
[20207.452145] usb 1-2.2: device descriptor read/64, error 8
[20207.644143] usb 1-2.2: new full-speed USB device number 11 using ehci_hcd
[20207.664510] usb 1-2.2: device descriptor read/8, error -61
[20207.784395] usb 1-2.2: device descriptor read/8, error -61
[20207.976145] usb 1-2.2: new full-speed USB device number 12 using ehci_hcd
[20207.996513] usb 1-2.2: device descriptor read/8, error -61
[20208.116515] usb 1-2.2: device descriptor read/8, error -61
[20208.220157] hub 1-2:1.0: unable to enumerate USB device on port 2

then I replug it again and it works 100% fine:

[20279.404085] usb 1-2.2: new full-speed USB device number 13 using ehci_hcd
[20279.513459] usb 1-2.2: New USB device found, idVendor=05a9, idProduct=8519
[20279.513462] usb 1-2.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[20279.513465] usb 1-2.2: Product: USB Camera
[20279.513466] usb 1-2.2: Manufacturer: OmniVision Technologies, Inc.
[20279.714000] Linux media interface: v0.10
[20279.727781] Linux video capture interface: v2.00
[20279.730517] gspca_main: v2.14.0 registered
[20279.733294] gspca_main: ov519-2.14.0 probing 05a9:8519
[20279.916286] input: ov519 as 
/devices/pci:00/:00:1a.7/usb1/1-2/1-2.2/input/input8
[20279.916482] usbcore: registered new interface driver ov519
[20279.917794] usbcore: registered new interface driver snd-usb-audio

As it works fine after replugging (twice), I guess it's not a problem
with the hardware...

-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.15-1) (debian-kernel@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Sun Apr 15 16:47:38 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-amd64 
root=UUID=12635a70-3def-4b39-bc78-1ee0ad29a2d2 ro quiet

** Tainted: PWO (4609)
 * Proprietary module has been loaded.
 * Taint on warning.
 * Out-of-tree module has been loaded.

** Kernel log:
[19194.144009] eth1: no IPv6 routers present
[19242.064006] eth1: no IPv6 routers present
[19524.928020] usb 1-5: reset high-speed USB device number 3 using ehci_hcd
[19586.21] usb 1-5: reset high-speed USB device number 3 using ehci_hcd
[19587.840008] eth1: no IPv6 routers present
[19635.536011] eth1: no IPv6 routers present
[19683.856011] eth1: no IPv6 routers present
[19731.584009] eth1: no IPv6 routers present
[20076.080007] eth1: no IPv6 routers present
[20124.624007] eth1: no IPv6 routers present
[20172.256007] eth1: no IPv6 routers present
[20206.700129] usb 1-2.2: new full-speed USB device number 9 using ehci_hcd
[20206.788133] usb 1-2.2: device descriptor

Bug#666781: marked as done (linux-image-2.6.32-5-amd64: can't mount cdrom (/dev/sr0))

Your message dated Thu, 27 Jun 2013 19:44:13 +0200
with message-id 20130627174413.GG4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #666781,
regarding linux-image-2.6.32-5-amd64: can't mount cdrom (/dev/sr0)
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.)


-- 
666781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-41squeeze2
Severity: normal

root@hsctb:/etc# mount /dev/sr0 /media/cdrom0
mount: /dev/sr0: unknown device

that is what returns when manually mounting. I don't see anything if I just
insert a cd...



-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Mar 22 17:26:33 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=5915530d-4e98-4979-86ae-72de126c51ab ro quiet

** Tainted: P (1)
 * Proprietary module has been loaded.

** Kernel log:
[350012.453280] usb 1-3.2: usbfs: interface 1 claimed by usblp while 'usb' sets 
config #1
[350012.460801] usb 1-3.1.1: usbfs: interface 0 claimed by usblp while 'usb' 
sets config #1
[350094.146126] usb 1-3.2: USB disconnect, address 8
[350094.146596] usblp0: removed
[350094.361323] usb 1-3.2: new high speed USB device using ehci_hcd and address 
9
[350094.461551] usb 1-3.2: New USB device found, idVendor=03f0, idProduct=5c11
[350094.461556] usb 1-3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[350094.461560] usb 1-3.2: Product: Photosmart C4200 series
[350094.461562] usb 1-3.2: Manufacturer: HP
[350094.461565] usb 1-3.2: SerialNumber: CN78EJG16C04VP
[350094.461695] usb 1-3.2: configuration #1 chosen from 1 choice
[350094.462356] usblp0: USB Bidirectional printer dev 9 if 1 alt 0 proto 2 vid 
0x03F0 pid 0x5C11
[350094.466260] scsi318 : SCSI emulation for USB Mass Storage devices
[350094.466419] usb-storage: device found at 9
[350094.466423] usb-storage: waiting for device to settle before scanning
[350095.882865] usb 1-3.2: usbfs: interface 1 claimed by usblp while 'usb' sets 
config #1
[350095.898726] usb 1-3.1.1: usbfs: interface 0 claimed by usblp while 'usb' 
sets config #1
[350099.265581] usb 1-3.2: USB disconnect, address 9
[350099.266052] usblp0: removed
[350099.469041] usb 1-3.2: new high speed USB device using ehci_hcd and address 
10
[350099.564881] usb 1-3.2: New USB device found, idVendor=03f0, idProduct=5c11
[350099.564892] usb 1-3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[350099.564901] usb 1-3.2: Product: Photosmart C4200 series
[350099.564907] usb 1-3.2: Manufacturer: HP
[350099.564912] usb 1-3.2: SerialNumber: CN78EJG16C04VP
[350099.565165] usb 1-3.2: configuration #1 chosen from 1 choice
[350099.566506] usblp0: USB Bidirectional printer dev 10 if 1 alt 0 proto 2 vid 
0x03F0 pid 0x5C11
[350099.567081] scsi319 : SCSI emulation for USB Mass Storage devices
[350099.567480] usb-storage: device found at 10
[350099.567485] usb-storage: waiting for device to settle before scanning
[350104.565935] usb-storage: device scan complete
[350104.567267] scsi 319:0:0:0: Direct-Access HP   Photosmart C4250 
1.00 PQ: 0 ANSI: 5
[350104.568648] sd 319:0:0:0: Attached scsi generic sg3 type 0
[350104.576664] sd 319:0:0:0: [sdc] Attached SCSI removable disk
[350108.224737] usb 1-3.2: USB disconnect, address 10
[350108.225123] usblp0: removed
[350108.385727] hub 1-3:1.0: unable to enumerate USB device on port 2
[350108.680938] usb 1-3.2: new high speed USB device using ehci_hcd and address 
12
[350108.698840] hub 1-3:1.0: unable to enumerate USB device on port 2
[350108.937406] usb 1-3.2: new high speed USB device using ehci_hcd and address 
13
[350109.032680] usb 1-3.2: New USB device found, idVendor=03f0, idProduct=5c11
[350109.032691] usb 1-3.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[350109.032699] usb 1-3.2: Product: Photosmart C4200 series
[350109.032705] usb 1-3.2: Manufacturer: HP
[350109.032710] usb 1-3.2: SerialNumber: CN78EJG16C04VP
[350109.032952] usb 1-3.2: configuration #1 chosen from 1 choice
[350109.035621] usblp0: USB Bidirectional printer dev 13 if 1 alt 0 proto 2 vid 
0x03F0 pid 0x5C11
[350109.036068] scsi320 : SCSI emulation for USB Mass Storage devices
[350109.036370] usb-storage: device found at 13
[350109.036377] usb-storage: waiting for device to settle before scanning
[350112.320966] usb 1-3.2: usbfs: interface 1 claimed by usblp while 'usb' sets 
config #1
[350112.332703] usb 1-3.1.1: usbfs: interface 0

Bug#558265: marked as done (Warns about firmware that is not needed)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #558265,
regarding Warns about firmware that is not needed
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.)


-- 
558265: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=558265
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6

I got the following message when upgrading the kernel about a firmware
that might be missing.  On this particular, the firmware is not needed
because it doesn't have a l8168 chip.

Could this firmware warning be smarter, e.g. by looking at the actual
chip and only showing the warning when the firmware is necessary?

  ┌──┤ Configuring linux-image-2.6.32-rc6-iop32x ├──┐
  │ │
  │ Required firmware files may be missing  │
  │ │
  │ This system is currently running Linux 2.6.30-1-iop32x and you are  │
  │ installing Linux 2.6.32-rc6-iop32x.  In the new version some of the │
  │ drivers used on this system may require additional firmware files:  │
  │ │
  │ r8169: rtl8168d-2.fw, rtl8168d-1.fw │
  │ │
  │ Most firmware files are not included in the Debian system because no│
  │ source code is available for them.  You may need to reconfigure the │
  │ package manager to include the non-free section of the Debian archive   │
  │ before you can install these firmware files.│

-- 
Martin Michlmayr
http://www.cyrius.com/


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and has
been tagged wontfix for some time, we're closing it now.

Cheers,
Moritz---End Message---

Bug#668547: marked as done (linux-image-3.2.0-2-686-pae: spammed by cfg80211 : Calling CRDA to update world regulatory domain)

Your message dated Thu, 27 Jun 2013 19:44:13 +0200
with message-id 20130627174413.GG4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #668547,
regarding linux-image-3.2.0-2-686-pae: spammed by cfg80211 : Calling CRDA to 
update world regulatory domain
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.)


-- 
668547: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668547
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.12-1
Severity: normal

Hi.

As you can see from this logs excerpts, I get spammed by cfg80211 in kernel 
logs every 5 seconds or so :-(

This tends to be filling up /var, if not paying attention.

I guess there must be something wrong somewhere...

Thanks in advance.

-- Package-specific info:
** Version:
Linux version 3.2.0-2-686-pae (Debian 3.2.12-1) 
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP 
Tue Mar 20 19:48:26 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae 
root=UUID=6ed8ff22-1b20-476a-b52a-f2c2c698c022 ro debug ignore_loglevel

** Not tainted

** Kernel log:
[ 9037.539543] cfg80211: Calling CRDA for country: 97
[ 9040.688025] cfg80211: Calling CRDA to update world regulatory domain
[ 9040.692551] cfg80211: World regulatory domain updated:
[ 9040.692555] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[ 9040.692559] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 9040.692561] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[ 9040.692564] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[ 9040.692567] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 9040.692569] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 9040.692578] cfg80211: Calling CRDA for country: 97
[ 9043.840100] cfg80211: Calling CRDA to update world regulatory domain
[ 9043.851239] cfg80211: World regulatory domain updated:
[ 9043.851249] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[ 9043.851258] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 9043.851266] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[ 9043.851274] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[ 9043.851282] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[ 9043.851290] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)

** Model information
not available

** Loaded modules:
cryptd
aes_i586
aes_generic
nls_utf8
nls_cp437
vfat
fat
hidp
snd_hrtimer
ip6table_filter
ip6_tables
ebtable_nat
ebtables
microcode
ipt_MASQUERADE
iptable_nat
nf_nat
nf_conntrack_ipv4
nf_defrag_ipv4
xt_state
nf_conntrack
ipt_REJECT
acpi_cpufreq
mperf
cpufreq_conservative
xt_CHECKSUM
iptable_mangle
cpufreq_powersave
xt_tcpudp
cpufreq_userspace
iptable_filter
cpufreq_stats
ip_tables
x_tables
tun
bridge
stp
ppdev
lp
bnep
rfcomm
binfmt_misc
uinput
fuse
kvm_intel
kvm
dm_crypt
configfs
coretemp
loop
firewire_sbp2
snd_hda_codec_hdmi
snd_hda_codec_idt
joydev
snd_hda_intel
snd_hda_codec
snd_hwdep
snd_pcm_oss
snd_mixer_oss
snd_pcm
snd_seq_midi
i915
arc4
snd_rawmidi
iwlwifi
drm_kms_helper
btusb
mac80211
snd_seq_midi_event
drm
bluetooth
cfg80211
psmouse
snd_seq
pcmcia
iTCO_wdt
parport_pc
snd_timer
snd_seq_device
dell_laptop
parport
dell_wmi
i2c_algo_bit
snd
crc16
iTCO_vendor_support
dcdbas
yenta_socket
i2c_i801
pcmcia_rsrc
serio_raw
pcspkr
sparse_keymap
processor
button
evdev
soundcore
i2c_core
rfkill
battery
snd_page_alloc
pcmcia_core
ac
video
wmi
power_supply
ext3
jbd
mbcache
raid10
raid456
async_raid6_recov
async_pq
usbhid
hid
raid6_pq
async_xor
xor
async_memcpy
async_tx
raid1
raid0
multipath
linear
md_mod
dm_mirror
dm_region_hash
dm_log
dm_mod
sd_mod
crc_t10dif
sr_mod
cdrom
usb_storage
uas
uhci_hcd
ahci
libahci
sdhci_pci
firewire_ohci
libata
thermal
thermal_sys
firewire_core
crc_itu_t
tg3
libphy
sdhci
mmc_core
ehci_hcd
scsi_mod
usbcore
usb_common

** Network interface configuration:

auto lo
iface lo inet loopback

iface eth0static inet static
address 157.159.110.21
netmask 255.255.255.0
gateway 157.159.110.1
dns-nameservers 157.159.10.12 157.159.10.13

















iface wlan0nab inet static
   wireless-mode managed
   wireless-essid Nabaztag4D
address 192.168.0.2
 netmask 255.255.255.0




iface wlan0freebox inet dhcp
 wireless-mode managed

Bug#521515: marked as done (linux-headers-2.6.29-1-amd64: please restore symlinks into -common)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #521515,
regarding linux-headers-2.6.29-1-amd64: please restore symlinks into -common
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.)


-- 
521515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521515
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-headers-2.6.29-1-amd64
Version: 2.6.29-1
Severity: normal

Historically, /usr/src/linux-headers-VERSION-FLAVOR used to contain
symlinks into /usr/src/linux-headers-VERSION-common for anything not at
least potentially flavor-specific.  As of 2.6.29-1, that no longer
holds, causing trouble for packages such as openafs-modules-source that
don't entirely defer to the kbuild framework.  (OpenAFS is particularly
special due to its age and support for a wide range of platforms, and
makes symlinks to /lib/modules/VERSION-FLAVOR/build/include/linux in
its build tree so that it can variously include the headers as h/*.h,
netinet/*.h, and sys/*.h.)

I have worked around the problem on my own system by throwing together
a package containing a portion of the dropped symlinks (those from and
into .../linux), but would appreciate it if you could please reinstate
the symlinks in the flavor-specific linux-headers packages.

Thanks!

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)

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

Versions of packages linux-headers-2.6.29-1-amd64 depends on:
ii  gcc-4.3   4.3.3-5The GNU C compiler
ii  linux-headers-2.6.29-1-common 2.6.29-1   Common header files for Linux 2.6.
ii  linux-kbuild-2.6.29   2.6.29-1   Kbuild infrastructure for Linux 2.

linux-headers-2.6.29-1-amd64 recommends no packages.

linux-headers-2.6.29-1-amd64 suggests no packages.

-- no debconf information


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and has
been tagged wontfix for some time, we're closing it now.

Cheers,
Moritz---End Message---

Bug#483781: marked as done (FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #483781,
regarding FAT: utf8 is not a recommended IO charset for FAT filesystems, 
filesystem will be case sensitive!
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.)


-- 
483781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-image-2.6.25-2-686
Version: 2.6.25-4
Severity: wishlist

One sees in dmesg
  FAT: utf8 is not a recommended IO charset for FAT filesystems,
  filesystem will be case sensitive!
even
# env - LC_ALL=C mount /fat
won't turn it off. How can one turn off the warning?

Anyway, the file system is not as sensitive as one thinks anyway:
$ touch K k
touch: cannot touch `k': File exists
$ mount
/dev/sdb1 on /mnt/usb/cf type vfat (rw,shortname=mixed,..)
$ touch Kk KK
$ touch bb BB
$ find -type f -mmin -11 -ls
   133   14 drwxr-xr-x   2 jidanni  jidanni 14336  5月 31 08:45 .
   2080 -rw-r--r--   1 jidanni  jidanni 0  5月 31 08:43 ./K
   2090 -rw-r--r--   1 jidanni  jidanni 0  5月 31 08:44 ./Kk
   2360 -rw-r--r--   1 jidanni  jidanni 0  5月 31 08:45 ./bb


See also http://ubuntuforums.org/showthread.php?t=264501 ,
https://launchpad.net/ubuntu/+bug/62321


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and has
been tagged wontfix for some time, we're closing it now.

Cheers,
Moritz---End Message---

Bug#502486: marked as done (mount: mounts VFAT filesystem with buggy iocharset=utf8 !)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #483781,
regarding mount: mounts VFAT filesystem with buggy iocharset=utf8 !
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.)


-- 
483781: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=483781
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: mount
Version: 2.13.1.1-1
Severity: important


  Hello,

  Unlike what is said in mount(1), mount now mounts VFAT filesystems
with iocharset=utf8. This is *very bad*, as it is not supported by the
kernel:

[ 9239.043602] FAT: utf8 is not a recommended IO charset for FAT filesystems, 
filesystem will be case sensitive!

  It can lead to severe filesystem corruption (see for instance
#443514, and the thourough analysis in bug #500540, which I think
might be due to this one).

  This is apparently not linked to the locale: 
$ LC_ALL=en_GB.iso88591 mount /dev/sdc /mnt  tail -n1 /proc/mounts 
/dev/sdc /mnt vfat 
rw,fmask=0022,dmask=0022,allow_utime=17,codepage=cp437,iocharset=utf8 0 0
$ LC_ALL=C mount /dev/sdc /mnt  tail -n1 /proc/mounts
/dev/sdc /mnt vfat 
rw,fmask=0022,dmask=0022,allow_utime=17,codepage=cp437,iocharset=utf8 0 0

  This *must* be fixed quickly. I'm sincerely tempted to tag this as
serious or even grave as for #500540, and this is stopping me from
fixing #443514 properly.

  Regards,

Vincent


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

Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB, LC_CTYPE=en_GB (charmap=ISO-8859-1) (ignored: LC_ALL set to 
en_GB)
Shell: /bin/sh linked to /bin/dash

Versions of packages mount depends on:
ii  libblkid1 1.41.3-1   block device id library
ii  libc6 2.7-15 GNU C Library: Shared libraries
ii  libselinux1   2.0.65-5   SELinux shared libraries
ii  libuuid1  1.41.3-1   universally unique id library

mount recommends no packages.

Versions of packages mount suggests:
pn  nfs-commonnone (no description available)

-- no debconf information


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and has
been tagged wontfix for some time, we're closing it now.

Cheers,
Moritz---End Message---

Bug#673107: marked as done (kirkwood: TCP checksum errors when using MTU 9000)

Your message dated Thu, 27 Jun 2013 19:44:39 +0200
with message-id 20130627174439.GH4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #673107,
regarding kirkwood: TCP checksum errors when using MTU 9000
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.)


-- 
673107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673107
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-45

A user on the Kirkwood platform reported TCP checksum errors when
using MTU 9000:
http://forum.qnap.com/viewtopic.php?f=147t=59281p=266527#p266527

This has been previously discussed:
http://lists.debian.org/debian-arm/2009/11/msg00087.html

iirc a patch went into the kernel to set the limits for the various
platforms (orion, kirkwood)... or maybe it was just discussed and
never went in.

Arnaud, can you investigate whether this patch really went in or
what's going on here?

-- 
Martin Michlmayr
http://www.cyrius.com/


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older 
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with 
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by 
sending
a mail to cont...@bugs.debian.org with the following three commands included in 
the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
Moritz---End Message---

Bug#639919: marked as done (linux-2.6: please enable DEBUG_STRICT_USER_COPY_CHECKS)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #639919,
regarding linux-2.6: please enable DEBUG_STRICT_USER_COPY_CHECKS
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.)


-- 
639919: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=639919
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.0.0-3
Severity: wishlist

Hey,

this was already asked as part of #605090 but I had the impression that
opening a bug was needed since people were aware, but I was wrong.

So here's a wishlist bug. Could DEBUG_STRICT_USER_COPY_CHECKS be
enabled?

It's used to enforce checks for the various copy_* to prevent overflows
etc. This is done at compile time, and, afaict, it worked fine (on
i386/amd64 Debian kernels) since 2.6.37.

Regards,
-- 
Yves-Alexis


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

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


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and has
been tagged wontfix for some time, we're closing it now.

Cheers,
Moritz---End Message---

Bug#671518: marked as done (linux-image-3.2: snd_hda_codec_hdmi OOPS on load when transparent_hugepage=always is set on kernel commandline)

Your message dated Thu, 27 Jun 2013 19:44:39 +0200
with message-id 20130627174439.GH4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #671518,
regarding linux-image-3.2: snd_hda_codec_hdmi OOPS on load when 
transparent_hugepage=always is set on kernel commandline
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.)


-- 
671518: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671518
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.4-1~bpo60+1
Severity: normal
File: linux-image-3.2


1. Computer has HDMI port (not in use for display), 
uses snd_hda_codec_hdmi driver.
2. udev startup loads snd_hda_codec_hdmi at boot.
3. Reboot and add transparent_hugepages=always to kernel commandline.
4. OOPS during boot (after initramfs, during main fs udev startup)
inside snd_hda_codec_hdmi.
4a. FS is read-only, don't save oops log.
5. blacklist snd_hda_codec_hdmi.
6. Boots fine.

Will test on Intel GMA wheezy system later.

-- Package-specific info:
** Version:
Linux version 3.2.0-0.bpo.1-amd64 (Debian 3.2.4-1~bpo60+1) 
(b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Sat Feb 11 
08:41:32 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-0.bpo.1-amd64 root=/dev/mapper/squeeze ro ro 
transparent_hugepage=always quiet

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

** Kernel log:
[   21.650089] mdadm: sending ioctl 1261 to a partition!
[   21.650092] mdadm: sending ioctl 1261 to a partition!
[   21.655618] [fglrx] Maximum main memory to use for locked dma buffers: 7770 
MBytes.
[   21.655798] [fglrx]   vendor: 1002 device: 683d count: 1
[   21.656166] [fglrx] ioport: bar 4, base 0xce00, size: 0x100
[   21.656176] pci :01:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18
[   21.656180] pci :01:00.0: setting latency timer to 64
[   21.656377] [fglrx] Kernel PAT support is enabled
[   21.656388] [fglrx] module loaded - fglrx 8.96.4 [Apr  5 2012] with 1 minors
[   21.670804] MCE: In-kernel MCE decoding enabled.
[   21.683265] EDAC MC: Ver: 2.1.0
[   21.684349] AMD64 EDAC driver v3.4.0
[   21.684384] EDAC amd64: DRAM ECC disabled.
[   21.684389] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
[   21.684390]  Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
[   21.684391]  (Note that use of the override may cause unknown side effects.)
[   21.877030] ACPI: resource piix4_smbus [io  0x0b00-0x0b07] conflicts with 
ACPI region SOR1 [io 0xb00-0xb0f]
[   21.877033] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[   21.899301] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[   21.899356] SP5100 TCO timer: mmio address 0xfec000f0 already in use
[   21.982556] snd_emu10k1 :05:06.0: PCI INT A - GSI 20 (level, low) - 
IRQ 20
[   21.988642] Installing spdif_bug patch: SB Audigy 2 ZS [SB0350]
[   21.995784] snd_hda_intel :01:00.1: PCI INT B - GSI 19 (level, low) - 
IRQ 19
[   21.995827] snd_hda_intel :01:00.1: irq 46 for MSI/MSI-X
[   21.995840] snd_hda_intel :01:00.1: setting latency timer to 64
[   22.130790] mdadm: sending ioctl 1261 to a partition!
[   22.130793] mdadm: sending ioctl 1261 to a partition!
[   22.132448] mdadm: sending ioctl 1261 to a partition!
[   22.132450] mdadm: sending ioctl 1261 to a partition!
[   22.132976] mdadm: sending ioctl 1261 to a partition!
[   22.132977] mdadm: sending ioctl 1261 to a partition!
[   22.197880] logitech-djreceiver 0003:046D:C52B.0003: hiddev0,hidraw0: USB 
HID v1.11 Device [Logitech USB Receiver] on usb-:00:12.0-3/input2
[   22.204917] input: Logitech Unifying Device. Wireless PID:1028 as 
/devices/pci:00/:00:12.0/usb5/5-3/5-3:1.2/0003:046D:C52B.0003/input/input4
[   22.204997] logitech-djdevice 0003:046D:C52B.0004: input,hidraw1: USB HID 
v1.11 Mouse [Logitech Unifying Device. Wireless PID:1028] on 
usb-:00:12.0-3:1
[   22.717223] EXT4-fs (dm-4): re-mounted. Opts: (null)
[   22.861048] EXT4-fs (dm-4): re-mounted. Opts: 
user_xattr,errors=remount-ro,commit=60,journal_checksum,stripe=768
[   22.943906] loop: module loaded
[   22.968951] it87: Found IT8718F chip at 0x228, revision 5
[   22.968972] it87: Beeping is supported
[   23.047489] sr 11:0:0:0: [sr0]  Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[   23.047492] sr 11:0:0:0: [sr0]  Sense Key : Illegal Request [current] 
[   23.047495] sr 11:0:0:0: [sr0]  Add. Sense: Illegal mode for this track
[

Bug#671116: marked as done (linux-image-3.2.0-2-686-pae: LCD backlight setting doesn't work on HP ProBook 451x)

Your message dated Thu, 27 Jun 2013 19:44:39 +0200
with message-id 20130627174439.GH4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #671116,
regarding linux-image-3.2.0-2-686-pae: LCD backlight setting doesn't work on HP 
ProBook 451x
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.)


-- 
671116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671116
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.15-1
Severity: normal

Hi. This is bugging me for quite some time (more than 6 months now).

I can not configure the LCD backlight brightness on my HP ProBook 4515s.

I tried booting with acpi_backlight=legacy|vendor, but all they did
was to keep the brightness to maximum; keyboard shortcuts didn't do
anything and also echo 10  /sys/class/backlight/acpi_video0/brightness
didn't do anything.

Booting without the acpi_backlight kernel parameter just dims the LCD to
a lower brightness level, but again, I can't change it neither through
the keyboard, nor the sysfs interface. I preffer to keep it to maximum
with the acpi_backlight=vendor.

I also tried booting with acpi_osi=Linux, but it made no change
whatsoever.

Changing the brightness through the sysfs interface does nothing (it
appears it does, but the LCD doesn't change brightness physicaly):

root@x:~# ls /sys/class/backlight/acpi_video0/
actual_brightness  bl_power  brightness  device  max_brightness  power
subsystem  type  uevent
root@x:~# cat /sys/class/backlight/acpi_video0/max_brightness 
24
root@x:~# echo 10  /sys/class/backlight/acpi_video0/brightness 
root@x:~# cat /sys/class/backlight/acpi_video0/actual_brightness
10
root@x:~# cat /sys/class/backlight/acpi_video0/brightness
10

Thanks.

-- Package-specific info:
** Version:
Linux version 3.2.0-2-686-pae (Debian 3.2.15-1) 
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-3) ) #1 SMP 
Sun Apr 15 17:56:31 UTC 2012

** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-2-686-pae 
root=UUID=c82fd34e-9549-4229-b8d2-5448428acfeb ro quiet splash acpi_osi=Linux 
acpi_backlight=legacy

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

** Kernel log:
[9.336426] wl: module license 'MIXED/Proprietary' taints kernel.
[9.336431] Disabling lock debugging due to kernel taint
[9.375908] wl :06:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[9.375921] wl :06:00.0: setting latency timer to 64
[9.417024] lib80211_crypt: registered algorithm 'TKIP'
[9.417348] wlan0: Broadcom BCM4315 802.11 Hybrid Wireless Controller 
5.100.82.112
[9.480705] udevd[385]: renamed network interface eth0 to eth1
[9.608445] psmouse serio4: synaptics: Touchpad model: 1, fw: 7.2, id: 
0x1c0b1, caps: 0xd04733/0xa4/0xa
[9.649756] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio4/input/input8
[   10.083499] Bluetooth: Core ver 2.16
[   10.083523] NET: Registered protocol family 31
[   10.083526] Bluetooth: HCI device and connection manager initialized
[   10.083530] Bluetooth: HCI socket layer initialized
[   10.083532] Bluetooth: L2CAP socket layer initialized
[   10.083741] Bluetooth: SCO socket layer initialized
[   10.115934] Bluetooth: Generic Bluetooth USB driver ver 0.6
[   10.116189] usbcore: registered new interface driver btusb
[   10.167102] [fglrx] Maximum main memory to use for locked dma buffers: 2644 
MBytes.
[   10.167193] [fglrx]   vendor: 1002 device: 9612 count: 1
[   10.167733] [fglrx] ioport: bar 1, base 0x5000, size: 0x100
[   10.167750] pci :01:05.0: PCI INT A - GSI 18 (level, low) - IRQ 18
[   10.167756] pci :01:05.0: setting latency timer to 64
[   10.168317] [fglrx] Kernel PAT support is enabled
[   10.168343] [fglrx] module loaded - fglrx 8.95.3 [Mar  8 2012] with 1 minors
[   10.413215] snd_hda_intel :00:14.2: power state changed by ACPI to D0
[   10.413223] snd_hda_intel :00:14.2: power state changed by ACPI to D0
[   10.413233] snd_hda_intel :00:14.2: PCI INT A - GSI 16 (level, low) - 
IRQ 16
[   10.683313] Linux media interface: v0.10
[   10.721783] Linux video capture interface: v2.00
[   10.802078] uvcvideo: Found UVC 1.00 device CNF8243 (04f2:b159)
[   10.859944] input: CNF8243 as 
/devices/pci:00/:00:13.2/usb2/2-2/2-2:1.0/input/input9
[   10.860060] usbcore: registered new interface driver uvcvideo
[   10.860063] USB Video Class driver (1.1.1)
[   11.035918] input: HDA Digital PCBeep as 
/devices/pci:00/:00:14.2/input/input10
[   11.043631] snd_hda_intel :01:05.1: PCI INT

Bug#642005: marked as done (general: maximum size of SHM memory blocks to low)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #642005,
regarding general: maximum size of SHM memory blocks to low
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.)


-- 
642005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=642005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: general
Severity: grave
Justification: renders package unusable

I know the program I'll basing this on isn't part of Debian but here it goes.
I'm an Avast user and in my search for a solution I found that this problem is
due to the basic kernel variable settings which renders Avast unable to update
the virus database and probably effects other programs. The people on the Avast
forums have found a fix but it makes it mandates an extra hook commander to
make a Debian Live image to find system infections. Here is the forums link for
the problem and solution: http://forum.avast.com/index.php?topic=57775.0 I hope
this can be addressed in a update soon so that people can use Debian Live to
find and remove infections on their computers a little bit better.



-- System Information:
Debian Release: 6.0.2  Note: Custom Debian Live build
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores)


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and has
been tagged wontfix for some time, we're closing it now.

Cheers,
Moritz---End Message---

Bug#705711: marked as done (linux-image-2.6.32-5-686: AMD A6-3500 APU with Radeon HD 6530D not supported)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #705711,
regarding linux-image-2.6.32-5-686: AMD A6-3500 APU with Radeon HD 6530D not 
supported
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.)


-- 
705711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=705711
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-46
Severity: wishlist
Tags: squeeze

This is just to let you know.
I don't know if a backport to support that driver is worthwhile or not, complex
or trivial, etc...
The VESA driver is unstable, sometimes X starts, sometimes not, when it starts
it doesn't support the monitors native resolution.
Thanks for your consideration!
Happy hacking!


-- Package-specific info:
** Version:
Linux version 2.6.32-5-686 (Debian 2.6.32-46) (da...@debian.org) (gcc version 
4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 23 09:49:36 UTC 2012

** Command line:
initrd=inteligentes/initrd.img fsprotect=50% 
nfsroot=/usr/local/terminales/inteligentes BOOT_IMAGE=inteligentes/vmlinuz 

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

** Kernel log:
[5.884366] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.887527] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.890714] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.895858] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.900191] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.903692] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.907855] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.912529] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.915711] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.919022] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.921823] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.925810] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.928731] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.932748] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.936422] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.940484] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.943392] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.947691] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.950899] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.956648] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.959580] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.963901] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.968694] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.972268] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.975335] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.978244] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.981024] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[5.984400] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[6.177528] usbcore: registered new interface driver usbserial
[6.177586] USB Serial support registered for generic
[6.177637] usbcore: registered new interface driver usbserial_generic
[6.177686] usbserial: USB Serial Driver core
[6.183778] USB Serial support registered for Handspring Visor / Palm OS
[6.183836] USB Serial support registered for Sony Clie 3.5
[6.183979] USB Serial support registered for Sony Clie 5.0
[6.184098] usbcore: registered new interface driver visor
[6.184135] visor: USB HandSpring Visor / Palm OS driver
[7.641971] svc: failed to register lockdv1 RPC service (errno 97).
[8.161350] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[8.163707] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[8.165977] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[8.168390] hda_codec: num_steps = 0 for NID=0xc (ctl = Front Playback 
Volume)
[8.170707] hda_codec: num_steps = 0 for NID=0xc (ctl = Front

Bug#630788: marked as done (linux-image-2.6.32-5-486: squeeze kernel doesn't include accept_ra=2 patch)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #630788,
regarding linux-image-2.6.32-5-486: squeeze kernel doesn't include accept_ra=2 
patch
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.)


-- 
630788: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630788
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-34squeeze1
Severity: wishlist
Tags: squeeze ipv6

The squeeze kernel doesn't have this patch:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=65e9b62d4503849b10bedfc29bff0473760cc597

Apparently that hit the kernel in 2.6.37, according to:
http://lists.debian.org/debian-ipv6/2011/05/msg00033.html

I'd really like that patch to be in the squeeze kernel, and I suspect the Adam
Spragg (who started that debian-ipv6 mailing list thread) would also like it.
The mailing list thread goes on and Bernard Scmidt suggests a work around 
(hence this being a wishlist bug).

This bug is my vote to get this patch into squeeze somehow (be that a
squeeze-n-half kernel, or a cherry picked patch to a later squeeze kernel).
I'll understand if you tag this wont-fix.

Cheers,
Geoff Crompton

-- Package-specific info:
** Version:
Linux version 2.6.32-5-486 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 Wed May 18 06:47:47 UTC 2011

** Command line:
BOOT_IMAGE=/vmlinuz-2.6.32-5-486 root=UUID=c412fa10-c869-4263-8a6e-02189d4fd4db 
ro console=ttyS0,19200n8 quiet

** Not tainted

** Kernel log:
[1119040.794420] Redirect from 112.200.253.139 on ppp0 about 112.200.211.142 
ignored.
[1119040.794461]   Advised path = 59.167.191.61 - 112.200.211.142
[1119040.794686] Redirect from 112.200.199.247 on ppp0 about 112.200.211.142 
ignored.
[1119040.794725]   Advised path = 59.167.191.61 - 112.200.211.142
[1119040.794938] Redirect from 112.200.238.21 on ppp0 about 112.200.211.142 
ignored.
[1119040.794977]   Advised path = 59.167.191.61 - 112.200.211.142
[1119040.801207] Redirect from 112.200.253.139 on ppp0 about 112.200.211.142 
ignored.
[1119040.801249]   Advised path = 59.167.191.61 - 112.200.211.142
[1131677.688120] __ratelimit: 6 callbacks suppressed
[1131677.688208] Redirect from 88.35.141.162 on ppp0 about 88.35.141.161 
ignored.
[1131677.688240]   Advised path = 59.167.191.61 - 140.80.100.10
[1243192.370958] Redirect from 89.18.23.222 on ppp0 about 89.18.23.8 ignored.
[1243192.370999]   Advised path = 59.167.191.61 - 89.18.23.8
[1284946.445214] device ppp0 entered promiscuous mode
[1284974.638661] device ppp0 left promiscuous mode
[1285170.093280] device ppp0 entered promiscuous mode
[1287879.642751] device ppp0 left promiscuous mode
[1336209.931739] device ppp0 entered promiscuous mode
[1336214.700390] device ppp0 left promiscuous mode
[1336226.366128] device ppp0 entered promiscuous mode
[1336241.063930] device ppp0 left promiscuous mode
[1336699.388234] device ppp0 entered promiscuous mode
[1336722.923456] device ppp0 left promiscuous mode
[1337080.779590] device ppp0 entered promiscuous mode
[1337095.010656] device ppp0 left promiscuous mode
[1337100.418061] device ppp0 entered promiscuous mode
[1337100.470448] device ppp0 left promiscuous mode
[1337110.222334] device ppp0 entered promiscuous mode
[1337113.858415] device ppp0 left promiscuous mode
[1337125.011096] device ppp0 entered promiscuous mode
[1337130.054529] device ppp0 left promiscuous mode
[1337134.612233] device ppp0 entered promiscuous mode
[1337196.293168] device ppp0 left promiscuous mode
[1337537.072394] device ppp0 entered promiscuous mode
[1337578.201078] device ppp0 left promiscuous mode
[1345382.369542] Redirect from 62.103.73.215 on ppp0 about 80.106.108.128 
ignored.
[1345382.369584]   Advised path = 59.167.191.61 - 125.125.10.5
[1345385.477505] Redirect from 62.103.73.215 on ppp0 about 80.106.108.128 
ignored.
[1345385.477546]   Advised path = 59.167.191.61 - 125.125.10.5
[1347462.420273] Redirect from 89.39.243.159 on ppp0 about 89.39.243.2 ignored.
[1347462.420314]   Advised path = 59.167.191.61 - 89.39.243.2
[1347462.427980] Redirect from 89.39.243.159 on ppp0 about 89.39.243.2 ignored.
[1347462.428021]   Advised path = 59.167.191.61 - 89.39.243.2
[1347462.448313] Redirect from 89.39.243.3 on ppp0 about 89.39.243.2 ignored.
[1347462.448354]   Advised path = 59.167.191.61 - 89.39.243.2
[1347462.448576] Redirect from 89.39.243.3 on ppp0 about 89.39.243.2 ignored.
[1347462.448613]   Advised path = 59.167.191.61 -

Bug#670783: marked as done (linux-image-3.2.0-2-686-pae: Very slow network connection with centrino ultimate on 802.11 N)

Your message dated Thu, 27 Jun 2013 19:44:39 +0200
with message-id 20130627174439.GH4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #670783,
regarding linux-image-3.2.0-2-686-pae: Very slow network connection with 
centrino ultimate on 802.11 N
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.)


-- 
670783: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670783
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.15-1
Severity: normal

Hi,

On Wheezy I'm experiencing very slow network connection under 802.11n with 
centrino ultimate:

I've found similar bug reports on redhat and ubuntu:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/836250
https://bugzilla.redhat.com/show_bug.cgi?id=708747
https://bugzilla.redhat.com/show_bug.cgi?id=804259

And some report on the backport list:
http://lists.debian.org/debian-backports/2012/02/msg00029.html

Here is a simple ping session showing that disabling 802.11n help a lot:

ccomb@ccomb:~$ ping soleil.anybox.fr
PING soleil.anybox.fr (88.191.140.57) 56(84) bytes of data.
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=1 ttl=55 time=710 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=2 ttl=55 time=855 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=3 ttl=55 time=692 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=4 ttl=55 time=44.5 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=6 ttl=55 time=1995 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=7 ttl=55 time=991 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=8 ttl=55 time=30.8 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=9 ttl=55 time=701 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=11 ttl=55 time=979 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=12 ttl=55 time=63.4 ms
^C
--- soleil.anybox.fr ping statistics ---
13 packets transmitted, 10 received, 23% packet loss, time 27898ms
rtt min/avg/max/mdev = 30.899/706.709/1995.724/561.135 ms, pipe 2
$ #disconnect from wifi
$ sudo rmmod iwlwifi
$ sudo modprobe iwlwifi 11n_disable=1
$ #reconnect to wifi
$ ping soleil.anybox.fr
PING soleil.anybox.fr (88.191.140.57) 56(84) bytes of data.
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=1 ttl=55 time=23.0 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=2 ttl=55 time=22.7 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=3 ttl=55 time=21.6 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=4 ttl=55 time=21.8 ms
64 bytes from ded1.anybox.fr (88.191.140.57): icmp_req=5 ttl=55 time=21.8 ms
^C
--- soleil.anybox.fr ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 21.673/22.232/23.024/0.576 ms


-- Package-specific info:
** Version:
Linux version 3.2.0-2-686-pae (Debian 3.2.15-1) 
(debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-3) ) #1 SMP 
Sun Apr 15 17:56:31 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae 
root=UUID=708f758f-2756-4957-9fe1-69e050282801 ro quiet i915.i915_enable_rc6=1

** Tainted: O (4096)
 * Out-of-tree module has been loaded.

** Kernel log:
[42193.031320] e1000e: eth0 NIC Link is Down
[42193.278399] thinkpad_acpi: unknown possible thermal alarm or keyboard event 
received
[42193.278402] thinkpad_acpi: unhandled HKEY event 0x6040
[42193.278403] thinkpad_acpi: please report the conditions when this event 
happened to ibm-acpi-de...@lists.sourceforge.net
[42193.278745] thinkpad_acpi: EC reports that Thermal Table has changed
[42193.378630] thinkpad_acpi: undocked from hotplug port replicator
[42196.559706] e1000e :00:19.0: PME# enabled
[42202.143297] iwlwifi :03:00.0: Tx aggregation enabled on ra = 
8e:d5:5b:ea:a2:a4 tid = 0
[42952.258678] smapi smapi: smapi_request: SMAPI error: SMAPI function is not 
available (func=2118)
[42952.258690] smapi smapi: get_force_discharge: failed for bat=0: SMAPI 
function is not available
[42952.318580] smapi smapi: smapi_request: SMAPI error: SMAPI function is not 
available (func=2116)
[42952.318592] smapi smapi: __get_real_thresh: cannot get start_thresh of 
bat=0: SMAPI function is not available
[43597.753909] CPU1: Package power limit notification (total events = 4)
[43597.753913] CPU2: Package power limit notification (total events = 4)
[43597.753916] CPU3: Package power limit notification (total events = 4)
[43597.753919] CPU0: Package power limit notification (total events = 4)
[43597.764950] CPU2: Package power limit normal
[43597.764953] CPU3: Package power

Bug#670492: marked as done (linux-image-2.6.32-5-amd64: RTL8111/8168B Wake on LAN does not work)

Your message dated Thu, 27 Jun 2013 19:44:39 +0200
with message-id 20130627174439.GH4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #670492,
regarding linux-image-2.6.32-5-amd64: RTL8111/8168B Wake on LAN does not work
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.)


-- 
670492: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670492
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.32-41squeeze2
Severity: normal

The title says it all. I already tried the ethtool setting from the debian 
wiki. No success. 

I found one solution by using the r8168 driver from realtek. With this driver 
WOL works. 

The r8168 driver has an other problem. Sometimes the pc does not wake up from 
Suspend to Ram. 

-- Package-specific info:
** Version:
Linux version 2.6.32-5-amd64 (Debian 2.6.32-41squeeze2) (da...@debian.org) (gcc 
version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Mar 22 17:26:33 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 
root=UUID=bc115a2e-a23d-4c00-9b7e-b30b2040006e ro quiet

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

** Kernel log:
[  554.552019] SMP alternatives: switching to UP code
[  554.562694] PM: Creating hibernation image: 
[  554.564006] PM: Need to copy 100351 pages
[  554.564006] PM: Normal pages needed: 100351 + 1024, available pages: 685633
[  554.564006] PM: Restoring platform NVS memory
[  554.564006] CPU0: Thermal monitoring handled by SMI
[  554.564006] Force enabled HPET at resume
[  554.564006] Enabling non-boot CPUs ...
[  554.564006] SMP alternatives: switching to SMP code
[  554.572812] Booting processor 1 APIC 0x1 ip 0x6000
[  554.564006] Initializing CPU#1
[  554.564006] CPU: Trace cache: 12K uops, L1 D cache: 16K
[  554.564006] CPU: L2 cache: 1024K
[  554.564006] CPU 1/0x1 - Node 0
[  554.564006] CPU: Physical Processor ID: 0
[  554.564006] CPU: Processor Core ID: 1
[  554.564006] CPU1: Thermal monitoring handled by SMI
[  554.660124] CPU1: Intel(R) Pentium(R) D CPU 3.20GHz stepping 04
[  554.660265] CPU0 attaching NULL sched-domain.
[  554.688046] CPU0 attaching sched-domain:
[  554.688051]  domain 0: span 0-1 level CPU
[  554.688054]   groups: group 88000180fd00 cpus 0 group 88000190fd00 
cpus 1
[  554.688064] CPU1 attaching sched-domain:
[  554.688067]  domain 0: span 0-1 level CPU
[  554.688070]   groups: group 88000190fd00 cpus 1 group 88000180fd00 
cpus 0
[  554.688446] CPU1 is up
[  554.689087] ACPI: Waking up from system sleep state S4
[  554.690227] Intel ICH :00:1e.2: restoring config space at offset 0x1 
(was 0x297, writing 0x293)
[  554.690294] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 
0x2880001, writing 0x2880005)
[  554.690324] ahci :00:1f.2: restoring config space at offset 0x1 (was 
0x2b00403, writing 0x2b00407)
[  554.690402] radeon :01:00.0: restoring config space at offset 0x1 (was 
0x100107, writing 0x100507)
[  554.690493] tg3 :03:00.0: restoring config space at offset 0xc (was 0x0, 
writing 0x7823)
[  554.690581] r8168 :04:00.0: restoring config space at offset 0x3 (was 
0x8, writing 0x20)
[  554.690590] r8168 :04:00.0: restoring config space at offset 0x1 (was 
0x100147, writing 0x100547)
[  554.704035] firewire_ohci :0a:09.0: restoring config space at offset 0xf 
(was 0x4020100, writing 0x4020105)
[  554.704056] firewire_ohci :0a:09.0: restoring config space at offset 0x3 
(was 0x0, writing 0x4008)
[  554.704063] firewire_ohci :0a:09.0: restoring config space at offset 0x1 
(was 0x210, writing 0x2100156)
[  554.767951] uhci_hcd :00:1d.0: setting latency timer to 64
[  554.767988] usb usb2: root hub lost power or was reset
[  554.768038] uhci_hcd :00:1d.1: setting latency timer to 64
[  554.768072] usb usb3: root hub lost power or was reset
[  554.768089] uhci_hcd :00:1d.2: setting latency timer to 64
[  554.768121] usb usb4: root hub lost power or was reset
[  554.768139] uhci_hcd :00:1d.3: setting latency timer to 64
[  554.768171] usb usb5: root hub lost power or was reset
[  554.768189] ehci_hcd :00:1d.7: setting latency timer to 64
[  554.768194] usb usb1: root hub lost power or was reset
[  554.772068] ehci_hcd :00:1d.7: cache line size of 128 is not supported
[  554.772084] pci :00:1e.0: setting latency timer to 64
[  554.772099] Intel ICH :00:1e.2: PCI INT A - GSI 22 (level, low) - IRQ 
22
[  554.772105] Intel ICH :00:1e.2: setting latency timer to 64
[  554.781906] ata_piix :00:1f.1: PCI INT A -

Bug#572639: marked as done (Please enable CONFIG_B43_FORCE_PIO)

Your message dated Thu, 27 Jun 2013 19:45:22 +0200
with message-id 20130627174522.GI4252@pisco.westfalen.local
and subject line Closing
has caused the Debian Bug report #572639,
regarding Please enable CONFIG_B43_FORCE_PIO
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.)


-- 
572639: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.33-1~experimental.2
Severity: wishlist


Please enable CONFIG_B43_FORCE_PIO.
It is required for using b43 driver on low-power LP-PHY bcm4312.
http://bugzilla.kernel.org/show_bug.cgi?id=14761
-- 
Hiroyuki Yamamoto
4096R/520304DC
 A75D B285 7050 4BF9 AEDA  91AC 3A10 59C6 5203 04DC


---End Message---
---BeginMessage---
Hi,
your bug has been filed against the linux-2.6 source package and has
been tagged wontfix for some time, we're closing it now.

Cheers,
Moritz---End Message---

Bug#664855: marked as done (linux-image-3.2.0-2-686-pae: Uhhuh. NMI received for unknown reason 31 on CPU 3. nmi_watchdog=0 fixes it)

Your message dated Thu, 27 Jun 2013 19:58:01 +0200
with message-id 20130627175801.gb6...@inutil.org
and subject line Re: linux-image-3.2.0-2-686-pae: Uhhuh. NMI received for 
unknown reason 31 on CPU 3. nmi_watchdog=0 fixes it
has caused the Debian Bug report #664855,
regarding linux-image-3.2.0-2-686-pae: Uhhuh. NMI received for unknown reason 
31 on CPU 3. nmi_watchdog=0 fixes it
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.)


-- 
664855: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=664855
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.9-1
Severity: normal

After upgrading to 3.2.0-2-688-pae (from 3.2.0-1-686-pae), I started getting 
tons of log messages:

Mar 21 05:02:13 clementine kernel: [  557.195949] Uhhuh. NMI received for 
unknown reason 31 on CPU 3.
Mar 21 05:02:13 clementine kernel: [  557.198327] Do you have a strange power 
saving mode enabled?
Mar 21 05:02:13 clementine kernel: [  557.198327] Dazed and confused, but 
trying to continue
Mar 21 05:02:13 clementine kernel: [  557.198327] Uhhuh. NMI received for 
unknown reason 21 on CPU 3.
Mar 21 05:02:13 clementine kernel: [  557.198327] Do you have a strange power 
saving mode enabled?
Mar 21 05:02:13 clementine kernel: [  557.198327] Dazed and confused, but 
trying to continue

And this would effectively hang the system.

I found different people talking about it on the internet:
workaround:
https://bugzilla.redhat.com/show_bug.cgi?id=688547
patch:
https://lkml.org/lkml/2012/2/6/365


I didn't try the patch, but the workaround of adding nmi_watchdog=0 to the 
kernel command line did the trick.

I am running on a cpu family: 15, which is supposedly the problem:
vendor_id   : GenuineIntel
cpu family  : 15
model   : 6
model name  : Genuine Intel(R) CPU 3.20GHz
stepping: 2
microcode   : 0x5
cpu MHz : 3191.831
cache size  : 2048 KB

However, I'm not having the problem on another server:
processor   : 0
vendor_id   : GenuineIntel
cpu family  : 15
model   : 4
model name  : Intel(R) Pentium(R) 4 CPU 3.00GHz
stepping: 3
microcode   : 0x5
cpu MHz : 3000.091
cache size  : 2048 KB

so I'm not sure if the family=15 is the complete issue.

The system seems to be running fine (for an hour now) with the watchdog turned 
off.
I'll report back here if either it breaks again, or if my other server starts 
breaking too.

This didn't happen on the prior kernel at all.

From the internet reports, it appears that it happens on 3.3 kernels as well, 
so I didn't try upgrading to unstable.

-- Package-specific info:
** Version:
Linux version 3.2.0-2-686-pae (Debian 3.2.9-1) (debian-kernel@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Mar 5 01:59:18 UTC 2012

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.2.0-2-686-pae 
root=UUID=317ecf6d-c170-4dbf-985f-29f2b2057bf6 ro hpet=disable nmi_watchdog=0

** Not tainted

** Kernel log:
[6.132510] ACPI: Invalid PBLK length [5]
[6.184891] i801_smbus :00:1f.3: PCI INT B - GSI 20 (level, low) - IRQ 
20
[6.218022] iTCO_vendor_support: vendor-support=0
[6.252668] iTCO_wdt: Intel TCO WatchDog Timer Driver v1.07
[6.252893] iTCO_wdt: Found a 631xESB/632xESB TCO device (Version=2, 
TCOBASE=0x0460)
[6.253136] iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0)
[6.411843] [drm] radeon defaulting to kernel modesetting.
[6.411929] [drm] radeon kernel modesetting enabled.
[6.412218] radeon :10:0c.0: PCI INT A - GSI 17 (level, low) - IRQ 17
[6.412583] [drm] initializing kernel modesetting (RV100 0x1002:0x515E 
0x1002:0x515E).
[6.412727] [drm] register mmio base: 0xAAA0
[6.412803] [drm] register mmio size: 65536
[6.420875] radeon :10:0c.0: VRAM: 128M 0xA000 - 
0xA7FF (16M used)
[6.420974] radeon :10:0c.0: GTT: 512M 0x8000 - 
0x9FFF
[6.421077] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[6.421156] [drm] Driver supports precise vblank timestamp query.
[6.421245] [drm] radeon: irq initialized.
[6.423897] [drm] Detected VRAM RAM=128M, BAR=128M
[6.423978] [drm] RAM width 16bits DDR
[6.424163] [TTM] Zone  kernel: Available graphics memory: 429870 kiB.
[6.424244] [TTM] Zone highmem: Available graphics memory: 2067444 kiB.
[6.424322] [TTM] Initializing pool allocator.
[6.424435] [drm] radeon: 16M of VRAM memory ready
[6.424512] [drm] radeon: 512M of GTT memory ready.
[6.424609] [drm] GART: num cpu pages

Bug#663981: marked as done (linux-image-3.2.0-2-amd64: mdadm complain during booting)

Your message dated Thu, 27 Jun 2013 19:57:54 +0200
with message-id 20130627175754.ga6...@inutil.org
and subject line Re: Bug#663981: linux-image-3.2.0-2-amd64: mdadm complain 
during booting
has caused the Debian Bug report #663981,
regarding linux-image-3.2.0-2-amd64: mdadm complain during booting
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.)


-- 
663981: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663981
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 3.2.9-1
Severity: normal

Hello!
Sorry my bad english.

After switch to kernel 3.x.x in syslog these messages:

[2.383412] mdadm: sending ioctl 800c0910 to a partition!
[2.383483] mdadm: sending ioctl 1261 to a partition!

-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.9-1) (debian-kernel@lists.debian.org) 
(gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Mar 5 02:56:07 UTC 2012

** Command line:
BOOT_IMAGE=Linux ro root=901

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

** Kernel log:
[2.383261] mdadm: sending ioctl 800c0910 to a partition!
[2.383345] mdadm: sending ioctl 800c0910 to a partition!
[2.383412] mdadm: sending ioctl 800c0910 to a partition!
[2.383483] mdadm: sending ioctl 1261 to a partition!
[2.383548] mdadm: sending ioctl 1261 to a partition!
[2.383790] mdadm: sending ioctl 1261 to a partition!
[2.383857] mdadm: sending ioctl 1261 to a partition!
[2.415406] mdadm: sending ioctl 1261 to a partition!
[2.415475] mdadm: sending ioctl 1261 to a partition!
[2.415686] mdadm: sending ioctl 1261 to a partition!
[2.426348] md: md0 stopped.
[2.427770] md: bindsda1
[2.427940] md: bindsdb1
[2.429822] bio: create slab bio-1 at 1
[2.429987] md/raid1:md0: active with 2 out of 2 mirrors
[2.430091] md0: detected capacity change from 0 to 1085603840
[2.430894]  md0: unknown partition table
[2.482738] md: md1 stopped.
[2.483935] md: bindsda2
[2.484105] md: bindsdb2
[2.485084] md/raid1:md1: active with 2 out of 2 mirrors
[2.485169] md1: detected capacity change from 0 to 318984486912
[2.487146]  md1: unknown partition table
[2.608330] PM: Starting manual resume from disk
[2.608413] PM: Hibernation image partition 9:0 present
[2.608415] PM: Looking for hibernation image.
[2.608584] PM: Image not found (code -22)
[2.608587] PM: Hibernation image not present or could not be loaded.
[2.617257] SGI XFS with ACLs, security attributes, realtime, large 
block/inode numbers, no debug enabled
[2.617638] SGI XFS Quota Management subsystem
[2.618931] XFS (md1): Mounting Filesystem
[2.747562] XFS (md1): Ending clean mount
[5.108931] udevd[372]: starting version 175
[5.924878] wmi: Mapper loaded
[6.047692] input: Power Button as 
/devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input2
[6.047783] ACPI: Power Button [PWRB]
[6.047899] input: Power Button as 
/devices/LNXSYSTM:00/LNXPWRBN:00/input/input3
[6.047983] ACPI: Power Button [PWRF]
[6.049529] ACPI: processor limited to max C-state 1
[6.433546] parport_serial :04:05.0: PCI INT A - GSI 20 (level, low) - 
IRQ 20
[6.433659] parport0: PC-style at 0xe000, irq 20 [PCSPP,TRISTATE,EPP]
[6.464738] ACPI: resource piix4_smbus [io  0x0b00-0x0b07] conflicts with 
ACPI region SOR1 [io 0xb00-0xb0f]
[6.464830] ACPI: If an ACPI driver is available for this device, you should 
use it instead of the native driver
[6.548540] :04:05.0: ttyS0 at I/O 0xe800 (irq = 20) is a 16550A
[6.580495] :04:05.0: ttyS1 at I/O 0xe400 (irq = 20) is a 16550A
[6.580576] SP5100 TCO timer: SP5100 TCO WatchDog Timer Driver v0.01
[6.581175] SP5100 TCO timer: mmio address 0xfec000f0 already in use
[6.684063] MCE: In-kernel MCE decoding enabled.
[6.780998] input: PC Speaker as /devices/platform/pcspkr/input/input4
[6.837276] EDAC MC: Ver: 2.1.0
[6.884895] AMD64 EDAC driver v3.4.0
[6.885060] EDAC amd64: DRAM ECC disabled.
[6.885135] EDAC amd64: ECC disabled in the BIOS or no ECC capability, 
module will not load.
[6.885136]  Either enable ECC checking or force module loading by setting 
'ecc_enable_override'.
[6.885137]  (Note that use of the override may cause unknown side effects.)
[7.015948] nvidia: module license 'NVIDIA' taints kernel.
[7.016030] Disabling lock debugging due to kernel taint
[7.105737] nvidia :02:00.0: PCI INT A - GSI 18 (level, low) - IRQ 18
[7.105816] nvidia

Processed: kirkwood: TCP checksum errors when using MTU 9000

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

 reopen 673107
Bug #673107 {Done: Moritz Mühlenhoff j...@inutil.org} [linux-2.6] kirkwood: 
TCP checksum errors when using MTU 9000
Bug reopened
Ignoring request to alter fixed versions of bug #673107 to the same values 
previously set
 reassign 673107 src:linux
Bug #673107 [linux-2.6] kirkwood: TCP checksum errors when using MTU 9000
Bug reassigned from package 'linux-2.6' to 'src:linux'.
No longer marked as found in versions 2.6.32-45.
Ignoring request to alter fixed versions of bug #673107 to the same values 
previously set
 thanks
Stopping processing here.

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

Bug#673107: kirkwood: TCP checksum errors when using MTU 9000

2013-06-27 Thread Damien Martins


cat /etc/debian_version
7.1

uname -a
Linux nassounet 3.2.0-4-orion5x #1 Debian 3.2.41-2 armv5tel GNU/Linux

When settings MTU to 9000 (ifconfig eth0 mtu 9000) :
[4098918.032189] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up, 
1000 Mb/s, full duplex, flow control disabled


When having heavy network usage (300MB file transfer using NFS) :

[4101722.937455] swapper: page allocation failure: order:2, mode:0x20
[4101722.943705] [c0017f90] (unwind_backtrace+0x0/0xe0) from 
[c0091194] (warn_alloc_failed+0xec/0x118)
[4101722.953115] [c0091194] (warn_alloc_failed+0xec/0x118) from 
[c009348c] (__alloc_pages_nodemask+0x634/0x718)
[4101722.963303] [c009348c] (__alloc_pages_nodemask+0x634/0x718) from 
[c028caec] (cache_alloc_refill+0x25c/0x510)
[4101722.973678] [c028caec] (cache_alloc_refill+0x25c/0x510) from 
[c00bc610] (__kmalloc_track_caller+0xa0/0x15c)
[4101722.983967] [c00bc610] (__kmalloc_track_caller+0xa0/0x15c) from 
[c01fb860] (__alloc_skb+0x50/0xf0)
[4101722.993455] [c01fb860] (__alloc_skb+0x50/0xf0) from [c01fb918] 
(dev_alloc_skb+0x18/0x3c)
[4101723.002126] [c01fb918] (dev_alloc_skb+0x18/0x3c) from 
[bf12dd78] (rxq_refill+0x7c/0x1e8 [mv643xx_eth])
[4101723.012020] [bf12dd78] (rxq_refill+0x7c/0x1e8 [mv643xx_eth]) from 
[bf12e4e8] (mv643xx_eth_poll+0x560/0x5e8 [mv643xx_eth])
[4101723.023542] [bf12e4e8] (mv643xx_eth_poll+0x560/0x5e8 
[mv643xx_eth]) from [c02053cc] (net_rx_action+0x88/0x26c)
[4101723.034089] [c02053cc] (net_rx_action+0x88/0x26c) from 
[c0030ad0] (__do_softirq+0xe8/0x1ec)
[4101723.042969] [c0030ad0] (__do_softirq+0xe8/0x1ec) from 
[c0030f1c] (irq_exit+0x40/0x94)
[4101723.051344] [c0030f1c] (irq_exit+0x40/0x94) from [c0013078] 
(handle_IRQ+0x64/0x84)
[4101723.059447] [c0013078] (handle_IRQ+0x64/0x84) from [c0011dd4] 
(__irq_svc+0x34/0x64)
[4101723.067635] [c0011dd4] (__irq_svc+0x34/0x64) from [c0013360] 
(cpu_idle+0x8c/0xcc)
[4101723.075657] [c0013360] (cpu_idle+0x8c/0xcc) from [c039871c] 
(start_kernel+0x2ac/0x300)

[4101723.084072] Mem-info:
[4101723.086518] Normal per-cpu:
[4101723.089486] CPU0: hi:   90, btch:  15 usd:  75
[4101723.094474] active_anon:3779 inactive_anon:10916 isolated_anon:0
[4101723.094489]  active_file:11966 inactive_file:12463 isolated_file:0
[4101723.094506]  unevictable:0 dirty:69 writeback:0 unstable:0
[4101723.094521]  free:14147 slab_reclaimable:5963 slab_unreclaimable:2227
[4101723.094538]  mapped:3882 shmem:172 pagetables:651 bounce:0
[4101723.124899] Normal free:56588kB min:2032kB low:2540kB high:3048kB 
active_anon:15116kB inactive_anon:43664kB active_file:47864kB 
inactive_file:49852kB unevictable:0kB isolated(anon):0kB 
isolated(file):0kB present:259072kB mlocked:0kB dirty:276kB 
writeback:0kB mapped:15528kB shmem:688kB slab_reclaimable:23852kB 
slab_unreclaimable:8908kB kernel_stack:2144kB pagetables:2604kB 
unstable:0kB bounce:0kB writeback_tmp:0kB pages_scanned:0 
all_unreclaimable? no

[4101723.164829] lowmem_reserve[]: 0 0
[4101723.168338] Normal: 5201*4kB 4473*8kB 0*16kB 0*32kB 0*64kB 0*128kB 
0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 56588kB

[4101723.179363] 26133 total pagecache pages
[4101723.183363] 1534 pages in swap cache
[4101723.187111] Swap cache stats: add 1073080, delete 1071546, find 
30858632/31034636

[4101723.194751] Free swap  = 892276kB
[4101723.198232] Total swap = 979836kB
[4101723.213363] 65536 pages of RAM
[4101723.216583] 14709 free pages
[4101723.219633] 1651 reserved pages
[4101723.222942] 8190 slab pages
[4101723.225907] 22105 pages shared
[4101723.229129] 1534 pages swap cached

--
Cordialement,
Damien Martins


--
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/51cc8e49.6060...@makelofine.org

Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with entry failed, hardware error 0x80000021

2013-06-27 Thread Gleb Natapov

On Thu, Jun 27, 2013 at 04:09:50PM +0200, Stefan Pietsch wrote:
 On 26.06.2013 12:47, Gleb Natapov wrote:
  On Mon, Jun 24, 2013 at 10:42:57PM +0200, Stefan Pietsch wrote:
  On 24.06.2013 14:30, Gleb Natapov wrote:
  On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
  As soon as I remove kvmvapic.bin the virtual machine boots with
  qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
  emulate_invalid_guest_state=0 or emulate_invalid_guest_state=1 make
  no difference.
 
  Please send your patches.
  Here it is, run with it and kvmvapic.bin present. See what is printed in
  dmesg after the failure.
 
 
  diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
  index f4a5b3f..65488a4 100644
  --- a/arch/x86/kvm/vmx.c
  +++ b/arch/x86/kvm/vmx.c
  @@ -3385,6 +3385,7 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
   {
struct vcpu_vmx *vmx = to_vmx(vcpu);
u32 ar;
  + unsigned long rip;
   
if (vmx-rmode.vm86_active  seg != VCPU_SREG_LDTR) {
*var = vmx-rmode.segs[seg];
  @@ -3408,6 +3409,9 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
var-db = (ar  14)  1;
var-g = (ar  15)  1;
var-unusable = (ar  16)  1;
  + rip = kvm_rip_read(vcpu);
  + if ((rip == 0xc101611c || rip == 0xc101611a)  seg == VCPU_SREG_FS)
  + printk(base=%p limit=%p selector=%x ar=%x\n, var-base, 
  var-limit, var-selector, ar);
   }
   
   static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)
 
 
  Booting kernel Linux 3.10-rc5 with your patch applied produces these
  messages in dmesg when starting a virtual machine:
 
  emulate_invalid_guest_state=0
  [  118.732151] base= limit=  (null) selector=ffff ar=0
  [  118.732341] base= limit=  (null) selector=ffff ar=0
 
  I've butchered printk format, but it gives me the idea of what is going
  on anyway. Can you try the patch below with
  emulate_invalid_guest_state=0|1?
  
  
  diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
  index f4a5b3f..eb062ce 100644
  --- a/arch/x86/kvm/vmx.c
  +++ b/arch/x86/kvm/vmx.c
  @@ -3395,19 +3395,20 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
  var-selector = vmx_read_guest_seg_selector(vmx, seg);
  return;
  }
  +
  var-base = vmx_read_guest_seg_base(vmx, seg);
  var-limit = vmx_read_guest_seg_limit(vmx, seg);
  var-selector = vmx_read_guest_seg_selector(vmx, seg);
  ar = vmx_read_guest_seg_ar(vmx, seg);
  +   var-unusable = (ar  16)  1;
  var-type = ar  15;
  var-s = (ar  4)  1;
  var-dpl = (ar  5)  3;
  -   var-present = (ar  7)  1;
  +   var-present = !var-unusable;
  var-avl = (ar  12)  1;
  var-l = (ar  13)  1;
  var-db = (ar  14)  1;
  var-g = (ar  15)  1;
  -   var-unusable = (ar  16)  1;
   }
   
   static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)
 
 
 Kernel 3.10-rc5 with your latest patch applied can successfully boot the
 virtual machine with emulate_invalid_guest_state 0 or 1.
Excellent. I will send the patch to the list. Thank you for your help
in tracking it.

--
Gleb.


-- 
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/20130627200103.ga25...@redhat.com

Processed: Re: Bug#673107: kirkwood: TCP checksum errors when using MTU 9000

Processing control commands:

 reassign -1 src:linux-2.6 2.6.32-45
Bug #673107 [src:linux] kirkwood: TCP checksum errors when using MTU 9000
Bug reassigned from package 'src:linux' to 'src:linux-2.6'.
Warning: Unknown package 'src:linux-2.6'
Warning: Unknown package 'src:linux-2.6'
Ignoring request to alter found versions of bug #673107 to the same values 
previously set
Warning: Unknown package 'src:linux-2.6'
Warning: Unknown package 'src:linux-2.6'
Ignoring request to alter fixed versions of bug #673107 to the same values 
previously set
Warning: Unknown package 'src:linux-2.6'
Bug #673107 [src:linux-2.6] kirkwood: TCP checksum errors when using MTU 9000
Warning: Unknown package 'src:linux-2.6'
Marked as found in versions linux-2.6/2.6.32-45.
Warning: Unknown package 'src:linux-2.6'
 close -1
Bug #673107 [src:linux-2.6] kirkwood: TCP checksum errors when using MTU 9000
Warning: Unknown package 'src:linux-2.6'
Marked Bug as done
Warning: Unknown package 'src:linux-2.6'

-- 
673107: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673107
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.b673107.137236324920028.transcr...@bugs.debian.org

Bug#673107: kirkwood: TCP checksum errors when using MTU 9000

Control: reassign -1 src:linux-2.6 2.6.32-45
Control: close -1

Don't reopen random unrelated bugs, thanks.

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/20130627200046.go4...@decadent.org.uk

Processed: reopening 627782, reassign 627782 to src:linux, found 627782 in 3.9.6-1

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

 reopen 627782
Bug #627782 {Done: Moritz Mühlenhoff j...@inutil.org} [linux-2.6] 
fcntl(F_SETFL, O_APPEND) has no effect on aufs filesystem
Bug reopened
Ignoring request to alter fixed versions of bug #627782 to the same values 
previously set
 reassign 627782 src:linux
Bug #627782 [linux-2.6] fcntl(F_SETFL, O_APPEND) has no effect on aufs 
filesystem
Bug reassigned from package 'linux-2.6' to 'src:linux'.
No longer marked as found in versions 2.6.39-2.
Ignoring request to alter fixed versions of bug #627782 to the same values 
previously set
 found 627782 3.9.6-1
Bug #627782 [src:linux] fcntl(F_SETFL, O_APPEND) has no effect on aufs 
filesystem
Marked as found in versions linux/3.9.6-1.
 thanks
Stopping processing here.

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

Page allocation failure with MTU 9000

On Thu, Jun 27, 2013 at 09:11:05PM +0200, Damien Martins wrote:
 cat /etc/debian_version
 7.1
 
 uname -a
 Linux nassounet 3.2.0-4-orion5x #1 Debian 3.2.41-2 armv5tel GNU/Linux
 
 When settings MTU to 9000 (ifconfig eth0 mtu 9000) :
 [4098918.032189] mv643xx_eth_port mv643xx_eth_port.0: eth0: link up,
 1000 Mb/s, full duplex, flow control disabled
 
 When having heavy network usage (300MB file transfer using NFS) :
 
 [4101722.937455] swapper: page allocation failure: order:2, mode:0x20
[...]

This is a common failure case when using most of the system memory and
using stupid drivers or hardware that can't scatter received packets
across individual buffers.  I don't know whether the hardware in this
case is capable of scattering.

Increasing sysctl vm.min_free_kbytes is sometimes an effective
workaround, but it may be that your system just don't have enough
memory to make jumbo packets usable.

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/20130627200637.gp4...@decadent.org.uk

Re: Donation of a Calxeda Highbank node

2013-06-27 Thread David Power

 My main concern is that having a single node as buildd without another
 for development purposes means that we don't have easy means to keep
 testing for example kernel upgrades.


Hey Guys, I stumbled upon this thread while trying to investigate if
debian would work on the calxeda platform. We're one of calxedas partners
and have specific customers who would really love to see debian working on
ours/calxedas platform.

Can I ask how far your efforts in porting have gone? Is there a wheezy
release for highbank that we could test out internally?

I would be more than happy to make some hardware available remotely for
you to use as a second build/test server. We have genuine demand for
debian on our platform. I'd also be happy to get involved in any way I can
to help out.

Thanks!
Dave

[please excuse the junk inserted by our mail server]





DISCLAIMER:
The information contained in this email is confidential and may be legally 
privileged. It is intended solely for the addressee and access by anyone else 
is unauthorised. If you are not the intended recipient, any disclosure, 
copying, distribution or any action taken or omitted to be taken in reliance on 
it, is prohibited and may be unlawful. When addressed to our customers, any 
information contained in this e-mail is subject to our standard terms and 
conditions. The views in this email may not necessarily reflect the views of 
the company. Please note that Boston uses the services of credit insurance 
agencies and cheque guarantee companies, therefore, customer details may be 
divulged as required by such companies. This information will be stored in 
their databases and may be exchanged with other credit reference agencies.


--
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/cdf0a78e.5fbe1%david.po...@boston.co.uk

Re: Donation of a Calxeda Highbank node

2013-06-27 Thread Lennart Sorensen

On Thu, Jun 27, 2013 at 07:27:54PM +, David Power wrote:
 Hey Guys, I stumbled upon this thread while trying to investigate if
 debian would work on the calxeda platform. We're one of calxedas partners
 and have specific customers who would really love to see debian working on
 ours/calxedas platform.
 
 Can I ask how far your efforts in porting have gone? Is there a wheezy
 release for highbank that we could test out internally?

Well I highly doubt that will happen.  Wheezy is released and uses 3.2
kernel which is certainly too old to work with this new hardware.

Would http://packages.debian.org/jessie/linux-image-3.9-1-vexpress by
any chance be a valid kernel image for the highbank?  I see in the git
logs of Linus's tree that there is a v7 multiplatform config that is
supposed to cover the highbank, socfpga, mvebu, and vexpress in one
kernel, so having a vexpress kernel in jessie could be a promising sign
for the next major release.

 I would be more than happy to make some hardware available remotely for
 you to use as a second build/test server. We have genuine demand for
 debian on our platform. I'd also be happy to get involved in any way I can
 to help out.

Well certainly I don't think there is a chance to be an officially
supported piece of hardware until the next major release (in a couple
of years, or whatever the release schedule is like these days).

Now you could of course build a newer kernel, and install everything
else from wheezy, and that should work fine, but it won't officially
be Debian, and updates to the kernel for security and such would not be
Debian's doing.

Other than booting and the kernel, it is just yet another arm system
though, so wheezy should work fine, otehr than the boot/kernel part.

I am of course not in any way official Debian anything, just a long time
user of Debian on many architectures and machine types, but I think I
have a decent understanding of how things work.

-- 
Len Sorensen


-- 
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/20130627211611.gu11...@csclub.uwaterloo.ca

Re: Donation of a Calxeda Highbank node

2013-06-27 Thread Luca Filipozzi

On Thu, Jun 27, 2013 at 07:27:54PM +, David Power wrote:
 On Tue, Apr 30, 2013 at 09:56:51AM +0300, Riku Voipio wrote:
  My main concern is that having a single node as buildd without another
  for development purposes means that we don't have easy means to keep
  testing for example kernel upgrades.
 
 Hey Guys, I stumbled upon this thread while trying to investigate if
 debian would work on the calxeda platform. We're one of calxedas partners
 and have specific customers who would really love to see debian working on
 ours/calxedas platform.
 
 Can I ask how far your efforts in porting have gone? Is there a wheezy
 release for highbank that we could test out internally?
 
 I would be more than happy to make some hardware available remotely for
 you to use as a second build/test server. We have genuine demand for
 debian on our platform. I'd also be happy to get involved in any way I can
 to help out.

Hi Dave,

We are more than happy to receive donations that assist us in properly
addressing the buildd/porter requirements for the ARM architecture.

Generally speaking, our requirements for equipment to be used as buildd/porter
machines are as follows:

* reliability - The stable release manager requires that we operate
  three machines for each port: two buildd machines in different
  locations and one porter machine.  These machines must be reliable.

* out of band management - We require the ability to manage the machines
  independently of their primary network interface: serial console or
  better, remotely-controllable power.

* supportability - We require that the machines be commercialy available
  (within financial constraints) and that they be supportable through a
  warranty or post-warranty support or are otherwise easy to replace.

* stability - We require that the machine's architecture have an
  actively-maintained stable kernel in the archive.

* environment - We require that packages critical for DSA operations be
  available: puppet, samhain, syslog-ng, ferm/pf, etc.

We would prefer to house such equipment in one of the data centres where we
have an existing presence (grnet (Greece), man-da (Germany), ubcece (Canada))
but we are amenable to a discussion regarding having a business host the
equipment on our behalf as long as the above requirements are met.

Please let me know how you'd like to proceed.

And thank you for your offer.  It is *only* through the generous donation of
time, equipment and/or funds from businesses and/or individuals such as
yourself that volunteers are able to make the operating system known as Debian.

Thanks again,

Luca

Debian System Administration Team
Debian Hardware Donations Team

-- 
Luca Filipozzi
http://www.crowdrise.com/SupportDebian


signature.asc
Description: Digital signature

Re: Donation of a Calxeda Highbank node

2013-06-27 Thread Raphael Hertzog

Hello David,

On Thu, 27 Jun 2013, Lennart Sorensen wrote:
 Would http://packages.debian.org/jessie/linux-image-3.9-1-vexpress by
 any chance be a valid kernel image for the highbank?  I see in the git
 logs of Linus's tree that there is a v7 multiplatform config that is
 supposed to cover the highbank, socfpga, mvebu, and vexpress in one
 kernel, so having a vexpress kernel in jessie could be a promising sign
 for the next major release.

Hector Oron sent us a kernel to test on the Hihgbank node we made
available to Debian, but lack of knowledge on everything IPMI related
means that we didn't dare to try it out yet:
http://www.rtp-net.org/misc/linux-image-3.9-1-armmp_3.9-1~experimental.1_armhf.deb

If you could try it out and give some feedback, it would be appreciated
I'm sure.

Cheers,
-- 
Raphaël Hertzog ◈ Debian Developer

Liberate the French translation of the Debian Administrator's Handbook:
→ http://www.ulule.com/liberation-cahier-admin-debian/


-- 
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/20130627213430.ge12...@x230-buxy.home.ouaza.com

Re: Donation of a Calxeda Highbank node

2013-06-27 Thread Luca Filipozzi

On Thu, Jun 27, 2013 at 05:16:11PM -0400, Lennart Sorensen wrote:
 I am of course not in any way official Debian anything, just a long time
 user of Debian on many architectures and machine types, but I think I
 have a decent understanding of how things work.

We have to start somewhere, however.  Having equipment on which to build, is a
good start.  I'll let the release team and the buildd team decide what to
build, when and where.  My goal is meet the supportability / reliability
requirements that DSA has for an architecture.

So, while you've brought up some excellent observations, let's not scare away
the potential donor quite yet :) [/me waves at David]

Luca

Debian System Administration Team
Debian Hardware Donations Team

-- 
Luca Filipozzi
http://www.crowdrise.com/SupportDebian


signature.asc
Description: Digital signature

Re: Donation of a Calxeda Highbank node

2013-06-27 Thread Hector Oron

Hello,

2013/6/27 Luca Filipozzi lfili...@debian.org:
On Thu, Jun 27, 2013 at 07:27:54PM +, David Power wrote:
On Tue, Apr 30, 2013 at 09:56:51AM +0300, Riku Voipio wrote:

My main concern is that having a single node as buildd without another
for development purposes means that we don't have easy means to keep
testing for example kernel upgrades.

Can I ask how far your efforts in porting have gone? Is there a wheezy
release for highbank that we could test out internally?

The armhf userland should run on those boxes, it already does in a
chroot environment. ARM hardware enablement is missing in Debian, for
example, custom IPMI Calxeda tools I think are not yet integrated in
Debian, but Ubuntu have those available. There is also missing
bootloader, and I do not think mainline u-boot/grub supports those
boxes yet. Kernel wise, there is a current effort to migrate as much
ARM platforms we have in Debian to armmp kernel (a.k.a. ARM
multiplatform). Those kernels we have been trying to test on the
donated node, but we are currently blocked on getting access to IPMI
interface in case we need to recover from the disaster. If you can
test armmp kernel and let us know something, that would really be a
step forward.

http://packages.debian.org/unstable/linux-image-3.9-1-armmp

I would be more than happy to make some hardware available remotely for
you to use as a second build/test server. We have genuine demand for
debian on our platform. I'd also be happy to get involved in any way I can
to help out.

I think that is very welcome from ARM porters point of view. Thanks
for the offer.

Hi Dave,

We are more than happy to receive donations that assist us in properly
addressing the buildd/porter requirements for the ARM architecture.

Generally speaking, our requirements for equipment to be used as buildd/porter
machines are as follows:

* reliability - The stable release manager requires that we operate
three machines for each port: two buildd machines in different
locations and one porter machine. These machines must be reliable.

We already got ipa.debian.net, if David can give more nodes to Debian,
then I think the requirement can be fulfilled.

* out of band management - We require the ability to manage the machines
independently of their primary network interface: serial console or
better, remotely-controllable power.

David, could you also allow Debian admins into IPMI interface?

* supportability - We require that the machines be commercialy available
(within financial constraints) and that they be supportable through a
warranty or post-warranty support or are otherwise easy to replace.

Those machines are selling commercially now.

* stability - We require that the machine's architecture have an
actively-maintained stable kernel in the archive.

Currently, there is an effort on going, as I explained above, but it
is not yet finished, just starting:
http://packages.debian.org/unstable/linux-image-3.9-1-armmp

* environment - We require that packages critical for DSA operations be
available: puppet, samhain, syslog-ng, ferm/pf, etc.

The armhf port already contains those.

We would prefer to house such equipment in one of the data centres where we
have an existing presence (grnet (Greece), man-da (Germany), ubcece (Canada))
but we are amenable to a discussion regarding having a business host the
equipment on our behalf as long as the above requirements are met.

Please let me know how you'd like to proceed.

And thank you for your offer. It is *only* through the generous donation of
time, equipment and/or funds from businesses and/or individuals such as
yourself that volunteers are able to make the operating system known as
Debian.

Thanks again,

Luca

Debian System Administration Team
Debian Hardware Donations Team

--
Luca Filipozzi
http://www.crowdrise.com/SupportDebian

Regards,
--
Héctor Orón -.. . -... .. .- -. -.. . ...- . .-.. --- .--. . .-.

Debian ARM porter
Debian ARM buildd admin

--
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/CAODfWeH_YXZpH=vsjgkxteo4t-8nqhrked8r1xbse4nzcat...@mail.gmail.com

Re: Dropping support for the smallest armel machines

2013-06-27 Thread Hector Oron

Hello,

2013/6/27 Ben Hutchings b...@decadent.org.uk:
 On Wed, Jun 26, 2013 at 04:39:15PM +0100, Ben Hutchings wrote:
 On Wed, Jun 26, 2013 at 03:13:48PM +0200, Arnaud Patard wrote:
  Ben Hutchings b...@decadent.org.uk writes:

  btw, iop32x is used on n2100 which are used on buildd/porter boxes. If
  we stop supporting it, I'm not sure how the DSA people will react about
  that.
 [...]

 Currently only 3 out of 10 are N2100s; the remainder are Marvell
 development boards running the mv78xx0 flavour.

DSA plans to decommission N2100 build daemons. Those have not even
been running as build daemons during wheezy release.

As I side note, I'll be sad to see N2100 go, as I own one myself.

Regards,
-- 
 Héctor Orón  -.. . -... .. .- -.   -.. . ...- . .-.. --- .--. . .-.


--
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/caodfwehqb8zbrokkacag-zdkz7n7f9v3wvhwruxcvsttyp5...@mail.gmail.com

Bug#714295: linux-image-3.2.0-4-686-pae: ext4 on top of raid1. Frequent and serious data corruption issues

Le jeudi 27 juin 2013 à 18:31 +0100, Ben Hutchings a écrit :
 On Thu, Jun 27, 2013 at 07:14:57PM +0200, Martin Braure de Calignon wrote:
 [...]
  So you think that this temperature stuff could be related to my ext4
  problems?
 [...]

 Are you overclocking the processor?
First of all, thank you for your support.

Well I was unsure, so I opened the computer, removed the CPU fan.
Processor is a 1.7Ghz, but in the BIOS the CPU clock was 110 where it
should be 100 to be 1.7Ghz.
So yes it was. It's no longer.
Second problem, my CPU fan was controlled by a potentiometer which was
not turned to it maximum. I just removed it and connected the cpu fan
directly to the mainboard. I'm not sure of that, but I'm not sure there
was enough thermal paste between the processor and the fan. So it is
still a future track if the problem reappeared.
Third problem the PC was full of dust. I just cleaned it.
Fourth problem [1], it seems (on purpose in linux source code) that my
processor is not happy with cpufreq governance to ondemand and was
automatically switched to performance.
I modified the default configuration so that it goes in powersave
mode...


In my original email, and before rebooting, I did a dmesg -T... The time
between the CPU related error and the ext4 error is like  17 hours, so
I'm still not sure it's related.

I just rebooted with the new CPU frequencies, and tried everything I
copy a big directory from my (new) ext3 partition to the raid1 ext4
device (which currently now has only 1 device in it ;))
no problem during like 15 minutes...
So I tried something else, because I'm not sure, but I've noticed that
problem occurred more when I'm deleting files, so I run a fdupes on
another big directory of that raid1 ext4 device.
and boum [2]!




[1]: when I do:
$cpufreq-set -g ondemand
  [3759.734304] ondemand governor failed, too long transition
latency of HW, fall back to performance governor

[2]: 
[...] // lines before are just boot of the system, then the manual mount
of the raid devices and the other devices. I ran a fsck.ext4 forced
right before.

[ 1618.164009] EXT4-fs (md0): mounted filesystem with journalled data
mode. Opts: data=journal
[ 3341.908050] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003610
[ 3342.327029] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003610
[ 3342.456047] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003604
[ 3342.607818] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003604
[ 3342.616049] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003597
[ 3342.616049] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003597
[ 3342.624584] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003587
[ 3342.628041] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003587
[ 3342.628055] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003607
[ 3342.628055] EXT4-fs error (device md0): ext4_lookup:1050: inode
#54003553: comm fdupes: deleted inode referenced: 54003607
[ 3480.764050] EXT4-fs error (device md0): ext4_lookup:1050: inode
#55972184: comm fdupes: deleted inode referenced: 55972483
[ 3480.764050] EXT4-fs error (device md0): ext4_lookup:1050: inode
#55972184: comm fdupes: deleted inode referenced: 55972483
[ 3480.764050] EXT4-fs error (device md0): ext4_lookup:1050: inode
#55972184: comm fdupes: deleted inode referenced: 55972492
[ 3480.764050] EXT4-fs error (device md0): ext4_lookup:1050: inode
#55972184: comm fdupes: deleted inode referenced: 55972492


any clue? :/
Few other comments: I have all other FS under ext4 (but the new ext3 i
created this afternoon) and never got problem with them.
My PC originally had only IDE BUS, so I added two PCI controller for
having SATA.
First two disks on the first controller (a big LVM) never got a problem
with ext4
the other two disks on the second controller (different brand) is the
RAID1 device.


-- 
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/1372375714.330.17.camel@phoenix

Bug#713042: linux-image-3.2.0-4-686-pae: USB webcam turns on but fails to work (regression)

2013-06-27 Thread David Jarvie

I thought wrongly that all my packages were up to date after installing Wheezy, 
which was when I reported the bug. I've now updated to 3.2.46-1 and the bug is 
indeed fixed. Sorry for the noise.

-- 
David Jarvie.
KDE developer.
KAlarm author -- http://www.astrojar.org.uk/kalarm


-- 
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/201306252340.04171.softw...@astrojar.org.uk

Bug#714217: Info received (Bug#714217: X display is shifted upwards on GMA500)

2013-06-27 Thread Stéphane Aulery

fixed 714217 linux/3.10~rc7-1~exp1
stop

cf. https://bugs.freedesktop.org/show_bug.cgi?id=66243#c1


-- 
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/20130627234535.ga3...@free.fr

Processed: Fixed 714217

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

 fixed 714217 linux/3.10~rc7-1~exp1
Bug #714217 [src:linux] X display is shifted upwards on GMA500
Marked as fixed in versions linux/3.10~rc7-1~exp1.

End of message, stopping processing here.

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

Processed: Forwarded 714217

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

 forwarded 714217 https://bugs.freedesktop.org/show_bug.cgi?id=66243
Bug #714217 [src:linux] X display is shifted upwards on GMA500
Set Bug forwarded-to-address to 
'https://bugs.freedesktop.org/show_bug.cgi?id=66243'.

End of message, stopping processing here.

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

Bug#714218: linux-image-3.10-rc5-amd64: Compile new intel-pstate driver

2013-06-27 Thread Andreas Kloeckner

Vincent Blut vincent.deb...@free.fr writes:
 close 714218
 thanks

 Le 26/06/2013 23:12, Andreas Kloeckner a écrit :
 Package: src:linux
 Version: 3.10~rc5-1~exp1
 Severity: wishlist
 
 Dear Maintainer,
 
 It'd be great if you could, in a future version of the kernel package,
 compile in the new intel-pstate driver. See:
 
 http://lkml.indiana.edu/hypermail/linux/kernel/1302.0/02669.html
 
 This is supposed to have landed in 3.9 (I believe).

 Hi,

 Please update to 3.10~rc7-1~exp1, you'll find your happiness ;-)

Hey,

thanks for the quick reply! I just updated, but there's no sign of the
new driver:

/lib/modules/3.10-rc7-amd64$ find -name 'intel-*'
./kernel/drivers/char/hw_random/intel-rng.ko
/lib/modules/3.10-rc7-amd64$

Andreas


pgpNH_qpm9IFX.pgp
Description: PGP signature

Bug#714295: linux-image-3.2.0-4-686-pae: ext4 on top of raid1. Frequent and serious data corruption issues

On Fri, 2013-06-28 at 01:28 +0200, Martin Braure de Calignon wrote:
 Le jeudi 27 juin 2013 à 18:31 +0100, Ben Hutchings a écrit :
  On Thu, Jun 27, 2013 at 07:14:57PM +0200, Martin Braure de Calignon wrote:
  [...]
   So you think that this temperature stuff could be related to my ext4
   problems?
  [...]
 
  Are you overclocking the processor?
 First of all, thank you for your support.
 
 Well I was unsure, so I opened the computer, removed the CPU fan.
 Processor is a 1.7Ghz, but in the BIOS the CPU clock was 110 where it
 should be 100 to be 1.7Ghz.
 So yes it was. It's no longer.
 Second problem, my CPU fan was controlled by a potentiometer which was
 not turned to it maximum. I just removed it and connected the cpu fan
 directly to the mainboard. I'm not sure of that, but I'm not sure there
 was enough thermal paste between the processor and the fan. So it is
 still a future track if the problem reappeared.
 Third problem the PC was full of dust. I just cleaned it.
 Fourth problem [1], it seems (on purpose in linux source code) that my
 processor is not happy with cpufreq governance to ondemand and was
 automatically switched to performance.

Right, I guess this is an old Pentium 4 which can't change frequency
very quickly.

[...]
 I just rebooted with the new CPU frequencies, and tried everything I
 copy a big directory from my (new) ext3 partition to the raid1 ext4
 device (which currently now has only 1 device in it ;))
 no problem during like 15 minutes...
 So I tried something else, because I'm not sure, but I've noticed that
 problem occurred more when I'm deleting files, so I run a fdupes on
 another big directory of that raid1 ext4 device.
 and boum [2]!
[...]
 [2]: 
 [...] // lines before are just boot of the system, then the manual mount
 of the raid devices and the other devices. I ran a fsck.ext4 forced
 right before.
 
 [ 1618.164009] EXT4-fs (md0): mounted filesystem with journalled data
 mode. Opts: data=journal
 [ 3341.908050] EXT4-fs error (device md0): ext4_lookup:1050: inode
 #54003553: comm fdupes: deleted inode referenced: 54003610
 [ 3342.327029] EXT4-fs error (device md0): ext4_lookup:1050: inode
 #54003553: comm fdupes: deleted inode referenced: 54003610
 [ 3342.456047] EXT4-fs error (device md0): ext4_lookup:1050: inode
 #54003553: comm fdupes: deleted inode referenced: 54003604
[...]
 any clue? :/

I still suspect a hardware problem, just because ext4 is the default
filesystem for 'wheezy' and no-one else reported this yet.

 Few other comments: I have all other FS under ext4 (but the new ext3 i
 created this afternoon) and never got problem with them.
 My PC originally had only IDE BUS, so I added two PCI controller for
 having SATA.
 First two disks on the first controller (a big LVM) never got a problem
 with ext4
 the other two disks on the second controller (different brand) is the
 RAID1 device.

So maybe the second controller (or its driver) is faulty.  Can you try
using the RAID-1 disks connected to the first controller, with nothing
connected to the second controller?  Or do you need the first two disks
in order to boot?

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


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

Bug#713042: marked as done (linux-image-3.2.0-4-686-pae: USB webcam turns on but fails to work (regression))

Your message dated Fri, 28 Jun 2013 02:34:41 +0100
with message-id 1372383281.23847.36.ca...@deadeye.wl.decadent.org.uk
and subject line Re: Bug#713042: linux-image-3.2.0-4-686-pae: USB webcam turns 
on but fails to work (regression)
has caused the Debian Bug report #713042,
regarding linux-image-3.2.0-4-686-pae: USB webcam turns on but fails to work 
(regression)
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.)


-- 
713042: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=713042
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: src:linux
Version: 3.2.41-2
Severity: normal

The Chicony/Sonix USB webcam using the uvcvideo driver does not work on my
Lenovo 3000 N200 laptop. The webcam is detected during bootup, and turns on
when using applications such as cheese and skype, but there is no image
produced.

The webcam worked correctly under Squeeze, so this is a regression. There is a
report about a similar problem on Ubuntu at
http://askubuntu.com/questions/264193/12-10-webcam-stopped-working-after-update,
which indicates that the problem may have been fixed again in more recent 
kernels.

-- Package-specific info:
** Version:
Linux version 3.2.0-4-686-pae (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-686-pae 
root=UUID=5925aa58-07cb-40d6-b790-4832612bdcd4 ro quiet

** Not tainted

** Kernel log:
[6.387011] Bluetooth: HCI socket layer initialized
[6.387015] Bluetooth: L2CAP socket layer initialized
[6.387222] Bluetooth: SCO socket layer initialized
[6.430038] iwl3945 :04:00.0: Tunable channels: 13 802.11bg, 23 802.11a 
channels
[6.430043] iwl3945 :04:00.0: Detected Intel Wireless WiFi Link 3945ABG
[6.430204] iwl3945 :04:00.0: irq 46 for MSI/MSI-X
[6.430383] Registered led device: phy0-led
[6.477707] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[6.498362] [drm] initialized overlay support
[6.533816] psmouse serio1: synaptics: Touchpad model: 1, fw: 6.3, id: 
0x25c0b1, caps: 0xa04713/0x20/0x0
[6.582426] Bluetooth: Generic Bluetooth USB driver ver 0.6
[6.583401] usbcore: registered new interface driver btusb
[6.620464] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input5
[6.667891] fbcon: inteldrmfb (fb0) is primary device
[6.978225] Console: switching to colour frame buffer device 160x50
[6.984253] fb0: inteldrmfb frame buffer device
[6.984256] drm: registered panic notifier
[7.072177] acpi device:07: registered as cooling_device2
[7.072406] input: Video Bus as 
/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:01/input/input6
[7.072482] ACPI: Video Device [GFX0] (multi-head: yes  rom: no  post: no)
[7.072528] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0
[7.072969] snd_hda_intel :00:1b.0: irq 47 for MSI/MSI-X
[7.073012] snd_hda_intel :00:1b.0: setting latency timer to 64
[7.631308] Linux media interface: v0.10
[7.640755] Linux video capture interface: v2.00
[7.667797] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (04f2:b013)
[7.672857] input: USB 2.0 Camera as 
/devices/pci:00/:00:1a.1/usb3/3-2/3-2:1.0/input/input7
[7.673000] usbcore: registered new interface driver uvcvideo
[7.673003] USB Video Class driver (1.1.1)
[7.694285] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input8
[7.837102] cfg80211: World regulatory domain updated:
[7.837106] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[7.837111] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[7.837116] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[7.837120] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[7.837124] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[7.837128] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[9.417445] Adding 3903788k swap on /dev/sda3.  Priority:-1 extents:1 
across:3903788k 
[9.446389] EXT4-fs (sda5): re-mounted. Opts: (null)
[   10.015599] EXT4-fs (sda5): re-mounted. Opts: errors=remount-ro
[   10.149523] loop: module loaded
[   12.118330] kjournald starting.  Commit interval 5 seconds
[   12.118606] EXT3-fs (sda1): using internal journal
[   12.118615] EXT3-fs (sda1): mounted filesystem with ordered data mode
[   12.161621] kjournald starting.  Commit interval

Processed: tagging 709647, tagging 709647, bug 709647 is forwarded to t...@linutronix.de

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

 tags 709647 - moreinfo
Bug #709647 [linux-source-3.2] linux-source-3.2: USB 1.1 no longer works
Removed tag(s) moreinfo.
 tags 709647 + upstream
Bug #709647 [linux-source-3.2] linux-source-3.2: USB 1.1 no longer works
Added tag(s) upstream.
 forwarded 709647 t...@linutronix.de
Bug #709647 [linux-source-3.2] linux-source-3.2: USB 1.1 no longer works
Set Bug forwarded-to-address to 't...@linutronix.de'.
 thanks
Stopping processing here.

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

Bug#709647: [PATCH] genirq: Fix can_request_irq() for IRQs without an action

Commit 02725e7471b8 ('genirq: Use irq_get/put functions'),
inadvertently changed can_request_irq() to return 0 for IRQs that have
no action.  This causes pcibios_lookup_irq() to select only IRQs that
already have an action with IRQF_SHARED set, or to fail if there are
none.  Change can_request_irq() to return 1 for IRQs that have no
action (if the first two conditions are met).

Reported-by: Bjarni Ingi Gislason bjarn...@rhi.hi.is
References: http://bugs.debian.org/709647
Tested-by: Bjarni Ingi Gislason bjarn...@rhi.hi.is (against 3.2)
Signed-off-by: Ben Hutchings b...@decadent.org.uk
Cc: sta...@vger.kernel.org # 2.6.39+
Cc: 709...@bugs.debian.org
---
 kernel/irq/manage.c |6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/kernel/irq/manage.c b/kernel/irq/manage.c
index fa17855..dc4db32 100644
--- a/kernel/irq/manage.c
+++ b/kernel/irq/manage.c
@@ -555,9 +555,9 @@ int can_request_irq(unsigned int irq, unsigned long 
irqflags)
return 0;
 
if (irq_settings_can_request(desc)) {
-   if (desc-action)
-   if (irqflags  desc-action-flags  IRQF_SHARED)
-   canrequest =1;
+   if (!desc-action ||
+   irqflags  desc-action-flags  IRQF_SHARED)
+   canrequest = 1;
}
irq_put_desc_unlock(desc, flags);
return canrequest;



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

Re: Donation of a Calxeda Highbank node

On Thu, 2013-06-27 at 17:16 -0400, Lennart Sorensen wrote:
 On Thu, Jun 27, 2013 at 07:27:54PM +, David Power wrote:
  Hey Guys, I stumbled upon this thread while trying to investigate if
  debian would work on the calxeda platform. We're one of calxedas partners
  and have specific customers who would really love to see debian working on
  ours/calxedas platform.
  
  Can I ask how far your efforts in porting have gone? Is there a wheezy
  release for highbank that we could test out internally?
 
 Well I highly doubt that will happen.  Wheezy is released and uses 3.2
 kernel which is certainly too old to work with this new hardware.
 
 Would http://packages.debian.org/jessie/linux-image-3.9-1-vexpress by
 any chance be a valid kernel image for the highbank?  I see in the git
 logs of Linus's tree that there is a v7 multiplatform config that is
 supposed to cover the highbank, socfpga, mvebu, and vexpress in one
 kernel, so having a vexpress kernel in jessie could be a promising sign
 for the next major release.
[...]

The 'armmp' flavour is the one with a multiplatform configuration.  All
the other armhf kernel flavours will be dropped once it's ready to
replace them.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


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

Bug#714218: linux-image-3.10-rc5-amd64: Compile new intel-pstate driver

On Thu, 2013-06-27 at 21:13 -0400, Andreas Kloeckner wrote:
 Vincent Blut vincent.deb...@free.fr writes:
  close 714218
  thanks
 
  Le 26/06/2013 23:12, Andreas Kloeckner a écrit :
  Package: src:linux
  Version: 3.10~rc5-1~exp1
  Severity: wishlist
  
  Dear Maintainer,
  
  It'd be great if you could, in a future version of the kernel package,
  compile in the new intel-pstate driver. See:
  
  http://lkml.indiana.edu/hypermail/linux/kernel/1302.0/02669.html
  
  This is supposed to have landed in 3.9 (I believe).
 
  Hi,
 
  Please update to 3.10~rc7-1~exp1, you'll find your happiness ;-)
 
 Hey,
 
 thanks for the quick reply! I just updated, but there's no sign of the
 new driver:
 
 /lib/modules/3.10-rc7-amd64$ find -name 'intel-*'
 ./kernel/drivers/char/hw_random/intel-rng.ko
 /lib/modules/3.10-rc7-amd64$

It's built-in.

Ben.

-- 
Ben Hutchings
Knowledge is power.  France is bacon.


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

Bug#714295: linux-image-3.2.0-4-686-pae: ext4 on top of raid1. Frequent and serious data corruption issues