Installing avahi-daemon crashes kernel, corrupts filesystem
Jason Heeris
CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I
could be wrong
RAM: 256MB
Swap: partitioned, about 236MB (just what the installer recommended)
Kernel: 2.6.32-5-486
Debian: Squeeze (from installer daily build, updated after install;
this also happens with Emdebian)
Storage is a 4GB flash card (I don't have sdparm or hdparm, and I
can't install either to get more info. If there's another way, let me
know.) It was formatted ext2.
My problem started when I installed avahi-daemon - the system crashed,
and I could not recover to a useable state. So I reinstalled the
system and approached it a little more carefully.
>From a fresh Squeeze install, I installed every dependency of
avahi-daemon (no recommends), and nothing bad happened. When I
installed avahi-daemon itself (aptitude -R install avahi-daemon), it
got to the stage of setting up the package when my screen filled with
what looked like a stack trace:
http://heeris.id.au/stuff/SBCError.jpg
Anything else went past too fast to see, sorry. I also got the
numlock/capslock blinking lights.
I can start in recovery mode, but when I log in as root I see the message
::: No such file or directory
(This is un-Google-able!)
First thing, I run fsck on the root FS, and one of the first problems is:
Unconnected directory inode 98170 (/var/lib/dpkg/???)
I hit "y" a few times when prompted, then Ctrl+C and run "fsck -y"
instead. There's a lot of cleanup, and I reboot.
Now if I run aptitude, I get:
E: 7/.aptitude - mkdir (2: No such file or directory)
E: dpkg was interrupted, you must manually run 'dpkg --configure
-a' to correct the problem.
...and then a segfault from aptitude. Funny thing is, when I run the
dpkg command, it just says
Setting up avahi-daemon (0.6.27-2)
...and back to the prompt. Next aptitude run, same mkdir error and segfault.
Anyway, suffice to say it's all pretty damaged. Another example is, as root:
# groups
groups: cannot find name for group ID 0
I'm not too interested in saving the system, it's a dev environment
and is completely expendable (because I use source control and make
backups, of course). So I can reinstall the system, but then I *would*
like to (a) install avahi-daemon if possible, and (b) figure out what
is causing this, because I'd rather not install some other package in
a few weeks and hose the system again... if I can help it.
I could use some help getting to the bottom of this! I can boot off my
installer USB into rescue mode, and I can do some very limited things
from recovery mode on the partition itself. I'm not averse to
recompiling packages (including the kernel, if there's room). I'll
keep the damaged system around for diagnostics until I can't get any
more info from it.
So if anyone can help, even with a "have you tried <this>..." or
"maybe it's the <something>..." remark, I'd appreciate it.
Thanks,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTi=Y7B72b9bh-BqzmePNhnZ4tS=N3grp=S9F...@mail.gmail.com
Jason Heeris
> Looks like a kernel panic or a kernel oops. Seeing the start of it would
> be helpful.
Any tips on catching it? Will there be useful info in a log somewhere?
> That looks like your filesystem is damaged beyond what one could expect
> from a single crash. I would try to (in that order)
I wonder if the flash card is more sensitive to crashes like this than
the usual spinning platters...?
> - make sure the CF card is ok (badblocks scan in another system)
Just finished one from the USB installer (rescue mode). Didn't seem to do much.
> - make sure the mainboard/CPU/RAM is ok (memtest86, if it runs on your
> system)
That will have to wait until a reinstall - I can only boot in recovery
mode, and I can't install anything because dpkg hits unrecoverable
errors (this time, "syntax error: unknown group 'crontab' in
statoverride file").
I did run memtest86+ a couple of weeks ago (no particular reason) and
it was fine, but a hardware problem is not out of the question. Not
sure how to catch it if memtest can't see it though.
> My guess would be that you have a hardware problem for some time now. I
> only find it curious that it can be reproduced when installing a
> particular package. Is the segfault reproducible after a reinstall as
> well?
Yep, every time. I just wonder if somehow the avahi-daemon package is
the only thing I'm trying to install that, say, requires that much
more memory than any other package for configuration.
> Where do your packages come from (official mirror, local mirror,
> self-burnt disc etc.)?
They're from the iiNet mirror (http://ftp.iinet.net.au/debian/debian)
Thanks,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTimgd_sEr-GzXgWPzZsJvPn+rL+uWL=EsVr...@mail.gmail.com
Jason Heeris
>> Any tips on catching it? Will there be useful info in a log somewhere?
>
> optimistic about that.
No, I had checked that already. :/
> May be. Do you have write caching enabled?
How would I know?
>>> - make sure the CF card is ok (badblocks scan in another system)
>>
>> Just finished one from the USB installer (rescue mode). Didn't seem to do much.
>
> What do you mean by that?
This is from memory, but I ran "fsck.ext2 -c -C 0 -p -f /dev/sdb1" and
after running for a while said something like:
updating bad blocks inode XXXXXXXX; /dev/sdb1: XXXX/XXXX files
(1.6% non-contiguous), XXXXX/XXXXX blocks
So... if there were bad blocks, it didn't make a fuss about it.
I'm going to commence a destructive badblocks scan ("badblocks -b 4096
-s -w /dev/sdb1") - can badblocks be given an entire device instead of
a partition? Or does that not make sense?
>> Yep, every time. I just wonder if somehow the avahi-daemon package is
>> the only thing I'm trying to install that, say, requires that much
>> more memory than any other package for configuration.
>
> Maybe you should try to install and run KDE and Firefox. ;-)
I don't want to start a fire, there's expensive equipment nearby...
- Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTimerxdPXb6Tt2w816ZRfw=4gckYD1=u-Sb...@mail.gmail.com
Henrique de Moraes Holschuh
> My system is a Helios single-board computer, with specs:
>
> CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I
> could be wrong
Yikes. You really need to track this one down, and find out whether it is
any different from a regular 486. The devil IS in the details, and these
older boxes are NOT regularly tested anymore.
In fact, we can't really attest that Debian does work perfectly even on
straight Intel i486 anymore, let alone on 486-alike chips: We depend on
sheer dumb luck that the kernel and gcc have not regressed (very little/no
testing is done on 486s anymore), and some packages might not be
486-compatible at all.
But your issue is NOT an avahi bug (package, compiler or otherwise). It is
either a kernel bug *or* the kernel is simply incompatible with your
vortex86 processor in a way that went undetected by the sanity checks at
kernel startup.
> My problem started when I installed avahi-daemon - the system crashed,
> and I could not recover to a useable state. So I reinstalled the
> system and approached it a little more carefully.
1. Set up a serial console (to capture crash data);
2. Make sure you're in condition to lose data;
3. Reproduce the crash, log *everything* since boot.
4. File a bug on bugzilla.kernel.org with all relevant information. This
does include the kernel config at the very least.
> http://heeris.id.au/stuff/SBCError.jpg
The box objected VERY HEAVILY to the ipv6 multicast operations trigerred by
avahi. Without fixing the underlying bug, your box will be unusable (lots
of other stuff are likely to trigger the same problem).
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/20101012023...@khazad-dum.debian.net
Jason Heeris
> On Sun, 10 Oct 2010, Jason Heeris wrote:
>>
>> CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I
>> could be wrong
>
> Yikes. You really need to track this one down, and find out whether it is
> any different from a regular 486. The devil IS in the details, and these
> older boxes are NOT regularly tested anymore.
According to http://www.vortex86.com/index2.html
Vortex86 family integrates a high-performance processor that
supports x86 instruction set with 3 integer units, 3-way
superscalar architecture, and a fully pipelined floating point unit.
Hmm. According to /proc/cpinfo on the installer,
> 1. Set up a serial console (to capture crash data);
> 2. Make sure you're in condition to lose data;
> 3. Reproduce the crash, log *everything* since boot.
What do you mean by "everything"? Every command? That's not hard. All
the kernel messages? That's harder... The logs in /var/log do not seem
to contain *anything* about the session during which the crash occurs.
> 4. File a bug on bugzilla.kernel.org with all relevant information. This
> does include the kernel config at the very least.
It's just the Debian stock kernel config.
> The box objected VERY HEAVILY to the ipv6 multicast operations trigerred by
> avahi.
Given this, can you think of another way I might be able to trigger
the bug? If so, I might be able to do it without needing to reinstall
the system every time.
> Without fixing the underlying bug, your box will be unusable (lots
> of other stuff are likely to trigger the same problem).
That's what I was afraid of. Thanks for the info, I'll see what I can do.
Cheers,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTimJN1p1iYnVwH4DT...@mail.gmail.com
Ron Johnson
> On 11 October 2010 18:36, Henrique de Moraes Holschuh<h...@debian.org> wrote:
>
>> The box objected VERY HEAVILY to the ipv6 multicast operations trigerred by
>> avahi.
>
> Given this, can you think of another way I might be able to trigger
> the bug? If so, I might be able to do it without needing to reinstall
> the system every time.
>
>> Without fixing the underlying bug, your box will be unusable (lots
>> of other stuff are likely to trigger the same problem).
>
> That's what I was afraid of. Thanks for the info, I'll see what I can do.
>
My 1st thought was whether you need IPv6...
--
Seek truth from facts.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
> My 1st thought was whether you need IPv6...
Well, no, and if I can't sort this out then I'll recompile without it
and see if the crash goes away (or... can I black list it, or is IPv6
compiled right in?). But this might be a good opportunity to find a
bug before I go down that path.
Cheers,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTinKLQArnKsH_-_bR...@mail.gmail.com
Ron Johnson
> 2010/10/12 Ron Johnson<ron.l....@cox.net>:
>> My 1st thought was whether you need IPv6...
>
> Well, no, and if I can't sort this out then I'll recompile without it
> and see if the crash goes away (or... can I black list it, or is IPv6
Sure.
http://blogs.koolwal.net/2009/10/11/howto-blacklisting-kernel-module-from-auto-loading-in-debian/
I'd also tell avahi not to use IPv6.
http://linux.die.net/man/5/avahi-daemon.conf
> compiled right in?). But this might be a good opportunity to find a
> bug before I go down that path.
--
Seek truth from facts.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
>> 4. File a bug on bugzilla.kernel.org with all relevant information. This
>> does include the kernel config at the very least.
>
> It's just the Debian stock kernel config.
Should I recompile it with any kind of debugging information enabled,
or does the Debian kernel already contain it?
— Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTinh05FUzXjJZf13A...@mail.gmail.com
Timo Juhani Lindfors
> Should I recompile it with any kind of debugging information enabled,
> or does the Debian kernel already contain it?
It depends on the architecture and debian version. Please post a
proper bug report with reportbug that shows all the relevant version
information. Can you make this crash happen under an emulator like
qemu (hint: you can sudo chmod a+r /dev/hda && qemu -snapshot -hda
/dev/hda to temporarily test the current installation under qemu
without writing anything to disk).
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
> [ I guess Henrique's interpretation of the problem is better than mine,
> I just wanted to follow-up on this specific question. ]
>> How would I know?
>
> $ dmesg | grep "Write cache"
> sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
>
> I don't whether disabling this would stress the CF card more or less,
> but you should experience less filesystem corruption after a crash.
> AFAICT you need hdparm to disable it, though.
I just sorted this out not ten seconds ago :)
hdparm -W 0 /dev/sda
...did the trick (and yes, it was on). I'm hoping to find the call
that makes avahi trigger the crash, so I can do it a little more
simply.
Cheers,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTimiSAM7050vdmZpj...@mail.gmail.com
Timo Juhani Lindfors
Jason Heeris <jason....@gmail.com> writes:
> Kernel: Linux 2.6.32-5-486
Please install linux-image-2.6.32-5-486-dbg
> Qemu won't start, it can't find a framebuffer:
>
> (!) Direct/Util: opening '/dev/fb0' and '/dev/fb/0' failed
> --> No such file or directory
Qemu defaults to X. Copying the system image to some machine that runs
X is probably the safest solution, you can then run qemu without any
extra privileges..
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
> Jason Heeris <jason....@gmail.com> writes:
>> Kernel: Linux 2.6.32-5-486
> Please install linux-image-2.6.32-5-486-dbg
There is no such package:
http://packages.debian.org/search?keywords=linux-image+dbg&searchon=names&suite=testing§ion=all
Yay. I'll build one on my PC.
> Qemu defaults to X. Copying the system image to some machine that runs
> X is probably the safest solution, you can then run qemu without any
> extra privileges..
Done, but avahi-daemon installs without a hitch (presumably because
the processor itself is part of the equation).
— Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTikvq9oF6wfpSSQOm...@mail.gmail.com
Timo Juhani Lindfors
> Yay. I'll build one on my PC.
Ah.
>> Qemu defaults to X. Copying the system image to some machine that runs
>> X is probably the safest solution, you can then run qemu without any
>> extra privileges..
>
> Done, but avahi-daemon installs without a hitch (presumably because
> the processor itself is part of the equation).
Ok. Then you need something to save the state of the system to disk on
panic. Kdump is probably easiest but it is not in debian yet. I have
only used Xen and qemu virtualization for my kernel debugging needs.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
> On Sun, 10 Oct 2010, Jason Heeris wrote:
>> CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I
>> could be wrong
>
> Yikes. You really need to track this one down, and find out whether it is
> any different from a regular 486. The devil IS in the details, and these
> older boxes are NOT regularly tested anymore.
For the sake of posterity, Diamond Systems Tech Support say:
The Vortex86 processor is a 486 class pre-pentium integrated circuit.
Cheers,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTinAeMqOcdMGJPo8F...@mail.gmail.com
Jason Heeris
> Jason Heeris <jason....@gmail.com> writes:
>> Yay. I'll build one on my PC.
>
> Ah.
To save me more trouble, can anyone tell me what the key is to
building a kernel exactly the same as what's in
linux-image-2.6.32-5-486? I'm on a PC with amd64 arch, so I created a
i386 chroot:
sudo debootstrap --arch i386 squeeze ia32-chroot
http://ftp.iinet.net.au/debian/debian
I installed linux-source-2.6.32 (actually from sid, since the one in
squeeze FTBs). Unpack the source, and:
linux32 make menuconfig
...selecting 486 processor family. Then:
linux32 make-kpkg clean
CONCURRENCY_LEVEL=4 linux32 make-kpkg --initrd
--append-to-version=-custom1 kernel_image kernel_debug
The resulting kernel does not find the root fs, so clearly it is
somehow different to what's in the archive. Where can I get the exact
config for the official 486 kernel?
Cheers,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTi=RdtXVqNFBnHMQEcbzn...@mail.gmail.com
Jason Heeris
> To save me more trouble, can anyone tell me what the key is to
> building a kernel exactly the same as what's in
> linux-image-2.6.32-5-486?
More RTFMing required on my part, sorry. In the DEBIAN.Readme for the
linux-image source package:
Each linux-image-* package provides the complete .config file that
was used to generate it. This file is installed in /boot.
So I found it in the deb package.
— Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTiþrHeuhwZNzv3MFb5_J...@mail.gmail.com
Jason Heeris
> 3. Reproduce the crash, log *everything* since boot.
Before I go off to bugzilla, I just want to check that I've actually
got debugging information here, since to me it doesn't look that
different. Do I need to boot with a special kernel arg?
- Jason
Jordan Metzmeier
> Before I go off to bugzilla, I just want to check that I've actually
> got debugging information here, since to me it doesn't look that
> different. Do I need to boot with a special kernel arg?
Looks like this bug was reported on the avahi upstream mailing list [1].
The person responding indicates a kernel problem, which makes sense when
you actually get a kernel panic as a result. This was also indicated on
this list.
The 'reportbug' tool will include quite a bit of information for you in
the report, so adding additional logs to the bug report may not even be
needed.
However, it appears that the log you included was the custom kernel you
attempted to use as directed by the others on this list. Make sure you
when you report the bug, you include relevant logs for the kernel
packaged by Debian.
Disabling support for ipv6 can actually be done via a kernel parameter,
so recompiling to remove ipv6 support should not be needed. Use the
kernel parameter "ipv6.disable=1".
Good luck!
[1] http://www.mail-archive.com/av...@lists.freedesktop.org/msg01550.html
Regards,
--
Jordan Metzmeier
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
> The person responding indicates a kernel problem, which makes sense when
> you actually get a kernel panic as a result. This was also indicated on
> this list.
I'm trying to figure out if there's a simpler way to trigger it, but
haven't really figured that out.
> However, it appears that the log you included was the custom kernel you
> attempted to use as directed by the others on this list. Make sure you
> when you report the bug, you include relevant logs for the kernel
> packaged by Debian.
I only used the custom kernel to get debugging information. The
configuration is the same, but I can do both.
> Disabling support for ipv6 can actually be done via a kernel parameter,
> so recompiling to remove ipv6 support should not be needed. Use the
> kernel parameter "ipv6.disable=1".
Good point. It seemed that there was no module to blacklist after all.
— Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTiÇYowejLqvGCbOYHbW3...@mail.gmail.com
Timo Juhani Lindfors
> To save me more trouble, can anyone tell me what the key is to
> building a kernel exactly the same as what's in
> linux-image-2.6.32-5-486? I'm on a PC with amd64 arch, so I created a
> i386 chroot:
I have personally used
http://wiki.debian.org/HowToRebuildAnOfficialDebianKernelPackage
many times.
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Henrique de Moraes Holschuh
> On 12 October 2010 10:36, Henrique de Moraes Holschuh <h...@debian.org> wrote:
> > On Sun, 10 Oct 2010, Jason Heeris wrote:
> >> CPU: Vortex86 SoC (800MHz) - I *think* this is pretty much a 486, I
> >> could be wrong
> >
> > Yikes. �You really need to track this one down, and find out whether it is
> > any different from a regular 486. �The devil IS in the details, and these
> > older boxes are NOT regularly tested anymore.
>
> For the sake of posterity, Diamond Systems Tech Support say:
>
> The Vortex86 processor is a 486 class pre-pentium integrated circuit.
You want them to tell you all of the optional features they did NOT
implement, i.e. in which ways are they different from Intel i486.
Hopefully, the answer is "none, we are fully compatible, even on the
optional features".
--
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot
Henrique Holschuh
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/2010101316...@khazad-dum.debian.net
Jason Heeris
> Disabling support for ipv6 can actually be done via a kernel parameter,
> so recompiling to remove ipv6 support should not be needed. Use the
> kernel parameter "ipv6.disable=1".
Yep, disabling IPv6 stops the crash!
So where should I report it, debian kernel bug tracker or upstream bug
tracker? I figured the former, since it's not a bleeding edge kernel
I'm running, but maybe I'm wrong.
Cheers,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTi=9ib01w-hJM8cZ77bHY...@mail.gmail.com
Jordan Metzmeier
Hash: SHA256
On 10/13/2010 08:58 PM, Jason Heeris wrote:
> So where should I report it, debian kernel bug tracker or upstream bug
> tracker? I figured the former, since it's not a bleeding edge kernel
> I'm running, but maybe I'm wrong.
>
> Cheers,
> Jason
I would first check to see if the problem still occurs in .35 from the
experimental repos. I believe it is much easier for them to provide a
fix when it can be backported from a newer upstream.
Regards,
- --
Jordan Metzmeier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMtl4fAAoJEKj/C3qNthmTjI0QAJyo1ffeSCYdVKmYxzbYBuiO
EZh7T0V5yRTEiD1LLNJmXDBb7aaMy1EndyPxeKPmcpa6Dztt3f5q4ic32RVq9J+X
65FR91ku0gt1Vp+sBbC+zUwnb0kAbu9Y7xlQlPmC0dnngpvwVUKTSViiD2NY6C1N
zLC16xblQH4K00UbHlBxgZ6fHybvGdUx3Ux201AScN7pV6dSnekbTrCdaOLO8n40
/vJxJTLxfM+gfix5NGMEg8meT5FPHhGeXklO4VesMDK8CIH7P+bGrP152gvtt8Tj
kFcvlFdx+55vNp/5kBaH3LsgBOrQ9PTWJr0oroqykflzBxypLdUpdIj5N+ShxIhF
IoGHwrHrh61X2r6HCIfo3svO7UedgSElwIeUjjtwWtM8qFriCWJj2PXWT9hTBcv/
gb+abXjy/tmcuxgc+Cu+QlluZeoepS4AWojbPWBh5BaJE0Koleqfi0lt4tWhL6TG
tZaQCyrlIVMAklDloJy/EgOfwlEPMvba2c+7JREYz9THBmvR6sjjqB5w2A6qVt34
zjwC0cXl6APq2MpN2wDktSYo/6KbUxxGsknMF81+XYuHu3Hq5Mw4ShAs/YdYWvPA
TUmpu3xHh8Sr6B3aNoTVqr+Nhdih6kPmG0NIIJoSN8n2c0vi5WbSYxuoftuG8gkl
88A2TP3+hSn1lGO9nLXd
=gZch
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
> I would first check to see if the problem still occurs in .35 from the
> experimental repos. I believe it is much easier for them to provide a
> fix when it can be backported from a newer upstream.
Interesting, no crash with 2.6.36-rc6-486. I'll report it anyway.
- Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTi=katuUeQcNw8=r9Quuk6TxnLq...@mail.gmail.com
Jordan Metzmeier
Hash: SHA256
On 10/13/2010 09:57 PM, Jason Heeris wrote:
> On 14 October 2010 09:34, Jordan Metzmeier <tita...@gmail.com> wrote:
>> I would first check to see if the problem still occurs in .35 from the
>> experimental repos. I believe it is much easier for them to provide a
>> fix when it can be backported from a newer upstream.
>
> Interesting, no crash with 2.6.36-rc6-486. I'll report it anyway.
>
> - Jason
Please do as .32 is what will ship in the next stable.
Regards,
- --
Jordan Metzmeier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMtn58AAoJEKj/C3qNthmTC0wP/iP/AGW50VGfk8ABBJj6+9hN
cPf1QqvBKBKIY/iQtNN/bqPFalIQSXhWB+avUoJUGrbBfCbmh4477UtyjnRi6yu5
ks3bmJcvKQvioqE5F0NDB7i7BaIRZ/sbB/XO8LNK9qCscHz2Nccp9IRzQr5bIBTV
zcLUJvvEoYpIuKTi39IJPaq6tE3eKW14Vndn9ggAsWH6iju0m4Y2BZxp8CYQDHRH
oeC/tPV6syI4ei+HS938tIfXPT4a2VpLb8XR01Av1TIiBX5NPloEssJnZFomqNXU
gf/swAtHGlBuawkRihnZVICKbHwZWRZzxL0D82PglsBzR3ZYZ/zRWYWTnnDQfNtw
iSEohvOGLoHuNjBc10VVFVjlsA0DD2dpMP1Jx2onixjyYjdz8tFeCc0TgmyiuPZ+
HWBQozr0/CS0YEUeLNxSRGfJemjkordo++JaVnS4MuQ7p80YIWAe9OSRCf9hiYic
+b/97jnUbs1iuPJi6hEi3/VEd1w1R0F5zp0QMZAedeQ+orJproxabgZHJpNkE1yc
opNbQ//VeUsk0kISaDdmbdB0KFKTtjNYwYgM6dt+rsXNTDz4dKqCnYZfteLfr2Y9
IstzLt73A+eB25zDVYfe3d7SPQsBAJpAQ1/WeUafmBjfSxxg+tZC9eSnDKFV0MUv
F4uEA8+ibYXpE63Cm+rI
=uVbB
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
> Please do as .32 is what will ship in the next stable.
Bug filed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600155
My real solution to all of this was to disable IPv6 altogether. Thanks
everyone for the help :) (Also, I learnt about a dozen new things over
the course of this thread, so that's nice...)
Cheers,
Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTimwd4TttnHW97Jqn...@mail.gmail.com
Jordan Metzmeier
Hash: SHA256
On 10/14/2010 12:32 AM, Jason Heeris wrote:
> On 14 October 2010 11:52, Jordan Metzmeier <tita...@gmail.com> wrote:
>> Please do as .32 is what will ship in the next stable.
>
> Bug filed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600155
>
> My real solution to all of this was to disable IPv6 altogether. Thanks
> everyone for the help :) (Also, I learnt about a dozen new things over
> the course of this thread, so that's nice...)
Anytime and subscribed :). That may even be an RC as full ipv6 was a
release goal of squeeze. Also, if it really was corrupting your
filesystem, I would think that would be a "critical" RC.
critical - makes unrelated software on the system (or the whole system)
break, or *causes serious data loss*, or introduces a security hole on
systems where you install the package. [1]
emphasis mine.
[1] http://www.debian.org/Bugs/Developer#severities
Regards,
- --
Jordan Metzmeier
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iQIcBAEBCAAGBQJMtoyLAAoJEKj/C3qNthmTC1oQAKzRmFdv+WOdmGJwNlJr0Oz9
ysekMddMeVXpl5BzwDTDh6YST6t5q4lmvixwQe0ZzgdYTljlPLORhqkXAF96fYsy
xVYNQ7ZSkbKZGuv3j3ZI/rJoZk7tj67+1+oHa2F+79g0Q6CUA+1p9eH0ctASd6sM
JTdZsGQtobLE3rVwHReGYc1SScVeshkesG1DWzmvJ1k+B9pf964dewDd4EiWXpE2
uSIJZ3vmsZa22nJjrn9HfdLebB4aj/jmJ5OpAiAES8GYT82XD3EU/MFtfudu8Os4
jz3TbdLB+dh1gWEo6+twf2iCl9oYTzFfWW1iZ8OfrevsXaZjO4k//KJeLkuR4RWy
DbBuRZe2qqzAPweqJPsJiAsajpeRiTeaSsFCQb099gQxV33KH8NQaevNJlWOoBtj
HX8oLG858JaqsE/LBdZH5W8iO5cOvE1Wy/avfdxv1uUhztDIKgevAE731pyfVOh3
g2LBQpzZRlCfLmJ0okkCLBEyfiNXVNWHuB89O/vGmUze5HmWXwm2NzoMzsFJ6yKo
OmMyFoUYpLL3GYHqS0C6AImll2NBB9tjJY/CLIURRiDp8vKhRVXfs6hUq7SXi47s
ev6fVZYw7MclopVF34GHrE9xqVB6gFemQQlt3PwevN7ZTant/WXrlB3M6HuZjSLw
4eKMxxAqG7nhx+Bee3fw
=bE/m
-----END PGP SIGNATURE-----
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Jason Heeris
> Anytime and subscribed :). That may even be an RC as full ipv6 was a
> release goal of squeeze. Also, if it really was corrupting your
> filesystem, I would think that would be a "critical" RC.
That's harder to assert, I think. My FS got corrupted because I had
write caching enabled... any kernel panic might have caused it.
(Having said that, it's now re-enabled so I don't overtax the CF card.
I'm happy with my dd-taken image as a checkpoint.)
- Jason
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/AANLkTik9r-KCCrKrZK3XS...@mail.gmail.com