All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Neal <jneal@nks.net>
To: Matt Zimmerman <mdz@debian.org>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Marius Gedminas <mgedmin@b4net.lt>,
	256873-forwarded@bugs.debian.org
Subject: Re: [uml-devel] [mgedmin@b4net.lt: Bug#256873: user-mode-linux: fails to start (kernel panic)]
Date: Tue, 29 Jun 2004 19:55:51 -0400	[thread overview]
Message-ID: <40E20187.1050803@nks.net> (raw)
In-Reply-To: <20040629182711.GM5243@alcor.net>

Matt Zimmerman wrote:

>I am receiving many reports from my users that 2.4.26-1um is less functional
>than past versions, especially (but not exclusively) where hostfs is
>concerned.  Are others experiencing problems as well?  I am considering
>reverting the Debian packages to 2.4.24-1um, which was the last version
>which was stable for me (it had only one frustrating hostfs bug, where
>readdir() would read forever).
>  
>
Yeah, I upgraded about a hundred (non-critical) UMLs to a straight 
2.4.26-1um kernel about a two weeks ago, and immediately started getting 
2-3 crashes (like the one below) per hour.   When backups kicked off, 
they pretty much all went down at the same time.  (Unfortunately, I 
hadn't added automatic backtracing to the UMLazi codebase yet, so I 
didn't get backtraces.)

I ended up going with a 2.4.26 kernel, with the 2.4.24-1um UML patch, 
and http://vs165141.v.sectoor.de/uml-2.4.26-cmpxchg.patch . This 
combination is running over 600 UMLs for 8 days without a crash.

-James

>----- Forwarded message from Marius Gedminas <mgedmin@b4net.lt> -----
>
>  [...]
>  Checking that ptrace can change system call numbers...OK
>  openpty failed to allocate a pty
>  openpty failed to allocate a pty
>  POSIX conformance testing by UNIFIX
>  process 553 exited with status 0
>  Kernel panic: wait_for_stop failed to wait for 553 to stop with 19
>
>  In idle task - not syncing
>   <6>SysRq : Show Regs
>
>  Kernel panic: Segfault with no mm
>  In idle task - not syncing
>   <6>SysRq : Show Regs
>
>  EIP: 0023:[<a015f2e5>] CPU: 0 Not tainted ESP: 002b:a121feb4 EFLAGS: 00010202
>      Not tainted
>  EAX: 00000000 EBX: a02adee0 ECX: 00000001 EDX: a121c274
>  ESI: 00000070 EDI: 00000007 EBP: a121fecc DS: 002b ES: 002b
>  Call Trace: [<a016ecd0>] [<a015589f>] [<a0023b2d>] [<a0014c08>] [<a0154b0b>]
>     [<a0264a67>] [<a0201c44>] [<a0152503>] [<a0154f65>] [<a015f2e5>] [<a0159241>]
>     [<a0155062>] [<a0201b58>] [<a015f2e5>] [<a015f2c7>] [<a0263345>] [<a016ed6a>]
>     [<a016ecd0>] [<a015589f>] [<a0023b2d>] [<a0014c08>] [<a0155e6f>] [<a02814c0>]
>     [<a014f3cb>] [<a014f360>] [<a021a49a>]
>
>The process ID (553) seems to vary, but the other numbers stay constant,
>at a glance.
>
>----- End forwarded message -----
>
>  
>



-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2004-06-29 23:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 18:27 [uml-devel] [mgedmin@b4net.lt: Bug#256873: user-mode-linux: fails to start (kernel panic)] Matt Zimmerman
2004-06-29 19:06 ` BlaisorBlade
2004-06-29 20:34 ` Stefan Gybas
2004-06-29 23:55 ` James Neal [this message]
2004-06-30  7:56   ` Paul Wagland
2004-06-30 18:38     ` BlaisorBlade
2004-07-01 21:02       ` Paul Wagland
2004-07-03 17:21         ` BlaisorBlade

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40E20187.1050803@nks.net \
    --to=jneal@nks.net \
    --cc=256873-forwarded@bugs.debian.org \
    --cc=mdz@debian.org \
    --cc=mgedmin@b4net.lt \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.