Bug#794849: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#794849: linux: custom linux-image packages fail to install)
Control: reopen -1 Control: reassign -1 os-prober On Wed, 2015-08-12 at 23:19 +0200, Stefan Bucur wrote: Thanks Ben for the advice and sorry for the latency. The steps you're suggesting are indeed more straightforward. However, the generated .deb packages still fail to install properly. I repeated the procedure on several fresh Debian 8.1 installations, using default settings in the installer, with the same outcome. After some digging, I realized that the root failure seems to first occur inside the running kernel (!!), during the dpkg installation. Below is the relevant dmesg output during dpkg -i: [...] All these warnings are likely to be the fault of os-prober which runs during kernel upgrades. Ben. -- Ben Hutchings Time is nature's way of making sure that everything doesn't happen at once. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#794849: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#794849: linux: custom linux-image packages fail to install)
Processing control commands:
reopen -1
Bug #794849 {Done: Ben Hutchings b...@decadent.org.uk} [src:linux] linux:
custom linux-image packages fail to install
Bug reopened
Ignoring request to alter fixed versions of bug #794849 to the same values
previously set
reassign -1 os-prober
Bug #794849 [src:linux] linux: custom linux-image packages fail to install
Bug reassigned from package 'src:linux' to 'os-prober'.
Ignoring request to alter found versions of bug #794849 to the same values
previously set
Ignoring request to alter fixed versions of bug #794849 to the same values
previously set
--
794849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794849
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Bug#761469: closed by Ben Hutchings b...@decadent.org.uk (Re: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb)
On Wed, 2015-08-12 at 17:57 -0400, Dylan Cali wrote: Ben, So are you basically saying this problem is not fixable, and switching tty's can't be expected to work under xen? I think it should work if you use a standard VGA console or a native (KMS) graphics driver. Only uvesafb won't work. Ben. -- Ben Hutchings Time is nature's way of making sure that everything doesn't happen at once. signature.asc Description: This is a digitally signed message part
Bug#794849: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#794849: linux: custom linux-image packages fail to install)
On Wed, Aug 12, 2015 at 11:19 PM, Stefan Bucur stefan.bu...@gmail.com wrote: Thanks Ben for the advice and sorry for the latency. The steps you're suggesting are indeed more straightforward. However, the generated .deb packages still fail to install properly. I repeated the procedure on several fresh Debian 8.1 installations, using default settings in the installer, with the same outcome. After some digging, I realized that the root failure seems to first occur inside the running kernel (!!), during the dpkg installation. Below is the relevant dmesg output during dpkg -i: [ 708.498832] device-mapper: uevent: version 1.0.3 [ 708.498991] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com [ 709.089486] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 709.095776] JFS: nTxBlock = 8192, nTxLock = 65536 [ 709.108028] ntfs: driver 2.1.30 [Flags: R/W MODULE]. [ 709.119640] QNX4 filesystem 0.2.3 registered. [ 709.190614] raid6: mmxx1 4992 MB/s [ 709.258663] raid6: mmxx2 5880 MB/s [ 709.326691] raid6: sse1x14514 MB/s [ 709.394717] raid6: sse1x25192 MB/s [ 709.462765] raid6: sse2x19530 MB/s [ 709.530787] raid6: sse2x2 11756 MB/s [ 709.530790] raid6: using algorithm sse2x2 (11756 MB/s) [ 709.530791] raid6: using ssse3x1 recovery algorithm [ 709.532132] xor: automatically using best checksumming function: [ 709.570816]avx : 20117.000 MB/sec [ 709.583698] Btrfs loaded [ 709.587963] fuse init (API version 7.23) [ 709.633347] EXT4-fs (sda2): unable to read superblock [ 709.634932] EXT4-fs (sda2): unable to read superblock [ 709.636302] EXT4-fs (sda2): unable to read superblock [ 709.638439] XFS (sda2): Invalid superblock magic number [ 709.641380] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 709.641576] FAT-fs (sda2): bogus number of reserved sectors [ 709.641643] FAT-fs (sda2): Can't find a valid FAT filesystem [ 709.642860] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 709.643015] FAT-fs (sda2): bogus number of reserved sectors [ 709.643080] FAT-fs (sda2): Can't find a valid FAT filesystem [ 709.648183] ntfs: (device sda2): read_ntfs_boot_sector(): Primary boot sector is invalid. [ 709.648322] ntfs: (device sda2): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover. [ 709.648423] ntfs: (device sda2): ntfs_fill_super(): Not an NTFS volume. [ 709.650203] MINIX-fs: unable to read superblock [ 709.651596] attempt to access beyond end of device [ 709.651598] sda2: rw=16, want=3, limit=2 [ 709.651600] hfsplus: unable to find HFS+ superblock [ 709.653236] qnx4: no qnx4 filesystem (no root dir). [ 709.654695] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... WARNING Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 709.657400] hfs: can't find a HFS filesystem on dev sda2 The EXT4-fs, FAT-fs, and ntfs errors seems suspicious, since the hardware doesn't seem faulty. Moreover, I ran this inside different virtual machines, all failing in the same way. Let me know if you'd need any extra information. I also discovered that the errors I'm getting are very similar to the ones reported here: http://www.linuxquestions.org/questions/linux-newbie-8/extended-partition-error-on-boot-4175542138/ In my case, the kernel installation scripts also seem to attempt to mount an extended partition (sda2). Here is the output of fdisk on my machine: $ sudo fdisk -l Disk /dev/sda: 20 GiB, 21474836480 bytes, 41943040 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0xc34760e8 Device BootStart End Sectors Size Id Type /dev/sda1 *2048 40136703 40134656 19.1G 83 Linux /dev/sda2 40138750 41940991 1802242 880M 5 Extended /dev/sda5 40138752 41940991 1802240 880M 82 Linux swap / Solaris Stefan
Bug#761469: closed by Ben Hutchings b...@decadent.org.uk (Re: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb)
Ben, So are you basically saying this problem is not fixable, and switching tty's can't be expected to work under xen? Thanks, Dylan On Wed, Aug 12, 2015 at 9:31 AM, Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the src:linux package: #761469: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb It has been closed by Ben Hutchings b...@decadent.org.uk. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Ben Hutchings b...@decadent.org.uk by replying to this email. -- 761469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Forwarded message -- From: Ben Hutchings b...@decadent.org.uk To: 761469-d...@bugs.debian.org Cc: Date: Wed, 12 Aug 2015 15:17:08 +0200 Subject: Re: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb This is not a configuration issue. uvesafb requires making BIOS calls, but Xen PV domains do not have access to the BIOS. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. -- Forwarded message -- From: Dylan Cali calid1...@gmail.com To: Debian Bug Tracking System sub...@bugs.debian.org Cc: Date: Sun, 14 Sep 2014 00:16:34 -0500 Subject: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb Package: xen-linux-system-3.2.0-4-amd64 Version: 3.2.60-1+deb7u3 Severity: important Dear Maintainer, Original symptom: under x11 switching tty's causes blank screen and monitor going to sleep. Researching indicated this could be related to having a Nvidia graphics card as well as a missing or misconfigured uvesafb module. [1] Checking dmesg showed the following error: [4.796570] uvesafb: Getting VBE info block failed (eax=0x4f00, err=0) [4.796635] uvesafb: vbe_init() failed with -22 [4.796688] uvesafb: probe of uvesafb.0 failed with error -22 Also /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes did not exist. When booting with the standard Debian linux kernel instead of xen tty switching under x11 worked as expected. There were no errors in demsg output: [3.275811] uvesafb: NVIDIA Corporation, GF110 Board - 12610002, Chip Rev , OEM: NVIDIA, VBE v3.0 [3.385649] uvesafb: VBIOS/hardware doesn't support DDC transfers [3.385651] uvesafb: no monitor limits have been set, default refresh rate will be used [3.386354] uvesafb: scrolling: redraw [3.563068] uvesafb: framebuffer at 0xf100, mapped to 0xc9000668, using 14336k, total 14336k Also /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes existed with expected content. This seems to indicate the Debian xen kernel has not been correctly configured for use with the uvesafb module. [1] https://bbs.archlinux.org/viewtopic.php?id=120326 -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-linux-system-3.2.0-4-amd64 depends on: ii linux-image-3.2.0-4-amd64 3.2.60-1+deb7u3 ii xen-system-amd64 4.1.4-3+deb7u2 xen-linux-system-3.2.0-4-amd64 recommends no packages. xen-linux-system-3.2.0-4-amd64 suggests no packages. -- no debconf information
Bug#795318: Subject: firmware-linux-nonfree: kernel modeswitching on radeon hardware broken
Package: firmware-linux-nonfree Version: 0.44 Severity: important when using fglrx for 3d acceleration all modeswitching provided by the non-free kernel module is moot point. There simply is no vterm at all to switch to.If for any reason X11 breaks you are up shit creek and must play whack-a-mole with the hard reset button to recover. This may be a config issue but the config needs to be posted somewhere so people know what to do. Using PITCAIRN hardware(HD 7850 x2). -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-linux-nonfree depends on no packages. firmware-linux-nonfree recommends no packages. Versions of packages firmware-linux-nonfree suggests: ii initramfs-tools 0.120 -- no debconf information
Bug#795318: marked as done (Subject: firmware-linux-nonfree: kernel modeswitching on radeon hardware broken)
Your message dated Thu, 13 Aug 2015 00:24:35 +0200 with message-id 1439418275.10857.85.ca...@decadent.org.uk and subject line Re: Bug#795318: Subject: firmware-linux-nonfree: kernel modeswitching on radeon hardware broken has caused the Debian Bug report #795318, regarding Subject: firmware-linux-nonfree: kernel modeswitching on radeon hardware broken 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.) -- 795318: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795318 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: firmware-linux-nonfree Version: 0.44 Severity: important when using fglrx for 3d acceleration all modeswitching provided by the non-free kernel module is moot point. There simply is no vterm at all to switch to.If for any reason X11 breaks you are up shit creek and must play whack-a-mole with the hard reset button to recover. This may be a config issue but the config needs to be posted somewhere so people know what to do. Using PITCAIRN hardware(HD 7850 x2). -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 4.0.0-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) firmware-linux-nonfree depends on no packages. firmware-linux-nonfree recommends no packages. Versions of packages firmware-linux-nonfree suggests: ii initramfs-tools 0.120 -- no debconf information ---End Message--- ---BeginMessage--- On Wed, 2015-08-12 at 16:57 -0500, richard jasmin wrote: Package: firmware-linux-nonfree Version: 0.44 Severity: important when using fglrx for 3d acceleration all modeswitching provided by the non-free kernel module is moot point. There simply is no vterm at all to switch to.If for any reason X11 breaks you are up shit creek and must play whack-a-mole with the hard reset button to recover. This may be a config issue but the config needs to be posted somewhere so people know what to do. Using PITCAIRN hardware(HD 7850 x2). This has nothing to do with firmware-linux-nonfree. Ben. signature.asc Description: This is a digitally signed message part ---End Message---
Bug#794849: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#794849: linux: custom linux-image packages fail to install)
Thanks Ben for the advice and sorry for the latency. The steps you're suggesting are indeed more straightforward. However, the generated .deb packages still fail to install properly. I repeated the procedure on several fresh Debian 8.1 installations, using default settings in the installer, with the same outcome. After some digging, I realized that the root failure seems to first occur inside the running kernel (!!), during the dpkg installation. Below is the relevant dmesg output during dpkg -i: [ 708.498832] device-mapper: uevent: version 1.0.3 [ 708.498991] device-mapper: ioctl: 4.27.0-ioctl (2013-10-30) initialised: dm-de...@redhat.com [ 709.089486] SGI XFS with ACLs, security attributes, realtime, large block/inode numbers, no debug enabled [ 709.095776] JFS: nTxBlock = 8192, nTxLock = 65536 [ 709.108028] ntfs: driver 2.1.30 [Flags: R/W MODULE]. [ 709.119640] QNX4 filesystem 0.2.3 registered. [ 709.190614] raid6: mmxx1 4992 MB/s [ 709.258663] raid6: mmxx2 5880 MB/s [ 709.326691] raid6: sse1x14514 MB/s [ 709.394717] raid6: sse1x25192 MB/s [ 709.462765] raid6: sse2x19530 MB/s [ 709.530787] raid6: sse2x2 11756 MB/s [ 709.530790] raid6: using algorithm sse2x2 (11756 MB/s) [ 709.530791] raid6: using ssse3x1 recovery algorithm [ 709.532132] xor: automatically using best checksumming function: [ 709.570816]avx : 20117.000 MB/sec [ 709.583698] Btrfs loaded [ 709.587963] fuse init (API version 7.23) [ 709.633347] EXT4-fs (sda2): unable to read superblock [ 709.634932] EXT4-fs (sda2): unable to read superblock [ 709.636302] EXT4-fs (sda2): unable to read superblock [ 709.638439] XFS (sda2): Invalid superblock magic number [ 709.641380] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 709.641576] FAT-fs (sda2): bogus number of reserved sectors [ 709.641643] FAT-fs (sda2): Can't find a valid FAT filesystem [ 709.642860] FAT-fs (sda2): utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 709.643015] FAT-fs (sda2): bogus number of reserved sectors [ 709.643080] FAT-fs (sda2): Can't find a valid FAT filesystem [ 709.648183] ntfs: (device sda2): read_ntfs_boot_sector(): Primary boot sector is invalid. [ 709.648322] ntfs: (device sda2): read_ntfs_boot_sector(): Mount option errors=recover not used. Aborting without trying to recover. [ 709.648423] ntfs: (device sda2): ntfs_fill_super(): Not an NTFS volume. [ 709.650203] MINIX-fs: unable to read superblock [ 709.651596] attempt to access beyond end of device [ 709.651598] sda2: rw=16, want=3, limit=2 [ 709.651600] hfsplus: unable to find HFS+ superblock [ 709.653236] qnx4: no qnx4 filesystem (no root dir). [ 709.654695] You didn't specify the type of your ufs filesystem mount -t ufs -o ufstype=sun|sunx86|44bsd|ufs2|5xbsd|old|hp|nextstep|nextstep-cd|openstep ... WARNING Wrong ufstype may corrupt your filesystem, default is ufstype=old [ 709.657400] hfs: can't find a HFS filesystem on dev sda2 The EXT4-fs, FAT-fs, and ntfs errors seems suspicious, since the hardware doesn't seem faulty. Moreover, I ran this inside different virtual machines, all failing in the same way. Let me know if you'd need any extra information. Stefan On Fri, Aug 7, 2015 at 7:24 PM, Debian Bug Tracking System ow...@bugs.debian.org wrote: This is an automatic notification regarding your Bug report which was filed against the src:linux package: #794849: linux: custom linux-image packages fail to install It has been closed by Ben Hutchings b...@decadent.org.uk. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Ben Hutchings b...@decadent.org.uk by replying to this email. -- 794849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794849 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- Forwarded message -- From: Ben Hutchings b...@decadent.org.uk To: 794849-d...@bugs.debian.org Cc: Date: Fri, 07 Aug 2015 18:21:09 +0100 Subject: Re: Bug#794849: linux: custom linux-image packages fail to install On Fri, 2015-08-07 at 12:30 +0200, Stefan Bucur wrote: Source: linux Severity: serious Justification: fails to build from source (but built successfully in the past) Dear Maintainer, * What led up to the situation? I was trying to create a custom kernel package by following the steps at https://kernel-handbook.alioth.debian.org/ch-common-tasks.html. I changed the ABI version from 4 to 4-s2e. I customized the kernel configuration using make localmodconfig. Then, I built the dpkg packages for the 586 subarchitecture (both linux-image and linux -headers). [...] It sounds like you've done things in the wrong order or the wrong directory, because this package can be and is being built from
Bug#795336: linux-image-4.0.0-2-amd64: kernel causes mounted usb drives to timeout transfers
Package: src:linux Version: 4.0.8-2 Severity: grave Tags: lfs Justification: renders package unusable It thought this was an encfs problem until I looked at the drive post umount. The access light was still flashing and post-disconnect I get a drive cannot be accessed error. Not only do drive transfers stall out to almost non-existance, they refuse to umount as well.This results in a hung drive with zombie i/o still occuring.Noticed this on wonky USB flash drive access some times using my front usb ports and a hub.Its neither a hub nor flash drive fault.Both connections use dual USB to power the connection. I tired a usb 3 hub but that seemed to have two-way un-dioded power passthru and weird access when connected without a power cord.Hard to tell if this was a usb issue or hub issue so I cant use that hub. --- Via usb I have around 35MB/sec or so transfers, nearly more than double this on SATA internal connection. Yet when writing encfs to disk I am getting slowed down to less than 1MB/sec and the disk is thrashing constantly. There is nothing wrong with the hardware. Encryption should be done in RAM before disk write, and buffered thru buffer or similar if encrypting files can cause slowdowns.This is not the case. The app may work for small or tiny size copy but anything larger than 2GB or so causes this issue. I was trying to encrypt a backup set when this occured. Let sit for a few hours and the transfers slow to a crawl yet the disk is thrashing writes, as evident on the USB connection activity light.The only other viable solution uses ROOT access, a major no-no. I am limited on useable sata ports due to the way the power cables are wired and the case is layed out, hence the USB hookup. -- Package-specific info: ** Version: Linux version 4.0.0-2-amd64 (debian-kernel@lists.debian.org) (gcc version 4.9.3 (Debian 4.9.3-2) ) #1 SMP Debian 4.0.8-2 (2015-07-22) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.0.0-2-amd64 root=UUID=e26b0d1e-661c-4ee3-8e0b-e1bf691fe8df ro quiet ** Tainted: PWO (4609) * Proprietary module has been loaded. * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [88823.200662] [81097570] ? wake_up_state+0x20/0x20 [88823.200681] [811ea570] ? writeback_inodes_sb_nr+0x80/0xb0 [88823.200683] [811f17dd] ? sync_filesystem+0x2d/0xa0 [88823.200685] [811c2dfb] ? generic_shutdown_super+0x2b/0xf0 [88823.200687] [811c31b5] ? kill_block_super+0x25/0x70 [88823.200691] [811c34c5] ? deactivate_locked_super+0x45/0x80 [88823.200693] [811e0bab] ? cleanup_mnt+0x3b/0x90 [88823.200695] [81089234] ? task_work_run+0xd4/0xf0 [88823.200698] [81013ef9] ? do_notify_resume+0x69/0x90 [88823.200700] [815690eb] ? int_signal+0x12/0x17 [88923.979522] usb 10-4: USB disconnect, device number 2 [88923.987513] sd 11:0:0:0: [sdb] FAILED Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK [88923.987518] sd 11:0:0:0: [sdb] CDB: Write(10) 2a 00 32 ec 97 00 00 00 f0 00 [88923.987520] blk_update_request: I/O error, dev sdb, sector 854365952 [88923.987524] EXT4-fs warning (device sdb2): ext4_end_bio:317: I/O error -5 writing to inode 27790621 (offset 411041792 size 8388608 starting block 106795774) [88923.987527] Buffer I/O error on device sdb2, logical block 106664416 [88923.987530] Buffer I/O error on device sdb2, logical block 106664417 [88923.987532] Buffer I/O error on device sdb2, logical block 106664418 [88923.987534] Buffer I/O error on device sdb2, logical block 106664419 [88923.987535] Buffer I/O error on device sdb2, logical block 106664420 [88923.987537] Buffer I/O error on device sdb2, logical block 106664421 [88923.987538] Buffer I/O error on device sdb2, logical block 106664422 [88923.987540] Buffer I/O error on device sdb2, logical block 106664423 [88923.987542] Buffer I/O error on device sdb2, logical block 106664424 [88923.987543] Buffer I/O error on device sdb2, logical block 106664425 [88923.987568] EXT4-fs warning (device sdb2): ext4_end_bio:317: I/O error -5 writing to inode 27790621 (offset 411041792 size 8388608 starting block 106795834) [88923.987584] EXT4-fs warning (device sdb2): ext4_end_bio:317: I/O error -5 writing to inode 27790621 (offset 411041792 size 8388608 starting block 106795864) [88923.987599] EXT4-fs warning (device sdb2): ext4_end_bio:317: I/O error -5 writing to inode 27790621 (offset 411041792 size 8388608 starting block 106795894) [88923.987613] EXT4-fs warning (device sdb2): ext4_end_bio:317: I/O error -5 writing to inode 27790621 (offset 411041792 size 8388608 starting block 106795924) [88923.987628] EXT4-fs warning (device sdb2): ext4_end_bio:317: I/O error -5 writing to inode 27790621 (offset 411041792 size 8388608 starting block 106795954) [88923.987643] EXT4-fs warning (device sdb2): ext4_end_bio:317: I/O error -5 writing to inode 27790621 (offset 411041792 size 8388608 starting block 106795984) [88923.987657] EXT4-fs warning (device sdb2):
Bug#786925: linux: overlay filesystem incompatible with NFS
On 2015-08-11, Vagrant Cascadian vagr...@debian.org wrote:
Control: found 4.1.3-1
On 2015-05-26, Vagrant Cascadian wrote:
LTSP has been using aufs to provide a writeable tmpfs layer on top of
NFS since wheezy.
With the switch to the overlay filesystem (after adjusting LTSP's
initramfs-tools hooks to support overlay), it appears to fail due to an
incompatibility with NFS.
I haven't confirmed, but this may be fixed in mainline, not sure how
difficult it would be to backport to 4.1.x:
The attached 3 patches from mainline (one of them refreshed to apply to
4.1.3) allow it to mount with NFS as a lowerdir, and it mostly works,
although with some odd behavior when writing to files:
# echo ltsp95 /etc/hostname
bash: /etc/hostname: Permission denied
# touch /etc/hostname
# echo ltsp95 /etc/hostname
# cat /etc/hostname
ltsp95
Something seems a bit odd with the copyup behavior...
live well,
vagrant
From a6f15d9a756571babbb2b2cd4fdd1b64a5de232b Mon Sep 17 00:00:00 2001
From: Miklos Szeredi mszer...@suse.cz
Date: Mon, 22 Jun 2015 13:53:48 +0200
Subject: [PATCH 1/2] ovl: don't traverse automount points
NFS and other distributed filesystems may place automount points in the
tree. Previoulsy overlayfs refused to mount such filesystems types (based
on the existence of the .d_automount callback), even if the actual export
didn't have any automount points.
It cannot be determined in advance whether the filesystem has automount
points or not. The solution is to allow fs with .d_automount but refuse to
traverse any automount points encountered.
Signed-off-by: Miklos Szeredi mszer...@suse.cz
---
fs/overlayfs/super.c | 8 ++--
1 file changed, 6 insertions(+), 2 deletions(-)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index bf8537c..de9d2ee 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -303,6 +303,10 @@ static inline struct dentry *ovl_lookup_real(struct dentry *dir,
} else if (!dentry-d_inode) {
dput(dentry);
dentry = NULL;
+ } else if (dentry-d_flags DCACHE_MANAGED_DENTRY) {
+ dput(dentry);
+ /* Don't support traversing automounts */
+ dentry = ERR_PTR(-EREMOTE);
}
return dentry;
}
@@ -700,12 +704,12 @@ static bool ovl_is_allowed_fs_type(struct dentry *root)
/*
* We don't support:
- * - automount filesystems
+ * - autofs
* - filesystems with revalidate (FIXME for lower layer)
* - filesystems with case insensitive names
*/
if (dop
- (dop-d_manage || dop-d_automount ||
+ (dop-d_manage ||
dop-d_revalidate || dop-d_weak_revalidate ||
dop-d_compare || dop-d_hash)) {
return false;
--
2.1.4
From 7c03b5d45b8eebf025053d8fe887cc262ba6 Mon Sep 17 00:00:00 2001
From: Miklos Szeredi mszer...@suse.cz
Date: Mon, 22 Jun 2015 13:53:48 +0200
Subject: [PATCH 2/2] ovl: allow distributed fs as lower layer
Allow filesystems with .d_revalidate as lower layer(s), but not as upper
layer.
For local filesystems the rule was that modifications on the layers
directly while being part of the overlay results in undefined behavior.
This can easily be extended to distributed filesystems: we assume the tree
used as lower layer is static, which means -d_revalidate() should always
return 1. If that is not the case, return -ESTALE, don't try to work
around the modification.
Signed-off-by: Miklos Szeredi mszer...@suse.cz
---
fs/overlayfs/super.c | 113 +++
1 file changed, 88 insertions(+), 25 deletions(-)
diff --git a/fs/overlayfs/super.c b/fs/overlayfs/super.c
index de9d2ee..8a08c58 100644
--- a/fs/overlayfs/super.c
+++ b/fs/overlayfs/super.c
@@ -273,10 +273,57 @@ static void ovl_dentry_release(struct dentry *dentry)
}
}
+static int ovl_dentry_revalidate(struct dentry *dentry, unsigned int flags)
+{
+ struct ovl_entry *oe = dentry-d_fsdata;
+ unsigned int i;
+ int ret = 1;
+
+ for (i = 0; i oe-numlower; i++) {
+ struct dentry *d = oe-lowerstack[i].dentry;
+
+ if (d-d_flags DCACHE_OP_REVALIDATE) {
+ ret = d-d_op-d_revalidate(d, flags);
+ if (ret 0)
+return ret;
+ if (!ret) {
+if (!(flags LOOKUP_RCU))
+ d_invalidate(d);
+return -ESTALE;
+ }
+ }
+ }
+ return 1;
+}
+
+static int ovl_dentry_weak_revalidate(struct dentry *dentry, unsigned int flags)
+{
+ struct ovl_entry *oe = dentry-d_fsdata;
+ unsigned int i;
+ int ret = 1;
+
+ for (i = 0; i oe-numlower; i++) {
+ struct dentry *d = oe-lowerstack[i].dentry;
+
+ if (d-d_flags DCACHE_OP_WEAK_REVALIDATE) {
+ ret = d-d_op-d_weak_revalidate(d, flags);
+ if (ret = 0)
+break;
+ }
+ }
+ return ret;
+}
+
static const struct dentry_operations ovl_dentry_operations = {
.d_release = ovl_dentry_release,
};
+static const struct dentry_operations ovl_reval_dentry_operations = {
+ .d_release = ovl_dentry_release,
+ .d_revalidate = ovl_dentry_revalidate,
+ .d_weak_revalidate = ovl_dentry_weak_revalidate,
+};
+
static struct ovl_entry *ovl_alloc_entry(unsigned int numlower)
{
Processed: severity of 793326 is grave
Processing commands for cont...@bugs.debian.org: severity 793326 grave Bug #793326 [linux] linux: raid0 data corruption when using trim Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 793326: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793326 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: found 793612 in 3.16.7-ckt9-3, fixed 793612 in 4.0.5-1
Processing commands for cont...@bugs.debian.org: found 793612 3.16.7-ckt9-3 Bug #793612 [src:linux] linux-image-3.16.0-4-amd64: Queued TRIM problem on other Samsung SSDs Bug #790520 [src:linux] linux: Samsung NCQ TRIM problem Marked as found in versions linux/3.16.7-ckt9-3. Marked as found in versions linux/3.16.7-ckt9-3. fixed 793612 4.0.5-1 Bug #793612 [src:linux] linux-image-3.16.0-4-amd64: Queued TRIM problem on other Samsung SSDs Bug #790520 [src:linux] linux: Samsung NCQ TRIM problem Marked as fixed in versions linux/4.0.5-1. Marked as fixed in versions linux/4.0.5-1. thanks Stopping processing here. Please contact me if you need assistance. -- 790520: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=790520 793612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Uploading linux (4.1.5-1)
I intend to upload linux version 4.1.5-1 to unstable in the next day or two. This includes an ABI bump due to upstream changes. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Bug#468114: Loopback file system support.
On 2015-08-11, Vagrant Cascadian wrote:
On 2015-08-11, Vagrant Cascadian wrote:
I've taken a quick stab as refreshing this, though I haven't yet tested
it. I did move mounting of the loopback to mount_loop_root in functions,
as I would like to eventually support loopback mounted files from NFS.
Made some small changes, updated and *tested* this time! Patch below...
And added NFS support! Full patch below...
live well,
vagrant
diff --git a/init b/init
index abf7f25..2760bcb 100755
--- a/init
+++ b/init
@@ -98,6 +98,15 @@ for x in $(cat /proc/cmdline); do
;;
esac
;;
+ loop=*)
+ LOOP=${x#loop=}
+ ;;
+ loopflags=*)
+ LOOPFLAGS=-o ${x#loopflags=}
+ ;;
+ loopfstype=*)
+ LOOPFSTYPE=${x#loopfstype=}
+ ;;
nfsroot=*)
NFSROOT=${x#nfsroot=}
;;
diff --git a/initramfs-tools.8 b/initramfs-tools.8
index ea8c098..ce8e830 100644
--- a/initramfs-tools.8
+++ b/initramfs-tools.8
@@ -42,6 +42,19 @@ The default is 180 seconds.
set the file system mount option string.
.TP
+\fB\fI loop
+path within the original root file system to loop-mount and use as the
+real root file system.
+
+.TP
+\fB\fI loopflags
+set the loop file system mount option string, if applicable.
+
+.TP
+\fB\fI loopfstype
+set the loop file system type, if applicable.
+
+.TP
\fB\fI nfsroot
can be either auto to try to get the relevant information from DHCP or a
string of the form NFSSERVER:NFSPATH or NFSSERVER:NFSPATH:NFSOPTS.
diff --git a/scripts/functions b/scripts/functions
index 8c1bb1f..2ed3ce3 100644
--- a/scripts/functions
+++ b/scripts/functions
@@ -426,6 +426,42 @@ mountfs()
${type}_mount_fs $1
}
+# Mount a loopback device, which is present on the mounted filesystem.
+mount_loop_root()
+{
+ mkdir -p /host
+ mount -o move ${rootmnt} /host
+ loopfile=/host/${LOOP#/}
+
+ while [ ! -e $loopfile ]; do
+ panic ALERT! $loopfile does not exist. Dropping to a shell!
+ done
+
+ if [ ${readonly} = y ]; then
+ roflag=-r
+ else
+ roflag=-w
+ fi
+
+ # Get the loop filesystem type if not set
+ if [ -z ${LOOPFSTYPE} ]; then
+ FSTYPE=$(get_fstype $loopfile)
+ else
+ FSTYPE=${LOOPFSTYPE}
+ fi
+
+ # FIXME This has no error checking
+ modprobe loop
+ modprobe ${FSTYPE}
+
+ # FIXME This has no error checking
+ mount ${roflag} -o loop -t ${FSTYPE} ${LOOPFLAGS} $loopfile ${rootmnt}
+
+ if [ -d ${rootmnt}/host ]; then
+ mount -o move /host ${rootmnt}/host
+ fi
+}
+
# Mount the root file system. It should be overridden by all
# boot scripts.
mountroot()
diff --git a/scripts/local b/scripts/local
index f6424f0..072013e 100644
--- a/scripts/local
+++ b/scripts/local
@@ -135,7 +135,8 @@ local_mount_root()
ROOT=$(resolve_device $ROOT)
- if [ ${readonly} = y ]; then
+ if [ ${readonly} = y ] \
+ ([ -z $LOOP ] || [ ${FSTYPE#ntfs} = $FSTYPE ]); then
roflag=-r
else
roflag=-w
@@ -153,6 +154,10 @@ local_mount_root()
else
mount ${roflag} ${ROOTFLAGS} ${ROOT} ${rootmnt}
fi
+
+ if [ ${LOOP} ]; then
+ mount_loop_root
+ fi
}
local_mount_fs()
diff --git a/scripts/nfs b/scripts/nfs
index 1c29850..d382413 100644
--- a/scripts/nfs
+++ b/scripts/nfs
@@ -72,6 +72,10 @@ nfs_mount_root_impl()
fi
nfsmount -o nolock ${roflag} ${NFSOPTS} ${NFSROOT} ${rootmnt}
+
+ if [ ${LOOP} ]; then
+ mount_loop_root
+ fi
}
# NFS root mounting
signature.asc
Description: PGP signature
Bug#761469: marked as done (xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb)
Your message dated Wed, 12 Aug 2015 15:17:08 +0200 with message-id 1439385428.10857.70.ca...@decadent.org.uk and subject line Re: xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb has caused the Debian Bug report #761469, regarding xen-linux-system-3.2.0-4-amd64: xen kernel appears misconfigured for uvesafb 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.) -- 761469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=761469 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: xen-linux-system-3.2.0-4-amd64 Version: 3.2.60-1+deb7u3 Severity: important Dear Maintainer, Original symptom: under x11 switching tty's causes blank screen and monitor going to sleep. Researching indicated this could be related to having a Nvidia graphics card as well as a missing or misconfigured uvesafb module. [1] Checking dmesg showed the following error: [4.796570] uvesafb: Getting VBE info block failed (eax=0x4f00, err=0) [4.796635] uvesafb: vbe_init() failed with -22 [4.796688] uvesafb: probe of uvesafb.0 failed with error -22 Also /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes did not exist. When booting with the standard Debian linux kernel instead of xen tty switching under x11 worked as expected. There were no errors in demsg output: [3.275811] uvesafb: NVIDIA Corporation, GF110 Board - 12610002, Chip Rev , OEM: NVIDIA, VBE v3.0 [3.385649] uvesafb: VBIOS/hardware doesn't support DDC transfers [3.385651] uvesafb: no monitor limits have been set, default refresh rate will be used [3.386354] uvesafb: scrolling: redraw [3.563068] uvesafb: framebuffer at 0xf100, mapped to 0xc9000668, using 14336k, total 14336k Also /sys/bus/platform/drivers/uvesafb/uvesafb.0/vbe_modes existed with expected content. This seems to indicate the Debian xen kernel has not been correctly configured for use with the uvesafb module. [1] https://bbs.archlinux.org/viewtopic.php?id=120326 -- System Information: Debian Release: 7.6 APT prefers stable APT policy: (990, 'stable'), (500, 'stable-updates') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/8 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xen-linux-system-3.2.0-4-amd64 depends on: ii linux-image-3.2.0-4-amd64 3.2.60-1+deb7u3 ii xen-system-amd64 4.1.4-3+deb7u2 xen-linux-system-3.2.0-4-amd64 recommends no packages. xen-linux-system-3.2.0-4-amd64 suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- This is not a configuration issue. uvesafb requires making BIOS calls, but Xen PV domains do not have access to the BIOS. 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---
Processed: fixed 794680 in 4.1.3-1
Processing commands for cont...@bugs.debian.org: fixed 794680 4.1.3-1 Bug #794680 [linux] drbd kernel module incompatible with drbd-utils - kernel panics There is no source info for the package 'linux' at version '4.1.3-1' with architecture '' Unable to make a source version for version '4.1.3-1' Marked as fixed in versions 4.1.3-1. thanks Stopping processing here. Please contact me if you need assistance. -- 794680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=794680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795294: Remove debian-kernel-maint list
Package: lists.debian.org Severity: normal The debian-kernel-maint list has received nothing but spam and unanswered user questions since February 2007, shortly after its creation. In fact I wasn't aware of its existence until just now when I scrolled down the list of lists fror developers. Please remove it now. Ben. -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Foreign Architectures: amd64 Kernel: Linux 4.1.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#795303: missing broadcom firmware
package: firmware-brcm80211 Hi, Using unstable kernel 4.1.0-1-686-pae, I miss the broadcom firmware for 43331, I had to download it as explained in https://wiki.debian.org/InstallingDebianOn/Asus/X205TA Cheers, Christophe
[PATCH kernel-team] Update kernel maintainers based on the last two years' activity
dann frazier explicitly requested removal from the security support list in 20140926200235.GA18789@fluid.dannf. The other changes are based on (in)activity as represented in the changelog and commit log. --- I hope these deletions don't offend anyone. I'm happy to keep anyone on this list who says they're still active. Ben. MAINTAINERS.Debian | 13 ++--- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/MAINTAINERS.Debian b/MAINTAINERS.Debian index 8a03077..0f01d6a 100644 --- a/MAINTAINERS.Debian +++ b/MAINTAINERS.Debian @@ -4,28 +4,27 @@ kernel-related packages: General kernel work: - Maximilian Attems - Bastian Blank - - Dann Frazier - Ben Hutchings - - Moritz Muehlenhoff Security support: - - Dann Frazier + - Salvatore Bonaccorso + - Ben Hutchings - Moritz Muehlenhoff Kernel packages, sorted by source architecture: * alpha -- (Michael Cree) +- (Helge Deller) * arm -- Arnaud Patard, Hector Oron, Ian Campbell +- Ian Campbell * arm64 - Ian Campbell * ia64 - no maintainer * m68k -- (Thorsten Glaser), Christian T. Steigies +- (Thorsten Glaser) * mips -- Aurelien Jarno, (Andi Barth) +- Aurelien Jarno * or1k - no maintainer * parisc -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Bug#795305: missing support in jessie for broadcom 43341
package: src:linux Hi, please include firmware for Broadcom 43341. (I manually downloaded it as explained in https://wiki.debian.org/InstallingDebianOn/Asus/X205TA) Cheers, Christophe
Processed: Re: Bug#795305: missing support in jessie for broadcom 43341
Processing control commands: found -1 3.16.7-ckt11-1+deb8u3 Bug #795305 [src:linux] missing support in jessie for broadcom 43341 Marked as found in versions linux/3.16.7-ckt11-1+deb8u3. severity -1 important Bug #795305 [src:linux] missing support in jessie for broadcom 43341 Severity set to 'important' from 'normal' -- 795305: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795305 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#795305: missing support in jessie for broadcom 43341
Control: found -1 3.16.7-ckt11-1+deb8u3 Control: severity -1 important On Wed, 2015-08-12 at 21:18 +0200, Christophe Siraut wrote: package: src:linux Hi, please include firmware for Broadcom 43341. (I manually downloaded it as explained in https://wiki.debian.org/InstallingDebianOn/Asus/X205TA) For the kernel part we need to update the brcmfmac driver. Ben. -- Ben Hutchings Teamwork is essential - it allows you to blame someone else. signature.asc Description: This is a digitally signed message part
Processed: Re: Bug#795303: missing broadcom firmware
Processing commands for cont...@bugs.debian.org: found 795303 0.44 Bug #795303 [firmware-brcm80211] missing broadcom firmware Marked as found in versions firmware-nonfree/0.44. severity 795303 important Bug #795303 [firmware-brcm80211] missing broadcom firmware Severity set to 'important' from 'normal' retitle 795303 firmware-brcm80211: Missing firmware brcmfmac43340-sdio.bin Bug #795303 [firmware-brcm80211] missing broadcom firmware Changed Bug title to 'firmware-brcm80211: Missing firmware brcmfmac43340-sdio.bin' from 'missing broadcom firmware' End of message, stopping processing here. Please contact me if you need assistance. -- 795303: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=795303 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
