* [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
@ 2001-04-02 22:51 Christoph Plattner
2001-04-02 23:17 ` Richard Hirst
0 siblings, 1 reply; 22+ messages in thread
From: Christoph Plattner @ 2001-04-02 22:51 UTC (permalink / raw)
To: parisc-linux
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
<here the system halts>
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 root@didymos.pladom1.at 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 (root@didymos.pladom1.at) (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 (sammy@oh.verio.com)
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
--
-------------------------------------------------------------------------
private: christoph.plattner@dot.at
company: christoph.plattner@alcatel.at
^ permalink raw reply [flat|nested] 22+ messages in thread* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-02 22:51 [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ? Christoph Plattner
@ 2001-04-02 23:17 ` Richard Hirst
2001-04-02 23:27 ` Matthew Wilcox
2001-04-03 6:55 ` Christoph Plattner
0 siblings, 2 replies; 22+ messages in thread
From: Richard Hirst @ 2001-04-02 23:17 UTC (permalink / raw)
To: Christoph Plattner; +Cc: parisc-linux
On Tue, Apr 03, 2001 at 12:51:32AM +0200, Christoph Plattner wrote:
> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-02 23:17 ` Richard Hirst
@ 2001-04-02 23:27 ` Matthew Wilcox
2001-04-02 23:41 ` Richard Hirst
2001-04-03 6:55 ` Christoph Plattner
1 sibling, 1 reply; 22+ messages in thread
From: Matthew Wilcox @ 2001-04-02 23:27 UTC (permalink / raw)
To: Richard Hirst; +Cc: Christoph Plattner, parisc-linux
On Tue, Apr 03, 2001 at 12:17:43AM +0100, Richard Hirst wrote:
> On Tue, Apr 03, 2001 at 12:51:32AM +0200, Christoph Plattner wrote:
> > 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.
> 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.
--
Revolutions do not require corporate support.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-02 23:27 ` Matthew Wilcox
@ 2001-04-02 23:41 ` Richard Hirst
0 siblings, 0 replies; 22+ messages in thread
From: Richard Hirst @ 2001-04-02 23:41 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: Christoph Plattner, parisc-linux
On Tue, Apr 03, 2001 at 12:27:49AM +0100, Matthew Wilcox wrote:
> On Tue, Apr 03, 2001 at 12:17:43AM +0100, Richard Hirst wrote:
> > On Tue, Apr 03, 2001 at 12:51:32AM +0200, Christoph Plattner wrote:
> > > 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.
You might well be right; it just reminded me of one of the problems
I saw on my 715/old with bad spinlock alignment.
> > 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-02 23:17 ` Richard Hirst
2001-04-02 23:27 ` Matthew Wilcox
@ 2001-04-03 6:55 ` Christoph Plattner
2001-04-03 9:12 ` Richard Hirst
2001-04-03 21:34 ` Matthew Wilcox
1 sibling, 2 replies; 22+ messages in thread
From: Christoph Plattner @ 2001-04-03 6:55 UTC (permalink / raw)
To: Richard Hirst; +Cc: Christoph Plattner, parisc-linux
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
Richard Hirst wrote:
>
> On Tue, Apr 03, 2001 at 12:51:32AM +0200, Christoph Plattner wrote:
> > 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
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
-----------------------------------------------------------------
private: christoph.plattner@dot.at
company: christoph.plattner@alcatel.at
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-03 6:55 ` Christoph Plattner
@ 2001-04-03 9:12 ` Richard Hirst
2001-04-03 9:23 ` Christoph Plattner
2001-04-03 21:34 ` Matthew Wilcox
1 sibling, 1 reply; 22+ messages in thread
From: Richard Hirst @ 2001-04-03 9:12 UTC (permalink / raw)
To: Christoph Plattner; +Cc: Christoph Plattner, parisc-linux
On Tue, Apr 03, 2001 at 08:55:15AM +0200, Christoph Plattner wrote:
> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-03 9:12 ` Richard Hirst
@ 2001-04-03 9:23 ` Christoph Plattner
2001-04-03 13:16 ` Richard Hirst
0 siblings, 1 reply; 22+ messages in thread
From: Christoph Plattner @ 2001-04-03 9:23 UTC (permalink / raw)
To: Richard Hirst; +Cc: Christoph Plattner, parisc-linux
Hello,
Richard Hirst wrote:
>
> On Tue, Apr 03, 2001 at 08:55:15AM +0200, Christoph Plattner wrote:
> > 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.
>
> Richard
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
--
+--------V--------+ Christoph.Plattner@alcatel.at
| A L C A T E L | -----------------------------
+-----------------+ Phone: +43 1 27722 3706
T A S Fax: +43 1 27722 3955
^ permalink raw reply [flat|nested] 22+ messages in thread* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-03 9:23 ` Christoph Plattner
@ 2001-04-03 13:16 ` Richard Hirst
0 siblings, 0 replies; 22+ messages in thread
From: Richard Hirst @ 2001-04-03 13:16 UTC (permalink / raw)
To: Christoph Plattner; +Cc: Christoph Plattner, parisc-linux
On Tue, Apr 03, 2001 at 11:23:58AM +0200, Christoph Plattner wrote:
> Hello,
>
> Richard Hirst wrote:
> >
> > On Tue, Apr 03, 2001 at 08:55:15AM +0200, Christoph Plattner wrote:
> > > 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-03 6:55 ` Christoph Plattner
2001-04-03 9:12 ` Richard Hirst
@ 2001-04-03 21:34 ` Matthew Wilcox
2001-04-04 7:08 ` Christoph Plattner
1 sibling, 1 reply; 22+ messages in thread
From: Matthew Wilcox @ 2001-04-03 21:34 UTC (permalink / raw)
To: Christoph Plattner; +Cc: Richard Hirst, Christoph Plattner, parisc-linux
On Tue, Apr 03, 2001 at 08:55:15AM +0200, Christoph Plattner wrote:
> 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.
--
Revolutions do not require corporate support.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-03 21:34 ` Matthew Wilcox
@ 2001-04-04 7:08 ` Christoph Plattner
2001-04-04 17:05 ` Matthew Wilcox
0 siblings, 1 reply; 22+ messages in thread
From: Christoph Plattner @ 2001-04-04 7:08 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: Richard Hirst, Christoph Plattner, parisc-linux
Hello,
Matthew Wilcox wrote:
>
> On Tue, Apr 03, 2001 at 08:55:15AM +0200, Christoph Plattner wrote:
> > 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.
>
> --
> Revolutions do not require corporate support.
--
+--------V--------+ Christoph.Plattner@alcatel.at
| A L C A T E L | -----------------------------
+-----------------+ Phone: +43 1 27722 3706
T A S Fax: +43 1 27722 3955
^ permalink raw reply [flat|nested] 22+ messages in thread* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-04 7:08 ` Christoph Plattner
@ 2001-04-04 17:05 ` Matthew Wilcox
2001-04-04 20:31 ` Christoph Plattner
2001-04-08 17:08 ` [parisc-linux] Many experience done on 720, but `init' fails !! Christoph Plattner
0 siblings, 2 replies; 22+ messages in thread
From: Matthew Wilcox @ 2001-04-04 17:05 UTC (permalink / raw)
To: Christoph Plattner
Cc: Matthew Wilcox, Richard Hirst, Christoph Plattner, parisc-linux
On Wed, Apr 04, 2001 at 09:08:23AM +0200, Christoph Plattner wrote:
> > 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 :-(
--
Revolutions do not require corporate support.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ?
2001-04-04 17:05 ` Matthew Wilcox
@ 2001-04-04 20:31 ` Christoph Plattner
2001-04-08 17:08 ` [parisc-linux] Many experience done on 720, but `init' fails !! Christoph Plattner
1 sibling, 0 replies; 22+ messages in thread
From: Christoph Plattner @ 2001-04-04 20:31 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: Christoph Plattner, Richard Hirst, parisc-linux
Matthew Wilcox wrote:
>
> On Wed, Apr 04, 2001 at 09:08:23AM +0200, Christoph Plattner wrote:
> > > 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 :-(
>
> --
> 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.
--
-------------------------------------------------------------------------
private: christoph.plattner@dot.at
company: christoph.plattner@alcatel.at
^ permalink raw reply [flat|nested] 22+ messages in thread
* [parisc-linux] Many experience done on 720, but `init' fails !!
2001-04-04 17:05 ` Matthew Wilcox
2001-04-04 20:31 ` Christoph Plattner
@ 2001-04-08 17:08 ` Christoph Plattner
2001-04-08 17:32 ` [parisc-linux] C180 Progress Marc Eisenbarth
` (2 more replies)
1 sibling, 3 replies; 22+ messages in thread
From: Christoph Plattner @ 2001-04-08 17:08 UTC (permalink / raw)
To: Matthew Wilcox; +Cc: Christoph Plattner, Richard Hirst, parisc-linux
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: christoph.plattner@dot.at
company: christoph.plattner@alcatel.at
^ permalink raw reply [flat|nested] 22+ messages in thread* [parisc-linux] C180 Progress
2001-04-08 17:08 ` [parisc-linux] Many experience done on 720, but `init' fails !! Christoph Plattner
@ 2001-04-08 17:32 ` Marc Eisenbarth
2001-04-09 13:36 ` Matt Taggart
2001-04-08 21:02 ` [parisc-linux] Many experiments on 720, but `init' fails !! Christoph Plattner
2001-04-09 20:52 ` [parisc-linux] Many experience done " Matt Taggart
2 siblings, 1 reply; 22+ messages in thread
From: Marc Eisenbarth @ 2001-04-08 17:32 UTC (permalink / raw)
To: parisc-linux
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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] C180 Progress
2001-04-08 17:32 ` [parisc-linux] C180 Progress Marc Eisenbarth
@ 2001-04-09 13:36 ` Matt Taggart
2001-04-09 17:05 ` Marc Eisenbarth
0 siblings, 1 reply; 22+ messages in thread
From: Matt Taggart @ 2001-04-09 13:36 UTC (permalink / raw)
To: Marc Eisenbarth; +Cc: parisc-linux
"Marc Eisenbarth" writes...
> 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.
--
Matt Taggart Linux Development Lab
taggart@fc.hp.com HP Linux Systems Operation
^ permalink raw reply [flat|nested] 22+ messages in thread
* RE: [parisc-linux] C180 Progress
2001-04-09 13:36 ` Matt Taggart
@ 2001-04-09 17:05 ` Marc Eisenbarth
0 siblings, 0 replies; 22+ messages in thread
From: Marc Eisenbarth @ 2001-04-09 17:05 UTC (permalink / raw)
To: Matt Taggart; +Cc: parisc-linux
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:taggart@carmen.fc.hp.com]
Sent: Monday, April 09, 2001 8:37 AM
To: Marc Eisenbarth
Cc: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] C180 Progress
"Marc Eisenbarth" writes...
> 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.
--
Matt Taggart Linux Development Lab
taggart@fc.hp.com HP Linux Systems Operation
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] Many experiments on 720, but `init' fails !!
2001-04-08 17:08 ` [parisc-linux] Many experience done on 720, but `init' fails !! Christoph Plattner
2001-04-08 17:32 ` [parisc-linux] C180 Progress Marc Eisenbarth
@ 2001-04-08 21:02 ` Christoph Plattner
2001-04-09 20:52 ` [parisc-linux] Many experience done " Matt Taggart
2 siblings, 0 replies; 22+ messages in thread
From: Christoph Plattner @ 2001-04-08 21:02 UTC (permalink / raw)
To: Matthew Wilcox, Christoph Plattner, Richard Hirst, parisc-linux
The same happens, if I use the `init' statically linked !
Christoph Plattner wrote:
>
> 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: christoph.plattner@dot.at
> company: christoph.plattner@alcatel.at
>
> _______________________________________________
> parisc-linux mailing list
> parisc-linux@lists.parisc-linux.org
> http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
--
-------------------------------------------------------------------------
private: christoph.plattner@dot.at
company: christoph.plattner@alcatel.at
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] Many experience done on 720, but `init' fails !!
2001-04-08 17:08 ` [parisc-linux] Many experience done on 720, but `init' fails !! Christoph Plattner
2001-04-08 17:32 ` [parisc-linux] C180 Progress Marc Eisenbarth
2001-04-08 21:02 ` [parisc-linux] Many experiments on 720, but `init' fails !! Christoph Plattner
@ 2001-04-09 20:52 ` Matt Taggart
2001-04-09 21:12 ` Christoph Plattner
2 siblings, 1 reply; 22+ messages in thread
From: Matt Taggart @ 2001-04-09 20:52 UTC (permalink / raw)
To: Christoph Plattner; +Cc: parisc-linux
Christoph Plattner writes...
> 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.
> 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.
--
Matt Taggart Linux Development Lab
taggart@fc.hp.com HP Linux Systems Operation
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] Many experience done on 720, but `init' fails !!
2001-04-09 20:52 ` [parisc-linux] Many experience done " Matt Taggart
@ 2001-04-09 21:12 ` Christoph Plattner
2001-04-10 8:46 ` Richard Hirst
0 siblings, 1 reply; 22+ messages in thread
From: Christoph Plattner @ 2001-04-09 21:12 UTC (permalink / raw)
To: Matt Taggart; +Cc: parisc-linux
Hello !
Matt Taggart wrote:
>
> Christoph Plattner writes...
>
> > 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.
>
> > 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 !
>
> 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.
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] Many experience done on 720, but `init' fails !!
2001-04-09 21:12 ` Christoph Plattner
@ 2001-04-10 8:46 ` Richard Hirst
0 siblings, 0 replies; 22+ messages in thread
From: Richard Hirst @ 2001-04-10 8:46 UTC (permalink / raw)
To: Christoph Plattner; +Cc: Matt Taggart, parisc-linux
On Mon, Apr 09, 2001 at 11:12:47PM +0200, Christoph Plattner wrote:
> 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
^ permalink raw reply [flat|nested] 22+ messages in thread
* Re: [parisc-linux] Many experiments on 720, but `init' fails !!
@ 2001-04-08 22:01 Jeff Arthur
2001-04-09 7:09 ` Christoph Plattner
0 siblings, 1 reply; 22+ messages in thread
From: Jeff Arthur @ 2001-04-08 22:01 UTC (permalink / raw)
To: parisc-linux
<FontFamily><param>Courier New</param>It seems like I have very similar problems with
a HP apollo series 700 (9000/730)
I have tried many builds, with home built cross
compilers, downloaded cross compilers, images
from CDs, downloaded lifs, roots on CDs,
ramdisks and nfsroots. booting using rbootd
over the lan, and off the .iso cd. I always
seem to end up with a variation of the
<color><param>0100,0100,0100</param>break 0,0: pid=1 command='init'
problem.
Am keen to help (If I can, though just a lowly
Sys Admin, not a kernel hack sadly)
P.S. i note that the boot only saw 1 cpu, even
though the box is reported to be a 3 way, I
presume this is as SMP is not compliled in by
default?
here is capture from my console port
(c) Copyright. Hewlett-Packard Company. 1991.
All rights reserved.
PDC ROM rev. 2.1
IODC ROM rev. 2.1
32 MB of memory configured and tested.
Searching for Potential Boot Devices.
To terminate search, press and hold the ESCAPE key.
Device Selection Device Path Device Type
----------------------------------------------------------------------------
P0 scsi.6.0 QUANTUM PD425S
P1 scsi.5.0 QUANTUM PD425S
P2 scsi.4.0 TOSHIBA CD-ROM XM-3701TA
P3 scsi.2.0 HP 2213A
P4 lan.00001c-030853.0.0 burner
b) Boot from specified device
s) Search for bootable devices
a) Enter Boot Administration mode
x) Exit and continue boot sequence
?) Help
Select from menu: b
Enter boot selection, (h)elp, or e(x)it: p4
Trying lan.00001c-030853.0.0
Boot path initialized.
Attempting to load IPL.
Hard booted.
palo ipl root@hetfield Sun Apr 8 19:24:31 UTC 2001
0/vmlinux 2561817 bytes @ 0x6800
0/palo-cmdline '0/vmlinux HOME=/ TERM=linux root=/dev/ram initrd=0/ramdisk console=ttyS0'
0/ramdisk 870400 bytes @ 0x277f19
Kernel: partition 0 file /vmlinux
Ramdisk: partition 0 file /ramdisk
ELF32 executable
Entry 00100000 first 00100000 n 5
Segment 0 load 00100000 size 1469208 mediaptr 0x1000
Segment 1 load 00268000 size 181976 mediaptr 0x168000
Segment 2 load 00298000 size 222280 mediaptr 0x195000
Segment 3 load 002d0000 size 8192 mediaptr 0x1cc000
Segment 4 load 002fef68 size 74720 mediaptr 0x1cef68
Loading ramdisk 870400 bytes @ 01f1a000...
branching to kernel entry point 0x00100000
PDC Console Initialized
Linux version 2.4.0 (root@hetfield) (gcc version 2.97 20010203 (experimental)) #1 Sun Apr 8 19:16:06 UTC 2001
FP[0] enabled: Rev 3 Model 0
The 32-bit Kernel has started...
Determining PDC firmware type: Older Legacy Box
setup_cmdline(0x64d58,0x64d58,0x1f1a000,0x1fee800)
PALO command line: 'HOME=/ TERM=linux root=/dev/ram console=ttyS0'
PALO initrd 1f1a000-1fee800
model 00002020 00000481 00000000 00000000 3a238470 000011f4 00000004 0000000d 00000000
vers 00000003
CPUID vers 0 rev 0
model 9000/730
Total Memory: 32 Mb
initrd: 11f1a000-11fee800
pagetable_init
On node 0 totalpages: 8192
zone(0): 8192 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 EISA BA (11) at 0xfc000000, versions 0x4, 0x0, 0x76, 0x0, 0x0
10. King Cobra (730) (0) at 0xfffbe000, versions 0x202, 0x0, 0x4, 0x0, 0x81
11. Cobra (1) at 0xfffbf000, versions 0x13, 0x0, 0x9, 0x0, 0x0
That's a total of 11 devices.
CPU(s): 1 x PA7000 (PCX-S) at 66.000000 MHz
Kernel command line: HOME=/ TERM=linux root=/dev/ram console=ttyS0
Calibrating delay loop... 65.74 BogoMIPS
Memory: 29156k available
Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 2048 (order: 2, 16384 bytes)
POSIX conformance testing by UNIFIX
ASP version 1 at 0xf0800000 found.
LED (ASP-style) display at f0800020 registered
Found HIL at 0xf0821000, IRQ 94
HIL: keyboard found at id 0
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
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 19 1B 34 IRQ 87.
82596.c $Revision: 1.17 $
RAMDISK: ext2 filesystem found at block 0
RAMDISK: Loading 850 blocks [1 disk] into ram disk... |\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\bdone.
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 (sammy@oh.verio.com)
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
Vendor: HP Model: 2213A Rev: C023
Type: Direct-Access ANSI SCSI revision: 01 CCS
Vendor: TOSHIBA Model: CD-ROM XM-3701TA Rev: 0236
Type: CD-ROM ANSI SCSI revision: 02
Vendor: QUANTUM Model: PD425S Rev: 535A
Type: Direct-Access ANSI SCSI revision: 02
Vendor: QUANTUM Model: PD425S Rev: 535A
Type: Direct-Access ANSI SCSI revision: 02
Detected scsi disk sda at scsi0, channel 0, id 2, lun 0
Detected scsi disk sdb at scsi0, channel 0, id 5, lun 0
Detected scsi disk sdc at scsi0, channel 0, id 6, lun 0
SCSI device sda: 1296512 512-byte hdwr sectors (664 MB)
Partition check:
sda: unknown partition table
SCSI device sdb: 833150 512-byte hdwr sectors (427 MB)
sdb: unknown partition table
SCSI device sdc: 833150 512-byte hdwr sectors (427 MB)
sdc: unknown partition table
Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0
Uniform CD-ROM driver Revision: 3.12
linear personality registered
raid0 personality registered
raid1 personality registered
raid5 personality registered
raid5: measuring checksumming speed
8regs : 41.910 MB/sec
8regs_prefetch: 53.721 MB/sec
32regs : 42.672 MB/sec
32regs_prefetch: 54.483 MB/sec
raid5: using function: 32regs_prefetch (54.483 MB/sec)
md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
md.c: sizeof(mdp_super_t) = 4096
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 2048 bind 2048)
eth0: link ok.
Sending BOOTP requests.... OK
IP-Config: Got BOOTP answer from 0.0.0.0, my address is 192.168.1.201
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem).
break 0,0: pid=1 command='init'
YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001000000000000001111
r0-3 00000000 1028260c 102d0000 00000000
r4-7 102d0580 1028260c 102d0000 00000000
r8-11 102d0580 00000000 00000000 1014ab60
r12-15 00000000 00000000 00000000 00000000
r16-19 11ff8000 1028260c 102d0000 00000000
r20-23 102d0580 00000000 00000000 00000000
r24-27 faf00038 faf0004c 00000001 10139494
r28-31 00000000 00000000 faf00080 00002f13
sr0-3 1ff2d60 11eef0c0 00000000 0000ffff
sr4-7 0000001 00000001 00000001 00000001
IASQ: 0000001 00000001 IAOQ: 00002f13 00002f17
IIR: 000000 ISR: 00000001 IOR: 00000000
ORIG_R28: 40800000
break 0,0: pid=1 command='init'
YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
PSW: 00000000000001000000000000001111
etc.....</color>
<nofill>
Thought for the Day:
Fax is stranger than fiction.
^ permalink raw reply [flat|nested] 22+ messages in thread* Re: [parisc-linux] Many experiments on 720, but `init' fails !!
2001-04-08 22:01 [parisc-linux] Many experiments " Jeff Arthur
@ 2001-04-09 7:09 ` Christoph Plattner
0 siblings, 0 replies; 22+ messages in thread
From: Christoph Plattner @ 2001-04-09 7:09 UTC (permalink / raw)
To: jeffa; +Cc: parisc-linux
This could be a simial problem, but in your case, another problem
is also likely.
You have a 9000/730, which really has *one* CPU. (There a three
chips, AFAIK, one is the CPU, one is a FPU coprocessor, and the
third often has to do with the cache).
The only difference is the CPU core speed (66HMz 730, 50Mhz 720),
and perhaps the machines are equipped a little different.
"Our" CPUs are very old. So there must be a line added in
the arch/parisc/kernel/trap.c file. In the handle_interruption()
you must add the line
`case 18:'
where
`case 15:'
`case 26:'
is in the code, because these old CPUs use an older method of
"reporting" page faults, etc...
But as you have the output of the "break" routine, this seems
not to be the interrupt code.
In my case it is pid=9. I have not find out yet, which "kernel
thread" pid will get.
With friendly regards
Christoph P.
Jeff Arthur wrote:
>
> It seems like I have very similar problems with a HP apollo series 700 (9000/730)
>
> I have tried many builds, with home built cross compilers, downloaded cross compilers, images from CDs, downloaded lifs, roots on CDs, ramdisks and nfsroots. booting using rbootd over the lan, and off the .iso cd. I always seem to end up with a variation of the
>
> break 0,0: pid=1 command='init'
>
> problem.
>
> Am keen to help (If I can, though just a lowly Sys Admin, not a kernel hack sadly)
>
> P.S. i note that the boot only saw 1 cpu, even though the box is reported to be a 3 way, I presume this is as SMP is not compliled in by default?
>
> here is capture from my console port
>
> (c) Copyright. Hewlett-Packard Company. 1991.
> All rights reserved.
>
> PDC ROM rev. 2.1
> IODC ROM rev. 2.1
> 32 MB of memory configured and tested.
>
> Searching for Potential Boot Devices.
> To terminate search, press and hold the ESCAPE key.
>
> Device Selection Device Path Device Type
> ----------------------------------------------------------------------------
>
> P0 scsi.6.0 QUANTUM PD425S
> P1 scsi.5.0 QUANTUM PD425S
> P2 scsi.4.0 TOSHIBA CD-ROM XM-3701TA
> P3 scsi.2.0 HP 2213A
> P4 lan.00001c-030853.0.0 burner
>
> b) Boot from specified device
> s) Search for bootable devices
> a) Enter Boot Administration mode
> x) Exit and continue boot sequence
> ?) Help
>
> Select from menu: b
>
> Enter boot selection, (h)elp, or e(x)it: p4
> Trying lan.00001c-030853.0.0
> Boot path initialized.
> Attempting to load IPL.
>
> Hard booted.
> palo ipl root@hetfield Sun Apr 8 19:24:31 UTC 2001
> 0/vmlinux 2561817 bytes @ 0x6800
> 0/palo-cmdline '0/vmlinux HOME=/ TERM=linux root=/dev/ram initrd=0/ramdisk console=ttyS0'
> 0/ramdisk 870400 bytes @ 0x277f19
> Kernel: partition 0 file /vmlinux
> Ramdisk: partition 0 file /ramdisk
> ELF32 executable
> Entry 00100000 first 00100000 n 5
> Segment 0 load 00100000 size 1469208 mediaptr 0x1000
> Segment 1 load 00268000 size 181976 mediaptr 0x168000
> Segment 2 load 00298000 size 222280 mediaptr 0x195000
> Segment 3 load 002d0000 size 8192 mediaptr 0x1cc000
> Segment 4 load 002fef68 size 74720 mediaptr 0x1cef68
> Loading ramdisk 870400 bytes @ 01f1a000...
> branching to kernel entry point 0x00100000
> PDC Console Initialized
> Linux version 2.4.0 (root@hetfield) (gcc version 2.97 20010203 (experimental)) #1 Sun Apr 8 19:16:06 UTC 2001
> FP[0] enabled: Rev 3 Model 0
> The 32-bit Kernel has started...
> Determining PDC firmware type: Older Legacy Box
> setup_cmdline(0x64d58,0x64d58,0x1f1a000,0x1fee800)
> PALO command line: 'HOME=/ TERM=linux root=/dev/ram console=ttyS0'
> PALO initrd 1f1a000-1fee800
> model 00002020 00000481 00000000 00000000 3a238470 000011f4 00000004 0000000d 00000000
> vers 00000003
> CPUID vers 0 rev 0
> model 9000/730
> Total Memory: 32 Mb
> initrd: 11f1a000-11fee800
> pagetable_init
> On node 0 totalpages: 8192
> zone(0): 8192 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 EISA BA (11) at 0xfc000000, versions 0x4, 0x0, 0x76, 0x0, 0x0
> 10. King Cobra (730) (0) at 0xfffbe000, versions 0x202, 0x0, 0x4, 0x0, 0x81
> 11. Cobra (1) at 0xfffbf000, versions 0x13, 0x0, 0x9, 0x0, 0x0
> That's a total of 11 devices.
> CPU(s): 1 x PA7000 (PCX-S) at 66.000000 MHz
> Kernel command line: HOME=/ TERM=linux root=/dev/ram console=ttyS0
> Calibrating delay loop... 65.74 BogoMIPS
> Memory: 29156k available
> Dentry-cache hash table entries: 4096 (order: 3, 32768 bytes)
> Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
> Page-cache hash table entries: 8192 (order: 3, 32768 bytes)
> Inode-cache hash table entries: 2048 (order: 2, 16384 bytes)
> POSIX conformance testing by UNIFIX
> ASP version 1 at 0xf0800000 found.
> LED (ASP-style) display at f0800020 registered
> Found HIL at 0xf0821000, IRQ 94
> HIL: keyboard found at id 0
> 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
> 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 19 1B 34 IRQ 87.
> 82596.c $Revision: 1.17 $
> RAMDISK: ext2 filesystem found at block 0
> RAMDISK: Loading 850 blocks [1 disk] into ram disk... |\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\b-\b\\b|\b/\bdone.
> 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 (sammy@oh.verio.com)
> 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
> Vendor: HP Model: 2213A Rev: C023
> Type: Direct-Access ANSI SCSI revision: 01 CCS
> Vendor: TOSHIBA Model: CD-ROM XM-3701TA Rev: 0236
> Type: CD-ROM ANSI SCSI revision: 02
> Vendor: QUANTUM Model: PD425S Rev: 535A
> Type: Direct-Access ANSI SCSI revision: 02
> Vendor: QUANTUM Model: PD425S Rev: 535A
> Type: Direct-Access ANSI SCSI revision: 02
> Detected scsi disk sda at scsi0, channel 0, id 2, lun 0
> Detected scsi disk sdb at scsi0, channel 0, id 5, lun 0
> Detected scsi disk sdc at scsi0, channel 0, id 6, lun 0
> SCSI device sda: 1296512 512-byte hdwr sectors (664 MB)
> Partition check:
> sda: unknown partition table
> SCSI device sdb: 833150 512-byte hdwr sectors (427 MB)
> sdb: unknown partition table
> SCSI device sdc: 833150 512-byte hdwr sectors (427 MB)
> sdc: unknown partition table
> Detected scsi CD-ROM sr0 at scsi0, channel 0, id 4, lun 0
> Uniform CD-ROM driver Revision: 3.12
> linear personality registered
> raid0 personality registered
> raid1 personality registered
> raid5 personality registered
> raid5: measuring checksumming speed
> 8regs : 41.910 MB/sec
> 8regs_prefetch: 53.721 MB/sec
> 32regs : 42.672 MB/sec
> 32regs_prefetch: 54.483 MB/sec
> raid5: using function: 32regs_prefetch (54.483 MB/sec)
> md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> md.c: sizeof(mdp_super_t) = 4096
> 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 2048 bind 2048)
> eth0: link ok.
> Sending BOOTP requests.... OK
> IP-Config: Got BOOTP answer from 0.0.0.0, my address is 192.168.1.201
> NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
> VFS: Mounted root (ext2 filesystem).
> break 0,0: pid=1 command='init'
>
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
> PSW: 00000000000001000000000000001111
> r0-3 00000000 1028260c 102d0000 00000000
> r4-7 102d0580 1028260c 102d0000 00000000
> r8-11 102d0580 00000000 00000000 1014ab60
> r12-15 00000000 00000000 00000000 00000000
> r16-19 11ff8000 1028260c 102d0000 00000000
> r20-23 102d0580 00000000 00000000 00000000
> r24-27 faf00038 faf0004c 00000001 10139494
> r28-31 00000000 00000000 faf00080 00002f13
> sr0-3 1ff2d60 11eef0c0 00000000 0000ffff
> sr4-7 0000001 00000001 00000001 00000001
>
> IASQ: 0000001 00000001 IAOQ: 00002f13 00002f17
> IIR: 000000 ISR: 00000001 IOR: 00000000
>
> ORIG_R28: 40800000
>
> break 0,0: pid=1 command='init'
>
> YZrvWESTHLNXBCVMcbcbcbcbOGFRQPDI
>
> PSW: 00000000000001000000000000001111
>
> etc.....
> Thought for the Day: Fax is stranger than fiction.
>
> _______________________________________________ parisc-linux mailing list parisc-linux@lists.parisc-linux.org http://lists.parisc-linux.org/cgi-bin/mailman/listinfo/parisc-linux
--
+--------V--------+ Christoph.Plattner@alcatel.at
| A L C A T E L | -----------------------------
+-----------------+ Phone: +43 1 27722 3706
T A S Fax: +43 1 27722 3955
^ permalink raw reply [flat|nested] 22+ messages in thread
end of thread, other threads:[~2001-04-10 8:45 UTC | newest]
Thread overview: 22+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-04-02 22:51 [parisc-linux] New kernel on 720 + Pa-Linux-0.5: Breakpoint ? Christoph Plattner
2001-04-02 23:17 ` Richard Hirst
2001-04-02 23:27 ` Matthew Wilcox
2001-04-02 23:41 ` Richard Hirst
2001-04-03 6:55 ` Christoph Plattner
2001-04-03 9:12 ` Richard Hirst
2001-04-03 9:23 ` Christoph Plattner
2001-04-03 13:16 ` Richard Hirst
2001-04-03 21:34 ` Matthew Wilcox
2001-04-04 7:08 ` Christoph Plattner
2001-04-04 17:05 ` Matthew Wilcox
2001-04-04 20:31 ` Christoph Plattner
2001-04-08 17:08 ` [parisc-linux] Many experience done on 720, but `init' fails !! Christoph Plattner
2001-04-08 17:32 ` [parisc-linux] C180 Progress Marc Eisenbarth
2001-04-09 13:36 ` Matt Taggart
2001-04-09 17:05 ` Marc Eisenbarth
2001-04-08 21:02 ` [parisc-linux] Many experiments on 720, but `init' fails !! Christoph Plattner
2001-04-09 20:52 ` [parisc-linux] Many experience done " Matt Taggart
2001-04-09 21:12 ` Christoph Plattner
2001-04-10 8:46 ` Richard Hirst
-- strict thread matches above, loose matches on Subject: below --
2001-04-08 22:01 [parisc-linux] Many experiments " Jeff Arthur
2001-04-09 7:09 ` Christoph Plattner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.