Jonathan Nieder wrote:
> Thanks for reporting, and sorry for the long silence.
That's understandable.
>
> Do you still have access to this hardware? If so, would you still be
> interested in pursuing this bug? ("No" is an ok answer, but please do
> let us know so we can plan accordingly.)
T
Eric Dumazet wrote:
> Which driver handles this Traverse Solos card ?
solos_pci, which also requires the atm module.
(I'm just trying to help here; I'm not affected by the bug.)
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
maximilian attems wrote:
> any update on newer 3.0 linux images from testing?
The problem hasn't occurred yet with the 3.0.0-1 kernel. Even with laptop-mode
not loaded, it still sometimes occurred under 2.6.39.
If my poweroff operations continue to succeed under 3.x for a while, we can
declare
Moritz Mühlenhoff wrote:
> On Mon, Apr 25, 2011 at 11:29:13AM +1000, Jason White wrote:
> > Laptop-mode appears to be the cause; can you reproduce the bug by enabling
> > it
> > on your X200?
>
> How did you activate the laptop mode on your system?
>
> If
Laptop-mode appears to be the cause; can you reproduce the bug by enabling it
on your X200?
--
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/20110425012913.ga16...@j
Moritz Mühlenhoff wrote:
> Hmm. I'm having a X200 myself and it powers down just fine with the current
> sid kernel.
Are you using laptop-mode? I'll try it without this. BIOS differences are
another possibility, I suppose.
Possibly relevant is the fact that acpitool reports, under 2.6.38, that
I've just tested this again, and the bug is still present as of the latest
package incorporating 2.6.38.4:
Linux jpc2 2.6.38-2-amd64 #1 SMP Sat Apr 23 18:47:49 UTC 2011 x86_64 GNU/Linux
After completing the normal shutdown (unmounting file systems, etc.), the
machine appears to stop very briefly a
Package: linux-2.6
Version: 2.6.38-3
Severity: normal
After upgrading to 2.6.38-2-amd64, my Lenovo X200 laptop reboots instead of
powering down when I run the poweroff command (or equivalently shutdown -h
now). That is, the ordinary reboot/shutdown sequence takes place until the
moment at which t
Ben Hutchings wrote:
> It is not included in the upstream source - even though idmapd(8) refers
> to it!
That's weird. Fedora have it, howver. Perhaps this is a "forward upstream"
bug.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
Package: nfs-common
Version: 1:1.2.3-1
Severity: wishlist
We're missing the idmapd.conf(5) manual page. I checked another distribution
and found it there, however, so it does exist.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Co
I ran grub-install /dev/sda and (just to be sure) rebuilt the initramfs. After
rebooting, kernel 2.6.33-2 loaded successfully.
Thank you for the help. I don't know why everything wasn't updated
automatically; perhaps grub-pc 1.98 didn't re-install itself during the
upgrade.
--
To UNSUBSCRIBE,
maximilian attems wrote:
> upps sorry, wrong message previously got confused.
>
> invoke *if and only if* sda is your harddisc where boot loader is on
> install-grub /dev/sda
>
> update-grub
>
> also check that you completed upgrade from grub to grub2.
I can confirm the latter; Grub 2 has be
maximilian attems wrote:
> aboves error message shows that there is no initramfs passed by the
> bootloader. which grub or lilo do you use?
Grub 2. Regenerating the initramfs is what I tried first, but it didn't help.
I'll try to investigate further.
--
To UNSUBSCRIBE, email to debian-kernel
Package: linux-2.6
Version: 2.6.33-1~experimental.4
Severity: normal
linux-image-2.6.32-3-amd64 is fine, but linux-image-2.6.33-2-amd64 from
experimental won't boot.
As I can't see the screen, I'm relying on others to report the error message,
which is approximately as follows.
Kernel panic - u
Package: linux-2.6
Version: 2.6.32-2
Severity: normal
I am experiencing the problem described here:
http://article.gmane.org/gmane.linux.kernel/927536/
after upgrading to the 2.6.32 kernel.
The symptom is that after boot, the current virtual console is not tty1, but
instead, for example, tty6 or
maximilian attems wrote:
> you could simply use rootfstype bootarg,
> as described in man initramfs-tools.
My mistake was to enter it in uppercase (corresponding to the name of the
environment variable in the script) rather than in lowercase as I should have
done. It works now.
Thanks.
--
Editing scripts.local to hard-code the file system type worked around this
bug.
I suppose this is now a wishlist bug for Btrfs file system type detection.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debi
Package: initramfs-tools
Version: 0.93.4
Severity: wishlist
To experiment with BTRFS as the root file system under KVM, I added btrfs and
associated modules to /etc/initramfs-tools/modules and built an initrd image,
which I then installed to an EXT3 partition in the QCOW2 image to be loaded by
KV
I've posted the details to linux-scsi in case this is known or being worked
on.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Unfortunately, the patch doesn't solve this problem, at least not by itself.
Are there any other options besides bisecting 2.6.30 to 2.6.31? I don't mind
doing a bisect, but it's likely to take more time than I have available in the
near future.
--
To UNSUBSCRIBE, email to debian-kernel-requ.
dann frazier wrote:
> hmm.. wonder if this would help:
>
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=9d2e9d66a3f032667934144cd61c396ba49f090d
>
> Would you be able to test that?
I'll test it against 2.6.31.3 in the next few days.
Maybe it will also app
By way of follow-up, I think I should be able to use netconsole to obtain
(non-visual) access to the kernel oops which this bug causes.
I should have time before the end of the year to work on it by upgrading to
kernel 2.6.31 and conducting some tests. this machine is not my current laptop
anymore
Package: linux-2.6
Version: 2.6.31-1~experimental.1
Severity: normal
After upgrading to 2.6.31 from 2.6.30, I get the following, quite frequently,
in my log.
Oct 8 19:15:03 jdc kernel: [34919.532016] sd 6:1:0:0: strange observation,
the
queue depth is (64) meanwhile fw queue depth (65)
Oct 8 1
Package: linux-image-2.6.30-1-amd64
Version: 2.6.30-5
Severity: normal
I was able to correct this by enabling the Beep,0 amixer setting, then
specifying a non-zero value for that control, and finally setting a reasonable
value for the Speaker,0 parameter.
I had to downgrade the kernel due to an
On Fri, May 23, 2008 at 11:22:30AM +0200, maximilian attems wrote:
> please file upstream in bugzilla.kernel.org and let us know the bug
> number.
Reported as bug 10784 at bugzilla.kernel.org.
I cited this Debian bug in the kernel.org bug report and noted your request
that the bug be taken upst
On Tue, May 20, 2008 at 04:27:09PM +0200, maximilian attems wrote:
> can we have an update for a recent kernel aka 2.6.25 from sid.
> installs just fine in testing.
May 23 15:55:41 jpc kernel: [ 38.255997] powernow-k8: error - out of sync,
fix 0x8 0x0, vid 0x6 0x12
uname -a Linux jpc 2.6.25-2-a
Package: linux-image-2.6.24-1-amd64
Version: 2.6.24-2
Severity: normal
My laptop has an AMD Athlon64 processor. With recent kernels (at least 2.6.22
and 2.6.24, possibly earlier), if run on battery, the laptop eventually hangs.
The error is as reported in the syslog output below. I am using the
p
27 matches
Mail list logo
