Re: Segmentation faults with aptitude and apt-get on some packages
I kinda figured that. I was trying to be clear in case someone else was following along. My question still is, is it necessary to run "update-initramfs -c -k 4.8.11" if "make install" performs that function? Does make install do the same thing as the update-initramfs command or do they do something different. Either way running "make install" and pointing image=/boot/vmlinuz-4.8.11 works. It now boots and uname-r returns 4.8.11. Now to see if it has eliminated the segfault I got when trying to access webmin (don't know if it's localized to webmin but it's what I was working on when this came up. Thanks for the help. Rod On 12/2/2016 1:00 PM, John Paul Adrian Glaubitz wrote: > You don't need to go through all steps again. Just "make install" is enough. > Unless you call "make clean", the compiled files and kernel are still in the > kernel's source directory. > > Adrian > >> On Dec 2, 2016, at 7:45 PM, rod wrote: >> >>> On 12/2/2016 12:13 PM, John Paul Adrian Glaubitz wrote: >>> Did you run "make install" in the kernel's source directory after building >>> kernel or did I forget mentioning it? >>> >>> Adrian >>> >>> PS: Sorry for the bad quoting style. Currently on mobile. >>> > On Dec 2, 2016, at 7:05 PM, rod wrote: > > On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote: > Change the first SILO entry to: > > image=/boot/vmlinuz-4.8.11 > label=Linux > initrd=/boot/initrd.img-4.8.11 > > You simply forgot to modify silo.conf to point to the correct kernel and > initrd. > > Currently it's configured to boot "vmlinuz" from the system's root > directory which is most likely a symlink to a kernel in /boot (check "ls > -l /vmlinuz") and use /initrd-4.8.11 as the initrd which is probably a > symlink as well. > > Adrian > >> On Dec 2, 2016, at 6:32 PM, rod wrote: >> >> image=/vmlinuz >> label=Linux >> initrd=/initrd.img-4.8.11 I noticed that whilst typing the email and have gone looking for vmlinuz-4.8.11. It's not in /boot and updatedb/locate doesn't show one on the system symlinked or otherwise. Did we not create it somehow? Is it supposed to be created when the kernel is built? Building kernels is fun! ;) >>> >> I did make "modules_install" but not "make install". >> >> $ cd linux-4.8.11 >> $ cp -av /boot/config-$(uname -r) . >> $ make oldconfig (Just always until the prompt comes back) >> $ make && make modules_install >> $ update-initramfs -c -k 4.8.11 >> >> If I run "make install" it appears to run update-initramfs >> automatically. So is the last line not needed? >> >> Personally I'd rather top reply. I find it easier to see new comments >> that way. No big deal either way. >> >> Rod >
Re: Segmentation faults with aptitude and apt-get on some packages
You don't need to go through all steps again. Just "make install" is enough. Unless you call "make clean", the compiled files and kernel are still in the kernel's source directory. Adrian > On Dec 2, 2016, at 7:45 PM, rod wrote: > >> On 12/2/2016 12:13 PM, John Paul Adrian Glaubitz wrote: >> Did you run "make install" in the kernel's source directory after building >> kernel or did I forget mentioning it? >> >> Adrian >> >> PS: Sorry for the bad quoting style. Currently on mobile. >> On Dec 2, 2016, at 7:05 PM, rod wrote: On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote: Change the first SILO entry to: image=/boot/vmlinuz-4.8.11 label=Linux initrd=/boot/initrd.img-4.8.11 You simply forgot to modify silo.conf to point to the correct kernel and initrd. Currently it's configured to boot "vmlinuz" from the system's root directory which is most likely a symlink to a kernel in /boot (check "ls -l /vmlinuz") and use /initrd-4.8.11 as the initrd which is probably a symlink as well. Adrian > On Dec 2, 2016, at 6:32 PM, rod wrote: > > image=/vmlinuz > label=Linux > initrd=/initrd.img-4.8.11 >>> >>> >>> I noticed that whilst typing the email and have gone looking for >>> vmlinuz-4.8.11. >>> >>> It's not in /boot and updatedb/locate doesn't show one on the system >>> symlinked or otherwise. >>> >>> Did we not create it somehow? Is it supposed to be created when the >>> kernel is built? >>> >>> Building kernels is fun! ;) >> > I did make "modules_install" but not "make install". > > $ cd linux-4.8.11 > $ cp -av /boot/config-$(uname -r) . > $ make oldconfig (Just always until the prompt comes back) > $ make && make modules_install > $ update-initramfs -c -k 4.8.11 > > If I run "make install" it appears to run update-initramfs > automatically. So is the last line not needed? > > Personally I'd rather top reply. I find it easier to see new comments > that way. No big deal either way. > > Rod
Re: Segmentation faults with aptitude and apt-get on some packages
On 12/2/2016 12:13 PM, John Paul Adrian Glaubitz wrote: > Did you run "make install" in the kernel's source directory after building > kernel or did I forget mentioning it? > > Adrian > > PS: Sorry for the bad quoting style. Currently on mobile. > >> On Dec 2, 2016, at 7:05 PM, rod wrote: >> >>> On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote: >>> Change the first SILO entry to: >>> >>> image=/boot/vmlinuz-4.8.11 >>> label=Linux >>> initrd=/boot/initrd.img-4.8.11 >>> >>> You simply forgot to modify silo.conf to point to the correct kernel and >>> initrd. >>> >>> Currently it's configured to boot "vmlinuz" from the system's root >>> directory which is most likely a symlink to a kernel in /boot (check "ls -l >>> /vmlinuz") and use /initrd-4.8.11 as the initrd which is probably a symlink >>> as well. >>> >>> Adrian >>> On Dec 2, 2016, at 6:32 PM, rod wrote: image=/vmlinuz label=Linux initrd=/initrd.img-4.8.11 >> >> >> I noticed that whilst typing the email and have gone looking for >> vmlinuz-4.8.11. >> >> It's not in /boot and updatedb/locate doesn't show one on the system >> symlinked or otherwise. >> >> Did we not create it somehow? Is it supposed to be created when the >> kernel is built? >> >> Building kernels is fun! ;) > I did make "modules_install" but not "make install". $ cd linux-4.8.11 $ cp -av /boot/config-$(uname -r) . $ make oldconfig (Just always until the prompt comes back) $ make && make modules_install $ update-initramfs -c -k 4.8.11 If I run "make install" it appears to run update-initramfs automatically. So is the last line not needed? Personally I'd rather top reply. I find it easier to see new comments that way. No big deal either way. Rod
Re: Segmentation faults with aptitude and apt-get on some packages
Did you run "make install" in the kernel's source directory after building kernel or did I forget mentioning it? Adrian PS: Sorry for the bad quoting style. Currently on mobile. > On Dec 2, 2016, at 7:05 PM, rod wrote: > >> On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote: >> Change the first SILO entry to: >> >> image=/boot/vmlinuz-4.8.11 >> label=Linux >> initrd=/boot/initrd.img-4.8.11 >> >> You simply forgot to modify silo.conf to point to the correct kernel and >> initrd. >> >> Currently it's configured to boot "vmlinuz" from the system's root directory >> which is most likely a symlink to a kernel in /boot (check "ls -l /vmlinuz") >> and use /initrd-4.8.11 as the initrd which is probably a symlink as well. >> >> Adrian >> >>> On Dec 2, 2016, at 6:32 PM, rod wrote: >>> >>> image=/vmlinuz >>> label=Linux >>> initrd=/initrd.img-4.8.11 > > > I noticed that whilst typing the email and have gone looking for > vmlinuz-4.8.11. > > It's not in /boot and updatedb/locate doesn't show one on the system > symlinked or otherwise. > > Did we not create it somehow? Is it supposed to be created when the > kernel is built? > > Building kernels is fun! ;)
Re: Segmentation faults with aptitude and apt-get on some packages
On 12/2/2016 11:51 AM, John Paul Adrian Glaubitz wrote: > Change the first SILO entry to: > > image=/boot/vmlinuz-4.8.11 >label=Linux >initrd=/boot/initrd.img-4.8.11 > > You simply forgot to modify silo.conf to point to the correct kernel and > initrd. > > Currently it's configured to boot "vmlinuz" from the system's root directory > which is most likely a symlink to a kernel in /boot (check "ls -l /vmlinuz") > and use /initrd-4.8.11 as the initrd which is probably a symlink as well. > > Adrian > >> On Dec 2, 2016, at 6:32 PM, rod wrote: >> >> image=/vmlinuz >>label=Linux >>initrd=/initrd.img-4.8.11 I noticed that whilst typing the email and have gone looking for vmlinuz-4.8.11. It's not in /boot and updatedb/locate doesn't show one on the system symlinked or otherwise. Did we not create it somehow? Is it supposed to be created when the kernel is built? Building kernels is fun! ;)
Re: Segmentation faults with aptitude and apt-get on some packages
Change the first SILO entry to: image=/boot/vmlinuz-4.8.11 label=Linux initrd=/boot/initrd.img-4.8.11 You simply forgot to modify silo.conf to point to the correct kernel and initrd. Currently it's configured to boot "vmlinuz" from the system's root directory which is most likely a symlink to a kernel in /boot (check "ls -l /vmlinuz") and use /initrd-4.8.11 as the initrd which is probably a symlink as well. Adrian > On Dec 2, 2016, at 6:32 PM, rod wrote: > > image=/vmlinuz >label=Linux >initrd=/initrd.img-4.8.11
Re: Segmentation faults with aptitude and apt-get on some packages
On 12/2/2016 9:50 AM, John Paul Adrian Glaubitz wrote: > On 12/02/2016 04:35 PM, rod wrote: >> [0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 4.22.33 2007/06/18 12:45' >> [0.00] PROMLIB: Root node compatible: >> [0.00] Linux version 4.8.0-1-sparc64-smp >> (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian >> 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13) > > This does not look like a kernel that you built yourself. Note the date > when it was built and which compiler was used. If you had built it > directly from source and without going through any Debian-specific > steps, the kernel version would not include "Debian" and would be > built with gcc-6. Also, the date would be around the past days. > >> Gave up waiting for root device. Common problems: >> - Boot args (cat /proc/cmdline) >>- Check rootdelay= (did the system wait long enough?) >>- Check root= (did the system wait for the right device?) >> - Missing modules (cat /proc/modules; ls /dev) >> ALERT! /dev/sda4 does not exist. Dropping to a shell! > > It's missing the drivers for your disk controllers. Are you sure > you built the initrd properly and that the SILO entry for "Linux" > points to the correct kernel and initrd? > > Adrian > I'm not sure about anything when it comes to this. Mostly it's new. I follow directions and read about what I don't understand so I CAN understand whats going on. I built the kernel following these directions (with Anatoly's modification of 'make olddefconfig' because I was being lazy in not wanting to hit ENTER alot. That may be my mistake and I will go back and try it with 'make oldconfig' just to be sure...): $ apt update $ apt-get build-dep linux $ cd /usr/src/ $ wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.8.11.tar.xz $ tar xf linux-4.8.11.tar.xz $ cd linux-4.8.11 $ cp -av /boot/config-$(uname -r) $ make oldconfig (Just always until the prompt comes back) $ make && make modules_install $ update-initramfs -c -k 4.8.11 The build went fine (as near as I can tell) and the tail end of the output is below: INSTALL /lib/firmware/edgeport/down2.fw INSTALL /lib/firmware/edgeport/down3.bin INSTALL /lib/firmware/whiteheat_loader.fw INSTALL /lib/firmware/whiteheat.fw INSTALL /lib/firmware/keyspan_pda/keyspan_pda.fw INSTALL /lib/firmware/keyspan_pda/xircom_pgs.fw INSTALL /lib/firmware/cpia2/stv0672_vp4.bin DEPMOD 4.8.11 root@mw-monitor:/usr/src/linux-4.8.11# update-initramfs -c -k 4.8.11 update-initramfs: Generating /boot/initrd.img-4.8.11 cp: cannot stat '/etc/modprobe.d/*': No such file or directory root@mw-monitor:/usr/src/linux-4.8.11# nano /etc/silo.conf silo.conf now looks like this: root=/dev/sda4 partition=1 default=Linux read-only timeout=100 image=/vmlinuz label=Linux initrd=/initrd.img-4.8.11 image=/vmlinuz label=LinuxWORKING initrd=/initrd.img image=/vmlinuz.old label=LinuxOLD initrd=/initrd.img.old and /boot has the following: root@mw-monitor:/usr/src# ls -la /boot total 225820 drwxr-xr-x 3 root root 4096 Dec 2 09:00 . drwxr-xr-x 23 root root 4096 Nov 29 13:08 .. lrwxrwxrwx 1 root root 1 Nov 29 09:50 boot -> . -rw-r--r-- 1 root root127403 Apr 30 2016 config-4.5.0-2-sparc64-smp -rw-r--r-- 1 root root131092 Nov 12 22:38 config-4.8.0-1-sparc64-smp lrwxrwxrwx 1 root root 1 Nov 29 09:50 etc -> . -rw-r--r-- 1 root root 1024 Jan 22 2016 fd.b -rw-r--r-- 1 root root 512 Jan 22 2016 first.b -rw-r--r-- 1 root root 1024 Jan 22 2016 generic.b -rw-r--r-- 1 root root 800 Jan 22 2016 ieee32.b lrwxrwxrwx 1 root root30 Nov 29 11:28 initrd.img -> initrd.img-4.8.0-1-sparc64-smp -rw-r--r-- 1 root root 17087722 Nov 29 11:07 initrd.img-4.5.0-2-sparc64-smp -rw-r--r-- 1 root root 17459632 Nov 29 13:10 initrd.img-4.8.0-1-sparc64-smp -rw-r--r-- 1 root root 183723635 Dec 2 09:00 initrd.img-4.8.11 lrwxrwxrwx 1 root root30 Nov 29 11:28 initrd.img.old -> initrd.img-4.5.0-2-sparc64-smp -rw-r--r-- 1 root root 6752 Jan 22 2016 isofs.b drwx-- 2 root root 16384 Nov 29 09:13 lost+found -rw-r--r-- 1 root root 7680 Nov 29 09:50 old.b -rw-r--r-- 1 root root 53760 Nov 29 09:50 second.b -rw-r--r-- 1 root root 235 Dec 2 09:02 silo.conf -rw-r--r-- 1 root root 51437 Jan 22 2016 silotftp.b -rw-r--r-- 1 root root 2314500 Apr 30 2016 System.map-4.5.0-2-sparc64-smp -rw-r--r-- 1 root root 2388680 Nov 12 22:38 System.map-4.8.0-1-sparc64-smp -rw-r--r-- 1 root root 512 Jan 22 2016 ultra.b lrwxrwxrwx 1 root root27 Nov 29 11:28 vmlinuz -> vmlinuz-4.8.0-1-sparc64-smp -rw-r--r-- 1 root root 3715429 Apr 30 2016 vmlinuz-4.5.0-2-sparc64-smp -rw-r--r-- 1 root root 3824109 Nov 12 22:38 vmlinuz-4.8.0-1-sparc64-smp lrwxrwxrwx 1 root root27 Nov 29 11:28 vmlinuz.old -> vmlinuz-4.5.0-2-sparc64-smp looking at the directory I'm wondering; 1) do I need to change the li
Re: Segmentation faults with aptitude and apt-get on some packages
On 12/02/2016 04:35 PM, rod wrote: > [0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 4.22.33 2007/06/18 12:45' > [0.00] PROMLIB: Root node compatible: > [0.00] Linux version 4.8.0-1-sparc64-smp > (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian > 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13) This does not look like a kernel that you built yourself. Note the date when it was built and which compiler was used. If you had built it directly from source and without going through any Debian-specific steps, the kernel version would not include "Debian" and would be built with gcc-6. Also, the date would be around the past days. > Gave up waiting for root device. Common problems: > - Boot args (cat /proc/cmdline) >- Check rootdelay= (did the system wait long enough?) >- Check root= (did the system wait for the right device?) > - Missing modules (cat /proc/modules; ls /dev) > ALERT! /dev/sda4 does not exist. Dropping to a shell! It's missing the drivers for your disk controllers. Are you sure you built the initrd properly and that the SILO entry for "Linux" points to the correct kernel and initrd? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/30/2016 2:43 AM, Anatoly Pugachev wrote: >> $ apt update >> $ apt-get build-dep linux >> $ cd /usr/src/ >> $ wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.8.11.tar.xz >> $ tar xf linux-4.8.11.tar.xz >> $ cd linux-4.8.11 >> $ cp -av /boot/config-$(uname -r) >> $ make oldconfig (Just always until the prompt comes back) > > or instead of "make oldconfig" use "make olddefconfig" > without hitting enter on every new kernel option So I'm making progress, of sorts. Learning is coming in bits and pieces. The building of the kernel went well and the adding to silo.conf also went well. I made a new configuration section for the new kernel and it shows up when I press TAB at the boot: prompt. I know this because after making the changes and rebooting the system it dropped me into an (initramfs) prompt. From discussions with Adrian I remembered the TAB option and was able to get back into a working system. Yay!! I rebooted the system with a console cable attached so I could see where it was dying. I got this: (I copied the whole thing in case there are other things that need fixing that I can help test...) Boot device: disk File and args: SILO Version 1.4.14 boot: LinuxLinuxWORKING LinuxOLD boot: Linux Allocated 64 Megs of memory at 0x4000 for kernel Uncompressing image... Loaded kernel version 4.8.7 Loading initial ramdisk (183723635 bytes at 0x120400 phys, 0x40C0 virt)... - [0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 4.22.33 2007/06/18 12:45' [0.00] PROMLIB: Root node compatible: [0.00] Linux version 4.8.0-1-sparc64-smp (debian-ker...@lists.debian.org) (gcc version 5.4.1 20161019 (Debian 5.4.1-3) ) #1 SMP Debian 4.8.7-1 (2016-11-13) [0.00] bootconsole [earlyprom0] enabled [0.00] ARCH: SUN4U [0.00] Ethernet address: 00:03:ba:fa:3b:ed [0.00] MM: PAGE_OFFSET is 0xfff0 (max_phys_bits == 42) [0.00] MM: VMALLOC [0x0001 --> 0x000c] [0.00] MM: VMEMMAP [0x000c --> 0x0018] [0.00] Kernel: Using 3 locked TLB entries for main kernel image. [0.00] Remapping the kernel... done. [0.00] OF stdout device is: /pci@1e,60/isa@7/serial@0,3f8 [0.00] PROM: Built device tree with 124181 bytes of memory. [0.00] Top of RAM: 0x123feee000, Total RAM: 0xffe78000 [0.00] Memory hole size: 70656MB [0.00] Allocated 40960 bytes for kernel page tables. [0.00] Zone ranges: [0.00] Normal [mem 0x-0x00123feedfff] [0.00] Movable zone start for each node [0.00] Early memory node ranges [0.00] node 0: [mem 0x-0x3fff] [0.00] node 0: [mem 0x0002-0x00023fff] [0.00] node 0: [mem 0x0010-0x00103fff] [0.00] node 0: [mem 0x0012-0x00123effdfff] [0.00] node 0: [mem 0x00123f00-0x00123fe5] [0.00] node 0: [mem 0x00123fe9-0x00123fe9] [0.00] node 0: [mem 0x00123fee-0x00123fee7fff] [0.00] node 0: [mem 0x00123feec000-0x00123feedfff] [0.00] Initmem setup node 0 [mem 0x-0x00123feedfff] [0.00] Booting Linux... [0.00] CPU CAPS: [flush,stbar,swap,muldiv,v9,ultra3,mul32,div32] [0.00] CPU CAPS: [v8plus,vis,vis2] [0.00] percpu: Embedded 10 pages/cpu @fff000123f80 s43096 r8192 d30632 u2097152 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 519485 [0.00] Kernel command line: root=/dev/sda4 ro [0.00] PID hash table entries: 4096 (order: 2, 32768 bytes) [0.00] Dentry cache hash table entries: 524288 (order: 9, 4194304 bytes) [0.00] Inode-cache hash table entries: 262144 (order: 8, 2097152 bytes) [0.00] Sorting __ex_table... [0.00] Memory: 3931704K/4192736K available (5704K kernel code, 769K rwdata, 1456K rodata, 488K init, 751K bss, 261032K reserved, 0K cma-reserved) [0.00] Hierarchical RCU implementation. [0.00] Build-time adjustment of leaf fanout to 64. [0.00] RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=2. [0.00] RCU: Adjusting geometry for rcu_fanout_leaf=64, nr_cpu_ids=2 [0.00] NR_IRQS:2048 nr_irqs:2048 1 [ 126.468276] clocksource: stick: mask: 0x max_cycles: 0x2c47f4ee7, max_idle_ns: 440795202497 ns [ 126.588030] clocksource: mult[5355] shift[24] [ 126.644279] clockevent: mult[3126e98] shift[32] [ 126.698795] Console: colour dummy device 80x25 [ 126.752032] console [tty0] enabled [ 126.792767] bootconsole [earlyprom0] disabled [0.00] PROMLIB: Sun IEEE Boot Prom 'OBP 4.22.33 2007/06/18 12:45' [0.00] PROMLIB: Root node compatible: [0.00] Linux version 4.8.0-1-sparc64-smp (debian-ker...@lists.debian.or
Re: Segmentation faults with aptitude and apt-get on some packages
> $ apt update > $ apt-get build-dep linux > $ cd /usr/src/ > $ wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.8.11.tar.xz > $ tar xf linux-4.8.11.tar.xz > $ cd linux-4.8.11 > $ cp -av /boot/config-$(uname -r) > $ make oldconfig (Just always until the prompt comes back) or instead of "make oldconfig" use "make olddefconfig" without hitting enter on every new kernel option
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/29/2016 11:43 PM, John Paul Adrian Glaubitz wrote: > Try: > > $ apt update > $ apt-get build-dep linux > $ cd /usr/src/ > $ wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.8.11.tar.xz > $ tar xf linux-4.8.11.tar.xz > $ cd linux-4.8.11 > $ cp -av /boot/config-$(uname -r) Oops, that should be: cp -av /boot/config-$(uname -r) . of course (the dot "." for the current directory. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/29/2016 11:33 PM, rod wrote: > 1) I have noodled around with this all day (slow day here) and I'm not > any closer to understanding the process to compile the 4.8.11 kernel. If > you could point me to a HOWTO or other documentation by which I can > further my knowledge and understanding of the process I'd be appreciative. Try: $ apt update $ apt-get build-dep linux $ cd /usr/src/ $ wget https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.8.11.tar.xz $ tar xf linux-4.8.11.tar.xz $ cd linux-4.8.11 $ cp -av /boot/config-$(uname -r) $ make oldconfig (Just always until the prompt comes back) $ make && make modules_install $ update-initramfs -c -k 4.8.11 Make sure that one of the entries in /etc/silo.conf points to the correct kernel and initrd. I suggest always having a backup kernel available under a second label. If you look at /etc/silo.conf, the configuration format should be straight-forward to understand. > 2) In looking at the buildd status, have 'we' rebuilt enough of the > packages to safely move the sources.list back to the debian-ports and > away from the snapshot prior to NOV 2? Yes. -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Segmentation faults with aptitude and apt-get on some packages
>> That's a bug I fixed, but it didn’t make it into the 4.8 branch until >> 4.8.10[1]. Unfortunately that’s not yet been packaged for Debian. There >> is 4.9~rc5-1~exp1 in experimental, but I haven’t tried that build, and I >> don’t know if the serious regression of not being able to load kernel >> modules has been fixed. My suggestion would be to try the experimental >> package, but that may fail with a whole load of missing memcpy etc >> symbols, in which case I recommend compiling an upstream version from >> the 4.8 branch (currently 4.8.11[2] is the latest stable release). >> >> Regards, >> James >> >> [1] >> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.8.y&id=51915c6d90704046600414e117d80e6a76ba13e6 >> [2] >> https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tag/?h=v4.8.11 >> > Assuming I understood you correctly, I added experimental to sources and > installed kernel 4.9~rc5-1~exp1. Upon reboot it dropped me into BusyBox > and initramfs prompt. Probably going to turn it off and start from > scratch tomorrow. I'll figure out how to compile the 4.8.11 after I get > a clean install using the snapshot as a starting point. > > Rod > Good afternoon/day/evening, 1) I have noodled around with this all day (slow day here) and I'm not any closer to understanding the process to compile the 4.8.11 kernel. If you could point me to a HOWTO or other documentation by which I can further my knowledge and understanding of the process I'd be appreciative. 2) In looking at the buildd status, have 'we' rebuilt enough of the packages to safely move the sources.list back to the debian-ports and away from the snapshot prior to NOV 2? Rod
Re: Segmentation faults with aptitude and apt-get on some packages
... >> Using the above thread and after installing several packages (apache2, >> mariadb, phpmyadmin, webmin, & shellinabox and their associated >> requirement packages); I got the following crash and had to reboot. ... >> [ 3061.611384] \|/ \|/ >> [ 3061.611384] "@'/ .. \`@" >> [ 3061.611384] /_| \__/ |_\ >> [ 3061.611384] \__U_/ >> [ 3061.611390] dbus-daemon(315): Kernel illegal instruction [#5] >> [ 3061.611398] CPU: 1 PID: 315 Comm: dbus-daemon Tainted: G D >> 4.8.0-1-sparc64-smp #1 Debian 4.8.5-1 >> [ 3061.611402] task: fff00012049564c0 task.stack: fff00012049d >> [ 3061.611406] TSTATE: 004411001606 TPC: 005ca4a8 TNPC: >> 005ca4ac Y: Tainted: G D >> [ 3061.611418] TPC: <__kmalloc_track_caller+0x128/0x200> >> [ 3061.611421] g0: fff000123d154648 g1: 0040 g2: >> g3: c000 >> [ 3061.611423] g4: fff00012049564c0 g5: fff000123edc6000 g6: >> fff00012049d g7: fff000123edc6000 > > That's a bug I fixed, but it didn’t make it into the 4.8 branch until > 4.8.10[1]. Unfortunately that’s not yet been packaged for Debian. There > is 4.9~rc5-1~exp1 in experimental, but I haven’t tried that build, and I > don’t know if the serious regression of not being able to load kernel > modules has been fixed. My suggestion would be to try the experimental > package, but that may fail with a whole load of missing memcpy etc > symbols, in which case I recommend compiling an upstream version from > the 4.8 branch (currently 4.8.11[2] is the latest stable release). > > Regards, > James > > [1] > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.8.y&id=51915c6d90704046600414e117d80e6a76ba13e6 > [2] > https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/tag/?h=v4.8.11 > Assuming I understood you correctly, I added experimental to sources and installed kernel 4.9~rc5-1~exp1. Upon reboot it dropped me into BusyBox and initramfs prompt. Probably going to turn it off and start from scratch tomorrow. I'll figure out how to compile the 4.8.11 after I get a clean install using the snapshot as a starting point. Rod
Re: Segmentation faults with aptitude and apt-get on some packages
> On 28 Nov 2016, at 22:07, rod wrote: >> On 11/18/2016 4:32 PM, John Paul Adrian Glaubitz wrote: >>> On 11/16/2016 06:13 PM, rod wrote: >>> The current problem I'm having is this: >>> >>> root@mw-monitor:/home/rod# aptitude >>> Ouch! Got SIGSEGV, dying.. >>> Segmentation fault >> >> This has turned out to be an issue with libstdc++6 which comes from the gcc-6 >> package which was built with a broken version of binutils. The buildds are >> currently building a fresh gcc-6 package which is being built with a fixed >> version of binutils which should mitigate the problem. >> >> For anyone experiencing the issue, here is a quick workaround to fix apt >> for the time being until the buildds have finished building the new gcc-6 >> package (which should be in around 2-3 hours). >> >> Fix: >> >> $ wget >> http://snapshot.debian.org/archive/debian-ports/20161022T004918Z/pool-sparc64/main/g/gcc-6/gcc-6-base_6.2.0-9_sparc64.deb >> \ >> >> http://snapshot.debian.org/archive/debian-ports/20161022T004918Z/pool-sparc64/main/g/gcc-6/libstdc%2B%2B6_6.2.0-9_sparc64.deb >> $ dpkg -i gcc-6-base_6.2.0-9_sparc64.deb libstdc++6_6.2.0-9_sparc64.deb >> >> Once gcc-6_6.2.1-3 has finished building on sparc64 here [1], it should be >> safe to dist-upgrade the machine again. >> >> Please let us know when you encounter any other issues. >> >> Adrian >> >>> [1] https://buildd.debian.org/status/package.php?p=gcc-6&suite=sid >> > Using the above thread and after installing several packages (apache2, > mariadb, phpmyadmin, webmin, & shellinabox and their associated > requirement packages); I got the following crash and had to reboot. > > [ 2983.405916] systemd[1]: apt-daily.timer: Adding 10h 21min 29.083051s > random time. > [ 2987.766873] systemd[1]: apt-daily.timer: Adding 4h 3min 23.373286s > random time. > [ 3049.054254] \|/ \|/ > [ 3049.054254] "@'/ .. \`@" > [ 3049.054254] /_| \__/ |_\ > [ 3049.054254] \__U_/ > [ 3049.247708] systemd(1): Kernel illegal instruction [#1] > [ 3049.316397] CPU: 0 PID: 1 Comm: systemd Not tainted > 4.8.0-1-sparc64-smp #1 Debian 4.8.5-1 > [ 3049.424029] task: fff000123e14f620 task.stack: fff000123e158000 > [ 3049.501869] TSTATE: 004411001603 TPC: 005ca4a8 TNPC: > 005ca4ac Y: Not tainted > [ 3049.631240] TPC: <__kmalloc_track_caller+0x128/0x200> > [ 3049.697661] g0: g1: 0040 g2: > g3: 0001 > [ 3049.812168] g4: fff000123e14f620 g5: fff000123ebc6000 g6: > fff000123e158000 g7: 00636500 > [ 3049.926669] o0: o1: 024000c0 o2: > o3: > [ 3050.041113] o4: o5: sp: > fff000123e15af01 ret_pc: 005ca4a0 > [ 3050.160172] RPC: <__kmalloc_track_caller+0x120/0x200> > [ 3050.226606] l0: fff000123e0032e0 l1: 4000 l2: > fff000123e004898 l3: 000c28fb0d68 > [ 3050.341088] l4: l5: fff000123f80f328 l6: > 000c28fb0d88 l7: fff100e9a000 > [ 3050.455564] i0: fff000123e0032e0 i1: 024000c0 i2: > 0058c47c i3: 024000c0 > [ 3050.570055] i4: 000b i5: 024000c0 i6: > fff000123e15afb1 i7: 0058c408 > [ 3050.635685] \|/ \|/ > [ 3050.635685] "@'/ .. \`@" > [ 3050.635685] /_| \__/ |_\ > [ 3050.635685] \__U_/ > [ 3050.635690] systemd-journal(209): Kernel illegal instruction [#2] > [ 3050.635698] CPU: 1 PID: 209 Comm: systemd-journal Not tainted > 4.8.0-1-sparc64-smp #1 Debian 4.8.5-1 > [ 3050.635701] task: fff00012049dc080 task.stack: fff000123d1dc000 > [ 3050.635705] TSTATE: 004411001604 TPC: 005ca4a8 TNPC: > 005ca4ac Y: Not tainted > [ 3050.635718] TPC: <__kmalloc_track_caller+0x128/0x200> > [ 3050.635720] g0: fff000123d1dee71 g1: 0040 g2: > g3: c000 > [ 3050.635723] g4: fff00012049dc080 g5: fff000123edc6000 g6: > fff000123d1dc000 g7: fff000123edc6000 > [ 3050.635725] o0: o1: 025106c0 o2: > fff000123de2dc20 o3: 00b15c00 > [ 3050.635727] o4: o5: sp: > fff000123d1deed1 ret_pc: 005ca4a0 > [ 3050.635731] RPC: <__kmalloc_track_caller+0x120/0x200> > [ 3050.635734] l0: fff000123e003220 l1: 4000 l2: > f000 l3: fff0001204c54e40 > [ 3050.635736] l4: l5: l6: > l7: fff100327e90 > [ 3050.635738] i0: fff000123e003220 i1: 025106c0 i2: > 00862a1c i3: 025106c0 > [ 3050.635740] i4: 0180 i5: 025106c0 i6: > fff000123d1def81 i7: 00862960 > [ 3050.635751] I7: <__kmalloc_reserve.isra.5+0x20/0x80> > [ 3050.635752] Call Trace: > [ 3050.635757] [00862960] __kmalloc_reserve.isra.5+0x20/0x80 > [ 3050.635760] [00862a1c] __alloc_skb+0x5c/0x180 > [ 30
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/28/2016 4:07 PM, rod wrote: > > > On 11/18/2016 4:32 PM, John Paul Adrian Glaubitz wrote: >> On 11/16/2016 06:13 PM, rod wrote: >>> The current problem I'm having is this: >>> >>> root@mw-monitor:/home/rod# aptitude >>> Ouch! Got SIGSEGV, dying.. >>> Segmentation fault >> >> This has turned out to be an issue with libstdc++6 which comes from the gcc-6 >> package which was built with a broken version of binutils. The buildds are >> currently building a fresh gcc-6 package which is being built with a fixed >> version of binutils which should mitigate the problem. >> >> For anyone experiencing the issue, here is a quick workaround to fix apt >> for the time being until the buildds have finished building the new gcc-6 >> package (which should be in around 2-3 hours). >> >> Fix: >> >> $ wget >> http://snapshot.debian.org/archive/debian-ports/20161022T004918Z/pool-sparc64/main/g/gcc-6/gcc-6-base_6.2.0-9_sparc64.deb >> \ >> >> http://snapshot.debian.org/archive/debian-ports/20161022T004918Z/pool-sparc64/main/g/gcc-6/libstdc%2B%2B6_6.2.0-9_sparc64.deb >> $ dpkg -i gcc-6-base_6.2.0-9_sparc64.deb libstdc++6_6.2.0-9_sparc64.deb >> >> Once gcc-6_6.2.1-3 has finished building on sparc64 here [1], it should be >> safe to dist-upgrade the machine again. >> >> Please let us know when you encounter any other issues. >> >> Adrian >> >>> [1] https://buildd.debian.org/status/package.php?p=gcc-6&suite=sid >> > Using the above thread and after installing several packages (apache2, > mariadb, phpmyadmin, webmin, & shellinabox and their associated > requirement packages); I got the following crash and had to reboot. > > [ 2983.405916] systemd[1]: apt-daily.timer: Adding 10h 21min 29.083051s > random time. > [ 2987.766873] systemd[1]: apt-daily.timer: Adding 4h 3min 23.373286s > random time. > [ 3049.054254] \|/ \|/ > [ 3049.054254] "@'/ .. \`@" > [ 3049.054254] /_| \__/ |_\ > [ 3049.054254] \__U_/ > [ 3049.247708] systemd(1): Kernel illegal instruction [#1] > [ 3049.316397] CPU: 0 PID: 1 Comm: systemd Not tainted > 4.8.0-1-sparc64-smp #1 Debian 4.8.5-1 > [ 3049.424029] task: fff000123e14f620 task.stack: fff000123e158000 > [ 3049.501869] TSTATE: 004411001603 TPC: 005ca4a8 TNPC: > 005ca4ac Y: Not tainted > [ 3049.631240] TPC: <__kmalloc_track_caller+0x128/0x200> > [ 3049.697661] g0: g1: 0040 g2: > g3: 0001 > [ 3049.812168] g4: fff000123e14f620 g5: fff000123ebc6000 g6: > fff000123e158000 g7: 00636500 > [ 3049.926669] o0: o1: 024000c0 o2: > o3: > [ 3050.041113] o4: o5: sp: > fff000123e15af01 ret_pc: 005ca4a0 > [ 3050.160172] RPC: <__kmalloc_track_caller+0x120/0x200> > [ 3050.226606] l0: fff000123e0032e0 l1: 4000 l2: > fff000123e004898 l3: 000c28fb0d68 > [ 3050.341088] l4: l5: fff000123f80f328 l6: > 000c28fb0d88 l7: fff100e9a000 > [ 3050.455564] i0: fff000123e0032e0 i1: 024000c0 i2: > 0058c47c i3: 024000c0 > [ 3050.570055] i4: 000b i5: 024000c0 i6: > fff000123e15afb1 i7: 0058c408 > [ 3050.635685] \|/ \|/ > [ 3050.635685] "@'/ .. \`@" > [ 3050.635685] /_| \__/ |_\ > [ 3050.635685] \__U_/ > [ 3050.635690] systemd-journal(209): Kernel illegal instruction [#2] > [ 3050.635698] CPU: 1 PID: 209 Comm: systemd-journal Not tainted > 4.8.0-1-sparc64-smp #1 Debian 4.8.5-1 > [ 3050.635701] task: fff00012049dc080 task.stack: fff000123d1dc000 > [ 3050.635705] TSTATE: 004411001604 TPC: 005ca4a8 TNPC: > 005ca4ac Y: Not tainted > [ 3050.635718] TPC: <__kmalloc_track_caller+0x128/0x200> > [ 3050.635720] g0: fff000123d1dee71 g1: 0040 g2: > g3: c000 > [ 3050.635723] g4: fff00012049dc080 g5: fff000123edc6000 g6: > fff000123d1dc000 g7: fff000123edc6000 > [ 3050.635725] o0: o1: 025106c0 o2: > fff000123de2dc20 o3: 00b15c00 > [ 3050.635727] o4: o5: sp: > fff000123d1deed1 ret_pc: 005ca4a0 > [ 3050.635731] RPC: <__kmalloc_track_caller+0x120/0x200> > [ 3050.635734] l0: fff000123e003220 l1: 4000 l2: > f000 l3: fff0001204c54e40 > [ 3050.635736] l4: l5: l6: > l7: fff100327e90 > [ 3050.635738] i0: fff000123e003220 i1: 025106c0 i2: > 00862a1c i3: 025106c0 > [ 3050.635740] i4: 0180 i5: 025106c0 i6: > fff000123d1def81 i7: 00862960 > [ 3050.635751] I7: <__kmalloc_reserve.isra.5+0x20/0x80> > [ 3050.635752] Call Trace: > [ 3050.635757] [00862960] __kmalloc_reserve.isra.5+0x20/0x80 > [ 3050.635760] [00862a1c] __alloc_skb+0x5c/0x180 > [ 3050.635764
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/18/2016 4:32 PM, John Paul Adrian Glaubitz wrote: > On 11/16/2016 06:13 PM, rod wrote: >> The current problem I'm having is this: >> >> root@mw-monitor:/home/rod# aptitude >> Ouch! Got SIGSEGV, dying.. >> Segmentation fault > > This has turned out to be an issue with libstdc++6 which comes from the gcc-6 > package which was built with a broken version of binutils. The buildds are > currently building a fresh gcc-6 package which is being built with a fixed > version of binutils which should mitigate the problem. > > For anyone experiencing the issue, here is a quick workaround to fix apt > for the time being until the buildds have finished building the new gcc-6 > package (which should be in around 2-3 hours). > > Fix: > > $ wget > http://snapshot.debian.org/archive/debian-ports/20161022T004918Z/pool-sparc64/main/g/gcc-6/gcc-6-base_6.2.0-9_sparc64.deb > \ > > http://snapshot.debian.org/archive/debian-ports/20161022T004918Z/pool-sparc64/main/g/gcc-6/libstdc%2B%2B6_6.2.0-9_sparc64.deb > $ dpkg -i gcc-6-base_6.2.0-9_sparc64.deb libstdc++6_6.2.0-9_sparc64.deb > > Once gcc-6_6.2.1-3 has finished building on sparc64 here [1], it should be > safe to dist-upgrade the machine again. > > Please let us know when you encounter any other issues. > > Adrian > >> [1] https://buildd.debian.org/status/package.php?p=gcc-6&suite=sid > Using the above thread and after installing several packages (apache2, mariadb, phpmyadmin, webmin, & shellinabox and their associated requirement packages); I got the following crash and had to reboot. [ 2983.405916] systemd[1]: apt-daily.timer: Adding 10h 21min 29.083051s random time. [ 2987.766873] systemd[1]: apt-daily.timer: Adding 4h 3min 23.373286s random time. [ 3049.054254] \|/ \|/ [ 3049.054254] "@'/ .. \`@" [ 3049.054254] /_| \__/ |_\ [ 3049.054254] \__U_/ [ 3049.247708] systemd(1): Kernel illegal instruction [#1] [ 3049.316397] CPU: 0 PID: 1 Comm: systemd Not tainted 4.8.0-1-sparc64-smp #1 Debian 4.8.5-1 [ 3049.424029] task: fff000123e14f620 task.stack: fff000123e158000 [ 3049.501869] TSTATE: 004411001603 TPC: 005ca4a8 TNPC: 005ca4ac Y: Not tainted [ 3049.631240] TPC: <__kmalloc_track_caller+0x128/0x200> [ 3049.697661] g0: g1: 0040 g2: g3: 0001 [ 3049.812168] g4: fff000123e14f620 g5: fff000123ebc6000 g6: fff000123e158000 g7: 00636500 [ 3049.926669] o0: o1: 024000c0 o2: o3: [ 3050.041113] o4: o5: sp: fff000123e15af01 ret_pc: 005ca4a0 [ 3050.160172] RPC: <__kmalloc_track_caller+0x120/0x200> [ 3050.226606] l0: fff000123e0032e0 l1: 4000 l2: fff000123e004898 l3: 000c28fb0d68 [ 3050.341088] l4: l5: fff000123f80f328 l6: 000c28fb0d88 l7: fff100e9a000 [ 3050.455564] i0: fff000123e0032e0 i1: 024000c0 i2: 0058c47c i3: 024000c0 [ 3050.570055] i4: 000b i5: 024000c0 i6: fff000123e15afb1 i7: 0058c408 [ 3050.635685] \|/ \|/ [ 3050.635685] "@'/ .. \`@" [ 3050.635685] /_| \__/ |_\ [ 3050.635685] \__U_/ [ 3050.635690] systemd-journal(209): Kernel illegal instruction [#2] [ 3050.635698] CPU: 1 PID: 209 Comm: systemd-journal Not tainted 4.8.0-1-sparc64-smp #1 Debian 4.8.5-1 [ 3050.635701] task: fff00012049dc080 task.stack: fff000123d1dc000 [ 3050.635705] TSTATE: 004411001604 TPC: 005ca4a8 TNPC: 005ca4ac Y: Not tainted [ 3050.635718] TPC: <__kmalloc_track_caller+0x128/0x200> [ 3050.635720] g0: fff000123d1dee71 g1: 0040 g2: g3: c000 [ 3050.635723] g4: fff00012049dc080 g5: fff000123edc6000 g6: fff000123d1dc000 g7: fff000123edc6000 [ 3050.635725] o0: o1: 025106c0 o2: fff000123de2dc20 o3: 00b15c00 [ 3050.635727] o4: o5: sp: fff000123d1deed1 ret_pc: 005ca4a0 [ 3050.635731] RPC: <__kmalloc_track_caller+0x120/0x200> [ 3050.635734] l0: fff000123e003220 l1: 4000 l2: f000 l3: fff0001204c54e40 [ 3050.635736] l4: l5: l6: l7: fff100327e90 [ 3050.635738] i0: fff000123e003220 i1: 025106c0 i2: 00862a1c i3: 025106c0 [ 3050.635740] i4: 0180 i5: 025106c0 i6: fff000123d1def81 i7: 00862960 [ 3050.635751] I7: <__kmalloc_reserve.isra.5+0x20/0x80> [ 3050.635752] Call Trace: [ 3050.635757] [00862960] __kmalloc_reserve.isra.5+0x20/0x80 [ 3050.635760] [00862a1c] __alloc_skb+0x5c/0x180 [ 3050.635764] [00862b84] alloc_skb_with_frags+0x44/0x1e0 [ 3050.635768] [0085d02c] sock_alloc_send_pskb+0x1ec/0x220 [ 3050.635775] [009329ec] unix_dgram_sendmsg+0x12c/0x600 [ 3050.635778] [
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/19/2016 01:13 PM, John Paul Adrian Glaubitz wrote: > Ok, the last fix for binutils was yet not enough. The problem was supposedly > introduced by this change in binutils [1]. We have reverted this change now > completely and are rebuilding gcc-6 again. This works now. Just make sure to install libstdc++6/gcc-6-base in the version 6.2.1-3+b1 or newer. It might take a few hours still until the updated packages have reached all mirrors. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/18/2016 11:32 PM, John Paul Adrian Glaubitz wrote: > This has turned out to be an issue with libstdc++6 which comes from the gcc-6 > package which was built with a broken version of binutils. The buildds are > currently building a fresh gcc-6 package which is being built with a fixed > version of binutils which should mitigate the problem. Ok, the last fix for binutils was yet not enough. The problem was supposedly introduced by this change in binutils [1]. We have reverted this change now completely and are rebuilding gcc-6 again. Once we have verified the problem has been finally fixed, we will rebuild all possibly affected packages again to be sure all collateral damage has been fixed. Again, if anyone runs into segmentation faults or similar crashes with any package, particularly if it was recently updated, please let us know. Thanks, Adrian > [1] https://sourceware.org/ml/binutils/2016-09/msg00067.html -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/16/2016 06:13 PM, rod wrote: > The current problem I'm having is this: > > root@mw-monitor:/home/rod# aptitude > Ouch! Got SIGSEGV, dying.. > Segmentation fault This has turned out to be an issue with libstdc++6 which comes from the gcc-6 package which was built with a broken version of binutils. The buildds are currently building a fresh gcc-6 package which is being built with a fixed version of binutils which should mitigate the problem. For anyone experiencing the issue, here is a quick workaround to fix apt for the time being until the buildds have finished building the new gcc-6 package (which should be in around 2-3 hours). Fix: $ wget http://snapshot.debian.org/archive/debian-ports/20161022T004918Z/pool-sparc64/main/g/gcc-6/gcc-6-base_6.2.0-9_sparc64.deb \ http://snapshot.debian.org/archive/debian-ports/20161022T004918Z/pool-sparc64/main/g/gcc-6/libstdc%2B%2B6_6.2.0-9_sparc64.deb $ dpkg -i gcc-6-base_6.2.0-9_sparc64.deb libstdc++6_6.2.0-9_sparc64.deb Once gcc-6_6.2.1-3 has finished building on sparc64 here [1], it should be safe to dist-upgrade the machine again. Please let us know when you encounter any other issues. Adrian > [1] https://buildd.debian.org/status/package.php?p=gcc-6&suite=sid -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
Re: Segmentation faults with aptitude and apt-get on some packages
On 11/16/2016 4:30 PM, James Clarke wrote: >> On 16 Nov 2016, at 22:26, rod wrote: >>> On 11/16/2016 2:12 PM, rod wrote: On 11/16/2016 1:32 PM, James Clarke wrote: Hi Rod, > On 16 Nov 2016, at 17:13, rod wrote: > > I followed the guide you wrote (after dumping debian for solaris to > reset the sc> password). It works well as written, covering all the > issues that came up. > > The current problem I'm having is this: > > root@mw-monitor:/home/rod# aptitude > Ouch! Got SIGSEGV, dying.. > Segmentation fault > > or > > root@mw-monitor:/home/rod# apt-get install gunzip > Reading package lists... Done > Building dependency tree > Reading state information... Done > ESegmentation fault > > with this on the console: > > [ 1656.976655] apt-get[545]: segfault at fff200794008 ip > fff100015994 (rpc fff100015970) sp 07feffa705b1 error 30001 > in ld-2.24.so[fff1+22000] > > Any ideas? We’ve had to rebuild ~1700 packages built in the last couple of weeks, since they were built with a broken binutils. My guess is that aptitude was broken by this (it’s one of the packages built during that time period). I am however surprised that apt-get is segfaulting; that was built well before any of this mess. If I run that command I get this: # apt-get install gunzip Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package gunzip That’s with the latest version (1.3.1). FYI, there is no gunzip package; it’s included in gzip. If you want to get a working system set up now, I suggest you reinstall with your mirror configured to a snapshot taken before 2nd November using http://snapshot.debian.org/archive/debian-ports/, as it’s going to be a few days before everything has finished building. Unfortunately we weren’t aware of the problem and how widespread it was when you were installing. Regards, James >>> >>> Thanks James. I did look at the buildd page and saw large number >>> working on being rebuilt and thought it might be something like this. >>> >>> I will change the mirror and reload simple for quickness. >>> >>> I figured it was better to mention it... >>> >>> Rod >> >> OK so new question... >> Once I've done the reinstall from the archive should I do apt-get update >> && apt-get upgrade followed by apt-get dist-upgrade? Will it grab from >> the newly built packages? Will it bork the newly installed system? > > You can, but it won’t do anything, since the installer should have put the > snapshot mirror in your /etc/apt/sources.list, so as far as it’s concerned > everything is up to date. Once everything has been rebuilt, you can put the > original mirror configuration back in /etc/apt/sources.list and do an upgrade. > > Regards, > James > Thanks
Re: Segmentation faults with aptitude and apt-get on some packages
> On 16 Nov 2016, at 22:26, rod wrote: >> On 11/16/2016 2:12 PM, rod wrote: >>> On 11/16/2016 1:32 PM, James Clarke wrote: >>> Hi Rod, On 16 Nov 2016, at 17:13, rod wrote: I followed the guide you wrote (after dumping debian for solaris to reset the sc> password). It works well as written, covering all the issues that came up. The current problem I'm having is this: root@mw-monitor:/home/rod# aptitude Ouch! Got SIGSEGV, dying.. Segmentation fault or root@mw-monitor:/home/rod# apt-get install gunzip Reading package lists... Done Building dependency tree Reading state information... Done ESegmentation fault with this on the console: [ 1656.976655] apt-get[545]: segfault at fff200794008 ip fff100015994 (rpc fff100015970) sp 07feffa705b1 error 30001 in ld-2.24.so[fff1+22000] Any ideas? >>> >>> We’ve had to rebuild ~1700 packages built in the last couple of weeks, >>> since they were built with a broken binutils. My guess is that aptitude >>> was broken by this (it’s one of the packages built during that time >>> period). I am however surprised that apt-get is segfaulting; that was >>> built well before any of this mess. If I run that command I get this: >>> >>> # apt-get install gunzip >>> Reading package lists... Done >>> Building dependency tree >>> Reading state information... Done >>> E: Unable to locate package gunzip >>> >>> That’s with the latest version (1.3.1). FYI, there is no gunzip package; >>> it’s included in gzip. >>> >>> If you want to get a working system set up now, I suggest you reinstall >>> with your mirror configured to a snapshot taken before 2nd November using >>> http://snapshot.debian.org/archive/debian-ports/, as it’s going to be a >>> few days before everything has finished building. Unfortunately we weren’t >>> aware of the problem and how widespread it was when you were installing. >>> >>> Regards, >>> James >> >> Thanks James. I did look at the buildd page and saw large number >> working on being rebuilt and thought it might be something like this. >> >> I will change the mirror and reload simple for quickness. >> >> I figured it was better to mention it... >> >> Rod > > OK so new question... > Once I've done the reinstall from the archive should I do apt-get update > && apt-get upgrade followed by apt-get dist-upgrade? Will it grab from > the newly built packages? Will it bork the newly installed system? You can, but it won’t do anything, since the installer should have put the snapshot mirror in your /etc/apt/sources.list, so as far as it’s concerned everything is up to date. Once everything has been rebuilt, you can put the original mirror configuration back in /etc/apt/sources.list and do an upgrade. Regards, James
Re: Segmentation faults with aptitude and apt-get on some packages
OK so new question... Once I've done the reinstall from the archive should I do apt-get update && apt-get upgrade followed by apt-get dist-upgrade? Will it grab from the newly built packages? Will it bork the newly installed system? Rod On 11/16/2016 2:12 PM, rod wrote: > Thanks James. I did look at the buildd page and saw large number > working on being rebuilt and thought it might be something like this. > > I will change the mirror and reload simple for quickness. > > I figured it was better to mention it... > > Rod > > On 11/16/2016 1:32 PM, James Clarke wrote: >> Hi Rod, >>> On 16 Nov 2016, at 17:13, rod wrote: >>> >>> I followed the guide you wrote (after dumping debian for solaris to >>> reset the sc> password). It works well as written, covering all the >>> issues that came up. >>> >>> The current problem I'm having is this: >>> >>> root@mw-monitor:/home/rod# aptitude >>> Ouch! Got SIGSEGV, dying.. >>> Segmentation fault >>> >>> or >>> >>> root@mw-monitor:/home/rod# apt-get install gunzip >>> Reading package lists... Done >>> Building dependency tree >>> Reading state information... Done >>> ESegmentation fault >>> >>> with this on the console: >>> >>> [ 1656.976655] apt-get[545]: segfault at fff200794008 ip >>> fff100015994 (rpc fff100015970) sp 07feffa705b1 error 30001 >>> in ld-2.24.so[fff1+22000] >>> >>> Any ideas? >> >> We’ve had to rebuild ~1700 packages built in the last couple of weeks, >> since they were built with a broken binutils. My guess is that aptitude >> was broken by this (it’s one of the packages built during that time >> period). I am however surprised that apt-get is segfaulting; that was >> built well before any of this mess. If I run that command I get this: >> >> # apt-get install gunzip >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> E: Unable to locate package gunzip >> >> That’s with the latest version (1.3.1). FYI, there is no gunzip package; >> it’s included in gzip. >> >> If you want to get a working system set up now, I suggest you reinstall >> with your mirror configured to a snapshot taken before 2nd November using >> http://snapshot.debian.org/archive/debian-ports/, as it’s going to be a >> few days before everything has finished building. Unfortunately we weren’t >> aware of the problem and how widespread it was when you were installing. >> >> Regards, >> James >> >
Re: Segmentation faults with aptitude and apt-get on some packages
Thanks James. I did look at the buildd page and saw large number working on being rebuilt and thought it might be something like this. I will change the mirror and reload simple for quickness. I figured it was better to mention it... Rod On 11/16/2016 1:32 PM, James Clarke wrote: > Hi Rod, >> On 16 Nov 2016, at 17:13, rod wrote: >> >> I followed the guide you wrote (after dumping debian for solaris to >> reset the sc> password). It works well as written, covering all the >> issues that came up. >> >> The current problem I'm having is this: >> >> root@mw-monitor:/home/rod# aptitude >> Ouch! Got SIGSEGV, dying.. >> Segmentation fault >> >> or >> >> root@mw-monitor:/home/rod# apt-get install gunzip >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> ESegmentation fault >> >> with this on the console: >> >> [ 1656.976655] apt-get[545]: segfault at fff200794008 ip >> fff100015994 (rpc fff100015970) sp 07feffa705b1 error 30001 >> in ld-2.24.so[fff1+22000] >> >> Any ideas? > > We’ve had to rebuild ~1700 packages built in the last couple of weeks, > since they were built with a broken binutils. My guess is that aptitude > was broken by this (it’s one of the packages built during that time > period). I am however surprised that apt-get is segfaulting; that was > built well before any of this mess. If I run that command I get this: > > # apt-get install gunzip > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package gunzip > > That’s with the latest version (1.3.1). FYI, there is no gunzip package; > it’s included in gzip. > > If you want to get a working system set up now, I suggest you reinstall > with your mirror configured to a snapshot taken before 2nd November using > http://snapshot.debian.org/archive/debian-ports/, as it’s going to be a > few days before everything has finished building. Unfortunately we weren’t > aware of the problem and how widespread it was when you were installing. > > Regards, > James >
Re: Segmentation faults with aptitude and apt-get on some packages
Thanks James. I did look at the buildd page and saw large number working on being rebuilt and thought it might be something like this. I will change the mirror and reload simple for quickness. I figured it was better to mention it... Rod On 11/16/2016 1:32 PM, James Clarke wrote: > Hi Rod, >> On 16 Nov 2016, at 17:13, rod wrote: >> >> I followed the guide you wrote (after dumping debian for solaris to >> reset the sc> password). It works well as written, covering all the >> issues that came up. >> >> The current problem I'm having is this: >> >> root@mw-monitor:/home/rod# aptitude >> Ouch! Got SIGSEGV, dying.. >> Segmentation fault >> >> or >> >> root@mw-monitor:/home/rod# apt-get install gunzip >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> ESegmentation fault >> >> with this on the console: >> >> [ 1656.976655] apt-get[545]: segfault at fff200794008 ip >> fff100015994 (rpc fff100015970) sp 07feffa705b1 error 30001 >> in ld-2.24.so[fff1+22000] >> >> Any ideas? > > We’ve had to rebuild ~1700 packages built in the last couple of weeks, > since they were built with a broken binutils. My guess is that aptitude > was broken by this (it’s one of the packages built during that time > period). I am however surprised that apt-get is segfaulting; that was > built well before any of this mess. If I run that command I get this: > > # apt-get install gunzip > Reading package lists... Done > Building dependency tree > Reading state information... Done > E: Unable to locate package gunzip > > That’s with the latest version (1.3.1). FYI, there is no gunzip package; > it’s included in gzip. > > If you want to get a working system set up now, I suggest you reinstall > with your mirror configured to a snapshot taken before 2nd November using > http://snapshot.debian.org/archive/debian-ports/, as it’s going to be a > few days before everything has finished building. Unfortunately we weren’t > aware of the problem and how widespread it was when you were installing. > > Regards, > James >
Re: Segmentation faults with aptitude and apt-get on some packages
Hi Rod, > On 16 Nov 2016, at 17:13, rod wrote: > > I followed the guide you wrote (after dumping debian for solaris to > reset the sc> password). It works well as written, covering all the > issues that came up. > > The current problem I'm having is this: > > root@mw-monitor:/home/rod# aptitude > Ouch! Got SIGSEGV, dying.. > Segmentation fault > > or > > root@mw-monitor:/home/rod# apt-get install gunzip > Reading package lists... Done > Building dependency tree > Reading state information... Done > ESegmentation fault > > with this on the console: > > [ 1656.976655] apt-get[545]: segfault at fff200794008 ip > fff100015994 (rpc fff100015970) sp 07feffa705b1 error 30001 > in ld-2.24.so[fff1+22000] > > Any ideas? We’ve had to rebuild ~1700 packages built in the last couple of weeks, since they were built with a broken binutils. My guess is that aptitude was broken by this (it’s one of the packages built during that time period). I am however surprised that apt-get is segfaulting; that was built well before any of this mess. If I run that command I get this: # apt-get install gunzip Reading package lists... Done Building dependency tree Reading state information... Done E: Unable to locate package gunzip That’s with the latest version (1.3.1). FYI, there is no gunzip package; it’s included in gzip. If you want to get a working system set up now, I suggest you reinstall with your mirror configured to a snapshot taken before 2nd November using http://snapshot.debian.org/archive/debian-ports/, as it’s going to be a few days before everything has finished building. Unfortunately we weren’t aware of the problem and how widespread it was when you were installing. Regards, James
Segmentation faults with aptitude and apt-get on some packages
Adrian, I followed the guide you wrote (after dumping debian for solaris to reset the sc> password). It works well as written, covering all the issues that came up. The current problem I'm having is this: root@mw-monitor:/home/rod# aptitude Ouch! Got SIGSEGV, dying.. Segmentation fault or root@mw-monitor:/home/rod# apt-get install gunzip Reading package lists... Done Building dependency tree Reading state information... Done ESegmentation fault with this on the console: [ 1656.976655] apt-get[545]: segfault at fff200794008 ip fff100015994 (rpc fff100015970) sp 07feffa705b1 error 30001 in ld-2.24.so[fff1+22000] Any ideas? Rod
