* parsic: strange boot crash on a500
@ 2016-11-26 0:13 Meelis Roos
2016-11-26 9:12 ` Helge Deller
0 siblings, 1 reply; 16+ messages in thread
From: Meelis Roos @ 2016-11-26 0:13 UTC (permalink / raw)
To: linux-parisc
I have succeeded in keepin my rp3410 and rp3440 up to date but I have
trouble on A500 after 4.8.
Tried two kernels, something around 4.9-rc2 and
4.9.0-rc5-00297-g20afa6e, they both crash on boot like that. Hardware
seems fine, I can boot kernels up to 4.8 without problems.
After these messages it just sits there, no progress is made.
PDT is empty.
All fields see to be 0 for the alert, except timestamp ands alert level
(=7).
Is there anything in PIM that might be of interest?
Bisecting slowly is possible.
HARD Booted.
palo ipl 1.95 portage@a500 Thu Jul 7 15:40:10 EEST 2016
Partition Start(MB) End(MB) Id Type
1 1 32 f0 Palo
2 33 224 83 ext2
3 225 31696 83 ext2
4 31697 34732 83 ext2
PALO(F0) partition contains:
Command line for kernel: 'root=/dev/sda3 console=ttyS0 palo_kernel=2/vmlinux'
Selected kernel: /vmlinux from partition 2
************* SYSTEM ALERT **************
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 7 = reserved
REASON FOR ALERT
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF ON ON
LED State: Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.
0x0000007000FF6292 00000000 00000000 - type 0 = Data Field Unused
0x5800087000FF6292 0000740A 19151E19 - type 11 = Timestamp 11/25/2016 21:30:25
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
->Choice:Timeout!
*****************************************
Interesting entries from SL GSP command from these seconds:
Log Entry # 300 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 6
PROBLEM DETAIL: 3 = function failure
CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 34 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x7000002382066343 00000000 00070200 type 14 = Problem Detail
0x5800082382066343 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 301 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 4
PROBLEM DETAIL: 3 = function failure
CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 34 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x7000002382046343 00000000 00070200 type 14 = Problem Detail
0x5800082382046343 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 302 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 2
PROBLEM DETAIL: 3 = function failure
CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 34 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x7000002382026343 00000000 00070200 type 14 = Problem Detail
0x5800082382026343 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 303 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 8 = I/O
SOURCE DETAIL: 2 = system bus adapter SOURCE ID: 0
PROBLEM DETAIL: 3 = function failure
CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 34 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x7000002382006343 00000000 00070200 type 14 = Problem Detail
0x5800082382006343 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 304 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 0 = No failure detected, forward progress
SOURCE: 8 = I/O
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 0
CALLER SUBACTIVITY: 30 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000000080006300 00000000 00000001 type 0 = Data Field Unused
0x5800080080006300 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 305 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 40 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000002000FF6402 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6402 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 306 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 44 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000002000FF6442 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6442 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 307 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 0 = No failure detected, forward progress
SOURCE: 8 = I/O
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: F
CALLER SUBACTIVITY: 31 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x000000008000631F 00000000 00000000 type 0 = Data Field Unused
0x580008008000631F 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 308 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 0 = No failure detected, forward progress
SOURCE: 8 = I/O
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 0
CALLER SUBACTIVITY: 31 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000000080006310 00000000 00000001 type 0 = Data Field Unused
0x5800080080006310 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 309 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 7 = memory
SOURCE DETAIL: 9 = unexpected SOURCE ID: 0
PROBLEM DETAIL: 3 = unexpected
CALLER ACTIVITY: 6 = machine check STATUS: 3
CALLER SUBACTIVITY: 13 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x7000002379006133 C1BFF0FF FED08040 type 14 = Problem Detail
0x5800082379006133 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 310 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 7 = memory
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 08 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x7000002070006082 00000000 00392400 type 14 = Problem Detail
0x5800082070006082 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 311 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 7 = memory
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 06 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x6000002070006062 00000000 00000010 type 12 = Device Status
0x5800082070006062 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 312 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 1 = Information only, no action required
SOURCE: 6 = platform
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 2A = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0xA000001060FF62A2 00000000 0000050B type 20 = major change in system
state
0x5800081060FF62A2 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 313 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 7 = reserved
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 29 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000007000FF6292 00000000 00000000 type 0 = Data Field Unused
0x5800087000FF6292 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 314 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 1 = processor
SOURCE DETAIL: 1 = processor general SOURCE ID: 0
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 31 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x1800002011006312 CB810000 00000000 type 3 = Actual Data
0x5800082011006312 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
Log Entry # 315 :
SYSTEM NAME: a500-m
DATE: 11/25/2016 TIME: 21:30:25
ALERT LEVEL: 2 = Non-Urgent operator attention required
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
CALLER ACTIVITY: 6 = machine check STATUS: 2
CALLER SUBACTIVITY: 24 = implementation dependent
REPORTING ENTITY TYPE: 0 = system firmware REPORTING ENTITY ID: 00
0x0000002000FF6242 00000000 00000000 type 0 = Data Field Unused
0x5800082000FF6242 0000740A 19151E19 type 11 = Timestamp 11/25/2016
21:30:25
Type CR for next entry, - CR for previous entry, Q CR to quit.
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: parsic: strange boot crash on a500
2016-11-26 0:13 parsic: strange boot crash on a500 Meelis Roos
@ 2016-11-26 9:12 ` Helge Deller
2016-11-27 21:35 ` Meelis Roos
0 siblings, 1 reply; 16+ messages in thread
From: Helge Deller @ 2016-11-26 9:12 UTC (permalink / raw)
To: Meelis Roos, linux-parisc
Hi Meelis,
I think I know what's going on...
On 26.11.2016 01:13, Meelis Roos wrote:
> I have succeeded in keepin my rp3410 and rp3440 up to date but I have
> trouble on A500 after 4.8.
>
> Tried two kernels, something around 4.9-rc2 and
In the rc1-rc3 kernel series I switched in kernel from bootmem
to memblock allocator. There was some bug in there which led to
a crash. It was fixed later on.
So, rc2 is probably bad, but this is not the main reason why
your machine dies at the stage you report here...
> 4.9.0-rc5-00297-g20afa6e, they both crash on boot like that.
rc5 should be more OK, but just last night we fixed some more problems:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3ad0e83cf86bcaeb6ca3c37060a3ce866b25fb42
So, if you try, please update to latest git head now.
> Hardware seems fine, I can boot kernels up to 4.8 without problems.
> ...
> HARD Booted.
> palo ipl 1.95 portage@a500 Thu Jul 7 15:40:10 EEST 2016
>
> Partition Start(MB) End(MB) Id Type
> 1 1 32 f0 Palo
> 2 33 224 83 ext2
> 3 225 31696 83 ext2
> 4 31697 34732 83 ext2
>
> PALO(F0) partition contains:
You sadly didn't included the PALO segment list here.
I think this is your main problem.
Probably you have quite some modules built-in, and your
kernel got bigger than before and as such it triggers
an old bug in the palo boot loader.
Please read this palo commit message which explains it:
https://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/commit/?id=70bd7a9a41e318c0575755a78c4d18ad97495c47
I think those steps should fix your problem:
1. Boot into a functional kernel (e.g. v4.8)
2. Update your palo boot loader:
https://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/
You should build palo 1.96, and then *install* it into
your palo boot partition: run "palo -v" once.
3. Pull and build Linus' latest git tree to get latest parisc fixes
4. boot again, palo should report version 1.96 and it should start your new kernel.
Helge
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: parsic: strange boot crash on a500
2016-11-27 21:35 ` Meelis Roos
@ 2016-11-27 20:37 ` Helge Deller
2016-11-27 23:45 ` Meelis Roos
0 siblings, 1 reply; 16+ messages in thread
From: Helge Deller @ 2016-11-27 20:37 UTC (permalink / raw)
To: Meelis Roos; +Cc: linux-parisc
On 27.11.2016 22:35, Meelis Roos wrote:
> Cloned git://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git
> and built and installed it.
>
>> You should build palo 1.96, and then *install* it into
>> your palo boot partition: run "palo -v" once.
>
> palo version 1.96 http://www.parisc-linux.org - Sun Nov 27 21:27:38 EET 2016
> Partition Start(MB) End(MB) Id Type
> 1 1 32 f0 Palo
> 2 33 224 83 ext2
> 3 225 31696 83 ext2
> 4 31697 34732 83 ext2
> F0 partition start sector 32 length 65504
> do_ra(1, 4, -1, -1, '2/vmlinux root=/dev/sda3 console=ttyS0', 3, -1, 16384, 33538048)
> check_bootloader 215
> checksum(0x331d8, 45056) = 0x00000000
> ipl: addr 16384 size 45056 entry 0x0
> ko 0x0 ksz 0 knsz 0 k64o 0x0 k64sz 0 k64nsz 0 rdo 0 rdsz 0
> <2/vmlinux root=/dev/sda3 console=ttyS0>
> check_bootloader 670
> checksum(0x281d0, 45056) = 0x00000000
> ipl: addr 16384 size 45056 entry 0x0
> ko 0x0 ksz 0 knsz 0 k64o 0x0 k64sz 0 k64nsz 0 rdo 0 rdsz 0
> <2/vmlinux root=/dev/sda3 console=ttyS0>
Good.
>> 3. Pull and build Linus' latest git tree to get latest parisc fixes
>
> Built.
Ok.
I assume you copied it to /boot/vmlinux then ?
>> 4. boot again, palo should report version 1.96 and it should start your new kernel.
>
> Unfortunately, still the same.
> Is iplboot precompiled? It shows 08 Oct.
Yes, it's precompiled (needed if palo is built on other architectures).
You can compile it yourself with "make iplboot".
But the precompiled version works for me, so I don't think it's related to your boot problem.
> Trying Primary Boot Path
> ------------------------
> Booting...
> Boot IO Dependent Code (IODC) revision 1
>
>
> HARD Booted.
> palo ipl 1.96 http://www.parisc-linux.org - Sun, 08 Oct 2016 22:40:31 +0100
Good.
> Partition Start(MB) End(MB) Id Type
> 1 1 32 f0 Palo
> 2 33 224 83 ext2
> 3 225 31696 83 ext2
> 4 31697 34732 83 ext2
>
> PALO(F0) partition contains:
>
> Command line for kernel: 'root=/dev/sda3 console=ttyS0
> palo_kernel=2/vmlinux'
> Selected kernel: /vmlinux from partition 2
I'm missing here the information of the various sections
in the vmlinux file which the boot loader usually prints
here.
Can you please check (e.g. readelf/objdump) your vmlinux file?
I assume partition 2 is your /boot partition, in which case it's /boot/vmlinux.
There seems to be a current problem with latest binutils (on x86_64), but
not sure if this affects you.
Helge
> ************* SYSTEM ALERT **************
> SYSTEM NAME: a500-m
> DATE: 11/27/2016 TIME: 19:34:16
> ALERT LEVEL: 7 = reserved
>
> REASON FOR ALERT
> SOURCE: 0 = unknown, no source stated
> SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
> PROBLEM DETAIL: 0 = no problem detail
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: parsic: strange boot crash on a500
2016-11-26 9:12 ` Helge Deller
@ 2016-11-27 21:35 ` Meelis Roos
2016-11-27 20:37 ` Helge Deller
0 siblings, 1 reply; 16+ messages in thread
From: Meelis Roos @ 2016-11-27 21:35 UTC (permalink / raw)
To: Helge Deller; +Cc: linux-parisc
> > 4.9.0-rc5-00297-g20afa6e, they both crash on boot like that.
>
> rc5 should be more OK, but just last night we fixed some more problems:
> http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=3ad0e83cf86bcaeb6ca3c37060a3ce866b25fb42
> So, if you try, please update to latest git head now.
Updated to ths version.
> 1. Boot into a functional kernel (e.g. v4.8)
> 2. Update your palo boot loader:
> https://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/
Cloned git://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git
and built and installed it.
> You should build palo 1.96, and then *install* it into
> your palo boot partition: run "palo -v" once.
palo version 1.96 http://www.parisc-linux.org - Sun Nov 27 21:27:38 EET 2016
Partition Start(MB) End(MB) Id Type
1 1 32 f0 Palo
2 33 224 83 ext2
3 225 31696 83 ext2
4 31697 34732 83 ext2
F0 partition start sector 32 length 65504
do_ra(1, 4, -1, -1, '2/vmlinux root=/dev/sda3 console=ttyS0', 3, -1, 16384, 33538048)
check_bootloader 215
checksum(0x331d8, 45056) = 0x00000000
ipl: addr 16384 size 45056 entry 0x0
ko 0x0 ksz 0 knsz 0 k64o 0x0 k64sz 0 k64nsz 0 rdo 0 rdsz 0
<2/vmlinux root=/dev/sda3 console=ttyS0>
check_bootloader 670
checksum(0x281d0, 45056) = 0x00000000
ipl: addr 16384 size 45056 entry 0x0
ko 0x0 ksz 0 knsz 0 k64o 0x0 k64sz 0 k64nsz 0 rdo 0 rdsz 0
<2/vmlinux root=/dev/sda3 console=ttyS0>
> 3. Pull and build Linus' latest git tree to get latest parisc fixes
Built.
> 4. boot again, palo should report version 1.96 and it should start your new kernel.
Unfortunately, still the same. Is iplboot precompiled? It shows 08 Oct.
Trying Primary Boot Path
------------------------
Booting...
Boot IO Dependent Code (IODC) revision 1
HARD Booted.
palo ipl 1.96 http://www.parisc-linux.org - Sun, 08 Oct 2016 22:40:31 +0100
Partition Start(MB) End(MB) Id Type
1 1 32 f0 Palo
2 33 224 83 ext2
3 225 31696 83 ext2
4 31697 34732 83 ext2
PALO(F0) partition contains:
Command line for kernel: 'root=/dev/sda3 console=ttyS0
palo_kernel=2/vmlinux'
Selected kernel: /vmlinux from partition 2
************* SYSTEM ALERT **************
SYSTEM NAME: a500-m
DATE: 11/27/2016 TIME: 19:34:16
ALERT LEVEL: 7 = reserved
REASON FOR ALERT
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH OFF ON ON
LED State: Running non-OS code. Non-critical error detected.
Check Chassis and Console Logs for error messages.
0x0000007000FF6292 00000000 00000000 - type 0 = Data Field Unused
0x5800087000FF6292 0000740A 1B132210 - type 11 = Timestamp 11/27/2016
19:34:16
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: parsic: strange boot crash on a500
2016-11-27 20:37 ` Helge Deller
@ 2016-11-27 23:45 ` Meelis Roos
2016-11-28 15:36 ` Aw: " Helge Deller
0 siblings, 1 reply; 16+ messages in thread
From: Meelis Roos @ 2016-11-27 23:45 UTC (permalink / raw)
To: Helge Deller; +Cc: linux-parisc
> > Cloned git://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git
> > and built and installed it.
> >
> >> You should build palo 1.96, and then *install* it into
> >> your palo boot partition: run "palo -v" once.
> >
> > palo version 1.96 http://www.parisc-linux.org - Sun Nov 27 21:27:38 EET 2016
> > Partition Start(MB) End(MB) Id Type
> > 1 1 32 f0 Palo
> > 2 33 224 83 ext2
> > 3 225 31696 83 ext2
> > 4 31697 34732 83 ext2
> > F0 partition start sector 32 length 65504
> > do_ra(1, 4, -1, -1, '2/vmlinux root=/dev/sda3 console=ttyS0', 3, -1, 16384, 33538048)
> > check_bootloader 215
> > checksum(0x331d8, 45056) = 0x00000000
> > ipl: addr 16384 size 45056 entry 0x0
> > ko 0x0 ksz 0 knsz 0 k64o 0x0 k64sz 0 k64nsz 0 rdo 0 rdsz 0
> > <2/vmlinux root=/dev/sda3 console=ttyS0>
> > check_bootloader 670
> > checksum(0x281d0, 45056) = 0x00000000
> > ipl: addr 16384 size 45056 entry 0x0
> > ko 0x0 ksz 0 knsz 0 k64o 0x0 k64sz 0 k64nsz 0 rdo 0 rdsz 0
> > <2/vmlinux root=/dev/sda3 console=ttyS0>
>
> Good.
>
> >> 3. Pull and build Linus' latest git tree to get latest parisc fixes
> >
> > Built.
>
> Ok.
> I assume you copied it to /boot/vmlinux then ?
Yes, as I always do.
> >> 4. boot again, palo should report version 1.96 and it should start your new kernel.
> >
> > Unfortunately, still the same.
> > Is iplboot precompiled? It shows 08 Oct.
>
> Yes, it's precompiled (needed if palo is built on other architectures).
> You can compile it yourself with "make iplboot".
> But the precompiled version works for me, so I don't think it's related to your boot problem.
>
> > Trying Primary Boot Path
> > ------------------------
> > Booting...
> > Boot IO Dependent Code (IODC) revision 1
> >
> >
> > HARD Booted.
> > palo ipl 1.96 http://www.parisc-linux.org - Sun, 08 Oct 2016 22:40:31 +0100
>
> Good.
>
> > Partition Start(MB) End(MB) Id Type
> > 1 1 32 f0 Palo
> > 2 33 224 83 ext2
> > 3 225 31696 83 ext2
> > 4 31697 34732 83 ext2
> >
> > PALO(F0) partition contains:
> >
> > Command line for kernel: 'root=/dev/sda3 console=ttyS0
> > palo_kernel=2/vmlinux'
> > Selected kernel: /vmlinux from partition 2
>
> I'm missing here the information of the various sections
> in the vmlinux file which the boot loader usually prints
> here.
Well, I did not leave anything out AFAIK?
>
> Can you please check (e.g. readelf/objdump) your vmlinux file?
> I assume partition 2 is your /boot partition, in which case it's /boot/vmlinux.
To discontinue, press any key within 10 seconds.
Boot terminated.
---- Main Menu
---------------------------------------------------------------
Command Description
------- -----------
BOot [PRI|ALT|<path>] Boot from specified path
PAth [PRI|ALT] [<path>] Display or modify a path
SEArch [DIsplay|IPL] [<path>] Search for boot devices
COnfiguration menu Displays or sets boot values
INformation menu Displays hardware information
SERvice menu Displays service commands
DIsplay Redisplay the current menu
HElp [<menu>|<command>] Display help for menu or command
RESET Restart the system
----
Main Menu: Enter command or menu > bo
Interact with IPL (Y, N, or Cancel)?> y
Booting...
Boot IO Dependent Code (IODC) revision 1
HARD Booted.
palo ipl 1.96 http://www.parisc-linux.org - Sun, 08 Oct 2016 22:40:31
+0100
Partition Start(MB) End(MB) Id Type
1 1 32 f0 Palo
2 33 224 83 ext2
3 225 31696 83 ext2
4 31697 34732 83 ext2
PALO(F0) partition contains:
Current command line:
2/vmlinux root=/dev/sda3 console=ttyS0
0: 2/vmlinux
1: root=/dev/sda3
2: console=ttyS0
<#> edit the numbered field
'b' boot with this command line
'r' restore command line
'l' list dir
'x' reset and reboot machine
? b
Command line for kernel: 'root=/dev/sda3 console=ttyS0
palo_kernel=2/vmlinux'
Selected kernel: /vmlinux from partition 2
************* SYSTEM ALERT **************
SYSTEM NAME: a500-m
DATE: 11/27/2016 TIME: 21:34:57
ALERT LEVEL: 7 = reserved
REASON FOR ALERT
SOURCE: 0 = unknown, no source stated
SOURCE DETAIL: 0 = unknown, no source stated SOURCE ID: FF
PROBLEM DETAIL: 0 = no problem detail
LEDs: RUN ATTENTION FAULT REMOTE POWER
FLASH FLASH FLASH ON ON
LED State: Unexpected Reboot. Running non-OS code. Non-critical error
detected.
Check Chassis and Console Logs for error messages.
0x0000007000FF6292 00000000 00000000 - type 0 = Data Field Unused
0x5800087000FF6292 0000740A 1B152239 - type 11 = Timestamp 11/27/2016
21:34:57
A: ack read of this entry - X: Disable all future alert messages
Anything else skip redisplay the log entry
=====================================================================================
When I boot 4.8.0, I do get some more ouptut:
Main Menu: Enter command or menu > bo
Interact with IPL (Y, N, or Cancel)?> y
Booting...
Boot IO Dependent Code (IODC) revision 1
HARD Booted.
palo ipl 1.96 http://www.parisc-linux.org - Sun, 08 Oct 2016 22:40:31
+0100
Partition Start(MB) End(MB) Id Type
1 1 32 f0 Palo
2 33 224 83 ext2
3 225 31696 83 ext2
4 31697 34732 83 ext2
PALO(F0) partition contains:
Current command line:
2/vmlinux root=/dev/sda3 console=ttyS0
0: 2/vmlinux
1: root=/dev/sda3
2: console=ttyS0
<#> edit the numbered field
'b' boot with this command line
'r' restore command line
'l' list dir
'x' reset and reboot machine
? 0
2/vmlinux-4.8.0
Current command line:
2/vmlinux-4.8.0 root=/dev/sda3 console=ttyS0
0: 2/vmlinux-4.8.0
1: root=/dev/sda3
2: console=ttyS0
<#> edit the numbered field
'b' boot with this command line
'r' restore command line
'l' list dir
'x' reset and reboot machine
? b
Command line for kernel: 'root=/dev/sda3 console=ttyS0
palo_kernel=2/vmlinux-4.8.0'
Selected kernel: /vmlinux-4.8.0 from partition 2
ELF64 executable
Entry 00100000 first 00100000 n 4
Segment 0 load 00100000 size 133632 mediaptr 0x1000
Segment 1 load 00121000 size 22176 mediaptr 0x22000
Segment 2 load 00200000 size 5748800 mediaptr 0x28000
Segment 3 load 00800000 size 1011968 mediaptr 0x5a4000
Branching to kernel entry point 0x00100000. If this is the last
message you see, you may need to switch your console. This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org
Linux version 4.8.0 (mroos@a500) (gcc version 5.4.0 (Gentoo 5.4.0 p1.0) ) #99 Wed Oct 5 20:36:13 EEST 2016
...
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 16+ messages in thread
* Aw: Re: parsic: strange boot crash on a500
2016-11-27 23:45 ` Meelis Roos
@ 2016-11-28 15:36 ` Helge Deller
2016-11-28 15:40 ` Helge Deller
0 siblings, 1 reply; 16+ messages in thread
From: Helge Deller @ 2016-11-28 15:36 UTC (permalink / raw)
To: Meelis Roos; +Cc: linux-parisc
> > > Partition Start(MB) End(MB) Id Type
> > > 1 1 32 f0 Palo
> > > 2 33 224 83 ext2
> > > 3 225 31696 83 ext2
> > > 4 31697 34732 83 ext2
> > >
> > > PALO(F0) partition contains:
> > >
> > > Command line for kernel: 'root=/dev/sda3 console=ttyS0
> > > palo_kernel=2/vmlinux'
> > > Selected kernel: /vmlinux from partition 2
> >
> > I'm missing here the information of the various sections
> > in the vmlinux file which the boot loader usually prints
> > here.
>
> Well, I did not leave anything out AFAIK?
It seems palo can't read the vmlinux file (aka get's confused with the contents
and doesn't print the ELF section list).
Did you maybe used a recent binutils package?
See:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845690
https://sourceware.org/ml/binutils/2016-11/msg00348.html
Maybe downgrading binutils helps?
Helge
^ permalink raw reply [flat|nested] 16+ messages in thread
* Aw: Re: parsic: strange boot crash on a500
2016-11-28 15:36 ` Aw: " Helge Deller
@ 2016-11-28 15:40 ` Helge Deller
2016-11-28 17:39 ` Meelis Roos
2016-11-28 18:37 ` Meelis Roos
0 siblings, 2 replies; 16+ messages in thread
From: Helge Deller @ 2016-11-28 15:40 UTC (permalink / raw)
To: Meelis Roos; +Cc: linux-parisc
> > > > Command line for kernel: 'root=/dev/sda3 console=ttyS0
> > > > palo_kernel=2/vmlinux'
> > > > Selected kernel: /vmlinux from partition 2
> > >
> > > I'm missing here the information of the various sections
> > > in the vmlinux file which the boot loader usually prints
> > > here.
> >
> > Well, I did not leave anything out AFAIK?
>
> It seems palo can't read the vmlinux file (aka get's confused with the contents
> and doesn't print the ELF section list).
>
> Did you maybe used a recent binutils package?
> See:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845690
> https://sourceware.org/ml/binutils/2016-11/msg00348.html
>
> Maybe downgrading binutils helps?
Sorry, I just noticed that you are pretty aware of this bug
(you actually opened the ticket) :-)
Helge
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-11-28 18:37 ` Meelis Roos
@ 2016-11-28 17:30 ` John David Anglin
2016-11-28 18:05 ` Helge Deller
1 sibling, 0 replies; 16+ messages in thread
From: John David Anglin @ 2016-11-28 17:30 UTC (permalink / raw)
To: Meelis Roos, Helge Deller; +Cc: linux-parisc
On 2016-11-28 1:37 PM, Meelis Roos wrote:
> Old binutils, but here is my vmlinux that does not boot (slightly larger
> than vmlinux-4.8.0):
Maybe compare ELF PHDRS and sections with working and non working
kernels. I think Helge
may have changed the placement of some stuff.
Dave
--
John David Anglin dave.anglin@bell.net
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-11-28 15:40 ` Helge Deller
@ 2016-11-28 17:39 ` Meelis Roos
2016-11-28 18:37 ` Meelis Roos
1 sibling, 0 replies; 16+ messages in thread
From: Meelis Roos @ 2016-11-28 17:39 UTC (permalink / raw)
To: Helge Deller; +Cc: linux-parisc
> > > > > Command line for kernel: 'root=/dev/sda3 console=ttyS0
> > > > > palo_kernel=2/vmlinux'
> > > > > Selected kernel: /vmlinux from partition 2
> > > >
> > > > I'm missing here the information of the various sections
> > > > in the vmlinux file which the boot loader usually prints
> > > > here.
> > >
> > > Well, I did not leave anything out AFAIK?
> >
> > It seems palo can't read the vmlinux file (aka get's confused with the contents
> > and doesn't print the ELF section list).
> >
> > Did you maybe used a recent binutils package?
> > See:
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=845690
> > https://sourceware.org/ml/binutils/2016-11/msg00348.html
> >
> > Maybe downgrading binutils helps?
>
> Sorry, I just noticed that you are pretty aware of this bug
> (you actually opened the ticket) :-)
Yes, but I did not understand it would affect parisc, since the problem
_seemed_ to be amd64-specific. But looking at the description, it might
well be related.
However, I seem to have installed version 2.25.1-r1 that seems to be
from Oct 3 2015 and thus is not likely to have this change.
There is also sys-devel/binutils-hppa64-2.25.1 that is probably used for
the 64-bit kernel, but this is emerged Jul 6 2016 and packaged Sep 30
2015.
In summary it seems my binutils last changed in July 2016, but
4.8.0 kernel was compile on Oct 5 2016, with the same binutils as I am
using now.
So, any other ideas?
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-11-28 18:37 ` Meelis Roos
2016-11-28 17:30 ` John David Anglin
@ 2016-11-28 18:05 ` Helge Deller
2016-11-28 18:09 ` Helge Deller
1 sibling, 1 reply; 16+ messages in thread
From: Helge Deller @ 2016-11-28 18:05 UTC (permalink / raw)
To: Meelis Roos; +Cc: linux-parisc
On 28.11.2016 19:37, Meelis Roos wrote:
>>>>>> Command line for kernel: 'root=/dev/sda3 console=ttyS0
>>>>>> palo_kernel=2/vmlinux'
>>>>>> Selected kernel: /vmlinux from partition 2
>>>>>
>>>>> I'm missing here the information of the various sections
>>>>> in the vmlinux file which the boot loader usually prints
>>>>> here.
>>>>
>>>> Well, I did not leave anything out AFAIK?
>>>
>>> It seems palo can't read the vmlinux file (aka get's confused with the contents
>>> and doesn't print the ELF section list).
>>>
>>> Did you maybe used a recent binutils package?
>
> Old binutils, but here is my vmlinux that does not boot (slightly larger
> than vmlinux-4.8.0):
>
> http://kodu.ut.ee/~mroos/vmlinux-4.9.0-rc6-00240-gd8e435f
This kernel boots nicely for me on my c3000 machine:
Main Menu: Enter command > bo pri
Interact with IPL (Y, N, Q)?> y
Booting...
Boot IO Dependent Code (IODC) revision 0
HARD Booted.
palo ipl 1.96 http://www.parisc-linux.org - Sun, 08 Oct 2016 22:40:31 +0100
Skipping extended partition 6 - beyond reach of IPL
Partition Start(MB) End(MB) Id Type
1 2 33 f0 Palo
2 34 157 83 ext2
5 159 134887 83 ext2
PALO(F0) partition contains:
0/vmlinux64 17631904(0) bytes @ 0x140000
Information: No console specified on kernel command line. This is normal.
PALO will choose the console currently used by firmware (serial).Current command line:
2/vmlinux root=LABEL=ROOT rootfstype=ext4 initrd=2/initrd.img HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102
...
Current command line:
2/vmlinux-4.9.0-rc6-00240-gd8e435f root=LABEL=ROOT rootfstype=ext4 HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102
0: 2/vmlinux-4.9.0-rc6-00240-gd8e435f
1: root=LABEL=ROOT
2: rootfstype=ext4
3: HOME=/
4: panic_timeout=60
5: panic=-1
6: console=ttyS0
7: TERM=vt102
<#> edit the numbered field
'b' boot with this command line
'r' restore command line
'l' list dir
'x' reset and reboot machine
? b
Command line for kernel: 'root=LABEL=ROOT rootfstype=ext4 HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102 palo_kernel=2/vmlinux-4.9.0-rc6-'
Selected kernel: /vmlinux-4.9.0-rc6-00240-gd8e435f from partition 2
ELF64 executable
Entry 00100000 first 00100000 n 5
Segment 0 load 00100000 size 134688 mediaptr 0x1000
Segment 1 load 00121000 size 22272 mediaptr 0x22000
Segment 2 load 00200000 size 4456864 mediaptr 0x28000
Segment 3 load 00641000 size 1387492 mediaptr 0x469000
Segment 4 load 00800000 size 1084600 mediaptr 0x5bc000
Branching to kernel entry point 0x00100000. If this is the last
message you see, you may need to switch your console. This is
a common symptom -- search the FAQ and mailing list at parisc-linux.org
Linux version 4.9.0-rc6-00240-gd8e435f (mroos@a500) (gcc version 5.4.0 (Gentoo 5.4.0 p1.0) ) #104 Sun Nov 27 16:30:20 EET 2016
unwind_init: start = 0x4075a444, end = 0x40793be4, entries = 14714
FP[0] enabled: Rev 1 Model 19
The 64-bit Kernel has started...
Kernel default page size is 4 KB. Huge pages enabled with 1 MB physical and 2 MB virtual size.
bootconsole [ttyB0] enabled
Initialized PDC Console for debugging.
Determining PDC firmware type: System Map.
model 00005dc0 00000481 00000000 00000002 777c3e84 100000f0 00000008 000000b2 000000b2
vers 00000301
CPUID vers 19 rev 11 (0x0000026b)
capabilities 0x7
model 9000/785/C3700
...
Helge
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-11-28 18:05 ` Helge Deller
@ 2016-11-28 18:09 ` Helge Deller
2016-11-28 20:23 ` Meelis Roos
0 siblings, 1 reply; 16+ messages in thread
From: Helge Deller @ 2016-11-28 18:09 UTC (permalink / raw)
To: Meelis Roos; +Cc: linux-parisc
On 28.11.2016 19:05, Helge Deller wrote:
> On 28.11.2016 19:37, Meelis Roos wrote:
>>>>>>> Command line for kernel: 'root=/dev/sda3 console=ttyS0
>>>>>>> palo_kernel=2/vmlinux'
>>>>>>> Selected kernel: /vmlinux from partition 2
>>>>>>
>>>>>> I'm missing here the information of the various sections
>>>>>> in the vmlinux file which the boot loader usually prints
>>>>>> here.
>>>>>
>>>>> Well, I did not leave anything out AFAIK?
>>>>
>>>> It seems palo can't read the vmlinux file (aka get's confused with the contents
>>>> and doesn't print the ELF section list).
>>>>
>>>> Did you maybe used a recent binutils package?
>>
>> Old binutils, but here is my vmlinux that does not boot (slightly larger
>> than vmlinux-4.8.0):
>>
>> http://kodu.ut.ee/~mroos/vmlinux-4.9.0-rc6-00240-gd8e435f
>
> This kernel boots nicely for me on my c3000 machine:
>
> Main Menu: Enter command > bo pri
> Interact with IPL (Y, N, Q)?> y
>
> Booting...
> Boot IO Dependent Code (IODC) revision 0
>
>
> HARD Booted.
> palo ipl 1.96 http://www.parisc-linux.org - Sun, 08 Oct 2016 22:40:31 +0100
> Skipping extended partition 6 - beyond reach of IPL
>
> Partition Start(MB) End(MB) Id Type
> 1 2 33 f0 Palo
> 2 34 157 83 ext2
> 5 159 134887 83 ext2
>
> PALO(F0) partition contains:
> 0/vmlinux64 17631904(0) bytes @ 0x140000
>
> Information: No console specified on kernel command line. This is normal.
> PALO will choose the console currently used by firmware (serial).Current command line:
> 2/vmlinux root=LABEL=ROOT rootfstype=ext4 initrd=2/initrd.img HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102
The only differences I currently see between your and my setup are:
1. My palo partition contains a vmlinux file (you need to add a vmlinux file to your /etc/palo.conf file and rerun "palo -v").
2. In my setup I didn't added "console=ttyS0". palo does that by itself if you run via serial console.
I'm not confident that those are the problem, but you may try...
Helge
> ...
> Current command line:
> 2/vmlinux-4.9.0-rc6-00240-gd8e435f root=LABEL=ROOT rootfstype=ext4 HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102
> 0: 2/vmlinux-4.9.0-rc6-00240-gd8e435f
> 1: root=LABEL=ROOT
> 2: rootfstype=ext4
> 3: HOME=/
> 4: panic_timeout=60
> 5: panic=-1
> 6: console=ttyS0
> 7: TERM=vt102
>
> <#> edit the numbered field
> 'b' boot with this command line
> 'r' restore command line
> 'l' list dir
> 'x' reset and reboot machine
> ? b
>
> Command line for kernel: 'root=LABEL=ROOT rootfstype=ext4 HOME=/ panic_timeout=60 panic=-1 console=ttyS0 TERM=vt102 palo_kernel=2/vmlinux-4.9.0-rc6-'
> Selected kernel: /vmlinux-4.9.0-rc6-00240-gd8e435f from partition 2
> ELF64 executable
> Entry 00100000 first 00100000 n 5
> Segment 0 load 00100000 size 134688 mediaptr 0x1000
> Segment 1 load 00121000 size 22272 mediaptr 0x22000
> Segment 2 load 00200000 size 4456864 mediaptr 0x28000
> Segment 3 load 00641000 size 1387492 mediaptr 0x469000
> Segment 4 load 00800000 size 1084600 mediaptr 0x5bc000
> Branching to kernel entry point 0x00100000. If this is the last
> message you see, you may need to switch your console. This is
> a common symptom -- search the FAQ and mailing list at parisc-linux.org
>
> Linux version 4.9.0-rc6-00240-gd8e435f (mroos@a500) (gcc version 5.4.0 (Gentoo 5.4.0 p1.0) ) #104 Sun Nov 27 16:30:20 EET 2016
> unwind_init: start = 0x4075a444, end = 0x40793be4, entries = 14714
> FP[0] enabled: Rev 1 Model 19
> The 64-bit Kernel has started...
> Kernel default page size is 4 KB. Huge pages enabled with 1 MB physical and 2 MB virtual size.
> bootconsole [ttyB0] enabled
> Initialized PDC Console for debugging.
> Determining PDC firmware type: System Map.
> model 00005dc0 00000481 00000000 00000002 777c3e84 100000f0 00000008 000000b2 000000b2
> vers 00000301
> CPUID vers 19 rev 11 (0x0000026b)
> capabilities 0x7
> model 9000/785/C3700
> ...
>
> Helge
>
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-11-28 15:40 ` Helge Deller
2016-11-28 17:39 ` Meelis Roos
@ 2016-11-28 18:37 ` Meelis Roos
2016-11-28 17:30 ` John David Anglin
2016-11-28 18:05 ` Helge Deller
1 sibling, 2 replies; 16+ messages in thread
From: Meelis Roos @ 2016-11-28 18:37 UTC (permalink / raw)
To: Helge Deller; +Cc: linux-parisc
> > > > > Command line for kernel: 'root=/dev/sda3 console=ttyS0
> > > > > palo_kernel=2/vmlinux'
> > > > > Selected kernel: /vmlinux from partition 2
> > > >
> > > > I'm missing here the information of the various sections
> > > > in the vmlinux file which the boot loader usually prints
> > > > here.
> > >
> > > Well, I did not leave anything out AFAIK?
> >
> > It seems palo can't read the vmlinux file (aka get's confused with the contents
> > and doesn't print the ELF section list).
> >
> > Did you maybe used a recent binutils package?
Old binutils, but here is my vmlinux that does not boot (slightly larger
than vmlinux-4.8.0):
http://kodu.ut.ee/~mroos/vmlinux-4.9.0-rc6-00240-gd8e435f
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-11-28 20:23 ` Meelis Roos
@ 2016-11-28 19:41 ` Helge Deller
2016-12-03 21:11 ` Helge Deller
0 siblings, 1 reply; 16+ messages in thread
From: Helge Deller @ 2016-11-28 19:41 UTC (permalink / raw)
To: Meelis Roos; +Cc: linux-parisc
Hi Meelis,
On 28.11.2016 21:23, Meelis Roos wrote:
>> The only differences I currently see between your and my setup are:
>> 1. My palo partition contains a vmlinux file (you need to add a vmlinux file to your /etc/palo.conf file and rerun "palo -v").
>
> I pondered about that - what do you mean...
Inside the palo partition, a vmlinux & initrd file can be stored,
just in case if /boot isn't readable.
Those two files need to be configured in /etc/palo.conf with those parameters:
--recoverykernel=/boot/vmlinux.recovery
--ramdisk=/boot/initrd.recovery
Afterwards you need to run "palo -v" once.
When the IPL loader from palo is started, you can select those kernel/initrd files
via partition "0", e.g. 0/vmlinux and 0/initrd.
partition 1 is the palo partition, partition 2 is usually the /boot (ext2) partition.
It's a fallback solution for booting a system.
> and then it dawned on me - I have wrong symlink under /boot. On most
> machines I have symlink named test that points to my latest test kernel,
> but on parisc I had default vmlinux since installerkenl worked out of
> the box with it. So it just worked, until I removed vmlinux and created
> "test" symlink by mistake whern testing 4.9-rc*. Now I recreated the
> vmlinux symlink and the new kernels just work.
>
> So it was a bad user error my side, probably from staying up too late
> some day :)
>
> However, palo seems to miss error handling in that case.
Agreed, I'll try to fix that.
>> 2. In my setup I didn't added "console=ttyS0". palo does that by itself if you run via serial console.
>
> Yes, I removed it and serial console just keeps working.
Ok.
> Thank you!
No problem.
Helge
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-11-28 18:09 ` Helge Deller
@ 2016-11-28 20:23 ` Meelis Roos
2016-11-28 19:41 ` Helge Deller
0 siblings, 1 reply; 16+ messages in thread
From: Meelis Roos @ 2016-11-28 20:23 UTC (permalink / raw)
To: Helge Deller; +Cc: linux-parisc
> The only differences I currently see between your and my setup are:
> 1. My palo partition contains a vmlinux file (you need to add a vmlinux file to your /etc/palo.conf file and rerun "palo -v").
I pondered about that - what do you mean...
and then it dawned on me - I have wrong symlink under /boot. On most
machines I have symlink named test that points to my latest test kernel,
but on parisc I had default vmlinux since installerkenl worked out of
the box with it. So it just worked, until I removed vmlinux and created
"test" symlink by mistake whern testing 4.9-rc*. Now I recreated the
vmlinux symlink and the new kernels just work.
So it was a bad user error my side, probably from staying up too late
some day :)
However, palo seems to miss error handling in that case.
> 2. In my setup I didn't added "console=ttyS0". palo does that by itself if you run via serial console.
Yes, I removed it and serial console just keeps working.
Thank you!
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-11-28 19:41 ` Helge Deller
@ 2016-12-03 21:11 ` Helge Deller
2016-12-05 10:22 ` Meelis Roos
0 siblings, 1 reply; 16+ messages in thread
From: Helge Deller @ 2016-12-03 21:11 UTC (permalink / raw)
To: Meelis Roos; +Cc: null
Hi Meelis,
On 28.11.2016 20:41, Helge Deller wrote:
>> and then it dawned on me - I have wrong symlink under /boot. On most
>> machines I have symlink named test that points to my latest test kernel,
>> but on parisc I had default vmlinux since installerkenl worked out of
>> the box with it. So it just worked, until I removed vmlinux and created
>> "test" symlink by mistake whern testing 4.9-rc*. Now I recreated the
>> vmlinux symlink and the new kernels just work.
>>
>> So it was a bad user error my side, probably from staying up too late
>> some day :)
>>
>> However, palo seems to miss error handling in that case.
>
> Agreed, I'll try to fix that.
I just tried to fix this problem, but could not reproduce it.
Can you explain exactly how your symlinks looked like ?
E.g. a "ls -la" output of /boot ?
Were they hardlinks ?
Can you still reproduce the problem with latest palo 1.96 ?
Thanks!
Helge
^ permalink raw reply [flat|nested] 16+ messages in thread
* Re: Aw: Re: parsic: strange boot crash on a500
2016-12-03 21:11 ` Helge Deller
@ 2016-12-05 10:22 ` Meelis Roos
0 siblings, 0 replies; 16+ messages in thread
From: Meelis Roos @ 2016-12-05 10:22 UTC (permalink / raw)
To: Helge Deller; +Cc: null
> >> and then it dawned on me - I have wrong symlink under /boot. On most
> >> machines I have symlink named test that points to my latest test kernel,
> >> but on parisc I had default vmlinux since installerkenl worked out of
> >> the box with it. So it just worked, until I removed vmlinux and created
> >> "test" symlink by mistake whern testing 4.9-rc*. Now I recreated the
> >> vmlinux symlink and the new kernels just work.
> >>
> >> So it was a bad user error my side, probably from staying up too late
> >> some day :)
> >>
> >> However, palo seems to miss error handling in that case.
> >
> > Agreed, I'll try to fix that.
>
> I just tried to fix this problem, but could not reproduce it.
> Can you explain exactly how your symlinks looked like ?
vmlinux and vmlinux.old are symlinks in /boot, with no path, just
pointing to vmlinux-... files. In the problematic case, there was no
vmlinux symlink, just "test" symlink that palo did not know anything
about.
> E.g. a "ls -la" output of /boot ?
Current one is
-rw-r--r-- 1 root root 1037705 Jul 1 2013 System.map-3.10.0
-rw-r--r-- 1 root root 1050543 Oct 8 2013 System.map-3.11.0
-rw-r--r-- 1 root root 1046172 Jun 9 2014 System.map-3.15.0
-rw-r--r-- 1 root root 1053608 Aug 12 2014 System.map-3.16.0
-rw-r--r-- 1 root root 1068795 Dec 8 2014 System.map-3.18.0
-rw-r--r-- 1 root root 1080097 Mar 9 2015 System.map-3.19.0
-rw-r--r-- 1 root root 1083003 Apr 15 2015 System.map-4.0.0
-rw-r--r-- 1 root root 1087981 Jun 26 2015 System.map-4.1.0
-rw-r--r-- 1 root root 1119899 Sep 1 2015 System.map-4.2.0
-rw-r--r-- 1 root root 777767 Jul 29 19:23 System.map-4.7.0
-rw-r--r-- 1 root root 783238 Oct 5 20:50 System.map-4.8.0
-rw-r--r-- 1 root root 792511 Nov 25 23:24 System.map-4.9.0-rc5-00297-g20afa6e
-rw-r--r-- 1 root root 798408 Nov 27 21:25 System.map-4.9.0-rc6-00240-gd8e435f
-rw-r--r-- 1 root root 798408 Nov 28 20:39 System.map-4.9.0-rc7
-rw-r--r-- 1 root root 798539 Dec 5 09:39 System.map-4.9.0-rc7-00198-g0cb65c8
-rw-r--r-- 1 root root 0 Jun 2 2014 System.map-dummy
-rw-r--r-- 1 root root 33032 Jul 1 2013 config-3.10.0
-rw-r--r-- 1 root root 33555 Oct 8 2013 config-3.11.0
-rw-r--r-- 1 root root 34596 Aug 12 2014 config-3.16.0
-rw-r--r-- 1 root root 35356 Dec 8 2014 config-3.18.0
-rw-r--r-- 1 root root 35788 Mar 9 2015 config-3.19.0
-rw-r--r-- 1 root root 35945 Apr 15 2015 config-4.0.0
-rw-r--r-- 1 root root 35930 Jun 26 2015 config-4.1.0
-rw-r--r-- 1 root root 32036 Sep 1 2015 config-4.2.0
-rw-r--r-- 1 root root 34196 Jul 29 19:23 config-4.7.0
-rw-r--r-- 1 root root 34342 Oct 5 20:50 config-4.8.0
-rw-r--r-- 1 root root 34725 Nov 25 23:24 config-4.9.0-rc5-00297-g20afa6e
-rw-r--r-- 1 root root 35044 Nov 27 21:25 config-4.9.0-rc6-00240-gd8e435f
-rw-r--r-- 1 root root 35044 Nov 28 20:39 config-4.9.0-rc7
-rw-r--r-- 1 root root 35076 Dec 5 09:39 config-4.9.0-rc7-00198-g0cb65c8
drwx------ 2 root root 12288 Nov 6 2012 lost+found
lrwxrwxrwx 1 root root 32 Dec 5 09:39 vmlinux -> vmlinux-4.9.0-rc7-00198-g0cb65c8
-rw-r--r-- 1 root root 7177406 Jul 1 2013 vmlinux-3.10.0
-rw-r--r-- 1 root root 7267400 Oct 8 2013 vmlinux-3.11.0
-rw-r--r-- 1 root root 7620429 Aug 12 2014 vmlinux-3.16.0
-rw-r--r-- 1 root root 7749731 Dec 8 2014 vmlinux-3.18.0
-rw-r--r-- 1 root root 7795213 Mar 9 2015 vmlinux-3.19.0
-rw-r--r-- 1 root root 7815201 Apr 15 2015 vmlinux-4.0.0
-rw-r--r-- 1 root root 7846008 Jun 26 2015 vmlinux-4.1.0
-rw-r--r-- 1 root root 8022604 Sep 1 2015 vmlinux-4.2.0
-rw-r--r-- 1 root root 7827216 Jul 29 19:23 vmlinux-4.7.0
-rw-r--r-- 1 root root 7882632 Oct 5 20:50 vmlinux-4.8.0
-rw-r--r-- 1 root root 8022800 Nov 25 23:24 vmlinux-4.9.0-rc5-00297-g20afa6e
-rw-r--r-- 1 root root 8071224 Nov 27 21:25 vmlinux-4.9.0-rc6-00240-gd8e435f
-rw-r--r-- 1 root root 8071224 Nov 28 20:39 vmlinux-4.9.0-rc7
-rw-r--r-- 1 root root 8071400 Dec 5 09:39 vmlinux-4.9.0-rc7-00198-g0cb65c8
lrwxrwxrwx 1 root root 17 Nov 28 20:39 vmlinux.old -> vmlinux-4.9.0-rc7
palo.conf:
# Please read the palo --help output for more info
# Non-commented lines are treated as command line arguments
--commandline=2/vmlinux root=/dev/sda3
--init-partitioned=/dev/sda
#Uncomment this if you want a rescue kernel
#--recoverykernel=/boot/vmlinux.old
> Were they hardlinks ?
No.
> Can you still reproduce the problem with latest palo 1.96 ?
Yes - just did "rm vmlinux" from the above state and rebooted and it
crashed like before.
--
Meelis Roos (mroos@linux.ee)
^ permalink raw reply [flat|nested] 16+ messages in thread
end of thread, other threads:[~2016-12-05 10:22 UTC | newest]
Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-11-26 0:13 parsic: strange boot crash on a500 Meelis Roos
2016-11-26 9:12 ` Helge Deller
2016-11-27 21:35 ` Meelis Roos
2016-11-27 20:37 ` Helge Deller
2016-11-27 23:45 ` Meelis Roos
2016-11-28 15:36 ` Aw: " Helge Deller
2016-11-28 15:40 ` Helge Deller
2016-11-28 17:39 ` Meelis Roos
2016-11-28 18:37 ` Meelis Roos
2016-11-28 17:30 ` John David Anglin
2016-11-28 18:05 ` Helge Deller
2016-11-28 18:09 ` Helge Deller
2016-11-28 20:23 ` Meelis Roos
2016-11-28 19:41 ` Helge Deller
2016-12-03 21:11 ` Helge Deller
2016-12-05 10:22 ` Meelis Roos
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.