Re: Linux 3.12 transition to testing
Ben Hutchings b...@decadent.org.uk (2014-01-03): linux 3.12.6-2 and linux-tools 3.12.6-1 should be ready for transition to testing tomorrow, except that they also need to go with linux-latest 55 which was uploaded with urgency=low. Please add a hint for linux-latest so that this isn't delayed unnecessarily. kibi@franck:~$ head -3 hints/kibi # 2014-01-03 # RoM: https://lists.debian.org/debian-release/2014/01/msg00022.html age-days 5 linux-latest/55 Thanks. Mraw, KiBi. signature.asc Description: Digital signature
Processed: Re: Bug#733537: base: GNOME/GDM Fails to Run
Processing commands for cont...@bugs.debian.org: reassign 733537 src:gnome Bug #733537 [base] base: GNOME/GDM Fails to Run Bug reassigned from package 'base' to 'src:gnome'. Warning: Unknown package 'src:gnome' Warning: Unknown package 'src:gnome' Ignoring request to alter found versions of bug #733537 to the same values previously set Warning: Unknown package 'src:gnome' Warning: Unknown package 'src:gnome' Ignoring request to alter fixed versions of bug #733537 to the same values previously set Warning: Unknown package 'src:gnome' retitle 733651 GNOME/GDM fails to run on ibook G4 Bug #733651 [src:linux] general: Any USB card reader works only after being replugged. Changed Bug title to 'GNOME/GDM fails to run on ibook G4' from 'general: Any USB card reader works only after being replugged.' thanks Stopping processing here. Please contact me if you need assistance. -- 733537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733537 733651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733651 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: http://lists.debian.org/handler.s.c.138874613316896.transcr...@bugs.debian.org
Processed: Re: Bug#733537: base: GNOME/GDM Fails to Run
Processing commands for cont...@bugs.debian.org: reassign 733537 gnome Bug #733537 [src:gnome] base: GNOME/GDM Fails to Run Warning: Unknown package 'src:gnome' Bug reassigned from package 'src:gnome' to 'gnome'. Ignoring request to alter found versions of bug #733537 to the same values previously set Ignoring request to alter fixed versions of bug #733537 to the same values previously set retitle 733651 GNOME/GDM fails to run on ibook G4 Bug #733651 [src:linux] GNOME/GDM fails to run on ibook G4 Ignoring request to change the title of bug#733651 to the same title thanks Stopping processing here. Please contact me if you need assistance. -- 733537: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733537 733651: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733651 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: http://lists.debian.org/handler.s.c.138874683021828.transcr...@bugs.debian.org
Re: Linux 3.12 transition to testing
On Fri, 2014-01-03 at 11:19 +0100, Cyril Brulebois wrote: Ben Hutchings b...@decadent.org.uk (2014-01-03): linux 3.12.6-2 and linux-tools 3.12.6-1 should be ready for transition to testing tomorrow, except that they also need to go with linux-latest 55 which was uploaded with urgency=low. Please add a hint for linux-latest so that this isn't delayed unnecessarily. kibi@franck:~$ head -3 hints/kibi # 2014-01-03 # RoM: https://lists.debian.org/debian-release/2014/01/msg00022.html age-days 5 linux-latest/55 Thanks. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#723180: [PATCH] Revert x86: Disable IST stacks for debug/int 3/stack fault for PREEMPT_RT
where do I start. Let me explain what is going on here. The code
sequence
| pushf
| pop%edx
| or $0x1,%dh
| push %edx
| mov$0xe0,%eax
| popf
| sysenter
triggers the bug. On 64bit kernel we see the double fault (with 32bit and
64bit userland) and on 32bit kernel there is no problem. The reporter said
that double fault does not happen on 64bit kernel with 64bit userland and
this is because in that case the VDSO uses the syscall interface instead
of sysenter.
The bug. popf loads the flags with the TF bit set which enables
single stepping and this leads to a debug exception. Usually on 64bit
we have a special IST stack for the debug exception. Due to patch [0] we
do not use the IST stack but the kernel stack instead. On 64bit the
sysenter instruction starts in kernel with the stack address NULL. The
code sequence above enters the debug exception (TF flag) after the
sysenter instruction was executed which sets the stack pointer to NULL
and we have a fault (it seems that the debug exception saves some bytes
on the stack).
To fix the double fault I'm going to drop patch [0]. It is completely
pointless. In do_debug() and do_stack_segment() we disable preemption
which means the task can't leave the CPU. So it does not matter if we run
on IST or on kernel stack.
There is a patch [1] which drops preempt_disable() call for a 32bit
kernel but not for 64bit so there should be no regression.
And [1] seems valid even for this code sequence. We enter the debug
exception with a 256bytes long per cpu stack and migrate to the kernel
stack before calling do_debug().
[0] x86-disable-debug-stack.patch
[1] fix-rt-int3-x86_32-3.2-rt.patch
Reported-by: Brian Silverman bsilver16...@gmail.com
Cc: Andi Kleen a...@firstfloor.org
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
arch/x86/include/asm/page_64_types.h | 21 ++---
arch/x86/kernel/cpu/common.c | 2 --
arch/x86/kernel/dumpstack_64.c | 4
3 files changed, 6 insertions(+), 21 deletions(-)
diff --git a/arch/x86/include/asm/page_64_types.h
b/arch/x86/include/asm/page_64_types.h
index 695e04d..43dcd80 100644
--- a/arch/x86/include/asm/page_64_types.h
+++ b/arch/x86/include/asm/page_64_types.h
@@ -14,21 +14,12 @@
#define IRQ_STACK_ORDER 2
#define IRQ_STACK_SIZE (PAGE_SIZE IRQ_STACK_ORDER)
-#ifdef CONFIG_PREEMPT_RT_FULL
-# define STACKFAULT_STACK 0
-# define DOUBLEFAULT_STACK 1
-# define NMI_STACK 2
-# define DEBUG_STACK 0
-# define MCE_STACK 3
-# define N_EXCEPTION_STACKS 3 /* hw limit: 7 */
-#else
-# define STACKFAULT_STACK 1
-# define DOUBLEFAULT_STACK 2
-# define NMI_STACK 3
-# define DEBUG_STACK 4
-# define MCE_STACK 5
-# define N_EXCEPTION_STACKS 5 /* hw limit: 7 */
-#endif
+#define STACKFAULT_STACK 1
+#define DOUBLEFAULT_STACK 2
+#define NMI_STACK 3
+#define DEBUG_STACK 4
+#define MCE_STACK 5
+#define N_EXCEPTION_STACKS 5 /* hw limit: 7 */
#define PUD_PAGE_SIZE (_AC(1, UL) PUD_SHIFT)
#define PUD_PAGE_MASK (~(PUD_PAGE_SIZE-1))
diff --git a/arch/x86/kernel/cpu/common.c b/arch/x86/kernel/cpu/common.c
index c0dcf06..2793d1f 100644
--- a/arch/x86/kernel/cpu/common.c
+++ b/arch/x86/kernel/cpu/common.c
@@ -1105,9 +1105,7 @@ DEFINE_PER_CPU(struct task_struct *, fpu_owner_task);
*/
static const unsigned int exception_stack_sizes[N_EXCEPTION_STACKS] = {
[0 ... N_EXCEPTION_STACKS - 1]= EXCEPTION_STKSZ,
-#if DEBUG_STACK 0
[DEBUG_STACK - 1] = DEBUG_STKSZ
-#endif
};
static DEFINE_PER_CPU_PAGE_ALIGNED(char, exception_stacks
diff --git a/arch/x86/kernel/dumpstack_64.c b/arch/x86/kernel/dumpstack_64.c
index 52b4bcd..addb207 100644
--- a/arch/x86/kernel/dumpstack_64.c
+++ b/arch/x86/kernel/dumpstack_64.c
@@ -21,14 +21,10 @@
(N_EXCEPTION_STACKS + DEBUG_STKSZ/EXCEPTION_STKSZ - 2)
static char x86_stack_ids[][8] = {
-#if DEBUG_STACK 0
[ DEBUG_STACK-1 ] = #DB,
-#endif
[ NMI_STACK-1 ] = NMI,
[ DOUBLEFAULT_STACK-1 ] = #DF,
-#if STACKFAULT_STACK 0
[ STACKFAULT_STACK-1] = #SS,
-#endif
[ MCE_STACK-1 ] = #MC,
#if DEBUG_STKSZ EXCEPTION_STKSZ
[ N_EXCEPTION_STACKS ...
--
1.8.5.2
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20140103135548.ga6...@linutronix.de
Bug#710120: you can close this bug
Hello, You can close this bug. This is a laptop-mode-tools problem. Thank you. -- Pierre Crescenzo mailto:pie...@crescenzo.nom.fr http://www.crescenzo.nom.fr/ -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87a9fd85om@tpol.unice.fr
Re: [PATCH 2/2] deb-pkg: Fix building for MIPS big-endian or ARM OABI
On 2013-12-05 15:39, Ben Hutchings wrote:
These commands will mysteriously fail:
$ make ARCH=arm versatile_defconfig
[...]
$ make ARCH=arm deb-pkg
[...]
make[1]: *** [deb-pkg] Error 1
make: *** [deb-pkg] Error 2
The Debian architecture selection for these kernel architectures does
'grep FOO=y $KCONFIG_CONFIG echo bar', and after 'set -e' this
aborts the script if grep does not find the given config symbol.
Fixes: 10f26fa64200 ('build, deb-pkg: select userland architecture based on
UTS_MACHINE')
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
scripts/package/builddeb | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Applied to kbuild.git#misc, thanks.
Michal
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52c6e56f.8000...@suse.cz
Re: [PATCH 1/2] deb-pkg: Fix cross-building linux-headers package
On 2013-12-06 05:20, Niew, Sh. wrote:
On Thu, Dec 5, 2013 at 10:37 PM, Ben Hutchings b...@decadent.org.uk
wrote:
builddeb generates a control file that says the linux-headers package
can only be built for the build system primary architecture. This
breaks cross-building configurations. We should use $debarch for this
instead.
Since $debarch is not yet set when generating the control file, set
Architecture: any and use control file variables to fill in the
description.
Fixes: cd8d60a20a45 ('kbuild: create linux-headers package in deb-pkg')
Reported-by: Niew, Sh. shn...@gmail.com
Signed-off-by: Ben Hutchings b...@decadent.org.uk
[...]
Thanks, the attach patch is applied.
And i just make it on linux-3.2.y by hand, and is successfully cross-build.
Haven't test in 3.12
Thanks, applied to kbuild.git#misc.
Michal
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52c6e45a.2040...@suse.cz
Processed: Re: Bug#710120: you can close this bug
Processing control commands: reassign -1 laptop-mode-tools Bug #710120 [src:linux] xserver-xorg-input-mouse: USB mouse is intermittent Bug reassigned from package 'src:linux' to 'laptop-mode-tools'. No longer marked as found in versions linux/3.2.41-2+deb7u2. Ignoring request to alter fixed versions of bug #710120 to the same values previously set -- 710120: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710120 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: http://lists.debian.org/handler.s.b710120.138877091412956.transcr...@bugs.debian.org
Bug#710120: you can close this bug
Control: reassign -1 laptop-mode-tools On Fri, Jan 03, 2014 at 04:07:37PM +0100, Pierre Crescenzo wrote: Hello, You can close this bug. This is a laptop-mode-tools problem. Then it should be reassigned, not closed, so that's what I've done. Ben. -- Ben Hutchings Who are all these weirdos? - David Bowie, about L-Space IRC channel #afp -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140103174148.gf5...@decadent.org.uk
Bug#733565: SIX messages per on boot console should be TWO
MKP == Martin K Petersen martin.peter...@oracle.com writes: MKP We have to discover the basics of the disk before we can create the MKP gendisk/block device/request queue. And some of the subsequent MKP parameters we need can't be stored or acted upon until everything has MKP been set up. So some questions we have to ask several times. Perhaps the messages could be each differentiated so the user doesn't see them as something that looks like a bug and needs to be reported. E.g., prefix/suffix with PHASE I CHECK, PHASE II CHECK, PHASE III CHECK. or FIRST CHECK, INTERMEDIATE CHECK, FINAL CHECK, or CHECK 1, CHECK 2... or INTERMEDIATE PROBE:, FINAL PROBE:, etc. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87ha9kvjp8@jidanni.org
Bug#733826: crazy loop xhci_hcd Too many fragments
BH == Ben Hutchings b...@decadent.org.uk writes: BH And what were those error messages? BH Which USB devices are you using (this is probably disk or network BH related)? I had done an aptitude update on writing onto # fdisk -l Disk /dev/sdg: 3867 MB, 3867148288 bytes 181 heads, 32 sectors/track, 1304 cylinders, total 7553024 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 Disk identifier: 0xc3072e18 # mount Device Boot Start End Blocks Id System /dev/sdg1 32 868799 434384 83 Linux /dev/sdg2 868800 7553023 3342112 83 Linux /dev/sdg2 on /var/cache/apt/archives type ext3 (rw,noatime,errors=remount-ro,data=ordered) /dev/sdg1 on /var/lib/apt/lists type ext3 (rw,noatime,errors=remount-ro,data=ordered) # cat /var/log/syslog Jan 1 06:57:38 jidanni5 ntpd[2822]: Listen normally on 5 lo ::1 UDP 123 Jan 1 06:57:38 jidanni5 ntpd[2822]: Listen normally on 6 eth0 fe80::2289:84ff:fe28:ad9 UDP 123 Jan 1 06:57:38 jidanni5 ntpd[2822]: peers refreshed Jan 1 06:57:38 jidanni5 ntpd[2822]: Listening on routing socket on fd #23 for interface updates Jan 1 07:04:49 jidanni5 kernel: [ 559.624680] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624695] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:49 jidanni5 kernel: [ 559.624704] xhci_hcd :00:14.0: Too many fragments 79, max 63 10 lines later... oops I mean an actual MILLION lines later # grep -c xhci /var/log/syslog 1052831: Jan 1 07:04:58 jidanni5 kernel: [ 568.615382] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:58 jidanni5 kernel: [ 568.615391] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:58 jidanni5 kernel: [ 568.615400] xhci_hcd :00:14.0: Too many fragments 79, max 63 Jan 1 07:04:58 jidanni5 kernel: [ 568.615784] usb 1-4.3: USB disconnect, device number 5 Jan 1 07:04:58 jidanni5 kernel: [ 568.622573] sd 7:0:0:0: [sdg] Unhandled error code Jan 1 07:04:58 jidanni5 kernel: [ 568.622577] sd 7:0:0:0: [sdg] Jan 1 07:04:58 jidanni5 kernel: [ 568.622579] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Jan 1 07:04:58 jidanni5 kernel: [ 568.622581] sd 7:0:0:0: [sdg] CDB: Jan 1 07:04:58 jidanni5 kernel: [ 568.622583] Write(10): 2a 00 00 06 85 0e 00 00 da 00 Jan 1 07:04:58 jidanni5 kernel: [ 568.622591] end_request: I/O error, dev sdg, sector 427278 Jan 1 07:04:58 jidanni5 kernel: [ 568.622595] Buffer I/O error on device sdg1, logical block 213623 Jan 1 07:04:58 jidanni5 kernel: [ 568.622596] lost page write due to I/O error on sdg1 Jan 1 07:04:58 jidanni5 kernel: [ 568.622673] Aborting journal on device sdg1-8. Jan 1 07:04:58 jidanni5 kernel: [ 568.622702] JBD2: Error -5 detected when updating journal superblock for sdg1-8. Jan 1 07:04:58 jidanni5 kernel: [ 568.622782] journal commit I/O error Jan 1 07:04:58 jidanni5 kernel: [ 568.842558] usb 1-4.3: new full-speed USB device number 6 using xhci_hcd Jan 1 07:05:03 jidanni5 kernel: [ 573.840855] xhci_hcd :00:14.0: Timeout while waiting for address device command Jan 1 07:05:04 jidanni5 kernel: [ 574.813608] usb 1-4.3: not running at top speed; connect to a high speed hub Jan 1 07:05:04 jidanni5 kernel: [ 574.816058] usb 1-4.3: New USB device found, idVendor=090c, idProduct=1000 Jan 1 07:05:04 jidanni5 kernel: [ 574.816074] usb 1-4.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jan 1 07:05:04 jidanni5 kernel: [ 574.816080] usb 1-4.3: Product: USB DISK Jan 1 07:05:04 jidanni5 kernel: [ 574.816084] usb 1-4.3: Manufacturer: SMI Corporation Jan 1 07:05:04 jidanni5 kernel: [ 574.816088] usb 1-4.3: SerialNumber: AA330463000360008655 Jan 1 07:05:04 jidanni5 kernel: [ 574.816658] usb-storage 1-4.3:1.0: USB Mass Storage device detected Jan 1 07:05:04 jidanni5 kernel: [ 574.816713] scsi9 : usb-storage 1-4.3:1.0 Jan 1 07:05:05 jidanni5 kernel: [ 575.817473] scsi 9:0:0:0: Direct-Access SMI USB DISK 1100 PQ: 0 ANSI: 0 CCS Jan 1 07:05:05 jidanni5 kernel: [ 575.817921] sd 9:0:0:0: Attached scsi generic sg7 type 0 Jan 1 07:05:05 jidanni5 kernel: [ 575.819774] sd 9:0:0:0: [sdi] 7553024 512-byte logical blocks: (3.86 GB/3.60 GiB) Jan 1 07:05:05 jidanni5 kernel: [ 575.820658] sd 9:0:0:0: [sdi] Write Protect is off Jan 1 07:05:05 jidanni5 kernel: [ 575.820663] sd 9:0:0:0: [sdi] Mode Sense: 43 00 00 00 Jan 1 07:05:05 jidanni5 kernel: [ 575.821457] sd 9:0:0:0: [sdi] No Caching mode page found Jan 1 07:05:05 jidanni5 kernel: [ 575.821462] sd 9:0:0:0: [sdi] Assuming drive cache: write through Jan 1 07:05:05 jidanni5 kernel: [ 575.825400] sd 9:0:0:0: [sdi] No Caching mode page found Jan 1 07:05:05 jidanni5 kernel: [ 575.825405] sd 9:0:0:0: [sdi] Assuming drive cache: write through Jan 1 07:05:05 jidanni5 kernel: [
Bug#733565: SIX messages per on boot console should be TWO
Ben == Ben Hutchings b...@decadent.org.uk writes: Ben I can see that it is emitted by sd_read_cache_type(), which is Ben called by sd_revalidate_disk(), and that is apparently now called 3 Ben times during probe. Which is quite ridiculous. We have to discover the basics of the disk before we can create the gendisk/block device/request queue. And some of the subsequent parameters we need can't be stored or acted upon until everything has been set up. So some questions we have to ask several times. Ben And I wonder whether this situation (no caching mode page) is Ben really serious enough to deserve logging at ERR severity? I guess we could extend the first_scan logic to cover the error case scenarios. But it is quite unusual for a device to not implement the caching mode page... -- Martin K. Petersen Oracle Linux Engineering -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/yq1ob3szun7@sermon.lab.mkp.net
Bug#733826: crazy loop xhci_hcd Too many fragments
Crap. The same thing happened again today. Now it is up to # grep -c xhci /var/log/syslog 1958427 lines! 222] usb 1-4.3: USB disconnect, device number 5 Jan 4 05:28:05 jidanni5 kernel: [ 3904.883696] sd 7:0:0:0: [sdg] Unhandled error code Jan 4 05:28:05 jidanni5 kernel: [ 3904.883702] sd 7:0:0:0: [sdg] Jan 4 05:28:05 jidanni5 kernel: [ 3904.883703] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Jan 4 05:28:05 jidanni5 kernel: [ 3904.883705] sd 7:0:0:0: [sdg] CDB: Jan 4 05:28:05 jidanni5 kernel: [ 3904.883707] Write(10): 2a 00 00 06 84 e0 00 00 bc 00 Jan 4 05:28:05 jidanni5 kernel: [ 3904.883715] end_request: I/O error, dev sdg, sector 427232 Jan 4 05:28:05 jidanni5 kernel: [ 3904.883756] EXT4-fs warning (device sdg1): ext4_end_bio:316: I/O error writing to inode 49349 (offset 0 size 0 starting block 130529) jidanni5 kernel: [ 3904.884184] EXT4-fs warning (device sdg1): ext4_end_bio:316: I/O error writing to inode 49349 (offset 0 size 0 starting block 133885) Jan 4 05:28:05 jidanni5 kernel: [ 3904.885980] Aborting journal on device sdg1-8. Jan 4 05:28:05 jidanni5 kernel: [ 3904.886159] JBD2: Error -5 detected when updating journal superblock for sdg1-8. Jan 4 05:28:05 jidanni5 kernel: [ 3904.886294] journal commit I/O error Jan 4 05:28:05 jidanni5 kernel: [ 3904.893305] EXT4-fs error (device sdg1): ext4_journal_check_start:56: Detected aborted journal Jan 4 05:28:05 jidanni5 kernel: [ 3904.893312] EXT4-fs (sdg1): Remounting filesystem read-only Jan 4 05:28:05 jidanni5 kernel: [ 3904.893314] EXT4-fs (sdg1): previous I/O error to superblock detected Jan 4 05:28:05 jidanni5 kernel: [ 3905.111627] usb 1-4.3: new full-speed USB device number 6 using xhci_hcd Jan 4 05:28:06 jidanni5 kernel: [ 3905.440770] EXT4-fs warning (device sdg1): __ext4_read_dirblock:681: error reading directory block (ino 2, block 0) 06:16 ~# fsck -V -f -v /dev/sdi1 fsck from util-linux 2.20.1 [/sbin/fsck.ext3 (1) -- /var/lib/apt/lists] fsck.ext3 -f -v /dev/sdi1 e2fsck 1.42.9 (28-Dec-2013) /dev/sdi1: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information Free blocks count wrong (351333, counted=347029). Fixy? y yes Free inodes count wrong (108932, counted=108929). Fixy? yes /dev/sdi1: * FILE SYSTEM WAS MODIFIED * 39 inodes used (0.04%, out of 108968) 16 non-contiguous files (41.0%) 1 non-contiguous directory (2.6%) # of inodes with ind/dind/tind blocks: 18/7/0 87148 blocks used (20.07%, out of 434177) 0 bad blocks 0 large files 27 regular files 3 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 30 files 06:17 1 ~# fsck -V -f -v /dev/sdi2 fsck from util-linux 2.20.1 [/sbin/fsck.ext3 (1) -- /var/cache/apt/archives] fsck.ext3 -f -v /dev/sdi2 e2fsck 1.42.9 (28-Dec-2013) /dev/sdi2: recovering journal Pass 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Pass 4: Checking reference counts Pass 5: Checking group summary information 1489 inodes used (0.71%, out of 209248) 709 non-contiguous files (47.6%) 1 non-contiguous directory (0.1%) # of inodes with ind/dind/tind blocks: 1087/59/0 360570 blocks used (43.15%, out of 835528) 0 bad blocks 1 large file 1477 regular files 3 directories 0 character device files 0 block device files 0 fifos 0 links 0 symbolic links (0 fast symbolic links) 0 sockets 1480 files 06:18 ~# mount /var/cache/apt/archives/ 06:19 ~# mount /var/lib/apt/lists/ 06:19 ~# mount |grep apt /dev/sdi2 on /var/cache/apt/archives type ext3 (rw,noatime,errors=remount-ro,data=ordered) /dev/sdi1 on /var/lib/apt/lists type ext3 (rw,noatime,errors=remount-ro,data=ordered) 06:19 ~# aptitude update ... OK # grep -v ^// /etc/apt/apt.conf.d/10jidanni APT::Default-Release experimental;//just order them in sources.list UNTRUE APT::Cache::AllVersions false; APT::Clean-Installed false; APT::Get::Purge true; APT::Install-Recommends false; Aptitude::CmdLine::Always-Prompt true; Aptitude::Purge-Unused true; Aptitude::CmdLine::Show-Why true;//511...@bugs.debian.org Aptitude::CmdLine::Show-Deps true;//587...@bugs.debian.org Acquire::http::No-Cache true;//564829 Acquire::PDiffs false; -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87zjncu2k2@jidanni.org
Bug#733565: SIX messages per on boot console should be TWO
Martin == Martin K Petersen martin.peter...@oracle.com writes:
Martin I guess we could extend the first_scan logic to cover the error
Martin case scenarios.
[SCSI] sd: Quiesce mode sense error messages
Messages about discovered disk properties are only printed once unless
they are found to have changed. Errors encountered during mode sense,
however, are printed every time we revalidate.
Quiesce mode sense errors so they are only printed during the first
scan.
Signed-off-by: Martin K. Petersen martin.peter...@oracle.com
diff --git a/drivers/scsi/sd.c b/drivers/scsi/sd.c
index 69725f7c32c1..14d601ed1956 100644
--- a/drivers/scsi/sd.c
+++ b/drivers/scsi/sd.c
@@ -2283,7 +2283,7 @@ sd_read_write_protect_flag(struct scsi_disk *sdkp,
unsigned char *buffer)
set_disk_ro(sdkp-disk, 0);
if (sdp-skip_ms_page_3f) {
- sd_printk(KERN_NOTICE, sdkp, Assuming Write Enabled\n);
+ sd_first_printk(KERN_NOTICE, sdkp, Assuming Write Enabled\n);
return;
}
@@ -2315,7 +2315,7 @@ sd_read_write_protect_flag(struct scsi_disk *sdkp,
unsigned char *buffer)
}
if (!scsi_status_is_good(res)) {
- sd_printk(KERN_WARNING, sdkp,
+ sd_first_printk(KERN_WARNING, sdkp,
Test WP failed, assume Write Enabled\n);
} else {
sdkp-write_prot = ((data.device_specific 0x80) != 0);
@@ -2383,7 +2383,8 @@ sd_read_cache_type(struct scsi_disk *sdkp, unsigned char
*buffer)
if (!data.header_length) {
modepage = 6;
first_len = 0;
- sd_printk(KERN_ERR, sdkp, Missing header in MODE_SENSE
response\n);
+ sd_first_printk(KERN_ERR, sdkp,
+ Missing header in MODE_SENSE response\n);
}
/* that went OK, now ask for the proper length */
@@ -2396,7 +2397,7 @@ sd_read_cache_type(struct scsi_disk *sdkp, unsigned char
*buffer)
if (len 3)
goto bad_sense;
else if (len SD_BUF_SIZE) {
- sd_printk(KERN_NOTICE, sdkp, Truncating mode parameter
+ sd_first_printk(KERN_NOTICE, sdkp, Truncating mode parameter
data from %d to %d bytes\n, len, SD_BUF_SIZE);
len = SD_BUF_SIZE;
}
@@ -2419,8 +2420,9 @@ sd_read_cache_type(struct scsi_disk *sdkp, unsigned char
*buffer)
/* We're interested only in the first 3 bytes.
*/
if (len - offset = 2) {
- sd_printk(KERN_ERR, sdkp, Incomplete
- mode parameter data\n);
+ sd_first_printk(KERN_ERR, sdkp,
+ Incomplete mode parameter
+ data\n);
goto defaults;
} else {
modepage = page_code;
@@ -2434,14 +2436,15 @@ sd_read_cache_type(struct scsi_disk *sdkp, unsigned
char *buffer)
else if (!spf len - offset 1)
offset += 2 + buffer[offset+1];
else {
- sd_printk(KERN_ERR, sdkp, Incomplete
- mode parameter data\n);
+ sd_first_printk(KERN_ERR, sdkp,
+ Incomplete mode
+ parameter data\n);
goto defaults;
}
}
}
- sd_printk(KERN_ERR, sdkp, No Caching mode page found\n);
+ sd_first_printk(KERN_ERR, sdkp, No Caching mode page found\n);
goto defaults;
Page_found:
@@ -2455,7 +2458,7 @@ sd_read_cache_type(struct scsi_disk *sdkp, unsigned char
*buffer)
sdkp-DPOFUA = (data.device_specific 0x10) != 0;
if (sdkp-DPOFUA !sdkp-device-use_10_for_rw) {
- sd_printk(KERN_NOTICE, sdkp,
+ sd_first_printk(KERN_NOTICE, sdkp,
Uses READ/WRITE(6), disabling FUA\n);
sdkp-DPOFUA = 0;
}
@@ -2477,16 +2480,19 @@ bad_sense:
sshdr.sense_key == ILLEGAL_REQUEST
sshdr.asc == 0x24 sshdr.ascq == 0x0)
/* Invalid field in CDB */
- sd_printk(KERN_NOTICE, sdkp, Cache data unavailable\n);
+ sd_first_printk(KERN_NOTICE, sdkp, Cache data unavailable\n);
else
- sd_printk(KERN_ERR, sdkp, Asking for cache data failed\n);
+
Bug#733551: Sanitation of CPU-state when switching from virtual-8086 mode to other task incomplete
Here is some more information from my latest tests: * Although first observed with virtual-8086 mode, the bug is not specific to virtual-8086 mode, it can be triggered with normal x86 userspace code also, even with better reproducibility. * It seems, that when changing the FPU control word with fstcw just before exit of the process, then another process could suffer when doing __do_switch * By having two rogue processes writing data to each other via a socket, time and code-position of OOPS can be influenced. * When deactivating mmap_min_addr, the NULL-dereferences during task-switch are exploitable, if kernel memory layout is known from System.map, privilege escalation might be quite likely. * I've not yet tried to build a 64-bit version, but since vm86-syscall is not required any more, there could be problems there also. You can find the new improved test code without virtual-8086 mode here: http://www.halfdog.net/Security/2013/Vm86SyscallTaskSwitchKernelPanic/FpuStateTaskSwitchOops.c -- http://www.halfdog.net/ PGP: 156A AE98 B91F 0114 FE88 2BD8 C459 9386 feed a bee -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52c745d8.1050...@halfdog.net
Processed: tagging 733826
Processing commands for cont...@bugs.debian.org: tags 733826 - moreinfo Bug #733826 [src:linux] xhci_hcd 'Too many fragments' warning appears Removed tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 733826: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733826 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: http://lists.debian.org/handler.s.c.13887950291537.transcr...@bugs.debian.org
Processed: tagging 733565
Processing commands for cont...@bugs.debian.org: tags 733565 + upstream patch Bug #733565 [src:linux] SIX messages per on boot console should be TWO Added tag(s) upstream and patch. thanks Stopping processing here. Please contact me if you need assistance. -- 733565: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=733565 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: http://lists.debian.org/handler.s.c.13888003331787.transcr...@bugs.debian.org
