On Sun, Jul 14, 2013 at 06:32:05PM +0200, Moritz Mühlenhoff wrote:
Version: 3.9-1
On Fri, Jul 12, 2013 at 11:19:56AM +0300, Martin-Éric Racine wrote:
It still does with 3.2 in stable, but not with 3.9 in testing.
Closing with that version, then.
No such version (3.9-1) was uploaded,
reassign 677655 src:linux
thanks
On Sat, Jun 16, 2012 at 03:48:45AM -0500, Jonathan Nieder wrote:
Martin-Éric Racine wrote:
Yup, this issue returns every now and then on the exact same host
(which was recently migrated from Ubuntu to Debian, now that Ubuntu
stopped supporting anything
It still does with 3.2 in stable, but not with 3.9 in testing.
Martin-Éric
2013/7/12 Moritz Muehlenhoff j...@inutil.org
reassign 677655 src:linux
thanks
On Sat, Jun 16, 2012 at 03:48:45AM -0500, Jonathan Nieder wrote:
Martin-Éric Racine wrote:
Yup, this issue returns every now and
2012/6/16 Jonathan Nieder jrnie...@gmail.com:
Jonathan Nieder wrote:
By the way, searching for that particular address yields the following
interesting result. (Nothing else recent, alas.)
Better link:
https://bugzilla.kernel.org/show_bug.cgi?id=13941
Yup, this issue returns every now
2012/6/16 Ben Hutchings b...@decadent.org.uk:
On Fri, 2012-06-15 at 22:37 +0300, Martin-Éric Racine wrote:
Hi Jonathan,
2012/6/15 Jonathan Nieder jrnie...@gmail.com:
Hi Martin-Éric,
Martin-Éric Racine wrote:
I'm not sure if it's too early to report on kernel 3.4 or not, but
here it
Martin-Éric Racine wrote:
Yup, this issue returns every now and then on the exact same host
(which was recently migrated from Ubuntu to Debian, now that Ubuntu
stopped supporting anything older than non-PAE 686 hardware), whenever
someone touches the inode code again. The nice thing, this
Package: linux-2.6
Version: 3.4.1-1~experimental.1
Severity: normal
I'm not sure if it's too early to report on kernel 3.4 or not, but here it
goes: dmesg keeps on reporting spurious kernel oppses involving inode
destructions, as seen below, whenever running kernel 3.4-trunk.
--
Hi Martin-Éric,
Martin-Éric Racine wrote:
I'm not sure if it's too early to report on kernel 3.4 or not, but
here it goes:
Any package uploaded to the archive is open for bug reports. :)
[...]
** Kernel log:
[ 29.054891] DR0: DR1: DR2: DR3:
[
Hi Jonathan,
2012/6/15 Jonathan Nieder jrnie...@gmail.com:
Hi Martin-Éric,
Martin-Éric Racine wrote:
I'm not sure if it's too early to report on kernel 3.4 or not, but
here it goes:
Any package uploaded to the archive is open for bug reports. :)
Could you send the full oops trace,
Martin-Éric Racine wrote:
Here's the dmesg output at bootup, right after the first few oopses
have started to appear.
Thanks, nice and quick.
Let's see:
[...]
6[ 28.167997] EXT4-fs (sda1): re-mounted. Opts: (null)
6[ 28.721401] EXT4-fs (sda1): re-mounted. Opts: (null)
1[ 29.595342]
On Fri, 2012-06-15 at 22:37 +0300, Martin-Éric Racine wrote:
Hi Jonathan,
2012/6/15 Jonathan Nieder jrnie...@gmail.com:
Hi Martin-Éric,
Martin-Éric Racine wrote:
I'm not sure if it's too early to report on kernel 3.4 or not, but
here it goes:
Any package uploaded to the archive
Ben Hutchings wrote:
On Fri, 2012-06-15 at 22:37 +0300, Martin-Éric Racine wrote:
Here's the dmesg output at bootup, right after the first few oopses
have started to appear.
The kernel is trying to free an inode and using an ACL pointer that
should presumably be 0x (special value
Jonathan Nieder wrote:
By the way, searching for that particular address yields the following
interesting result. (Nothing else recent, alas.)
Better link:
https://bugzilla.kernel.org/show_bug.cgi?id=13941
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a
On Fri, 2012-06-15 at 21:23 -0500, Jonathan Nieder wrote:
Jonathan Nieder wrote:
By the way, searching for that particular address yields the following
interesting result. (Nothing else recent, alas.)
Better link:
https://bugzilla.kernel.org/show_bug.cgi?id=13941
Oohkay, so you've
14 matches
Mail list logo
