Bug#806952: Enable CONFIG_MOUSE_ELAN_I2C
Package: linux-latest Version: 68 Dear Maintainers, There is a fairly trivially fixed, but ignored bug report here (since July): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791631 It is a request to enable the config options MOUSE_ELAN_I2C, MOUSE_ELAN_I2C_I2C and MOUSE_ELAN_I2C_SMBUS. This is a driver for the touchpad in some Acer laptops (and maybe others). It would be nice to add this to older kernel versions as well and to backport it, since the touchpad has been around for some time. Best regards, Florian Uekermann
Bug#806951: Please enable CONFIG_MOUSE_ELAN_I2C
Package: linux-latest Version: 68 Dear Maintainers, There is a fairly trivially fixed, but ignored bug report here (since July): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791631 It is a request to enable the config options MOUSE_ELAN_I2C, MOUSE_ELAN_I2C_I2C and MOUSE_ELAN_I2C_SMBUS. This is a driver for the touchpad in some Acer laptops (and maybe others). It would be nice to add this to older kernel versions as well and to backport it, since the touchpad has been around for some time. Best regards, Florian Uekermann
Processed: merging 806951 806952
Processing commands for cont...@bugs.debian.org: > merge 806951 806952 Bug #806951 [linux-latest] Please enable CONFIG_MOUSE_ELAN_I2C Bug #806952 [linux-latest] Enable CONFIG_MOUSE_ELAN_I2C Bug #806952 [linux-latest] Enable CONFIG_MOUSE_ELAN_I2C Merged 806951 806952 > thanks Stopping processing here. Please contact me if you need assistance. -- 806951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806951 806952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: merging 806951 806952
Processing commands for cont...@bugs.debian.org: > merge 806951 806952 Bug #806951 [linux-latest] Please enable CONFIG_MOUSE_ELAN_I2C Bug #806952 [linux-latest] Enable CONFIG_MOUSE_ELAN_I2C Merged 806951 806952 > thanks Stopping processing here. Please contact me if you need assistance. -- 806951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806951 806952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806952 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#806951: marked as done (Please enable CONFIG_MOUSE_ELAN_I2C)
Your message dated Thu, 03 Dec 2015 12:38:55 + with message-id <1449146335.30642.59.ca...@decadent.org.uk> and subject line Re: Bug#806951: Please enable CONFIG_MOUSE_ELAN_I2C has caused the Debian Bug report #806951, regarding Please enable CONFIG_MOUSE_ELAN_I2C to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-latest Version: 68 Dear Maintainers, There is a fairly trivially fixed, but ignored bug report here (since July): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791631 It is a request to enable the config options MOUSE_ELAN_I2C, MOUSE_ELAN_I2C_I2C and MOUSE_ELAN_I2C_SMBUS. This is a driver for the touchpad in some Acer laptops (and maybe others). It would be nice to add this to older kernel versions as well and to backport it, since the touchpad has been around for some time. Best regards, Florian Uekermann --- End Message --- --- Begin Message --- On Thu, 2015-12-03 at 07:23 -0500, Florian Uekermann wrote: > Package: linux-latest > Version: 68 > > Dear Maintainers, > > There is a fairly trivially fixed, but ignored bug report here (since July): > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791631 [...] It's not ignored; you can see it's tagged pending. And even if it was, that's no reason to send a new bug report. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part --- End Message ---
Bug#806952: marked as done (Enable CONFIG_MOUSE_ELAN_I2C)
Your message dated Thu, 03 Dec 2015 12:38:55 + with message-id <1449146335.30642.59.ca...@decadent.org.uk> and subject line Re: Bug#806951: Please enable CONFIG_MOUSE_ELAN_I2C has caused the Debian Bug report #806951, regarding Enable CONFIG_MOUSE_ELAN_I2C to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 806951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=806951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-latest Version: 68 Dear Maintainers, There is a fairly trivially fixed, but ignored bug report here (since July): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791631 It is a request to enable the config options MOUSE_ELAN_I2C, MOUSE_ELAN_I2C_I2C and MOUSE_ELAN_I2C_SMBUS. This is a driver for the touchpad in some Acer laptops (and maybe others). It would be nice to add this to older kernel versions as well and to backport it, since the touchpad has been around for some time. Best regards, Florian Uekermann --- End Message --- --- Begin Message --- On Thu, 2015-12-03 at 07:23 -0500, Florian Uekermann wrote: > Package: linux-latest > Version: 68 > > Dear Maintainers, > > There is a fairly trivially fixed, but ignored bug report here (since July): > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=791631 [...] It's not ignored; you can see it's tagged pending. And even if it was, that's no reason to send a new bug report. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part --- End Message ---
btrfs issue with kernel from experimental
Hi, dmesg is telling me that btrfs is aborting transactions; [94881.487330] [ cut here ] [94881.487350] WARNING: CPU: 2 PID: 3501 at /build/linux-7sjCdl/linux-4.3/fs/btrfs/extent-tree.c:6360 __btrfs_free_extent.isra.69+0x2f3/0xd30 [btrfs]() [94881.487352] BTRFS: Transaction aborted (error -5) [94881.487353] Modules linked in: uas usb_storage fuse rfcomm binfmt_misc bnep snd_hda_codec_hdmi ax88179_178a usbnet mii intel_rapl iosf_mbi x86_pkg_temp_thermal intel_powerclamp dell_wmi sparse_keymap coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul hid_generic jitterentropy_rng btusb btrtl btbcm btintel iTCO_wdt joydev bluetooth iTCO_vendor_support hid_rmi sha256_ssse3 sha256_generic hmac drbg dell_laptop dcdbas dell_smm_hwmon ansi_cprng aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd i915 pcspkr psmouse evdev serio_raw uvcvideo videobuf2_vmalloc videobuf2_memops sg videobuf2_core v4l2_common snd_hda_codec_realtek videodev hid_multitouch snd_hda_codec_generic media arc4 snd_soc_rt5640 snd_soc_rl6231 snd_hda_intel snd_soc_core snd_hda_codec snd_compress i2c_i801 snd_hda_core [94881.487395] snd_hwdep snd_pcm drm_kms_helper mei_me lpc_ich mfd_core snd_timer drm snd shpchp soundcore mei i2c_algo_bit wmi battery regmap_i2c snd_soc_sst_acpi dw_dmac dw_dmac_core video i2c_designware_platform i2c_designware_core button intel_smartconnect ac processor iwlmvm mac80211 loop iwlwifi cfg80211 rfkill parport_pc ppdev lp parport autofs4 ext4 crc16 mbcache jbd2 btrfs xor usbhid raid6_pq sd_mod crc32c_intel ahci libahci libata ehci_pci xhci_pci scsi_mod ehci_hcd xhci_hcd usbcore usb_common thermal sdhci_acpi sdhci mmc_core i2c_hid hid [94881.487432] CPU: 2 PID: 3501 Comm: umount Tainted: GW 4.3.0-trunk-amd64 #1 Debian 4.3-1~exp1 [94881.487434] Hardware name: Dell Inc. XPS13 9333/0D13CM, BIOS A04 03/19/2014 [94881.487436] a02b3250 812c53a9 880049a8fad8 8106ebad [94881.487439] fffb 880049a8fb28 8801e1222800 8801381b [94881.487441] 8106ec2c a02b3420 00a80020 [94881.487443] Call Trace: [94881.487450] [] ? dump_stack+0x40/0x57 [94881.487453] [] ? warn_slowpath_common+0x7d/0xb0 [94881.487455] [] ? warn_slowpath_fmt+0x4c/0x50 [94881.487459] [] ? kmem_cache_alloc+0x191/0x1a0 [94881.487468] [] ? __btrfs_free_extent.isra.69+0x2f3/0xd30 [btrfs] [94881.487472] [] ? internal_add_timer+0x34/0x80 [94881.487474] [] ? add_timer_on+0xab/0x110 [94881.487483] [] ? __btrfs_run_delayed_refs+0x987/0x1050 [btrfs] [94881.487492] [] ? btrfs_run_delayed_refs+0x78/0x2a0 [btrfs] [94881.487505] [] ? commit_cowonly_roots+0x7f/0x285 [btrfs] [94881.487514] [] ? btrfs_run_delayed_refs+0x1da/0x2a0 [btrfs] [94881.487529] [] ? btrfs_qgroup_account_extents+0x6d/0x100 [btrfs] [94881.487541] [] ? btrfs_commit_transaction+0x5e4/0xaa0 [btrfs] [94881.487551] [] ? close_ctree+0x27f/0x320 [btrfs] [94881.487555] [] ? generic_shutdown_super+0x64/0xf0 [94881.487557] [] ? kill_anon_super+0xe/0x20 [94881.487564] [] ? btrfs_kill_super+0x13/0x100 [btrfs] [94881.487566] [] ? deactivate_locked_super+0x34/0x60 [94881.487570] [] ? cleanup_mnt+0x3b/0x80 [94881.487573] [] ? task_work_run+0x71/0x90 [94881.487576] [] ? prepare_exit_to_usermode+0xce/0xf0 [94881.487579] [] ? int_ret_from_sys_call+0x25/0x8f [94881.487580] ---[ end trace 9e5f60211f33f267 ]--- [94881.487583] BTRFS: error (device sdb1) in __btrfs_free_extent:6360: errno=-5 IO failure [94881.487586] BTRFS info (device sdb1): forced readonly [94881.487588] BTRFS: error (device sdb1) in btrfs_run_delayed_refs:2851: errno=-5 IO failure [94881.487590] BTRFS warning (device sdb1): Skipping commit of aborted transaction. [94881.487592] BTRFS: error (device sdb1) in cleanup_transaction:1741: errno=-5 IO failure [94881.487603] BTRFS error (device sdb1): commit super ret -5 Is this a bug I ought to file upstream? And if so, where, btrfs and/or kernel? Regards, Jeremiah
Bug#807000: initramfs-tools: module nvme not included in block modules on kernel > 4.2
Package: initramfs-tools Version: 0.120 Severity: normal Dear Maintainer, I tried creating an initrd on a system with an NVMe SSD PCIe card. The card is supported using the nvme kernel module and with the 4.2 kernel I was successfully able to boot the system. However, the upcoming 4.4 kernel includes a commit that moves the nvme module from drivers/block/nvme into its own directory drivers/nvme (see https://github.com/torvalds/linux/commit/57dacad5f2288e3de91f99b29f07b4a2793446d2), therefore preventing it from being automatically added to the list of modules included in the initrd. Adding the module manually to the initramfs configuration solves the issue. Here's a patch that adds the module again to the 'most' set: - --- hook-functions 2015-12-03 23:14:12.150731429 +0100 +++ hook-functions.new 2015-12-03 23:14:02.758856723 +0100 @@ -526,6 +526,7 @@ modules="$modules nfs nfsv2 nfsv3 nfsv4" modules="$modules af_packet atkbd i8042" modules="$modules virtio_pci virtio_mmio" + modules="$modules nvme" # Include all HID drivers unless we're sure they # don't support keyboards. hid-*ff covers various - Thanks, Philipp -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 19M Oct 7 17:39 /boot/initrd.img-4.2.0-1-amd64 -rw-r--r-- 1 root root 20M Dec 3 22:32 /boot/initrd.img-4.4.0-rc3 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.4.0-rc3 root=/dev/mapper/Debian-root ro quiet -- resume RESUME=/dev/mapper/Debian-swap_1 -- /proc/filesystems ext3 ext2 ext4 vfat fuseblk -- lsmod Module Size Used by fuse 94208 3 rfcomm 69632 2 bnep 20480 2 joydev 20480 0 snd_hda_codec_hdmi 49152 1 dell_wmi 16384 0 dell_laptop20480 0 dcdbas 16384 1 dell_laptop dell_led 16384 1 sparse_keymap 16384 1 dell_wmi intel_rapl 20480 0 x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 nls_utf8 16384 1 coretemp 16384 0 kvm_intel 167936 0 nls_cp437 20480 1 kvm 507904 1 kvm_intel vfat 20480 1 fat69632 1 vfat snd_hda_codec_realtek81920 1 irqbypass 16384 1 kvm snd_hda_codec_generic73728 1 snd_hda_codec_realtek efi_pstore 16384 0 snd_hda_intel 36864 6 psmouse 118784 0 pcspkr 16384 0 serio_raw 16384 0 efivars20480 1 efi_pstore snd_hda_codec 131072 4 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_intel snd_hda_core 65536 5 snd_hda_codec_realtek,snd_hda_codec_hdmi,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel snd_hwdep 16384 1 snd_hda_codec brcmfmac 233472 0 snd_pcm 102400 4 snd_hda_codec_hdmi,snd_hda_codec,snd_hda_intel,snd_hda_core snd_timer 32768 1 snd_pcm brcmutil 16384 1 brcmfmac snd81920 20 snd_hda_codec_realtek,snd_hwdep,snd_timer,snd_hda_codec_hdmi,snd_pcm,snd_hda_codec_generic,snd_hda_codec,snd_hda_intel uvcvideo 90112 0 soundcore 16384 1 snd i2c_i801 20480 0 rtsx_pci_ms20480 0 cfg80211 528384 1 brcmfmac videobuf2_vmalloc 16384 1 uvcvideo videobuf2_memops 16384 1 videobuf2_vmalloc memstick 20480 1 rtsx_pci_ms videobuf2_v4l2 28672 1 uvcvideo videobuf2_core 32768 2 uvcvideo,videobuf2_v4l2 v4l2_common16384 1 videobuf2_v4l2 videodev 167936 4 uvcvideo,v4l2_common,videobuf2_core,videobuf2_v4l2 media 24576 2 uvcvideo,videodev shpchp 36864 0 btusb 45056 0 btrtl 16384 1 btusb mei_me 28672 0 mei94208 1 mei_me processor_thermal_device16384 0 intel_soc_dts_iosf 16384 1 processor_thermal_device iosf_mbi 16384 2 intel_soc_dts_iosf,intel_rapl wmi16384 2 dell_led,dell_wmi battery16384 0 hci_uart 73728 0 btbcm 16384 2 btusb,hci_uart btintel16384 2 btusb,hci_uart bluetooth 503808 30 bnep,btbcm,btrtl,btusb,hci_uart,rfcomm,btintel evdev 24576 15 rfkill 24576 7 cfg80211,bluetooth,dell_laptop tpm_tis20480 0 tpm45056 1 tpm_tis int3400_thermal16384 0 processor 36864 0 acpi_thermal_rel 16384 1 int3400_thermal int3403_thermal16384 0 int340x_thermal_zone16384 2 processor_thermal_device,int3403_thermal ac
Bug#588675: / left as /dev/root with non-initrd kernel
On 12/02/2015 04:30 PM, Elliott Mitchell wrote:
> You're thinking of the wrong bug. #588675 is the bug # for /proc/mounts
> having "/dev/root" listed as the device for the root filesystem. Your
Indeed, I think I confused this with #656333 ("Please ignore rootfs in
df output"), which may be related to this one.
> previous mention indicated you would expect "/dev/sda6" to be there. I'm
> guessing prior to wheezy, when you were using BLK_DEV_IDE_PMAC, you would
> have been seeing "/dev/hda6" listed as the root device?
Again, I'm afraid I don't remember what I've seen prior to wheezy. The
system is running 24x7 but I'll try to boot a pre-wheezy image (or
something with BLK_DEV_IDE_PMAC enabled) the next time this machine is
rebooted and see if the actual disk or /dev/rootfs is displayed.
Christian.
Bug#807004: initramfs-tools: Breaks when installing kdump-tools with bcache rootfs
Package: initramfs-tools Version: 0.120 Severity: important Tags: patch I have /dev/bcache0 as my rootfs. When upgrading kdump-tools, the postinst fails because /etc/kernel/postinst.d/kdump-tools returns an error. When I run this manually, I get: kdump-tools: Generating /var/lib/kdump/initrd.img-4.2.0-1-amd64 mkinitramfs: for device /dev/bcache0 missing bcache /sys/block/ entry mkinitramfs: workaround is MODULES=most mkinitramfs: Error please report the bug The "missing bcache /sys/block/ entry" message comes from dep_add_modules_mount in /usr/share/initramfs-tools/hook-functions The problem is that the "classical block device" case strips the numeric suffix from the device name, but this is needed for the entry in /sys/block. The attached patch fixes the problem, although I don't know if it's the best way to solve it. -- Package-specific info: -- initramfs sizes -rw-r--r-- 1 root root 18M Dec 3 17:06 /boot/initrd.img-4.2.0-1-amd64 -- /proc/cmdline BOOT_IMAGE=/vmlinuz-4.2.0-1-amd64 root=UUID=8e8ffc83-7eb2-4f54-8119-aafad05e1921 ro cgroup_enable=memory crashkernel=256M resume=UUID=752ca093-5231-4349-afc1-e63c1b549954 quiet -- resume RESUME=UUID=19307990-fe33-4596-ad78-2ba36dff42ba -- /proc/filesystems ext3 ext2 ext4 vfat fuseblk xfs jfs msdos ntfs minix hfs hfsplus qnx4 ufs btrfs -- lsmod Module Size Used by cfg80211 532480 0 nfnetlink_queue20480 0 nfnetlink_log 20480 0 nfnetlink 16384 2 nfnetlink_log,nfnetlink_queue bluetooth 499712 0 btrfs 933888 0 xor24576 1 btrfs raid6_pq 102400 1 btrfs ufs77824 0 qnx4 16384 0 hfsplus 102400 0 hfs53248 0 minix 36864 0 ntfs 200704 0 msdos 20480 0 jfs 176128 0 xfs 913408 0 libcrc32c 16384 1 xfs dm_mod106496 0 cpuid 16384 0 fuse 94208 3 xt_addrtype16384 2 br_netfilter 24576 0 overlay45056 0 xt_multiport 16384 1 xt_CHECKSUM16384 1 iptable_mangle 16384 1 ipt_MASQUERADE 16384 4 nf_nat_masquerade_ipv416384 1 ipt_MASQUERADE iptable_nat16384 1 nf_nat_ipv416384 1 iptable_nat nf_nat 24576 2 nf_nat_ipv4,nf_nat_masquerade_ipv4 nf_conntrack_ipv4 20480 3 nf_defrag_ipv4 16384 1 nf_conntrack_ipv4 xt_conntrack 16384 2 nf_conntrack 110592 5 nf_nat,nf_nat_ipv4,xt_conntrack,nf_nat_masquerade_ipv4,nf_conntrack_ipv4 ipt_REJECT 16384 2 nf_reject_ipv4 16384 1 ipt_REJECT xt_tcpudp 16384 6 tun28672 1 bridge110592 1 br_netfilter stp16384 1 bridge llc16384 2 stp,bridge ebtable_filter 16384 0 ebtables 36864 1 ebtable_filter ip6table_filter16384 0 ip6_tables 28672 1 ip6table_filter iptable_filter 16384 1 ip_tables 28672 3 iptable_filter,iptable_mangle,iptable_nat x_tables 36864 13 ip6table_filter,xt_CHECKSUM,ip_tables,xt_tcpudp,ipt_MASQUERADE,xt_conntrack,xt_multiport,iptable_filter,ebtables,ipt_REJECT,iptable_mangle,ip6_tables,xt_addrtype binfmt_misc20480 1 nfsd 282624 2 auth_rpcgss57344 1 nfsd oid_registry 16384 1 auth_rpcgss nfs_acl16384 1 nfsd nfs 249856 0 lockd 90112 2 nfs,nfsd grace 16384 2 nfsd,lockd fscache61440 1 nfs sunrpc327680 6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl nls_utf8 16384 1 nls_cp437 20480 1 vfat 20480 1 fat69632 2 vfat,msdos x86_pkg_temp_thermal16384 0 intel_powerclamp 16384 0 kvm_intel 163840 0 kvm 495616 1 kvm_intel crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 amdkfd118784 1 radeon 1499136 8 sha256_ssse3 28672 1 sha256_generic 24576 1 sha256_ssse3 hmac 16384 1 drbg 24576 1 ansi_cprng 16384 0 eeepc_wmi 16384 0 asus_wmi 28672 1 eeepc_wmi aesni_intel 167936 0 sparse_keymap 16384 1 asus_wmi ttm94208 1 radeon rfkill 24576 5 cfg80211,bluetooth,asus_wmi snd_hda_codec_realtek86016 1 aes_x86_64 20480 1 aesni_intel iTCO_wdt 16384 0 lrw16384 1 aesni_intel drm_kms_helper126976 1 radeon iTCO_vendor_support
Bug#805098: [armhf] stmmac platform modules missing from nic-modules
On Thu, 2015-12-03 at 19:08 +0100, Karsten Merker wrote: > On Sat, Nov 14, 2015 at 06:17:32PM +, Ben Hutchings wrote: > > On Sat, 2015-11-14 at 13:28 +0100, Karsten Merker wrote: > > [...] > > > it looks as if we have two separate issues here. One of them is a > > > bug in ethdetect, which should be fixed with the attached patch. > > > With this patch applied, the hang does not occur anymore, but d-i > > > doesn't detect any network interface either. This in turn seems > > > to stem from missing modules, which is the result of a series of > > > upstream kernel changes to the stmmac driver that have split out > > > functionality from an existing module into different sub-modules: > > [...] > > > As a result, the installer nic-modules list in the Debian kernel > > > package needs to be adjusted accordingly. I'll prepare a patch > > > for the kernel package, but I probably won't be able to actually > > > test it before tomorrow as building it takes quite some time on > > > my (comparatively slow) hardware. > > > > Based on the platform modules that are currently being selected, I'm > > intending to apply this: > > > > diff --git a/debian/changelog b/debian/changelog > > index 0053bf9..5eca6d3 100644 > > --- a/debian/changelog > > +++ b/debian/changelog > > @@ -21,6 +21,8 @@ linux (4.3-1~exp2) UNRELEASED; urgency=medium > > * [armhf] Enable new drivers for Allwinner chips (Closes: #804856) > > - crypto: Enable CRYPTO_DEV_SUN4I_SS as module > > - musb: Enable USB_MUSB_SUNXI as module > > + * [armhf] udeb: Add stmmac platform modules dwmac-generic, dwmac-socfpga > > +and dwmac-sunxi to nic-modules (Closes: #805098) > > > > [ Ian Campbell ] > > * [armel/orion5x] Enable Device Tree for orion5x. Patch from Roger > > Shimizu > > diff --git a/debian/config/armhf/config.armmp > > b/debian/config/armhf/config.armmp > > index 4d65053..d6ce545 100644 > > --- a/debian/config/armhf/config.armmp > > +++ b/debian/config/armhf/config.armmp > > @@ -596,6 +596,9 @@ CONFIG_SMSC911X=m > > ## file: drivers/net/ethernet/stmicro/stmmac/Kconfig > > ## > > CONFIG_STMMAC_ETH=m > > +CONFIG_DWMAC_GENERIC=m > > +CONFIG_DWMAC_SOCFPGA=m > > +CONFIG_DWMAC_SUNXI=m > > > > ## > > ## file: drivers/net/ethernet/ti/Kconfig > > diff --git a/debian/installer/armhf/modules/armhf-armmp/nic-modules > > b/debian/installer/armhf/modules/armhf-armmp/nic-modules > > index 13086f0..e3d0df7 100644 > > --- a/debian/installer/armhf/modules/armhf-armmp/nic-modules > > +++ b/debian/installer/armhf/modules/armhf-armmp/nic-modules > > @@ -4,6 +4,9 @@ mvmdio > > smsc911x > > stmmac > > stmmac-platform > > +dwmac-generic > > +dwmac-socfpga > > +dwmac-sunxi > > sun4i-emac > > xgmac > > ti_cpsw > > Hello Ben, > > I've just looked at the debian kernel repository and have seen > that the patch is in the master (kernel 4.3) branch, but not in > the sid (kernel 4.2) branch. The problem exists already in > kernel 4.2 - could you apply the patch to the sid branch as well? Maybe. I had expected there to be a 4.3.1 release by now, which could be uploaded to unstable. As that still hasn't appeared (and it isn't even under review), perhaps I'll make another 4.2-based upload. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Bug#807004: initramfs-tools: Breaks when installing kdump-tools with bcache rootfs
Here's a patch for the initramfs-tools git repo.
Bug#807004: [PATCH] Handle bcache devices correctly (Closes: #807004)
---
hook-functions | 3 +++
1 file changed, 3 insertions(+)
diff --git a/hook-functions b/hook-functions
index ee1c205..97626ec 100644
--- a/hook-functions
+++ b/hook-functions
@@ -434,6 +434,9 @@ dep_add_modules_mount()
block=${dev_node#/dev/i2o/}
block=${block%%[0-9]*}
block='i2o!'$block
+ # bcache device
+ elif [ "${dev_node#/dev/bcache}" != "${dev_node}" ]; then
+ block=${dev_node#/dev/}
# classical block device
else
block=${dev_node#/dev/}
--
2.6.2
Uploading linux (4.2.6-2)
I intend to upload linux version 4.2.6-2 to unstable on Friday or Saturday. This has a few security fixes, plus I've cherry-picked all the relevant bug fixes from the master branch. There should not be any ABI change. Ben. -- Ben Hutchings For every action, there is an equal and opposite criticism. - Harrison signature.asc Description: This is a digitally signed message part
Bug#588675: / left as /dev/root with non-initrd kernel
On Thu, Dec 03, 2015 at 03:11:45PM -0800, Christian Kujau wrote:
> On 12/02/2015 04:30 PM, Elliott Mitchell wrote:
> > You're thinking of the wrong bug. #588675 is the bug # for /proc/mounts
> > having "/dev/root" listed as the device for the root filesystem. Your
>
> Indeed, I think I confused this with #656333 ("Please ignore rootfs in
> df output"), which may be related to this one.
So many bugs, so little time. :-/ This actually effected many other
utilities as well. I'm a bit surprised if this is getting fixed in the
kernel, I thought the kernel maintainers had decided "this is the way the
kernel does this, userspace needs to compensate".
> > previous mention indicated you would expect "/dev/sda6" to be there. I'm
> > guessing prior to wheezy, when you were using BLK_DEV_IDE_PMAC, you would
> > have been seeing "/dev/hda6" listed as the root device?
>
> Again, I'm afraid I don't remember what I've seen prior to wheezy. The
> system is running 24x7 but I'll try to boot a pre-wheezy image (or
> something with BLK_DEV_IDE_PMAC enabled) the next time this machine is
> rebooted and see if the actual disk or /dev/rootfs is displayed.
Thanks. I'm pretty sure it will show the actual disk, but another
confirmation will help.
--
(\___(\___(\__ --=> 8-) EHM <=-- __/)___/)___/)
\BS (| ehem+sig...@m5p.com PGP 87145445 |) /
\_CS\ | _ -O #include O- _ | / _/
8A19\___\_|_/58D2 7E3D DDF4 7BA6 <-PGP-> 41D1 B375 37D0 8714\_|_/___/5445
