> >> 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@xxxxxxxx) -- To unsubscribe from this list: send the line "unsubscribe linux-parisc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
