On Wed, May 12, 2010 at 07:51:52PM +0200, maximilian attems wrote: > On Wed, May 12, 2010 at 05:32:49PM +0200, Jan Hauke Rahm wrote: > > On Wed, May 12, 2010 at 04:50:10PM +0200, maximilian attems wrote: > > > severity 581353 important > > > tags 581353 moreinfo > > > stop > > > > > > On Wed, May 12, 2010 at 11:55:42AM +0200, Jan Hauke Rahm wrote: > > > > Package: linux-2.6 > > > > Version: 2.6.32-9 > > > > Severity: grave > > > > > > very outdated, please try to reproduce with uptodate 2.6.32-12. > > > thanks > > > > Please read my bug report. I can't boot 2.6.32-12. > > Thanks > > > > http://bugs.debian.org/580894#29 > > how should I know that this is related? > please don't assume that the matrix of d-kernel bug reports are linked > and mapped on top of my head, thanks. Max, seriously? I really don't wanna smart-ass around here but quoting from the bug report you replied to: ,---- | Attached is what seems to be the appropriate part from kern.log. I would | run a newer kernel if it didn't fail to boot for me [1]. Any help is | welcome. If I can help, say so. --- snip --- | [1] http://bugs.debian.org/580894#29 `---- There is nothing related. I reported a bug on 2.6.32-9 because it happened there. I can't run a newer kernel, i.e. 2.6.32-12, because it wouldn't boot. I actually only reported the problem in 2.6.32-9 since it's possible that it still exists in -12 which I can't test. > anyway did you try to blacklist nouveau for now? Wouldn't help. Well, at least I now know that -12 failing to boot is not related to #580894. Do you want another bug report for that? I can tell you up front that I don't really have infos about that boot failure. kern.log doesn't contain anything about it. :-/ Hauke -- .''`. Jan Hauke Rahm <jhr@debian.org> www.jhr-online.de : :' : Debian Developer www.debian.org `. `'` Member of the Linux Foundation www.linux.com `- Fellow of the Free Software Foundation Europe www.fsfe.org
Attachment:
signature.asc
Description: Digital signature