Bug#697501: AR9285: enabling or disabling Wi-Fi freezes the system

2013-01-07 Thread programmer11...@programist.ru
06.01.2013, 16:21, Jonathan Nieder jrnie...@gmail.com:

  Hi,

  Thanks for reporting.  By enable/disable wi-fi, do you mean using a
  hardware switch?  Can you reproduce this problem without the quiet
  option on the kernel command line (for example when booting in
  recovery mode), and if so, does it show any messages on the screen
  when it hangs?  A photograph would be fine.

  Hope that helps,
  Jonathan

Yes, I am using a hardware switch. Hard to reproduce the problem, because it 
occurs randomly.
When system start, Wi-Fi enabled simultaneously with display manager. If system 
hangs, I see the black screen.


--
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/4094991357546...@web8h.yandex.ru



Bug#697501: AR9285: enabling or disabling Wi-Fi freezes the system

2013-01-07 Thread Jonathan Nieder
programmer11...@programist.ru wrote:

 Yes, I am using a hardware switch. Hard to reproduce the problem,
 because it occurs randomly.
 When system start, Wi-Fi enabled simultaneously with display
 manager. If system hangs, I see the black screen.

Thanks.  Please try to reproduce it in recovery mode --- in that
mode there is no display manager.  If you can reproduce the hang
with a 3.7.x or newer kernel from experimental, that would be best
since then we can get help from upstream.

You can also get some information about wifi events by running iw
event -t with output redirected to a file and examining that file
after rebooting.

I assume that in the hanged state the magic sysrq key doesn't work?

Regards,
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/20130107082841.GG27909@elie.Belkin



Bug#697501: AR9285: enabling or disabling Wi-Fi freezes the system

2013-01-07 Thread programmer11...@programist.ru
07.01.2013, 12:28, Jonathan Nieder jrnie...@gmail.com:

  Thanks.  Please try to reproduce it in recovery mode --- in that
  mode there is no display manager.  If you can reproduce the hang
  with a 3.7.x or newer kernel from experimental, that would be best
  since then we can get help from upstream.

  You can also get some information about wifi events by running iw
  event -t with output redirected to a file and examining that file
  after rebooting.

  I assume that in the hanged state the magic sysrq key doesn't work?

  Regards,
  Jonathan

Hang also present in linux-image-3.7-trunk-686-pae.
sysrq do not work if hangs. Work only Fn+ - keys for increase/decrease 
brightness, that is strange.
iw event -t shows nothing - output file not created (it has a null size).
If I press in wicd-gtk Switch off Wi-Fi and immediately press Disconnect 
All system hangs (on kernel linux-image-3.7-trunk-686-pae).

syslog
Jan  7 17:04:15 gateway-lmde dhclient: Internet Systems Consortium DHCP Client 
4.2.4
Jan  7 17:04:15 gateway-lmde dhclient: Copyright 2004-2012 Internet Systems 
Consortium.
Jan  7 17:04:15 gateway-lmde dhclient: All rights reserved.
Jan  7 17:04:15 gateway-lmde dhclient: For info, please visit 
https://www.isc.org/software/dhcp/
Jan  7 17:04:15 gateway-lmde dhclient: 
Jan  7 17:04:15 gateway-lmde dhclient: Listening on LPF/wlan0/00:26:5e:0f:9f:d3
Jan  7 17:04:15 gateway-lmde dhclient: Sending on   LPF/wlan0/00:26:5e:0f:9f:d3
Jan  7 17:04:15 gateway-lmde dhclient: Sending on   Socket/fallback
Jan  7 17:04:15 gateway-lmde dhclient: DHCPRELEASE on wlan0 to 192.168.3.128 
port 67
Jan  7 17:04:15 gateway-lmde kernel: [  160.101816] IPv6: ADDRCONF(NETDEV_UP): 
wlan0: link is not ready
Jan  7 17:04:15 gateway-lmde dhclient: Internet Systems Consortium DHCP Client 
4.2.4
Jan  7 17:04:15 gateway-lmde dhclient: Copyright 2004-2012 Internet Systems 
Consortium.
Jan  7 17:04:15 gateway-lmde dhclient: All rights reserved.
Jan  7 17:04:15 gateway-lmde dhclient: For info, please visit 
https://www.isc.org/software/dhcp/
Jan  7 17:04:15 gateway-lmde dhclient: 
Jan  7 17:04:15 gateway-lmde dhclient: Listening on LPF/eth1/00:23:8b:ef:35:34
Jan  7 17:04:15 gateway-lmde dhclient: Sending on   LPF/eth1/00:23:8b:ef:35:34
Jan  7 17:04:15 gateway-lmde dhclient: Sending on   Socket/fallback
Jan  7 17:04:16 gateway-lmde dhclient: DHCPRELEASE on eth1 to 192.168.3.128 
port 67
Jan  7 17:04:16 gateway-lmde dhclient: receive_packet failed on eth1: Network 
is down
Jan  7 17:04:16 gateway-lmde kernel: [  160.729232] r8169 :03:00.0 eth1: 
link down
Jan  7 17:04:16 gateway-lmde kernel: [  160.729489] r8169 :03:00.0 eth1: 
link down
Jan  7 17:04:16 gateway-lmde kernel: [  160.729579] IPv6: ADDRCONF(NETDEV_UP): 
eth1: link is not ready
Jan  7 17:04:16 gateway-lmde dhclient: Internet Systems Consortium DHCP Client 
4.2.4
Jan  7 17:04:16 gateway-lmde dhclient: Copyright 2004-2012 Internet Systems 
Consortium.
Jan  7 17:04:16 gateway-lmde dhclient: All rights reserved.
Jan  7 17:04:16 gateway-lmde dhclient: For info, please visit 
https://www.isc.org/software/dhcp/
Jan  7 17:04:16 gateway-lmde dhclient: 
Jan  7 17:04:16 gateway-lmde dhclient: Listening on LPF/eth1/00:23:8b:ef:35:34
Jan  7 17:04:16 gateway-lmde dhclient: Sending on   LPF/eth1/00:23:8b:ef:35:34
Jan  7 17:04:16 gateway-lmde dhclient: Sending on   Socket/fallback
Jan  7 17:04:16 gateway-lmde dhclient: DHCPRELEASE on eth1 to 192.168.3.128 
port 67
Jan  7 17:04:16 gateway-lmde dhclient: send_packet: Network is unreachable
Jan  7 17:04:16 gateway-lmde dhclient: send_packet: please consult README file 
regarding broadcast address.
Jan  7 17:04:16 gateway-lmde dhclient: dhclient.c:2270: Failed to send 300 byte 
long packet over fallback interface.
Jan  7 17:04:16 gateway-lmde dhclient: receive_packet failed on eth1: Network 
is down
Jan  7 17:04:16 gateway-lmde kernel: [  161.213211] r8169 :03:00.0 eth1: 
link down
Jan  7 17:04:16 gateway-lmde kernel: [  161.213588] IPv6: ADDRCONF(NETDEV_UP): 
eth1: link is not ready
Jan  7 17:04:18 gateway-lmde kernel: [  162.844001] r8169 :03:00.0 eth1: 
link up
Jan  7 17:04:18 gateway-lmde kernel: [  162.844260] IPv6: 
ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
Jan  7 17:04:19 gateway-lmde dhclient: Internet Systems Consortium DHCP Client 
4.2.4
Jan  7 17:04:19 gateway-lmde dhclient: Copyright 2004Jan  7 17:05:44 
gateway-lmde rsyslogd: [origin software=rsyslogd swVersion=7.2.4 
x-pid=2586 x-info=http://www.rsyslog.com;] start
Jan  7 17:05:44 gateway-lmde kernel: [0.00] Initializing cgroup subsys 
cpuset
Jan  7 17:05:44 gateway-lmde kernel: [0.00] Initializing cgroup subsys 
cpu

And other notes made after reboot.

Sorry for my bad English, if that..


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



Bug#681089: firmware-linux-nonfree: Broadcom NetXtreme BCM5722 dropped packets

2013-01-07 Thread Berni Elbourn

On 06/01/13 02:44, Ben Hutchings wrote:


If I understand your original report correctly, the tg3 driver in Debian
kernel version 2.6.32-45 fails periodically and the driver in version
3.2.20-1~bpo60+1 does not.  So we need to look for a fix to the driver
that was made between those versions.

Let me know if my understanding is correct.

Ben.



Sorry for not updating. The current versions in squeeze seems to be fine now 
running for days without incident.

elbournb@red:~$ cat /proc/version
Linux version 2.6.32-5-amd64 (Debian 2.6.32-46) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 
23 10:07:46 UTC 2012


elbournb@red:~$ sudo ethtool -i eth0
driver: tg3
version: 3.116
firmware-version: 5722-v3.07, ASFIPMI v6.02
bus-info: :11:00.0

I can easily move this system to the backport kernel for a few days. Would that be a valid test to close the issue for 
Wheezy too?


Huge thanks,

Berni

--
Confidence is what you have before you understand a problem - Woody Allen


--
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/50eaae7a.5090...@gmail.com



Bug#624343: data corruption: md changes max_sector setting of running md devices

2013-01-07 Thread bug556610

Hello,
thanks for responding.

NeilBrown:
 The upstream bug tracker is
mailto:linux-r...@vger.kernel.org

Well ok, though a regular mailinglist makes it rather hard to get an overview 
for non-devs, 
and reporting involves receiving unrelated messages.

 This really needs to be fixed by cleaning up the bio path so that big bios
 are split by the device that needs the split, not be the fs sending the
 bio.

Where ist that tracked? 

 Maybe the best interim fix is to reject the added device is its limits are
 too low.

Good Idea to avoid the data corruption. MD could save the
max_sectors default limit for arrays. If the array is modified and the new 
limit gets smaller, postpone the sync until the next assembe/restart.

And of course print a message if postponing, that explains when --force would 
be save.
What ever that would be: no block device abstraction layer (device mapper, lvm, 
luks,...) 
between an unmounted? ext, fat?, ...? filesystem and md?

 


-- 
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/1844285783.588464.1357562045190.javamail.ngm...@webmail10.arcor-online.net



Processed: reassign 697035 to src:linux

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

 reassign 697035 src:linux 3.2.35-2
Bug #697035 [installation-reports] installer: kb and mouse don't work on a 
decTop (NSC geode processor)
Bug reassigned from package 'installation-reports' to 'src:linux'.
Ignoring request to alter found versions of bug #697035 to the same values 
previously set
Ignoring request to alter fixed versions of bug #697035 to the same values 
previously set
Bug #697035 [src:linux] installer: kb and mouse don't work on a decTop (NSC 
geode processor)
Marked as found in versions linux/3.2.35-2.
 thanks
Stopping processing here.

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



Bug#681089: firmware-linux-nonfree: Broadcom NetXtreme BCM5722 dropped packets

2013-01-07 Thread Ben Hutchings
Control: tag -1 unreproducible

On Mon, 2013-01-07 at 11:16 +, Berni Elbourn wrote:
 On 06/01/13 02:44, Ben Hutchings wrote:
 
  If I understand your original report correctly, the tg3 driver in Debian
  kernel version 2.6.32-45 fails periodically and the driver in version
  3.2.20-1~bpo60+1 does not.  So we need to look for a fix to the driver
  that was made between those versions.
 
  Let me know if my understanding is correct.
 
  Ben.
 
 
 Sorry for not updating. The current versions in squeeze seems to be fine now 
 running for days without incident.
 
 elbournb@red:~$ cat /proc/version
 Linux version 2.6.32-5-amd64 (Debian 2.6.32-46) (da...@debian.org) (gcc 
 version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Sun Sep 
 23 10:07:46 UTC 2012

There have been no changes to tg3 between 2.6.32-45 and -46, so there
cannot have been any bug fix.

 elbournb@red:~$ sudo ethtool -i eth0
 driver: tg3
 version: 3.116
 firmware-version: 5722-v3.07, ASFIPMI v6.02
 bus-info: :11:00.0
 
 I can easily move this system to the backport kernel for a few days. Would 
 that be a valid test to close the issue for 
 Wheezy too?

If you can't reproduce the bug on squeeze now, then I don't think you
can tell whether it has been fixed in any other version.  Perhaps there
was a change in some external condition that triggered it.

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.


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


Processed: Re: firmware-linux-nonfree: Broadcom NetXtreme BCM5722 dropped packets

2013-01-07 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 unreproducible
Bug #681089 [firmware-linux-nonfree] firmware-linux-nonfree: Broadcom NetXtreme 
BCM5722 dropped packets
Added tag(s) unreproducible.

-- 
681089: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=681089
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.b681089.135756859430354.transcr...@bugs.debian.org



Bug#697606: linux-image-3.2.0-4-powerpc: Suspend on iBook G3 (A1007) no longer works

2013-01-07 Thread Ted To

Package: src:linux
Version: 3.2.35-2
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?
upgraded kernel linux-image-3.2.0-4 from prior version of 3.2.0-4
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
suspend no longer works
   * What outcome did you expect instead?
suspend would continue to work

*** End of the template - remove these lines ***



-- Package-specific info:
** Version:
Linux version 3.2.0-4-powerpc (debian-kernel@lists.debian.org) (gcc 
version 4.6.3 (Debian 4.6.3-8) ) #1 Debian 3.2.35-2


** Command line:
root=UUID=362cffcd-65ce-4dba-b9ae-00fa2847ef6a ro radeon.modeset=0

** Not tainted

** Kernel log:
[   12.464617] airport: Physical address 8003
[   12.958781] usb 2-1: reset full-speed USB device number 2 using 
ohci_hcd
[   13.669456] airport 0.0003:radio: Hardware identity 
0005:0001:0001:0002
[   13.677439] airport 0.0003:radio: Station identity  
001f:0001:0008:0046
[   13.685122] airport 0.0003:radio: Firmware determined as 
Lucent/Agere 8.70
[   13.721713] ieee80211 phy1: Selected rate control algorithm 
'minstrel_ht'

[   13.724648] Registered led device: rt73usb-phy1::radio
[   13.724818] Registered led device: rt73usb-phy1::assoc
[   13.724986] Registered led device: rt73usb-phy1::quality
[   13.727889] usbcore: registered new interface driver rt73usb
[   13.838225] airport 0.0003:radio: firmware: agent loaded 
agere_sta_fw.bin into memory
[   13.931290] airport 0.0003:radio: Hardware identity 
0005:0001:0001:0002
[   13.939376] airport 0.0003:radio: Station identity  
001f:0002:0009:0030
[   13.947252] airport 0.0003:radio: Firmware determined as 
Lucent/Agere 9.48

[   13.955115] airport 0.0003:radio: Ad-hoc demo mode supported
[   13.962923] airport 0.0003:radio: IEEE standard IBSS ad-hoc mode 
supported

[   13.970745] airport 0.0003:radio: WEP supported, 104-bit key
[   13.978482] airport 0.0003:radio: WPA-PSK supported
[   16.051350] Adding 741204k swap on /dev/sda4.  Priority:-1 extents:1 
across:741204k

[   16.099207] EXT4-fs (sda3): re-mounted. Opts: (null)
[   16.711972] EXT4-fs (sda3): re-mounted. Opts: errors=remount-ro
[   17.412409] loop: module loaded
[   18.314991] i2c i2c-0: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.322788] i2c i2c-0: Please use another way to instantiate your 
i2c_client
[   18.330336] i2c i2c-1: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.337932] i2c i2c-1: Please use another way to instantiate your 
i2c_client
[   18.345564] i2c i2c-2: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.353253] i2c i2c-2: Please use another way to instantiate your 
i2c_client
[   18.360961] i2c i2c-3: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.368599] i2c i2c-3: Please use another way to instantiate your 
i2c_client
[   18.376146] i2c i2c-4: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.383742] i2c i2c-4: Please use another way to instantiate your 
i2c_client
[   18.391160] i2c i2c-5: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.398419] i2c i2c-5: Please use another way to instantiate your 
i2c_client
[   18.405689] i2c i2c-6: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.413001] i2c i2c-6: Please use another way to instantiate your 
i2c_client
[   18.528561] i2c i2c-7: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.536332] i2c i2c-7: Please use another way to instantiate your 
i2c_client
[   18.543983] i2c i2c-8: PMac Keywest Audio: attach_adapter method is 
deprecated
[   18.551785] i2c i2c-8: Please use another way to instantiate your 
i2c_client
[   18.620588] input: PowerMac Beep as 
/devices/pci0001:10/0001:10:17.0/input/input4
[   21.273996] EXT4-fs (sda5): mounted filesystem with ordered data 
mode. Opts: (null)
[   21.895503] input: Macintosh mouse button emulation as 
/devices/virtual/input/input5

[   27.303548] lp: driver loaded but no devices found
[   29.260855] ondemand governor failed, too long transition latency of 
HW, fallback to performance governor

[   31.765589] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   31.951285] eth1: New link status: Connected (0001)
[   31.959010] rt73usb 2-1:1.0: firmware: agent loaded rt73.bin into 
memory

[   32.472706] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[   32.474791] ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready
[   32.498305] ADDRCONF(NETDEV_UP): eth1: link is not ready
[   32.595082] sungem_phy: PHY ID: 4061e4, addr: 0
[   32.595445] gem 0002:20:0f.0: eth0: Found BCM5221 PHY
[   32.598451] ADDRCONF(NETDEV_UP): eth0: link is not ready
[   35.471545] radeonfb :00:10.0: Invalid ROM contents
[   35.471869] radeonfb :00:10.0: Invalid ROM contents
[   35.601156] [drm] Initialized drm 1.1.0 20060810
[   35.831062] [drm] 

Bug#697606: linux-image-3.2.0-4-powerpc: Suspend on iBook G3 (A1007) no longer works

2013-01-07 Thread Ben Hutchings
Control: tag -1 moreinfo

On Mon, 2013-01-07 at 09:50 -0500, Ted To wrote:
 Package: src:linux
 Version: 3.2.35-2
 Severity: important
 
 Dear Maintainer,
 *** Please consider answering these questions, where appropriate ***
 
 * What led up to the situation?
 upgraded kernel linux-image-3.2.0-4 from prior version of 3.2.0-4
 * What exactly did you do (or not do) that was effective (or
   ineffective)?
 * What was the outcome of this action?
 suspend no longer works
 * What outcome did you expect instead?
 suspend would continue to work

How does it not work?  Does the computer hang, wake up immediately, or
reboot when woken?

If it wakes up immediately, please do this:

1. Send the kernel log covering a failed suspend (from the dmesg
command)
2. Mount debugfs ('mount -t debugfs debugfs /sys/kernel/debug')
3. Send a copy of /sys/kernel/debug/suspend_stats

Ben.

-- 
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.


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


Processed: Re: Bug#697606: linux-image-3.2.0-4-powerpc: Suspend on iBook G3 (A1007) no longer works

2013-01-07 Thread Debian Bug Tracking System
Processing control commands:

 tag -1 moreinfo
Bug #697606 [src:linux] linux-image-3.2.0-4-powerpc: Suspend on iBook G3 
(A1007) no longer works
Added tag(s) moreinfo.

-- 
697606: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697606
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.b697606.135757246526955.transcr...@bugs.debian.org



Bug#697319: [PATCH 1/2] Remove '2.6.' from initramfs wildcard in bug script (Closes: #697319)

2013-01-07 Thread Ben Hutchings
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
 debian/script |2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/debian/script b/debian/script
index 5069ccb..e83f10e 100755
--- a/debian/script
+++ b/debian/script
@@ -3,7 +3,7 @@
 exec 3
 
 echo -- initramfs sizes
-ls -lh /boot/initrd.img-2.6.*
+ls -lh /boot/initrd.img-*
 
 echo -- /proc/cmdline
 cat /proc/cmdline




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


[PATCH 2/2] Remove more references to linux-2.6 in manual page and comments

2013-01-07 Thread Ben Hutchings
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
 initramfs-tools.8 |4 ++--
 mkinitramfs   |2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/initramfs-tools.8 b/initramfs-tools.8
index bc6a030..375e5c1 100644
--- a/initramfs-tools.8
+++ b/initramfs-tools.8
@@ -245,10 +245,10 @@ mkinitramfs sets several variables for the hook scripts 
environment.
 
 .TP
 \fB\fI MODULESDIR
-corresponds to the linux-2.6 modules dir.
+corresponds to the linux modules dir.
 .TP
 \fB\fI version
-is the $(uname \-r) linux-2.6 version against mkinitramfs is run.
+is the $(uname \-r) linux version against mkinitramfs is run.
 .TP
 \fB\fI CONFDIR
 is the path of the used initramfs-tools configurations.
diff --git a/mkinitramfs b/mkinitramfs
index 0196d9a..d9a54e2 100755
--- a/mkinitramfs
+++ b/mkinitramfs
@@ -236,7 +236,7 @@ esac
 # Resolve hidden dependencies
 hidden_dep_add_modules
 
-# First file executed by linux-2.6
+# First file executed by linux
 cp -p /usr/share/initramfs-tools/init ${DESTDIR}/init
 
 # add existant boot scripts



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


Bug#657690: General protection fault in XFS code

2013-01-07 Thread Will Aoki
found 657690 linux-2.6/2.6.32-46
thanks

After months of quiet, this problem has reared its head again. This time
the system is still responsive. The system configuration is the same as
mentioned previously, except that the flash drive is no longer attached.

[7617112.478337] general protection fault:  [#1] SMP
[7617112.478369] last sysfs file: /sys/devices/virtual/block/md0/md/mismatch_cnt
[7617112.478402] CPU 0
[7617112.478423] Modules linked in: rpcsec_gss_krb5 nfsd nfs lockd fscache 
nfs_acl a
[7617112.478722] Pid: 47, comm: kswapd0 Not tainted 2.6.32-5-amd64 #1
[7617112.478760] RIP: 0010:[a01c0449]  [a01c0449] 
xfs_count_page
[7617112.478836] RSP: 0018:8801254ef968  EFLAGS: 00010207
[7617112.478872] RAX: 880100c0 RBX: eaff0008 RCX: 
8801254ef9c4
[7617112.478929] RDX: 8801254ef9c8 RSI: 8801254ef9cc RDI: 
eaff0008
[7617112.478989] RBP: 00d0 R08: 27a78c762204feef R09: 
365c4a93b1e9e885
[7617112.479048] R10: 880127c20080 R11: a01c19fb R12: 
880126540d90
[7617112.479108] R13: 880126540eb0 R14: dead00100101 R15: 
8801254efe10
[7617112.479168] FS:  () GS:88000520() 
knlGS:000
[7617112.479230] CS:  0010 DS: 0018 ES: 0018 CR0: 8005003b
[7617112.479267] CR2: 016235e0 CR3: a9828000 CR4: 
06f0
[7617112.479324] DR0:  DR1:  DR2: 

[7617112.479383] DR3:  DR6: 0ff0 DR7: 
0400
[7617112.479440] Process kswapd0 (pid: 47, threadinfo 8801254ee000, task 
880
[7617112.479502] Stack:
[7617112.479528]  a01c1a4b   
000
[7617112.479569] 0  0001  

[7617112.479633] 0   eaff0008 
000100ff
[7617112.479717] Call Trace:
[7617112.479753]  [a01c1a4b] ? xfs_vm_releasepage+0x50/0xa5 [xfs]
[7617112.479796]  [810be75d] ? shrink_page_list+0x48d/0x623
[7617112.479836]  [810114ce] ? common_interrupt+0xe/0x13
[7617112.479873]  [810bd710] ? isolate_pages_global+0xa1/0x20f
[7617112.479911]  [810bf028] ? shrink_list+0x45c/0x767
[7617112.479948]  [81064f67] ? bit_waitqueue+0x10/0xa0
[7617112.479987]  [811315ca] ? proc_delete_inode+0x0/0x40
[7617112.480024]  [810bb255] ? determine_dirtyable_memory+0xd/0x1d
[7617112.480063]  [8103fc3e] ? update_curr+0xa6/0x147
[7617112.480100]  [810bf5b3] ? shrink_zone+0x280/0x342
[7617112.480137]  [810bffd8] ? kswapd+0x4b9/0x686
[7617112.480171]  [810bd66f] ? isolate_pages_global+0x0/0x20f
[7617112.480209]  [81065046] ? autoremove_wake_function+0x0/0x2e
[7617112.480249]  [8103aa06] ? __wake_up_common+0x44/0x72
[7617112.480286]  [810bfb1f] ? kswapd+0x0/0x686
[7617112.480320]  [81064d79] ? kthread+0x79/0x81
[7617112.480356]  [81011baa] ? child_rip+0xa/0x20
[7617112.480391]  [81064d00] ? kthread+0x0/0x81
[7617112.480423]  [81011ba0] ? child_rip+0x0/0x20
[7617112.480457] Code: 49 89 1f eb ef 90 c7 01 00 00 00 00 c7 02 00 00 00 00 c7 
06 0
[7617112.480607] RIP  [a01c0449] xfs_count_page_state+0x25/0x66 [xfs]
[7617112.480654]  RSP 8801254ef968
[7617112.480857] ---[ end trace 56748dedc4909bd1 ]---


-- 
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/20130107161827.gb5...@umnh.utah.edu



Processed: General protection fault in XFS code

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

 found 657690 linux-2.6/2.6.32-46
Bug #657690 [src:linux-2.6] General protection fault in xfs_vm_releasepage
Marked as found in versions linux-2.6/2.6.32-46.
 thanks
Stopping processing here.

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



Bug#697606: linux-image-3.2.0-4-powerpc: Suspend on iBook G3 (A1007) no longer works

2013-01-07 Thread Ted To

On 01/07/2013 10:27 am, Ben Hutchings wrote:

Control: tag -1 moreinfo

On Mon, 2013-01-07 at 09:50 -0500, Ted To wrote:

Package: src:linux
Version: 3.2.35-2
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

* What led up to the situation?
upgraded kernel linux-image-3.2.0-4 from prior version of 3.2.0-4
* What exactly did you do (or not do) that was effective (or
  ineffective)?
* What was the outcome of this action?
suspend no longer works
* What outcome did you expect instead?
suspend would continue to work


How does it not work?  Does the computer hang, wake up immediately, 
or

reboot when woken?


The computer suspends when the lid is shut (this is independent of 
software) but when I open the lid, it hangs.  The USB wireless adapter 
wakes up but nothing can be done but a hard shutdown.


Ted


--
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/306bb67584ad9e93988da22406af6...@theo.to



Bug#697619: USB keyboard no longer works at initramfs passphrase prompt

2013-01-07 Thread Josh Triplett
Package: src:linux
Version: 3.7.1-1~experimental.1
Severity: grave

The 3.7 kernel in experimental no longer accepts input from a USB
keyboard at the initramfs passphrase prompt for an encrypted root.  This
works fine with the 3.6 kernel currently in latest unstable, which I
booted to make this report.

Reporting this as grave because it breaks a common configuration
supported by the installer (the vast majority of desktop systems have
USB keyboards, and the installer offers encrypted root filesystems).

- Josh Triplett

-- Package-specific info:
** Model information
sys_vendor: LENOVO
product_name: 42915J0
product_version: ThinkPad X220
chassis_vendor: LENOVO
chassis_version: Not Available
bios_vendor: LENOVO
bios_version: 8DET47WW (1.17 )
board_vendor: LENOVO
board_name: 42915J0
board_version: Not Available

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation 2nd Generation Core Processor 
Family DRAM Controller [8086:0104] (rev 09)
Subsystem: Lenovo Device [17aa:21da]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort+ SERR- PERR- INTx-
Latency: 0
Capabilities: access denied

00:02.0 VGA compatible controller [0300]: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 
00 [VGA controller])
Subsystem: Lenovo Device [17aa:21da]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 42
Region 0: Memory at f000 (64-bit, non-prefetchable) [size=4M]
Region 2: Memory at e000 (64-bit, prefetchable) [size=256M]
Region 4: I/O ports at 5000 [size=64]
Expansion ROM at unassigned [disabled]
Capabilities: access denied
Kernel driver in use: i915

00:16.0 Communication controller [0780]: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 [8086:1c3a] (rev 04)
Subsystem: Lenovo Device [17aa:21da]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx+
Latency: 0
Interrupt: pin A routed to IRQ 11
Region 0: Memory at f2525000 (64-bit, non-prefetchable) [size=16]
Capabilities: access denied

00:19.0 Ethernet controller [0200]: Intel Corporation 82579LM Gigabit Network 
Connection [8086:1502] (rev 04)
Subsystem: Lenovo Device [17aa:21ce]
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 40
Region 0: Memory at f250 (32-bit, non-prefetchable) [size=128K]
Region 1: Memory at f252b000 (32-bit, non-prefetchable) [size=4K]
Region 2: I/O ports at 5080 [size=32]
Capabilities: access denied
Kernel driver in use: e1000e

00:1a.0 USB controller [0c03]: Intel Corporation 6 Series/C200 Series Chipset 
Family USB Enhanced Host Controller #2 [8086:1c2d] (rev 04) (prog-if 20 [EHCI])
Subsystem: Lenovo Device [17aa:21da]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- 
TAbort- MAbort- SERR- PERR- INTx-
Latency: 0
Interrupt: pin A routed to IRQ 16
Region 0: Memory at f252a000 (32-bit, non-prefetchable) [size=1K]
Capabilities: access denied
Kernel driver in use: ehci_hcd

00:1b.0 Audio device [0403]: Intel Corporation 6 Series/C200 Series Chipset 
Family High Definition Audio Controller [8086:1c20] (rev 04)
Subsystem: Lenovo Device [17aa:21da]
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- PERR- INTx-
Latency: 0, Cache Line Size: 64 bytes
Interrupt: pin A routed to IRQ 44
Region 0: Memory at f252 (64-bit, non-prefetchable) [size=16K]
Capabilities: access denied
Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 6 Series/C200 Series Chipset 
Family PCI Express Root Port 1 [8086:1c10] (rev b4) (prog-if 00 [Normal decode])
Control: I/O- Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- 
MAbort- SERR- 

Bug#687442: Successful test with ASUS Eee PC 701 4G (Intel 915GMS) (was: Bug#687442: linux-image-3.2.0-3-686-pae: Add Intel Ivy Bridge support)

2013-01-07 Thread Paul Menzel
Am Samstag, den 05.01.2013, 17:25 +0100 schrieb Julien Cristau:
 On Fri, Jan  4, 2013 at 17:13:35 +0100, Julien Cristau wrote:
 
  http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-686-pae_3.2.35-3~jcristau.1_i386.deb
  sha1sum 17980ee5bafc40bb4e7bf42576ce40ac81c75833

I successfully used that one under an Eee PC 701 4G with an Intel 915
GMS chipset.

$ lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation Mobile 
915GM/GMS/910GML Express Graphics Controller (rev 04)

  
  http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.35-3~jcristau.1_amd64.deb
  sha1sum f6711fe6d0d924aab82ec82fe1a86102a69a8c32

 Added
 http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-486_3.2.35-3~jcristau.1_i386.deb
 sha1sum 76f67adbed522f8e42216f8595c8b5d1699af9ec


Thanks,

Paul


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


Bug#686284: closed by Ben Hutchings b...@decadent.org.uk (Bug#686284: fixed in linux 3.2.35-1)

2013-01-07 Thread Stefan Monnier
 We believe that the bug you reported is fixed in the latest version of
 Linux, which is due to be installed in the Debian FTP archive.

Indeed, I confirm that this problem is fixed in the linux-image-3.2.0-4
package that's now in `testing'.  Thank you very much,


Stefan


-- 
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/jwv38ycoqbt.fsf-monnier+in...@gnu.org



Bug#697635: linux-image-3.7-trunk-amd64: System doesn't reboot nor power off with 3.7.1-1~experimental.2

2013-01-07 Thread Nicolas Le Cam
Package: src:linux
Version: 3.7.1-1~experimental.2
Severity: important

Dear Maintainer,

Since upgrading to 3.7 my Dell D630 doesn't power off or reboot after the end 
of the runlevel.

The system shows [info] Will now halt. or [info] Will now restart. then 
seems to enter an infinite loop
(system starts to heat and fan is spinning fast)

Downgrading to 3.6 fixes the problem.

-- Package-specific info:
** Version:
Linux version 3.7-trunk-amd64 (debian-kernel@lists.debian.org) (gcc version 
4.7.2 (Debian 4.7.2-4) ) #1 SMP Debian 3.7.1-1~experimental.2

** Command line:
BOOT_IMAGE=/boot/vmlinuz-3.7-trunk-amd64 
root=UUID=6c9b8e4c-e994-4158-b6de-616a055fc929 ro quiet nowatchdog

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

** Kernel log:
[   16.450051] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[   16.450053] [drm] No driver support for vblank timestamp query.
[   16.501901] usb 3-2: New USB device found, idVendor=413c, idProduct=8140
[   16.501905] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   16.596879] Bluetooth: Core ver 2.16
[   16.596921] NET: Registered protocol family 31
[   16.596923] Bluetooth: HCI device and connection manager initialized
[   16.597137] Bluetooth: HCI socket layer initialized
[   16.597141] Bluetooth: L2CAP socket layer initialized
[   16.597149] Bluetooth: SCO socket layer initialized
[   16.616066] usb 7-1: new full-speed USB device number 2 using uhci_hcd
[   16.628778] usbcore: registered new interface driver btusb
[   16.769997] usb 7-1: New USB device found, idVendor=0b97, idProduct=7761
[   16.770003] usb 7-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   16.772056] hub 7-1:1.0: USB hub found
[   16.773993] hub 7-1:1.0: 4 ports detected
[   16.813128] ieee80211 phy0: Selected rate control algorithm 'iwl-3945-rs'
[   16.837432] cfg80211: World regulatory domain updated:
[   16.837437] cfg80211:   (start_freq - end_freq @ bandwidth), 
(max_antenna_gain, max_eirp)
[   16.837440] cfg80211:   (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   16.837443] cfg80211:   (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   16.837446] cfg80211:   (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 
2000 mBm)
[   16.837448] cfg80211:   (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   16.837451] cfg80211:   (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 
2000 mBm)
[   17.054004] usb 7-1.2: new full-speed USB device number 3 using uhci_hcd
[   17.175006] usb 7-1.2: New USB device found, idVendor=0b97, idProduct=7772
[   17.175010] usb 7-1.2: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[   17.175014] usb 7-1.2: Product: O2Micro CCID SC Reader
[   17.175017] usb 7-1.2: Manufacturer: O2
[   17.760229] nouveau  [ DRM] 3 available performance level(s)
[   17.760237] nouveau  [ DRM] 0: core 169MHz shader 338MHz memory 100MHz 
voltage 1150mV fanspeed 100%
[   17.760242] nouveau  [ DRM] 1: core 275MHz shader 550MHz memory 301MHz 
voltage 1150mV fanspeed 100%
[   17.760247] nouveau  [ DRM] 2: core 400MHz shader 800MHz memory 594MHz 
voltage 1150mV fanspeed 100%
[   17.760251] nouveau  [ DRM] c: core 275MHz shader 550MHz memory 302MHz
[   17.787654] nouveau  [ DRM] MM: using CRYPT for buffer copies
[   17.851634] composite sync not supported
[   17.942042] nouveau  [ DRM] allocated 1280x800 fb: 0x6, bo 
880071e0f800
[   17.942144] fbcon: nouveaufb (fb0) is primary device
[   17.983231] Console: switching to colour frame buffer device 160x50
[   17.985569] fb0: nouveaufb frame buffer device
[   17.985572] drm: registered panic notifier
[   17.985588] [drm] Initialized nouveau 1.1.0 20120801 for :01:00.0 on 
minor 0
[   18.104370] pci_pm_runtime_suspend(): azx_runtime_suspend+0x0/0x37 
[snd_hda_intel] returns -11
[   18.314050] ehci_hcd :00:1a.7: setting latency timer to 64
[   18.414141] ehci_hcd :00:1d.7: setting latency timer to 64
[   18.762409] nvidia: module license 'NVIDIA' taints kernel.
[   18.762418] Disabling lock debugging due to kernel taint
[   18.794734] NVRM: The NVIDIA probe routine was not called for 1 device(s).
[   18.794740] NVRM: This can occur when a driver such as nouveau, rivafb,
[   18.794740] NVRM: nvidiafb, or rivatv was loaded and obtained ownership of
[   18.794740] NVRM: the NVIDIA device(s).
[   18.794744] NVRM: Try unloading the conflicting kernel module (and/or
[   18.794744] NVRM: reconfigure your kernel without the conflicting
[   18.794744] NVRM: driver(s)), then try loading the NVIDIA kernel module
[   18.794744] NVRM: again.
[   18.794747] NVRM: No NVIDIA graphics adapter probed!
[   19.583965] Adding 3212284k swap on /dev/sda5.  Priority:-1 extents:1 
across:3212284k 
[   19.623203] EXT4-fs (sda1): re-mounted. Opts: (null)
[   19.891702] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[   20.089604] loop: module loaded
[   21.732613] RPC: 

Bug#687442: [Backport] Use DRM/KMS subsystem from Linux 3.4 in wheezy

2013-01-07 Thread Vincent Blut
Le samedi 05 janvier 2013 à 17:25 +0100, Julien Cristau a écrit :
 On Fri, Jan  4, 2013 at 17:13:35 +0100, Julien Cristau wrote:
 
  http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-686-pae_3.2.35-3~jcristau.1_i386.deb
  sha1sum 17980ee5bafc40bb4e7bf42576ce40ac81c75833
  
  http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-amd64_3.2.35-3~jcristau.1_amd64.deb
  sha1sum f6711fe6d0d924aab82ec82fe1a86102a69a8c32

Hi Julien et al.

I tested with an Asus UX31A (Ivybridge Mobile GT2, eDP1 display), using
2D and 3D drivers from Wheezy (respectively versions 2.19.0-6 and
8.0.5-3).

On the DE side, I used GNOME Shell and Cinnamon (both need 3D
acceleration).

On the kernel side, I used:

i915.i915_enable_rc6={0, 1, 3} → no issue (don't know if it worth to
test RC6pp)

i915.semaphores=1 → ditto

In order to stress the GPU, I played some video bits in 1080p mostly
using VAAPI, played video games (native and emulated), and the usual
glxgear to see if all went well, and that's a *success*, the kernel is
pretty stable (contrary to the raw 3.2 series which causes some
freezes on this system, but that's another story I need to
investigate ;-)).

Voilà, to me this kernel is in really good shape, so thank you Julien
for backporting this stuff!

TODO:
- Testing VGA and HDMI outputs
- Testing my old GPUs to prevent regressions (Radeon X800XL and Nvidia
7600GS)
- Testing SNA (?)
- Advertising about this kernel (I found it haphazardly by diving in the
BTS)

  
 Added
 http://people.debian.org/~jcristau/linux-image-3.2.0-4.drm-486_3.2.35-3~jcristau.1_i386.deb
 sha1sum 76f67adbed522f8e42216f8595c8b5d1699af9ec
 
 Cheers,
 Julien

Regards,
Vincent


PS: By the way if Greg KH tags a new longterm kernel, will there be a
chance to see the DRM subsystem backported in Wheezy or that's
definitely too invasive and we'll stay with 3.4 (I don't have any issue
with that, I'm just curious).


--
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/1357599309.23683.51.camel@lamella



Bug#624343: data corruption: md changes max_sector setting of running md devices

2013-01-07 Thread NeilBrown
On Mon, 7 Jan 2013 13:34:05 +0100 (CET) bug556...@arcor.de wrote:

 
 Hello,
 thanks for responding.
 
 NeilBrown:
  The upstream bug tracker is
 mailto:linux-r...@vger.kernel.org
 
 Well ok, though a regular mailinglist makes it rather hard to get an overview 
 for non-devs, 
 and reporting involves receiving unrelated messages.

Reporting only requires that you send an email. You don't have to be
subscribed to post - that would be a ridiculous requirement. :-)


 
  This really needs to be fixed by cleaning up the bio path so that big bios
  are split by the device that needs the split, not be the fs sending the
  bio.
 
 Where ist that tracked? 

No sure exactly what you mean.  However Kent Overstreet has been doing some
work that could lead towards this:

https://lkml.org/lkml/2012/10/15/398

NeilBrown


 
  Maybe the best interim fix is to reject the added device is its limits are
  too low.
 
 Good Idea to avoid the data corruption. MD could save the
 max_sectors default limit for arrays. If the array is modified and the new 
 limit gets smaller, postpone the sync until the next assembe/restart.
 
 And of course print a message if postponing, that explains when --force would 
 be save.
 What ever that would be: no block device abstraction layer (device mapper, 
 lvm, luks,...) 
 between an unmounted? ext, fat?, ...? filesystem and md?
 
  



signature.asc
Description: PGP signature


Processed: tagging 697229

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

 tags 697229 + pending
Bug #697229 [src:linux] Disabling KMS makes X unstable
Added tag(s) pending.
 thanks
Stopping processing here.

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



Bug#697635: [3.6.9 - 3.7.1 regression] Dell D630: System doesn't reboot nor power off

2013-01-07 Thread Jonathan Nieder
Hi Nicolas,

Nicolas Le Cam wrote:

 Since upgrading to 3.7 my Dell D630 doesn't power off or reboot
 after the end of the runlevel.

Please attach full dmesg output from booting a good and a bad
kernel.

Thanks and hope that helps,
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/20130108063241.GB3131@elie.Belkin



Re: Adding armhf vexpress udebs

2013-01-07 Thread Aurelien Jarno
On Wed, Jan 02, 2013 at 08:56:45PM +0100, Cyril Brulebois wrote:
 Cyril Brulebois k...@debian.org (24/11/2012):
  From a d-i point of view, this is more than welcome. I haven't
  reviewed the patch itself yet, but you can commit it right now,
  as d-i wheezy beta 4 has just been released. Just remember to
  keep us posted if some issues are detected in the upcoming days,
  so that we don't release d-i wheezy rc1 with a buggy vexpress
  support. ;-)
 
 Aurélien, ping?

Sorry about doing that late and also for the late answer. The changes
have been committed to the linux SVN on December 31st.

-- 
Aurelien Jarno  GPG: 1024D/F1BCDB73
aurel...@aurel32.net http://www.aurel32.net


-- 
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/20130107232858.gb4...@ohm.aurel32.net



Re: Adding armhf vexpress udebs

2013-01-07 Thread Cyril Brulebois
Hello,

Aurelien Jarno aurel...@aurel32.net (08/01/2013):
 On Wed, Jan 02, 2013 at 08:56:45PM +0100, Cyril Brulebois wrote:
  Cyril Brulebois k...@debian.org (24/11/2012):
   From a d-i point of view, this is more than welcome. I haven't
   reviewed the patch itself yet, but you can commit it right now,
   as d-i wheezy beta 4 has just been released. Just remember to
   keep us posted if some issues are detected in the upcoming days,
   so that we don't release d-i wheezy rc1 with a buggy vexpress
   support. ;-)
  
  Aurélien, ping?
 
 Sorry about doing that late and also for the late answer. The changes
 have been committed to the linux SVN on December 31st.

no worries, we're not entirely ready yet anyway; thanks for the heads-up!

Mraw,
KiBi.


signature.asc
Description: Digital signature