Re: [parisc-linux] 715/33]

Re: [parisc-linux] 715/33]

[Alex deVries]

Matthew Wilcox wrote:

> Linux version 2.2.1 (willy@bmw) (gcc version egcs-2.91.60 19981201 (egcs-1.1.1
> release)) #18
>  Wed Jun 30 05:46:53 METDST 1999
> 
> at which point it hangs and I have to reset.  Excellent work.

Well, not a bad start, but what worries me is that this boot sequence
should really go on a bit more.  I'm not quite sure where the problem
is, it might be with some PDC calls we do within setup_arch().

I'll upload a binary of the kernel that I know works on my A class.  I'd
appreciate it if people could email tests of this on different machines.


- Alex
-- 
Alex deVries
Vice President of Engineering
The Puffin Group

Re: [parisc-linux] 715/33]

[Matthew Wilcox]

On Tue, Jun 29, 1999 at 10:31:09PM -0400, Alex deVries wrote:
> 
> Matthew Wilcox wrote:
> 
> > Linux version 2.2.1 (willy@bmw) (gcc version egcs-2.91.60 19981201 (egcs-1.1.1
> > release)) #18
> >  Wed Jun 30 05:46:53 METDST 1999
> > 
> > at which point it hangs and I have to reset.  Excellent work.
> 
> Well, not a bad start, but what worries me is that this boot sequence
> should really go on a bit more.  I'm not quite sure where the problem
> is, it might be with some PDC calls we do within setup_arch().

It fails before it gets that far (what a joy it is to have a working
printk..):

in arch/parisc/kernel/setup.c
__initfunc(void setup_arch(char **cmdline_p,
        unsigned long * memory_start_p, unsigned long * memory_end_p))
{
        char cpuinfo_text[2000];
printk("setup_arch(%p, %p, %p)\n", cmdline_p, memory_start_p, memory_end_p);
printk("-3\n");
printk("%p\n", *cmdline_p);
printk("%s\n", *cmdline_p);
        strcpy(*cmdline_p,saved_command_line);  // copy the command-line
printk("-2\n");

I get the following printout:

setup_arch(000a0860, 000767e0, 000767e4)
-3
f000013c
 zC

and there it hangs.

> I'll upload a binary of the kernel that I know works on my A class.  I'd
> appreciate it if people could email tests of this on different machines.

When you put it up, I'll happily test it; maybe my kernel is larger than
yours and is causing something to be overwritten?

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

Re: [parisc-linux] 715/33]

[Alan Cox]

> printk("-3\n");
> printk("%p\n", *cmdline_p);
> printk("%s\n", *cmdline_p);
>         strcpy(*cmdline_p,saved_command_line);  // copy the command-line
> printk("-2\n");
> 
> I get the following printout:
> 
> setup_arch(000a0860, 000767e0, 000767e4)
> -3
> f000013c
>  zC

f000013c is in I/O space. Is the command line really meant to point into
I/O space..

Re: [parisc-linux] 715/33]

[Matthew Wilcox]

On Wed, Jun 30, 1999 at 03:55:53PM +0200, Helge Deller wrote:
> Alan Cox wrote:
> 
> > > printk("-3\n");
> > > printk("%p\n", *cmdline_p);
> > > printk("%s\n", *cmdline_p);
> > >         strcpy(*cmdline_p,saved_command_line);  // copy the command-line
> > > printk("-2\n");
> > >
> > > I get the following printout:
> > >
> > > setup_arch(000a0860, 000767e0, 000767e4)
> > > -3
> > > f000013c
> > >  zC
> >
> > f000013c is in I/O space. Is the command line really meant to point into
> > I/O space..
> 
> It was completely wrong to use strcpy() !
> Sorry, my fault !!!!!
> It is now corrected in CVS.

So it is.  Thank you very much.

Has the price of beef gone up?
[if you've not booted the kernel, there's no way you'll understand this :-)]

-- 
Matthew Wilcox <willy@bofh.ai>
"Windows and MacOS are products, contrived by engineers in the service of
specific companies. Unix, by contrast, is not so much a product as it is a
painstakingly compiled oral history of the hacker subculture." - N Stephenson

Re: [parisc-linux] 715/33]

[Philipp Rumpf]

> Has the price of beef gone up?
> [if you've not booted the kernel, there's no way you'll understand this :-)]
you could, of course, read the source code as well ...