Bug#628444: Info received (iwlagn - "MAC is in deep sleep", cannot restore wifi operation)

2012-03-08 Thread Venkataraman, Meenakshi 
Hi Shannon and others,

First up, my sincere apologies for not responding earlier. I've been swamped 
with other work, and have had a chance to look at this only now.

I just got caught up with the email thread, and it appears that you're seeing a 
problem with the following configuration most frequently:

1)  Enable power saving in the driver (power_save)

2)  Enabling 11n

3)  Leaving aspm at its default

4)  wd_disable=0 (the default)

Our devices are known to have issues with being in L1 (a PCIe sleep state), and 
so we use L0S by default - this is a lower latency and higher power state.

We've also not been able to reproduce the "MAC in deep sleep" problem at our 
end, so not sure at the moment what is causing it.

However, there was one issue with queue-stuck detection that we found and fixed 
very recently. The patch is available in the wireless-next tree, and will 
likely improve the situation if a stuck queue was the initial cause of your 
problem.

You can get the source here: 
http://git.kernel.org/pub/scm/linux/kernel/git/linville/wireless-next.git

And the patch I'm talking about is this: 
git.kernel.org/?p=linux/kernel/git/linville/wireless-next.git;a=commit;h=342bbf3fee2fa9a18147e74b2e3c4229a4564912

My suggestion is to load the module with power_save=0, wd_disable=1. Enabling 
11n should not be a problem, but if it is, then please let us know. You should 
not need to use the wd_disable=1 in the upcoming versions of the kernel, but 
for now, I'd suggest using it. Since your problem seems to be reducing 
significantly by using pcie_aspm=off, I would appreciate it much if you could 
tell us what the behaviour is with all other parameters being the same 
(power_save=0, wd_disable=1), and just toggling the state of this variable.

We'll try to reproduce the suspend/hibernate/resume issue in-house and let you 
know if we were able to reproduce the problem at our end. If not, we'd like you 
to try out a newer WiFi card; as the 5100 is a fairly old device, and will 
likely not get any firmware updates (if it is some weird firmware/driver combo 
that produced the PCIe error).

Thanks!
Meenakshi Venkataraman

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

2012-03-08 Thread Harold R. Grove 
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] ehci_hcd :00:13.2: restoring config space at offset 0x1 (was 
0x2b0, writing 0x2b00013)
[  844.284491] ehci_hcd :00:13.2: PME# disabled
[  844.284521] ehci_hcd :00:13.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17
[  845.262546] scsi 3:0:0:0: Direct-AccessMass  Storage Device
PQ: 0 ANSI: 0
[  845.267900] sd 3:0:0:0: [sdb] 488397166 512-byte logical blocks: (250 GB/232 
GiB)
[  845.269777] sd 3:0:0:0: [sdb] Write Protect is off
[  845.269794] sd 3:0:0:0: [sdb] Mode Sense: 03 00 00 00
[  845.270449] sd 3:0:0:0: [sdb] No Caching mode page present
[  845.270463] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[  845.274136] sd 3:0:0:0: [sdb] No Caching mode page present
[  845.274154] sd 3:0:0:0: [sdb] Assuming drive cache: write through
[  845.331930]  sdb: sdb1
[  845.335055] sd 3:0:0:0: [sdb] No Caching mode page present
[  845.335075] sd 3:0:0:

Processed: bug 649735 is forwarded to https://bugzilla.kernel.org/show_bug.cgi?id=42783 http://lkml.org/lkml/2012/2/21/443

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

> forwarded 649735 https://bugzilla.kernel.org/show_bug.cgi?id=42783 
> http://lkml.org/lkml/2012/2/21/443
Bug #649735 [linux-2.6] linux-image-3.0.0-2-amd64: kernel oops on removing an 
USB floppy drive
Bug #655625 [linux-2.6] kernel NULL pointer dereference after repartitioning 
USB disk
Changed Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=42783 
http://lkml.org/lkml/2012/2/21/443' from 
'https://bugzilla.kernel.org/show_bug.cgi\?id\=42783 
http://lkml.org/lkml/2012/2/21/443'
Changed Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi?id=42783 
http://lkml.org/lkml/2012/2/21/443' from 
'https://bugzilla.kernel.org/show_bug.cgi\?id\=42783 
http://lkml.org/lkml/2012/2/21/443'
> thanks
Stopping processing here.

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

Processed: bug 649735 is forwarded to https://bugzilla.kernel.org/show_bug.cgi\?id\=42783 http://lkml.org/lkml/2012/2/21/443

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

> forwarded 649735 https://bugzilla.kernel.org/show_bug.cgi\?id\=42783 
> http://lkml.org/lkml/2012/2/21/443
Bug #649735 [linux-2.6] linux-image-3.0.0-2-amd64: kernel oops on removing an 
USB floppy drive
Bug #655625 [linux-2.6] kernel NULL pointer dereference after repartitioning 
USB disk
Changed Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi\?id\=42783 
http://lkml.org/lkml/2012/2/21/443' from 'http://lkml.org/lkml/2012/2/21/443'
Changed Bug forwarded-to-address to 
'https://bugzilla.kernel.org/show_bug.cgi\?id\=42783 
http://lkml.org/lkml/2012/2/21/443' from 'http://lkml.org/lkml/2012/2/21/443'
> thanks
Stopping processing here.

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

Bug#607227: [RV516] screen flickers

2012-03-08 Thread Jonathan Nieder 
Marcos Marado wrote:

> I finally got some time to test this, so I fired up the machine and...
> the problem was gone. The silly thing that happened was that when
> trying the new-compiled kernel, I chose the wrong one at boot time, so
> I was sure I was testing the new kernel but I wasn't at all... Seems
> that, after all, using patch 1 and 2 but not 3 was a solution after
> all.

Oh, excellent!  Thanks, Marcos.  That's a comfort.



-- 
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/20120308222758.GA10398@burratino

Bug#607227: [RV516] screen flickers

2012-03-08 Thread Marcos Marado 
Hi there,

I'm very very sorry, I've been wasting your time.
I finally got some time to test this, so I fired up the machine and...
the problem was gone. The silly thing that happened was that when
trying the new-compiled kernel, I chose the wrong one at boot time, so
I was sure I was testing the new kernel but I wasn't at all... Seems
that, after all, using patch 1 and 2 but not 3 was a solution after
all.

Sorry once again for the mistake, and if you want me to test anything
else just ask...

Best regards,
-- 
Marcos Marado



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

Processed: reassign 663119 to kmod

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

> reassign 663119 kmod
Bug #663119 [initramfs-tools] FATAL: Module multipath not found.
Bug reassigned from package 'initramfs-tools' to 'kmod'.
Bug No longer marked as found in versions initramfs-tools/0.101.
> thanks
Stopping processing here.

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

[bts-link] source package linux-2.6

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

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

# remote status report for #649412 (http://bugs.debian.org/649412)
# Bug title: "Destination Host Unreachable" after some time with
#  * http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2330
#  * remote status changed: ASSIGNED -> RESOLVED
#  * remote resolution changed: (?) -> FIXED
#  * closed upstream
tags 649412 + fixed-upstream
usertags 649412 - status-ASSIGNED
usertags 649412 + status-RESOLVED resolution-FIXED

thanks


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

Bug#663119: FATAL: Module multipath not found.

2012-03-08 Thread Jamie Heilman 
Package: initramfs-tools
Version: 0.101

Got a new error message--

Setting up initramfs-tools (0.101) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for dictionaries-common ...
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-3.3.0-rc6
FATAL: Module multipath not found.
Press return to continue.

The only real differences from stock on this system are
in /etc/initramfs-tools/initramfs.conf:
  MODULES=list
  BUSYBOX=n

and in /etc/initramfs-tools/modules I've added:
md_mod
raid1
dm_mod
xfs

as this system is xfs on top of lvm on top of partitioned md raid1.
My kernel is (obviously) custom, I don't need or build either md or dm
multipath drivers.  There's no reason not having them should be a
"fatal" error (the initrd.img is still built, I haven't tested it yet
or dug into the changes since 0.100 that introduced this message).

-- 
Jamie Heilman http://audible.transient.net/~jamie/
"Paranoia is a disease unto itself, and may I add, the person standing
 next to you may not be who they appear to be, so take precaution."
-Sathington Willoughby



-- 
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/20120308164750.gb22...@cucamonga.audible.transient.net

Processed: [bts-link] source package linux-2.6

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

> #
> # bts-link upstream status pull for source package linux-2.6
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to bts-link-upstr...@lists.alioth.debian.org (was 
bts-link-de...@lists.alioth.debian.org).
> # remote status report for #649412 (http://bugs.debian.org/649412)
> # Bug title: "Destination Host Unreachable" after some time with
> #  * http://bugzilla.intellinuxwireless.org/show_bug.cgi?id=2330
> #  * remote status changed: ASSIGNED -> RESOLVED
> #  * remote resolution changed: (?) -> FIXED
> #  * closed upstream
> tags 649412 + fixed-upstream
Bug #649412 [linux-2.6] "Destination Host Unreachable" after some time with
Added tag(s) fixed-upstream.
> usertags 649412 - status-ASSIGNED
Bug#649412: "Destination Host Unreachable" after some time with
Usertags were: status-ASSIGNED.
Usertags are now: .
> usertags 649412 + status-RESOLVED resolution-FIXED
Bug#649412: "Destination Host Unreachable" after some time with
There were no usertags set.
Usertags are now: status-RESOLVED resolution-FIXED.
> thanks
Stopping processing here.

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

Bug#623377: init: don't start in runlevel S *and* 2345

2012-03-08 Thread Michael Biebl 
On 21.04.2011 06:07, Ben Hutchings wrote:
> On Tue, 2011-04-19 at 20:40 +0200, Michael Biebl wrote:

> [...]
> 
> All filesystems listed in /etc/fstab should be mounted even in single-
> user mode.  If any of those are mounted over NFS, rpc.statd and portmap
> or rpcbind must be started.
> 
> Additional daemons may be required for multi-user access; those are
> installed in /usr.  And so it may be necessary to run nfs-common a
> second time, when those daemons are available.
> 

..

> 
> I suppose we should split the init script, assuming that people stuck in
> the 90s continue to insist that separate /usr must be supported.

Reading all this, it sounds like splitting the init script into
different parts is the cleanest solution and the way to go.

The question now is, which bits need to go where. Can someone with more
insight into the internals of nfs-common/rpcbind/... give a more
detailed overview?

Michael





-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?



signature.asc
Description: OpenPGP digital signature

Re: Linux kernel hardening - link restrictions

2012-03-08 Thread Ben Hutchings 
On Thu, 2012-03-08 at 12:19 +0100, Vincent Lefevre wrote:
> Hi,
> 
> On 2012-03-02 05:11:58 +, Ben Hutchings wrote:
> > I'm therefore intending to warn about this with the following NEWS
> > entry in the linux-image metapackages:
> > 
> > Index: debian/linux-image.NEWS
> > ===
> > --- debian/linux-image.NEWS (revision 18757)
> > +++ debian/linux-image.NEWS (working copy)
> > @@ -1,3 +1,18 @@
> > +linux-latest (44) unstable; urgency=low
> > +
> > +  * The new kernel version includes security restrictions on links, which
> > +are enabled by default.  These are specified in
> > +Documentation/sysctl/fs.txt in the linux-doc-3.2 and linux-source-3.2
> > +packages.
> > +  
> > +These restrictions may cause some legitimate programs to fail.
> > +In particular, if the 'at' package is installed, you should either:
> > +- Upgrade it to at least version 3.1.13-1 (or a backport of that)
> > +or:
> > +- Set sysctl fs.protected_hardlinks=0 (see /etc/sysctl.conf)
> > +
> > + -- Ben Hutchings   Fri, 02 Mar 2012 04:58:24 +
> > +
> >  linux-latest-2.6 (26) unstable; urgency=low
> >  
> >* The old IDE (PATA) drivers are no longer developed.  Most PATA
> > --- END ---
> > 
> > (Why in the metapackages, you ask?  Because apt-listchanges shows NEWS
> > from upgraded packages, not new packages.)
> 
> I didn't see anything! (I noticed the change thanks to a diff on
> "sysctl -a" output, otherwise I wouldn't be aware of it.)
[...]

Since 'at' is going to be updated in stable, I added a versioned
'Breaks' instead.

Ben.

-- 
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.


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

Bug#663111: linux-image-3.2.0-2-amd64: Inproper Display Port output signal form integrated intel graphics with kernel 3.2. and 3.3.

2012-03-08 Thread Hynek Vychodil 
Package: linux-2.6
Version: 3.2.9-1
Severity: important

Dear Maintainer,
I have tried test newer linux kernel version 3.2. (both 3.2.0-1 and 3.2.0-2)
but with both of them Display Port output of mine notebook Lenovo T410s
doesn't generate signal. With linux-image-3.1.0-1-amd64 it works well.

I set video output using KDE system settings to external monitor and monitor
keeps dark and behaves like there is not proper signal. When I reboot using
linux-image-3.1.0-1-amd64 the exactly same action works well.

External monitor is detected properly and when I try use smaller resolution
(around 1280x800) I can manage make image appear after several attempt .
When I set monitor native resolution (1920x1080) then sometimes image appears
but is unstable and disappear (black screen) for up to 2 second randomly.
With older kernel there is not such weird behaviour.

Then I tried also inux-image-3.3.0-rc6-amd64 which shows image as in 3.1.
but is unstable in same way as 3.2.

-- 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=/vmlinuz-3.2.0-2-amd64 root=/dev/mapper/vg1-root ro quiet 
i915.i915_enable_rc6=1 pcie_aspm=force i915.i915_enable_fbc=1 
i915.lvds_downclock=1

** Not tainted

** Kernel log:
[   18.695931] thinkpad_acpi: http://ibm-acpi.sf.net/
[   18.695934] thinkpad_acpi: ThinkPad BIOS 6UET42WW (1.22 ), EC 6UHT30WW-1.11
[   18.695939] thinkpad_acpi: Lenovo ThinkPad T410s, model 2912RC7
[   18.696827] thinkpad_acpi: detected a 8-level brightness capable ThinkPad
[   18.696977] thinkpad_acpi: radio switch found; radios are enabled
[   18.699629] Registered led device: tpacpi::thinklight
[   18.699713] Registered led device: tpacpi::power
[   18.699755] Registered led device: tpacpi::standby
[   18.699785] Registered led device: tpacpi::thinkvantage
[   18.701747] thinkpad_acpi: Standard ACPI backlight interface available, not 
loading native one
[   18.701929] thinkpad_acpi: Console audio control enabled, mode: monitor 
(read only)
[   18.703019] input: ThinkPad Extra Buttons as 
/devices/platform/thinkpad_acpi/input/input9
[   18.790768] input: HDA Digital PCBeep as 
/devices/pci:00/:00:1b.0/input/input10
[   18.797124] psmouse serio1: synaptics: Touchpad model: 1, fw: 7.2, id: 
0x1c0b1, caps: 0xd047b3/0xb4/0xa
[   18.797138] psmouse serio1: synaptics: serio: Synaptics pass-through port at 
isa0060/serio1/input0
[   18.847979] input: SynPS/2 Synaptics TouchPad as 
/devices/platform/i8042/serio1/input/input11
[   18.954579] rtl8192se :03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 
17
[   18.954636] rtl8192se :03:00.0: setting latency timer to 64
[   18.977484] rtl8192se: rtl8192ce: FW Power Save off (module option)
[   18.977571] rtl8192se: Driver for Realtek RTL8192SE/RTL8191SE
[   18.977572] Loading firmware rtlwifi/rtl8192sefw.bin
[   18.992441] HDMI status: Codec=3 Pin=4 Presence_Detect=0 ELD_Valid=0
[   18.992644] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0
[   18.992950] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0
[   18.993120] input: HDA Intel HDMI/DP,pcm=8 as 
/devices/pci:00/:00:1b.0/sound/card0/input12
[   18.993272] input: HDA Intel HDMI/DP,pcm=7 as 
/devices/pci:00/:00:1b.0/sound/card0/input13
[   18.993435] input: HDA Intel HDMI/DP,pcm=3 as 
/devices/pci:00/:00:1b.0/sound/card0/input14
[   19.265539] Linux media interface: v0.10
[   19.299289] ieee80211 phy0: Selected rate control algorithm 'rtl_rc'
[   19.329903] Linux video capture interface: v2.00
[   19.355541] uvcvideo: Found UVC 1.00 device Integrated Camera (17ef:480d)
[   19.357197] input: Integrated Camera as 
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.6/1-1.6:1.0/input/input15
[   19.357260] usbcore: registered new interface driver uvcvideo
[   19.357262] USB Video Class driver (1.1.1)
[   20.036241] cfg80211: World regulatory domain updated:
[   20.036247] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   20.036253] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   20.036258] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   20.036263] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   20.036267] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   20.036272] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   20.036669] cfg80211: Calling CRDA for country: EC
[   20.042316] cfg80211: Regulatory domain changed to country: EC
[   20.042321] cfg80211: (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   20.042327] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 
2000 mBm)
[   20.042332] cfg80211: (517 KHz - 525 KHz @ 2 KHz), (300 mBi, 
1700 mBm)
[   20.042337] cfg80211:

Re: Linux kernel hardening - link restrictions

2012-03-08 Thread Vincent Lefevre 
Hi,

On 2012-03-02 05:11:58 +, Ben Hutchings wrote:
> I'm therefore intending to warn about this with the following NEWS
> entry in the linux-image metapackages:
> 
> Index: debian/linux-image.NEWS
> ===
> --- debian/linux-image.NEWS   (revision 18757)
> +++ debian/linux-image.NEWS   (working copy)
> @@ -1,3 +1,18 @@
> +linux-latest (44) unstable; urgency=low
> +
> +  * The new kernel version includes security restrictions on links, which
> +are enabled by default.  These are specified in
> +Documentation/sysctl/fs.txt in the linux-doc-3.2 and linux-source-3.2
> +packages.
> +  
> +These restrictions may cause some legitimate programs to fail.
> +In particular, if the 'at' package is installed, you should either:
> +- Upgrade it to at least version 3.1.13-1 (or a backport of that)
> +or:
> +- Set sysctl fs.protected_hardlinks=0 (see /etc/sysctl.conf)
> +
> + -- Ben Hutchings   Fri, 02 Mar 2012 04:58:24 +
> +
>  linux-latest-2.6 (26) unstable; urgency=low
>  
>* The old IDE (PATA) drivers are no longer developed.  Most PATA
> --- END ---
> 
> (Why in the metapackages, you ask?  Because apt-listchanges shows NEWS
> from upgraded packages, not new packages.)

I didn't see anything! (I noticed the change thanks to a diff on
"sysctl -a" output, otherwise I wouldn't be aware of it.)

> Does anyone have a better idea how to do this?  Know about other
> packages that are affected?

There seems to be something wrong. The upgrade was done via
linux-image-amd64 3.2+44 (from source linux-latest 44), and
/usr/share/doc/linux-image-amd64/NEWS.Debian.gz just contains:

linux-latest-2.6 (26) unstable; urgency=low

[...]

 -- Ben Hutchings   Tue, 04 May 2010 02:10:04 +0100

-- 
Vincent Lefèvre  - Web: 
100% accessible validated (X)HTML - Blog: 
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)


-- 
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/20120308111928.gc3...@xvii.vinc17.org

Bug#663041: please enable ib_srpt

2012-03-08 Thread Adam Heath 

On 03/08/2012 01:57 AM, Jonathan Nieder wrote:

reassign 663041 src:linux-2.6 3.3~rc6-1~experimental.1
found 663041 linux-2.6/3.2.9-1
tags 663041 + upstream patch
quit

Adam Heath wrote:

[commit a42d985bd5b234da8b61347a78dc3057bf7bb94d, applied during
  the 3.3 merge window]

That enables SRP target support for Infiniband.


For 3.3 release candidates in experimental, I believe you are
requesting that CONFIG_INFINIBAND_SRPT=m be added to the kernel
configuration in topconfig.  For wheezy, a backport of the driver
would presumably be useful.

Thanks for a pleasant report,
Jonathan


Additionally, upgrading from 3.2.0 to 3.3.0-rc6 increased my ipoib 
bandwidth from 130MB/s to 283MB/s.  I'm not certain which patchset does 
that.  But that should really be a separate bug.




--
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/4f586725.8050...@brainfood.com

Processed: Re: please enable ib_srpt

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

> reassign 663041 src:linux-2.6 3.3~rc6-1~experimental.1
Bug #663041 [linux-image-3.3.0-rc6-amd64] please enable ib_srpt
Bug reassigned from package 'linux-image-3.3.0-rc6-amd64' to 'src:linux-2.6'.
Bug No longer marked as found in versions linux-2.6/3.3~rc6-1~experimental.1.
Bug #663041 [src:linux-2.6] please enable ib_srpt
Bug Marked as found in versions linux-2.6/3.3~rc6-1~experimental.1.
> found 663041 linux-2.6/3.2.9-1
Bug #663041 [src:linux-2.6] please enable ib_srpt
Bug Marked as found in versions linux-2.6/3.2.9-1.
> tags 663041 + upstream patch
Bug #663041 [src:linux-2.6] please enable ib_srpt
Added tag(s) upstream and patch.
> quit
Stopping processing here.

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

Bug#663041: please enable ib_srpt

2012-03-08 Thread Jonathan Nieder 
reassign 663041 src:linux-2.6 3.3~rc6-1~experimental.1
found 663041 linux-2.6/3.2.9-1
tags 663041 + upstream patch
quit

Adam Heath wrote:

[commit a42d985bd5b234da8b61347a78dc3057bf7bb94d, applied during
 the 3.3 merge window]
> That enables SRP target support for Infiniband.

For 3.3 release candidates in experimental, I believe you are
requesting that CONFIG_INFINIBAND_SRPT=m be added to the kernel
configuration in topconfig.  For wheezy, a backport of the driver
would presumably be useful.

Thanks for a pleasant report,
Jonathan



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