Bug#690727: linux-image-3.2.0-3-686-pae: user space serial console messages held back on HS20 blade until qla2xxx is loaded
Ben Hutchings b...@decadent.org.uk writes: On Tue, 2012-10-16 at 20:44 +0200, Ferenc Wagner wrote: This is an issue on IBM HS20 blades with serial over LAN console. In short, kernel messages get through all right, but user space messages are buffered until the qla2xxx FC HBA driver module is loaded. Everything is right if I reverse the order of the two console parameters, making /dev/console refer to the tty0 virtual console. For debugging, I made the following changes: Please test Linux 3.5 (as packaged in experimental) or 3.6. 3.5 from experimental behaves the exact same way. -- Thanks, Feri. -- 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/87bog11u0a@lant.ki.iif.hu
Bug#690727: linux-image-3.2.0-3-686-pae: user space serial console messages held back on HS20 blade until qla2xxx is loaded
Ben Hutchings b...@decadent.org.uk writes: On Tue, 2012-10-16 at 20:44 +0200, Ferenc Wagner wrote: This is an issue on IBM HS20 blades with serial over LAN console. In short, kernel messages get through all right, but user space messages are buffered until the qla2xxx FC HBA driver module is loaded. Everything is right if I reverse the order of the two console parameters, making /dev/console refer to the tty0 virtual console. For debugging, I made the following changes: Please test Linux 3.5 (as packaged in experimental) or 3.6. Forgot to say that I've already partially tested 3.6 (minimal config, no modules, no qla2xxx driver): no user space console at all. I couldn't test whether loading the module eventually activates it, but the problem definitely seems to be there. I'll fully test the packaged 3.5 shortly. -- Thanks, Feri. -- 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/87hapt1uqh@lant.ki.iif.hu
Bug#595920: lxc-attach does not work
On Wed, Oct 17, 2012 at 1:37 AM, Jonathan Nieder jrnie...@gmail.com wrote: reassign 595920 src:linux linux-2.6/2.6.32-21 found 595920 linux/3.0.0~rc1-1~experimental.1 quit Grant McLean wrote[1]: It looks like someone has got the kernel patches working with 3.2 (and later in the thread, 3.3). http://www.mail-archive.com/lxc-users@lists.sourceforge.net/msg03397.html Thanks! In that message, Xavi León wrote: | FYI, I attach the kernel patchset (based on the 3.0.0-lxc1 version on | the website) for the linux version 3.2.9. Mainly I removed the patches | already applied upstream and minor twicks to comply with some changes | on the kernel. I guess they may need still some work to make it The tarball contains six patches: 1-add-SA_CLDREBOOT-flag.patch 2-Notify-container-init-parent-a-reboot-occured.patch 7-pidns-Don-t-allow-new-pids-after-the-namespace-is-d.patch 8-pidns-Support-unsharing-the-pid-namespace.patch 00014-ns-proc-Add-support-for-the-mount-namespace.patch 00015-ns-proc-add-support-for-the-pid-namespace.patch They don't match the patches in the 3.0.0-lxc1 patchset I downloaded (tarball sha1sum: 62be7a82f83c1b2dd0f45e23d09d97d3b49d1e8b) too closely. Xavi, where do these patches come from? Can we have your sign-off on them? (See Documentation/SubmittingPatches for what this means.) Hi, The patches comes from [1]. They are basically a stripped down version of those patches. I removed the code already included upstream, did some minor changes and rebased the patches so no real hard development -- that's why checksum doesn't match. In [2] and [3] (patches 19901 - 19915) you can find the patches for upstream kernel 3.2 and 3.3 respectively. I tested them and they work, although I cannot assure they are correct and bug free. To be honest, I doubt they can make it upstream in their current shape. I moved into other stuff and I didn't follow the progress of those patches on subsequent kernels -- maybe they are already applied? I can certainly sign-off them if you are willing to continue the work on them. However, I don't have a clear idea on how to proceed once they are signed-off. Do I need to send them here? Is it ok to just link to the github repo [2-3]? cheers, Xavi [1] http://lxc.sourceforge.net/patches/linux/3.0.0/3.0.0-lxc1/patches/ [2] https://github.com/confine-project/openwrt/tree/master/target/linux/generic/patches-3.2 [2] https://github.com/confine-project/openwrt/tree/master/target/linux/generic/patches-3.3 It really would be good to get lxc-attach working on a stock kernel. Thanks much for your work on this. Sincerely, Jonathan [1] http://bugs.debian.org/595920 -- 0 0 0 Xavi León| UPC - DAC - Distributed Systems Group 0 0 0 xl...@ac.upc.edu | Room D6-116 0 0 0 (+34) 93 4017187 | http://personals.ac.upc.edu/xleon -- 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/ca+hbk2yy69pj6p7bktuqv0jvh+ujw8ewext5bpa7feoykkb...@mail.gmail.com
Bug#690767: linux-image-3.2.0-3-amd64: blueteeth adaptor cause kernel crash
Package: src:linux Version: 3.2.23-1 Severity: important Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? 1. plug in the bluetooth adaptor 2. start to connect my phone to computer throw bluetooth * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? The kernel crashs. * What outcome did you expect instead? *** End of the template - remove these lines *** -- Package-specific info: ** Version: Linux version 3.2.0-3-amd64 (Debian 3.2.23-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-8) ) #1 SMP Mon Jul 23 02:45:17 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-3-amd64 root=UUID=3135c974-44cd-4309-a99c-56768252a7a1 ro resume=UUID=0f5c0dc5-14ad-42c4-b7f8-05de90f28175 quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [6.699051] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [6.699054] [drm] MTRR allocation failed. Graphics performance may suffer. [6.699307] i915 :00:02.0: irq 41 for MSI/MSI-X [6.699311] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [6.699313] [drm] Driver supports precise vblank timestamp query. [6.699345] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [6.960461] fbcon: inteldrmfb (fb0) is primary device [7.146497] Console: switching to colour frame buffer device 240x67 [7.161408] fb0: inteldrmfb frame buffer device [7.161412] drm: registered panic notifier [7.161543] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [7.161631] snd_hda_intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [7.161704] snd_hda_intel :00:1b.0: irq 42 for MSI/MSI-X [7.161728] snd_hda_intel :00:1b.0: setting latency timer to 64 [9.073198] Adding 8388604k swap on /dev/sdb10. Priority:-1 extents:1 across:8388604k [9.280428] EXT4-fs (sdb9): re-mounted. Opts: (null) [9.822079] EXT4-fs (sdb9): re-mounted. Opts: errors=remount-ro [9.979376] loop: module loaded [ 11.649977] EXT4-fs (sdb12): mounted filesystem with ordered data mode. Opts: (null) [ 11.712628] EXT4-fs (sdb6): mounted filesystem with ordered data mode. Opts: (null) [ 12.811123] RPC: Registered named UNIX socket transport module. [ 12.811129] RPC: Registered udp transport module. [ 12.811133] RPC: Registered tcp transport module. [ 12.811137] RPC: Registered tcp NFSv4.1 backchannel transport module. [ 12.851369] FS-Cache: Loaded [ 12.885889] FS-Cache: Netfs 'nfs' registered for caching [ 12.903139] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 13.220607] fuse init (API version 7.17) [ 15.268655] vboxdrv: Found 4 processor cores. [ 15.269024] vboxdrv: fAsync=0 offMin=0x3b8 offMax=0x1cb4 [ 15.269071] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [ 15.269072] vboxdrv: Successfully loaded version 4.1.18_Debian (interface 0x0019). [ 15.460510] vboxpci: IOMMU not found (not registered) [ 17.767119] Bluetooth: Core ver 2.16 [ 17.767149] NET: Registered protocol family 31 [ 17.767153] Bluetooth: HCI device and connection manager initialized [ 17.767156] Bluetooth: HCI socket layer initialized [ 17.767159] Bluetooth: L2CAP socket layer initialized [ 17.767171] Bluetooth: SCO socket layer initialized [ 17.791939] Bluetooth: RFCOMM TTY layer initialized [ 17.791945] Bluetooth: RFCOMM socket layer initialized [ 17.791947] Bluetooth: RFCOMM ver 1.11 [ 19.241029] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 19.241034] Bluetooth: BNEP filters: protocol multicast [ 22.126267] r8169 :01:00.0: eth0: link down [ 22.126278] r8169 :01:00.0: eth0: link down [ 22.127598] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 23.711028] r8169 :01:00.0: eth0: link up [ 23.712295] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 24.274719] lp0: using parport0 (interrupt-driven). [ 24.390840] ppdev: user-space parallel port driver [39787.955882] usb 1-1.3: USB disconnect, device number 3 [39789.433173] usb 1-1.3: new low-speed USB device number 4 using ehci_hcd [39789.529178] usb 1-1.3: New USB device found, idVendor=093a, idProduct=2510 [39789.529183] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [39789.529187] usb 1-1.3: Product: USB OPTICAL MOUSE [39789.529190] usb 1-1.3: Manufacturer: PIXART [39789.533169] input: PIXART USB OPTICAL MOUSE as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.3/1-1.3:1.0/input/input5 [39789.533558] generic-usb 0003:093A:2510.0002: input,hidraw0: USB HID v1.11 Mouse [PIXART USB OPTICAL MOUSE] on usb-:00:1a.0-1.3/input0 [85761.793584] usb 2-1.6: new high-speed USB device number 3 using ehci_hcd [85762.702019] hub 2-1:1.0: unable to enumerate USB device on port 6 [85762.933702] usb 2-1.6: new
Bug#690770: linux-tools-3.2: Please provide debugging package
Package: linux-tools-3.2 Version: 3.2.17-1 Severity: normal Dear Debian folks, it would be great if you could provide a package containing the debugging symbols for `perf_3.2` so I can easily debug the following issue. $ gdb -q perf_3.2 (gdb) run report Program received signal SIGSEGV, Segmentation 0x080b365c in hists__inc_nr_events () (gdb) bt f #0 0x080b365c in hists__inc_nr_events () No symbol table info available. #1 0x0809cb85 in ?? () No symbol table info available. #2 0x0809d1cd in ?? () No symbol table info available. #3 0x0809e9e0 in __perf_session__process_events () No symbol table info available. #4 0x0809ee45 in perf_session__process_events () No symbol table info available. #5 0x0806380a in cmd_report () No symbol table info available. #6 0x08057dee in _start () No symbol table info available. Thanks, Paul -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-tools-3.2 depends on: ii libc6 2.13-35 ii libdw10.153-2 ii libelf1 0.153-2 ii libnewt0.52 0.52.14-11 ii libperl5.14 5.14.2-14 ii libpython2.7 2.7.3-5 ii libslang2 2.2.4-15 ii perl 5.14.2-14 ii python2.7.3-2 Versions of packages linux-tools-3.2 recommends: ii linux-base 3.5 Versions of packages linux-tools-3.2 suggests: pn linux-doc-3.2 none -- no debconf information signature.asc Description: This is a digitally signed message part
Bug#690727: linux-image-3.2.0-3-686-pae: user space serial console messages held back on HS20 blade until qla2xxx is loaded
Ben Hutchings b...@decadent.org.uk writes: On Tue, 2012-10-16 at 20:44 +0200, Ferenc Wagner wrote: This is an issue on IBM HS20 blades with serial over LAN console. In short, kernel messages get through all right, but user space messages are buffered until the qla2xxx FC HBA driver module is loaded. Everything is right if I reverse the order of the two console parameters, making /dev/console refer to the tty0 virtual console. For debugging, I made the following changes: Please test Linux 3.5 (as packaged in experimental) or 3.6. I tried the same in another IBM Bladecenter with slightly different parts and firmware versions. There loading qla2xxx does not fix the user space console output. Even worse (on a virtual console): (initramfs) cat /proc/tty/driver/serial [ 225.538801] BUG: unable to handle kernel NULL pointer dereference at 009d [ 225.542505] IP: [c11d15a1] tty_ldisc_try+0xe/0x37 [ 225.542505] *pdpt = 376f8001 *pde = [ 225.642256] Oops: [#1] SMP and the machine freezes here (sometimes after printing two lines only). Maybe http://thread.gmane.org/gmane.linux.kernel/1101432/focus=1303356? On the other hand: (initramfs) setserial -g /dev/ttyS0 /dev/ttyS0, UART: 16550A, Port: 0x03f8, IRQ: 4 (initramfs) cat /proc/tty/driver/serial serinfo:1.0 driver revision: 0: uart:16550A port:03F8 irq:4 tx:0 rx:0 DSR|CD 1: uart:16550A port:02F8 irq:3 tx:0 rx:0 CTS|DSR|CD 2: uart:unknown port:03E8 irq:4 3: uart:unknown port:03E8 irq:3 But setserial -g /dev/ttyS1 or S2 or S3 does not help like this. (initramfs) echo hello /dev/ttyS0 waits for 30 seconds then returns without printing anything. (initramfs) echo '2hello' /dev/kmsg does not print to the serial console either, only to the VC (command line: console=ttyS0,19200n8r console=tty0 loglevel=3 break=top). User space console output appears on this machine after starting udev, but I haven't yet found out which module does this. -- Regards, Feri. -- 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/874nltz0u6@lant.ki.iif.hu
Bug#595920: lxc-attach does not work
Xavi León wrote: In [2] and [3] (patches 19901 - 19915) you can find the patches for upstream kernel 3.2 and 3.3 respectively. I tested them and they work, although I cannot assure they are correct and bug free. To be honest, I doubt they can make it upstream in their current shape. Excellent, thanks for explaining. [...] I can certainly sign-off them if you are willing to continue the work on them. However, I don't have a clear idea on how to proceed once they are signed-off. Do I need to send them here? Is it ok to just link to the github repo [2-3]? It's useful that they are in an actively maintained repo. To sign off, it would be enough to send a message saying that you certify what is said in the Developer's Certificate of Origin 1.1 --- there's no need to actually modify the patches, since we can do that already. :) To be honest, I don't know what would happen next, but that would give us everything we need for someone to submit these for discussion upstream. Once the patches are in linux-next, we can take them. Regards, Jonathan [1] http://lxc.sourceforge.net/patches/linux/3.0.0/3.0.0-lxc1/patches/ [2] https://github.com/confine-project/openwrt/tree/master/target/linux/generic/patches-3.2 [2] https://github.com/confine-project/openwrt/tree/master/target/linux/generic/patches-3.3 -- 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/20121017164905.GA12456@elie.Belkin
Bug#690794: linux-image-3.2.0-3-amd64: Fails to read EDID, results in bad monitor flickering
Package: src:linux Version: 3.2.23-1 Severity: important Dear Maintainer, Possibly identical to a problem I had on ubuntu: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/958439 In Debian Testing's gnome-control-center, and in the display settings in Debian Stable, it says that my monitor is Unknown. This results in not being able to set the refresh rate of my (CRT) monitor above what looks to me like 60hz, which is physically uncomfortable to look at. In Stable, it won't let me change the refresh rate from 0. Testing doesn't have any refresh rate settings. When my monitor is detected properly (EDID is read), based on recent experience with Ubuntu, appropriate refresh rates are selected by default. On Ubuntu, this problem persisted when I switched from an Nvidia to ATI Radeon video card, but went away, I believe, with a kernel upgrade. Output of xrandr --verbose on Debian Testing, note the lack of EDID (is there a way to attach these instead of inlining them?): - Screen 0: minimum 640 x 400, current 1600 x 1200, maximum 1920 x 1440 default connected 1600x1200+0+0 (0x13b) normal (normal) 0mm x 0mm Identifier: 0x137 Timestamp: 37561 Subpixel: no subpixels Clones: CRTC: 0 CRTCs: 0 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: 1920x1440 (0x138)0.0MHz h: width 1920 start0 end0 total 1920 skew0 clock0.0KHz v: height 1440 start0 end0 total 1440 clock0.0Hz 1856x1392 (0x139)0.0MHz h: width 1856 start0 end0 total 1856 skew0 clock0.0KHz v: height 1392 start0 end0 total 1392 clock0.0Hz 1792x1344 (0x13a)0.0MHz h: width 1792 start0 end0 total 1792 skew0 clock0.0KHz v: height 1344 start0 end0 total 1344 clock0.0Hz 1600x1200 (0x13b)0.0MHz *current h: width 1600 start0 end0 total 1600 skew0 clock0.0KHz v: height 1200 start0 end0 total 1200 clock0.0Hz 1280x1024 (0x13c)0.0MHz h: width 1280 start0 end0 total 1280 skew0 clock0.0KHz v: height 1024 start0 end0 total 1024 clock0.0Hz 1152x864 (0x13d)0.0MHz h: width 1152 start0 end0 total 1152 skew0 clock0.0KHz v: height 864 start0 end0 total 864 clock0.0Hz 1024x768 (0x13e)0.0MHz h: width 1024 start0 end0 total 1024 skew0 clock0.0KHz v: height 768 start0 end0 total 768 clock0.0Hz 800x600 (0x13f)0.0MHz h: width 800 start0 end0 total 800 skew0 clock0.0KHz v: height 600 start0 end0 total 600 clock0.0Hz 640x480 (0x140)0.0MHz h: width 640 start0 end0 total 640 skew0 clock0.0KHz v: height 480 start0 end0 total 480 clock0.0Hz 720x400 (0x141)0.0MHz h: width 720 start0 end0 total 720 skew0 clock0.0KHz v: height 400 start0 end0 total 400 clock0.0Hz - Output of xrandr --verbose on Ubuntu Oneric, which does not have this problem: - Screen 0: minimum 320 x 200, current 1600 x 1200, maximum 16384 x 16384 DisplayPort-0 disconnected (normal left inverted right x axis y axis) Identifier: 0x55 Timestamp: 32750 Subpixel: horizontal rgb Clones: CRTCs: 0 1 2 3 4 5 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: underscan vborder: 0 (0x) range: (0,128) underscan hborder: 0 (0x) range: (0,128) underscan: off supported: off on auto coherent: 1 (0x0001)range: (0,1) DisplayPort-1 disconnected (normal left inverted right x axis y axis) Identifier: 0x56 Timestamp: 32750 Subpixel: horizontal rgb Clones: CRTCs: 0 1 2 3 4 5 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: underscan vborder: 0 (0x) range: (0,128) underscan hborder: 0 (0x) range: (0,128) underscan: off supported: off on auto coherent: 1 (0x0001)
Bug#595920: lxc-attach does not work
Xavi León wrote: However, I don't have a clear idea on how to proceed once they are signed-off. Ok, looking for the current status, [1] and [2] are interesting: | So I have been working on the hard tricky fixes off and on with Oleg. It sounds to me like there are some newer patches than 3.0.0-lxc1 lurking... somewhere. ;-) [1] http://thread.gmane.org/gmane.linux.kernel/1307459/focus=2610 [2] http://thread.gmane.org/gmane.linux.kernel/1307459/focus=1308874 -- 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/20121017171005.GB12456@elie.Belkin
Bug#690794: [wheezy] Fails to read EDID, results in bad monitor flickering
Hi Darxus, Darxus wrote: In Debian Testing's gnome-control-center, and in the display settings in Debian Stable, it says that my monitor is Unknown. This results in not being able to set the refresh rate of my (CRT) monitor above what looks to me like 60hz, which is physically uncomfortable to look at. In Stable, it won't let me change the refresh rate from 0. Testing doesn't have any refresh rate settings. When my monitor is detected properly (EDID is read), based on recent experience with Ubuntu, appropriate refresh rates are selected by default. On Ubuntu, this problem persisted when I switched from an Nvidia to ATI Radeon video card, but went away, I believe, with a kernel upgrade. Thanks for a clear report. Please test with 3.5.5 or newer from experimental. (If it reproduces the bug, we can get help from upstream, and if it doesn't, we can try to find what patch fixed it.) Thanks, 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/20121017191755.GD12456@elie.Belkin
Bug#690767: [wheezy] blueteeth adaptor cause kernel crash
Hi Fermat, fermat wrote: 1. plug in the bluetooth adaptor 2. start to connect my phone to computer throw bluetooth [...] The kernel crashs. Is this reproducible? How hard is the crash --- do the caps lock and magic sysrq keys work? does ctrl-alt-delete reboot? can you access the machine remotely, e.g. using ssh? Is this a regression? Have you tried any other kernel versions, and if so, how did they behave? Do you have a log of the crash? A serial console[1] or netconsole[2] can be a good way to get one if nothing survives on-disk or on-screen (a photograph is fine). Thanks and hope that helps, Jonathan [1] http://www.kernel.org/doc/Documentation/serial-console.txt [2] http://www.kernel.org/doc/Documentation/networking/netconsole.txt -- 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/20121017193654.GE12456@elie.Belkin
Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Hi, Alan Stern a écrit : In addition to what Sarah said, it's possible that your problem is related to the fact that the keyboard and mouse operate at low speed. If you connected them through a hub then that hub would communicate with the internal hub at high speed, not low speed. I had no freeze since I bought wireless keyboard and mouse ten days ago. Obviously, I am satisfied by this happy end but I am surprised too because my previous keyboard and mouse still work fine with older hardware... Jonathan, as far as I am concerned, you can close this bug! A big thanks to all of you. Sebastien -- Sébastien Dinot, sebastien.di...@free.fr http://sebastien.dinot.free.fr/ Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer ! -- 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/20121017201312.ga17...@dinot.net
Bug#690812: linux-image-3.2.0-0.bpo.3-686-pae: Kernel 3.2.0 reports bad dvd type from NEC DVD_RW ND-3540A drive
Package: src:linux Version: 3.2.23-1~bpo60+2 Severity: important *** Please type your report below this line *** A lot of issue occurs from NEC DVD_RW ND-3540A drive with 3.2.0 kernel. The last 2.6.32 kernel has not this issues (burning and reading). A lot of DVD-R are unreadable. They are seen as DVD-RW instead of DVD-R. I must say that with 2.6.32, the dvd are not recognized all the times. Sometimes, I must open and close the tray one or two times before that the dvd is recognized. But they are always seen, not with 3.2.0. Same iso9660 dvd with photos in directories for the two kernels. linux-image 3.2.0 : dvd+rw-mediainfo /dev/sr0 INQUIRY:[_NEC][DVD_RW ND-3540A ][1.01] GET [CURRENT] CONFIGURATION: Mounted Media: 14h, DVD-RW Sequential Media ID: MCC 03RG20 Current Write Speed: 6.1x1385=8467KB/s Write Speed #0:6.1x1385=8467KB/s Write Speed #1:5.1x1385=7056KB/s Write Speed #2:4.1x1385=5645KB/s Write Speed #3:3.1x1385=4234KB/s Write Speed #4:2.0x1385=2822KB/s Write Speed #5:1.0x1385=1411KB/s GET [CURRENT] PERFORMANCE: Write Performance: 1.0x1385=1385KB/s@[0 - 2297888] :-( empty GET PERFORMACE descriptor READ DVD STRUCTURE[#10h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at:2298496*2KB=4707319808 READ DVD STRUCTURE[#0h]: Media Book Type: 25h, DVD-R book [revision 5] Last border-out at:2045*2KB=4188160 READ DISC INFORMATION: Disc status: complete Number of Sessions:1 State of Last Session: complete Number of Tracks: 1 READ FORMAT CAPACITIES: formatted:0*2048=0 00h(800):2297888*2048=4706074624 10h(10):2297888*2048=4706074624 15h(10):2297888*2048=4706074624 READ TRACK INFORMATION[#1]: Track State: complete,damaged Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:1*2KB FABRICATED TOC: Track#1 : 14@0 Track#AA : 14@2297888 Multi-session Info:#1@0 READ CAPACITY: 0*2048=0 linux-image 2.6.32 dvd+rw-mediainfo /dev/sr0 INQUIRY:[_NEC][DVD_RW ND-3540A ][1.01] GET [CURRENT] CONFIGURATION: Mounted Media: 11h, DVD-R Sequential Media ID: MCC 03RG20 Current Write Speed: 6.1x1385=8467KB/s Write Speed #0:6.1x1385=8467KB/s Write Speed #1:5.1x1385=7056KB/s Write Speed #2:4.1x1385=5645KB/s Write Speed #3:3.1x1385=4234KB/s Write Speed #4:2.0x1385=2822KB/s Write Speed #5:1.0x1385=1411KB/s GET [CURRENT] PERFORMANCE: Write Performance: 6.6x1385=9141KB/s@0 - 16.0x1385=22160KB/s@2251904 Speed Descriptor#0:03/2251904 R@16.0x1385=22160KB/s W@16.0x1385=22160KB/s Speed Descriptor#1: 03/2251904 R@12.0x1385=16620KB/s W@12.0x1385=16620KB/s Speed Descriptor#2:00/2251904 R@8.0x1385=11080KB/s W@8.0x1385=11080KB/s Speed Descriptor#3: 00/2251904 R@8.0x1385=11080KB/s W@6.0x1385=8310KB/s Speed Descriptor#4:00/2251904 R@5.0x1385=6925KB/s W@4.0x1385=5540KB/s Speed Descriptor#5: 00/2251904 R@5.0x1385=6925KB/s W@2.0x1385=2770KB/s READ DVD STRUCTURE[#10h]: Media Book Type: 00h, DVD-ROM book [revision 0] Legacy lead-out at: 2298496*2KB=4707319808 READ DVD STRUCTURE[#0h]: Media Book Type: D0h, unrecognized value Last border-out at:2045*2KB=4188160 READ DISC INFORMATION: Disc status: complete Number of Sessions:1 State of Last Session: complete Number of Tracks: 1 READ TRACK INFORMATION[#1]: Track State: complete Track Start Address: 0*2KB Free Blocks: 0*2KB Track Size:2251898*2KB Last Recorded Address: 2251897*2KB FABRICATED TOC: Track#1 : 14@0 Track#AA : 14@2251904 Multi-session Info:#1@0 READ CAPACITY: 2251898*2048=4611887104 -- Package-specific info: ** Version: Linux version 3.2.0-0.bpo.3-686-pae (Debian 3.2.23-1~bpo60+2) (debian-kernel@lists.debian.org) (gcc version 4.4.5 (Debian 4.4.5-8) ) #1 SMP Thu Aug 23 08:21:41 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.2.0-0.bpo.3-686-pae root=UUID=310f205d-4dfc-4293-966c-8b952c4d258b ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [5.429197] [drm] radeon: 64M of GTT memory ready. [5.452204] radeon :01:00.0: WB disabled [5.453871] [drm] Loading R100 Microcode [5.493346] via_rhine: v1.10-LK1.5.0 2010-10-09 Written by Donald Becker [5.493428] via-rhine :00:08.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [5.501075] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [5.502334] via-rhine :00:08.0: eth0: VIA Rhine III at 0x1e800, 00:40:f4:75:0a:3d, IRQ 19 [5.503048] via-rhine :00:08.0: eth0: MII PHY found at address 1, status 0x7849 advertising 05e1 Link [5.503103] 8139cp :00:09.0: This (id 10ec:8139 rev 10) is not an 8139C+ compatible chip, use 8139too [5.506274] 8139too: 8139too
Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Hi Sébastien, Sébastien Dinot wrote: Alan Stern a écrit : In addition to what Sarah said, it's possible that your problem is related to the fact that the keyboard and mouse operate at low speed. If you connected them through a hub then that hub would communicate with the internal hub at high speed, not low speed. I had no freeze since I bought wireless keyboard and mouse ten days ago. Obviously, I am satisfied by this happy end but I am surprised too because my previous keyboard and mouse still work fine with older hardware... Thanks, that's interesting. If you have time to test connecting the old keyboard and mouse through a hub, that would still be useful. 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/20121017205401.GF12456@elie.Belkin
Bug#690814: linux-image-3.2.0-3-486: vmlinuz-3.2.0-3-486 locks up on VIA EPIA CL-6000
Package: src:linux Version: 3.2.23-1 Severity: normal Dear Maintainer, Installation of Wheezy on this VIA EPIA CL-6000 box went fine but when the system booted after the installation, it locked up at different points in time. With locked up, I mean that nothing could be done anymore: my ssh session stalled, the machine did not answer echo requests, I could not do anything at the console. At this point, the LED indicating disk activity was turned on. I had to use the power button to restart the machine. The first time I rebooted, the system got stuck when trying to mount one of the filesystems. Rebooted again and got the login prompt. Did some more reboots and found out that the system hangs during more or less 50% of the reboots. Since the disk activity LED was always on, I tried to provoke some disk activity e.g. by installing some packages. This effectively locked up the system. I only once got the system in a locked up state without having the disk activity LED turned on. Ran memtest86+ (4 runs) without any problem. Tried another (identical) harddisk and tried to use the other IDE controller but always ran into the same problem. Since this machine had been running Lenny just fine, and Squeeze also worked fine, I decided to install a 2.6 kernel. In Wheezy however, linux-image-2.6-486 depends on linux-image-486, which in turn depends on linux-image-3.2.0-3-486. I therefore installed the 2.6 kernel from Squeeze. Note that it took several reboots to get the deb file on the system and to install it. With this kernel, the box runs just fine. Note that I also have a VIA EPIA PD-6000, which is almost identical, but runs Wheezy with the 3.2 kernel just fine. Note that, as this machine cannot run version 3.2.0-3-486 of the kernel, I used reportbug when the machine was running version 2.6.32-5-486 of the kernel. This kernel is the one from Squeeze. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: VIA Technologies, Inc. VT8623 [Apollo CLE266] [1106:3123] Subsystem: VIA Technologies, Inc. Device [1106:aa01] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 8 Region 0: Memory at e000 (32-bit, prefetchable) [size=64M] Capabilities: access denied Kernel driver in use: agpgart-via 00:01.0 PCI bridge [0604]: VIA Technologies, Inc. VT8633 [Apollo Pro266 AGP] [1106:b091] (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR+ INTx- Latency: 0 Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 Memory behind bridge: e800-e9ff Prefetchable memory behind bridge: e400-e7ff Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort+ SERR- PERR+ BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied 00:0f.0 Ethernet controller [0200]: VIA Technologies, Inc. VT6105/VT6106S [Rhine-III] [1106:3106] (rev 8b) Subsystem: VIA Technologies, Inc. Device [1106:0106] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32 (750ns min, 2000ns max), Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 12 Region 0: I/O ports at d000 [size=256] Region 1: Memory at ea00 (32-bit, non-prefetchable) [size=256] Capabilities: access denied Kernel driver in use: via-rhine 00:10.0 USB controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. Device [1106:aa01] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 32, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 11 Region 4: I/O ports at d400 [size=32] Capabilities: access denied Kernel driver in use: uhci_hcd 00:10.1 USB controller [0c03]: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller [1106:3038] (rev 80) (prog-if 00 [UHCI]) Subsystem: VIA Technologies, Inc. Device [1106:aa01] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
Bug#690814: [squeeze-wheezy regression] disk activity provokes lockups on VIA EPIA CL-6000
# regression severity 690814 important quit Hi Frank, Frank Lenaerts wrote: I had to use the power button to restart the machine. The first time I rebooted, the system got stuck when trying to mount one of the filesystems. Rebooted again and got the login prompt. Did some more reboots and found out that the system hangs during more or less 50% of the reboots. Since the disk activity LED was always on, I tried to provoke some disk activity e.g. by installing some packages. This effectively locked up the system. I only once got the system in a locked up state without having the disk activity LED turned on. [...] Since this machine had been running Lenny just fine, and Squeeze also worked fine, I decided to install a 2.6 kernel. [...] Note that it took several reboots to get the deb file on the system and to install it. With this kernel, the box runs just fine. Thanks for reporting it. A few suggestions for moving forward: * please attach full dmesg output from a normal boot (with the 2.6.32-based kernel) * could you also get a kernel log from booting the 3.2-based kernel? A full log including the lockup would be ideal --- netconsole[1] might help here. * if you have time to run a bisection search through the pre-compiled kernels at http://snapshot.debian.org/package/linux-2.6/ to find the first broken one, that could help narrow down things quite a bit. Hope that helps, and sorry I have no better ideas, Jonathan [1] http://www.kernel.org/doc/Documentation/networking/netconsole.txt -- 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/20121017211906.GG12456@elie.Belkin
Processed: Re: [squeeze-wheezy regression] disk activity provokes lockups on VIA EPIA CL-6000
Processing commands for cont...@bugs.debian.org: # regression severity 690814 important Bug #690814 [src:linux] linux-image-3.2.0-3-486: vmlinuz-3.2.0-3-486 locks up on VIA EPIA CL-6000 Severity set to 'important' from 'normal' quit Stopping processing here. Please contact me if you need assistance. -- 690814: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690814 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.135050875911692.transcr...@bugs.debian.org
Processed: Re: Mouse and keyboard freeze on Ivy Bridge platform
Processing commands for cont...@bugs.debian.org: tags 689368 + moreinfo Bug #689368 [src:linux] linux-image-3.5-trunk-amd64: Mouse and keyboard freeze on Ivy Bridge platform Added tag(s) moreinfo. # worked around by using another mouse + keyboard severity 689368 normal Bug #689368 [src:linux] linux-image-3.5-trunk-amd64: Mouse and keyboard freeze on Ivy Bridge platform Severity set to 'normal' from 'important' End of message, stopping processing here. Please contact me if you need assistance. -- 689368: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689368 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.135050888112725.transcr...@bugs.debian.org
Bug#689268: [wheezy] Intel HD 4000 (Ivy Bridge) graphics freeze
On 2012-10-17 05:21, Jonathan Nieder wrote: Per Foreby wrote: However my computer has been running without any problems for 11 days, so whatever caused this bug seems to be fixed in the 3.5.5 kernel. Drat. Ok. To recap: * Asus P8Z77-V LE. * Newish system. Works fine under load (e.g., Folding@Home) but when you started normal interactive use it started to freeze a few times a day while you were interacting with it (in particular, the freeze happens around the same time as a keyboard or mouse action). * The freeze is a bad one --- the fan spins down, the NIC stops responding, caps lock doesn't light up, ctrl+alt+del and magic sysrq have no effect. No messages about it in netconsole. * Happens reliably (how reliably? 80% of the time?) after a few hours of sustained use (?) * Logs available in the bug log. No obvious smoking guns. ;-) * Changing the amount of memory allocated to the integrated GPU in BIOS doesn't change anything. * The above describes 3.2.23-1. Based on a week and a half of running 3.5.5-1~experimental.1 it doesn't seem to be affected. Correct, apart from the timing. It's been from a few hours to five days between the freezes. But with very little interactive use during the five days. I can add that stressing the graphics doesn't seem to trigger the problem. None of the changes from 3.2 to 3.5.5 are jumping out as likely candidates for the fix, but that's a pretty wide range. What about the MTRR patch that Ben Hutchings mentioned above (commit 9e984bc1dffd405138ff22356188b6a1677c64c8)? Or maybe that's just a cosmetic change? According to https://bugs.freedesktop.org/show_bug.cgi?id=41648, this patch was added in 3.5-rc1. How reliably can you reproduce the hang on a known-bad kernel? If you have time to try 3.2.30-1 from sid, 3.4.4-1~experimental.1 from http://snapshot.debian.org/package/linux/ and 3.3.6-1~experimental.1 from http://snapshot.debian.org/package/linux-2.6/ then that could help narrow down the search. With up to five days (so far) for a freeze to occur, it might take long to narrow down the change, and the computer in question is semi production (working from home), so the freezes are very annoying. But I'll give it a try in the name of the good cause. Maybe I should start with running 3.5.5 for a few weeks, just to make sure that the freezes really are gone? Jonathan Nieder wrote: * Asus P8Z77-V LE. This makes as good a keyword for a web search as any. It found [1] which is not too encouraging. Maybe memtest86+ could be worth a try to rule some problems out. [1] http://thread.gmane.org/gmane.linux.debian.user.french/176707/focus=176710 Memory and cpu cooling were of course the first suspects. But I'm using a large Arctic heatpipe cooler and have never seen higher temperatures than +57.0°C on any core according to lm_sensors. And memtest86+ has been happy. I ran an extra pass today (about 2.5 hours) just to make sure, and everything was blue and white. The french discussion talks about RAM timing and voltage, but I'm not an overclocker (vanilla i7 3770, not 3770K) so that hardly applies. And please note that with FAH running 24/7, the computer is always under heavy load, but has never frozen while running unattended. Even when running interactively, the freezes have never been random, but has happened *exactly* when I was clicking or typing something. Btw, I found http://www.linuxbsdos.com/2012/10/06/ubuntu-12-04-lts-and-12-10-beta-2-on-intel-ivy-bridge-powered-computer/. One of the comments indicate that 3.4 fixes some sort of freeze problem on ivy bridge/HD4000. And the partiallysanedeveloper page that I linked to in the initial bug report says that the freezes are gone in 3.3. Here are some other other discussions of freezes on similar hardware on debian derivatives with the same kernel generation: http://forums.linuxmint.com/viewtopic.php?f=90t=114382 http://phoronix.com/forums/showthread.php?71895-Intel-Ivy-Bridge-On-Linux-Two-Month-Redux http://forums.linuxmint.com/viewtopic.php?f=198t=113070 http://ubuntuforums.org/showthread.php?t=1995945 /Per -- 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/507f23b3.6020...@foreby.se
Bug#689268: [wheezy] Intel HD 4000 (Ivy Bridge) graphics freeze
Per Foreby wrote: Correct, apart from the timing. It's been from a few hours to five days between the freezes. But with very little interactive use during the five days. Right --- how much interactive use does it take? I'm guessing that the time when you're not interacting the computer doesn't affect this bug (regardless of load). [...] None of the changes from 3.2 to 3.5.5 are jumping out as likely candidates for the fix, but that's a pretty wide range. What about the MTRR patch that Ben Hutchings mentioned above (commit 9e984bc1dffd405138ff22356188b6a1677c64c8)? Or maybe that's just a cosmetic change? That should be cosmetic with your card, though there's always the possibility of something subtle happening. [...] With up to five days (so far) for a freeze to occur, it might take long to narrow down the change, and the computer in question is semi production (working from home), so the freezes are very annoying. But I'll give it a try in the name of the good cause. Maybe I should start with running 3.5.5 for a few weeks, just to make sure that the freezes really are gone? Selfishly, I would suggest first trying to reproduce it on a known-bad kernel and then trying 3.3 or disabling the intel driver. [...] And memtest86+ has been happy. I ran an extra pass today (about 2.5 hours) just to make sure, and everything was blue and white. Thanks for checking. [...] Btw, I found http://www.linuxbsdos.com/2012/10/06/ubuntu-12-04-lts-and-12-10-beta-2-on-intel-ivy-bridge-powered-computer/. One of the comments indicate that 3.4 fixes some sort of freeze problem on ivy bridge/HD4000. And the partiallysanedeveloper page that I linked to in the initial bug report says that the freezes are gone in 3.3. Yes, it would be nice to narrow this down... If you blacklist the i915 kernel module and use the vesa X driver, does that avoid trouble? Thanks, 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/20121017220221.GI12456@elie.Belkin
Bug#689268: [wheezy] Intel HD 4000 (Ivy Bridge) graphics freeze
On 2012-10-18 00:02, Jonathan Nieder wrote: Per Foreby wrote: Correct, apart from the timing. It's been from a few hours to five days between the freezes. But with very little interactive use during the five days. Right --- how much interactive use does it take? Very little. I've had freezes so far, and all of the with almost no activity on the screen. Clicking a link, typing an email or closing an rxvt window. That should be cosmetic with your card, though there's always the possibility of something subtle happening. As a rule of thumb, every bugfix in a complex enough system introduces another bug. So I suppose that sometimes a bugfux might accidentally fix another bug :) With up to five days (so far) for a freeze to occur, it might take long to narrow down the change, and the computer in question is semi production (working from home), so the freezes are very annoying. But I'll give it a try in the name of the good cause. Maybe I should start with running 3.5.5 for a few weeks, just to make sure that the freezes really are gone? Selfishly, I would suggest first trying to reproduce it on a known-bad kernel and then trying 3.3 or disabling the intel driver. OK, I'll go back to 3.2.23 and work my way up. It might take some time though if the freeze doesn't behave... If you blacklist the i915 kernel module and use the vesa X driver, does that avoid trouble? Does the vesa driver support 1920x1200 these days? /Per -- 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/507f2f31.1050...@foreby.se
Bug#690821: GPU driver changes from 2.6.32.59+drm33.26
Source: linux-2.6 Version: 2.6.32-46 Tags: security - drm/i915: Attempt to fix watermark setup on 85x (v2) Prevents a crash launching the X server with 85x cards (aka #661696, also in 2.6.32.60). Regression introduced in 2.6.32-rc1 (e70236a8d3d0). - drm/i915: Move Pineview CxSR and watermark code into update_wm hook - drm/i915: Add CxSR support on Pineview DDR3 For certain cards the driver would set up self-refresh for power saving but did so incorrectly in external monitor only mode, producing flicker. - drm: integer overflow in drm_mode_dirtyfb_ioctl Integer overflow leading to denial of service or privilege escalation by users able to use the dirtyfb ioctl (i.e., users in group video, CVE-2012-0044). (The current item for CVE-2012-0044 in the Debian changelog is a typo for CVE-2012-0038.) Cc-ing Bill in case he'd like to trying the updated package once it's available to follow up on http://bugs.debian.org/688564#26. Thanks, 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/20121018000810.GK12456@elie.Belkin
Bug#690794: [wheezy] Fails to read EDID, results in bad monitor flickering
Verified problem does still exist with linux-image-3.5-trunk-amd64 from experimental. $ uname -a Linux dancer 3.5-trunk-amd64 #1 SMP Debian 3.5.5-1~experimental.1 x86_64 GNU/Linux I'm still seeing flickering. gnome-control-center still says the display is Unknown. xrandr --verbose output: - xrandr: Failed to get size of gamma for output default Screen 0: minimum 640 x 400, current 1600 x 1200, maximum 1920 x 1440 default connected 1600x1200+0+0 (0x13b) normal (normal) 0mm x 0mm Identifier: 0x137 Timestamp: 40607 Subpixel: no subpixels Clones: CRTC: 0 CRTCs: 0 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: 1920x1440 (0x138)0.0MHz h: width 1920 start0 end0 total 1920 skew0 clock0.0KHz v: height 1440 start0 end0 total 1440 clock0.0Hz 1856x1392 (0x139)0.0MHz h: width 1856 start0 end0 total 1856 skew0 clock0.0KHz v: height 1392 start0 end0 total 1392 clock0.0Hz 1792x1344 (0x13a)0.0MHz h: width 1792 start0 end0 total 1792 skew0 clock0.0KHz v: height 1344 start0 end0 total 1344 clock0.0Hz 1600x1200 (0x13b)0.0MHz *current h: width 1600 start0 end0 total 1600 skew0 clock0.0KHz v: height 1200 start0 end0 total 1200 clock0.0Hz 1280x1024 (0x13c)0.0MHz h: width 1280 start0 end0 total 1280 skew0 clock0.0KHz v: height 1024 start0 end0 total 1024 clock0.0Hz 1152x864 (0x13d)0.0MHz h: width 1152 start0 end0 total 1152 skew0 clock0.0KHz v: height 864 start0 end0 total 864 clock0.0Hz 1024x768 (0x13e)0.0MHz h: width 1024 start0 end0 total 1024 skew0 clock0.0KHz v: height 768 start0 end0 total 768 clock0.0Hz 800x600 (0x13f)0.0MHz h: width 800 start0 end0 total 800 skew0 clock0.0KHz v: height 600 start0 end0 total 600 clock0.0Hz 640x480 (0x140)0.0MHz h: width 640 start0 end0 total 640 skew0 clock0.0KHz v: height 480 start0 end0 total 480 clock0.0Hz 720x400 (0x141)0.0MHz h: width 720 start0 end0 total 720 skew0 clock0.0KHz v: height 400 start0 end0 total 400 clock0.0Hz - get-edid 21 | parse-edid get-parse-edid.txt 21 output: - parse-edid: parse-edid version 2.0.0 parse-edid: EDID checksum failed - data is corrupt. Continuing anyway. parse-edid: first bytes don't match EDID version 1 header parse-edid: do not trust output (if any). # EDID version 32 revision 118 Section Monitor Identifier NQ@:6765 VendorName NQ@ ModelName NQ@:6765 # DPMS capabilities: Active off:yes Suspend:yes Standby:no Mode1110x1568 # vfreq 17.559Hz, hfreq 33.766kHz DotClock82.93 HTimings1110 1218 1326 2456 VTimings1568 1600 1626 1923 EndMode Mode884x888 # vfreq 335.422Hz, hfreq 314.290kHz DotClock287.89 HTimings884 916 1029 916 VTimings888 943 967 937 EndMode Mode888x632 # vfreq 389.264Hz, hfreq 264.700kHz DotClock251.20 HTimings888 987 1107 949 VTimings632 635 648 680 EndMode Mode1652x1902 # vfreq 16.831Hz, hfreq 45.478kHz DotClock254.54 HTimings1652 1769 1881 5597 VTimings1902 1957 2005 2702 EndMode EndSection - -- 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/20121018004939.gc5...@chaosreigns.com
Bug#690794: [wheezy] Fails to read EDID, results in bad monitor flickering
found 690794 linux/3.5.5-1~experimental.1 quit Hi again, dar...@chaosreigns.com wrote: Verified problem does still exist with linux-image-3.5-trunk-amd64 from experimental. Thanks much for checking. Please report this to http://bugs.freedesktop.org, product DRI, component General, and let us know the bug number so we can track it. Be sure to mention: - steps to reproduce, expected result, actual result, and how the difference indicates a bug (should be simple enough) - which kernel versions and video cards you have tested and what happened with each - full dmesg output from booting and testing an affected kernel, as an attachment - full dmesg output from an unaffected kernel (also as an attachment), for comparison - any other weird symptoms or workarounds - links to http://bugs.debian.org/690794 and https://launchpad.net/bugs/958439 for the backstory Hopefully someone upstream will have some idea about how to pin the source of the problem down more precisely. The only other idea I have is that if you know of an older, unaffected kernel, it would be useful to find as new an unaffected kernel as possible by trying kernels halfway between the newest known-bad and oldest known-good kernel at http://snapshot.debian.org/package/linux-2.6/ and http://snapshot.debian.org/package/linux/ to figure out how this bug was introduced. Thanks and hope that helps, 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/20121018011825.GL12456@elie.Belkin
Processed: Re: [wheezy] Fails to read EDID, results in bad monitor flickering
Processing commands for cont...@bugs.debian.org: found 690794 linux/3.5.5-1~experimental.1 Bug #690794 [src:linux] linux-image-3.2.0-3-amd64: Fails to read EDID, results in bad monitor flickering Marked as found in versions linux/3.5.5-1~experimental.1. quit Stopping processing here. Please contact me if you need assistance. -- 690794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690794 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.135052312520664.transcr...@bugs.debian.org
Bug#690794: [wheezy] Fails to read EDID, results in bad monitor flickering
On 10/17, Jonathan Nieder wrote: component General, and let us know the bug number so we can track it. DRI bug is: https://bugs.freedesktop.org/show_bug.cgi?id=56111 -- 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/20121018014340.ge5...@chaosreigns.com
Bug#690767: [wheezy] blueteeth adaptor cause kernel crash
Hi Jonathan, On Wed, Oct 17, 2012 at 12:36:54PM -0700, Jonathan Nieder wrote: Hi Fermat, fermat wrote: 1. plug in the bluetooth adaptor 2. start to connect my phone to computer throw bluetooth [...] The kernel crashs. Is this reproducible? How hard is the crash --- do the caps lock and magic sysrq keys work? does ctrl-alt-delete reboot? can you access the machine remotely, e.g. using ssh? Yes, it can be easily reproduced, and I just prduced it two times. It is ok to plug in the adaptor, but when I send files to my phone through bluetooth, the screen frozes. capslock, magic sysrq and ctrl-alt-delete all don't works. What's more, several seconds later, the power of the keyboard get down, and then several seconds later, the power of the mouse get down again. Is this a regression? Have you tried any other kernel versions, and if so, how did they behave? I tried kernel 2.6.32-5-amd64, that kernel didn't break down, and I can send file from computer to my phone, but sending files from phone to computer failed. Do you have a log of the crash? A serial console[1] or netconsole[2] can be a good way to get one if nothing survives on-disk or on-screen (a photograph is fine). I tried to get the log. When I plug off the bluetooth adaptor and then plug in it, three messages appear on dmesg(1) output. these are the corresponding messages in /var/log/messages Oct 18 08:54:28 debian kernel: [ 473.567217] usb 2-1.5: new full-speed USB device number 4 using ehci_hcd Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New USB device found, idVendor=0a12, idProduct=0001 Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 After the crash, I rebooted my computer and run # cd /var/log; grep 473.66 -R . then I got # cd /var/log; grep 473.66 -R . ./kern.log:Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New USB device found, idVendor=0a12, idProduct=0001 ./kern.log:Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ./syslog:Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New USB device found, idVendor=0a12, idProduct=0001 ./syslog:Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 ./messages:Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New USB device found, idVendor=0a12, idProduct=0001 ./messages:Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 I checked these three files, and only syslog contains messages that are after my pluging in the adaptor and before the reboot. ## related messages in /var/log/syslog Oct 18 08:54:28 debian kernel: [ 473.567217] usb 2-1.5: new full-speed USB device number 4 using ehci_hcd Oct 18 08:54:28 debian bluetoothd[2614]: HCI dev 0 registered Oct 18 08:54:28 debian bluetoothd[2614]: Listening for HCI events on hci0 Oct 18 08:54:28 debian kernel: [ 473.661080] usb 2-1.5: New USB device found, idVendor=0a12, idProduct=0001 Oct 18 08:54:28 debian kernel: [ 473.661088] usb 2-1.5: New USB device strings: Mfr=0, Product=0, SerialNumber=0 Oct 18 08:54:28 debian bluetoothd[2614]: HCI dev 0 up Oct 18 08:54:28 debian bluetoothd[2614]: Proximity GATT Reporter Driver: Operation not permitted (1) Oct 18 08:54:28 debian bluetoothd[2614]: input-headset driver probe failed for device 54:F3:DE:69:66:01 Oct 18 08:54:28 debian bluetoothd[2614]: input-headset driver probe failed for device D8:71:57:64:5D:FD Oct 18 08:54:28 debian bluetoothd[2614]: Unable to load keys to adapter_ops: Function not implemented (38) Oct 18 08:54:28 debian bluetoothd[2614]: Adapter /org/bluez/2614/hci0 has been enabled Oct 18 08:55:01 debian /USR/SBIN/CRON[5217]: (root) CMD (/etc/init.d/apf-firewall stop /dev/null 21) Oct 18 08:55:01 debian /USR/SBIN/CRON[5218]: (fermat) CMD (/usr/bin/notify-send foo bar) Oct 18 08:55:17 debian obex-data-server: sdp_extract_seqtype: Unexpected end of packet Oct 18 09:01:02 debian kernel: imklog 5.8.11, log source = /proc/kmsg started. Oct 18 09:01:02 debian rsyslogd: [origin software=rsyslogd swVersion=5.8.11 x-pid=2273 x-info=http://www.rsyslog.com;] start Oct 18 09:01:02 debian kernel: [0.00] Initializing cgroup subsys cpuset ## messages end The former times kernel crashes, I have ever been able to see kernel messages on the screen, the these two times the screen just freeze, no messages appear. Thanks and hope that helps, Jonathan [1] http://www.kernel.org/doc/Documentation/serial-console.txt [2] http://www.kernel.org/doc/Documentation/networking/netconsole.txt -- 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/20121018014513.ga4...@debian.lzu.edu.cn
