Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works
On Fri, Jul 20, 2012 at 01:40:52 +0200, Vincent Lefevre wrote: On 2012-07-14 21:38:05 +0200, Vincent Lefevre wrote: So, it seems that when the problem occurs, the keyboard modifiers may still be working with clicks (to be confirmed). Forget that. The problem is the following: a keypress is taken into account only if the key is kept pressed for about half a second (key modifiers are generally pressed at least that time when used as a combination with a click, that's why they appear to be working as usual), a bit like the Power button needs to be pressed for some time to be taken into account. If a normal key is pressed long enough, it repeats until it is released, as usual. Sounds like you have slowkeys enabled. http://who-t.blogspot.fr/2012/06/xkb-slowkeys.html Cheers, Julien signature.asc Description: Digital signature
Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works
On 2012-07-20 08:31:19 +0200, Julien Cristau wrote: Sounds like you have slowkeys enabled. http://who-t.blogspot.fr/2012/06/xkb-slowkeys.html So, it would seem that some part of the system would enable SlowKeys in my back for one of the keyboards (I recall that when this happens while I'm using the USB keyboard, only the USB keyboard is affected, not the laptop keyboard). If there a way to know whether SlowKeys is enabled, for each available keyboard? (Note: I'm not using GNOME, and even GNOME would be useless because according to what I see on this page, it cannot differentiate keyboards.) -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- 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/20120720065857.ga4...@xvii.vinc17.org
Re: Bug#677173: 3.2.19-1: after some time, the USB keyboard no longer works
On 2012-07-20 08:58:57 +0200, Vincent Lefevre wrote: So, it would seem that some part of the system would enable SlowKeys in my back for one of the keyboards (I recall that when this happens while I'm using the USB keyboard, only the USB keyboard is affected, not the laptop keyboard). If there a way to know whether SlowKeys is enabled, for each available keyboard? (Note: I'm not using GNOME, and even GNOME would be useless because according to what I see on this page, it cannot differentiate keyboards.) Additional information: * SlowKeys can be turned on and off by pressing the Shift key for at least 10 seconds: https://bugzilla.redhat.com/show_bug.cgi?id=816764 I've tried and I confirm that this works. When several keyboards are attached, only the keyboard for which the Shift key is pressed is affected (I suppose that this is expected). * When the bug occurred in my case, I don't think I've pressed Shift for 10 seconds (well, when I do this, this is in combination with another key like PageUp / PageDown, but in this case, SlowKeys switching isn't triggered), at least in most of the cases. * It may happen that the system misses the Shift Release event. Actually this is what happened on July 14. I recall: Something interesting occurred with the USB keyboard. I was using Iceweasel, and suddenly it behaved as if both the Shift and Ctrl keys were pressed: left-clicks were extending the selection, and a left-click on a link was opening it in a background tab. After hitting various keys, this no longer occurred, [...] And this is what happened last night. This could explain why the problem occurs and that this could be specific to the USB keyboard on this machine. * I had said that the problem also occurred with the main keyboard, but I don't remember whether I did anything special with the Shift key in this case. To summarize, there could be two different problems (but I'm not sure): 1. The fact that pressing the Shift key for at least 10 seconds activates SlowKeys for this keyboard. I don't think that this feature should be enabled by default. Hidden features are bad. Also, there may be a good reason to hold the Shift key for 10 seconds: when using it in a combination of Shift + clicks. And when SlowKeys is enabled/disabled (in this way at least), something should be written to some log file, so that the user can get the information in case he wonders. 2. The fact that a Shift Release event can be missed (it remains to be confirmed) with this USB keyboard. Note: I haven't noticed any missing Release event for the other keys. -- Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/ 100% accessible validated (X)HTML - Blog: http://www.vinc17.net/blog/ Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon) -- 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/20120720074204.gb4...@xvii.vinc17.org
Bug#682116: Acknowledgement (linux-image-3.2.0-0.bpo.2-amd64: NULL pointer dereference related to nfs/cachefilesd)
As a short update: I've done some researching and came across several issues that look quite similar to this problem, e.g. http://thread.gmane.org/gmane.linux.file-systems.cachefs.general/2983 http://thread.gmane.org/gmane.linux.file-systems.cachefs.general/3043 Discussions lead to a couple of fixes that are, as far as i've seen, not part of the mainline yet: http://thread.gmane.org/gmane.linux.file-systems.cachefs.general/3003 http://thread.gmane.org/gmane.linux.nfs/46874 I've also sent an email to David Howells yesterday but will be on vacation for the next weeks so will not be able to follow up here as quickly as normally. Thanks, Raoul -- DI (FH) Raoul Bhatia M.Sc. email. r.bha...@ipax.at Technischer Leiter IPAX - Aloy Bhatia Hava OG web. http://www.ipax.at Barawitzkagasse 10/2/2/11 email.off...@ipax.at 1190 Wien tel. +43 1 3670030 FN 277995t HG Wien fax.+43 1 3670030 15 -- 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/50091feb.8010...@ipax.at
Re: [RFC] Simplifying kernel configuration for distro issues
On Fri, 13 Jul 2012, Linus Torvalds wrote: So this has long been one of my pet configuration peeves: as a user I am perfectly happy answering the questions about what kinds of hardware I want the kernel to support (I kind of know that), but many of the support infrastructure questions are very opaque, and I have no idea which of the them any particular distribution actually depends on. And it tends to change over time. For example, F14 (iirc) started using TMPFS and TMPFS_POSIX_ACL/XATTR for /dev. And starting in F16, the initrd setup requires DEVTMPFS and DEVTMPFS_MOUNT. There's been several times when I started with my old minimal config, and the resulting kernel would boot, but something wouldn't quite work right, and it can be very subtle indeed. Similarly, the distro ends up having very particular requirements for exactly *which* security models it uses and needs, and they tend to change over time. And now with systemd, CGROUPS suddenly aren't just esoteric things that no normal person would want to use, but are used for basic infrastructure. And I remember being surprised by OpenSUSE suddenly needing the RAW table support for netfilter, because it had a NOTRACK rule or something. The point I'm slowly getting to is that I would actually love to have *distro* Kconfig-files, where the distribution would be able to say These are the minimums I *require* to work. So we'd have a Distro submenu, where you could pick the distro(s) you use, and then pick which release, and we'd have something like I agree that this would be very nice to have exactly for the reasons you have pointed out. [ ... snip ... ] and then depending on the DISTRO config, we'd include one of the distro-specific ones with lists of supported distro versions and then the random config settings for that version: - distro/Kconfig.suse: config OPENSUSE_121 select OPENSUSE_11 select IP_NF_RAW # .. - distro/Kconfig.Fedora: config FEDORA_16 select FEDORA_15 select DEVTMPFS # F16 initrd needs this select DEVTMPFS_MOUNT # .. and expects the kernel to mount DEVTMPFS automatically ... config FEDORA_17 select FEDORA_16 select CGROUP_xyzzy ... and the point would be that it would make it much easier for a normal user (and quite frankly, I want to put myself in that group too) to make a kernel config that just works. But we'll first have to make 'select' to actually work, right? It currently doesn't resolve the dependencies of the selected configs, so it will just produce some very broken config. -- Jiri Kosina SUSE Labs -- 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/alpine.lrh.2.00.1207201145310.16...@twin.jikos.cz
Re: [RFC] Simplifying kernel configuration for distro issues
But we'll first have to make 'select' to actually work, right? It currently doesn't resolve the dependencies of the selected configs, so it will just produce some very broken config. We could restrict select to only select symbols with no dependencies, or *exactly* the same dependencies as the symbol containing the select. So we could have something like: config FEDORA select WANT_TMPFS config WANT_TMPFS bool config TMPFS defbool y if WANT_TMPFS This is a pattern used today in many places. But fixing up all the current select XXX would not be trivial... I have no idea how many of the select we have today that would fail the above semantic restrictions - but I guess it is a lot. We could also come up with something new like: config FEDORA require TMPFS require EXT4 = m require EXT3 = y This would set TMPS to y if TMPFS dependencies are met. And EXT3 to y and EXT4 to m if their dependencies are met. This should be more or less the same as setting the value to y/m in the user interface, which is only possible if the value is visible. Sam -- 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/20120720102644.ga23...@merkur.ravnborg.org
Bug#682226: linux-image-3.2.0-0.bpo.2-686-pae: error in removable Flash disk on remove files
Package: src:linux Version: 3.2.20-1~bpo60+1 Severity: normal Deleting some files from USB flash storage stick, kernel make error. Perhaps this is due to a ISO9660 partition in this USB stick. -- Package-specific info: ** Version: Linux version 3.2.0-0.bpo.2-686-pae (Debian 3.2.20-1~bpo60+1) (debian-kernel@lists.debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Sat Jun 30 08:29:17 UTC 2012 ** Tainted: W (512) * Taint on warning. ** Kernel log: [6.687705] Console: switching to colour frame buffer device 128x48 [6.704042] fb0: radeondrmfb frame buffer device [6.704046] drm: registered panic notifier [6.704670] [drm] Initialized radeon 2.12.0 20080528 for :01:00.0 on minor 0 [8.537367] Adding 1052252k swap on /dev/sda3. Priority:-1 extents:1 across:1052252k [8.581901] Adding 511996k swap on /dev/sdb2. Priority:-2 extents:1 across:511996k [8.591884] EXT4-fs (sdb1): re-mounted. Opts: (null) [9.189534] EXT4-fs (sdb1): re-mounted. Opts: errors=remount-ro [9.382787] loop: module loaded [9.499856] w83627hf: w83627hf: Found W83627HF chip at 0x290 [9.499940] ACPI: resource w83627hf [io 0x0295-0x0296] conflicts with ACPI region HWMT [io 0x295-0x296] [9.499945] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [ 22.696654] EXT4-fs (sdb3): mounted filesystem with ordered data mode. Opts: (null) [ 22.822806] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 22.923067] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null) [ 23.053916] EXT4-fs (sdb4): mounted filesystem with ordered data mode. Opts: (null) [ 24.369481] 8139too :00:06.0: eth1: link up, 100Mbps, full-duplex, lpa 0x41E1 [ 25.752788] ip_tables: (C) 2000-2006 Netfilter Core Team [ 25.823542] nf_conntrack version 0.5.0 (16158 buckets, 64632 max) [ 26.114759] ip6_tables: (C) 2000-2006 Netfilter Core Team [ 27.764813] RPC: Registered named UNIX socket transport module. [ 27.764822] RPC: Registered udp transport module. [ 27.764826] RPC: Registered tcp transport module. [ 27.764829] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 27.821343] FS-Cache: Loaded [ 27.928308] FS-Cache: Netfs 'nfs' registered for caching [ 27.986124] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 30.007953] via-rhine :00:08.0: eth0: link down [ 30.008821] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 34.592070] eth1: no IPv6 routers present [ 37.133585] lp0: using parport0 (interrupt-driven). [ 37.149845] ppdev: user-space parallel port driver [ 81.844604] sshd (3097): /proc/3097/oom_adj is deprecated, please use /proc/3097/oom_score_adj instead. [ 82.488102] usb 2-1: USB disconnect, device number 2 [ 82.772107] usb 2-1: new low-speed USB device number 3 using uhci_hcd [ 82.948310] usb 2-1: New USB device found, idVendor=046d, idProduct=c01b [ 82.948318] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 82.948324] usb 2-1: Product: USB-PS/2 Optical Mouse [ 82.948328] usb 2-1: Manufacturer: Logitech [ 82.966334] input: Logitech USB-PS/2 Optical Mouse as /devices/pci:00/:00:11.2/usb2/2-1/2-1:1.0/input/input6 [ 82.967061] generic-usb 0003:046D:C01B.0002: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:11.2-1/input0 [ 102.100057] usb 1-5: new high-speed USB device number 2 using ehci_hcd [ 102.238355] usb 1-5: New USB device found, idVendor=1970, idProduct=2606 [ 102.238362] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 102.238368] usb 1-5: Product: NoLimits 4GB [ 102.238372] usb 1-5: Manufacturer: DaneElec [ 102.238375] usb 1-5: SerialNumber: X (hidden) [ 102.362221] usbcore: registered new interface driver uas [ 102.383122] Initializing USB Mass Storage driver... [ 102.383406] scsi2 : usb-storage 1-5:1.0 [ 102.383617] usbcore: registered new interface driver usb-storage [ 102.383621] USB Mass Storage support registered. [ 103.382653] scsi 2:0:0:0: Direct-Access DaneElec NoLimits 4GB 1100 PQ: 0 ANSI: 0 CCS [ 103.387869] sd 2:0:0:0: Attached scsi generic sg4 type 0 [ 103.392997] sd 2:0:0:0: [sdc] 7831552 512-byte logical blocks: (4.00 GB/3.73 GiB) [ 103.393885] sd 2:0:0:0: [sdc] Write Protect is off [ 103.393896] sd 2:0:0:0: [sdc] Mode Sense: 43 00 00 00 [ 103.394733] sd 2:0:0:0: [sdc] No Caching mode page present [ 103.394744] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 103.407479] sd 2:0:0:0: [sdc] No Caching mode page present [ 103.407491] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 103.439595] sdc: sdc1 sdc2 [ 103.445453] sd 2:0:0:0: [sdc] No Caching mode page present [ 103.445462] sd 2:0:0:0: [sdc] Assuming drive cache: write through [ 103.445470] sd 2:0:0:0: [sdc] Attached SCSI removable disk [ 104.371682] [ cut here ] [ 104.371710] WARNING:
Processed: Re: Bug#682233: mpt2sas: kernel crash under load with hanged disks
Processing commands for cont...@bugs.debian.org: reassign 682233 src:linux 3.4.4-1~experimental.1 Bug #682233 [src] mpt2sas: kernel crash under load with hanged disks Warning: Unknown package 'src' Bug reassigned from package 'src' to 'src:linux'. No longer marked as found in versions 3.4.4-1~experimental.1. Ignoring request to alter fixed versions of bug #682233 to the same values previously set Bug #682233 [src:linux] mpt2sas: kernel crash under load with hanged disks Marked as found in versions linux/3.4.4-1~experimental.1. thanks Stopping processing here. Please contact me if you need assistance. -- 682233: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682233 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.13427948242494.transcr...@bugs.debian.org
Bug#682007: [squeeze-backports] NULL pointer dereference in __fscache_read_or_alloc_pages
merge 682116 682007 quit Hi, Ben Hutchings b...@decadent.org.uk 2012-07-19 13:32: On Thu, 2012-07-19 at 13:37 +0200, Bastian Blank wrote: We don't support proprietary stuff. Please remove and try again. To be clear, Bastian is referring to the proprietary kernel module (nvidia). I think this stance is too aggressive. Testing without the modules we do not support can certainly help, but in cases like this where the proprietary module is not likely to be related, I'd rather hear about problems earlier than have submitters wait until they have time to reproduce without. Luckily this has been reproduced without the nvidia module, so merging. Rhaoul writes: This is reproducable using grep -r abc * inside a directory with 9541 files (no sym- or hardlinks, no block or character special files) in 1524 directories (PHP MODX installation) Brian, is it reproducible for you, too? What is the newest kernel you tried that did not have this problem? Thanks, all. Jonathan -- 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/20120720162557.GB2885@burratino
Bug#682007: linux-image-3.2.0-0.bpo.2-amd64: NULL pointer dereference in __fscache_read_or_alloc_pages
Ben Hutchings b...@decadent.org.uk 2012-07-19 16:21: On Thu, Jul 19, 2012 at 09:03:26AM -0500, Brian Kroth wrote: Ben Hutchings b...@decadent.org.uk 2012-07-19 13:32: On Thu, 2012-07-19 at 13:37 +0200, Bastian Blank wrote: On Wed, Jul 18, 2012 at 11:16:33AM -0500, Brian Kroth wrote: ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. 21:04:00 kefka [187206.183487] Pid: 20810, comm: MATLAB Tainted: P O 3.2.0-0.bpo.2-amd64 #1 We don't support proprietary stuff. Please remove and try again. To be clear, Bastian is referring to the proprietary kernel module (nvidia). Ok. The driver is required for some third party engineering software we have to run, but I can rig a spare machine to run some of these other jobs without it for a bit. I'll report back if/when I have a new panic. I will note though that the driver comes from the debian provided packages (albeit from backports instead of stable). I realise that, but it's not part of Debian proper and none of us signed up to debug drivers that don't come with source. Fair enough. I've attached a new set of kernel messages captured from some runs without the nvidia driver loaded, but with the rest of the setup the same. It doesn't quite seem to be tickling the same code path - this time it's an invalid opcode message instead of a NULL pointer dereference. I'll let it go for a while more to see if I can get the same style message to back. Unfortunately I don't exactly know how to reproduce it. Thanks, Brian Jul 19 15:45:53 kefka [ 4289.632673] [ cut here ] Jul 19 15:45:53 kefka [ 4289.632711] kernel BUG at /build/buildd-linux_3.2.20-1~bpo60+1-amd64-tQMw4f/linux-3.2.20/fs/buffer.c:3088! Jul 19 15:45:53 kefka [ 4289.632756] invalid opcode: [#1] Jul 19 15:45:53 kefka SMP Jul 19 15:45:53 kefka Jul 19 15:45:53 kefka [ 4289.632784] CPU 3 Jul 19 15:45:53 kefka Jul 19 15:45:53 kefka [ 4289.632792] Modules linked in: Jul 19 15:45:53 kefka acpi_cpufreq Jul 19 15:45:53 kefka mperf Jul 19 15:45:53 kefka cpufreq_userspace Jul 19 15:45:53 kefka cpufreq_powersave Jul 19 15:45:53 kefka cpufreq_conservative Jul 19 15:45:53 kefka cpufreq_stats Jul 19 15:45:53 kefka autofs4 Jul 19 15:45:53 kefka cachefiles Jul 19 15:45:53 kefka kvm_intel Jul 19 15:45:53 kefka kvm Jul 19 15:45:53 kefka binfmt_misc Jul 19 15:45:53 kefka nfsd Jul 19 15:45:53 kefka nfs Jul 19 15:45:53 kefka lockd Jul 19 15:45:53 kefka fscache Jul 19 15:45:53 kefka auth_rpcgss Jul 19 15:45:53 kefka nfs_acl Jul 19 15:45:53 kefka sunrpc Jul 19 15:45:53 kefka netconsole Jul 19 15:45:53 kefka configfs Jul 19 15:45:53 kefka ext3 Jul 19 15:45:53 kefka jbd Jul 19 15:45:53 kefka coretemp Jul 19 15:45:53 kefka ipmi_watchdog Jul 19 15:45:53 kefka ipmi_devintf Jul 19 15:45:53 kefka ipmi_si Jul 19 15:45:53 kefka ipmi_msghandler Jul 19 15:45:53 kefka fuse Jul 19 15:45:53 kefka uhci_hcd Jul 19 15:45:53 kefka ohci_hcd Jul 19 15:45:53 kefka tpm_infineon Jul 19 15:45:53 kefka snd_hda_codec_realtek Jul 19 15:45:53 kefka snd_hda_intel Jul 19 15:45:53 kefka snd_hda_codec Jul 19 15:45:53 kefka snd_hwdep Jul 19 15:45:53 kefka snd_pcm_oss Jul 19 15:45:53 kefka snd_mixer_oss Jul 19 15:45:53 kefka snd_pcm Jul 19 15:45:53 kefka snd_seq_midi Jul 19 15:45:53 kefka snd_rawmidi Jul 19 15:45:53 kefka snd_seq_midi_event Jul 19 15:45:53 kefka snd_seq Jul 19 15:45:53 kefka snd_timer Jul 19 15:45:53 kefka snd_seq_device Jul 19 15:45:53 kefka snd Jul 19 15:45:53 kefka i2c_i801 Jul 19 15:45:53 kefka tpm_tis Jul 19 15:45:53 kefka tpm Jul 19 15:45:53 kefka processor Jul 19 15:45:53 kefka soundcore Jul 19 15:45:53 kefka hp_wmi Jul 19 15:45:53 kefka sparse_keymap Jul 19 15:45:53 kefka rfkill Jul 19 15:45:53 kefka tpm_bios Jul 19 15:45:53 kefka snd_page_alloc Jul 19 15:45:53 kefka thermal_sys Jul 19 15:45:53 kefka i2c_core Jul 19 15:45:53 kefka psmouse Jul 19 15:45:53 kefka wmi Jul 19 15:45:53 kefka serio_raw Jul 19 15:45:53 kefka evdev Jul 19 15:45:53 kefka joydev Jul 19 15:45:53 kefka button Jul 19 15:45:53 kefka ext4 Jul 19 15:45:53 kefka mbcache Jul 19 15:45:53 kefka jbd2 Jul 19 15:45:53 kefka crc16 Jul 19 15:45:53 kefka dm_mod Jul 19 15:45:53 kefka raid10 Jul 19 15:45:53 kefka raid456 Jul 19 15:45:53 kefka async_raid6_recov Jul 19 15:45:53 kefka async_pq Jul 19 15:45:53 kefka raid6_pq Jul 19 15:45:53 kefka async_xor Jul 19 15:45:53 kefka xor Jul 19 15:45:53 kefka async_memcpy Jul 19 15:45:53 kefka async_tx Jul 19 15:45:53 kefka raid1 Jul 19 15:45:53 kefka raid0 Jul 19 15:45:53 kefka multipath Jul 19 15:45:53 kefka linear Jul 19 15:45:53 kefka md_mod Jul 19 15:45:53 kefka hid_microsoft Jul 19 15:45:53 kefka usbhid Jul 19 15:45:53 kefka hid Jul 19 15:45:53 kefka sg Jul 19 15:45:53 kefka sr_mod Jul 19 15:45:53 kefka sd_mod Jul 19 15:45:53 kefka cdrom Jul 19 15:45:53 kefka crc_t10dif Jul 19 15:45:53 kefka ahci Jul 19 15:45:53 kefka libahci Jul 19 15:45:53 kefka libata Jul 19 15:45:53 kefka scsi_mod Jul 19 15:45:53 kefka ehci_hcd Jul 19 15:45:53
Processed: Re: [squeeze-backports] NULL pointer dereference in __fscache_read_or_alloc_pages
Processing commands for cont...@bugs.debian.org: merge 682116 682007 Bug #682116 [src:linux] linux-image-3.2.0-0.bpo.2-amd64: NULL pointer dereference related to nfs/cachefilesd Bug #682007 [src:linux] linux-image-3.2.0-0.bpo.2-amd64: NULL pointer dereference in __fscache_read_or_alloc_pages Merged 682007 682116 quit Stopping processing here. Please contact me if you need assistance. -- 682007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682007 682116: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682116 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.13428015711093.transcr...@bugs.debian.org
Bug#682007: [squeeze-backports] NULL pointer dereference in __fscache_read_or_alloc_pages
Jonathan Nieder jrnie...@gmail.com 2012-07-20 11:25: merge 682116 682007 quit Hi, Ben Hutchings b...@decadent.org.uk 2012-07-19 13:32: On Thu, 2012-07-19 at 13:37 +0200, Bastian Blank wrote: We don't support proprietary stuff. Please remove and try again. To be clear, Bastian is referring to the proprietary kernel module (nvidia). I think this stance is too aggressive. Testing without the modules we do not support can certainly help, but in cases like this where the proprietary module is not likely to be related, I'd rather hear about problems earlier than have submitters wait until they have time to reproduce without. Luckily this has been reproduced without the nvidia module, so merging. Rhaoul writes: This is reproducable using grep -r abc * inside a directory with 9541 files (no sym- or hardlinks, no block or character special files) in 1524 directories (PHP MODX installation) Brian, is it reproducible for you, too? Thanks for the test. Unfortunately, I'm on my way out of town for a couple of days and didn't have time to look at this closely. I'll get back to you with some proper results on this sometime next week. What is the newest kernel you tried that did not have this problem? I don't recall having this level of problems with 3.2.1-2~bpo60+1, but maybe it was just less frequent and I didn't notice it. Cheers, Brian signature.asc Description: Digital signature
Bug#682250: linux-image-3.2.0-2-amd64: sleep/suspend with USB drive connected produces instability (eventually lockup) on wake/resume
Package: linux-2.6
Version: 3.2.9-1
Severity: important
Dear Maintainer,
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this action?
I do not recall observing the following behavior before installing a 3.x
kernel, which I did as part of updating LMDE.
I have observed similar behavior with different hardware (a ThinkPad W510) with
same distro/version (LMDE update pack 4).
The problem is often but intermittently observed on resume from sleep/suspend
(which I do frequently).
I believe it happens most often when I do the following sequence:
1 physically attach a USB drive to my system, which automounts (almost always
as sdb, i.e. no other external drives)
Note the USB drive (a Sansa+ mp3 player) itself contains a microSD card,
which may complicate matters.
2 umount the USB drive but leave it physically attached
3 sleep the PC
4 physically detach the USB drive
5 wake the PC
This produces boot to white text messages on black screen. Often the system
will hang at this point.
Today I was able to C-A-F7 (C-A-F1 .. C-A-F6 had no effect) to the graphical
login, whereupon I observed the following text in all terminal tabs:
Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
kernel:[99821.505724] Oops: [#1] SMP
Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
kernel:[99821.507390] Stack:
Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
kernel:[99821.507589] Call Trace:
Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
kernel:[99821.508029] Code: 31 f6 88 c2 83 e2 ef a8 02 88 95 bc 02 00 00 74
13 83 e0 08 3c 01 19 f6 81 e6 00 fc ff ff 81 c6 00 0c 00 00 48 8b 85 88 02 00
00 48 8b b8 30 03 00 00 e8 75 d9 08 e1 48 8b 85 98 02 00 00 48 8b
Message from syslogd@tlrPanP5 at Jul 20 11:21:12 ...
kernel:[99821.508029] CR2: 0330
In my experience, observing text such as the above usually indicate system
instability.
(Note, that, in the scenario above, the message format above is constant: what
changes is
* the strings in square brackets (though they are invariably [0-9]{5}\.[0-9]{6})
* the string following 'Code: '
* the sting following 'CR2: '
) I.e., if I continue using the system after observing the above, it will lock
up within a matter of hours.
* What outcome did you expect instead?
I expect the system to restart normally and stably, whether or not a device is
physically attached or detached.
-- Package-specific info:
** Version:
Linux version 3.2.0-2-amd64 (Debian 3.2.9-1) (debian-kernel@lists.debian.org)
(gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Sun Mar 4 22:48:17 UTC 2012
** Command line:
BOOT_IMAGE=/vmlinuz-3.2.0-2-amd64
root=UUID=5821418b-0f83-43b0-99f2-77964602ef6b ro quiet
** Tainted: D (128)
* Kernel has oopsed before.
** Kernel log:
[99817.716239] jmb38x_ms :07:00.3: setting latency timer to 64
[99817.716323] nouveau :01:00.0: power state changed by ACPI to D0
[99817.716333] nouveau :01:00.0: power state changed by ACPI to D0
[99817.716344] nouveau :01:00.0: power state changed by ACPI to D0
[99817.716353] nouveau :01:00.0: power state changed by ACPI to D0
[99817.716364] nouveau :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16
[99817.716371] nouveau :01:00.0: setting latency timer to 64
[99817.716378] [drm] nouveau :01:00.0: POSTing device...
[99817.716384] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset
0xDBE1
[99817.716882] sd 0:0:0:0: [sda] Starting disk
[99817.741847] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset
0xDFE6
[99817.748233] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset
0xE8A9
[99817.748306] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset
0xE977
[99817.749456] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset
0xEC20
[99817.749460] [drm] nouveau :01:00.0: Parsing VBIOS init table at offset
0xEC85
[99817.769392] [drm] nouveau :01:00.0: Restoring GPU objects...
[99818.036075] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[99818.038689] ata2.00: configured for UDMA/100
[99818.044062] ata6: SATA link down (SStatus 0 SControl 300)
[99818.052061] usb 8-2: reset full-speed USB device number 20 using uhci_hcd
[99818.052107] ata5: SATA link down (SStatus 0 SControl 300)
[99818.063047] [drm] nouveau :01:00.0: Reinitialising engines...
[99818.063601] [drm] nouveau :01:00.0: Restoring mode...
[99818.179182] iwlwifi :02:00.0: RF_KILL bit toggled to enable radio.
[99818.182635] Extended CMOS year: 2000
[99818.336052] usb 3-2: reset full-speed USB device number 2 using uhci_hcd
[99820.748173] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[99820.752597] ata1.00: configured for UDMA/133
[99820.780070] PM: resume of devices complete after 3068.344 msecs
[99820.780540] PM: Finishing wakeup.
[99820.780544] Restarting tasks ...
[99820.780625] usb 8-2: USB
Bug#682250: linux-image-3.2.0-2-amd64: sleep/suspend with USB drive connected produces instability (eventually lockup) on wake/resume
On Fri, Jul 20, 2012 at 01:56:00PM -0400, Tom Roche wrote: Package: linux-2.6 Version: 3.2.9-1 Severity: important [...] This is long outdated, please upgrade to 3.2.21-3. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- 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/20120720182414.ga1...@decadent.org.uk
Processed: tagging 682250
Processing commands for cont...@bugs.debian.org: tags 682250 + moreinfo Bug #682250 [linux-2.6] linux-image-3.2.0-2-amd64: sleep/suspend with USB drive connected produces instability (eventually lockup) on wake/resume Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 682250: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=682250 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.13428086675865.transcr...@bugs.debian.org
Bug#681553: Hardware problem
Hi! Now i have the same problem with linux-image-3.2.0-2-686-pae (linux-image-3. 3.2.20-1) so i think its hardware related, so this bug is no bug and can be closed. /Peter. -- 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/caddkrcg64nwicm531+-jt3qmpmxzsgoxsqzyzgra8a1km8s...@mail.gmail.com
