New kernel on 720 + Pa-Linux-0.5: Breakpoint ?

parisc-linux Christoph Plattner 6 participants 20 messages Apr 2, 2001 – Apr 10, 2001

lore

Share & tools

lore

Christoph Plattner

author

2001-04-02 22:51 UTC #0 lore raw

What this in the new kernel ?
A manually inserted breakpoint ?

Have I to do something in the code to remove ?

Output:

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0. Looking up port of RPC 100003/2 on 196.1.1.20 Looking up port of RPC 100005/2 on 196.1.1.20
VFS: Mounted root (nfs filesystem) readonly. break 0,0: pid=9 command='init'
init[9]: Breakpoint 0

YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001111

r0-3     00000000 102de010 00000000 00000000
r4-7     00000000 00000000 00000000 00000000
r8-11    00000000 00000000 00000000 00000000
r12-15   00000000 00000000 00000040 10125434
r16-19   13f1c5c0 13f1c000 00000004 00000001
r20-23   102efcc0 102efcc0 10022760 102efcc0
r24-27   0000002e 00001000 00000000 1024c010
r28-31   00000000 00000000 13f1c9c0 10131288
sr0-3    00000000 00000000 00000000 00000001
sr4-7    00000000 00000000 00000000 00000000

IASQ: 00000000 00000000 IAOQ: 00000000 00000004
IIR: 00000000 ISR: 00000000 IOR: 00000000
ORIG_R28: 00000000

On a kernel a month ago everthing was ok.
Now the SCSI problem and system does not boot correctly !

Log below.

With friendly regards
Christoph P.

Soft booted.
palo ipl [email protected] Tue Apr 3 00:25:26 CEST 2001 0/vmlinux 2491775 bytes @ 0x6800
0/palo-cmdline '0/vmlinux HOME=/ TERM=vt100 root=/dev/nfs console=ttyS0'
Kernel: partition 0 file /vmlinux
ELF32 executable
Entry 00100170 first 00100000 n 5
Segment 0 load 00100000 size 1351880 mediaptr 0x1000
Segment 1 load 0024c000 size 175952 mediaptr 0x14c000 Segment 2 load 00278000 size 230488 mediaptr 0x177000 Segment 3 load 002b4000 size 8192 mediaptr 0x1b0000
Segment 4 load 002de188 size 69024 mediaptr 0x1b2188 branching to kernel entry point 0x00100170
PDC Console Initialized
Linux version 2.4.0 ([email protected]) (gcc version 3.0 20010315 (prerelease)) #2 Tue Apr 3 00:28:20 CEST 2001
FP[0] enabled: Rev 3 Model 0
The 32-bit Kernel has started...
Determining PDC firmware type: Older Legacy Box setup_cmdline(0x64cc4,0x64cc4,0x0,0x0)
PALO command line: 'HOME=/ TERM=vt100 root=/dev/nfs console=ttyS0' PALO initrd 0-0
model 00002000 00000481 00000000 00000000 0234072e 000011f4 00000004
0000000d 00000000

vers    00000003
CPUID   vers 0 rev 0
model   9000/720

Total Memory: 64 Mb
initrd: 00000000-00000000
pagetable_init
On node 0 totalpages: 16384
zone(0): 16384 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Searching for devices...
Found devices:
1. Coral SGC Graphics (10) at 0xf8000000, versions 0x4, 0x0, 0x77, 0x0, 0x0
2. Cobra Core BA (11) at 0xf082f000, versions 0x4, 0x0, 0x70, 0x0, 0x0
3. Cobra Core SCSI (10) at 0xf0825000, versions 0x4, 0x0, 0x71, 0x0, 0x0
4. Cobra Core LAN (802.3) (10) at 0xf0826000, versions 0x4, 0x0, 0x72, 0x0, 0x0
5. Cobra Core HIL (10) at 0xf0821000, versions 0x4, 0x0, 0x73, 0x0, 0x0
6. Cobra Core RS-232 (10) at 0xf0823000, versions 0x4, 0x0, 0x75, 0x0, 0x0
7. Cobra Core RS-232 (10) at 0xf0822000, versions 0x4, 0x0, 0x75, 0x0, 0x0
8. Cobra Core Centronics (10) at 0xf0824000, versions 0x4, 0x0, 0x74, 0x0, 0x0
9. Cobra (720) (0) at 0xfffbe000, versions 0x200, 0x0, 0x4, 0x0, 0x81
10. Cobra (1) at 0xfffbf000, versions 0x13, 0x0, 0x9, 0x0, 0x0 That's a total of 10 devices.
CPU(s): 1 x PA7000 (PCX-S) at 50.000000 MHz
Kernel command line: HOME=/ TERM=vt100 root=/dev/nfs console=ttyS0 Error reading tod clock
Calibrating delay loop... 49.76 BogoMIPS
Memory: 62396k available
Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) POSIX conformance testing by UNIFIX
ASP version 1 at 0xf0800000 found.
LED (ASP-style) display at f0800020 registered
Found i82596 at 0xf0826000, IRQ 87
early initialization of device eth0 is deferred
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039 Starting kswapd v1.8
pty: 256 Unix98 ptys configured request_module[parport_lowlevel]: Root fs not mounted
lp: driver loaded but no devices found
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize 82596.c: MAC of HP700 LAN blindely read from the prom!
eth0: Couldn't get consistent shared memory
eth0: 82596 at 0xf0826000, 08 00 09 24 64 06 IRQ 87.
82596.c $Revision: 1.15 $
Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI enabled
ttyS00 at iomem 0xf0823800 (irq = 90) is a 16550A
ttyS01 at iomem 0xf0822800 (irq = 89) is a 16550A
Generic RTC Driver v1.02 05/27/1999 Sam Creasey ([email protected])
parport_init_chip: enhanced parport-modes not supported.
parport0: PC-style at 0xf0824800, irq 88 [PCSPP]
lp0: using parport0 (interrupt-driven).
SCSI subsystem driver Revision: 1.00
sim700: Couldn't get consistent shared memory
sim700: Configuring 53c700 (SCSI-ID 7) at f0825100, IRQ 86, options 1
scsi0: Revision 0x0
Post test1, istat 05, sstat0 00, dstat 84
sim700: WARNING IRQ probe failed, (returned 0)
scsi0: WARNING: target data areas are not dma coherent!
scsi0: test 1 completed ok.
scsi0 : LASI/Simple 53c7xx
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID0
scsi0: Unable to send Bus Device Reset for target 0
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID1
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID1
scsi0: Unable to send Bus Device Reset for target 1
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID1
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID2
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID2
scsi0: Unable to send Bus Device Reset for target 2
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID2
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID3
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID3
scsi0: Unable to send Bus Device Reset for target 3
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID3
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID4
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID4
scsi0: Unable to send Bus Device Reset for target 4
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID4
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID5
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID5
scsi0: Unable to send Bus Device Reset for target 5
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID5
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID6
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID6
scsi0: Unable to send Bus Device Reset for target 6
scsi0: Unable to do SCSI bus reset
scsi0: >>>>>>>>>>>> Host reset <<<<<<<<<<<<
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Bad dsp on abort, 0x00057458, offset 0x41858
scsi0: Failed to handle interrupt. Failing commands and resetting SCSI bus and chip
scsi0: istat = 04, sstat0 = 00, sstat1 = 00, dstat = 00
scsi0: dsp = 00057458 (script[0x1d16]), dsps = 00057468, target = 0
scsi0: Failing command for ID6
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 4096 bind 8192)
eth0: link ok.
Sending BOOTP requests.... OK
IP-Config: Got BOOTP answer from 196.1.1.20, my address is 196.1.1.110
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
Looking up port of RPC 100003/2 on 196.1.1.20
Looking up port of RPC 100005/2 on 196.1.1.20
VFS: Mounted root (nfs filesystem) readonly.
break 0,0: pid=9 command='init'
init[9]: Breakpoint 0

YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001111

r0-3     00000000 102de010 00000000 00000000
r4-7     00000000 00000000 00000000 00000000
r8-11    00000000 00000000 00000000 00000000
r12-15   00000000 00000000 00000040 10125434
r16-19   13f1c5c0 13f1c000 00000004 00000001
r20-23   102efcc0 102efcc0 10022760 102efcc0
r24-27   0000002e 00001000 00000000 1024c010
r28-31   00000000 00000000 13f1c9c0 10131288
sr0-3    00000000 00000000 00000000 00000001
sr4-7    00000000 00000000 00000000 00000000

IASQ: 00000000 00000000 IAOQ: 00000000 00000004
IIR: 00000000 ISR: 00000000 IOR: 00000000
ORIG_R28: 00000000

Signature · 3 lines

-------------------------------------------------------------------------
private:	[email protected]
company:	[email protected]

Richard Hirst

2001-04-02 23:18 UTC #1 lore raw

Quoted 2 lines · Christoph Plattner

What this in the new kernel ?
A manually inserted breakpoint ?

No, you need new user space stuff. It looks like there will be a new base tarball Real Soon Now, so it might be easiest to wait a few days for that. Alternatively you could try the file system at

http://mkhppa1.esiee.fr/en/download.html

which is pretty up to date - havn't tried that myself though.

Richard

Matthew Wilcox

2001-04-02 23:27 UTC #2 lore raw

Quoted 5 lines · Richard Hirst

Quoted 2 lines · Christoph Plattner
What this in the new kernel ?
A manually inserted breakpoint ?
No, you need new user space stuff. It looks like there will be a

Why do you say that? From:

sr0-3 00000000 00000000 00000000 00000001
sr4-7 00000000 00000000 00000000 00000000

IASQ: 00000000 00000000 IAOQ: 00000000 00000004

it looks like it's a kernel null pointer dereference.

Quoted 7 lines

new base tarball Real Soon Now, so it might be easiest to wait a few days for that. Alternatively you could try the file system at
http://mkhppa1.esiee.fr/en/download.html
which is pretty up to date - havn't tried that myself though.

Works well for me. Though as you say there's a new nfsroot out RSN.

Signature · 1 line

Revolutions do not require corporate support.

Richard Hirst

2001-04-02 23:41 UTC #3 lore raw

Quoted 7 lines · Matthew Wilcox

Quoted 5 lines · Richard Hirst
Quoted 2 lines · Christoph Plattner
What this in the new kernel ?
A manually inserted breakpoint ?
No, you need new user space stuff. It looks like there will be a

Quoted 8 lines

Why do you say that? From:
sr0-3 00000000 00000000 00000000 00000001
sr4-7 00000000 00000000 00000000 00000000
IASQ: 00000000 00000000 IAOQ: 00000000 00000004
it looks like it's a kernel null pointer dereference.

You might well be right; it just reminded me of one of the problems I saw on my 715/old with bad spinlock alignment.

Quoted 9 lines

Quoted 7 lines
new base tarball Real Soon Now, so it might be easiest to wait a few days for that. Alternatively you could try the file system at
http://mkhppa1.esiee.fr/en/download.html
which is pretty up to date - havn't tried that myself though.
Works well for me. Though as you say there's a new nfsroot out RSN.

OK, I'm not sure when that was produced relative to my latest glibc spinlock alignment fix though.

Richard

Christoph Plattner

2001-04-03 06:56 UTC #4 lore raw

In reply to Richard Hirst

With the file system of ESIEE, I always have the problem, that my machine hangs, before init does any output !

I also have selfmade stuff, I will see, what will run on that machine.

Thanks for your prompt answer.

With friendly regards
Christoph Plattner

Quoted 12 lines · Richard Hirst

Quoted 2 lines · Christoph Plattner
What this in the new kernel ?
A manually inserted breakpoint ?
No, you need new user space stuff. It looks like there will be a new base tarball Real Soon Now, so it might be easiest to wait a few days for that. Alternatively you could try the file system at
http://mkhppa1.esiee.fr/en/download.html

Quoted 8 lines

which is pretty up to date - havn't tried that myself though.
Richard
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux

-----------------------------------------------------------------

private:        [email protected]
company:        [email protected]

Richard Hirst

2001-04-03 09:13 UTC #5 lore raw

Quoted 2 lines · Christoph Plattner

With the file system of ESIEE, I always have the problem, that my machine hangs, before init does any output !

Have you tried using init=/bin/sash? You may have to build your own sash, from userspace/sash on pehc cvs.

Richard

Christoph Plattner

2001-04-03 09:24 UTC #6 lore raw

Hello,

Quoted 7 lines · Richard Hirst

Quoted 2 lines · Christoph Plattner
With the file system of ESIEE, I always have the problem, that my machine hangs, before init does any output !
Have you tried using init=/bin/sash? You may have to build your own sash, from userspace/sash on pehc cvs.

No. I built up my own bash (it was statically linked by accident). I never used sash.

Cheers
Christoph P.

Quoted 7 lines

Richard
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux

Signature · 4 lines

  +--------V--------+	[email protected]
  |  A L C A T E L  |	-----------------------------
  +-----------------+	Phone: +43 1 27722 3706	
         T A S		Fax:   +43 1 27722 3955

Richard Hirst

2001-04-03 13:16 UTC #7 lore raw

Quoted 5 lines · Christoph Plattner

Hello,
Quoted 2 lines · Richard Hirst
On Tue, Apr 03, 2001 at 08:55:15AM +0200, Christoph Plattner wrote:

Quoted 8 lines

Quoted 5 lines
Quoted 2 lines
With the file system of ESIEE, I always have the problem, that my machine hangs, before init does any output !
Have you tried using init=/bin/sash? You may have to build your own sash, from userspace/sash on pehc cvs.
No. I built up my own bash (it was statically linked by accident). I never used sash.

You should try sash. It will make less demands on your system, and might show us something useful.

Richard

Matthew Wilcox

2001-04-03 21:34 UTC #8 lore raw

In reply to Christoph Plattner

Quoted 5 lines · Christoph Plattner

With the file system of ESIEE, I always have the problem, that my machine hangs, before init does any output !
I also have selfmade stuff, I will see, what will run on that machine.

have you looked at all the followups to the esiee announcement noting the problems with it? i suspect it's switching to STI console.

Signature · 1 line

Revolutions do not require corporate support.

Christoph Plattner

2001-04-04 07:08 UTC #9 lore raw

Hello,

Quoted 10 lines · Matthew Wilcox

Quoted 5 lines · Christoph Plattner
With the file system of ESIEE, I always have the problem, that my machine hangs, before init does any output !
I also have selfmade stuff, I will see, what will run on that machine.
have you looked at all the followups to the esiee announcement noting the problems with it? i suspect it's switching to STI console.

Although I definitely write

console=ttyS0

as kernel parameter ?

Cheers
Christoph P.

Quoted 3 lines

--
Revolutions do not require corporate support.

Signature · 4 lines

  +--------V--------+	[email protected]
  |  A L C A T E L  |	-----------------------------
  +-----------------+	Phone: +43 1 27722 3706	
         T A S		Fax:   +43 1 27722 3955

Matthew Wilcox

2001-04-04 17:05 UTC #10 lore raw

Quoted 8 lines · Christoph Plattner

Quoted 2 lines
have you looked at all the followups to the esiee announcement noting the problems with it? i suspect it's switching to STI console.
Although I definitely write
console=ttyS0
as kernel parameter ?

yes. they symlinked /dev/console to tty0 instead of leaving it as a char device. the kernel can't help you out here, you have to change that symlink :-(

Signature · 1 line

Revolutions do not require corporate support.

Christoph Plattner

author

2001-04-04 20:31 UTC #11 lore raw

Quoted 9 lines · Matthew Wilcox

Quoted 7 lines · Christoph Plattner
Quoted 2 lines
have you looked at all the followups to the esiee announcement noting the problems with it? i suspect it's switching to STI console.
Although I definitely write
console=ttyS0

Quoted 8 lines

Quoted 1 line
as kernel parameter ?
yes. they symlinked /dev/console to tty0 instead of leaving it as a char device. the kernel can't help you out here, you have to change that symlink :-(
--
Revolutions do not require corporate support.

No, No !

This problem have I fixed in my tree !
I tried it with both, the correct one

	/dev/console = 5,1
and the hack !
	/dev/console -> /dev/ttyS0

Further I hacked in a test in the kernel. Before it starts init' or any other process, it tries to open the console (You know, the warning, if this fail). After the open I write out a string using write (1, )' as check the return value. I see the string on the serial console !! and return value is ok.

So the device `/dev/console' IS WORKING in my setup, but the rest is not !!!....

Cheers
Christoph P.

Signature · 3 lines

-------------------------------------------------------------------------
private:	[email protected]
company:	[email protected]

Christoph Plattner

author

2001-04-08 17:08 UTC #12 lore raw

[parisc-linux] Many experience done on 720, but `init' fails !!

In reply to Matthew Wilcox

A week ago, I reported the problem booting PA-Linux 0.5 with the new kernel and new selfmade cross tool chain.

The last week I used to experience with cross toolchain setup. The aim was to find away having "one" glibc-2 for cross development and for the target (to mount, NFS-ROOT). I also used tricks like
--prefix=/usr and
make install install_root=/usr/parisc/target....
but the result and discussion with other showed following:

There must be TWO glibc trees, one for the cross toolchain, the other for the target. The second one is built with the method defining prefix to /usr and install it in a target tree.

SO I build sash, a also build a bash (shared and static !), I build fileutils, text-utils, shell-utils, etc, etc.....
The system boots with bash and I can mount, run programs, etc....

The I build "my own" startup stuff. A /sbin/init.d/xxx , etc/rc.d/xxx and so on. I also build a sysvinit-2.78 (and 2.77 before), but the `init'
has it's problems. The error message is:

VFS: Mounted root (nfs filesystem) readonly.
break 0,0: pid=9 command='init'
init[9]: Breakpoint 0

YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001111

r0-3     00000000 102de010 00000000 00000000
r4-7     00000000 00000000 00000000 00000000
r8-11    00000000 00000000 00000000 00000000
r12-15   00000000 00000000 00000040 1012544c
r16-19   13f085c0 13f08000 c804c804 00000001
r20-23   102efcc0 102efcc0 10022800 102efcc0
r24-27   0000002e 00001000 00000000 1024c010
r28-31   00000000 00000000 13f089c0 101312a0
sr0-3    00000000 00000000 00000000 00000001
sr4-7    00000000 00000000 00000000 00000000

IASQ: 00000000 00000000 IAOQ: 00000000 00000004
IIR: 00000000 ISR: 00000000 IOR: 00000000
ORIG_R28: 00000000

How can I follow up the thing ?
Is the GDB of the CVS usable (for example starting gdbserver init instead of init and `target remote' via the second serial interface ?)

By the way: I did a "super hack" in the kernel. In the serial interrupt routine, I catch the charcater ^\', filter it for /dev/ttyS0' and do a machine_restart(). This is perfect for development !!

With friendly regards
Christoph P.

Signature · 3 lines

-------------------------------------------------------------------------
private:	[email protected]
company:	[email protected]

Marc Eisenbarth

2001-04-08 17:33 UTC #13 lore raw

[parisc-linux] C180 Progress

What is the statis for a Linux install for an HP C180 Visualize? I tried to install
0.5, but it seems to hang and will not accept input from the keyboard after the cd
boots up.

Thanks,
-Marc

Matt Taggart

2001-04-09 13:34 UTC #14 lore raw

Re: [parisc-linux] C180 Progress

"Marc Eisenbarth" writes...

Quoted 3 lines

What is the statis for a Linux install for an HP C180 Visualize? I tried to install 0.5, but it seems to hang and will not accept input from the keyboard after the cd boots up.

IIRC, the C180 requires fixes that are not in the kernel on the 0.5 iso. Either build a new kernel(and boot from an nfsroot root), or wait for a new iso.

Signature · 2 lines

Matt Taggart        Linux Development Lab
[email protected]   HP Linux Systems Operation

Marc Eisenbarth

2001-04-09 17:06 UTC #15 lore raw

RE: [parisc-linux] C180 Progress

what is the status on the new iso? I do not have the resources to boot from a nfsroot =(

-Marc

-----Original Message-----
From: Matt Taggart [mailto:[email protected]]
Sent: Monday, April 09, 2001 8:37 AM
To: Marc Eisenbarth
Cc: [email protected]
Subject: Re: [parisc-linux] C180 Progress

"Marc Eisenbarth" writes...

Quoted 1 line

What is the statis for a Linux install for an HP C180 Visualize? I tried

Quoted 2 lines

install 0.5, but it seems to hang and will not accept input from the keyboard after the cd boots up.

IIRC, the C180 requires fixes that are not in the kernel on the 0.5 iso. Either build a new kernel(and boot from an nfsroot root), or wait for a new iso.

--
Matt Taggart Linux Development Lab
[email protected] HP Linux Systems Operation

Christoph Plattner

author

2001-04-08 21:02 UTC #16 lore raw

Re: [parisc-linux] Many experiments on 720, but `init' fails !!

In reply to Christoph Plattner

The same happens, if I use the `init' statically linked !

Quoted 65 lines · Christoph Plattner

A week ago, I reported the problem booting PA-Linux 0.5 with the new kernel and new selfmade cross tool chain.
The last week I used to experience with cross toolchain setup. The aim was to find away having "one" glibc-2 for cross development and for the target (to mount, NFS-ROOT). I also used tricks like
--prefix=/usr and
make install install_root=/usr/parisc/target....
but the result and discussion with other showed following:
There must be TWO glibc trees, one for the cross toolchain, the other for the target. The second one is built with the method defining prefix to /usr and install it in a target tree.
SO I build sash, a also build a bash (shared and static !), I build fileutils, text-utils, shell-utils, etc, etc.....
The system boots with bash and I can mount, run programs, etc....
The I build "my own" startup stuff. A /sbin/init.d/xxx , etc/rc.d/xxx and so on. I also build a sysvinit-2.78 (and 2.77 before), but the `init'
has it's problems. The error message is:
VFS: Mounted root (nfs filesystem) readonly.
break 0,0: pid=9 command='init'
init[9]: Breakpoint 0
YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001001111111100001111
r0-3     00000000 102de010 00000000 00000000
r4-7     00000000 00000000 00000000 00000000
r8-11    00000000 00000000 00000000 00000000
r12-15   00000000 00000000 00000040 1012544c
r16-19   13f085c0 13f08000 c804c804 00000001
r20-23   102efcc0 102efcc0 10022800 102efcc0
r24-27   0000002e 00001000 00000000 1024c010
r28-31   00000000 00000000 13f089c0 101312a0
sr0-3    00000000 00000000 00000000 00000001
sr4-7    00000000 00000000 00000000 00000000
IASQ: 00000000 00000000 IAOQ: 00000000 00000004
IIR: 00000000 ISR: 00000000 IOR: 00000000
ORIG_R28: 00000000
How can I follow up the thing ?
Is the GDB of the CVS usable (for example starting gdbserver init instead of init and `target remote' via the second serial interface ?)
By the way: I did a "super hack" in the kernel. In the serial interrupt routine, I catch the charcater ^\', filter it for /dev/ttyS0' and do a machine_restart(). This is perfect for development !!
With friendly regards
Christoph P.
--
-------------------------------------------------------------------------
private:        [email protected]
company:        [email protected]
_______________________________________________
parisc-linux mailing list
[email protected]
http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux

Signature · 3 lines

-------------------------------------------------------------------------
private:	[email protected]
company:	[email protected]

Matt Taggart

2001-04-09 20:49 UTC #17 lore raw

Re: [parisc-linux] Many experience done on 720, but `init' fails !!

In reply to Christoph Plattner

Christoph Plattner writes...

Quoted 3 lines

SO I build sash, a also build a bash (shared and static !), I build fileutils, text-utils, shell-utils, etc, etc.....
The system boots with bash and I can mount, run programs, etc....

Good.

Quoted 3 lines

The I build "my own" startup stuff. A /sbin/init.d/xxx , etc/rc.d/xxx and so on. I also build a sysvinit-2.78 (and 2.77 before), but the `init' has it's problems. The error message is:

Make sure you don't have multiple init's. The kernel will look in several places and I don't remember what order it looks in. If you only have one then that's the only one it can find :)

Are you still having problems with the init in the base tarball? Is it important to you to build your own init? If it is reply privately and maybe I can help.

Signature · 2 lines

Matt Taggart        Linux Development Lab
[email protected]   HP Linux Systems Operation

Christoph Plattner

author

2001-04-09 21:12 UTC #18 lore raw

Re: [parisc-linux] Many experience done on 720, but `init' fails !!

Hello !

Quoted 9 lines · Matt Taggart

Christoph Plattner writes...
Quoted 3 lines
SO I build sash, a also build a bash (shared and static !), I build fileutils, text-utils, shell-utils, etc, etc.....
The system boots with bash and I can mount, run programs, etc....
Good.

Quoted 7 lines

Quoted 3 lines
The I build "my own" startup stuff. A /sbin/init.d/xxx , etc/rc.d/xxx and so on. I also build a sysvinit-2.78 (and 2.77 before), but the `init' has it's problems. The error message is:
Make sure you don't have multiple init's. The kernel will look in several places and I don't remember what order it looks in. If you only have one then that's the only one it can find :)

I have only one init. But this is not a problem haveing more than one. In the linux kernel it is very simply to have a "source look" (init/main.c
bottom of the file). The kernel tries to exec /sbin/init. Only if the exec fails
(cannot open, load, execute) then the next thing is tried. But if the init has
a problem later on (faults, execptions, etc)the kernel does not try other entries.

My problem is in another point. The `init' is also responsible to start kernel
built-in processes (like kernel threads). They are AFAIK compiled in the kernel,
the init process only starts and supervise (or only starts) them. With the command
ps' those processes are named with [', ]', like the NFS daemon [nfsd]'.
Those procresses have very low pids (2,3,....). So I have to analyse the code,
what pid=9 will become ? The break happens here !

Quoted 4 lines

Are you still having problems with the init in the base tarball? Is it important to you to build your own init? If it is reply privately and maybe I can help.

I read from this tarball in thr mailing list.
Is this a new root file system ?
How can I use it.
I have no debian experence, up to now I only had Redhat and formerly Suse.
Do I need special knowledge ?

It is a hobby of mine, to build everything myself. I `dream' from a source
directory, where I can say `make install' and a whole Linux is the result,
of course for very small distribution of embeded Linux or firewall stuff.
In my private sparetime, "small & embedded" Linux is my hobby and the HP stuff and HP workstation is for me a perfect cross-build-lerning-equipment.

Richard Hirst

2001-04-10 08:45 UTC #19 lore raw

Re: [parisc-linux] Many experience done on 720, but `init' fails !!

Quoted 3 lines · Christoph Plattner

Those procresses have very low pids (2,3,....). So I have to analyse the code,
what pid=9 will become ? The break happens here !

  PID TTY      STAT   TIME COMMAND
    1 ?        S      0:02 init
    2 ?        SW     0:00 [keventd]
    3 ?        SW     0:00 [kswapd]
    4 ?        SW     0:00 [kreclaimd]
    5 ?        SW     0:00 [bdflush]
    6 ?        SW     0:00 [kupdate]
    7 ?        SW     0:00 [scsi_eh_1]
   73 ?        S      0:00 /sbin/portmap
   80 ?        SW     0:00 [rpciod]
   81 ?        SW     0:00 [lockd]
  124 ?        S      0:00 /sbin/syslogd
  127 ?        S      0:00 /sbin/klogd
  134 ?        S      0:00 /usr/sbin/inetd
  144 ?        S      0:01 /usr/sbin/sshd
  148 ?        S      0:00 /usr/sbin/atd
  151 ?        S      0:00 /usr/sbin/cron
  154 ttyS0    S      0:00 /sbin/getty -L ttyS0 9600 vt100
  155 ?        S      0:00 in.telnetd: beast.home
  156 pts/0    S      0:00 -bash
  157 pts/0    R      0:00 ps ax

Looks like PID 9 has run and exited during startup. This is a freshly booted B180.

One thought, if you have module support or hotplug support turned on in your kernel config, you should turn them off for the time being. The kernel might be trying to trigger a module load and failing.

Richard