[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#357065: marked as done (linux-image-2.6-r4k-ip22 immediately reboots on Indy 200MHz R4400)

Your message dated Fri, 14 Nov 2008 18:56:38 +0100
with message-id <20081114175638.GB22909@inutil.org>
and subject line Re: Bug#357065: linux-image-2.6-r4k-ip22 immediately reboots on Indy  200MHz R4400
has caused the Debian Bug report #357065,
regarding linux-image-2.6-r4k-ip22 immediately reboots on Indy 200MHz R4400
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.)


-- 
357065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=357065
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: linux-image-2.6-r4k-ip22
Version: 2.6.12-3

When I boot the kernel image from linux-image-2.6-r4k-ip22, the kernel boots
and after a number of lines (but before trying to mount the root fs) resets
the Indy (R4400/200, XL24 graphics, using graphical console).

Is this an already known fact? Should I report bugs for packages in
experimental? What extra information should I provide? I could hook up the
Indy to another computer and (after switching to serial console) log the
exact boot messages I get, would that help?

Ciao,
Thomas Jahns
-- 
"Computers are good at following instructions,
 but not at reading your mind."
D. E. Knuth, The TeXbook, Addison-Wesley1984, 1986, 1996, p. 9

--- End Message ---
--- Begin Message --- 
On Fri, Nov 14, 2008 at 11:35:11AM +0100, Thomas Jahns wrote:
> On 2008-11-14 01:16:25 +0100 Moritz Muehlenhoff <jmm@inutil.org> wrote:
> >On Mon, Mar 27, 2006 at 07:02:16PM +0200, Thomas Jahns wrote:
> >>On 2006-03-27 18:15, Frans Pop wrote:
> >>>On Monday 27 March 2006 16:58, Thomas Jahns wrote:
> >>>>Please comment. But with non-working PS/2 keyboard and non-working
> >>>>/etc/fstab for both kernel version, the 2.6.16 image is pretty
> >>>>worthless to me at this moment.
> >>>
> >>>You could try using the rescue mode [1] of the Etch Beta 2 release 
> >>>[2] of 
> >>>Debian Installer to correct your /etc/fstab.
> >>
> >>I'm not too keen on constantly swapping two incompatible versions of 
> >>/etc/fstab. And since I expect it'll take some time before all 
> >>drivers 
> >>which are working in 2.4.27 also do in 2.6 that would be necessary 
> >>for  too 
> >>long to be practical.
> >
> >Does this error still occur with more recent kernel versions?
> 
> Unfortunately I can't tell: after learning that there were no plans to 
> revert the new method of enumerating partitions, I decided to simply 
> edit the partition table such that both schemes  result in the same 
> numbering so I get consistent partition names.

Closing the bug, then (which is ancient anyway).

Cheers,
        Moritz

--- End Message ---
Reply to: