Bug#787004: FTBFS on amd64
Package: linux Version: 4.0.4 Followup-For: Bug #787004 I just tried this in a clean unstable amd64 chroot and it does indeed fail near the end, just as the buildd did. This is causing linux-libc-dev multiarch skew so multiarch-built crosstoolchains are currently unbuildable (on amd64). The issue is that installer/amd64/modules/amd64/scsi-extra-modules lists i2o_block and i2o_scsi and installer/modules/scsi-extra-modules lists i2o_block But the modules are not built because CONFIG_I2O_BLOCK and CONFIG_I2o_SCSI are not set The changelog says: Disable i2o So I presume the correct fix is to stop asking to install the modules into the scsi-extra-modules udeb (As opposed to enabling the config options). This does indeed allow the build to complete. Patch attached. And whilst I am here, the package doesn't build (with dpkg-buildpackage -S ) a second time, with all these changed files left over: dpkg-source: info: local changes detected, the modified files are: linux-4.0.4/arch/s390/include/asm/cmb.h.1 linux-4.0.4/drivers/dma-buf/reservation.c.1 linux-4.0.4/drivers/dma-buf/seqno-fence.c.1 linux-4.0.4/drivers/gpu/drm/i915/i915_irq.c.1 linux-4.0.4/drivers/scsi/constants.c.1 linux-4.0.4/drivers/usb/gadget/function/f_acm.c.1 linux-4.0.4/drivers/usb/gadget/function/f_ecm.c.1 linux-4.0.4/drivers/usb/gadget/function/f_obex.c.1 linux-4.0.4/drivers/usb/gadget/function/f_serial.c.1 linux-4.0.4/drivers/usb/gadget/function/f_subset.c.1 linux-4.0.4/include/linux/reservation.h.1 linux-4.0.4/kernel/sys.c.1 linux-4.0.4/lib/crc32.c.1 linux-4.0.4/sound/soc/soc-cache.c.1 Changed date and build bath in man page. Only in linux-4.0.4.new/arch/s390/include/asm: cmb.h.1 diff -ur linux-4.0.4/debian/changelog linux-4.0.4.new/debian/changelog --- linux-4.0.4/debian/changelog 2015-05-26 02:30:07.0 +0100 +++ linux-4.0.4.new/debian/changelog 2015-06-05 03:13:13.936808845 +0100 @@ -1,3 +1,10 @@ +linux (4.0.4-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS on amd64 (Closes: #787004) + + -- Wookey woo...@debian.org Fri, 05 Jun 2015 03:11:53 +0100 + linux (4.0.4-1) unstable; urgency=medium * New upstream stable update: diff -ur linux-4.0.4/debian/config.defines.dump linux-4.0.4.new/debian/config.defines.dump diff -ur linux-4.0.4/debian/control.md5sum linux-4.0.4.new/debian/control.md5sum diff -ur linux-4.0.4/debian/installer/amd64/modules/amd64/scsi-extra-modules linux-4.0.4.new/debian/installer/amd64/modules/amd64/scsi-extra-modules --- linux-4.0.4/debian/installer/amd64/modules/amd64/scsi-extra-modules 2015-05-11 14:22:50.0 +0100 +++ linux-4.0.4.new/debian/installer/amd64/modules/amd64/scsi-extra-modules 2015-06-05 02:18:32.352722659 +0100 @@ -1,4 +1,2 @@ #include scsi-extra-modules dpt_i2o - -i2o_block -i2o_scsi diff -ur linux-4.0.4/debian/rules.gen linux-4.0.4.new/debian/rules.gen Only in linux-4.0.4.new/drivers/dma-buf: reservation.c.1 Only in linux-4.0.4.new/drivers/dma-buf: seqno-fence.c.1 Only in linux-4.0.4.new/drivers/gpu/drm/i915: i915_irq.c.1 Only in linux-4.0.4.new/drivers/scsi: constants.c.1 Only in linux-4.0.4.new/drivers/usb/gadget/function: f_acm.c.1 Only in linux-4.0.4.new/drivers/usb/gadget/function: f_ecm.c.1 Only in linux-4.0.4.new/drivers/usb/gadget/function: f_obex.c.1 Only in linux-4.0.4.new/drivers/usb/gadget/function: f_serial.c.1 Only in linux-4.0.4.new/drivers/usb/gadget/function: f_subset.c.1 Only in linux-4.0.4.new/include/linux: reservation.h.1 Only in linux-4.0.4.new/kernel: sys.c.1 Only in linux-4.0.4.new/lib: crc32.c.1 Only in linux-4.0.4.new/sound/soc: soc-cache.c.1
Processed: Re: Bug#787735: debian-maintainers: [28560.848194] hub 1-0:1.0: unable to enumerate USB device on port 6
Processing control commands: reassign 787735 linux Bug #787735 [debian-maintainers] debian-maintainers: [28560.848194] hub 1-0:1.0: unable to enumerate USB device on port 6 Bug reassigned from package 'debian-maintainers' to 'linux'. Ignoring request to alter found versions of bug #787735 to the same values previously set Ignoring request to alter fixed versions of bug #787735 to the same values previously set tags 787735 + moreinfo Bug #787735 [linux] debian-maintainers: [28560.848194] hub 1-0:1.0: unable to enumerate USB device on port 6 Added tag(s) moreinfo. -- 787735: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787735 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.b787735.143344017223150.transcr...@bugs.debian.org
Bug#776192: [src:linux] udev 220-4 from SID solved similar problem
Hello I have a similar problem, and the solution is install the sid packages udev and libudev1 (220-4) in stable. I report that problem in #787738 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787738 Many thanks for the inspiration. Greetings. Martintxo. Package: src:linux --- Please enter the report below this line. --- --- System information. --- Architecture: i386 Kernel: Linux 4.0.2 Debian Release: stretch/sid 500 testing-updates ftp.debian.org 500 testing security.debian.org 500 testing ftp.de.debian.org 10 testing www.deb-multimedia.org --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. Sustrai Erakuntza: respuesta jurídico-técnica a proyectos insostenibles. proiektu jasangaitzei erantzun juridiko-teknikoa. http://www.fundacionsustrai.org http://www.sustraierakuntza.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150604180051.76e65d2d@fundy
Re: Build kernel with clang(sid)
On Thu, Jun 04, 2015 at 04:00:18PM +0800, Joseph Lee wrote: I am working on GSOC project bootable clang built debian and need to build Linux with clang. I used patches from LLVMLinux and add a new Kconfig file, modified debian/rules and debian/rules.real. May I report this as a bug(I attached the patch I made)? dude break up this patch in logic parts. this an unreadable mess. I don't get why a clang patch should patch a fs!? -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150604102120.GB14499@gluino
Re: Build kernel with clang(sid)
On Thu, Jun 04, 2015 at 04:00:18PM +0800, Joseph Lee wrote: I am working on GSOC project bootable clang built debian and need to build Linux with clang. I used patches from LLVMLinux and add a new Kconfig file, modified debian/rules and debian/rules.real. May I report this as a bug(I attached the patch I made)? the patch as is is unacceptable, why do you create a full new copy of a config, this is certainly not needed. best, -- maks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150604101901.GA14499@gluino
Processed: [bts-link] source package linux
Processing commands for cont...@bugs.debian.org: # # bts-link upstream status pull for source package linux # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html # user bts-link-upstr...@lists.alioth.debian.org Setting user to bts-link-upstr...@lists.alioth.debian.org (was bts-link-de...@lists.alioth.debian.org). # remote status report for #742512 (http://bugs.debian.org/742512) # Bug title: linux: kernel 3.13 breaks fan cooling on HP 6830S laptop # * http://bugzilla.kernel.org/show_bug.cgi?id=71711 # * remote status changed: NEEDINFO - CLOSED # * remote resolution changed: (?) - INSUFFICIENT-DATA # * closed upstream tags 742512 + fixed-upstream Bug #742512 [linux] linux: kernel 3.13 breaks fan cooling on HP 6830S laptop Added tag(s) fixed-upstream. usertags 742512 - status-NEEDINFO Usertags were: status-NEEDINFO. Usertags are now: . usertags 742512 + status-CLOSED resolution-INSUFFICIENT-DATA There were no usertags set. Usertags are now: resolution-INSUFFICIENT-DATA status-CLOSED. # remote status report for #787099 (http://bugs.debian.org/787099) # Bug title: pulseaudio: Output is muted when headphones/speakers are plugged in # * https://bugs.freedesktop.org/show_bug.cgi?id=90491 # * remote status changed: (?) - RESOLVED # * remote resolution changed: (?) - NOTOURBUG # * closed upstream tags 787099 + fixed-upstream Bug #787099 [linux-image-4.0.0-1-amd64] pulseaudio: Output is muted when headphones/speakers are plugged in Added tag(s) fixed-upstream. usertags 787099 + status-RESOLVED resolution-NOTOURBUG There were no usertags set. Usertags are now: resolution-NOTOURBUG status-RESOLVED. thanks Stopping processing here. Please contact me if you need assistance. -- 742512: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=742512 787099: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787099 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/handler.s.c.143344511414980.transcr...@bugs.debian.org
Bug#783381: upgrade from wheezy to jessie on a PowerMac G4 Silver/Confirmation
I gave this a try as I'm also using yaboot. Purging mkvmlinuz solved this issue for me as well. And now to the graphics problems :-( On Thu, Jun 4, 2015 at 9:01 PM, Manfred Stock manfred.stock+deb...@gmail.com wrote: Package: upgrade-reports, linux-image-3.16.0-4-powerpc Followup-For: Bug #783381 I also had this problem on an iBook G4, but had not rebooted, yet. When I started to look into it, I looked at the mkvmlinuz package page [1] and upon reading the description, I just decided to remove/purge the mkvmlinuz package, since I'm using yaboot as bootloader. That way, I got rid of this error, and the configuration of the kernel package was successful. I did not have issues during the reboot either, so at least in my setup, mkvmlinuz does not seem to be required. I do have other issues on this system though (mainly with the graphics card, and suspend to ram/disk), but I think they are not related to the problem with mkvmlinuz. Kind regards Manfred [1] https://packages.debian.org/jessie/mkvmlinuz -- To unsubscribe, send mail to 783381-unsubscr...@bugs.debian.org.
Bug#783381: upgrade from wheezy to jessie on a PowerMac G4 Silver/Confirmation
Package: upgrade-reports, linux-image-3.16.0-4-powerpc Followup-For: Bug #783381 I also had this problem on an iBook G4, but had not rebooted, yet. When I started to look into it, I looked at the mkvmlinuz package page [1] and upon reading the description, I just decided to remove/purge the mkvmlinuz package, since I'm using yaboot as bootloader. That way, I got rid of this error, and the configuration of the kernel package was successful. I did not have issues during the reboot either, so at least in my setup, mkvmlinuz does not seem to be required. I do have other issues on this system though (mainly with the graphics card, and suspend to ram/disk), but I think they are not related to the problem with mkvmlinuz. Kind regards Manfred [1] https://packages.debian.org/jessie/mkvmlinuz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150604190133.11665.71300.report...@choi.nfred.ch
Build kernel with clang(sid)
Dear maintainers, Hello. I am working on GSOC project bootable clang built debian and need to build Linux with clang. I used patches from LLVMLinux and add a new Kconfig file, modified debian/rules and debian/rules.real. May I report this as a bug(I attached the patch I made)? Many thanks. Cheers, Joseph diff -Nru linux-4.0.4/debian/config/kernelarch-x86/config-clang linux-4.0.4/debian/config/kernelarch-x86/config-clang --- linux-4.0.4/debian/config/kernelarch-x86/config-clang 1970-01-01 00:00:00.0 + +++ linux-4.0.4/debian/config/kernelarch-x86/config-clang 2015-06-03 15:04:07.0 + @@ -0,0 +1,1923 @@ +## +## file: arch/Kconfig +## +# CONFIG_OPROFILE_EVENT_MULTIPLEX is not set + +## +## file: arch/x86/Kconfig +## +CONFIG_ZONE_DMA=y +CONFIG_X86_MPPARSE=y +# CONFIG_X86_EXTENDED_PLATFORM is not set +CONFIG_X86_INTEL_LPSS=y +CONFIG_IOSF_MBI=m +CONFIG_SCHED_OMIT_FRAME_POINTER=y +CONFIG_HYPERVISOR_GUEST=y +CONFIG_PARAVIRT=y +# CONFIG_PARAVIRT_DEBUG is not set +CONFIG_PARAVIRT_SPINLOCKS=y +CONFIG_KVM_GUEST=y +# CONFIG_KVM_DEBUG_FS is not set +# CONFIG_PARAVIRT_TIME_ACCOUNTING is not set +CONFIG_MEMTEST=y +CONFIG_HPET_TIMER=y +CONFIG_DMI=y +CONFIG_GART_IOMMU=y +CONFIG_SCHED_SMT=y +CONFIG_SCHED_MC=y +CONFIG_X86_REROUTE_FOR_BROKEN_BOOT_IRQS=y +CONFIG_X86_MCE=y +CONFIG_X86_MCE_INTEL=y +CONFIG_X86_MCE_AMD=y +# CONFIG_X86_ANCIENT_MCE is not set +CONFIG_X86_MCE_INJECT=m +CONFIG_X86_16BIT=y +CONFIG_I8K=m +CONFIG_MICROCODE=y +CONFIG_MICROCODE_INTEL=y +CONFIG_MICROCODE_AMD=y +CONFIG_MICROCODE_EARLY=y +CONFIG_X86_MSR=m +CONFIG_X86_CPUID=m +CONFIG_NODES_SHIFT=6 +# CONFIG_ARCH_MEMORY_PROBE is not set +# CONFIG_X86_CHECK_BIOS_CORRUPTION is not set +CONFIG_X86_RESERVE_LOW=64 +CONFIG_MTRR=y +CONFIG_MTRR_SANITIZER=y +CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=0 +CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1 +CONFIG_X86_PAT=y +CONFIG_ARCH_RANDOM=y +CONFIG_X86_SMAP=y +CONFIG_EFI=y +CONFIG_EFI_STUB=y +CONFIG_SECCOMP=y +CONFIG_KEXEC=y +CONFIG_CRASH_DUMP=y +# CONFIG_KEXEC_JUMP is not set +CONFIG_RELOCATABLE=y +CONFIG_HOTPLUG_CPU=y +# CONFIG_BOOTPARAM_HOTPLUG_CPU0 is not set +# CONFIG_DEBUG_HOTPLUG_CPU0 is not set +# CONFIG_COMPAT_VDSO is not set +# CONFIG_CMDLINE_BOOL is not set +CONFIG_PCI=y +# CONFIG_PCI_CNB20LE_QUIRK is not set +# CONFIG_RAPIDIO is not set +CONFIG_X86_SYSFB=y +CONFIG_IA32_EMULATION=y +CONFIG_IA32_AOUT=y + +## +## file: arch/x86/Kconfig.cpu +## +# CONFIG_PROCESSOR_SELECT is not set + +## +## file: arch/x86/Kconfig.debug +## +CONFIG_STRICT_DEVMEM=y +# CONFIG_X86_VERBOSE_BOOTUP is not set +CONFIG_EARLY_PRINTK=y +# CONFIG_EARLY_PRINTK_DBGP is not set +CONFIG_EARLY_PRINTK_EFI=y +# CONFIG_X86_PTDUMP is not set +CONFIG_DEBUG_RODATA=y +# CONFIG_DEBUG_RODATA_TEST is not set +CONFIG_DEBUG_SET_MODULE_RONX=y +# CONFIG_DEBUG_NX_TEST is not set +CONFIG_DOUBLEFAULT=y +# CONFIG_DEBUG_TLBFLUSH is not set +# CONFIG_IOMMU_DEBUG is not set +# CONFIG_IOMMU_STRESS is not set +# CONFIG_X86_DECODER_SELFTEST is not set +## choice: IO delay type +CONFIG_IO_DELAY_0X80=y +# CONFIG_IO_DELAY_0XED is not set +# CONFIG_IO_DELAY_UDELAY is not set +# CONFIG_IO_DELAY_NONE is not set +## end choice +# CONFIG_DEBUG_BOOT_PARAMS is not set +# CONFIG_CPA_DEBUG is not set +CONFIG_OPTIMIZE_INLINING=y +# CONFIG_DEBUG_NMI_SELFTEST is not set +# CONFIG_X86_DEBUG_STATIC_CPU_HAS is not set + +## +## file: arch/x86/kvm/Kconfig +## +CONFIG_VIRTUALIZATION=y +CONFIG_KVM=m +CONFIG_KVM_INTEL=m +CONFIG_KVM_AMD=m +# CONFIG_KVM_MMU_AUDIT is not set +CONFIG_KVM_DEVICE_ASSIGNMENT=y + +## +## file: arch/x86/xen/Kconfig +## +CONFIG_XEN=y +# CONFIG_XEN_DEBUG_FS is not set +CONFIG_XEN_PVH=y + +## +## file: block/partitions/Kconfig +## +CONFIG_ACORN_PARTITION=y +# CONFIG_ACORN_PARTITION_CUMANA is not set +# CONFIG_ACORN_PARTITION_EESOX is not set +CONFIG_ACORN_PARTITION_ICS=y +# CONFIG_ACORN_PARTITION_ADFS is not set +# CONFIG_ACORN_PARTITION_POWERTEC is not set +CONFIG_ACORN_PARTITION_RISCIX=y +CONFIG_OSF_PARTITION=y +CONFIG_AMIGA_PARTITION=y +CONFIG_ATARI_PARTITION=y +CONFIG_MAC_PARTITION=y +CONFIG_BSD_DISKLABEL=y +CONFIG_MINIX_SUBPARTITION=y +CONFIG_SOLARIS_X86_PARTITION=y +CONFIG_UNIXWARE_DISKLABEL=y +CONFIG_LDM_PARTITION=y +# CONFIG_LDM_DEBUG is not set +CONFIG_SGI_PARTITION=y +CONFIG_ULTRIX_PARTITION=y +CONFIG_SUN_PARTITION=y + +## +## file: crypto/Kconfig +## +CONFIG_CRYPTO_CRC32C_INTEL=m +CONFIG_CRYPTO_CRC32_PCLMUL=m +CONFIG_CRYPTO_GHASH_CLMUL_NI_INTEL=m +#CONFIG_CRYPTO_AES_NI_INTEL can't be set for now when building kernel with clang + +## +## file: drivers/acpi/Kconfig +## +CONFIG_ACPI=y +# CONFIG_ACPI_PROCFS_POWER is not set +# CONFIG_ACPI_EC_DEBUGFS is not set +CONFIG_ACPI_AC=m +CONFIG_ACPI_BATTERY=m +CONFIG_ACPI_BUTTON=m +CONFIG_ACPI_VIDEO=m +CONFIG_ACPI_FAN=m +CONFIG_ACPI_DOCK=y +CONFIG_ACPI_PROCESSOR=m +CONFIG_ACPI_IPMI=m +CONFIG_ACPI_PROCESSOR_AGGREGATOR=m +CONFIG_ACPI_THERMAL=m +# CONFIG_ACPI_DEBUG is not set +CONFIG_ACPI_PCI_SLOT=y +CONFIG_X86_PM_TIMER=y +CONFIG_ACPI_CONTAINER=y +CONFIG_ACPI_HOTPLUG_MEMORY=y +CONFIG_ACPI_SBS=m
Bug#784688: Thousands of xen:balloon: Cannot add additional memory (-17) messages despite dom0 ballooning disabled
On Wednesday, 27.05.2015 at 10:05, Martin Lucina wrote: Does xl mem-set 0 4051 make the messages stop? If not what about using 4050? I'm not sure if this is due to my rebooting the dom0 since I reported this issue, it now appears to be using a slightly different amount of memory just under the target: Domain-0 0 4065 8 r- 36437.3 xl mem-set 0 4065 seems to have made the messages stop. Will run with it for a while and see what happens. No messages for ~4 days, then it started again. What is weird is that dom0 now thinks it has less memory: Domain-0 0 4064 8 r- 41240.6 4064 vs. 4065. I did not change anything. So, something is causing dom0 to change its memory target, despite the fact that ballooning should be disabled. Relevant files from xen_memory0: ./info/current_kb: 4162252 ./info/low_kb: 0 ./info/high_kb: 0 ./max_schedule_delay: 20 ./retry_count: 1 ./target_kb: 4162560 ./target: 4262461440 ./uevent: ./schedule_delay: 1 ./max_retry_count: 0 Any ideas? Martin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150604095408.gc20...@nodbug.lucina.net
Bug#787716: linux-image-4.0.0-2-kirkwood: [feature request] enable CONFIG_ARM_KIRKWOOD_CPUIDLE for the kirkwood platform
Package: src:linux Version: 4.0.4-1 Severity: wishlist Dear Maintainer, Please consider enabling CONFIG_ARM_KIRKWOOD_CPUIDLE for the kirkwood platform. Currently, the .config contains CONFIG_CPU_IDLE=y CONFIG_CPU_IDLE_GOV_LADDER=y CONFIG_CPU_IDLE_GOV_MENU=y but without an actual driver for the cpuidle subsystem, these governors are not doing much. I have rebuilt the 4.0.4-1 kernel to include CONFIG_ARM_KIRKWOOD_CPUIDLE and tested on QNAP TS-212P (Marvell Feroceon). The driver works correctly and the system is stable: root@yukikaze:~$ cat /sys/devices/system/cpu/cpuidle/current_driver kirkwood_idle Using powertop: Frequency stats: Package |CPU 0 1.60 GHz 0.4% | 1.60 GHz 0.4% 533 MHz 8.6% | 533 MHz 8.6% Idle91.1% | Idle91.1% Idle stats: Package |CPU 0 WFI91.1%| WFI90.8%7.0 ms DDR SR 0.0%| DDR SR 0.0%0.0 ms Previously, the 'Idle' state in Frequency stats was not available and the 'Idle stats' tab was blank. Considering that most of devices in this platform running Debian are NASes that spend most of the time idling, this could be a worthwhile option to enable. The size of vmlinuz with this option enabled is 2066520. -- Package-specific info: ** Version: Linux version 4.0.0-2-kirkwood (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 Debian 4.0.4-1 (2015-05-26) ** Command line: console=ttyS0,115200 root=/dev/ram initrd=0xa0,0x90 ramdisk=34816 ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [0.00] Booting Linux on physical CPU 0x0 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Initializing cgroup subsys cpuacct [0.00] Linux version 4.0.0-2-kirkwood ( debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 Debian 4.0.4-1 (2015-05-26) [0.00] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [0.00] CPU: VIVT data cache, VIVT instruction cache [0.00] Machine model: QNAP TS219 family [0.00] Memory policy: Data cache writeback [0.00] On node 0 totalpages: 131072 [0.00] free_area_init_node: node 0, pgdat c05c16fc, node_mem_map dfbf8000 [0.00] DMA zone: 1024 pages used for memmap [0.00] DMA zone: 0 pages reserved [0.00] DMA zone: 131072 pages, LIFO batch:31 [0.00] pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768 [0.00] pcpu-alloc: [0] 0 [0.00] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 130048 [0.00] Kernel command line: console=ttyS0,115200 root=/dev/ram initrd=0xa0,0x90 ramdisk=34816 [0.00] PID hash table entries: 2048 (order: 1, 8192 bytes) [0.00] Dentry cache hash table entries: 65536 (order: 6, 262144 bytes) [0.00] Inode-cache hash table entries: 32768 (order: 5, 131072 bytes) [0.00] Memory: 504240K/524288K available (3866K kernel code, 298K rwdata, 1476K rodata, 272K init, 287K bss, 20048K reserved, 0K cma-reserved, 0K highmem) [0.00] Virtual kernel memory layout: vector : 0x - 0x1000 ( 4 kB) fixmap : 0xffc0 - 0xfff0 (3072 kB) vmalloc : 0xe080 - 0xff00 ( 488 MB) lowmem : 0xc000 - 0xe000 ( 512 MB) pkmap : 0xbfe0 - 0xc000 ( 2 MB) modules : 0xbf00 - 0xbfe0 ( 14 MB) .text : 0xc0008000 - 0xc053fd80 (5344 kB) .init : 0xc054 - 0xc0584000 ( 272 kB) .data : 0xc0584000 - 0xc05ce8e0 ( 299 kB) .bss : 0xc05ce8e0 - 0xc0616898 ( 288 kB) [0.00] NR_IRQS:16 nr_irqs:16 16 [0.12] sched_clock: 32 bits at 200MHz, resolution 5ns, wraps every 21474836475ns [0.000321] Console: colour dummy device 80x30 [0.000345] Calibrating delay loop... 1587.20 BogoMIPS (lpj=3174400) [0.020067] pid_max: default: 32768 minimum: 301 [0.020168] Security Framework initialized [0.020206] Yama: disabled by default; enable with sysctl kernel.yama.* [0.020295] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.020311] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes) [0.020883] Initializing cgroup subsys blkio [0.020905] Initializing cgroup subsys devices [0.020923] Initializing cgroup subsys freezer [0.020939] Initializing cgroup subsys net_cls [0.020962] Initializing cgroup subsys perf_event [0.020982] Initializing cgroup subsys net_prio [0.021054] CPU: Testing write buffer coherency: ok [0.021127] ftrace: allocating 16148 entries in 32 pages [0.038871] Setting up static identity map for 0x3aadf0 - 0x3aae2c [0.039084] mvebu-soc-id: MVEBU SoC ID=0x6282, Rev=0x1 [0.041623] devtmpfs: initialized [0.042801] pinctrl core: initialized pinctrl subsystem [0.047154] NET: Registered protocol family 16 [0.047442] DMA:
Re: Build kernel with clang(sid)
Hello, Thanks for reply. why do you create a full new copy of a config, this is certainly not needed. An option in standard config file must be disable to pass compilation. I am not very familiar with how these options are used. This is the way I found. It's a little ugly indeed. I will try another way. dude break up this patch in logic parts. this an unreadable mess. Sorry for that, I gather everything in one patch make this patch a little big. Should I send them in different parts? I don't get why a clang patch should patch a fs!? You mean patch files in fs? This is for removing valais that clang doesn't support. Many thanks for your time. Cheers, Joseph 2015-06-04 18:21 GMT+08:00 maximilian attems m...@stro.at: On Thu, Jun 04, 2015 at 04:00:18PM +0800, Joseph Lee wrote: I am working on GSOC project bootable clang built debian and need to build Linux with clang. I used patches from LLVMLinux and add a new Kconfig file, modified debian/rules and debian/rules.real. May I report this as a bug(I attached the patch I made)? dude break up this patch in logic parts. this an unreadable mess. I don't get why a clang patch should patch a fs!?
Re: Build kernel with clang(sid)
On Thu, Jun 04, 2015 at 07:44:13PM +0800, Joseph Lee wrote: Hello, Thanks for reply. why do you create a full new copy of a config, this is certainly not needed. An option in standard config file must be disable to pass compilation. I am not very familiar with how these options are used. This is the way I found. It's a little ugly indeed. I will try another way. it is unneeded. Please don't add more noise. see https://wiki.debian.org/DebianKernel for docs dude break up this patch in logic parts. this an unreadable mess. Sorry for that, I gather everything in one patch make this patch a little big. Should I send them in different parts? of course ! nobody is going to seriously review a 100k patch. I don't get why a clang patch should patch a fs!? You mean patch files in fs? This is for removing valais that clang doesn't support. I do not care about whatever patchset you want to promote, our policy concerning that is pretty clear: https://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines Hence if you want any non bugfix patches, get them upstream accepted first. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150604115029.gg10...@stro.at
