* block after "io scheduler noop registered"
@ 2006-06-28 14:48 morelli.gab
2006-06-28 17:48 ` Vitaly Bordug
0 siblings, 1 reply; 2+ messages in thread
From: morelli.gab @ 2006-06-28 14:48 UTC (permalink / raw)
To: linuxppc-embedded
Hi All,
i,m upgrading the linux kernel 2.4 from 2.6, during the phase of restart =
on my card the system blocks on message "io scheduler noop registered".
the board mount MPC875 processor
...
Serial: CPM driver $Revision: 0.01 $
ttyCPM0 at MMIO 0xf0000a80 (irq =3D 20) is a CPM UART
ttyCPM1 at MMIO 0xf0000a90 (irq =3D 19) is a CPM UART
io scheduler noop registered
Thanks,
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: block after "io scheduler noop registered"
2006-06-28 14:48 block after "io scheduler noop registered" morelli.gab
@ 2006-06-28 17:48 ` Vitaly Bordug
0 siblings, 0 replies; 2+ messages in thread
From: Vitaly Bordug @ 2006-06-28 17:48 UTC (permalink / raw)
To: linuxppc-embedded
On Wed, 28 Jun 2006 16:48:34 +0200
"morelli.gab" <morelli.gab@libero.it> wrote:
> Hi All,
>
> i,m upgrading the linux kernel 2.4 from 2.6, during the phase of restart on my card the system blocks on message "io scheduler noop registered".
> the board mount MPC875 processor
>
>
> ...
> Serial: CPM driver $Revision: 0.01 $
> ttyCPM0 at MMIO 0xf0000a80 (irq = 20) is a CPM UART
> ttyCPM1 at MMIO 0xf0000a90 (irq = 19) is a CPM UART
> io scheduler noop registered
You should add the proper cpm uart initialization bits to the board-specific code, as say 885ads does (ppc/platforms/mpc885ads_setup.c).
What experienced is uart misconfiguration which alters pins in a way the console doesn't like very much.
--
Sincerely,
Vitaly
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2006-06-28 17:48 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-06-28 14:48 block after "io scheduler noop registered" morelli.gab
2006-06-28 17:48 ` Vitaly Bordug
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox