Bug#653580: ITP: yasat -- YASAT (Yet Another Stupid Audit Tool) is a simple stupid audit tool.
Package: wnpp Severity: wishlist Owner: Corentin LABBE * Package name: yasat Version : 456 Upstream Author : Corentin LABBE * URL : http://yasat.sourceforge.net/ * License : (GPLv3) Programming Lang: (Shell) Description : YASAT (Yet Another Stupid Audit Tool) is a simple stupid audit tool. YASAT (Yet Another Stupid Audit Tool) is a simple stupid audit tool. Its goal is to be as simple as possible with minimum binary dependencies (only sed, grep and cut) Second goal is to document each test with maximum information and links to official documentation. It do many tests for checking security configuration issue or others good practice. It checks many software configurations like: Apache, Bind DNS, CUPS, PHP, kernel configuration, mysql, network configuration, openvpn, Packages update, samba, snmpd, squid, syslog, tomcat, user accounting, vsftpd, xinetd -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20111229142153.32655.44581.reportbug@localhost
Bug#953637: debootstrap remove /proc when ran under docker
Package: debootstrap Version: 1.0.114 On a fresh install buster under docker I ran "debootstrap buster test". This lead to a system without /proc mounted. The following error are found: >> I: Target architecture can be executed >> I: Retrieving InRelease >> I: Checking Release signature >> I: Valid Release signature (key id 6D33866EDD8FFA41C0143AEDDCC9EFBF77E11517) >> I: Retrieving Packages >> I: Validating Packages >> I: Resolving dependencies of required packages... >> I: Resolving dependencies of base packages... >> I: Checking component main on http://deb.debian.org/debian... >> I: Validating libacl1 2.2.53-4 >> I: Validating adduser 3.118 >> I: Validating apt 1.8.2 [...] >> I: Extracting mount... >> I: Extracting util-linux... >> I: Extracting liblzma5... >> I: Extracting zlib1g... >> W: Failure trying to run: chroot "//test" mount -t proc proc /proc >> W: See //test/debootstrap/debootstrap.log for details >> I: Installing core packages... >> I: Unpacking required packages... >> I: Unpacking libacl1:amd64... >> I: Unpacking adduser... [...] In the debootstrap.log I saw: mount: /proc: mount(2) system call failed: Too many levels of symbolic links. It reproduces always, even with different host OS (stretch and gentoo are tested) I have also tried the "testing" version without changes.
Bug#955426: qemu-system-x86_64 randomly kernel panic
Package: qemu-system-x86 Version: 1:3.1+dfsg-8+deb10u4 On our kernelci lab, each qemu worker pass an healtcheck job each day and after each job failure, so it is heavily used. The healtcheck job is a Linux boot with a stable release. Since we upgraded our worker to buster, the qemu x86_64 healthcheck randomly panic with: <6>[0.001000] APIC: Switch to symmetric I/O mode setup <6>[0.001000] ..TIMER: vector=0x30 apic1=0 pin1=2 apic2=-1 pin2=-1 <3>[0.005000] ..MP-BIOS bug: 8254 timer not connected to IO-APIC <6>[0.005000] ...trying to set up timer (IRQ0) through the 8259A ... <6>[0.005000] . (found apic 0 pin 2) ... <6>[0.009000] ... failed. <6>[0.009000] ...trying to set up timer as Virtual Wire IRQ... <6>[0.009000] . failed. <6>[0.009000] ...trying to set up timer as ExtINT IRQ... <6>[0.009000] . failed :(. <0>[0.009000] Kernel panic - not syncing: IO-APIC + timer doesn't work! Boot with apic=debug and send a report. Then try booting with the 'noapic' option. <4>[0.009000] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.4.23 #1 <4>[0.009000] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.12.0-1 04/01/2014 <4>[0.009000] Call Trace: <4>[0.009000] dump_stack+0x50/0x70 <4>[0.009000] panic+0xf6/0x2b7 <4>[0.009000] setup_IO_APIC+0x7c3/0x81c <4>[0.009000] ? clear_IO_APIC_pin+0xb3/0x100 <4>[0.009000] x86_late_time_init+0x1b/0x20 <4>[0.009000] start_kernel+0x429/0x4e2 <4>[0.009000] secondary_startup_64+0xa4/0xb0 The qemu is called with: /usr/bin/qemu-system-x86_64 -cpu host -enable-kvm -nographic -net nic,model=virtio,macaddr=52:54:00:12:34:58 -net user -m 512 -monitor none -kernel /var/lib/lava/dispatcher/tmp/741722/deployimages-xl6ogak_/kernel/bzImage -append "console=ttyS0,115200 root=/dev/ram0 debug verbose console_msg_format=syslog" -initrd /var/lib/lava/dispatcher/tmp/741722/deployimages-xl6ogak_/ramdisk/rootfs.cpio.gz -drive format=qcow2,file=/var/lib/lava/dispatcher/tmp/741722/apply-overlay-guest-sfn3zqna/lava-guest.qcow2,media=disk,if=ide,id=lavatest We have tried to upgrade the Linux version from 5.0.21 to 5.4.23 without any change. Only our buster worker fail like this. No problem with stretch, and no problem on my gentoo worker (qemu 4.2.0). Since more recent qemu work perfectly, I suspect a bug in the buster release.
Bug#1088372: ppc64el: kernel panic: corrupted stack end detected inside scheduler after upgrade of nvidia-kernel-dkms
Package: nvidia-kernel-dkms Version: 535.183.01-1~deb12u1 Upgrading my bookworm ppc64el machine lead to unsuccessfull boot: [4.376878] Kernel panic - not syncing: corrupted stack end detected inside scheduler [4.376927] CPU: 5 PID: 797 Comm: nvidia-persiste Tainted: P O 6.1.0-28-powerpc64le #1 Debian 6.1.119-1 [4.376972] Hardware name: T2P9D01 REV 1.00 POWER9 0x4e1203 opal:skiboot-9858186 PowerNV [4.377006] Call Trace: [4.377037] [c0002fa3af10] [c0d7a2ec] dump_stack_lvl+0x70/0xa0 (unreliable) [4.377083] [c0002fa3af40] [c0137c68] panic+0x16c/0x444 [4.377131] [c0002fa3afd0] [c0daf00c] __schedule+0xbfc/0xc00 [4.377179] [c0002fa3b0b0] [c0daf084] schedule+0x74/0x140 [4.377212] [c0002fa3b120] [c0db7e34] schedule_timeout+0xb4/0x1c0 [4.377271] [c0002fa3b1f0] [c00815544b50] os_delay+0x168/0x3e0 [nvidia] [4.377768] [c0002fa3b2a0] [c008164294e0] _nv038220rm+0x20/0x50 [nvidia] [4.378313] [c0002fa3b2d0] [c008155ec704] _nv038438rm+0x264/0x530 [nvidia] [4.378821] [c0002fa3b3c0] [c0081643da08] _nv000655rm+0x13a8/0x2170 [nvidia] [4.379309] [c0002fa3b550] [c00816432ff4] rm_init_adapter+0x114/0x130 [nvidia] [4.379799] [c0002fa3b640] [c008155308a4] nv_open_device+0x60c/0xa40 [nvidia] [4.380099] [c0002fa3b6f0] [c008155320e0] nvidia_open+0x2e8/0x570 [nvidia] [4.380389] [c0002fa3b7a0] [c0081554cde8] nvidia_frontend_open+0xa0/0x120 [nvidia] [4.380705] [c0002fa3b7f0] [c0530ac8] chrdev_open+0x178/0x3b0 [4.380734] [c0002fa3b860] [c0521130] do_dentry_open+0x290/0x560 [4.380784] [c0002fa3b8b0] [c0544460] path_openat+0xb90/0x15a0 [4.380803] [c0002fa3b9a0] [c0545b98] do_filp_open+0xc8/0x1a0 [4.380821] [c0002fa3bad0] [c0523e40] do_sys_openat2+0x110/0x230 [4.380862] [c0002fa3bb40] [c0524378] sys_openat+0x88/0xe0 [4.380887] [c0002fa3bba0] [c002b038] system_call_exception+0x138/0x260 [4.380900] [c0002fa3be10] [c000c0f0] system_call_vectored_common+0xf0/0x280 [4.380938] --- interrupt: 3000 at 0x7fff92b3a948 [4.380963] NIP: 7fff92b3a948 LR: 7fff92b3a948 CTR: [4.380980] REGS: c0002fa3be80 TRAP: 3000 Tainted: P O (6.1.0-28-powerpc64le Debian 6.1.119-1) [4.381020] MSR: 9280f033 CR: 44004448 XER: [4.381091] IRQMASK: 0 [4.381091] GPR00: 011e 7d5dc360 7fff92c56f00 ff9c [4.381091] GPR04: 7d5dc400 00080002 0030 [4.381091] GPR08: 7fff928e01b8 [4.381091] GPR12: 7fff92f4dc40 [4.381091] GPR16: [4.381091] GPR20: [4.381091] GPR24: 7fff92903398 7fff92902a48 7fff92902a48 [4.381091] GPR28: 7d5dc53c 00080002 7fff92903398 [4.381305] NIP [7fff92b3a948] 0x7fff92b3a948 [4.381334] LR [7fff92b3a948] 0x7fff92b3a948 [4.381352] --- interrupt: 3000 [4.415728] bridge: filt This happen with both 6.1.0-28-powerpc64le and 6.1.0-21-powerpc64le. Removing /lib/modules/6.1.0-28-powerpc64le/updates/dkms/* was needed to recover. System was working perfectly with previous 525.147.05-7~deb12u1 Regards
Bug#1088372: reopen
reopen
Bug#1088372: not fixed
It refail the same way with 6.1.0-31-powerpc64le and 6.1.0-32-powerpc64le I tried unstable package but still fail: 4.469944] Kernel panic - not syncing: corrupted stack end detected inside scheduler [4.469980] CPU: 19 PID: 785 Comm: nvidia-persiste Tainted: PW O 6.1.0-32-powerpc64le #1 Debian 6.1.129-1 [4.470009] Hardware name: T2P9D01 REV 1.00 POWER9 0x4e1203 opal:skiboot-9858186 PowerNV [4.470044] Call Trace: [4.470050] [c0002c6aad60] [c0d7c70c] dump_stack_lvl+0x70/0xa0 (unreliable) [4.470084] [c0002c6aad90] [c0137cf8] panic+0x16c/0x444 [4.470121] [c0002c6aae20] [c0db137c] __schedule+0xbfc/0xc00 [4.470156] [c0002c6aaf00] [c0db13f4] schedule+0x74/0x140 [4.470192] [c0002c6aaf70] [c0dba1a4] schedule_timeout+0xb4/0x1c0 [4.470219] [c0002c6ab040] [c00815674890] os_delay+0x168/0x3e0 [nvidia] [4.470498] [c0002c6ab0f0] [c0081655afe0] _nv038241rm+0x20/0x50 [nvidia] [4.470788] [c0002c6ab120] [c0081571c4a4] _nv038459rm+0x264/0x530 [nvidia] [4.471081] [c0002c6ab210] [c0081656f538] _nv000655rm+0x13a8/0x2170 [nvidia] [4.471357] [c0002c6ab3a0] [c00816564af4] rm_init_adapter+0x114/0x130 [nvidia] [4.471638] [c0002c6ab490] [c008156608a4] nv_open_device+0x60c/0xa40 [nvidia] [4.471878] [c0002c6ab540] [c008156620e0] nvidia_open+0x2e8/0x570 [nvidia] [4.472101] [c0002c6ab5f0] [c0081567ca88] nvidia_frontend_open+0xa0/0x120 [nvidia] [4.472337] [c0002c6ab640] [c0531258] chrdev_open+0x178/0x3b0 [4.472352] [c0002c6ab6b0] [c05218c0] do_dentry_open+0x290/0x560 [4.472389] [c0002c6ab700] [c0544c50] path_openat+0xb90/0x15a0 [4.472403] [c0002c6ab7f0] [c0546388] do_filp_open+0xc8/0x1a0 [4.472456] [c0002c6ab920] [c05245d0] do_sys_openat2+0x110/0x230 [4.472503] [c0002c6ab990] [c0524b08] sys_openat+0x88/0xe0 [4.472550] [c0002c6ab9f0] [c002b038] system_call_exception+0x138/0x260 [4.472599] [c0002c6abe10] [c000c0f0] system_call_vectored_common+0xf0/0x280 [4.472637] --- interrupt: 3000 at 0x7fffa8b3a948 [4.472680] NIP: 7fffa8b3a948 LR: 7fffa8b3a948 CTR: [4.472726] REGS: c0002c6abe80 TRAP: 3000 Tainted: PW O (6.1.0-32-powerpc64le Debian 6.1.129-1) [4.472764] MSR: 9280f033 CR: 44004448 XER: [4.472793] IRQMASK: 0 [4.472793] GPR00: 011e 7fffe0ccd900 7fffa8c56f00 ff9c [4.472793] GPR04: 7fffe0ccd9a0 00080002 0030 [4.472793] GPR08: 7fffa87f01f8 [4.472793] GPR12: 7fffa8e5dc40 [4.472793] GPR16: [4.472793] GPR20: [4.472793] GPR24: 7fffa8813398 7fffa8812a48 7fffa8812a48 [4.472793] GPR28: 7fffe0ccdadc 00080002 7fffa8813398 [4.472991] NIP [7fffa8b3a948] 0x7fffa8b3a948 [4.473012] LR [7fffa8b3a948] 0x7fffa8b3a948 [4.473044] --- interrupt: 3000 [4.488316] [ cut here ] [4.488321] WARNING: CPU: 2 PID: 982 at kernel/sched/core.c:3147 set_task_cpu+0x240/0x250 [4.488334] Modules linked in: nfs(+) fscache netfs overlay i2c_dev evdev nvidia_drm(PO) drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvidia_modeset(PO) binfmt_misc hid_generic ofpart xts ecb powernv_flash ipmi_powernv ctr ipmi_devintf vmx_crypto gf128mul at24(+) mtd ipmi_msghandler opal_prd regmap_i2c sg usbhid hid nvidia(PO) nfsd auth_rpcgss nfs_acl lockd grace drm loop fuse drm_panel_orientation_quirks sunrpc configfs ip_tables x_tables autofs4 ext4 crc16 mbcache jbd2 crc32c_generic dm_mod ses enclosure sd_mod scsi_transport_sas xhci_pci xhci_hcd nvme crc32c_vpmsum nvme_core t10_pi tg3 crc64_rocksoft crc64 usbcore crc_t10dif crct10dif_generic crct10dif_common libphy ahci aacraid usb_common libahci [4.488454] CPU: 2 PID: 982 Comm: netstat Tainted: PW O 6.1.0-32-powerpc64le #1 Debian 6.1.129-1 [4.488460] Hardware name: T2P9D01 REV 1.00 POWER9 0x4e1203 opal:skiboot-9858186 PowerNV [4.488463] NIP: c018b8f0 LR: c018dfd4 CTR: c019a590 [4.488466] REGS: c00014a7b640 TRAP: 0700 Tainted: PW O (6.1.0-32-powerpc64le Debian 6.1.129-1) [4.488471] MSR: 900
Bug#1088372: fixed
Sorry, I forgot to update this bug. It works with: linux-image-6.1.0-30-powerpc64le and nvidia-kernel-dkms 535.216.01-1~deb12u1 Thanks Regards
