Bug#547129: marked as done (Debian testig: real unstable system)
Your message dated Sat, 13 Feb 2010 13:01:09 +0100
with message-id <20100213120109.GN2821@stro.at>
and subject line Re: Bug#547129: Debian testig: real unstable system
has caused the Debian Bug report #547129,
regarding Debian testig: real unstable system
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
547129: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=547129
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Debian testig: real unstable system
- From: dAgeCKo <dagecko@free.fr>
- Date: Thu, 17 Sep 2009 08:37:19 +0200
- Message-id: <1253169439.4ab1d91f068df@imp.free.fr>
Package: kernel
Version: 2.6.30-1-686
Gravity: CRITICAL
Real unstable system on my computer on debian testing.
Boot almost never finishes and complains about kernel panics, udev
issues.
Boot can ends but system can hangs afterward.
Udev and kernel broke most of the time just as bttv driver.
(I'll also make a bug report about udev).
Can't retreive logs since boot does not finish and boot log are lost
in the next mount.
Computer:
Debian testing squeeze
AMD Athlon 3000+
1GB RAM
Nvidia Geforce 7600
Asrock motherboard with SIS chips
--- End Message ---
--- Begin Message ---
- To: 547129-done@bugs.debian.org
- Subject: Re: Bug#547129: Debian testig: real unstable system
- From: maximilian attems <max@stro.at>
- Date: Sat, 13 Feb 2010 13:01:09 +0100
- Message-id: <20100213120109.GN2821@stro.at>
- In-reply-to: <1253309247.3415.9.camel@localhost>
- References: <1253169439.4ab1d91f068df@imp.free.fr> <1253309247.3415.9.camel@localhost>
closing as no follow up since and no hint of linux-2.6 bug.
thanks for your report.
--- End Message ---
Reply to: