| Subject | Re: [patch 07/21] Cleanup sclp printk messages. | From | Martin Schwidefsky <> | Date | Thu, 26 Jun 2008 09:26:16 +0200 |
| |
On Wed, 2008-06-25 at 17:15 +0200, Bastian Blank wrote: > On Wed, Jun 25, 2008 at 04:35:06PM +0200, Martin Schwidefsky wrote: > > + if (finished_sccb != (u32) (addr_t) sclp_init_sccb) > > + panic("sclp: unsolicited interrupt for buffer at 0x%x\n", > > + finished_sccb); > > Does that really need to be a panic?
Yes, that should be a panic. The point is that we got an unsolicited interrupt from sclp at boot time. That means that there has been an sclp request around from the last incarnation of the system. An sclp request can do a lot of things, in particular it can change memory. Not a good start for the new system ..
-- blue skies, Martin.
"Reality continues to ruin my life." - Calvin.
|