This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-bugs] [Bug 672] calling printk early enough kills dom0 boot on x86-

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 672] calling printk early enough kills dom0 boot on x86-64
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 12 Apr 2007 08:38:55 -0700
Delivery-date: Thu, 12 Apr 2007 08:39:27 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <bug-672-3@xxxxxxxxxxxxxxxxxxxxxxxxxxx/bugzilla/>
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

henning_sprang@xxxxxx changed:

           What    |Removed                     |Added
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX

------- Comment #1 from henning_sprang@xxxxxx  2007-04-12 08:38 -------
I'm closing this bug in the course of bugzilla 2007 spring cleaning.
No patch has been attached, and no developer has dealt with it since months,
so I'm closing it as "wontfix" which matches this fact best.
Please reopen this bug if it still exists in current Xen versions, and is
important to you - sorry for the inconvenience in that case.
We are hoping to get a cleaner bugzilla, so in the future we can send out
reminders for unhandled
bugs and take better care no reports are being forgotten.
But therefore, the bug database must be cleaned of old and forgotten bugs,

In this specific case, the reason for nobody working on this is, that it's not
exactly clear what the consequences are so it's unclear to decide the
importance of this bugs and who should handle it - so you might add this
information when reopening it.

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-bugs] [Bug 672] calling printk early enough kills dom0 boot on x86-64, bugzilla-daemon <=