Bug#627957: False alarm

2011-10-13 Thread Yves-Alexis Perez
Ok so I'm not sure if the fix is the same for everyone, but in my case the issue wasn't in the Debian install but in the laptop itself, and more precisely either in the embedded controler or in some low level firmware (e1000e or AMT I'd say). A longer explanation for people interested is at http:/

Bug#627957: Same issue here

2011-10-13 Thread Yves-Alexis Perez
I have the same kind of issue on a Thinkpad T61. I don't really know how/when it started, this T61 is not my main laptop anymore but this morning I had to do stuff on it and noticed network connection wasn't working while the network cable was plugged correctly. I modprobe-r'ed e1000e, then modpro

Bug#645071: linux-image-2.6.32-5-686-bigmem: init crashes during runlevel switch

2011-10-13 Thread Дмитрий Матросов
I suppose, that result of previous attempt is not very useful, because something is missed in the output (after "of" word). So, i rewrite your patch a little: [..] + printk(KERN_DEBUG "%s: refcount of %p (%s, num=%d, mag=%d, flags=%d) is still %d\n", + __

Bug#645071: linux-image-2.6.32-5-686-bigmem: init crashes during runlevel switch

2011-10-13 Thread Дмитрий Матросов
I try to compile with printk() instead of printk_ratelimited() in your patch, and it's succeeded. Then i install it with # dpkg -i ./linux-image-2.6.32-5-686-bigmem_2.6.32-38a~test_i386.deb # dpkg --configure --force-depends-version linux-image-2.6.32-5-686-bigmem and then try to reproduce thi

Bug#645071: linux-image-2.6.32-5-686-bigmem: init crashes during runlevel switch

2011-10-13 Thread Дмитрий Матросов
2011/10/13 Ben Hutchings : > On Wed, 2011-10-12 at 14:05 +0300, Matrosov Dmitriy wrote: >> Package: linux-2.6 >> Version: 2.6.32-38 >> Severity: normal >> Tags: squeeze >> >> Steps to reproduce: >> 1. Reboot computer. >> 2. Boot into runlevel 2. >> 3. Switch to console and go to single-user runleve

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing

2011-10-13 Thread martin f krafft
also sprach Jort Koopmans [2011.10.13.1148 +0200]: > First of all, thanks for helping me out. (I did not CC the bug report at the time…) > > - if you are criticising initramfs/mdadm, then it helps to > > reproduce the output you are seeing, ideally after set -x. > > True, since this machi

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing

2011-10-13 Thread Will Set
Thursday, October 13, 2011 10:07 AM Jort Koopmans wrote: >>>Instead of patching this here and there with band aids, I suggest >>>that everyone with an interest instead invests time in testing >>>mdadm/experimental, which provides event-based assembly, >> >>I was wondering what documentation the

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing

2011-10-13 Thread Jort Koopmans
Hi Will, >>Instead of patching this here and there with band aids, I suggest >>that everyone with an interest instead invests time in testing >>mdadm/experimental, which provides event-based assembly, > >I was wondering what documentation the reporter was following. > >I haven't seen RAID on USB

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing

2011-10-13 Thread Jort Koopmans
Hi Martin, First of all, thanks for helping me out. On Thu, 2011-10-13 at 11:10 +0200, martin f krafft wrote: also sprach Jort Koopmans [2011.10.12.2143 +0200]: > > Common guys...can somebody look at my bugreport? > > We have. Let me offer some suggestions: > > - two days in FLOSS time is n

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing

2011-10-13 Thread Will Set
Thursday, October 13, 2011 9:06 AM martin f krafft wrote: >also sprach Jort Koopmans [2011.10.12.2143 +0200]: >> In the mean while I've checked another solution; moving the call >> to the local-top scripts till after the ROOTDELAY loop (within the >> local file). > >init-top/udev also uses it.

Bug#644876: initramfs-tools: Boot failure from software RAID1 + LVM2 by timing

2011-10-13 Thread martin f krafft
also sprach Jort Koopmans [2011.10.12.2143 +0200]: > In the mean while I've checked another solution; moving the call > to the local-top scripts till after the ROOTDELAY loop (within the > local file). init-top/udev also uses it. > This works in my config. But this would delay finding the ROOT d