Re: Unable to boot Kernel 2.6.10
I got to boot.
I erased my modprobe.conf and modprobe.d as well as my modules.conf and
modutils, then removed modconf and modutils and reinstalled them as well as
installed udev.
I have now no problem
Thanks for the different tips
Xavier
Le Mardi 25 Janvier 2005 19:37, Leoncini Xavier a écrit :
> I guess it's my fault I was toolazy to copy the error message
> and retype it. I was hoping it was a more common problem.
> My computer is a laptop with an athlon 3000+
> I use a precompiled debian kernel, and installed debian pure 64
> on it last june and been upgrading regularly ever since.
>
> The error message is:
> Pid: 2065, comm setserial Tainted: G M 2.6.10-9-amd64-k8
> RIP 0010 with garbage
> RSP: 0018:.......
> RAX: etc..
> Process setserial (pid: 2065, threadinfo ......)
> Stack: fffff
> Call trace
> [n_tty_flush_buffer+9}
> etc..
> last message
> Code: Bad RIP value
> RIP [<ffffffffff...] RSP ...
> CR2: ...
> /etc/rcS.d/S46setserial: line 152: 2065 killed ¤{SETSERIAL} -z $device
> $args Then if I type ctrl C I lose allability to do anything
> with another Bad RIP value and some kthread thread return worker_thread
> message in the CallTrace message
> I use also the cpudyn daemon when I can boot.
>
> Well I hope it helps
>
> PS: I have been using Debian since late 96, and its the first time I get
> such a silly answer
> Best
> Xavier Leoncini
>
> Le Mardi 25 Janvier 2005 19:17, Alvaro Hernandez a écrit :
> > Tue, Jan 25, 2005 at 07:10:07PM +0100, Egon Willighagen escribió:
> > >On Tuesday 25 January 2005 17:22, Alvaro Hernandez wrote:
> > >> Tue, Jan 25, 2005 at 05:01:53PM +0100, Leoncini Xavier wrote:
> > >> >I have a problem while booting 2.6.10
> > >
> > ><snip>
> > >
> > >> ;)) Take it with a grain of salt!
> > >
> > >Yes, sure. Ok, I've encountered boot problems too in the past, but don't
> > >really care about them.
> > >
> > >It might be more helpful if people would not make fun of Leonici, but
> > > tell him where to find information on how to debug the problems he has
> > > ?
> >
> > Nobody is making fun of anyone, just joking. Anyway, it is very
> > difficult to tell someone how to debug a problem he hasn't provided no
> > information about it.
> >
> > There is need, first, to know what is going on, what the error
> > messages are, software versions, etc.
> >
> > Do you go to doctor and say "it hurts, doctor, help me"? Or do
> > you provide information to help doctor start asking questions?
> >
> > Regards,
> >
> > Alvaro
Reply to: