On 11/24/2011 09:25 AM, Jonathan Nieder wrote:
Interesting. Is this the same machine ashttp://bugs.debian.org/593792?
Yes, it is. Last year, I've tried to exclude memory problems by running
memtest86+ for probably ~24h, there were no errors.
BTW: I've stopped using curlftpfs because I
Dear Jonathan,
On 10/21/2011 01:26 AM, Jonathan Nieder wrote:
I came across this BUG yesterday on my Asus Eee PC 1000HG. I had probably
done 10-15 suspend/resume cycles that day. I think I had mounted curlftpfs
over a somewhat flaky 3G connection earlier that day, but I didn't access it
at
On 08/21/2010 05:03 AM, Ben Hutchings wrote:
Unless this is reproducible, there is little we can do with this
information.
Ok, so from now on, I'll only report BUGs which have occurred more than
once.
However, if you want to record oops messages to help developers spot
patterns, please
On 08/21/2010 05:19 AM, Ben Hutchings wrote:
The kernel image in the above package contains this machine code around
the address of the faulting instruction:
[...]
Notice that several bytes around the faulting instruction (8b) differ
from this in the recorded 'oops'. This indicates memory or
Package: linux-2.6
Version: 2.6.32-18
Severity: normal
this killed my X:
gdm[1826]: WARNING: gdm_slave_xioerror_handler: Fatal X error - Restarting :0
[101389.218207] BUG: unable to handle kernel paging request at ffd17c8c
[101389.218223] IP: [c10bd1ab] do_vfs_ioctl+0x3ad/0x4e5
[101389.218242]
Package: linux-2.6
Version: 2.6.32-15
Severity: normal
that one is a couple of weeks old. (I've rebooted in between).
[154768.442008] BUG: unable to handle kernel NULL pointer dereference at
0041
[154768.442026] IP: [c10c0d46] __d_lookup+0xb5/0xd3
[154768.442046] *pde =
I think I have found a way to reproduce the problem:
1. Mount a remote ftp server using curlftpfs.
2. Start a write process on that ftp mount, eg.
dd if=/dev/zero of=/file/on/ftp/mount
3. Suspend will fail as long as dd is running.
Cheers, Thiemo
--
To UNSUBSCRIBE, email to
On 05/22/2010 01:04 AM, Ben Hutchings wrote:
Has this error occurred before, or just once?
Never since the beginning of my logs, which is July 2009.
Which filesystem are you using for /boot?
# mount | grep boot
/dev/sda6 on /boot type ext3
Package: linux-2.6
Version: 2.6.32-12
Severity: normal
Cheers!
Thiemo
[ 3587.353975] BUG: Bad page state in process 10_linux pfn:352fe
[ 3587.353996] page:c1b67fc0 flags:4000 count:0 mapcount:-9835008
mapping:(null) index:bfffe
[ 3587.354013] Pid: 9401, comm: 10_linux Not tainted
Maybe to avoid confusion I should add that during the time of reporting
the bug, I had 2.6.32-13 already installed, but not rebooted yet. The
bug applies to 2.6.32-12.
Cheers!
Thiemo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble?
On 05/03/2010 03:20 PM, Ben Hutchings wrote:
It was only accepted earlier today, so it may take another day to
propagate.
I've installed it. Let's see whether I hit the problem again. I assume
the odds are low, though, as I've only seen it once in 2.6.32-4.
Cheers, Thiemo
--
To
Julien Cristau wrote:
Reassigning to the kernel.
Sorry for filing against the wrong package.
If this is reproducible with
linux-image-2.6.32-5-686 (version 2.6.32-12)
Where can I get 2.6.32-5?
Cheers, Thiemo
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a
On 04/12/2010 12:02 AM, Ben Hutchings wrote:
Sorry for the delay in responding to this. Does this problem still
occur when using the current kernel version (2.6.32-9 in testing or
2.6.32-11 in unstable)?
I've seen it just yesterday, using Linux version 2.6.32-4-686 (Debian
2.6.32-11).
If
I've reported the issue to Linux bugzilla:
https://bugzilla.kernel.org/show_bug.cgi?id=15772
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
-22
[130900.000342] PM: Some devices failed to suspend
Running
rmmod ehci_hcd modprobe ehci_hcd
cures the problem.
Cheers!
Thiemo Nagel
-- Package-specific info:
** Version:
Linux version 2.6.32-trunk-686 (Debian 2.6.32-5) (b...@decadent.org.uk) (gcc
version 4.3.4 (Debian 4.3.4-6) ) #1
Ordinary users will be affected as soon as the linux kernel version adds
another digit:
* 2.6.100
* 2.10.x
* 10.x.x
Even today 2.6.30.10 sorts before 2.6.30.9, so anybody who builds his
own kernel may be affected (not -rc kernels only).
--
To UNSUBSCRIBE, email to
Package: initramfs-tools
Version: 0.93.4
Severity: normal
It seems as if lexical sort is used to determine the newest kernel for which
the initramfs is updated when calling update-initramfs -u. For example, at
my machine, this leads to the initramfs of 2.6.32-rc8 being updated instead of
the
On 12/14/2009 06:46 PM, maximilian attems wrote:
On Mon, Dec 14, 2009 at 03:00:59PM +0100, Thiemo Nagel wrote:
It seems as if lexical sort is used to determine the newest kernel for which
the initramfs is updated when calling update-initramfs -u. For example, at
my machine, this leads
Just to let you know: I can still reproduce this issue with 2.6.26-1-amd64.
Kind regards,
Thiemo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
|
\- LV /dev/crypto-VG/root_lv -- mounted /
Output of pvdisplay, vgdisplay and lvdisplay is attached.
I'm also attaching the system configuration info generated by reportbug.
In case you need more info, just ask. I'm willing to investigate further.
Kind regards,
Thiemo Nagel
the idea is to backup on an update call any initramfs
that is older than a certain time, lets say 6h or maybe 24h
thus not created while upgrading mdadm, udev, usplash, cryptsetup or
so together.
How about backuping any initramfs that is older than uptime?
will be in 0.81 update-initramfs.
A power cut during update-initramfs may leave the system in an unbootable state as the old initrd.img is
overwritten, but the new initrd.img is not yet completed. (This happened to me when my laptop battery ran empty.)
A simple fix would be to create the new initrd.img as a temporary file and
Package: initramfs-tools
Version: 0.79
Severity: important
A power cut during update-initramfs may leave the system in an unbootable state
as the old initrd.img is
overwritten, but the new initrd.img is not yet completed. (This happened to me
when my laptop battery ran empty.)
A simple fix
Package: kernel-image-2.6.8-2-k7
Version: 2.6.8-12
Severity: grave
Justification: causes non-serious data loss
Zero-length accesses to Samba shares return errors after 30s timeout, while
the requested action seems to happen:
[EMAIL PROTECTED]:/mnt/thiemo$ l test
-rw-r--r-- 1 thiemo users 0 Jan
24 matches
Mail list logo
