On Thu, 14 Oct 2010, Jordan Metzmeier wrote:
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
It is clearly something that requires testing on UP, probably on a i486 to
reproduce (otherwise, our kernels would be
On 12 October 2010 19:49, Timo Juhani Lindfors timo.lindf...@iki.fi wrote:
Jason Heeris jason.hee...@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 13 October 2010 14:45, Jason Heeris jason.hee...@gmail.com wrote:
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
On 11 October 2010 18:36, Henrique de Moraes Holschuh h...@debian.org wrote:
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
On 10/13/2010 05:16 AM, Jason Heeris wrote:
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
On 13 October 2010 22:35, Jordan Metzmeier titan8...@gmail.com wrote:
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
Jason Heeris jason.hee...@gmail.com writes:
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
On Wed, 13 Oct 2010, Jason Heeris wrote:
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
On 13 October 2010 06:35, Jordan Metzmeier titan8...@gmail.com wrote:
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
-BEGIN PGP SIGNED MESSAGE-
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
On 14 October 2010 09:34, Jordan Metzmeier titan8...@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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/13/2010 09:57 PM, Jason Heeris wrote:
On 14 October 2010 09:34, Jordan Metzmeier titan8...@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
On 14 October 2010 11:52, Jordan Metzmeier titan8...@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,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 10/14/2010 12:32 AM, Jason Heeris wrote:
On 14 October 2010 11:52, Jordan Metzmeier titan8...@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
On 14 October 2010 12:52, Jordan Metzmeier titan8...@gmail.com wrote:
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
On 12 October 2010 10:59, Jason Heeris jason.hee...@gmail.com wrote:
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
Jason Heeris jason.hee...@gmail.com writes:
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
On 11 October 2010 23:44, Jochen Schulz m...@well-adjusted.de wrote:
[ 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
[please keep this on the list]
Jason Heeris jason.hee...@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
On 12 October 2010 15:59, Timo Juhani Lindfors timo.lindf...@iki.fi wrote:
Jason Heeris jason.hee...@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:
Jason Heeris jason.hee...@gmail.com writes:
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
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
On 10 October 2010 21:43, Jochen Schulz m...@well-adjusted.de wrote:
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
On 11 October 2010 03:03, Jochen Schulz m...@well-adjusted.de wrote:
Any tips on catching it? Will there be useful info in a log somewhere?
It *could* have made it to /var/log/syslog, but I am not particularly
optimistic about that.
No, I had checked that already. :/
May be. Do you have
On Sun, 10 Oct 2010, Jason Heeris wrote:
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.
On 11 October 2010 18:36, Henrique de Moraes Holschuh h...@debian.org wrote:
On Sun, 10 Oct 2010, Jason Heeris wrote:
t 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
On 10/11/2010 09:59 PM, Jason Heeris wrote:
On 11 October 2010 18:36, Henrique de Moraes Holschuhh...@debian.org wrote:
[snip]
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
2010/10/12 Ron Johnson ron.l.john...@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
compiled right in?). But this might be a good opportunity to find
On 10/11/2010 10:11 PM, Jason Heeris wrote:
2010/10/12 Ron Johnsonron.l.john...@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.
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
RAM: 256MB
Swap: partitioned, about 236MB (just what the installer recommended)
Kernel: 2.6.32-5-486
Debian: Squeeze (from installer daily build, updated
30 matches
Mail list logo
