Processed: reassign 666021 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 666021 src:linux Bug #666021 [src:linux-2.6] linux-image-3.2.0-2-powerpc64: Kernel reports page allocation failure: order:1, mode:0x20 Warning: Unknown package 'src:linux-2.6' Bug reassigned from package 'src:linux-2.6' to 'src:linux'. No longer marked as found in versions linux-2.6/3.2.12-1, linux-2.6/3.2.18-1, linux-2.6/3.2.9-1, and linux-2.6/3.2.13-1. Ignoring request to alter fixed versions of bug #666021 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 666021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666021 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.137214076724244.transcr...@bugs.debian.org
Bug#714037: linux-image-3.9-1-amd64: Display subsystem runs mad when using Xorg atop linux-image-3.9-1-amd64.
Package: src:linux Version: 3.9.6-1 Severity: important Dear Maintainer, I have a well-working Debian GNU/Linux System with linux-image-3.2.0-4-amd64 on my MacBook5,2 laptop. Yesterday, linux-image-3.9-1-amd64 came with upgrades. From then on, the gdm3 seems launching Xorg and showing login screen normally, but once I log in, the screen become dark, and a large amount of white dots start growing from the top of the screen. Xorg then seems crashes and restart, but screen become dark again, and everything repeats. The problem does not occur on my other computers running Debian atop linux-image-3.9-1-amd64, which are all lack of a NVIDIA GeForce 9400M G video card within an MCP79 chipset. Is this problem caused by module nouveau? By the way, Bug #709806 may be related to the same reason, for they are only known to occur on MacBook5,2 laptop. In order to work with this MacBook5,2 laptop, I have to boot it with linux-image-3.2.0-4-amd64, with using metacity instead of gnome-shell. Thanks for your regardness. -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-4) ) #1 SMP Debian 3.9.6-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.9-1-amd64 root=UUID=582ac105-02e7-4f0d-ad8b-0d341c17afab ro ** Not tainted ** Kernel log: [ 11.924140] nouveau [ PTHERM][:02:00.0] Programmed thresholds [ 90(3), 95(3), 95(2), 135(5) ] [ 11.924296] [TTM] Zone kernel: Available graphics memory: 1899754 kiB [ 11.924302] [TTM] Initializing pool allocator [ 11.924310] [TTM] Initializing DMA pool allocator [ 11.926079] nouveau [ DRM] VRAM: 256 MiB [ 11.926089] nouveau [ DRM] GART: 512 MiB [ 11.926097] nouveau [ DRM] TMDS table version 2.0 [ 11.926101] nouveau [ DRM] DCB version 4.0 [ 11.926106] nouveau [ DRM] DCB outp 00: 01000123 00010014 [ 11.926111] nouveau [ DRM] DCB outp 01: 02021232 0010 [ 11.926115] nouveau [ DRM] DCB outp 02: 01021230 001e [ 11.926120] nouveau [ DRM] DCB conn 00: 0040 [ 11.926125] nouveau [ DRM] DCB conn 01: 2130 [ 11.936156] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 11.936163] [drm] No driver support for vblank timestamp query. [ 11.948328] nouveau E[PBUS][:02:00.0] MMIO read of 0x00020002 FAULT at 0x100220 [ 11.984303] nouveau E[PBUS][:02:00.0] MMIO read of 0x0008 FAULT at 0x10022c [ 12.012279] nouveau E[PBUS][:02:00.0] MMIO read of 0x0008 FAULT at 0x100238 [ 12.072237] nouveau E[PBUS][:02:00.0] MMIO read of 0x0008 FAULT at 0x1002c0 [ 12.104222] nouveau E[PBUS][:02:00.0] MMIO read of 0x0008 FAULT at 0x1002e4 [ 12.104224] nouveau [ DRM] 4 available performance level(s) [ 12.104228] nouveau [ DRM] 0: core 100MHz shader 200MHz voltage 900mV fanspeed 100% [ 12.104231] nouveau [ DRM] 1: core 150MHz shader 300MHz voltage 900mV fanspeed 100% [ 12.104235] nouveau [ DRM] 2: core 350MHz shader 800MHz voltage 900mV fanspeed 100% [ 12.104238] nouveau [ DRM] 3: core 450MHz shader 1100MHz voltage 1010mV fanspeed 100% [ 12.104239] nouveau [ DRM] c: [ 12.116225] hda_codec: ALC889A: SKU not ready 0x40f0 [ 12.117007] nouveau [ DRM] MM: using M2MF for buffer copies [ 12.148515] nouveau [ DRM] allocated 1280x800 fb: 0x5, bo 88013ab3a000 [ 12.148624] fbcon: nouveaufb (fb0) is primary device [ 12.186790] Console: switching to colour frame buffer device 160x50 [ 12.187614] nouveau :02:00.0: fb0: nouveaufb frame buffer device [ 12.187631] nouveau :02:00.0: registered panic notifier [ 12.187651] [drm] Initialized nouveau 1.1.0 20120801 for :02:00.0 on minor 0 [ 12.230190] cfg80211: World regulatory domain updated: [ 12.230212] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 12.230223] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 12.230234] cfg80211: (2457000 KHz - 2482000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 12.230244] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (300 mBi, 2000 mBm) [ 12.230255] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 12.230265] cfg80211: (5735000 KHz - 5835000 KHz @ 4 KHz), (300 mBi, 2000 mBm) [ 12.230350] cfg80211: Calling CRDA for country: AW [ 12.243519] cfg80211: Regulatory domain changed to country: AW [ 12.243540] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 12.243550] cfg80211: (2402000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm) [ 12.243560] cfg80211: (517 KHz - 525 KHz @ 4 KHz), (N/A, 2000 mBm) [ 12.243569] cfg80211: (525 KHz - 533 KHz @ 4 KHz), (N/A, 2000 mBm) [ 12.243578] cfg80211: (549 KHz - 571 KHz @ 4 KHz), (N/A, 2700 mBm) [ 12.636130] input: HDA Digital PCBeep as /devices/pci00
Bug#629636: marked as done (linux-image-2.6.32-5-kirkwood: IPsec aes-sha1 with kirkwood/mv_cesa causes CPU to spin)
Your message dated Tue, 25 Jun 2013 08:09:20 +0200 with message-id <20130625060920.GA5610@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #629636, regarding linux-image-2.6.32-5-kirkwood: IPsec aes-sha1 with kirkwood/mv_cesa causes CPU to spin to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 629636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=629636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: normal Whilst deploying IPsec (with strongswan-ike2) I ran into a complication[1] that causes mv_cesa to spin the CPU when the system receives an IPsec ESP packet; it seems to be able to send traffic (before the CPU spin) as a ICMP Echo request (a la pin) out from the system out is okay, until the ICMP Reply comes back. The packet never 'arrives' as far as userspace is concerned and the only way to stop the CPU spinning is a reboot. The configuration I have been using is: server (Marvell OpenRD) conn %default keyexchange=ikev2 mobike=no auto=add conn soas-v6 left=2001:db8:f00:ba4::1 leftprotoport=tcp/echo right=%any authby=secret type=transport conn soas-v4 left=192.0.2.1 leftprotoport=tcp/echo right=%any authby=secret type=transport client (my x86-filth laptop) conn %default keyexchange=ikev2 mobike=no auto=route conn soas-v6 left=%defaultroute right=2001:db8:f00:ba4::1 rightprotoport=tcp/echo authby=secret type=transport conn soas-v4 left=%defaultroute right=192.0.2.1 rightprotoport=tcp/echo authby=secret type=transport Noticing that IPsec is doing hardware offloading, I looked to see what has been happening to mv_cesa.c since v2.6.32[2] and nothing stands out other than 750052dd where SHA1 is enabled (which was backported into 2.6.32) and there does not seem to be anything bug fixing wise since. So I tried disabling SHA1 by tinkering with the server side of the configuration to add: conn %default esp=aes-md5 Now using md5, things start to work. Looks to me as either SHA1 does not work with IPsec, or when it is combined with at least AES. If more information is needed then do get intouch. Cheers [1] I seem to not be the only one http://marc.info/?l=linux-crypto-vger&m=130746635214483&w=2 [2] git log v2.6.32..HEAD drivers/crypto/mv_cesa.c -- Package-specific info: ** Version: Linux version 2.6.32-5-kirkwood (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Thu May 19 12:56:20 UTC 2011 ** Command line: console=ttyS1,115200 panic=10 ubi.mtd=root kw_openrd_init_uart1=232 root=ubi0:rootfs rootfstype=ubifs rw ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [ 46.358343] NET: Registered protocol family 15 [ 46.372871] alg: No test for cipher_null (cipher_null-generic) [ 46.378824] alg: No test for ecb(cipher_null) (ecb-cipher_null) [ 46.384900] alg: No test for digest_null (digest_null-generic) [ 46.390835] alg: No test for compress_null (compress_null-generic) [ 47.586948] Initializing XFRM netlink socket [ 88.324860] alg: No test for authenc(hmac(md5),cbc(aes)) (authenc(hmac(md5-generic),mv-cbc-aes)) [ snipped] ... [24010.137237] alg: No test for authenc(hmac(sha1),cbc(aes)) (authenc(mv-hmac-sha1,mv-cbc-aes)) ** Model information Processor : Feroceon 88FR131 rev 1 (v5l) Hardware: Marvell OpenRD Ultimate Board Revision: ** Loaded modules: Module Size Used by xfrm6_mode_tunnel 1474 0 xfrm4_mode_tunnel 1546 0 esp64591 0 xfrm6_mode_transport 1300 0 authenc 5940 0 xfrm4_mode_transport 1276 0 xt_multiport2341 1 xfrm_user 18561 2 xfrm4_tunnel1407 0 tunnel4 2035 1 xfrm4_tunnel ipcomp 1698 0 xfrm_ipcomp 3557 1 ipcomp esp44807 0 ah4 3703 0 ctr 3241 0 twofish 7467 0 twofish_common 14498 1 twofish camellia 21397 0 serpent21417 0 blowfish8262 0 cast5 16967 0 des_generic16617 0 cbc 2313 0 xcbc2219 0 rmd160 8978 0 sha256_generic 8818 0 crypto_null 2122 0 af_key 32325 0 sd_mo
Bug#630253: marked as done (linux-2.6: motion / v4l / kernel causing USB to disconnect)
Your message dated Tue, 25 Jun 2013 08:09:20 +0200 with message-id <20130625060920.GA5610@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #630253, regarding linux-2.6: motion / v4l / kernel causing USB to disconnect to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 630253: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=630253 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-5-486 Severity: important Hello, I am unable to get motion work stable under squeeze. This was workin fine in lenny. In squeeze I had to use libv4l-compat and start motion with LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so /usr/bin/motion However it crashes the USB subsystem after few seconds: sudo LD_PRELOAD=/usr/lib/libv4l/v4l1compat.so /usr/bin/motion [0] Processing thread 0 - config file /etc/motion/motion.conf [0] Motion 3.2.12 Started [0] ffmpeg LIBAVCODEC_BUILD 3412993 LIBAVFORMAT_BUILD 3415808 [0] Thread 1 is from /etc/motion/motion.conf [0] motion-httpd/3.2.12 running, accepting connections [1] Thread 1 started [0] motion-httpd: waiting for data on port TCP 8080 [1] cap.driver: "spca561" [1] cap.card: "Generic Digital camera" [1] cap.bus_info: "usb-:00:11.2-2" [1] cap.capabilities=0x0501 [1] - VIDEO_CAPTURE [1] - READWRITE [1] - STREAMING [1] Test palette YU12 (320x240) [1] Using palette YU12 (320x240) bytesperlines 320 sizeimage 115200 colorspace 0008 [1] found control 0x00980900, "Brightness", range 0,63 [1] "Brightness", default 32, current 32 [1] found control 0x00980901, "Contrast", range 0,63 [1] "Contrast", default 32, current 32 [1] found control 0x00980903, "Hue", range 1,127 [1] "Hue", default 64, current 64 [1] found control 0x00980910, "Gamma (software)", range 500,3000 [1] "Gamma (software)", default 1000, current 1000 [1] found control 0x00980912, "Auto Gain", range 0,1 [1] "Auto Gain", default 1, current 1 [1] mmap information: [1] frames=4 [1] 0 length=16777216 [1] 1 length=16777216 [1] 2 length=16777216 [1] 3 length=16777216 [1] Using V4L2 [1] Resizing pre_capture buffer to 1 items libv4l2: error dequeuing buf: Input/output error [1] v4l2_next: VIDIOC_DQBUF: EIO (s->pframe 0): Input/output error [1] v4l2_next: VIDIOC_QBUF: Invalid argument [1] v4l2_next: VIDIOC_QBUF: Invalid argument [1] v4l2_next: VIDIOC_QBUF: Invalid argument [1] v4l2_next: VIDIOC_QBUF: Invalid argument [1] Error capturing first image [1] Started stream webcam server in port 8081 [1] v4l2_next: VIDIOC_QBUF: Invalid argument [1] Video device fatal error - Closing video device [1] Closing video device /dev/video0 libv4l2: warning v4l2 mmap buffers still mapped on close() ^C[0] httpd - Finishing [0] httpd Closing [0] httpd thread exit [1] Thread exiting [0] Motion terminating Followin is logged in messages: Jun 12 13:37:40 wyse motion: [1] #011"Auto Gain", default 1, current 1 Jun 12 13:37:41 wyse kernel: [ 258.655781] gspca: ISOC data error: [0] len=320, status=-84 Jun 12 13:37:41 wyse kernel: [ 258.816275] usb 1-2: USB disconnect, address 13 Jun 12 13:37:41 wyse kernel: [ 258.822589] gspca: disconnect complete Jun 12 13:37:41 wyse kernel: [ 259.072151] usb 1-2: new full speed USB device u sing uhci_hcd and address 14 Jun 12 13:37:41 wyse motion: [1] Closing video device /dev/video0 Jun 12 13:37:41 wyse kernel: [ 259.277314] usb 1-2: New USB device found, idVen dor=04fc, idProduct=0561 Jun 12 13:37:41 wyse kernel: [ 259.277365] usb 1-2: New USB device strings: Mfr =1, Product=2, SerialNumber=0 Jun 12 13:37:41 wyse kernel: [ 259.277409] usb 1-2: Product: Generic Digital ca mera Jun 12 13:37:41 wyse kernel: [ 259.277446] usb 1-2: Manufacturer: Sunplus Techn ology Co., Ltd. I don't have any other USB device connected to the machine. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following
Bug#632044: marked as done (linux-image-2.6.32-5-amd64: Sandisk Cruzer U3 memory stick not usable)
Your message dated Tue, 25 Jun 2013 08:09:20 +0200 with message-id <20130625060920.GA5610@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #632044, regarding linux-image-2.6.32-5-amd64: Sandisk Cruzer U3 memory stick not usable to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 632044: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=632044 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-35 Severity: normal Hi, i am experiencing problems between Debian 6.0.2 and a Sandisk Cruzer U3 memory stick (4 GB). These sticks appear as USB hub with an emulated CD-ROM drive and a memory stick storage device. So Linux creates /dev/srN as well as /dev/sdX and /dev/sdX1 when such a stick is plugged in. But Debian 6.0.2 drops the devices a few seconds after they appear. /var/log/messages reports a normal installation of the devices, then an unrecoverable error with an SCSI command READ(10), then it resets the USB device multiple times, and finally drops the device files. If i kill the udisks demon, the devices do not vanish and i can read at ~ 900 kB/s from the /dev/sr2 device. But reading from the /dev/sdb device stalls and causes the device files to vanish after some seconds. /var/log/messages lines are similar to those with udisks enabled. The hardware is not to blame alone. I booted RIPLinuX 9.3 (slackware based) on the same machine. No problems with reading the entire memory stick. Speed is 23 MB/s. A SuSE on an older machine could read at 6 MB/s. --- $ uname -a Linux debian2 2.6.32-5-amd64 #1 SMP Tue Jun 14 09:42:28 UTC 2011 x86_64 GNU/Linux $ dpkg -l | grep ^ii | grep linux-image ii linux-image-2.6-amd642.6.32+29 Linux 2.6 for 64-bit PCs (meta-package) ii linux-image-2.6.32-5-amd64 2.6.32-35 Linux 2.6.32 for 64-bit PCs --- With udisks demon still active and trying to automount, i got: --- Jun 26 09:44:22 debian2 kernel: [165443.464304] usb 1-3.2: new high speed USB device using ehci_hcd and address 27 Jun 26 09:44:22 debian2 kernel: [165443.557530] usb 1-3.2: New USB device found, idVendor=0781, idProduct=5406 Jun 26 09:44:22 debian2 kernel: [165443.557539] usb 1-3.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Jun 26 09:44:22 debian2 kernel: [165443.557546] usb 1-3.2: Product: U3 Cruzer Micro Jun 26 09:44:22 debian2 kernel: [165443.557551] usb 1-3.2: Manufacturer: SanDisk Jun 26 09:44:22 debian2 kernel: [165443.557555] usb 1-3.2: SerialNumber: 0164620760128686 Jun 26 09:44:22 debian2 kernel: [165443.557757] usb 1-3.2: configuration #1 chosen from 1 choice Jun 26 09:44:22 debian2 kernel: [165443.558188] scsi15 : SCSI emulation for USB Mass Storage devices Jun 26 09:44:27 debian2 kernel: [165448.557054] scsi 15:0:0:0: Direct-Access SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 CCS Jun 26 09:44:27 debian2 kernel: [165448.557680] scsi 15:0:0:1: CD-ROM SanDisk Cruzer 8.02 PQ: 0 ANSI: 0 Jun 26 09:44:27 debian2 kernel: [165448.558693] sd 15:0:0:0: Attached scsi generic sg4 type 0 Jun 26 09:44:27 debian2 kernel: [165448.561374] sd 15:0:0:0: [sdb] 7864319 512-byte logical blocks: (4.02 GB/3.74 GiB) Jun 26 09:44:27 debian2 kernel: [165448.562519] sd 15:0:0:0: [sdb] Write Protect is off Jun 26 09:44:27 debian2 kernel: [165448.563570] sr3: scsi3-mmc drive: 48x/48x tray Jun 26 09:44:27 debian2 kernel: [165448.563970] sr 15:0:0:1: Attached scsi generic sg5 type 5 Jun 26 09:44:27 debian2 kernel: [165448.565121] sdb: sdb1 Jun 26 09:44:27 debian2 kernel: [165448.567643] sd 15:0:0:0: [sdb] Attached SCSI removable disk Jun 26 09:44:57 debian2 kernel: [165478.853879] usb 1-3.2: reset high speed USB device using ehci_hcd and address 27 Jun 26 09:45:28 debian2 kernel: [165509.880686] usb 1-3.2: reset high speed USB device using ehci_hcd and address 27 Jun 26 09:45:59 debian2 kernel: [165540.365260] usb 1-3.2: reset high speed USB device using ehci_hcd and address 27 Jun 26 09:46:29 debian2 kernel: [165570.829581] usb 1-3.2: reset high speed USB device using ehci_hcd and address 27 Jun 26 09:46:50 debian2 kernel: [165591.417455] sd 15:0:0:0: Device offlined - not ready after error recovery Jun 26 09:46:50 debian2 kernel: [165591.417478] sd 15:0:0:0: [sdb] Unhandled error code Jun 26 09:46:50 debian2 kernel: [165591.417
Re: Dropping support for the smallest armel machines
I increased the kernel zimage flash available to 4mb on an Intel SS4000E (iop32x) by reconfiguring the flash with fconfig, deleting the unused parts used by the stock firmware. This enabled me to upgrade the kernel to v3.2. This does need serial console access as Ben says but that is true whatever kernel you want to flash. Chris Sent from my Nexus 10 Aaro Koskinen wrote: >On Mon, Jun 24, 2013 at 11:44:42PM +0100, Ben Hutchings wrote: >> We have a recurring problem with building kernels for armel: three >> flavours (iop32x, ixp4xx, orion5x) require the kernel image size to be >> less than 1.4-1.5 MB in order to fit into a fixed flash partition. > >At least on Thecus N2100 (iop32x), the kernel partition can be increased >to 2.5 MB by deleting a redundant partition used by the original firmware. >This will however require manual actions from the user and access to >serial console. > >A. > > >-- >To UNSUBSCRIBE, email to debian-arm-requ...@lists.debian.org >with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org >Archive: >http://lists.debian.org/20130624235218.gd20...@blackmetal.musicnaut.iki.fi >
linux_3.10~rc7-1~exp1_multi.changes is NEW
binary:linux-support-3.10-rc7 is NEW. Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. -- 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/e1urhux-0004al...@franck.debian.org
Processing of linux_3.10~rc7-1~exp1_multi.changes
linux_3.10~rc7-1~exp1_multi.changes uploaded successfully to localhost along with the files: linux_3.10~rc7-1~exp1.dsc linux_3.10~rc7.orig.tar.xz linux_3.10~rc7-1~exp1.debian.tar.xz linux-support-3.10-rc7_3.10~rc7-1~exp1_all.deb linux-doc-3.10_3.10~rc7-1~exp1_all.deb linux-manual-3.10_3.10~rc7-1~exp1_all.deb linux-source-3.10_3.10~rc7-1~exp1_all.deb Greetings, Your Debian queue daemon (running on host franck.debian.org) -- 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/e1urhb6-0002it...@franck.debian.org
Re: Dropping support for the smallest armel machines
On Mon, Jun 24, 2013 at 11:44:42PM +0100, Ben Hutchings wrote: > We have a recurring problem with building kernels for armel: three > flavours (iop32x, ixp4xx, orion5x) require the kernel image size to be > less than 1.4-1.5 MB in order to fit into a fixed flash partition. At least on Thecus N2100 (iop32x), the kernel partition can be increased to 2.5 MB by deleting a redundant partition used by the original firmware. This will however require manual actions from the user and access to serial console. A. -- 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/20130624235218.gd20...@blackmetal.musicnaut.iki.fi
Re: Dropping support for the smallest armel machines
I don't think anyone is going to greatly miss support for the nslu2. It can no longer be installed using d-i anyway. I imagine most of the deployments where it makes sense to still be using a nslu2 are ones where running an old kernel version doesn't much matter. The iop32x boxes are rather more expandable and tend to lend themselves to being important little servers on a LAN, which would be painful to lose support for. -- see shy jo signature.asc Description: Digital signature
Re: Dropping support for the smallest armel machines
On Tue, 2013-06-25 at 00:26 +0100, Ben Hutchings wrote: [...] > I think it may just be a > case of adding the right ID numbers and block sizes to the existing > Spansion SPI flash driver, though. I have a datasheet for the flash > chip, if anyone's interested. Sorry, not sure I thought that. The chip is actually memory-mapped and supports CFI. It should be supported by the cfi_flash and/or cfi_mtd drivers in u-boot (not sure what the distinction between those is). Ben. -- Ben Hutchings Life is like a sewer: what you get out of it depends on what you put into it. signature.asc Description: This is a digitally signed message part
Re: Dropping support for the smallest armel machines
On Mon, 2013-06-24 at 23:44 +0100, Ben Hutchings wrote: [...] > Perhaps [the DNS-323] could be supported by > putting a second stage uboot in flash which would load the kernel and > initramfs from disk, as suggested in [3]? [...] > [3] http://dns323.kood.org/howto:uboot Alternately it could load a combined kernel+initramfs image from the ~6 MB 'filesystem' partition, if the initramfs size is likely to say under ~4 MB. Upstream u-boot still doesn't support this model and doesn't appear to have a driver for the S29GL-M MirrorBit flash. I think it may just be a case of adding the right ID numbers and block sizes to the existing Spansion SPI flash driver, though. I have a datasheet for the flash chip, if anyone's interested. Ben. -- Ben Hutchings Life is like a sewer: what you get out of it depends on what you put into it. signature.asc Description: This is a digitally signed message part
Dropping support for the smallest armel machines
We have a recurring problem with building kernels for armel: three flavours (iop32x, ixp4xx, orion5x) require the kernel image size to be less than 1.4-1.5 MB in order to fit into a fixed flash partition. As more features continue to be added to Linux and cannot always configurable as a module, it is necessary to override and disable them on these three configurations[1]. I don't think this is sustainable unless someone who particularly cares about these older platforms steps up to take on this task. The iop32x and ixp4xx hardware appears to been discontinued in 2008. If we remove these flavours now, they will still be supported in Debian 7 until 2016. I think 8 years of support is pretty good. According to comments in the current configuration, the current size limit of 1.5 MB for orion5x is due to the DNS-323, while other models have a ~2 MB flash partition for the kernel. Dropping support for the DNS-323 would make it possible to raise this limit. However, this model was only discontinued in 2012[2]. Perhaps it could be supported by putting a second stage uboot in flash which would load the kernel and initramfs from disk, as suggested in [3]? [1] Currently OABI_COMPAT, CRYPTO_FIPS, VGA_ARB, PCI_QUIRKS, FTRACE, KSM, NETLINK_MMAP, NETLINK_DIAG, SECURITY_YAMA. Also, SECURITY_APPARMOR and SECURITY_TOMOYO are currently disabled for all armel flavours, but I think they should be enabled where possible. [2] http://www.dlink.com/us/en/support/product/dns-323-sharecenter-2-bay-network-storage-enclosure [3] http://dns323.kood.org/howto:uboot Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Re: Linux udeb cleanup
On Tue, 2013-06-11 at 05:50 +0100, Ben Hutchings wrote: > - minix-modules: unmaintained upstream; not suitable for installation > (16-bit uid/gid, 32-bit size) ...but really needed for at least one platform: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502936 Ben. -- Ben Hutchings Lowery's Law: If it jams, force it. If it breaks, it needed replacing anyway. signature.asc Description: This is a digitally signed message part
Bug#711891: Acknowledgement (linux-image-3.2.0-4-amd64: parallel printer port not detected (parport_serial, NetMos 9835))
Hi there, I tested the following versions with following results: 3.2.41-2 (bug is in there) 3.2.41-1 (bug is in there) 3.2.39-2 (bug is NOT in there) (both from http://snapshot.debian.org/binary/linux-image-3.2.0-4-amd64/) So 3.2.41-1 is the first version where the bug occurs. Good night, Sebi -- 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/201306242333.22065.sebi.ba...@gmx.de
Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"
On 24.06.2013 14:30, Gleb Natapov wrote:
> On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
>> As soon as I remove "kvmvapic.bin" the virtual machine boots with
>> qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
>> "emulate_invalid_guest_state=0" or "emulate_invalid_guest_state=1" make
>> no difference.
>>
>> Please send your patches.
> Here it is, run with it and kvmvapic.bin present. See what is printed in
> dmesg after the failure.
>
>
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index f4a5b3f..65488a4 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -3385,6 +3385,7 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
> {
> struct vcpu_vmx *vmx = to_vmx(vcpu);
> u32 ar;
> + unsigned long rip;
>
> if (vmx->rmode.vm86_active && seg != VCPU_SREG_LDTR) {
> *var = vmx->rmode.segs[seg];
> @@ -3408,6 +3409,9 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
> var->db = (ar >> 14) & 1;
> var->g = (ar >> 15) & 1;
> var->unusable = (ar >> 16) & 1;
> + rip = kvm_rip_read(vcpu);
> + if ((rip == 0xc101611c || rip == 0xc101611a) && seg == VCPU_SREG_FS)
> + printk("base=%p limit=%p selector=%x ar=%x\n", var->base,
> var->limit, var->selector, ar);
> }
>
> static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)
Booting kernel Linux 3.10-rc5 with your patch applied produces these
messages in dmesg when starting a virtual machine:
emulate_invalid_guest_state=0
[ 118.732151] base= limit= (null) selector=ffff ar=0
[ 118.732341] base= limit= (null) selector=ffff ar=0
emulate_invalid_guest_state=1
[ 196.481653] base= limit= (null) selector=ffff ar=0
[ 196.481700] base= limit= (null) selector=ffff ar=0
[ 196.481706] base= limit= (null) selector=ffff ar=0
[ 196.481711] base= limit= (null) selector=ffff ar=0
[ 196.481716] base= limit= (null) selector=ffff ar=0
[ 196.481720] base= limit= (null) selector=ffff ar=0
[ 196.481725] base= limit= (null) selector=ffff ar=0
[ 196.481730] base= limit= (null) selector=ffff ar=0
[ 196.481735] base= limit= (null) selector=ffff ar=0
[ 196.481739] base= limit= (null) selector=ffff ar=0
[ 196.481777] base= limit= (null) selector=ffff ar=0
[ 196.482068] base= limit= (null) selector=ffff ar=0
[ 196.482073] base= limit= (null) selector=ffff ar=0
[ 196.482079] base= limit= (null) selector=ffff ar=0
[ 196.482084] base= limit= (null) selector=ffff ar=0
[ 196.482131] base= limit= (null) selector=ffff ar=0
[ 196.482136] base= limit= (null) selector=ffff ar=0
[ 196.482142] base= limit= (null) selector=ffff ar=0
[ 196.482146] base= limit= (null) selector=ffff ar=0
[ 196.482193] base= limit= (null) selector=ffff ar=0
[ 196.482198] base= limit= (null) selector=ffff ar=0
[ 196.482203] base= limit= (null) selector=ffff ar=0
[ 196.482208] base= limit= (null) selector=ffff ar=0
[ 196.482255] base= limit= (null) selector=ffff ar=0
[ 196.482259] base= limit= (null) selector=ffff ar=0
[ 196.482265] base= limit= (null) selector=ffff ar=0
[ 196.482269] base= limit= (null) selector=ffff ar=0
[ 196.482316] base= limit= (null) selector=ffff ar=0
[ 196.482321] base= limit= (null) selector=ffff ar=0
[ 196.482326] base= limit= (null) selector=ffff ar=0
[ 196.482331] base= limit= (null) selector=ffff ar=0
[ 196.482378] base= limit= (null) selector=ffff ar=0
[ 196.482382] base= limit= (null) selector=ffff ar=0
[ 196.482388] base= limit= (null) selector=ffff ar=0
[ 196.482392] base= limit= (null) selector=ffff ar=0
[ 196.482439] base= limit= (null) selector=ffff ar=0
[ 196.482444] base= limit= (null) selector=ffff ar=0
[ 196.482449] base= limit= (null) selector=ffff ar=0
[ 196.482454] base= limit= (null) selector=ffff ar=0
[ 196.482501] base= limit= (null) selector=ffff ar=0
[ 196.482505] base= limit= (null) selector=ffff ar=0
[ 196.482511] base= limit= (null) selector=ffff ar=0
[ 196.482516] base= limit= (null) selector=ffff ar=0
[ 196.482562] base= limit= (null) selector=ffff ar=0
[ 196.482567] base= limit= (null) selector=ffff ar=0
[ 196.482573] base= limit= (null) selector=ffff ar=0
[ 196.482577] base= limit= (null) selector=ffff ar=0
[ 196.483137] base= limit= (null) selector=ffff ar=0
[ 196.483142] base= limit= (null) selector=ffff ar=0
[ 196.483147] base=
Re: Problem with 3.9 dvb module
2013/6/22 Ben Hutchings : > On Sat, 2013-06-22 at 18:12 +0200, Josu Lazkano wrote: >> 2013/6/22 Ben Hutchings : >> > On Sat, 2013-06-22 at 15:36 +0200, Josu Lazkano wrote: > [...] >> > The media drivers were reorganised. You'll need to update the patch. >> > >> > Ben. >> > >> > -- >> > Ben Hutchings >> > Klipstein's 4th Law of Prototyping and Production: >> > A fail-safe circuit will destroy >> > others. >> >> Hello Ben, and thanks for the reply. >> >> I try again without apply the patch and there is same error in the >> "make modules SUBDIRS=drivers/media/dvb/" command. >> >> So the patch is not the problem. Could someone reproduce this in 64bits >> jessie? > > Like I said, the media drivers were reorganised. There is no longer a > subdirectory called drivers/media/dvb. > > Why don't you ask whoever gave you this patch and canned commands in the > first place? > > Ben. > > -- > Ben Hutchings > Klipstein's 4th Law of Prototyping and Production: > A fail-safe circuit will destroy others. Thanks! It works with this: make modules SUBDIRS=drivers/media/dvb-core/ Best regards. -- Josu Lazkano -- 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/cal9g6wv6zonbuu_c3w3qgsq9l06f1oybsz20w_7qg7nssbq...@mail.gmail.com
Bug#628650: marked as done (linux-image-2.6.32-5-amd64: dd fails with ASC-1045 SAS controller and LTO-4)
Your message dated Mon, 24 Jun 2013 22:04:34 +0200 with message-id <20130624200433.GA5078@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #628650, regarding linux-image-2.6.32-5-amd64: dd fails with ASC-1045 SAS controller and LTO-4 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 628650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628650 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: normal I have a Quantum LTO-4 tape drive connected to an ASC-1045 controller. The kernel logs included do show the nature of the problem I have encountered. I am writing data to / from the tape drive using dd, like so: dd if=/dev/nst0 of=file bs=32K This causes the messages you see below. The tape drive will become unusable, and I have no choice but to do a cold boot to restore access to the device, otherwise I get "device busy" messages. I have attempted to use the "official" adaptec drivers for this card, and get the same result as when I use mvsas. I am not sure if this problem is a hardware issue (I suspect not, since sometimes things work) or a software issue. I am able to send some data to the tape drive, and read some data... the problem has been very difficult for me to narrow down. The information attached to this particular bug report comes from an attempt to use the Adaptec driver, which is not part of Debian, but identical messages are generated with the mvsas module. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 23:13:22 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-amd64 root=/dev/mapper/virtualmachines-virtualserver--root ro quiet ** Not tainted ** Kernel log: [ 482.176432] [] ? scsi_init_sgtable+0x3f/0x5a [scsi_mod] [ 482.176438] [] ? schedule_timeout+0x2e/0xdd [ 482.176443] [] ? blk_peek_request+0x18b/0x19f [ 482.176446] [] ? wait_for_common+0xde/0x15b [ 482.176453] [] ? default_wake_function+0x0/0x9 [ 482.176456] [] ? st_do_scsi+0x2c4/0x2f4 [st] [ 482.176460] [] ? st_read+0x38a/0x8cf [st] [ 482.176465] [] ? vfs_read+0xa6/0xff [ 482.176467] [] ? sys_read+0x45/0x6e [ 482.176471] [] ? system_call_fastpath+0x16/0x1b [ 602.176047] INFO: task dd:2388 blocked for more than 120 seconds. [ 602.176165] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 602.176318] ddD 88081d2bd4c0 0 2388 2387 0x [ 602.176321] 88081d2bd4c0 0086 8118314f [ 602.176325] 00800020 0fe0 f9e0 88081cb31fd8 [ 602.176328] 00015780 00015780 88081d2bdbd0 88081d2bdec8 [ 602.176331] Call Trace: [ 602.176337] [] ? blk_rq_map_sg+0x140/0x289 [ 602.176349] [] ? scsi_init_sgtable+0x3f/0x5a [scsi_mod] [ 602.176353] [] ? schedule_timeout+0x2e/0xdd [ 602.176357] [] ? blk_peek_request+0x18b/0x19f [ 602.176359] [] ? wait_for_common+0xde/0x15b [ 602.176364] [] ? default_wake_function+0x0/0x9 [ 602.176367] [] ? st_do_scsi+0x2c4/0x2f4 [st] [ 602.176371] [] ? st_read+0x38a/0x8cf [st] [ 602.176374] [] ? vfs_read+0xa6/0xff [ 602.176377] [] ? sys_read+0x45/0x6e [ 602.176380] [] ? system_call_fastpath+0x16/0x1b [ 722.176069] INFO: task dd:2388 blocked for more than 120 seconds. [ 722.176188] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 722.176341] ddD 88081d2bd4c0 0 2388 1 0x0004 [ 722.176346] 88081d2bd4c0 0086 8118314f [ 722.176349] 00800020 0fe0 f9e0 88081cb31fd8 [ 722.176352] 00015780 00015780 88081d2bdbd0 88081d2bdec8 [ 722.176355] Call Trace: [ 722.176363] [] ? blk_rq_map_sg+0x140/0x289 [ 722.176379] [] ? scsi_init_sgtable+0x3f/0x5a [scsi_mod] [ 722.176385] [] ? schedule_timeout+0x2e/0xdd [ 722.176389] [] ? blk_peek_request+0x18b/0x19f [ 722.176392] [] ? wait_for_common+0xde/0x15b [ 722.176397] [] ? default_wake_function+0x0/0x9 [ 722.176401] [] ? st_do_scsi+0x2c4/0x2f4 [st] [ 722.176404] [] ? st_read+0x38a/0x8cf [st] [ 722.176409] [] ? vfs_read+0xa6/0xff [ 722.176412] [] ? sys_read+0x45/0x6e [ 722.176415] [] ? system_call_fastpath+0x16/0x1b [ 842.176106] INFO: task dd:2388 blocked for more than 120 seconds. [ 842.176225] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this mes
Bug#628641: marked as done (linux-image-2.6.32-5-686: crashes when closing laptop lid (dell inspiron 300m))
Your message dated Mon, 24 Jun 2013 22:04:34 +0200 with message-id <20130624200433.GA5078@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #628641, regarding linux-image-2.6.32-5-686: crashes when closing laptop lid (dell inspiron 300m) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 628641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-34squeeze1 Severity: normal after upgrading the kernel, my laptop seems to crash immediately after closing the laptop screen. i've seen it happen both when running console (screen goes black and stays black) or when running X (screen freezes, but whatever content was there remains visible). previous versions (including 2.6.32-31, just confirmed) worked fine, in that closing the lid didn't really do anything. so far, it seems to be completely repeatable. live well, vagrant -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-34squeeze1) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Wed May 18 07:08:50 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/lilwalrus-rt ro keyboard=us quiet ** Not tainted ** Kernel log: [ 14.514303] nsc-ircc, chip->init [ 14.514315] nsc-ircc, Found chip at base=0x02e [ 14.514339] nsc-ircc, driver loaded (Dag Brattli) [ 14.514544] nsc_ircc_open(), can't get iobase of 0x2f8 [ 14.514571] nsc-ircc, Found chip at base=0x02e [ 14.514595] nsc-ircc, driver loaded (Dag Brattli) [ 14.514601] nsc_ircc_open(), can't get iobase of 0x2f8 [ 14.515534] nsc-ircc 00:06: disabled [ 14.614073] lib80211: common routines for IEEE802.11 drivers [ 14.614079] lib80211_crypt: registered algorithm 'NULL' [ 15.013847] [drm] Initialized drm 1.1.0 20060810 [ 15.038928] ieee80211: 802.11 data/management/control stack, git-1.1.13 [ 15.038935] ieee80211: Copyright (C) 2004-2005 Intel Corporation [ 15.240345] ipw2100: Intel(R) PRO/Wireless 2100 Network Driver, git-1.2.2 [ 15.240351] ipw2100: Copyright(c) 2003-2006 Intel Corporation [ 15.240803] ACPI: PCI Interrupt Link [LNKE] enabled at IRQ 5 [ 15.240808] PCI: setting IRQ 5 as level-triggered [ 15.240816] ipw2100 :02:04.0: PCI INT A -> Link[LNKE] -> GSI 5 (level, low) -> IRQ 5 [ 15.241488] ipw2100: Detected Intel PRO/Wireless 2100 Network Connection [ 15.241513] ipw2100 :02:04.0: firmware: requesting ipw2100-1.3.fw [ 15.795771] i915 :00:02.0: PCI INT A -> Link[LNKA] -> GSI 10 (level, low) -> IRQ 10 [ 15.795781] i915 :00:02.0: setting latency timer to 64 [ 15.801373] [drm] set up 7M of stolen space [ 15.950305] [drm] initialized overlay support [ 16.212227] yenta_cardbus :02:03.0: CardBus bridge found [1028:0150] [ 16.340844] yenta_cardbus :02:03.0: ISA IRQ mask 0x0018, PCI irq 10 [ 16.340851] yenta_cardbus :02:03.0: Socket status: 3006 [ 16.340858] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #02 to #06 [ 16.340872] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff [ 16.340878] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3000-0x3fff: clean. [ 16.341260] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge Memory window: 0xe020 - 0xe02f [ 16.341265] yenta_cardbus :02:03.0: pcmcia: parent PCI bridge Memory window: 0x4800 - 0x4fff [ 16.352161] yenta_cardbus :02:03.1: CardBus bridge found [1028:0150] [ 16.752833] yenta_cardbus :02:03.1: ISA IRQ mask 0x0018, PCI irq 10 [ 16.752839] yenta_cardbus :02:03.1: Socket status: 3006 [ 16.752845] pci_bus :02: Raising subordinate bus# of parent bus (#02) from #06 to #0a [ 16.752856] yenta_cardbus :02:03.1: pcmcia: parent PCI bridge I/O window: 0x3000 - 0x3fff [ 16.752862] pcmcia_socket pcmcia_socket1: cs: IO port probe 0x3000-0x3fff: clean. [ 16.753241] yenta_cardbus :02:03.1: pcmcia: parent PCI bridge Memory window: 0xe020 - 0xe02f [ 16.753246] yenta_cardbus :02:03.1: pcmcia: parent PCI bridge Memory window: 0x4800 - 0x4fff [ 16.932969] Console: switching to colour frame buffer device 128x48 [ 16.941850] fb0: inteldrmfb frame buffer device [ 16.941853] registered panic notifier [ 16.943520] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 16.943596] Intel ICH Modem :00:1f.6: PCI INT B -> Link[LNKB] -> GSI 10 (level, low) -> IRQ 10 [ 16.943622] Intel ICH Modem :00:1f.6: setting la
Bug#627782: marked as done (fcntl(F_SETFL, O_APPEND) has no effect on aufs filesystem)
Your message dated Mon, 24 Jun 2013 22:04:34 +0200 with message-id <20130624200433.GA5078@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #627782, regarding fcntl(F_SETFL, O_APPEND) has no effect on aufs filesystem to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 627782: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627782 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: archivemail Version: 0.8.2-1 Severity: serious Justification: fails to build from source archivemail FTBFS in unstable: | make[1]: Entering directory `/build/archivemail-GeuLuZ/archivemail-0.8.2' | ./test_archivemail | .F.F.E. | == | ERROR: testMixedExisting (__main__.TestMaildir) | -- | Traceback (most recent call last): | File "./test_archivemail", line 1437, in testMixedExisting | self.verify() | File "./test_archivemail", line 1275, in verify | self._verify_archive() | File "./test_archivemail", line 1327, in _verify_archive | assertEqualContent(archive, self.orig_archive, iszipped) | File "./test_archivemail", line 1726, in assertEqualContent | assert cmp_fileobj(fp1, fp2) | File "./test_archivemail", line 1737, in cmp_fileobj | b1 = fp1.read(bufsize) | File "/usr/lib/python2.6/gzip.py", line 219, in read | self._read(readsize) | File "/usr/lib/python2.6/gzip.py", line 267, in _read | self._read_eof() | File "/usr/lib/python2.6/gzip.py", line 304, in _read_eof | hex(self.crc))) | IOError: CRC check failed 0x1a15fced != 0xe10d79e9L | | == | FAIL: archiving an old mailbox with an existing archive | -- | Traceback (most recent call last): | File "./test_archivemail", line 790, in testOldExisting | self.verify() | File "./test_archivemail", line 663, in verify | assertEqualContent(archive_name, self.good_archive, iszipped) | File "./test_archivemail", line 1726, in assertEqualContent | assert cmp_fileobj(fp1, fp2) | AssertionError | | == | FAIL: archiving an old mailbox uncopressed with an existing archive | -- | Traceback (most recent call last): | File "./test_archivemail", line 1203, in testOldExists | self.verify() | File "./test_archivemail", line 663, in verify | assertEqualContent(archive_name, self.good_archive, iszipped) | File "./test_archivemail", line 1731, in assertEqualContent | assert filecmp.cmp(firstfile, secondfile, shallow=0) | AssertionError | | -- | Ran 95 tests in 6.602s | | FAILED (failures=2, errors=1) -- Jakub Wilk --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#628750: marked as done (udev: takes too long to detect and configure mouse (steelseries XAI))
Your message dated Mon, 24 Jun 2013 22:04:34 +0200 with message-id <20130624200433.GA5078@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #628750, regarding udev: takes too long to detect and configure mouse (steelseries XAI) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 628750: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628750 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: udev Version: 169-1 Severity: normal Udev is taking around 15 secs to detect and configure my mouse. If you take a look at my bootchart, you see a big hole: http://i.imgur.com/whbA8.png . That hole is caused by udev trying to figure out my Steelseries XAI mouse. This ( http://imgur.com/7tSVP.png ) is the same bootchart with the mouse unplugged. You can see that when I plug it, a modprobe runs and takes about 15 seconds. I don't see any weird module loaded for the mouse afterwards (hid, usbhid and that's it), so the modprobe is pointless (?). Here's the dmesg output (at loglevel 9) after booting my PC without the mouse and pluggin it in: [ 30.892447] SysRq : Changing Loglevel [ 30.896441] Loglevel set to 9 [ 42.700013] usb 5-1: new full speed USB device number 2 using uhci_hcd [ 42.877032] usb 5-1: New USB device found, idVendor=1038, idProduct=1360 [ 42.886016] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=2 [ 42.894967] usb 5-1: Product: SteelSeries Gaming Device [ 42.903794] usb 5-1: Manufacturer: Ruling Technologies Sdn. Bhd. [ 42.912457] usb 5-1: SerialNumber: SteelSeries Gaming Device [ 48.032209] input: Ruling Technologies Sdn. Bhd. SteelSeries Gaming Device as /devices/pci:00/:00:1d.3/usb5/5-1/5-1:1.0/input/input4 [ 48.051405] generic-usb 0003:1038:1360.0001: input,hidraw0: USB HID v1.00 Mouse [Ruling Technologies Sdn. Bhd. SteelSeries Gaming Device] on usb-:00:1d.3-1/input0 [ 53.080105] input: Ruling Technologies Sdn. Bhd. SteelSeries Gaming Device as /devices/pci:00/:00:1d.3/usb5/5-1/5-1:1.1/input/input5 [ 53.100631] generic-usb 0003:1038:1360.0002: input,hidraw1: USB HID v1.00 Keyboard [Ruling Technologies Sdn. Bhd. SteelSeries Gaming Device] on usb-:00:1d.3-1/input1 [ 58.131964] generic-usb 0003:1038:1360.0003: hiddev0,hidraw2: USB HID v1.00 Device [Ruling Technologies Sdn. Bhd. SteelSeries Gaming Device] on usb-:00:1d.3-1/input2 [ 58.154898] usbcore: registered new interface driver usbhid [ 58.166373] usbhid: USB HID core driver Why would there be a 5 sec delay between detecting the device and loading it as a mouse? And then another delay on detecting the hidden devices? For comparison, this is a fresh boot, pluggin in a logitech mouse: [ 24.677331] Loglevel set to 9 [ 31.476010] usb 5-1: new low speed USB device number 2 using uhci_hcd [ 31.661033] usb 5-1: New USB device found, idVendor=046d, idProduct=c03e [ 31.669925] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 31.678864] usb 5-1: Product: USB-PS/2 Optical Mouse [ 31.687670] usb 5-1: Manufacturer: Logitech [ 31.802224] input: Logitech USB-PS/2 Optical Mouse as /devices/pci:00/:00:1d.3/usb5/5-1/5-1:1.0/input/input4 [ 31.811264] generic-usb 0003:046D:C03E.0001: input,hidraw0: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-:00:1d.3-1/input0 [ 31.829507] usbcore: registered new interface driver usbhid [ 31.837730] usbhid: USB HID core driver It's almost instantaneous... On that same boot, I unplugged that mouse, and plugged the XAI. Again, 5 secs delay between the plugin and input doing something. [ 56.696033] usb 5-1: USB disconnect, device number 2 [ 84.952014] usb 5-1: new full speed USB device number 3 using uhci_hcd [ 85.129031] usb 5-1: New USB device found, idVendor=1038, idProduct=1360 [ 85.139476] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=2 [ 85.149869] usb 5-1: Product: SteelSeries Gaming Device [ 85.160199] usb 5-1: Manufacturer: Ruling Technologies Sdn. Bhd. [ 85.170529] usb 5-1: SerialNumber: SteelSeries Gaming Device [ 90.192203] input: Ruling Technologies Sdn. Bhd. SteelSeries Gaming Device as /devices/pci:00/:00:1d.3/usb5/5-1/5-1:1.0/input/input5 [ 90.213819] generic-usb 0003:1038:1360.0002: input,hidraw0: USB HID v1.00 Mouse [Ruling Technologies Sdn. Bhd. SteelSeries Gaming Device] on usb-:00:1d.3-1/input0 [ 95.240128] input: Ruling Technologies Sdn. Bhd. SteelSeries Gaming Device as /devices/pci:00/:00:1d.3/usb5/5-1/5-1:1.1/input/input6 [ 95.262370] generic-usb 0003:10
Bug#628085: marked as done (Sound stuck after resuming from hibernation: SNDRV_PCM_IOCTL_RESUME failed (-38): Function not implemented)
Your message dated Mon, 24 Jun 2013 22:04:34 +0200 with message-id <20130624200433.GA5078@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #628085, regarding Sound stuck after resuming from hibernation: SNDRV_PCM_IOCTL_RESUME failed (-38): Function not implemented to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 628085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628085 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.39-1+b1 Severity: normal My laptop hibernated while playing a video, and on resume the sound got stuck (rapidly repeating a fraction of a second) until I closed the video. mplayer and ALSA said: [AO_ALSA] Pcm in suspend mode, trying to resume. [AO_ALSA] alsa-lib: pcm_hw.c:709:(snd_pcm_hw_resume) SNDRV_PCM_IOCTL_RESUME failed (-38): Function not implemented My audio device, copied from the information below for convenience: 00:1b.0 Audio device [0403]: Intel Corporation 6 Series Chipset Family High Definition Audio Controller [8086:1c20] (rev 04) - Josh Triplett -- Package-specific info: ** Version: Linux version 2.6.39-1-amd64 (Debian 2.6.39-1) (buildd_amd64-bra...@buildd.debian.org) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Tue May 24 14:34:19 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.39-1-amd64 root=/dev/mapper/leaf-root ro quiet ** Not tainted ** Kernel log: [116299.361165] PM: Saving platform NVS memory [116299.372093] Disabling non-boot CPUs ... [116299.374401] CPU 1 is now offline [116299.536918] CPU 2 is now offline [116299.660752] CPU 3 is now offline [116299.661508] Extended CMOS year: 2000 [116299.661623] PM: Creating hibernation image: [116299.867238] PM: Need to copy 161100 pages [116299.867244] PM: Normal pages needed: 161100 + 1024, available pages: 858510 [116299.661643] PM: Restoring platform NVS memory [116299.662536] Extended CMOS year: 2000 [116299.662560] Enabling non-boot CPUs ... [116299.662666] Booting Node 0 Processor 1 APIC 0x1 [116299.662668] smpboot cpu 1: start_ip = 98000 [116299.769913] NMI watchdog enabled, takes one hw-pmu counter. [116299.773616] Switched to NOHz mode on CPU #1 [116299.881528] CPU1 is up [116299.881891] Booting Node 0 Processor 2 APIC 0x2 [116299.881898] smpboot cpu 2: start_ip = 98000 [116299.989649] NMI watchdog enabled, takes one hw-pmu counter. [116299.993336] Switched to NOHz mode on CPU #2 [116300.045342] CPU2 is up [116300.045702] Booting Node 0 Processor 3 APIC 0x3 [116300.045708] smpboot cpu 3: start_ip = 98000 [116300.157539] NMI watchdog enabled, takes one hw-pmu counter. [116300.161123] Switched to NOHz mode on CPU #3 [116300.213146] CPU3 is up [116300.220191] ACPI: Waking up from system sleep state S4 [116300.484838] ACPI: \_SB_.PCI0.LPC_.EC__.BAT1 - docking [116300.500765] ACPI: Unable to dock! [116300.576776] i915 :00:02.0: restoring config space at offset 0x1 (was 0x97, writing 0x900407) [116300.592606] e1000e :00:19.0: BAR 0: set to [mem 0xd260-0xd261] (PCI address [0xd260-0xd261]) [116300.592622] e1000e :00:19.0: BAR 1: set to [mem 0xd262b000-0xd262bfff] (PCI address [0xd262b000-0xd262bfff]) [116300.592637] e1000e :00:19.0: BAR 2: set to [io 0x5080-0x509f] (PCI address [0x5080-0x509f]) [116300.592670] e1000e :00:19.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [116300.592715] e1000e :00:19.0: restoring config space at offset 0x1 (was 0x10, writing 0x17) [116300.592837] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [116300.592849] ehci_hcd :00:1a.0: power state changed by ACPI to D0 [116300.592922] HDA Intel :00:1b.0: restoring config space at offset 0x1 (was 0x16, writing 0x12) [116300.593508] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [116300.593519] ehci_hcd :00:1d.0: power state changed by ACPI to D0 [116300.593659] ahci :00:1f.2: restoring config space at offset 0x1 (was 0x2b00403, writing 0x2b00407) [116300.608584] sdhci-pci :0d:00.0: BAR 0: set to [mem 0xd150-0xd15000ff] (PCI address [0xd150-0xd15000ff]) [116300.608670] sdhci-pci :0d:00.0: restoring config space at offset 0x3 (was 0x800010, writing 0x10) [116300.608688] sdhci-pci :0d:00.0: restoring config space at offset 0x1 (was 0x12, writing 0x16) [116300.609018] PM: early restore of devices complete after 32.390 msecs [116300.789669] i915 :00:02.0: setting latency timer to 64 [116300.789681] ehci_hcd :00:1a.0: setting latency timer to 64 [116300.789692] e1000e :00:19.0: wake-up capabi
Bug#627933: marked as done (Regression: hot plugging sdhc card on Acer Aspire One)
Your message dated Mon, 24 Jun 2013 22:04:34 +0200 with message-id <20130624200433.GA5078@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #627933, regarding Regression: hot plugging sdhc card on Acer Aspire One to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 627933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.38-5 Severity: normal The Acer Aspire One netbook has two card readers, left & right. Until recently (sorry not sure when regression happened) hotplugging the right hand card worked. But now such a card is only seen on cold boot. I am reporting on a system which has just booted with the card present, and all is well: $ ls -l /dev/disk/by-label/ total 0 lrwxrwxrwx 1 root root 15 May 25 16:22 ael_elf1 -> ../../mmcblk0p1 lrwxrwxrwx 1 root root 15 May 25 16:22 ael_elf2 -> ../../mmcblk1p1 lrwxrwxrwx 1 root root 10 May 25 16:22 Elf_ST_ssd -> ../../sda1 The rh card above is "ael_elf1" and /dev/mmcblkop1. Relevant extracts from /var/log/messages seem to be:- == May 25 16:22:32 elf kernel: [2.913360] sdhci: Secure Digital Host Controller Interface driver May 25 16:22:32 elf kernel: [2.913464] sdhci: Copyright(c) Pierre Ossman May 25 16:22:32 elf kernel: [2.934644] sdhci-pci :01:00.0: SDHCI control ler found [197b:2382] (rev 0) May 25 16:22:32 elf kernel: [2.934800] sdhci-pci :01:00.0: enabling devi ce ( -> 0002) May 25 16:22:32 elf kernel: [2.934918] sdhci-pci :01:00.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 25 16:22:32 elf kernel: [2.935266] mmc0: no vmmc regulator found May 25 16:22:32 elf kernel: [2.936396] mmc0: SDHCI controller on PCI [:01:00.0] using ADMA May 25 16:22:32 elf kernel: [2.936545] sdhci-pci :01:00.2: SDHCI controller found [197b:2381] (rev 0) May 25 16:22:32 elf kernel: [2.936689] sdhci-pci :01:00.2: enabling device ( -> 0002) May 25 16:22:32 elf kernel: [2.936805] sdhci-pci :01:00.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 May 25 16:22:32 elf kernel: [2.936939] sdhci-pci :01:00.2: Refusing to bind to secondary interface. May 25 16:22:32 elf kernel: [2.937048] sdhci-pci :01:00.2: PCI INT A disabled May 25 16:22:32 elf kernel: [2.937188] sdhci-pci :04:00.0: SDHCI controller found [197b:2382] (rev 0) May 25 16:22:32 elf kernel: [2.937336] sdhci-pci :04:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19 May 25 16:22:32 elf kernel: [2.937624] mmc1: no vmmc regulator found May 25 16:22:32 elf kernel: [2.938505] mmc1: SDHCI controller on PCI [:04:00.0] using ADMA May 25 16:22:32 elf kernel: [2.938644] sdhci-pci :04:00.2: SDHCI controller found [197b:2381] (rev 0) May 25 16:22:32 elf kernel: [2.938797] sdhci-pci :04:00.2: PCI INT A -> GSI 19 (level, low) -> IRQ 19 May 25 16:22:32 elf kernel: [2.938937] sdhci-pci :04:00.2: Refusing to bind to secondary interface. May 25 16:22:32 elf kernel: [2.939046] sdhci-pci :04:00.2: PCI INT A disabled -- May 25 16:22:32 elf kernel: [4.289286] mmc0: new SDHC card at address 0007 <=== The target card ***RH slot* May 25 16:22:32 elf kernel: [4.317047] mmcblk0: mmc0:0007 SD16G 15.0 GiB May 25 16:22:32 elf kernel: [4.321947] mmcblk0: p1 May 25 16:22:32 elf kernel: [4.531611] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) May 25 16:22:32 elf kernel: [4.883331] mmc1: new SDHC card at address 0003 < left hand slot May 25 16:22:32 elf kernel: [4.883989] mmcblk1: mmc1:0003 SD32G 30.0 GiB May 25 16:22:32 elf kernel: [4.885868] mmcblk1: p1 May 25 16:22:32 elf kernel: [5.228510] <30>udev[315]: starting version 167 -- May 25 16:22:32 elf kernel: [9.838195] pci_hotplug: PCI Hot Plug PCI Core ve rsion: 0.5 May 25 16:22:32 elf kernel: [9.862304] pciehp: PCI Express Hot Plug Controll er Driver version: 0.4 May 25 16:22:32 elf kernel: [ 10.526330] EXT4-fs (mmcblk1p1): mounted filesystem without journal. Opts: (null) -- May 25 16:28:01 elf kernel: [ 343.594266] EXT4-fs (mmcblk1p1): re-mounted. Opts: commit=0 [ Comment: notice that LH card looks like a hotplug remount, but nothing similar for the target RH card. Consistent with problem hotplug? ] = In /etc/modprobe.d/aspire-rhs-sd_slot.conf :- #options pciehp pciehp_force
Bug#627612: marked as done (linux-image-2.6.39-1-686-pae: Kernel boots but syslog contains references to kernel null pointer)
Your message dated Mon, 24 Jun 2013 22:04:34 +0200 with message-id <20130624200433.GA5078@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #627612, regarding linux-image-2.6.39-1-686-pae: Kernel boots but syslog contains references to kernel null pointer to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 627612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627612 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.39-1 Severity: normal Tags: sid Kernel eventually boots...and **seems** to operate normally but I found this in syslog. May 22 12:25:21 sid kernel: [5.626206] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 May 22 12:25:21 sid kernel: [5.626215] ACPI: Power Button [PWRF] May 22 12:25:21 sid kernel: [5.684298] ACPI: acpi_idle registered with cpuidle May 22 12:25:21 sid kernel: [5.698554] BUG: unable to handle kernel NULL pointer dereference at (null) May 22 12:25:21 sid kernel: [5.698680] IP: [< (null)>] (null) May 22 12:25:21 sid kernel: [5.698762] *pdpt = 3734f001 *pde = May 22 12:25:21 sid kernel: [5.698863] Oops: [#1] SMP May 22 12:25:21 sid kernel: [5.698959] last sysfs file: /sys/devices/pci:00/:00:1d.7/usb1/idProduct May 22 12:25:21 sid kernel: [5.699003] Modules linked in: processor video thermal_sys button ext3 jbd mbcache usb_storage uas sg sr_mod sd_mod cdrom crc_t10dif ata_generic ata_piix uhci_hcd libata ehci_hcd scsi_mod usbcore e100 mii [last unloaded: scsi_wait_scan] May 22 12:25:21 sid kernel: [5.699813] May 22 12:25:21 sid kernel: [5.699849] Pid: 318, comm: usb_id Not tainted 2.6.39-1-686-pae #1 /D865GBF May 22 12:25:21 sid kernel: [5.699987] EIP: 0060:[<>] EFLAGS: CPU: 0 May 22 12:25:21 sid kernel: [5.700014] EIP is at 0x0 May 22 12:25:21 sid kernel: [5.700014] EAX: EBX: 03a9 ECX: f719c0d9 EDX: May 22 12:25:21 sid kernel: [5.700014] ESI: 03a9 EDI: EBP: c1158635 ESP: f72dfce8 May 22 12:25:21 sid kernel: [5.700014] DS: fd06 ES: 007b FS: c884 GS: 00e0 SS: 0068 May 22 12:25:21 sid kernel: [5.700014] Process usb_id (pid: 318, ti=f72de000 task=f5bd7b00 task.ti=f73e8000) May 22 12:25:21 sid kernel: [5.700014] Stack: May 22 12:25:21 sid kernel: [5.700014] 158c f582e400 c1011cbf f63071c0 03a3 0803c000 1306 0002 May 22 12:25:21 sid kernel: [5.700014] f6302198 f6302298 c1012716 f6302198 f6308f4c c10125fb May 22 12:25:21 sid kernel: [5.700014] 0001 f6308f7c f6308f4c f63042b0 0001 May 22 12:25:21 sid kernel: [5.700014] Call Trace: May 22 12:25:21 sid kernel: [5.700014] [] ? p4_pmu_enable_event+0x102/0x10b May 22 12:25:21 sid kernel: [5.700014] [] ? p4_pmu_enable_all+0x2a/0x37 May 22 12:25:21 sid kernel: [5.700014] [] ? x86_pmu_enable+0x1d1/0x243 May 22 12:25:21 sid kernel: [5.700014] [] ? hrtimer_forward+0x10f/0x123 May 22 12:25:21 sid kernel: [5.700014] [] ? timekeeping_get_ns+0x11/0x4f May 22 12:25:21 sid kernel: [5.700014] [] ? lapic_next_event+0x13/0x16 May 22 12:25:21 sid kernel: [5.700014] [] ? clockevents_program_event+0xd2/0xe4 May 22 12:25:21 sid kernel: [5.700014] [] ? tick_dev_program_event+0x1e/0xfc May 22 12:25:21 sid kernel: [5.700014] [] ? tick_program_event+0x14/0x17 May 22 12:25:21 sid kernel: [5.700014] [] ? hrtimer_interrupt+0x16c/0x236 May 22 12:25:21 sid kernel: [5.700014] [] ? irq_exit+0x56/0x79 May 22 12:25:21 sid kernel: [5.700014] [] ? smp_apic_timer_interrupt+0x6b/0x75 May 22 12:25:21 sid kernel: [5.700014] [] ? apic_timer_interrupt+0x31/0x38 May 22 12:25:21 sid kernel: [5.700014] [] ? generic_exec_single+0x58/0x65 May 22 12:25:21 sid kernel: [5.700014] [] ? leave_mm+0x29/0x29 May 22 12:25:21 sid kernel: [5.700014] [] ? smp_call_function_single+0xd1/0xe2 May 22 12:25:21 sid kernel: [5.700014] [] ? leave_mm+0x29/0x29 May 22 12:25:21 sid kernel: [5.700014] [] ? leave_mm+0x29/0x29 May 22 12:25:21 sid kernel: [5.700014] [] ? 0xf8379fff May 22 12:25:21 sid kernel: [5.700014] [] ? smp_call_function+0x17/0x1b May 22 12:25:21 sid kernel: [5.700014] [] ? on_each_cpu+0xd/0x30 May 22 12:25:21 sid kernel: [5.700014] [] ? 0xf8379fff May 22 12:25:21 sid kernel: [5.700014] [] ? kmap_flush_unused+0xf/0x16 May 22 12:25:21 sid kernel: [5.700014] [] ? change_page_attr_set_clr+0xf7/0x338 May 22
Bug#628028: marked as done (linux-image-2.6.32-5-amd64: Kernel hang in radeon module)
Your message dated Mon, 24 Jun 2013 22:04:34 +0200 with message-id <20130624200433.GA5078@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #628028, regarding linux-image-2.6.32-5-amd64: Kernel hang in radeon module to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 628028: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=628028 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-30 Severity: normal Once in a while, about once or twice a week, my X server freezes. No predictable pattern; nothing in particular that could seem to trigger the freeze. I can ssh into the machine, but can't kill X or even reboot because the radeon module is stuck. >From dmesg: [16054.367022] INFO: task events/1:28 blocked for more than 120 seconds. [16054.367027] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [16054.367031] events/1 D 880008c4fb30 028 2 0x [16054.367038] 88021f06b880 0046 88021f14bcc0 88021f14bcbc [16054.367044] 0001 f9e0 88021f14bfd8 [16054.367050] 00015780 00015780 88021f128710 88021f128a08 [16054.367056] Call Trace: [16054.367087] [] ? radeon_ttm_bo_destroy+0x0/0x94 [radeon] [16054.367098] [] ? ttm_bo_wait_unreserved+0x102/0x11c [ttm] [16054.367104] [] ? autoremove_wake_function+0x0/0x2e [16054.367113] [] ? ttm_bo_reserve_locked+0x71/0xbc [ttm] [16054.367120] [] ? ttm_bo_cleanup_refs+0xe4/0x248 [ttm] [16054.367123] [] ? ttm_bo_delayed_delete+0x88/0xf8 [ttm] [16054.367126] [] ? ttm_bo_delayed_workqueue+0x12/0x26 [ttm] [16054.367128] [] ? worker_thread+0x188/0x21d [16054.367131] [] ? ttm_bo_delayed_workqueue+0x0/0x26 [ttm] [16054.367132] [] ? autoremove_wake_function+0x0/0x2e [16054.367134] [] ? worker_thread+0x0/0x21d [16054.367136] [] ? kthread+0x79/0x81 [16054.367138] [] ? child_rip+0xa/0x20 [16054.367140] [] ? kthread+0x0/0x81 [16054.367142] [] ? child_rip+0x0/0x20 After this happens, various processes fail: May 26 15:18:26 xman kernel: [179933.009523] INFO: task Xorg:1472 blocked for more than 120 seconds. May 26 15:18:26 xman kernel: [179933.009524] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. May 26 15:18:26 xman kernel: [179933.009525] Xorg D 0 1472 1461 0x0044 May 26 15:18:26 xman kernel: [179933.009527] 88021f0c0e20 0086 81017759 May 26 15:18:26 xman kernel: [179933.009529] 880008d0fa98 f9e0 88021e2bdfd8 May 26 15:18:26 xman kernel: [179933.009531] 00015780 00015780 88021b631530 88021b631828 May 26 15:18:26 xman kernel: [179933.009533] Call Trace: May 26 15:18:26 xman kernel: [179933.009536] [] ? __switch_to_xtra+0x13e/0x19a May 26 15:18:26 xman kernel: [179933.009539] [] ? __switch_to+0x285/0x297 May 26 15:18:26 xman kernel: [179933.009542] [] ? schedule_timeout+0x2e/0xdd May 26 15:18:26 xman kernel: [179933.009545] [] ? finish_task_switch+0x3a/0xaf May 26 15:18:26 xman kernel: [179933.009546] [] ? thread_return+0x79/0xe0 May 26 15:18:26 xman kernel: [179933.009548] [] ? wait_for_common+0xde/0x15b May 26 15:18:26 xman kernel: [179933.009550] [] ? default_wake_function+0x0/0x9 May 26 15:18:26 xman kernel: [179933.009552] [] ? flush_work+0x75/0x87 May 26 15:18:26 xman kernel: [179933.009554] [] ? wq_barrier_func+0x0/0x9 May 26 15:18:26 xman kernel: [179933.009557] [] ? n_tty_poll+0x5e/0x138 May 26 15:18:26 xman kernel: [179933.009558] [] ? tty_poll+0x56/0x6d May 26 15:18:26 xman kernel: [179933.009561] [] ? do_select+0x37b/0x57a May 26 15:18:26 xman kernel: [179933.009563] [] ? __pollwait+0x0/0xd6 May 26 15:18:26 xman kernel: [179933.009565] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009567] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009568] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009570] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009572] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009573] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009575] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009576] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009578] [] ? pollwake+0x0/0x5b May 26 15:18:26 xman kernel: [179933.009580] [] ? core_sys_select+0x184/0x21e May 26 15:18:26 xman kernel: [179933.009583] [] ? __remo
Bug#704242: Driver for PL-2303 HX not working
On Mon, Jun 24, 2013 at 12:38:17PM -0400, Aric Fedida wrote: > I will gladly ship you one. Give me address details, and I'll go to > the post office to send it. I'll send it off-list, thanks. > Personally, I have resolved to abandon the PL2303 chip, and move to > FTDI instead. But for the sake of other Linux users who might buy that > adapter by mistake, I am willing to donate the hardware to an able > kernel hacker :-) Yes, I recommend the ftdi devices as well, the specs are availble, and the driver seems to work better because of it. thanks, greg k-h -- 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/20130624190056.ga23...@kroah.com
Bug#704242: Fwd: Re: Bug#704242: Driver for PL-2303 HX not working
On Mon, Jun 24, 2013 at 08:37:59PM +0200, Karsten Malcher wrote: > Am 24.06.2013 20:18, schrieb Greg KH: > >On Mon, Jun 24, 2013 at 06:41:38PM +0200, Karsten Malcher wrote: > >>Hello Greg, > >> > >>Am 24.06.2013 18:17, schrieb Greg KH: > >>>On Mon, Jun 24, 2013 at 10:41:07AM +0200, Karsten Malcher wrote: > Hello Greg, > > have you buyed one of this jinxed PL-2303 HX adapters? > >>>No, I have not been able to find one. Does anyone know where I can > >>>purchase one? > >>Just take this one: > >>http://www.ebay.com/itm/USB-To-RS232-TTL-PL2303HX-Auto-Converter-Module-5V-3-3V-Output-Converter-Adapter-/370812126675 > >>US $1.67 and it is yours. > >But wiring that up to a "real" 9pin serial port would be a pain (doable, > >but a pain). Is there any devices out there with a DB-9 output > >connector? > > You mean if you want to test full handshake with all signals - that's true. Which is what the driver needs to test, right? And of course, everone with this problem is properly hooking up these signals, right? Otherwise, there will be problems as the pins could float and cause transmissions / receive data to stop happening. At the least, loop-back testing is important. > The advantage of the adapter is to get directly 5V and 3,3V. What do you mean by this? > I don't know some other adapter with exactly this chip, because i don't need > them. > Only this Adapter which use the other chip ch341-uart which works without > problems > http://www.ebay.com/itm/USB-to-RS232-Serial-9-Pin-DB9-Adapter-PC-PDA-RS-232-/180399132966 > > When i think about it i never seen that someone uses the handshake for this > simple serial communication. > Not in communication with mobiles, ARM-boards or AVR microcontroller. > The built-in UART's in the ARM and AVR don't suffer handshake > signals, so that you must do it by software with additional IO > ports. What's wrong with software flow control? Why reinvent something that has been successfully used for 30+ years? thanks, greg k-h -- 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/20130624185627.ga23...@kroah.com
Re: gcc 4.8
On Mon, Jun 24, 2013 at 07:27:24PM +0200, Bastian Blank wrote: > Hi > > I did a first build of Linux 3.9 with gcc 4.8. It works fine on s390x, > however I found a weird not longer reproducible bug in s390. I think > about using it as default pretty fast for all architectures. I think Arnaud said it was generating unbootable kernels for some ARM configurations. I don't remember any details, though. 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/20130624185523.gd4...@decadent.org.uk
Bug#704242: Fwd: Re: Bug#704242: Driver for PL-2303 HX not working
Am 24.06.2013 20:18, schrieb Greg KH: On Mon, Jun 24, 2013 at 06:41:38PM +0200, Karsten Malcher wrote: Hello Greg, Am 24.06.2013 18:17, schrieb Greg KH: On Mon, Jun 24, 2013 at 10:41:07AM +0200, Karsten Malcher wrote: Hello Greg, have you buyed one of this jinxed PL-2303 HX adapters? No, I have not been able to find one. Does anyone know where I can purchase one? Just take this one: http://www.ebay.com/itm/USB-To-RS232-TTL-PL2303HX-Auto-Converter-Module-5V-3-3V-Output-Converter-Adapter-/370812126675 US $1.67 and it is yours. But wiring that up to a "real" 9pin serial port would be a pain (doable, but a pain). Is there any devices out there with a DB-9 output connector? You mean if you want to test full handshake with all signals - that's true. The advantage of the adapter is to get directly 5V and 3,3V. I don't know some other adapter with exactly this chip, because i don't need them. Only this Adapter which use the other chip ch341-uart which works without problems http://www.ebay.com/itm/USB-to-RS232-Serial-9-Pin-DB9-Adapter-PC-PDA-RS-232-/180399132966 When i think about it i never seen that someone uses the handshake for this simple serial communication. Not in communication with mobiles, ARM-boards or AVR microcontroller. The built-in UART's in the ARM and AVR don't suffer handshake signals, so that you must do it by software with additional IO ports. thanks, greg k-h Cheers Karsten -- 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/51c89207.5090...@dct.mine.nu
Bug#704242: Fwd: Re: Bug#704242: Driver for PL-2303 HX not working
On Mon, Jun 24, 2013 at 06:41:38PM +0200, Karsten Malcher wrote: > Hello Greg, > > Am 24.06.2013 18:17, schrieb Greg KH: > >On Mon, Jun 24, 2013 at 10:41:07AM +0200, Karsten Malcher wrote: > >>Hello Greg, > >> > >>have you buyed one of this jinxed PL-2303 HX adapters? > >No, I have not been able to find one. Does anyone know where I can > >purchase one? > > Just take this one: > http://www.ebay.com/itm/USB-To-RS232-TTL-PL2303HX-Auto-Converter-Module-5V-3-3V-Output-Converter-Adapter-/370812126675 > US $1.67 and it is yours. But wiring that up to a "real" 9pin serial port would be a pain (doable, but a pain). Is there any devices out there with a DB-9 output connector? thanks, greg k-h -- 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/20130624181821.gb8...@kroah.com
Bug#626701: marked as done (Kernel Panic in linux-image-2.6.38-2-sparc64)
Your message dated Mon, 24 Jun 2013 20:11:15 +0200 with message-id <20130624181115.GB19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #626701, regarding Kernel Panic in linux-image-2.6.38-2-sparc64 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 626701: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626701 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.38-2-sparc64 Version: 2.6.38-3 Random Kernel Panic occurring during boot or within 20-30 minutes. scsi target0:0:6: Ending Domain Validation [ 87.834460] kernel BUG at /build/buildd-linux-2.6_2.6.38-3-sparc-675DHN/linux-2.6-2.6.38/debian/build/source_sparc_none/drivers/scsi/esp_scsi.c:583! [ 87.991947] \|/ \|/ [ 87.991966] "@'/ .. \`@" [ 87.991984] /_| \__/ |_\ [ 87.992002] \__U_/ [ 88.167876] kworker/u:0(5): Kernel bad sw trap 5 [#1] [ 88.228308] TSTATE: 004480e01606 TPC: 100e4998 TNPC: 100e499c Y: Not tainted [ 88.346055] TPC: [ 88.409520] g0: 0004 g1: 0087a400 g2: 0087a448 g3: 008ad1a8 [ 88.513707] g4: f80003851600 g5: 0028 g6: f80003878000 g7: [ 88.617855] o0: 009b o1: 100e82e0 o2: 0247 o3: 0400 [ 88.722011] o4: f8000387bb94 o5: sp: f80013f132f1 ret_pc: 100e4990 [ 88.830341] RPC: [ 88.893829] l0: l1: 00814df1 l2: 0020 l3: 0025 [ 88.998009] l4: 0004 l5: 0077e8f8 l6: 005b2ab0 l7: 005b2a80 [ 89.102165] i0: f800115ff860 i1: f80011659000 i2: 000c i3: 0003 [ 89.206314] i4: 0002 i5: f8000387bb97 i6: f80013f133a1 i7: 100e5ec0 [ 89.310481] I7: [ 89.372909] Call Trace: [ 89.402097] [100e5ec0] esp_cmd_is_done+0x44/0x178 [esp_scsi] [ 89.479177] [100e6ddc] esp_process_event+0x97c/0x1490 [esp_scsi] [ 89.560415] [100e819c] scsi_esp_intr+0x8ac/0x9a8 [esp_scsi] [ 89.636464] [004a036c] handle_IRQ_event+0x7c/0x178 [ 89.703091] [004a249c] handle_fasteoi_irq+0x94/0xe4 [ 89.770798] [00429f70] handler_irq+0xb0/0xe8 [ 89.831198] [004208b4] tl0_irq5+0x14/0x20 [ 89.888484] [0045b600] vprintk+0xb8/0x3a0 [ 89.945760] [007581ec] printk+0x24/0x38 [ 90.000955] [00640a2c] dev_printk+0x2c/0x40 [ 90.060392] [101269ec] sd_revalidate_disk+0x944/0x1ae0 [sd_mod] [ 90.140564] [10128840] sd_probe_async+0xa4/0x1ac [sd_mod] [ 90.214479] [0047bc94] async_run_entry_fn+0xa8/0x174 [ 90.283224] [00471d5c] process_one_work+0x2a0/0x408 [ 90.350919] [004720c8] worker_thread+0x204/0x414 [ 90.415486] [00475910] kthread+0x5c/0x70 [ 90.471707] Disabling lock debugging due to kernel taint [ 90.535276] Caller[100e5ec0]: esp_cmd_is_done+0x44/0x178 [esp_scsi] [ 90.618595] Caller[100e6ddc]: esp_process_event+0x97c/0x1490 [esp_scsi] [ 90.706109] Caller[100e819c]: scsi_esp_intr+0x8ac/0x9a8 [esp_scsi] [ 90.788362] Caller[004a036c]: handle_IRQ_event+0x7c/0x178 [ 90.861253] Caller[004a249c]: handle_fasteoi_irq+0x94/0xe4 [ 90.935202] Caller[00429f70]: handler_irq+0xb0/0xe8 [ 91.001858] Caller[004208b4]: tl0_irq5+0x14/0x20 [ 91.065393] Caller[005b54ec]: vsnprintf+0x198/0x2fc [ 91.132043] Caller[007581ec]: printk+0x24/0x38 [ 91.193494] Caller[00640a2c]: dev_printk+0x2c/0x40 [ 91.259149] Caller[101269ec]: sd_revalidate_disk+0x944/0x1ae0 [sd_mod] [ 91.345621] Caller[10128840]: sd_probe_async+0xa4/0x1ac [sd_mod] [ 91.425756] Caller[0047bc94]: async_run_entry_fn+0xa8/0x174 [ 91.500748] Caller[00471d5c]: process_one_work+0x2a0/0x408 [ 91.574696] Caller[004720c8]: worker_thread+0x204/0x414 [ 91.645515] Caller[00475910]: kthread+0x5c/0x70 [ 91.708004] Caller[0042ac1c]: kernel_thread+0x30/0x48 [ 91.776742] Caller[00475878]: kthreadd+0xa4/0xe0 [ 91.840251] Instruction DUMP: 110403a0 7c0d1342 901222e0 <91d02005> 9de3bf50 c25e2098 c4006008 80a0a000 22480007 [ 91.969393] Kernel panic - not syncing: Aiee, killing interrupt handler! [ 92.049608] Call Trace: [ 92.078779] [0045dda8] do_exit+0x64/0x6b4 [ 92.136064] [00427a50] die_if_kernel+
Bug#627151: marked as done (linux-image-2.6.38-2-686: Dell latitude E5400 freezes during X session)
Your message dated Mon, 24 Jun 2013 20:11:15 +0200 with message-id <20130624181115.GB19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #627151, regarding linux-image-2.6.38-2-686: Dell latitude E5400 freezes during X session to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 627151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.38-5 Severity: normal Hi. My laptop (Dell latitude E5400) has just frozen during an X session :-( Sorry but dunno how to help debug what happened. Note that with linux-image-2.6.32-5-686 I had no similar problems. Thanks in advance. Best regards, -- Package-specific info: ** Version: Linux version 2.6.38-2-686 (Debian 2.6.38-5) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Sun May 8 14:49:45 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-686 root=UUID=6ed8ff22-1b20-476a-b52a-f2c2c698c022 ro quiet ** Not tainted ** Kernel log: [7.417207] [drm] Driver supports precise vblank timestamp query. [7.431072] Bluetooth: Generic Bluetooth USB driver ver 0.6 [7.431435] usbcore: registered new interface driver btusb [7.495635] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [7.672804] iwlagn :0c:00.0: loaded firmware version 8.83.5.1 build 33692 [7.727921] ieee80211 phy0: Selected rate control algorithm 'iwl-agn-rs' [7.840526] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. [7.842239] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x4d0-0x4d7 [7.842955] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [7.843533] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: excluding 0xc80-0xcbf [7.844048] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc 0xe-0xf [7.844101] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [7.844149] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff [7.844206] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [7.854439] fbcon: inteldrmfb (fb0) is primary device [7.901573] Console: switching to colour frame buffer device 106x30 [7.902981] fb0: inteldrmfb frame buffer device [7.902983] drm: registered panic notifier [7.927488] acpi device:3e: registered as cooling_device2 [7.928094] input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A03:00/LNXVIDEO:01/input/input8 [7.928191] ACPI: Video Device [VID1] (multi-head: yes rom: no post: no) [7.928206] [Firmware Bug]: Duplicate ACPI video bus devices for the same VGA controller, please try module parameter "video.allow_duplicates=1"if the current driver doesn't work. [7.928577] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [7.928613] HDA Intel :00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [7.928697] HDA Intel :00:1b.0: irq 46 for MSI/MSI-X [7.928724] HDA Intel :00:1b.0: setting latency timer to 64 [8.080882] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input9 [8.225418] input: HDA Intel Mic at Sep Left Jack as /devices/pci:00/:00:1b.0/sound/card0/input10 [8.225505] input: HDA Intel Mic at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input11 [8.225569] input: HDA Intel Line Out at Sep Left Jack as /devices/pci:00/:00:1b.0/sound/card0/input12 [8.225635] input: HDA Intel HP Out at Ext Right Jack as /devices/pci:00/:00:1b.0/sound/card0/input13 [8.735379] EXT3-fs (sda3): using internal journal [9.072535] loop: module loaded [ 10.720368] Adding 2097148k swap on /dev/mapper/main-swap. Priority:-1 extents:1 across:2097148k [ 13.247590] EXT3-fs: barriers not enabled [ 13.257053] kjournald starting. Commit interval 5 seconds [ 13.257604] EXT3-fs (dm-2): using internal journal [ 13.257609] EXT3-fs (dm-2): mounted filesystem with ordered data mode [ 13.291073] EXT3-fs: barriers not enabled [ 13.291683] kjournald starting. Commit interval 5 seconds [ 13.292149] EXT3-fs (dm-4): using internal journal [ 13.292151] EXT3-fs (dm-4): mounted filesystem with ordered data mode [ 13.317983] EXT3-fs: barriers not enabled [ 13.319356] kjournald starting. Commit interval 5 seconds [ 13.319782] EXT3-fs (dm-1): using in
Bug#627055: marked as done (linux-image-2.6.32: ipw2200 periodically stops transmitting packets, needs to be reinserted)
Your message dated Mon, 24 Jun 2013 20:11:15 +0200 with message-id <20130624181115.GB19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #627055, regarding linux-image-2.6.32: ipw2200 periodically stops transmitting packets, needs to be reinserted to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 627055: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=627055 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-31 Severity: normal File: linux-image-2.6.32 Every now and then when the network is stressed the interface just dies. Network manager displays flawless signal and connectivity but not as much as a ping will go out. If module is removed and reinserted normal operation resumes (until the next time this happens anyway). If Bittorrent is used, this occurs practically daily. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 7 21:35:22 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=36a9a51f-5159-47e9-8d7e-6a36de6c8112 ro quiet ** Not tainted ** Kernel log: [157065.737187] ipw2200: No space for Tx [157065.737193] ipw2200: Failed to send SSID: Reason -16 [157100.772368] ipw2200: No space for Tx [157100.772374] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157135.799493] ipw2200: No space for Tx [157135.799500] ipw2200: Failed to send SSID: Reason -16 [157170.832089] ipw2200: No space for Tx [157170.832095] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157205.864129] ipw2200: No space for Tx [157205.864136] ipw2200: Failed to send SSID: Reason -16 [157240.897188] ipw2200: No space for Tx [157240.897194] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157275.928088] ipw2200: No space for Tx [157275.928095] ipw2200: Failed to send SSID: Reason -16 [157310.943645] ipw2200: No space for Tx [157310.943651] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157345.978819] ipw2200: No space for Tx [157345.978826] ipw2200: Failed to send SSID: Reason -16 [157380.992090] ipw2200: No space for Tx [157380.992096] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157416.024087] ipw2200: No space for Tx [157416.024094] ipw2200: Failed to send SSID: Reason -16 [157451.059262] ipw2200: No space for Tx [157451.059269] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157486.093468] ipw2200: No space for Tx [157486.093475] ipw2200: Failed to send SSID: Reason -16 [157521.128643] ipw2200: No space for Tx [157521.128650] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157556.139742] ipw2200: No space for Tx [157556.139749] ipw2200: Failed to send SSID: Reason -16 [157591.152098] ipw2200: No space for Tx [157591.152104] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157626.182914] ipw2200: No space for Tx [157626.182920] ipw2200: Failed to send SSID: Reason -16 [157661.213227] ipw2200: No space for Tx [157661.213235] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157696.244588] ipw2200: No space for Tx [157696.244595] ipw2200: Failed to send SSID: Reason -16 [157731.279769] ipw2200: No space for Tx [157731.279776] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157766.292088] ipw2200: No space for Tx [157766.292095] ipw2200: Failed to send SSID: Reason -16 [157801.326690] ipw2200: No space for Tx [157801.326697] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157836.361865] ipw2200: No space for Tx [157836.361872] ipw2200: Failed to send SSID: Reason -16 [157871.397039] ipw2200: No space for Tx [157871.397046] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157906.432358] ipw2200: No space for Tx [157906.432364] ipw2200: Failed to send SSID: Reason -16 [157941.467276] ipw2200: No space for Tx [157941.467283] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [157976.502448] ipw2200: No space for Tx [157976.502455] ipw2200: Failed to send SSID: Reason -16 [158011.521417] ipw2200: No space for Tx [158011.521424] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158046.553186] ipw2200: No space for Tx [158046.553192] ipw2200: Failed to send SSID: Reason -16 [158081.588337] ipw2200: No space for Tx [158081.588343] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158116.623266] ipw2200: No space for Tx [158116.623272] ipw2200: Failed to send SSID: Reason -16 [158151.658443] ipw2200: No space for Tx [158151.658450] ipw2200: Failed to send SCAN_REQUEST_EXT: Reason -16 [158186.693193] ipw2200: No space for Tx [158186.693200
Bug#626601: marked as done (plymouth: Kernel null pointer deference at boot time)
Your message dated Mon, 24 Jun 2013 20:11:15 +0200 with message-id <20130624181115.GB19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #626601, regarding plymouth: Kernel null pointer deference at boot time to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 626601: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626601 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: plymouth Version: 0.8.3-18+b1 Severity: normal At boot time, kernel displays a null pointer dereference error on screen, instead of display manager (kdm in my case). This NPD is always reproductible, at each boot. All other parts of boot sequence are correct, and shift to graphical console (ctrl+alt+f7) redisplay kdm and I can login and use the computer without any other problem. Join to this report stacktrace found in /var/log/kern.log -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (600, 'stable'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages plymouth depends on: ii initramfs-tools 0.98.8 tools for generating an initramfs ii libc6 2.11.2-11 Embedded GNU C Library: Shared lib plymouth recommends no packages. plymouth suggests no packages. -- Configuration Files: /etc/plymouth/plymouthd.conf changed: [Daemon] Theme=spinfinity -- no debconf information May 10 21:10:49 aeris kernel: [ 31.448397] BUG: unable to handle kernel NULL pointer dereference at (null) May 10 21:10:49 aeris kernel: [ 31.448419] IP: [] __mutex_lock_common+0xcb/0x193 May 10 21:10:49 aeris kernel: [ 31.448432] PGD 124efe067 PUD 125007067 PMD 0 May 10 21:10:49 aeris kernel: [ 31.448441] Oops: 0002 [#1] SMP May 10 21:10:49 aeris kernel: [ 31.448447] last sysfs file: /sys/devices/pci:00/:00:1f.2/host3/target3:0:0/3:0:0:0/block/sr1/stat May 10 21:10:49 aeris kernel: [ 31.448457] CPU 0 May 10 21:10:49 aeris kernel: [ 31.448460] Modules linked in: vboxnetadp(O) vboxnetflt(O) vboxdrv(O) xt_multiport ppdev lp xt_tcpudp nf_conntrack_ipv6 nf_defrag_ipv6 xt_state ip6table_mangle iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip6table_filter ip6_tables iptable_filter ip_tables x_tables uinput fuse loop joydev hid_logitech ff_memless snd_hda_codec_analog usbhid hid usb_storage uas option usb_wwan usbserial snd_hda_intel snd_hda_codec snd_ctxfi snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq nouveau uhci_hcd ttm drm_kms_helper snd_timer snd_seq_device ehci_hcd drm usbcore snd soundcore sg i2c_algo_bit tg3 power_supply libphy snd_page_alloc nls_base sr_mod tpm_tis i2c_i801 cdrom video parport_pc tpm floppy i2c_core psmouse parport x38_edac tpm_bios dcdbas evdev edac_core processor thermal_sys pcspkr serio_raw ext4 mbcache jbd2 crc16 dm_mod sd_mod crc_t10dif ahci libahci libata scsi_mod button May 10 21:10:49 aeris kernel: [ 31.448722] May 10 21:10:49 aeris kernel: [ 31.448726] Pid: 234, comm: plymouthd Tainted: G O 2.6.38-2-amd64 #1 Dell Inc. Precision WorkStation T3400 /0TP412 May 10 21:10:49 aeris kernel: [ 31.448740] RIP: 0010:[] [] __mutex_lock_common+0xcb/0x193 May 10 21:10:49 aeris kernel: [ 31.448750] RSP: 0018:880124f07e28 EFLAGS: 00010246 May 10 21:10:49 aeris kernel: [ 31.448756] RAX: RBX: 880127076008 RCX: 880127076020 May 10 21:10:49 aeris kernel: [ 31.448762] RDX: 880124f07e48 RSI: 0002 RDI: 88012707600c May 10 21:10:49 aeris kernel: [ 31.448772] RBP: 8801244f06c0 R08: R09: May 10 21:10:49 aeris kernel: [ 31.448781] R10: R11: 0246 R12: 0002 May 10 21:10:49 aeris kernel: [ 31.448791] R13: 88012707600c R14: 880127076010 R15: 880124f06010 May 10 21:10:49 aeris kernel: [ 31.448801] FS: 7f1fce439700() GS:8800cfa0() knlGS: May 10 21:10:49 aeris kernel: [ 31.448810] CS: 0010 DS: ES: CR0: 80050033 May 10 21:10:49 aeris kernel: [ 31.448816] CR2: CR3: 0001257c9000 CR4: 06f0 May 10 21:10:49 aeris kernel: [ 31.448826] DR0: DR1: DR2: May 10 21:10:49 aeris kernel: [ 31.
Bug#625820: marked as done (i915: KMS leaves text console blank on HP Compaq 6710b)
Your message dated Mon, 24 Jun 2013 20:10:45 +0200 with message-id <20130624181044.GA19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #625820, regarding i915: KMS leaves text console blank on HP Compaq 6710b to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 625820: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625820 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: initscripts Version: 2.88dsf-13.1 Severity: normal Synopsis: = when the machine does an fsck while booting, there's no way to know. The user should be informed of the fact otherwise she has no way to know whether the machine is dead or not. Long version: = Lately, while rebooting, my machine just stayed black. Nothing was happening except for the disk drive LED being on. It needs to be noted, that my laptop has problems waking up from suspend and related subjects, so it just could have been that it was trying to revive and somehow had died in the process. Changing the screen with Alt-Fx was not possible, pinging the machine was not possible either (I think - I did not test that, lacking a second machine) and logging into the machine over the net didn't work. So the machine was indistinguishible from a brick with a shining led. Consequently I hard shut down the machine a few times and tried to reboot again and again before starting it in rescue mode and seeing that indeed it was doing a long fsck of the large root partition. Wish: = Please provide the user with live feedback, about when a fsck is happening and about the progress of it. I'm not sure initscripts is the correct package to report this bug against?... Thanks, *t --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#626309: marked as done (linux-image-2.6.38-2-amd64: Wifi connection drops randomly with Realtek RTL8187 wifi adapter)
Your message dated Mon, 24 Jun 2013 20:11:15 +0200 with message-id <20130624181115.GB19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #626309, regarding linux-image-2.6.38-2-amd64: Wifi connection drops randomly with Realtek RTL8187 wifi adapter to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 626309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626309 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.38-5 Severity: normal I have a USB adapter (identified as Realtek RTL8187 Wireless Adapter) that I use to connect to wifi. Until updating the kernel from 2.6.37-2 to the current version, it worked perfectly, but now the connection drops randomly: sometimes once a day, sometimes every 20 minutes, and sometimes all the time. The computer can still detect the Wifi network, but I can't browse or download anything. The same computer with the same adapter can connect perfectly with Windows 7 and with the previous kernel, and the system does not detect any signal drop when the connection drops, so I suppose it's some driver issue. -- Package-specific info: ** Version: Linux version 2.6.38-2-amd64 (Debian 2.6.38-5) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Sun May 8 13:51:57 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-amd64 root=UUID=6fc5455a-d392-4fe4-9306-b088e71d090f ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [3.939429] sd 4:0:0:2: Attached scsi generic sg4 type 0 [3.944553] sd 4:0:0:1: [sdc] Attached SCSI removable disk [3.950025] sd 4:0:0:2: [sdd] Attached SCSI removable disk [3.950771] sd 4:0:0:0: [sdb] Attached SCSI removable disk [4.993978] PM: Starting manual resume from disk [4.993980] PM: Hibernation image partition 8:6 present [4.993981] PM: Looking for hibernation image. [4.994140] PM: Image not found (code -22) [4.994143] PM: Hibernation image not present or could not be loaded. [5.009954] EXT3-fs: barriers not enabled [5.020845] kjournald starting. Commit interval 5 seconds [5.020866] EXT3-fs (sda5): mounted filesystem with ordered data mode [5.869250] <30>udevd[410]: starting version 168 [6.288541] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input4 [6.288547] ACPI: Power Button [PWRB] [6.288603] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input5 [6.288606] ACPI: Power Button [PWRF] [6.659918] ACPI: acpi_idle registered with cpuidle [6.662858] Monitor-Mwait will be used to enter C-1 state [6.662878] Monitor-Mwait will be used to enter C-2 state [6.662893] Monitor-Mwait will be used to enter C-3 state [6.780505] cfg80211: Calling CRDA to update world regulatory domain [7.010569] input: PC Speaker as /devices/platform/pcspkr/input/input6 [7.216079] i801_smbus :00:1f.3: PCI INT C -> GSI 18 (level, low) -> IRQ 18 [7.357016] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [7.357447] ieee80211 phy0: hwaddr 00:e0:4c:04:4f:d7, RTL8187vB (default) V1 + rtl8225z2, rfkill mask 2 [7.368271] rtl8187: Customer ID is 0x00 [7.368327] Registered led device: rtl8187-phy0::radio [7.368365] Registered led device: rtl8187-phy0::tx [7.368393] Registered led device: rtl8187-phy0::rx [7.368763] rtl8187: wireless switch is on [7.368804] usbcore: registered new interface driver rtl8187 [7.440148] rt61pci :04:02.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [7.446952] ieee80211 phy1: Selected rate control algorithm 'minstrel_ht' [7.447408] Registered led device: rt61pci-phy1::radio [7.447426] Registered led device: rt61pci-phy1::assoc [7.464379] <30>udevd[429]: renamed network interface wlan1 to rename4 [7.680434] HDA Intel :00:1b.0: PCI INT A -> GSI 22 (level, low) -> IRQ 22 [7.680476] HDA Intel :00:1b.0: irq 42 for MSI/MSI-X [7.680496] HDA Intel :00:1b.0: setting latency timer to 64 [7.725842] HDA Intel :01:00.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [7.725844] hda_intel: Disable MSI for Nvidia chipset [7.725865] HDA Intel :01:00.1: setting latency timer to 64 [7.779637] <30>udevd[430]: renamed network interface wlan0 to wlan1 [7.803435] <30>udevd[429]: renamed network interface rename4 to wlan0 [9.124604] Adding 7661564k swap on /dev/sda6. Priority:-1 extents:1 across:7661564k [9.374452] EXT3-fs (sda5): using internal jo
Bug#626451: marked as done (linux-image: mremap returns useless pages moving anonymous shared mmap, access causes SIGBUS)
Your message dated Mon, 24 Jun 2013 20:11:15 +0200
with message-id <20130624181115.GB19955@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #626451,
regarding linux-image: mremap returns useless pages moving anonymous shared
mmap, access causes SIGBUS
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
626451: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626451
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image
Severity: normal
one-line summary:
mremap yields unusable pages when growing an ANONYMOUS SHARED mmap with MAYMOVE.
full description:
This program (courtesy of Alan Curry) demonstrates the raising of a
bus error by the (misguided?) sequence of
- mmap'ing a one-page map with MAP_SHARED | MAP_ANONYMOUS
- mremap'ing to a larger size
- attempting to access the new portion of the map
#define _GNU_SOURCE
#include
#include
#include
int main(void)
{
int pgsz;
void *p;
pgsz = getpagesize();
printf("pgsz = %d\n", pgsz);
p = mmap(NULL, pgsz, PROT_READ|PROT_WRITE, MAP_SHARED|MAP_ANONYMOUS, -1, 0);
printf("p before growth = %p\n", p);
p = mremap(p, pgsz, pgsz*2, MREMAP_MAYMOVE);
printf("p after growth = %p\n", p);
/* try to access the last byte of the original allocation */
printf("p[%d] = %d\n", pgsz-1, ((volatile char *)p)[pgsz-1]);
/* try to access the first byte of the new allocation */
printf("p[%d] = %d\n", pgsz, ((volatile char *)p)[pgsz]);
return 0;
}
Alan Curry's comments: {
The problem seems to be that a growing mremap doesn't work on shared
anonymous mappings. This might be by design, but it seems fishy to me since
mremap doesn't return an error but instead gives you some pages that you
can't use.
I think you'd be justified in reporting this as a kernel bug. If it turns out
to be an intentional restriction it should at least be mentioned in the
mremap man page.
Here's a much smaller demo program. If MAP_SHARED is changed to MAP_PRIVATE,
there's no problem. If a file is provided for backing store instead of
MAP_ANONYMOUS, there's no problem. The combination of shared and anonymous
causes the SIGBUS.
}
Upon further reflection, the sequence is meaningless; and if it's
possible for mremap to detect that the combination MAP_SHARED|MAP_ANONYMOUS
is defined for the mapping, it ought to refuse the request
(returning MAP_FAILED, with errno==EINVAL) if it included
MREMAP_MAYMOVE, or ignore the option and attempt to keep the
mapping fixed.
Also, the manpage for mremap ought to advise against doing this.
Because an anonymous mapping can only be shared by forking, but
once the two processes have separated, if one moves the mapping,
how is the other ever to find it? Sure, one can think of ways
of informing this second program of the change; but there's no
clear way of maintaining this association automatically.
This problem arose in a discussion in comp.unix.programmer
which began with the message:
<6e42b7e2-8f29-4c41-98eb-3caa4108f...@m10g2000yqd.googlegroups.com>
or
http://groups.google.com/group/comp.unix.programmer/browse_thread/thread/9a8c963aedc91ca2#
I can be contacted at mijo...@yahoo.com or in the newsgroup thread.
Thank you for your time.
M. Joshua Ryan
keywords
mmap mremap mman.h MAP_SHARED MAP_ANONYMOUS MREMAP_MAYMOVE
-- System Information:
Debian Release: 5.0.8
APT prefers oldstable
APT policy: (500, 'oldstable')
Architecture: i386 (i586)
Kernel: Linux 2.6.25.15
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/bash
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.
We don't have the ressources to reproduce the complete backlog of all older
kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with
Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by
sending
a mail to cont...@bugs.debian.org with the following three commands included in
the
mail:
reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks
Cheers,
Moritz--- End Message ---
Bug#626077: marked as done (Debian testing couldn't see plugged peripherals devices after boot)
Your message dated Mon, 24 Jun 2013 20:11:15 +0200 with message-id <20130624181115.GB19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #626077, regarding Debian testing couldn't see plugged peripherals devices after boot to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 626077: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626077 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: I don't know Debian testing couldn't see plugged peripherals devices after boot. For example couldn't work internal keyboard and touchpad in netbook Acer Aspire One 521, but plugged after boot external keyboard and mice work well. If external keyboard and mice plugged during Debian boot, after start X session, their devices couldn't work too. But after reconnect, their start work again. Also couldn't work internal wireless network and network adapters and sound card. How I install debian testing (steps to reproduse my bug): 1) Download this image: http://ftp.acc.umu.se/cdimage/weekly-builds/i386/iso-cd/debian-testing-i386-CD-1.iso 2) Copy image to usb stick: dd if=/home/mikhail/Загрузки/debian-testing-i386-CD-1.iso of=/dev/sdd 3) Install Debian testing with GNOME Desktop shell 4) After first boot internal keyboard and touchpad couldnt work. I am try using Debian GNU/Linux 6 testing, kernel 2.6.38-2-686 -- Best Regards, Mike Gavrilov. --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#625899: marked as done (BUG at fs/btrfs/inode.c:799)
Your message dated Mon, 24 Jun 2013 20:10:45 +0200 with message-id <20130624181044.GA19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #625899, regarding BUG at fs/btrfs/inode.c:799 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 625899: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625899 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-31 Severity: normal -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 - -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Mon Mar 7 21:35:22 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=d8fdc5a3-6df6-4d8c-aa34-0bd226a3f49e ro quiet ** Tainted: PD (129) * Proprietary module has been loaded. * Kernel has oopsed before. ** Kernel log: [699325.791931] [ cut here ] [699325.791934] kernel BUG at /build/buildd-linux-2.6_2.6.32-31-amd64-vrfdM4/linux-2.6-2.6.32/debian/build/source_amd64_none/fs/btrfs/inode.c:799! [699325.791938] invalid opcode: [#1] SMP [699325.791941] last sysfs file: /sys/devices/virtual/block/dm-4/queue/rotational [699325.791943] CPU 1 [699325.791945] Modules linked in: powernow_k8 cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative binfmt_misc fuse firewire_sbp2 loop snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq _midi_emul snd_emu10k1 snd_intel8x0 snd_ac97_codec ac97_bus snd_seq_midi snd_rawmidi snd_seq_midi_event snd_pcm_oss snd_mixer_oss snd_seq snd_pcm emu10k1_gp snd_timer snd_util_mem snd_hwdep gameport snd_seq_device nvidia(P) snd amd64_edac_mod s oundcore shpchp parport_pc edac_core i2c_nforce2 pci_hotplug parport edac_mce_amd k8temp snd_page_alloc serio_raw pcspkr i2c_core evdev button container processor reiserfs dm_mod raid456 async_raid6_recov async_pq usbhid hid usb_storage raid6_p q async_xor xor async_memcpy async_tx raid1 md_mod btrfs zlib_deflate crc32c libcrc32c ohci_hcd ata_generic sg sd_mod crc_t10dif firewire_ohci pata_amd thermal arcmsr ehci_hcd floppy firewire_core crc_itu_t sata_nv forcedeth usbcore nls_base li bata thermal_sys scsi_mod [last unloaded: sc si_wait_scan] [699325.792004] Pid: 74987, comm: git Tainted: P 2.6.32-5-amd64 #1 S2895 [699325.792007] RIP: 0010:[] [] cow_file_range+0x1ff/0x34f [btrfs] [699325.792043] RSP: 0018:88011c195a98 EFLAGS: 00010286 [699325.792045] RAX: ffe4 RBX: 06434000 RCX: 195b [699325.792048] RDX: 0001 RSI: 0092 RDI: 88007e557ec0 [699325.792050] RBP: 1000 R08: 8101654b R09: 813af56b [699325.792053] R10: R11: 000186a0 R12: 1000 [699325.792055] R13: 1000 R14: 880031371970 R15: 88007e0ee800 [699325.792058] FS: 7f6046535700() GS:88000370() knlGS:f74356d0 [699325.792061] CS: 0010 DS: ES: CR0: 80050033 [699325.792063] CR2: 00472000 CR3: 000169525000 CR4: 06e0 [699325.792066] DR0: DR1: DR2: [699325.792069] DR3: DR6: 0ff0 DR7: 0400 [699325.792072] Process git (pid: 74987, threadinfo 88011c194000, task 88015b98) [699325.792074] Stack: [699325.792075] 88011c195b08 0001 810e5af1 [699325.792079] <0> 88011c195cf0 88011c195d0c ea000198b308 1000 [699325.792083] <0> 8800313717f8 880031371800 88007f5d2380 000c [699325.792087] Call Trace: [699325.792095] [] ? virt_to_head_page+0x9/0x2a [699325.792109] [] ? run_delalloc_range+0xa1/0x36b [btrfs] [699325.792122] [] ? test_range_bit+0x2a/0xd3 [btrfs] [699325.792135] [] ? find_lock_delalloc_range+0x181/0x1a9 [btrfs] [699325.792147] [] ? btrfs_wake_function+0x0/0x10 [btrfs] [699325.792160] [] ? __extent_writepage+0x1fb/0x660 [btrfs] [699325.792165] [] ? __lookup_tag+0xad/0x11b [699325.792178] [] ? extent_write_cache_pages+0x135/0x209 [btrfs] [699325.792191] [] ? flush_write_bio+0x0/0x2 [btrfs] [699325.792203] [] ? __extent_writepage+0x0/0x660 [btrfs] [699325.792215] [] ? extent_writepages+0x4b/0x5f [btrfs] [699325.792229] [] ? btrfs_get_extent+0x0/0x73f [btrfs] [699325.792234] [] ? __filemap_fdatawrite_range+0x4b/0x54 [699325.792238] [] ? filemap_write_and_wait_range+0x26/0x52 [699325.792243] [] ? vfs_fsync_range+0x55/0x9e
Bug#626021: marked as done (linux-image-2.6.38-2-686: icebp (opcode 0xf1) no longer causing a SIGTRAP, breaks Wine)
Your message dated Mon, 24 Jun 2013 20:11:15 +0200 with message-id <20130624181115.GB19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #626021, regarding linux-image-2.6.38-2-686: icebp (opcode 0xf1) no longer causing a SIGTRAP, breaks Wine to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 626021: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=626021 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.38-3 Severity: normal This is a bug in the kernel itself, there have been a few patches to the kernel, but it seems at least one patch is not in the vanilla kernel. Some other distributions are including this patch. See https://bugzilla.kernel.org/show_bug.cgi?id=16315 and http://bugs.winehq.org/show_bug.cgi?id=23323 for more info. -- Package-specific info: ** Version: Linux version 2.6.38-2-686 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 05:24:21 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-686 root=UUID=fc173ee2-9266-4bce-b5c3-ff468730f225 ro quiet ** Not tainted ** Kernel log: [0.664763] 00:06: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A [0.664919] Linux agpgart interface v0.103 [0.665034] i8042: PNP: PS/2 Controller [PNP0303:KBD,PNP0f13:MOU] at 0x60,0x64 irq 1,12 [0.665505] serio: i8042 KBD port at 0x60,0x64 irq 1 [0.665516] serio: i8042 AUX port at 0x60,0x64 irq 12 [0.665606] mousedev: PS/2 mouse device common for all mice [0.665792] input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input0 [0.665965] rtc_cmos 00:01: rtc core: registered rtc_cmos as rtc0 [0.666036] rtc0: alarms up to one day, 114 bytes nvram, hpet irqs [0.666047] cpuidle: using governor ladder [0.666048] cpuidle: using governor menu [0.666192] TCP cubic registered [0.666292] NET: Registered protocol family 10 [0.666726] Mobile IPv6 [0.666730] NET: Registered protocol family 17 [0.666735] Registering the dns_resolver key type [0.666751] Using IPI No-Shortcut mode [0.666819] PM: Hibernation image not present or could not be loaded. [0.666826] registered taskstats version 1 [0.666928] rtc_cmos 00:01: setting system clock to 2011-05-06 19:42:14 UTC (1304710934) [0.666944] Initalizing network drop monitor service [0.666997] Freeing unused kernel memory: 392k freed [0.667098] Write protecting the kernel text: 2648k [0.667109] Write protecting the kernel read-only data: 1000k [0.679883] <30>udev[45]: starting version 167 [0.695518] 8139cp: 8139cp: 10/100 PCI Ethernet driver v1.3 (Mar 22, 2004) [0.695633] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [0.695654] 8139cp :00:03.0: PCI INT A -> Link[LNKC] -> GSI 11 (level, high) -> IRQ 11 [0.744936] FDC 0 is a S82078B [0.745467] 8139cp :00:03.0: eth0: RTL-8139C+ at 0xc8806000, 52:54:00:12:34:56, IRQ 11 [0.745490] 8139cp :00:03.0: setting latency timer to 64 [0.747229] 8139too: 8139too Fast Ethernet driver 0.9.28 [0.748483] SCSI subsystem initialized [0.759932] libata version 3.00 loaded. [0.761768] ata_piix :00:01.1: version 2.13 [0.761824] ata_piix :00:01.1: setting latency timer to 64 [0.762212] scsi0 : ata_piix [0.762298] scsi1 : ata_piix [0.762328] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc000 irq 14 [0.762330] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc008 irq 15 [0.916539] ata1.01: NODEV after polling detection [0.916751] ata2.01: NODEV after polling detection [0.916959] ata1.00: ATA-7: QEMU HARDDISK, 0.13.0, max UDMA/100 [0.916961] ata1.00: 20971520 sectors, multi 16: LBA48 [0.917096] ata2.00: ATAPI: QEMU DVD-ROM, 0.13.0, max UDMA/100 [0.917408] ata1.00: configured for MWDMA2 [0.917492] scsi 0:0:0:0: Direct-Access ATA QEMU HARDDISK0.13 PQ: 0 ANSI: 5 [0.917864] ata2.00: configured for MWDMA2 [0.918137] scsi 1:0:0:0: CD-ROMQEMU QEMU DVD-ROM 0.13 PQ: 0 ANSI: 5 [0.928603] sd 0:0:0:0: [sda] 20971520 512-byte logical blocks: (10.7 GB/10.0 GiB) [0.928628] sd 0:0:0:0: [sda] Write Protect is off [0.928630] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00 [0.928641] sd 0:0:0:0: [sda] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA [0.929229] sr0: scsi3-mmc drive: 4x/4x xa/form2 tray [0.929231] cdrom: Uniform CD-ROM driver Revision: 3.20 [0.929407] sda: sda1 sda2 < sda5 > [0.929622] sd 0:0:0:0: [
Bug#624791: marked as done (reiserfs woes on huge write session)
Your message dated Mon, 24 Jun 2013 20:10:45 +0200 with message-id <20130624181044.GA19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #624791, regarding reiserfs woes on huge write session to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 624791: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624791 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.32-5-amd64 Version: 2.6.32-31 I've got a huge file server with about 3.5 TByte disk space (reiserfs), 64 GByte RAM and 2 quadcore CPUs. Trying to copy (rsync) about 2 TByte data to this disk it takes a few minutes, the load goes up to 6 or higher, then there is this message: May 1 14:50:04 srvl011 kernel: [ 1081.086183] reiserfs/1D 0 334 2 0x May 1 14:50:04 srvl011 kernel: [ 1081.086188] 881029cb3880 0046 812fae54 May 1 14:50:04 srvl011 kernel: [ 1081.086191] 0046 f9e0 8810262b5fd8 May 1 14:50:04 srvl011 kernel: [ 1081.086193] 00015780 00015780 881026fa5bd0 881026fa5ec8 May 1 14:50:04 srvl011 kernel: [ 1081.086195] Call Trace: May 1 14:50:04 srvl011 kernel: [ 1081.086205] [] ? thread_return+0x8d/0xe0 May 1 14:50:04 srvl011 kernel: [ 1081.086208] [] ? __mutex_lock_common+0x122/0x192 May 1 14:50:04 srvl011 kernel: [ 1081.086210] [] ? mutex_lock+0x1a/0x31 May 1 14:50:04 srvl011 kernel: [ 1081.086232] [] ? flush_commit_list+0x146/0x5d0 [reiserfs] May 1 14:50:04 srvl011 kernel: [ 1081.086241] [] ? flush_commit_list+0xf6/0x5d0 [reiserfs] May 1 14:50:04 srvl011 kernel: [ 1081.086249] [] ? flush_async_commits+0x42/0x4b [reiserfs] May 1 14:50:04 srvl011 kernel: [ 1081.086258] [] ? worker_thread+0x188/0x21d May 1 14:50:04 srvl011 kernel: [ 1081.086266] [] ? flush_async_commits+0x0/0x4b [reiserfs] May 1 14:50:04 srvl011 kernel: [ 1081.086272] [] ? autoremove_wake_function+0x0/0x2e May 1 14:50:04 srvl011 kernel: [ 1081.086278] [] ? worker_thread+0x0/0x21d May 1 14:50:04 srvl011 kernel: [ 1081.086282] [] ? kthread+0x79/0x81 May 1 14:50:04 srvl011 kernel: [ 1081.086289] [] ? child_rip+0xa/0x20 May 1 14:50:04 srvl011 kernel: [ 1081.086294] [] ? kthread+0x0/0x81 May 1 14:50:04 srvl011 kernel: [ 1081.086298] [] ? child_rip+0x0/0x20 May 1 14:50:04 srvl011 kernel: [ 1081.086310] reiserfs/3D 0 336 2 0x May 1 14:50:04 srvl011 kernel: [ 1081.086317] 881029cb7100 0046 813c7097 881026237da5 May 1 14:50:04 srvl011 kernel: [ 1081.086325] 881026237d98 0006 f9e0 881026237fd8 May 1 14:50:04 srvl011 kernel: [ 1081.086332] 00015780 00015780 881026fa62e0 881026fa65d8 May 1 14:50:04 srvl011 kernel: [ 1081.086340] Call Trace: May 1 14:50:04 srvl011 kernel: [ 1081.086345] [] ? __mutex_lock_common+0x122/0x192 May 1 14:50:04 srvl011 kernel: [ 1081.086350] [] ? mutex_lock+0x1a/0x31 May 1 14:50:04 srvl011 kernel: [ 1081.086359] [] ? flush_commit_list+0x146/0x5d0 [reiserfs] May 1 14:50:04 srvl011 kernel: [ 1081.086368] [] ? flush_commit_list+0xf6/0x5d0 [reiserfs] May 1 14:50:04 srvl011 kernel: [ 1081.086376] [] ? flush_async_commits+0x42/0x4b [reiserfs] May 1 14:50:04 srvl011 kernel: [ 1081.086382] [] ? worker_thread+0x188/0x21d May 1 14:50:04 srvl011 kernel: [ 1081.086390] [] ? flush_async_commits+0x0/0x4b [reiserfs] May 1 14:50:04 srvl011 kernel: [ 1081.086396] [] ? autoremove_wake_function+0x0/0x2e May 1 14:50:04 srvl011 kernel: [ 1081.086401] [] ? worker_thread+0x0/0x21d May 1 14:50:04 srvl011 kernel: [ 1081.086407] [] ? kthread+0x79/0x81 May 1 14:50:04 srvl011 kernel: [ 1081.086412] [] ? child_rip+0xa/0x20 May 1 14:50:04 srvl011 kernel: [ 1081.086417] [] ? worker_thread+0x0/0x21d May 1 14:50:04 srvl011 kernel: [ 1081.086422] [] ? kthread+0x0/0x81 May 1 14:50:04 srvl011 kernel: [ 1081.086427] [] ? child_rip+0x0/0x20 May 1 14:50:04 srvl011 kernel: [ 1081.086446] rsync D 0 1927 1926 0x May 1 14:50:04 srvl011 kernel: [ 1081.086452] 881029cb7100 0082 May 1 14:50:04 srvl011 kernel: [ 1081.086461] 88056a08 0001 f9e0 880f5806bfd8 May 1 14:50:04 srvl011 kernel: [ 1081.086468] 00015780 00015780 88102640b170 88102640b468 May 1 14:50:04 srvl011 kernel: [ 1081.086476] Call Trace: May 1 14:5
Bug#625738: marked as done (>2TB SCSI disk size not recognized correctly)
Your message dated Mon, 24 Jun 2013 20:10:45 +0200 with message-id <20130624181044.GA19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #625738, regarding >2TB SCSI disk size not recognized correctly to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 625738: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625738 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.32-5-686 Version: 2.6.32-31 I upgraded a machine from Lenny to Squeeze, and it failed to mount one of the disks. Here is a large swath of dmesg from the failing kernel: [0.00] Linux version 2.6.32-5-686 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Mar 8 21:36:00 UTC 2011 ... [3.914558] scsi 4:0:0:0: Direct-Access R0.0 PQ: 0 ANSI: 5 [3.914564] scsi 4:0:0:0: Information Units disabled by blacklist [3.914576] scsi target4:0:0: Beginning Domain Validation [3.914594] scsi5 : ioc1: LSI53C1030 C0, FwRev=01032700h, Ports=1, MaxQ=255, IRQ=18 [4.566692] scsi target4:0:0: Ending Domain Validation [4.566756] scsi target4:0:0: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 127) [5.728614] scsi 4:0:5:0: Sequential-Access CERTANCE ULTRIUM 31770 PQ: 0 ANSI: 4 [5.728625] scsi target4:0:5: Beginning Domain Validation [6.058280] scsi target4:0:5: Domain Validation skipping write tests [6.058283] scsi target4:0:5: Ending Domain Validation [6.058345] scsi target4:0:5: FAST-80 WIDE SCSI 160.0 MB/s DT (12.5 ns, offset 127) [8.310955] scsi 3:0:0:0: Direct-Access ATA SEAGATE ST32500N n/a PQ: 0 ANSI: 5 [8.325016] sd 2:0:0:0: [sda] 488390625 512-byte logical blocks: (250 GB/232 GiB) [8.325071] sd 2:0:0:0: [sda] Write Protect is off [8.325075] sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00 [8.325098] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [8.325233] sda: [8.332152] sd 3:0:0:0: [sdc] 488390625 512-byte logical blocks: (250 GB/232 GiB) [8.332201] sd 3:0:0:0: [sdc] Write Protect is off [8.332204] sd 3:0:0:0: [sdc] Mode Sense: 00 3a 00 00 [8.332225] sd 3:0:0:0: [sdc] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [8.332365] sdc: [8.332488] st: Version 20081215, fixed bufsize 32768, s/g segs 256 [8.09] st 4:0:5:0: Attached scsi tape st0 [8.12] st 4:0:5:0: st0: try direct i/o: yes (alignment 512 B) [8.343674] sd 4:0:0:0: [sdb] 4294967296 512-byte logical blocks: (2.19 TB/2.00 TiB) [8.344551] usbcore: registered new interface driver hiddev [8.344741] sd 4:0:0:0: [sdb] Write Protect is off [8.344745] sd 4:0:0:0: [sdb] Mode Sense: bf 00 00 08 [8.345180] sd 4:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [8.345421] sda1 sda2 [8.345672] sd 2:0:0:0: [sda] Attached SCSI disk [8.345973] sd 4:0:0:0: [sdb] 13651132416 512-byte logical blocks: (6.98 TB/6.35 TiB) [8.347305] sdb: detected capacity change from 219902322 to 6989379796992 [8.347310] sdb: [8.348685] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.348837] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.348986] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.349135] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.349286] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.349435] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.349442] sd 4:0:0:0: [sdb] Unhandled error code [8.349444] sd 4:0:0:0: [sdb] Result: hostbyte=DID_SOFT_ERROR driverbyte=DRIVER_OK [8.349449] sd 4:0:0:0: [sdb] CDB: Read(16): 88 00 00 00 00 03 2d ab bf f8 00 00 00 08 00 00 [8.349461] end_request: I/O error, dev sdb, sector 13651132408 [8.349520] Buffer I/O error on device sdb, logical block 1706391551 [8.349732] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.349886] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.350046] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.350196] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.350347] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.350497] Errataon LSI53C1030 occurred.sc->req_bufflen=0x1000,xfer_cnt=0x00 [8.350503] sd 4:0:0:0: [sdb] Unhandled error code [8.350505]
Bug#624711: marked as done (linux-image-2.6.32-5-powerpc: orinoco/airport driver returns two ESSIDs for an AP)
Your message dated Mon, 24 Jun 2013 20:10:45 +0200 with message-id <20130624181044.GA19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #624711, regarding linux-image-2.6.32-5-powerpc: orinoco/airport driver returns two ESSIDs for an AP to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 624711: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624711 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-31 Severity: normal Hi, 'iwlist eth2 scan' returns two 'ESSID' fields on my airport equipped TiBook from a DD-WRT router. The latter ESSID is garbage, but it nevertheless gets picked up by the higher level network configuration (wicd), which makes automatic network configuration fail. Running iwconfig and ifup manually works fine, and there are no other network problems with this card / AP combination. iwlist also reports 'Mode:Unknown/bug' for this router. Other wireless cards I've tested give the correct iwlist output from this router, i.e. a single ESSID and the correct Mode. On the other hand, this router is the only one exhibiting the problem, other access points work correctly. Here's the full scan output (cell address has been blanked): eth2 Scan completed : Cell 01 - Address: xx:xx:xx:xx:xx:xx Channel:11 Frequency:2.462 GHz (Channel 11) Quality=24/70 Signal level=-86 dBm Encryption key:off ESSID:"DD-WRT" Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s 9 Mb/s; 12 Mb/s; 18 Mb/s Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s ESSID:"\x0B\x00\x1B\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00" Mode:Unknown/bug Extra:tsf=002812c5da51 Extra: Last beacon: 164ms ago IE: Unknown: 000461736D61 IE: Unknown: 010882848B960C121824 IE: Unknown: 03010B IE: Unknown: 2A0107 IE: Unknown: 32043048606C IE: Unknown: DD180050F20201010A0003A427A442435E0062322F00 IE: Unknown: 331ACC131B00 IE: Unknown: 2D1ACC131B00 IE: Unknown: 34160B001B00 IE: Unknown: 3D160B001B00 IE: Unknown: 4A0E14000A002C01C800140005001900 IE: Unknown: 7F0101 IE: Unknown: DD0900037F0101FF7F IE: Unknown: DD0A00037F040100 Best, Teemu -- Package-specific info: ** Version: Linux version 2.6.32-5-powerpc (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 Mon Mar 7 22:49:07 UTC 2011 ** Command line: root=UUID=caa877ca-7d43-48c1-ad17-2e368b05a84a ro ** Not tainted ** Kernel log: [ 3977.550201] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 3977.745443] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 4113.108782] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 4113.306089] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 4113.399829] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 4115.551576] eth2: Lucent/Agere firmware doesn't support manual roaming [ 4184.653200] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 4184.849084] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 4315.210957] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 4315.402101] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 4315.494345] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 4317.647017] eth2: Lucent/Agere firmware doesn't support manual roaming [ 4381.955753] ADDRCONF(NETDEV_UP): eth2: link is not ready [ 4382.368595] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 4467.627687] eth2: New link status: Connected (0001) [ 4467.627804] ADDRCONF(NETDEV_CHANGE): eth2: link becomes ready [ 4478.085138] eth2: no IPv6 routers present ** Model information revision: 2.1 (pvr 8000 0201) platform: PowerMac model : PowerBook3,3 machine : PowerBook3,3 motherboard : PowerBook3,3 MacRISC2 MacRISC Power Macintosh ** Loaded modules: Module Size Used by binfmt_misc10371 1 radeon693199 0 ttm46868 1 radeon drm_kms_helper 24325 1 radeon drm
Bug#625688: marked as done (NIC problems)
Your message dated Mon, 24 Jun 2013 20:10:45 +0200 with message-id <20130624181044.GA19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #625688, regarding NIC problems to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 625688: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=625688 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: Image version: Date: Machine: Processor:AMD Phenom II quad core SN 9213227D90014 Memory:3 x 4GB DDR3 Kingston KHX1600C9D3K3/12GX Partitions: <2gb boot, 4gb swap, 63gb root> Output of lspci -knn (or lspci -nn): 00:00.0 Host bridge [0600]: ATI Technologies Inc RD890 Northbridge only single slot PCI-e GFX Hydra part [1002:5a11] (rev 02) 00:02.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port B) [1002:5a16] 00:04.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port D) [1002:5a18] 00:05.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port E) [1002:5a19] 00:06.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port F) [1002:5a1a] 00:07.0 PCI bridge [0604]: ATI Technologies Inc RD890 PCI to PCI bridge (PCI express gpp port G) [1002:5a1b] 00:11.0 SATA controller [0106]: ATI Technologies Inc SB700/SB800 SATA Controller [IDE mode] [1002:4390] (rev 40) 00:12.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:12.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:13.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:13.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:14.0 SMBus [0c05]: ATI Technologies Inc SBx00 SMBus Controller [1002:4385] (rev 41) 00:14.1 IDE interface [0101]: ATI Technologies Inc SB700/SB800 IDE Controller [1002:439c] (rev 40) 00:14.2 Audio device [0403]: ATI Technologies Inc SBx00 Azalia (Intel HDA) [1002:4383] (rev 40) 00:14.3 ISA bridge [0601]: ATI Technologies Inc SB700/SB800 LPC host controller [1002:439d] (rev 40) 00:14.4 PCI bridge [0604]: ATI Technologies Inc SBx00 PCI to PCI Bridge [1002:4384] (rev 40) 00:14.5 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI2 Controller [1002:4399] 00:16.0 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB OHCI0 Controller [1002:4397] 00:16.2 USB Controller [0c03]: ATI Technologies Inc SB700/SB800 USB EHCI Controller [1002:4396] 00:18.0 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor HyperTransport Configuration [1022:1200] 00:18.1 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Address Map [1022:1201] 00:18.2 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor DRAM Controller [1022:1202] 00:18.3 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Miscellaneous Control [1022:1203] 00:18.4 Host bridge [0600]: Advanced Micro Devices [AMD] Family 10h Processor Link Control [1022:1204] 02:00.0 USB Controller [0c03]: NEC Corporation uPD720200 USB 3.0 Host Controller [1033:0194] (rev 03) 03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06) 04:00.0 FireWire (IEEE 1394) [0c00]: VIA Technologies, Inc. VT6315 Series Firewire Controller [1106:3403] (rev 01) 05:00.0 SATA controller [0106]: JMicron Technology Corp. JMB361 AHCI/IDE [197b:2361] (rev 02) 05:00.1 IDE interface [0101]: JMicron Technology Corp. JMB361 AHCI/IDE [197b:2361] (rev 02) 06:00.0 VGA compatible controller [0300]: ATI Technologies Inc Cypress [Radeon HD 5800 Series] [1002:6899] 06:00.1 Audio device [0403]: ATI Technologies Inc Cypress HDMI Audio [Radeon HD 5800 Series] [1002:aa50] Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: NIC install was incomplete. Motherboard is ASUS M4A89 series with on-board NIC (Realtek 8111e). Still, it initiated with the install. It saw my home network and router, but not beyon
Bug#624400: marked as done (linux-image-2.6.32-5-amd64: Intel Ethernetcard does not work)
Your message dated Mon, 24 Jun 2013 20:10:45 +0200 with message-id <20130624181044.GA19955@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #624400, regarding linux-image-2.6.32-5-amd64: Intel Ethernetcard does not work to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 624400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.32-5-amd64 Severity: normal There is a problem with the e1000e driver, the Intel cards Intel Corporation 82571EB Gigabit Ethnernet Controller (rev 06) dual port Intel Corporation 82574L Gigabit Ethnet Connection dual port both cards show up via lspci and dmesg but they cant get any link and they dont activate when a network cable gets plugged in. -- System Information: Debian Release: 6.0.1 APT prefers stable APT policy: (990, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-xen-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
gcc 4.8
Hi I did a first build of Linux 3.9 with gcc 4.8. It works fine on s390x, however I found a weird not longer reproducible bug in s390. I think about using it as default pretty fast for all architectures. Bastian -- Change is the essential process of all existence. -- Spock, "Let That Be Your Last Battlefield", stardate 5730.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/20130624172724.gb10...@mail.waldi.eu.org
Bug#623943: marked as done (EeePC SDHC Reader and Failure to Disable ehci-hcd)
Your message dated Mon, 24 Jun 2013 19:30:55 +0200 with message-id <20130624173054.GB22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #623943, regarding EeePC SDHC Reader and Failure to Disable ehci-hcd to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 623943: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623943 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: installation-reports Boot method: CD image on USB drive Image version: http://cdimage.debian.org/debian-cd/6.0.1a/i386/iso-cd/debian-6.0.1a-i386-netinst.iso Date: 24 April 2011 Machine: Asus EeePC 2G Surf (EeePC 700) Processor: Celeron M Memory: 512MB Partitions: Cannot get raw partition table; fails at partitioning. ~ # df -TI df: invalid option -- 'T' BusyBox v1.17.1 (Debian 1:1.17.1-8) multi-call binary. Usage: df [-Pkmh] [FILESYSTEM]... ~ # df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs 25332856253272 0% /dev /dev/sdb1 193390193390 0 100% /cdrom ~ # lspci -knn 00:00.0 Host bridge [0600]: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller [8086:2590] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] 00:02.1 Display controller [0380]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2792] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d9] 00:1b.0 Audio device [0403]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) High Definition Audio Controller [8086:2668] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82a1] 00:1c.0 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 1 [8086:2660] (rev 04) Kernel driver in use: pcieport 00:1c.1 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 2 [8086:2662] (rev 04) Kernel driver in use: pcieport 00:1c.2 PCI bridge [0604]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) PCI Express Port 3 [8086:2664] (rev 04) Kernel driver in use: pcieport 00:1d.0 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #1 [8086:2658] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] Kernel driver in use: uhci_hcd 00:1d.1 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #2 [8086:2659] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] Kernel driver in use: uhci_hcd 00:1d.2 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #3 [8086:265a] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] Kernel driver in use: uhci_hcd 00:1d.3 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB UHCI #4 [8086:265b] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] Kernel driver in use: uhci_hcd 00:1d.7 USB Controller [0c03]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) USB2 EHCI Controller [8086:265c] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] Kernel driver in use: ehci_hcd 00:1e.0 PCI bridge [0604]: Intel Corporation 82801 Mobile PCI Bridge [8086:2448] (rev d4) 00:1f.0 ISA bridge [0601]: Intel Corporation 82801FBM (ICH6M) LPC Interface Bridge [8086:2641] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] 00:1f.2 IDE interface [0101]: Intel Corporation 82801FBM (ICH6M) SATA Controller [8086:2653] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] Kernel driver in use: ata_piix 00:1f.3 SMBus [0c05]: Intel Corporation 82801FB/FBM/FR/FW/FRW (ICH6 Family) SMBus Controller [8086:266a] (rev 04) Subsystem: ASUSTeK Computer Inc. Device [1043:82d8] 01:00.0 Ethernet controller [0200]: Atheros Communications Inc. AR5001 Wireless Network Adapter [168c:001c] (rev 01) Subsystem: AzureWave Device [1a3b:1026] Kernel driver in use: ath5k 03:00.0 Ethernet controller [0200]: Atheros Communications L2 Fast Ethernet [1969:2048] (rev a0) Subsystem: ASUSTeK Computer Inc. Device [1043:8233] Kernel driver in use: atl2 Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below),
Bug#623542: marked as done ([linux-image-2.6.38-2-amd64] Watchdog detected hard LOCKUP)
Your message dated Mon, 24 Jun 2013 19:30:55 +0200 with message-id <20130624173054.GB22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #623542, regarding [linux-image-2.6.38-2-amd64] Watchdog detected hard LOCKUP to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 623542: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623542 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.38-2-amd64 Version: 2.6.38-3 Severity: normal --- Please enter the report below this line. --- Apr 20 21:29:25 desk1 kernel: [709752.833704] [ cut here ] Apr 20 21:29:25 desk1 kernel: [709752.833704] WARNING: at /build/buildd-linux-2.6_2.6.38-3-amd64-4XBLY6/linux-2.6-2.6.38/debian/build/source_amd64_none/kernel/watchdog.c:226 watchdog_overflow_callback+0x96/0xa1() Apr 20 21:29:25 desk1 kernel: [709752.833704] Hardware name: System Product Name Apr 20 21:29:25 desk1 kernel: [709752.833704] Watchdog detected hard LOCKUP on cpu 3 Apr 20 21:29:25 desk1 kernel: [709752.833704] Modules linked in: nls_utf8 nls_cp437 vfat fat dm_mod powernow_k8 mperf cpufreq_powersave cpufreq_userspace cpufreq_stats cpufreq_conservative ppdev lp snd_hrtimer binfmt_misc fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc loop snd_hda_codec_via snd_usb_audio snd_usbmidi_lib snd_hda_intel snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_codec gspca_zc3xx gspca_main snd_hwdep snd_pcm videodev snd_seq snd_timer snd_seq_device snd v4l2_compat_ioctl32 soundcore snd_page_alloc evdev radeon ttm drm_kms_helper drm i2c_piix4 edac_core i2c_algo_bit edac_mce_amd i2c_core processor power_supply button shpchp asus_atk0110 psmouse pcspkr parport_pc k10temp tpm_tis tpm tpm_bios parport pci_hotplug serio_raw thermal_sys ext3 jbd mbcache usbhid hid sg sd_mod sr_mod cdrom usb_storage crc_t10dif ata_generic uas ohci_hcd pata_atiixp floppy ahci libahci ehci_hcd libata usbcore r8169 scsi_mod mii nls_base [last unloaded: scsi_wait_scan] Apr 20 21:29:25 desk1 kernel: [709752.833704] Pid: 14344, comm: chromium-browse Not tainted 2.6.38-2-amd64 #1 Apr 20 21:29:25 desk1 kernel: [709752.833704] Call Trace: Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? warn_slowpath_common+0x78/0x8c Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? warn_slowpath_fmt+0x45/0x4a Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? watchdog_overflow_callback+0x96/0xa1 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? __perf_event_overflow+0x12a/0x189 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? x86_pmu_handle_irq+0x153/0x193 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? perf_event_nmi_handler+0x50/0x98 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? notifier_call_chain+0x2e/0x5b Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? notify_die+0x2d/0x32 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? do_nmi+0x63/0x206 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? nmi+0x20/0x30 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? rs600_page_flip+0x10a/0x1bf [radeon] Apr 20 21:29:25 desk1 kernel: [709752.833704] <> [] ? radeon_crtc_handle_flip+0x73/0x1b9 [radeon] Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? __wake_up+0x35/0x46 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? r600_irq_process+0x1a1/0x528 [radeon] Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? handle_IRQ_event+0x4c/0x10a Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? handle_fasteoi_irq+0x9e/0xdf Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? handle_irq+0x17/0x1f Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? do_IRQ+0x45/0xaa Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? ret_from_intr+0x0/0x15 Apr 20 21:29:25 desk1 kernel: [709752.833704] [] ? system_call_fastpath+0x16/0x1b Apr 20 21:29:25 desk1 kernel: [709752.833704] ---[ end trace ff314d3ef704fdec ]--- --- System information. --- Architecture: amd64 Kernel: Linux 2.6.38-2-amd64 Debian Release: wheezy/sid 990 testing www.debian-multimedia.org 990 testing security.debian.org 990 testing ftp.us.debian.org 500 unstable ftp.us.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== module-init-tools | 3.12-1 linux-base (>= 3~) | 3.2 initramfs-tools (>= 0.55) | 0.98.8 OR linux-initramfs-tool | Package Status (Version) | Installed =-+-=== firmware-bnx2 | firmware-bnx2x | firmware-ipw2x00 | firmware-ivtv | firmware-iwlwifi | firmware-linux | 0.29 firmware-li
Bug#623840: marked as done (linux-image-2.6.38-2-amd64: no sound via headphones)
Your message dated Mon, 24 Jun 2013 19:30:55 +0200 with message-id <20130624173054.GB22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #623840, regarding linux-image-2.6.38-2-amd64: no sound via headphones to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 623840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623840 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.38-2 Severity: normal Afer upgrading to 2.6.38, no sound comes out of headphones plugged into my headphones jack. It worked with 2.6.32-5-amd64. I'm using a Satellite T115D Here's the relevent lspci output: 0 jamie@chicken:~$ sudo lspci -vv -s 00:14.2 00:14.2 Audio device: ATI Technologies Inc SBx00 Azalia (Intel HDA) Subsystem: Toshiba America Info Systems Device ffe2 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- SERR- TAbort- SERR- GSI 22 (level, low) -> IRQ 22 [770849.729011] ohci_hcd :00:12.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [770849.729033] ohci_hcd :00:12.1: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [770849.729088] ehci_hcd :00:12.2: PCI INT B -> GSI 17 (level, low) -> IRQ 17 [770849.729110] ohci_hcd :00:13.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [770849.729131] ohci_hcd :00:13.1: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [770849.729154] ehci_hcd :00:13.2: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [770849.729179] HDA Intel :00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [770849.729225] radeon :01:05.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [770849.729230] radeon :01:05.0: setting latency timer to 64 [770849.756639] pcieport :00:05.0: wake-up capability disabled by ACPI [770849.756647] atl1c :08:00.0: PME# disabled [770849.756676] r8180 :09:00.0: PCI INT A -> GSI 18 (level, low) -> IRQ 18 [770849.756682] r8180: Bringing up iface [770849.955359] r8180: Card successfully reset [770850.698053] r8180: WIRELESS_MODE_G [770850.698055] [770850.730852] radeon :01:05.0: WB enabled [770850.763722] sd 0:0:0:0: [sda] Starting disk [770850.764052] [drm] ring test succeeded in 0 usecs [770850.764073] [drm] ib test succeeded in 0 usecs [770850.764076] [drm] Enabling audio support [770850.780756] HDA Intel :01:05.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [770850.780763] HDA Intel :01:05.1: setting latency timer to 64 [770850.796520] atl1c :08:00.0: irq 42 for MSI/MSI-X [770851.196082] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [770851.253310] ata1.00: configured for UDMA/100 [770856.236160] PM: resume of devices complete after 6507.341 msecs [770856.236371] PM: Finishing wakeup. [770856.236373] Restarting tasks ... [770856.236858] usb 2-5: USB disconnect, address 60 [770856.257587] done. [770856.257597] video LNXVIDEO:01: Restoring backlight state [770856.352103] usb 2-5: new high speed USB device using ehci_hcd and address 61 [770856.836873] usb 2-5: New USB device found, idVendor=064e, idProduct=d201 [770856.836879] usb 2-5: New USB device strings: Mfr=3, Product=1, SerialNumber=4 [770856.836884] usb 2-5: Product: USB 2.0 Camera [770856.836887] usb 2-5: Manufacturer: SuYin [770856.836890] usb 2-5: SerialNumber: CN031B-M08C-MI02-VS-R01.01.00 [770856.861567] uvcvideo: Found UVC 1.00 device USB 2.0 Camera (064e:d201) [770856.865171] input: USB 2.0 Camera as /devices/pci:00/:00:13.2/usb2/2-5/2-5:1.0/input/input71 [770972.720920] atl1c :08:00.0: atl1c: cable NIC Link is Up<100 Mbps Full Duplex> [771679.851163] virbr0: port 2(vnet1) entering forwarding state [771679.851824] device vnet1 left promiscuous mode [771679.851829] virbr0: port 2(vnet1) entering disabled state [771882.856818] virbr0: port 1(vnet0) entering forwarding state [771882.857585] device vnet0 left promiscuous mode [771882.857590] virbr0: port 1(vnet0) entering disabled state [772241.392242] HDA Intel :01:05.1: PCI INT B disabled [772241.397477] HDA Intel :00:14.2: PCI INT A disabled [772241.790852] HDA Intel :00:14.2: PCI INT A -> GSI 16 (level, low) -> IRQ 16 [772241.850728] input: HDA Digital PCBeep as /devices/pci:00/:00:14.2/input/input72 [772241.861964] HDA Intel :01:05.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19 [772241.862021] HDA Intel :01:05.1: setting latency timer to 64 [772578.688270] HDA Intel :01:05.1: PCI INT B disabled [772578.691913] HDA Intel :00:14.2: PCI INT A disabled [772649.439711]
Bug#623535: marked as done (linux-image-2.6.32-5-686: hibernation crash related to ttyACM on Dell 5550 HSPA card)
Your message dated Mon, 24 Jun 2013 19:30:55 +0200 with message-id <20130624173054.GB22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #623535, regarding linux-image-2.6.32-5-686: hibernation crash related to ttyACM on Dell 5550 HSPA card to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 623535: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623535 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.32-31 Severity: normal My Dell Latitude 2120, with a Dell 5550 HSPA card[1], crashes on resume from hibernation with the squeeze i386 686 kernel, but only if before hibernation I used the HSPA card. Steps to reproduce: boot press func- run pppd debug call hspa (which talks to /dev/ttyACM0) check network is working killlall pppd pm-hibernate boot again Observed behaviour varies. In each case the system appears to load the hibernation image from disk (for some reason I don't get a progress display even if it's working). But after that it might: - unexpectedly reset and go back to BIOS screen - sit with a black screen doing nothing - sort of resume but with an oops and then not shut down properly (this happened once - see trace below) If I don't use the ttyACM the problem doesn't arise. I'm not sure if it's necessary to actually run pppd; it may be that simply connecting to ttyACM0 with picocom is sufficient. I tried rmmod cdc_adm cdc_wdm before hibernating but it still crashed. [1] The Dell 5550 HSPA card is not available via Dell's website yet. I was told by the salesperson who sold me the laptop (without an operating system other than a FreeDOS CD thrown into the box) that they are having difficulty with Windows certification. This might mean that the card is buggy somehow of course. However, it does work: I'm able to connect via my cellular provider and exchange data. Ian. -- Package-specific info: ** Version: Linux version 2.6.32-5-686 (Debian 2.6.32-31) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Mar 8 21:36:00 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=/dev/mapper/vg--zealot-lv--root ro quiet ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [ 15.529033] mtrr: type mismatch for e000,1000 old: write-back new: write-combining [ 15.529043] [drm] MTRR allocation failed. Graphics performance may suffer. [ 15.530563] Changing max_res_mask to 0x [ 15.530569] Changing min_res_mask to 0x200d [ 15.531604] i915 :00:02.0: irq 29 for MSI/MSI-X [ 15.531620] [drm] set up 7M of stolen space [ 15.536660] Applying 4313 WARs [ 15.537775] wlc_bmac_attach:: deviceid 0x4727 nbands 1 board 0x10 macaddr: 68:a3:c4:6e:86:e4 [ 15.636618] [drm] initialized overlay support [ 15.658766] phy0: Selected rate control algorithm 'minstrel' [ 15.660416] wl_set_hint: Sending country code US to MAC80211 [ 15.660436] wl0: Broadcom BCM43xx 802.11 MAC80211 Driver 5.75.11 (1.82.8.0) (Compiled in . at 21:29:36 on Mar 8 2011) [ 15.660776] cfg80211: Calling CRDA for country: US [ 16.084108] [drm] Big FIFO is enabled [ 16.084122] [drm] Big FIFO is enabled [ 16.201026] Console: switching to colour frame buffer device 170x48 [ 16.215474] fb0: inteldrmfb frame buffer device [ 16.215479] registered panic notifier [ 16.271360] acpi device:22: registered as cooling_device4 [ 16.272984] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:00/input/input7 [ 16.273167] ACPI: Video Device [VID] (multi-head: yes rom: no post: no) [ 16.273340] ACPI Warning for \_SB_.PCI0.VID2._DOD: Return Package has no elements (empty) (20090903/nspredef-433) [ 16.273594] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A03:00/LNXVIDEO:01/input/input8 [ 16.273696] ACPI: Video Device [VID2] (multi-head: yes rom: no post: no) [ 16.273744] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 16.274527] HDA Intel :00:1b.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21 [ 16.274651] HDA Intel :00:1b.0: setting latency timer to 64 [ 16.434676] hda_codec: ALC269: BIOS auto-probing. [ 16.434909] hda_codec: connection list not available for 0x24 [ 16.435412] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input9 [ 17.437543] hda-intel: azx_get_response timeout, switching to polling mode: last cmd=0x002f0012 [ 18.341389] EXT3 FS on dm-1, internal journal [ 18.646156] loop: module loaded [ 19.509213] Adding 97648
Bug#623363: marked as done ([linux-2.6] after upgrading 2.6.32->2.6.38 can no longer hibernate with nouveau and NV11)
Your message dated Mon, 24 Jun 2013 19:30:55 +0200 with message-id <20130624173054.GB22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #623363, regarding [linux-2.6] after upgrading 2.6.32->2.6.38 can no longer hibernate with nouveau and NV11 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 623363: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623363 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: linux-image-2.6.38-2-686 Severity: normal Hello, After upgrading from debian kernel 2.6.32 to 2.6.38 my computer no longer hibernates. I switched to vanilla kernels and found the same issue. I git-bisected the problem and found a range of commits which caused the problem. (The specific commit could not be identified b/c the kernel doesn't compile.) I'm fairly certain that this hibernate problem is due to the kernel nouveau driver. When I use the old kernel nvidia driver the computer can hibernate. Also, the problem does not depend on whether or not X is running. I posted the bisection info to the kernel bugzilla. Should have I instead posted to https://bugs.freedesktop.org? (This was recommended in a different nouveau bug.) https://bugzilla.kernel.org/show_bug.cgi?id=33582 Thanks! C. --- System information. --- Architecture: i386 Kernel: Linux 2.6.38.2 Debian Release: wheezy/sid 990 testing security.debian.org 990 testing debian.uchicago.edu 500 stable mirror.cs.wisc.edu 50 unstableftp.egr.msu.edu 49 experimentalftp.us.debian.org 10 testing mirror.csclub.uwaterloo.ca --- Package information. --- Package's Depends field is empty. Package's Recommends field is empty. Package's Suggests field is empty. --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#623365: marked as done (linux-image-2.6.38-1-amd64: cancelling suspend to disk causes GPU reset loop)
Your message dated Mon, 24 Jun 2013 19:30:55 +0200 with message-id <20130624173054.GB22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #623365, regarding linux-image-2.6.38-1-amd64: cancelling suspend to disk causes GPU reset loop to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 623365: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623365 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.38-1 Severity: normal Starting hibernate starts uswsusp which in turn starts saving kernel state to disk. While doing so pressing backspace cancels the operation. After the system "resumes" without really going down GPU keeps resetting and X locks up. Killing X restores the system. Going through full suspend/resume works flawlessly. For further testing linux 2.6.39-rc3 or later is required. The 2.6.38-2 in debian does AFAIK not support suspend and resume. -- Package-specific info: ** Version: Linux version 2.6.38-1-amd64 (Debian 2.6.38-1) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-14) ) #1 SMP Wed Mar 16 17:38:02 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-1-amd64 root=UUID=3b8f6a64-5899-462a-aec0-6ddefd878ecf ro fbcon=rotate:3 quiet ** Tainted: WO (4608) * Taint on warning. * Out-of-tree module has been loaded. ** Kernel log: [1526776.060061] Modules linked in: snd_seq_dummy nls_iso8859_1 nls_cp437 vfat fat uinput binfmt_misc vboxnetadp(O) vboxnetflt(O) vboxdrv(O) kvm_intel kvm bridge stp xt_tcpudp xt_conntrack xt_state xt_dscp xt_DSCP xt_CLASSIFY ipt_LOG ipt_REJECT xt_owner nf_conntrack_tftp nf_nat_ftp nf_conntrack_ftp nf_nat_sip nf_conntrack_sip nf_nat_h323 nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_conntrack_proto_gre nf_nat_proto_gre nf_nat_irc nf_conntrack_irc iptable_filter iptable_nat ipt_MASQUERADE nf_nat xt_multiport xt_iprange nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables tun fuse snd_pcm_oss snd_mixer_oss coretemp loop snd_hda_codec_hdmi snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_hwdep snd_pcm usbhid hid snd_seq snd_timer snd_seq_device snd soundcore snd_page_alloc parport_pc i2c_i801 parport psmouse dcdbas dell_wmi evdev sparse_keymap tpm_tis tpm tpm_bios processor wmi thermal_sys pcspkr button serio_raw ext3 jbd mbcache usb_storage uas sg sd_mod sr _mod crc_t10dif cdrom uhci_hcd radeon ttm drm_kms_helper ahci libahci drm e1000e ata_generic libata ehci_hcd usbcore scsi_mod i2c_algo_bit i2c_core power_supply nls_base [last unloaded: scsi_wait_scan] [1526776.060132] Pid: 10829, comm: Xorg Tainted: GW O 2.6.38-1-amd64 #1 [1526776.060134] Call Trace: [1526776.060142] [] ? warn_slowpath_common+0x78/0x8c [1526776.060145] [] ? warn_slowpath_fmt+0x45/0x4a [1526776.060161] [] ? radeon_fence_wait+0x2a9/0x34b [radeon] [1526776.060166] [] ? autoremove_wake_function+0x0/0x2a [1526776.060182] [] ? radeon_ib_get+0x101/0x1a5 [radeon] [1526776.060199] [] ? radeon_cs_ioctl+0x81/0x191 [radeon] [1526776.060216] [] ? radeon_gem_get_tiling_ioctl+0x87/0x94 [radeon] [1526776.060225] [] ? drm_ioctl+0x24e/0x321 [drm] [1526776.060241] [] ? radeon_cs_ioctl+0x0/0x191 [radeon] [1526776.060246] [] ? do_page_fault+0x314/0x34c [1526776.060250] [] ? do_vfs_ioctl+0x467/0x4b4 [1526776.060254] [] ? sys_ioctl+0x4b/0x70 [1526776.060257] [] ? system_call_fastpath+0x16/0x1b [1526776.060260] ---[ end trace 61a6667a3ce866d7 ]--- [1526776.061354] radeon :01:00.0: GPU softreset [1526776.061357] radeon :01:00.0: GRBM_STATUS=0xB2703828 [1526776.061360] radeon :01:00.0: GRBM_STATUS_SE0=0x1C07 [1526776.061362] radeon :01:00.0: GRBM_STATUS_SE1=0x0007 [1526776.061365] radeon :01:00.0: SRBM_STATUS=0x20C0 [1526776.061375] radeon :01:00.0: GRBM_SOFT_RESET=0x7F6B [1526776.061478] radeon :01:00.0: GRBM_STATUS=0x3828 [1526776.061481] radeon :01:00.0: GRBM_STATUS_SE0=0x0007 [1526776.061483] radeon :01:00.0: GRBM_STATUS_SE1=0x0007 [1526776.061486] radeon :01:00.0: SRBM_STATUS=0x20C0 [1526776.062482] radeon :01:00.0: GPU reset succeed [1526776.128397] radeon :01:00.0: WB enabled [1526776.144410] [drm] ring test succeeded in 0 usecs [1526776.144418] [drm] ib test succeeded in 1 usecs [1526778.083233] [drm:drm_mode_getfb] *ERROR* invalid framebuffer id [1526790.684022] radeon :01:00.0: GPU lockup CP stall for more than 1msec [1526790.684025] [ cut here ] [1526790.684052] WARNING: at /build/buildd-linux-2.6_2.6.38-1-amd64-t80ZCo/linux-
Bug#623066: marked as done (linux-image-2.6.38-2-686: Module acer-wmi is not loaded on Acer Aspire 5610 (regression))
Your message dated Mon, 24 Jun 2013 19:27:57 +0200 with message-id <20130624172757.GA22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #623066, regarding linux-image-2.6.38-2-686: Module acer-wmi is not loaded on Acer Aspire 5610 (regression) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 623066: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623066 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-2.6 Version: 2.6.38-3 Severity: normal Hi, I have Debian testing on an Acer Aspire 5610. The acer-wmi module was always loaded automatically, without me having to do something. after an upgrade to 2.6.38, i noticed that i could no longer turn my wireless on and off via /sys/devices/platform/acer-wmi/rfkill0/state, however, after modprobe acer-wmi, everything still works fine. so the only problem is that the module is not loaded by default, as it was with the previous kernel, and as it should be on acer hardware i think. btw it's not blacklisted tell me in case you need more information, greetings andreas -- Package-specific info: ** Version: Linux version 2.6.38-2-686 (Debian 2.6.38-3) (b...@decadent.org.uk) (gcc version 4.4.5 (Debian 4.4.5-15) ) #1 SMP Thu Apr 7 05:24:21 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.38-2-686 root=/dev/mapper/aspire-lv1 ro quiet ** Tainted: O (4096) * Out-of-tree module has been loaded. ** Kernel log: [93916.472034] wlan0: no IPv6 routers present [95276.916675] wlan0: deauthenticating from 00:01:e3:e5:8a:36 by local choice (reason=3) [95276.956685] cfg80211: Calling CRDA for country: AT [95277.028257] b44 ssb0:0: eth0: powering down PHY [95277.492725] PM: Marking nosave pages: 0009f000 - 0010 [95277.492733] PM: Basic memory bitmaps created [95277.492735] PM: Syncing filesystems ... done. [95277.513970] Freezing user space processes ... (elapsed 0.01 seconds) done. [95277.528111] Freezing remaining freezable tasks ... (elapsed 0.01 seconds) done. [95277.544186] PM: Preallocating image memory... done (allocated 280983 pages) [95279.204363] PM: Allocated 1123932 kbytes in 1.66 seconds (677.06 MB/s) [95279.204367] Suspending console(s) (use no_console_suspend to debug) [95279.252684] ACPI handle has no context! [95279.252695] sdhci-pci :06:04.4: PCI INT B disabled [95279.252703] ACPI handle has no context! [95279.252809] ACPI handle has no context! [95279.252815] sdhci-pci :06:04.2: PCI INT B disabled [95279.252823] ACPI handle has no context! [95279.252907] b44 :06:01.0: PCI INT A disabled [95279.252997] pci :00:1f.3: PCI INT B disabled [95279.356125] HDA Intel :00:1b.0: PCI INT A disabled [95279.456036] sd 0:0:0:0: [sda] Synchronizing SCSI cache [95279.456340] ata2: port disabled. ignoring. [95279.456402] ata_piix :00:1f.1: PCI INT B disabled [95279.456417] PM: freeze of devices complete after 228.013 msecs [95279.457740] PM: late freeze of devices complete after 1.318 msecs [95279.458164] ACPI: Preparing to enter system sleep state S4 [95279.460589] PM: Saving platform NVS memory [95279.464980] Disabling non-boot CPUs ... [95279.600031] CPU 1 is now offline [95279.604246] PM: Creating hibernation image: [95279.608007] PM: Need to copy 131902 pages [95279.608007] PM: Normal pages needed: 41024 + 1024, available pages: 186154 [95279.608007] PM: Restoring platform NVS memory [95279.608007] Enabling non-boot CPUs ... [95279.608007] Booting Node 0 Processor 1 APIC 0x1 [95279.497481] Initializing CPU#1 [95279.696021] Switched to NOHz mode on CPU #1 [95279.752310] NMI watchdog enabled, takes one hw-pmu counter. [95279.756033] CPU1 is up [95279.756902] ACPI: Waking up from system sleep state S4 [95279.757524] HDA Intel :00:1b.0: restoring config space at offset 0x1 (was 0x100106, writing 0x100102) [95279.757572] pcieport :00:1c.0: restoring config space at offset 0x7 (was 0x2020, writing 0x20002020) [95279.757645] pcieport :00:1c.1: restoring config space at offset 0x7 (was 0x3030, writing 0x20003030) [95279.757717] pcieport :00:1c.2: restoring config space at offset 0x7 (was 0x4040, writing 0x20004040) [95279.757788] pcieport :00:1c.3: restoring config space at offset 0x7 (was 0x5050, writing 0x20005050) [95279.758017] pci :00:1e.0: restoring config space at offset 0x6 (was 0x20070600, writing 0x200a0600) [95279.758111] ata_piix :00:1f.1: restoring config space at offset 0x1 (was 0x2880001, writing 0x2880005) [95279.758300] iwl3945 :05:00.0: restoring config space at offset 0x1 (was 0x100106, writing 0x10050
Bug#538081: marked as done (linux-image-2.6.26-2-amd64: The fan that doesn't adapt the speed to the cpu load. The Laptop shuts down by overheating)
Your message dated Mon, 24 Jun 2013 19:27:57 +0200 with message-id <20130624172757.GA22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #538081, regarding linux-image-2.6.26-2-amd64: The fan that doesn't adapt the speed to the cpu load. The Laptop shuts down by overheating to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 538081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=538081 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-2-amd64 Version: 2.6.26-17 Severity: normal -- Package-specific info: -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) Locale: LANG=pt_PT.UTF-8, LC_CTYPE=pt_PT.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.26-2-amd64 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.3 tools for generating an initramfs ii module-init-tools 3.9-2 tools for managing Linux kernel mo linux-image-2.6.26-2-amd64 recommends no packages. Versions of packages linux-image-2.6.26-2-amd64 suggests: ii grub 0.97-53GRand Unified Bootloader (Legacy v pn linux-doc-2.6.26 (no description available) -- debconf information: shared/kernel-image/really-run-bootloader: true linux-image-2.6.26-2-amd64/postinst/bootloader-error-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/lilo-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/depmod-error-2.6.26-2-amd64: false linux-image-2.6.26-2-amd64/postinst/old-dir-initrd-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/create-kimage-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/initrd-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/lilo-has-ramdisk: linux-image-2.6.26-2-amd64/preinst/abort-install-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/postinst/old-initrd-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/depmod-error-initrd-2.6.26-2-amd64: false linux-image-2.6.26-2-amd64/postinst/bootloader-test-error-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/overwriting-modules-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/kimage-is-a-directory: linux-image-2.6.26-2-amd64/preinst/failed-to-move-modules-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/prerm/would-invalidate-boot-loader-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/postinst/old-system-map-link-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/abort-overwrite-2.6.26-2-amd64: linux-image-2.6.26-2-amd64/preinst/bootloader-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/preinst/elilo-initrd-2.6.26-2-amd64: true linux-image-2.6.26-2-amd64/prerm/removing-running-kernel-2.6.26-2-amd64: true --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#623275: marked as done (linux-2.6: [x86] Null pointer dereference in hrtick_start_fair)
Your message dated Mon, 24 Jun 2013 19:27:57 +0200
with message-id <20130624172757.GA22021@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #623275,
regarding linux-2.6: [x86] Null pointer dereference in hrtick_start_fair
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
623275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623275
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: linux-2.6
Version: 2.6.26-*
This is the same bug that was reported in PR 538332, that bug was
archived so submitting new changes here.
Sorry for not replying on the other bug earlier. I totally forgot about
this bug report, until I received multiple reports of hitting this bug
more often while running reboot loop tests on the debian (5.x) kernel,
and started looking at this closely.
First of all this is the panic message that we see.
<1>[ 1.890083] BUG: unable to handle kernel NULL pointer dereference at
<1>[ 1.890083] IP: [] hrtick_start_fair+0x63/0x12c
<4>[ 1.890083] *pde =
<0>[ 1.890083] Oops: [#1] SMP
<4>[ 1.890083] Modules linked in:
<4>[ 1.890083]
<4>[ 1.890083] Pid: 11, comm: khelper Not tainted (2.6.26-2-686 #1)
<4>[ 1.890083] EIP: 0060:[] EFLAGS: 00010046 CPU: 0
<4>[ 1.890083] EIP is at hrtick_start_fair+0x63/0x12c
<4>[ 1.890083] EAX: EBX: c1413ffc ECX: 0001 EDX: 0001
<4>[ 1.890083] ESI: df47d900 EDI: c1413fc0 EBP: df4bd228 ESP: df499f20
<4>[ 1.890083] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068
<0>[ 1.890083] Process khelper (pid: 11, ti=df498000 task=df48e8c0
task.ti=df498000)
<0>[ 1.890083] Stack: df4bd200 df4bd200 c02c4d40 df47d900 c1413fc0 0001
c0118966 c1413fc0
<0>[ 1.890083] df47d900 0001 c011898c df47d900 c1413fc0 c011b6fa 0003
0002
<0>[ 1.890083] df47feb0 df47fed4 0001 0001 c0118511 0003
df47fedc
<0>[ 1.890083] Call Trace:
<0>[ 1.890083] [] enqueue_task+0x52/0x5d
<0>[ 1.890083] [] activate_task+0x1b/0x26
<0>[ 1.890083] [] try_to_wake_up+0xaf/0xf1
<0>[ 1.890083] [] __wake_up_common+0x2e/0x58
<0>[ 1.890083] [] complete+0x28/0x36
<0>[ 1.890083] [] __call_usermodehelper+0x0/0x4b
<0>[ 1.890083] [] run_workqueue+0x74/0xf2
<0>[ 1.890083] [] worker_thread+0x0/0xbd
<0>[ 1.890083] [] worker_thread+0xb3/0xbd
<0>[ 1.890083] [] autoremove_wake_function+0x0/0x2d
<0>[ 1.890083] [] kthread+0x38/0x5d
<0>[ 1.890083] [] kthread+0x0/0x5d
<0>[ 1.890083] [] kernel_thread_helper+0x7/0x10
<0>[ 1.890083] ===
<0>[ 1.890083] Code: 00 b8 51 09 31 c0 e8 17 95 00 00 f6 05 40 45 37 c0 40 0f
84 d5 00 00 00 f6 87 28 04 00 00 04 0f 85 c8 00 00 00 8b 87 4c 04 00 00 <8b> 00
83 78 7c 00 0f 84 b6 00 00 00 83 7b 08 01 0f 86 ac 00 0
0
<0>[ 1.890083] EIP: [] hrtick_start_fair+0x63/0x12c SS:ESP
0068:df499f20
<4>[ 1.890083] ---[ end trace a7919e7f17c0a725 ]---
I think there maybe a race between hrtimer_start and hrtick_start_fair,
which can cause this.
The timer->base for the rq (run queue) of all possible cpu's is setup in
__hrtimer_init and at this time all cpu's rq.timer->base points to
cpu0's hrtimer_bases.
When cpu1 start running, the first time hrtimer_start gets called on
this cpu, it will try to change the base to the local cpu's base, as
seen in __hrtimer_init it is still pointing to cpu0's base, the switch
is done in switch_hrtimer_base.
At the time this is happening on cpu1, if cpu0 tries to access cpu1
runqueue's timer base (rq.timer->base), without calling lock_timer_base
it may see the null value. As seen in the stack trace this may happen,
when cpu0 might be trying to wake up a task which is on cpu1's runqueue,
and it may see rq.timer->base as NULL.
static inline struct hrtimer_clock_base *
switch_hrtimer_base(struct hrtimer *timer, struct hrtimer_clock_base *base)
{
/* See the comment in lock_timer_base() */
timer->base = NULL;<< after this, cpu0 might see
the base as NULL for cpu1's runqueue.
spin_unlock(&base->cpu_base->lock);
spin_lock(&new_base->cpu_base->lock);
timer->base = new_base;
}
I didn't dig when was the race introduced, but it seems to exist on
mainline 2.6.26 too, looking at recent kernels, the hrtimer code has
been revamped quite a bit here and the race doesn't exist on those
versions.
Can you please take a look at the analysis and let me know if you have
any comments.
Thanks,
Alok
--- End Message ---
--- Begin Message ---
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a s
Bug#541073: marked as done (issues with 152d:2338 JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge)
Your message dated Mon, 24 Jun 2013 19:27:57 +0200 with message-id <20130624172757.GA22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #541073, regarding issues with 152d:2338 JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 541073: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541073 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: normal deluged (bittorrent client) is using my external disk as download dir. I suppose that deluge read/write to many times and kernel reset disk. External disk (lsusb): Bus 001 Device 004: ID 152d:2338 JMicron Technology Corp. / JMicron USA Technology Corp. JM20337 Hi-Speed USB to SATA & PATA Combo Bridge -- Package-specific info: ** Version: Linux version 2.6.30-1-686 (Debian 2.6.30-5) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-15) ) #1 SMP Mon Aug 3 16:18:30 UTC 2009 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.30-1-686 root=/dev/sda1 ro quiet nosplash ** Tainted: P W (513) ** Kernel log: [12469.837080] usb 2-1.4.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [12469.837087] usb 2-1.4.2: Product: Flash Disk [12469.837092] usb 2-1.4.2: Manufacturer: ORP [12469.837097] usb 2-1.4.2: SerialNumber: 293424206251 [12469.837279] usb 2-1.4.2: configuration #1 chosen from 1 choice [12469.842694] scsi5 : SCSI emulation for USB Mass Storage devices [12469.849618] usb-storage: device found at 8 [12469.849624] usb-storage: waiting for device to settle before scanning [12474.848478] usb-storage: device scan complete [12474.849128] scsi 5:0:0:0: Direct-Access ORP Flash Disk 4.00 PQ: 0 ANSI: 2 [12474.850777] sd 5:0:0:0: [sdc] 517759 2048-byte hardware sectors: (1.06 GB/1011 MiB) [12474.851308] sd 5:0:0:0: [sdc] Write Protect is off [12474.851308] sd 5:0:0:0: [sdc] Mode Sense: 00 00 00 00 [12474.851308] sd 5:0:0:0: [sdc] Assuming drive cache: write through [12474.853826] sd 5:0:0:0: [sdc] 517759 2048-byte hardware sectors: (1.06 GB/1011 MiB) [12474.854277] sd 5:0:0:0: [sdc] Assuming drive cache: write through [12474.854290] sdc: sdc1 [12474.855527] sd 5:0:0:0: [sdc] Attached SCSI removable disk [12475.370305] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [12595.590507] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use) [12607.852148] device br0 entered promiscuous mode [12768.692090] device br0 left promiscuous mode [12857.566156] usb 2-1.4.2: USB disconnect, address 8 [18206.794132] usb 1-3: USB disconnect, address 3 [18207.810088] EXT3-fs error (device sdb2): ext3_find_entry: reading directory #8863745 offset 0 [18207.892453] EXT3-fs error (device sdb2): ext3_find_entry: reading directory #8863745 offset 0 [18207.892665] [ cut here ] [18207.892678] WARNING: at /build/buildd-linux-2.6_2.6.30-5-i386-Lff5qC/linux-2.6-2.6.30/debian/build/source_i386_none/fs/buffer.c:1152 mark_buffer_dirty+0x20/0x77() [18207.892686] Hardware name: 89185QG [18207.892690] Modules linked in: nls_utf8 nls_cp437 vfat fat nls_base ppdev parport_pc lp parport tuner_simple tuner_types tuner saa7115 sco bnep l2cap bluetooth uinput binfmt_misc vboxnetadp vboxnetflt cpufreq_userspace fuse nfsd exportfs nfs lockd fscache nfs_acl auth_rpcgss sunrpc ipt_ULOG ipt_LOG ip6table_filter ip6_tables xt_time xt_connlimit xt_helper xt_realm xt_NFQUEUE xt_hashlimit xt_tcpmss xt_tcpudp ipt_addrtype xt_pkttype iptable_raw xt_CLASSIFY xt_CONNMARK xt_MARK xt_comment ipt_REJECT xt_length xt_connmark xt_owner xt_recent xt_iprange xt_physdev xt_policy xt_multiport xt_conntrack xt_state iptable_mangle iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 iptable_filter ip_tables x_tables bridge stp vboxdrv cpufreq_powersave cpufreq_conservative cpufreq_stats acpi_cpufreq nvidia(P) firewire_sbp2 firewire_core crc_itu_t loop snd_hda_codec_analog arc4 snd_hda_intel ecb snd_hda_codec snd_hwdep iwlagn snd_pcm_oss snd_mixer_oss iwlcore snd_pcm snd_seq_m idi usbvision snd_rawmidi v4l2_common snd_seq_midi_event videodev joydev snd_seq snd_timer snd_seq_device pcmcia v4l1_compat mac80211 snd usbhid soundcore yenta_socket hid rsrc_nonstatic pcmcia_core snd_page_alloc thinkpad_acpi i2c_i801 cfg80211 rfkill i2c_core serio_raw processor nvram psmouse pcspkr wmi button ac battery evdev ext3 jbd mbcache sd_mod crc_t10dif ide_cd_mod cdrom ata_generic usb_storage uhci_hcd id
Bug#539059: marked as done (Suspending SATA hard disks degrades software RAID 1)
Your message dated Mon, 24 Jun 2013 19:27:57 +0200 with message-id <20130624172757.GA22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #539059, regarding Suspending SATA hard disks degrades software RAID 1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 539059: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=539059 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.30-1-amd64 Version: 2.6.30-3 I just discovered that when I power down my hard disks using "hdparm -Y", md doesn't take it too well, and disables one of the drives: [ 3538.565135] ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 3538.565138] ata2.00: waking up from sleep [ 3538.565144] ata2: hard resetting link [ 3538.565154] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 [ 3538.565156] ata1.00: waking up from sleep [ 3538.565160] ata1: hard resetting link [ 3538.884034] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 3538.884050] ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) [ 3538.895775] ata1.00: configured for UDMA/133 [ 3538.895789] ata1: EH complete [ 3538.895884] ata2.00: configured for UDMA/133 [ 3538.895889] ata2: EH complete [ 3542.893071] end_request: I/O error, dev sdb, sector 175815231 [ 3542.893077] md: super_written gets error=-5, uptodate=0 [ 3542.893081] raid1: Disk failure on sdb1, disabling device. [ 3542.893083] raid1: Operation continuing on 1 devices. [ 3543.340822] end_request: I/O error, dev sda, sector 175815231 [ 3543.340827] md: super_written gets error=-5, uptodate=0 [ 3543.357427] RAID1 conf printout: [ 3543.357429] --- wd:1 rd:2 [ 3543.357432] disk 0, wo:0, o:1, dev:sda1 [ 3543.357435] disk 1, wo:1, o:0, dev:sdb1 [ 3543.372026] RAID1 conf printout: [ 3543.372029] --- wd:1 rd:2 [ 3543.372032] disk 0, wo:0, o:1, dev:sda1 This is probably some sort of "don't do it" scenario, but it still looks like a bug to me. --- End Message --- --- Begin Message --- Hi, your bug has been filed against the "linux-2.6" source package and was filed for a kernel older than the recently released Debian 7.x / Wheezy with a severity less than important. We don't have the ressources to reproduce the complete backlog of all older kernel bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy or a more recent kernel from testing or unstable, please reopen the bug by sending a mail to cont...@bugs.debian.org with the following three commands included in the mail: reopen BUGNUMBER reassign BUGNUMBER src:linux thanks Cheers, Moritz--- End Message ---
Bug#542440: marked as done (linux-image-2.6.26-2-686: pcimcia sata not detecting dvd burner)
Your message dated Mon, 24 Jun 2013 19:27:57 +0200 with message-id <20130624172757.GA22021@pisco.westfalen.local> and subject line Closing has caused the Debian Bug report #542440, regarding linux-image-2.6.26-2-686: pcimcia sata not detecting dvd burner to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 542440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=542440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: linux-image-2.6.26-2-686 Version: 2.6.26-17 Severity: normal *** Please type your report below this line *** I have pcmcia sata card working on chipset Silicon Image Sil 3512. My previous distribution was Kubutu Jaunty. Under Debian Lenny Pioneer dvd-writer connected to this card not working. On Kubuntu everything working fine. -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-17) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Sun Jun 21 04:57:38 UTC 2009 ** Command line: root=/dev/sda1 ro quiet ** Not tainted ** Kernel log: [ 41.792026] ata4: link is slow to respond, please be patient (ready=-19) [ 71.472024] ata4: COMRESET failed (errno=-16) [ 76.496026] ata4: COMRESET failed (errno=-16) [ 76.496098] ata4: reset failed, giving up [ 76.816081] ata5: SATA link down (SStatus 0 SControl 310) [ 77.736012] Adding 1951888k swap on /dev/sda3. Priority:-1 extents:1 across:1951888k [ 78.117075] EXT3 FS on sda1, internal journal [ 78.308838] loop: module loaded [ 79.292071] fuse init (API version 7.9) [ 79.344043] kjournald starting. Commit interval 5 seconds [ 79.344075] EXT3 FS on sda5, internal journal [ 79.344075] EXT3-fs: mounted filesystem with ordered data mode. [ 79.344430] kjournald starting. Commit interval 5 seconds [ 79.344462] EXT3 FS on sda6, internal journal [ 79.344462] EXT3-fs: mounted filesystem with ordered data mode. [ 82.421242] NET: Registered protocol family 10 [ 82.421592] lo: Disabled Privacy Extensions [ 82.64] lp: driver loaded but no devices found [ 82.637025] ppdev: user-space parallel port driver [ 85.880544] input: b43-phy0 as /class/input/input8 [ 85.968068] firmware: requesting b43/ucode5.fw [ 86.060298] firmware: requesting b43/pcm5.fw [ 86.072580] firmware: requesting b43/b0g0initvals5.fw [ 86.079677] firmware: requesting b43/b0g0bsinitvals5.fw [ 86.200044] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 87.524473] Registered led device: b43-phy0::tx [ 87.524492] Registered led device: b43-phy0::rx [ 87.524508] Registered led device: b43-phy0::radio [ 87.576259] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 87.983794] Bluetooth: Core ver 2.11 [ 87.984953] NET: Registered protocol family 31 [ 87.984958] Bluetooth: HCI device and connection manager initialized [ 87.984961] Bluetooth: HCI socket layer initialized [ 88.001570] Bluetooth: L2CAP ver 2.9 [ 88.001575] Bluetooth: L2CAP socket layer initialized [ 88.249126] Bluetooth: RFCOMM socket layer initialized [ 88.249140] Bluetooth: RFCOMM TTY layer initialized [ 88.249141] Bluetooth: RFCOMM ver 1.8 [ 88.695197] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 91.011429] input: b43-phy0 as /class/input/input9 [ 91.208034] b43-phy0: Loading firmware version 410.2160 (2007-05-26 15:32:10) [ 92.087257] [drm] Initialized drm 1.1.0 20060810 [ 92.093782] ACPI: PCI Interrupt :00:02.0[A] -> GSI 16 (level, low) -> IRQ 16 [ 92.093792] PCI: Setting latency timer of device :00:02.0 to 64 [ 92.093869] [drm] Initialized i915 1.6.0 20060119 on minor 0 [ 93.296496] Registered led device: b43-phy0::tx [ 93.296518] Registered led device: b43-phy0::rx [ 93.296534] Registered led device: b43-phy0::radio [ 93.348287] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 94.972100] wlan0: Initial auth_alg=0 [ 94.972107] wlan0: authenticate with AP 00:21:27:e3:95:e8 [ 94.972577] wlan0: Initial auth_alg=0 [ 94.972582] wlan0: authenticate with AP 00:21:27:e3:95:e8 [ 94.973545] wlan0: RX authentication from 00:21:27:e3:95:e8 (alg=0 transaction=2 status=0) [ 94.973550] wlan0: authenticated [ 94.973553] wlan0: associate with AP 00:21:27:e3:95:e8 [ 94.980009] wlan0: authentication frame received from 00:21:27:e3:95:e8, but not in authenticate state - ignored [ 94.980074] wlan0: RX AssocResp from 00:21:27:e3:95:e8 (capab=0x431 status=0 aid=1) [ 94.980074] wlan0: associated [ 94.980074] wlan0: switched to short barker preamble (BSSID=00:21:27:e3:95:e8) [ 94.980074] ADDRCONF(NETDEV_CHANGE):
Bug#704242: Driver for PL-2303 HX not working
Am 24.06.2013 18:38, schrieb Aric Fedida: I will gladly ship you one. Give me address details, and I'll go to the post office to send it. Personally, I have resolved to abandon the PL2303 chip, and move to FTDI instead. But for the sake of other Linux users who might buy that adapter by mistake, I am willing to donate the hardware to an able kernel hacker :-) Yes - i will also spend $1,67 and buy one to send to the right destination address to help to solve the problem. Just let me know ... The advantage of this universal adapters is that you can simply shorten RXD and TXD for a loop with one of the included cables. Karsten -- 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/51c87a3e.20...@dct.mine.nu
Bug#704242: Fwd: Re: Bug#704242: Driver for PL-2303 HX not working
Hello Greg, Am 24.06.2013 18:17, schrieb Greg KH: On Mon, Jun 24, 2013 at 10:41:07AM +0200, Karsten Malcher wrote: Hello Greg, have you buyed one of this jinxed PL-2303 HX adapters? No, I have not been able to find one. Does anyone know where I can purchase one? Just take this one: http://www.ebay.com/itm/USB-To-RS232-TTL-PL2303HX-Auto-Converter-Module-5V-3-3V-Output-Converter-Adapter-/370812126675 US $1.67 and it is yours. Yesterday i got this interesting mail from Aric, who has analyzed a similar problem with this chip. I think something went wrong in the usb serial handling, but not in the driver itself. But the error is really complicate to figure out in the depth of the software. The really annoying thing is that it worked with kernel 2.6.32. That's a really long time ago, loads of things have changed since then. If someone can run 'git bisect' to track down the problem, that would be wonderful. Yes - that would reduce the problem. But i think it must be debugged with the correspondend hardware too, or not? thanks, greg k-h Cheers Karsten -- 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/51c876c2.6080...@dct.mine.nu
Bug#704242: Driver for PL-2303 HX not working
I will gladly ship you one. Give me address details, and I'll go to the post office to send it. Personally, I have resolved to abandon the PL2303 chip, and move to FTDI instead. But for the sake of other Linux users who might buy that adapter by mistake, I am willing to donate the hardware to an able kernel hacker :-) Aric Fedida -- Mobile: +1.609.422.0311 Skype: AricFedidaNSA On Jun 24, 2013, at 12:17 PM, Greg KH wrote: > On Mon, Jun 24, 2013 at 10:41:07AM +0200, Karsten Malcher wrote: >> Hello Greg, >> >> have you buyed one of this jinxed PL-2303 HX adapters? > > No, I have not been able to find one. Does anyone know where I can > purchase one? > >> Yesterday i got this interesting mail from Aric, who has analyzed a >> similar problem with this chip. I think something went wrong in the >> usb serial handling, but not in the driver itself. But the error is >> really complicate to figure out in the depth of the software. >> >> The really annoying thing is that it worked with kernel 2.6.32. > > That's a really long time ago, loads of things have changed since then. > If someone can run 'git bisect' to track down the problem, that would be > wonderful. > > thanks, > > greg k-h -- 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/635e6aeb-a241-4f45-a980-3f2107faf...@nsa.co.il
Bug#704242: Fwd: Re: Bug#704242: Driver for PL-2303 HX not working
On Mon, Jun 24, 2013 at 10:41:07AM +0200, Karsten Malcher wrote: > Hello Greg, > > have you buyed one of this jinxed PL-2303 HX adapters? No, I have not been able to find one. Does anyone know where I can purchase one? > Yesterday i got this interesting mail from Aric, who has analyzed a > similar problem with this chip. I think something went wrong in the > usb serial handling, but not in the driver itself. But the error is > really complicate to figure out in the depth of the software. > > The really annoying thing is that it worked with kernel 2.6.32. That's a really long time ago, loads of things have changed since then. If someone can run 'git bisect' to track down the problem, that would be wonderful. thanks, greg k-h -- 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/20130624161702.ga16...@kroah.com
Processed: reassign 598644 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 598644 src:linux Bug #598644 [linux-2.6] linux-2.6: README.Debian gets installed in the wrong package Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 2.6.32-24. Ignoring request to alter fixed versions of bug #598644 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 598644: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=598644 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.1372089288.transcr...@bugs.debian.org
Processed: reassign 706999 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 706999 src:linux Bug #706999 [linux-2.6] Writing ISO to USB results in an unkillable blkid process Bug reassigned from package 'linux-2.6' to 'src:linux'. Ignoring request to alter found versions of bug #706999 to the same values previously set Ignoring request to alter fixed versions of bug #706999 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 706999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706999 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.13720892782157.transcr...@bugs.debian.org
Processed: reassign 706818 to src:linux
Processing commands for cont...@bugs.debian.org: > reassign 706818 src:linux Bug #706818 [linux-2.6] NFSv4.1 breaks suspend Bug reassigned from package 'linux-2.6' to 'src:linux'. No longer marked as found in versions 3.2.41-2. Ignoring request to alter fixed versions of bug #706818 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 706818: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706818 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.13720892822183.transcr...@bugs.debian.org
Processed: snd-powermac
Processing commands for cont...@bugs.debian.org:
> reopen 609747
Bug #609747 {Done: Moritz Mühlenhoff } [linux-2.6] udev:
snd-powermac.ko not loaded automatically on iBook (first generation), resulting
in no audio
Bug reopened
Ignoring request to alter fixed versions of bug #609747 to the same values
previously set
> reassign 609747 src:linux
Bug #609747 [linux-2.6] udev: snd-powermac.ko not loaded automatically on iBook
(first generation), resulting in no audio
Bug reassigned from package 'linux-2.6' to 'src:linux'.
Ignoring request to alter found versions of bug #609747 to the same values
previously set
Ignoring request to alter fixed versions of bug #609747 to the same values
previously set
> found 609747 3.2.46-1
Bug #609747 [src:linux] udev: snd-powermac.ko not loaded automatically on iBook
(first generation), resulting in no audio
Marked as found in versions linux/3.2.46-1.
> found 609747 3.9.6-1
Bug #609747 [src:linux] udev: snd-powermac.ko not loaded automatically on iBook
(first generation), resulting in no audio
Marked as found in versions linux/3.9.6-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
609747: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609747
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.137208159421226.transcr...@bugs.debian.org
Bug#609747: snd-powermac
reopen 609747 reassign 609747 src:linux found 609747 3.2.46-1 found 609747 3.9.6-1 thanks It looks to me like snd-powermac still has this issue of not knowing to load automatically. I've confirmed it on the above two kernels. --dkg signature.asc Description: OpenPGP digital signature
Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"
On Mon, Jun 24, 2013 at 01:59:34PM +0200, Stefan Pietsch wrote:
> On 24.06.2013 13:47, Gleb Natapov wrote:
> > On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote:
> >> On 23.06.2013 19:36, Gleb Natapov wrote:
> >>> On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote:
> On 23.06.2013 09:51, Gleb Natapov wrote:
> > On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote:
> >>> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94
> >>> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu
> >>> monitor after the hang.
> >>
> >>
> >> 25391454e73e3156202264eb3c473825afe4bc94
> >> emulate_invalid_guest_state=0
> >>
> > Very interesting. Looks like somewhere during TPR access FS
> > register gets corrupted. Can you remove /usr/share/kvm/kvmvapic.bin
> > and try again? This will disable some code paths during TPR access and
> > will narrow down the issue.
>
>
> Doing this, qemu complains
> "Could not open option rom 'kvmvapic.bin': No such file or directory",
> but the virtual machine boots successful with
> emulate_invalid_guest_state=0 and emulate_invalid_guest_state=1.
>
> >>> Hmm, I think we ate close. Can you try with upstream qemu?
> >>>
> kvmvapic.bin comes with Debian package "seabios 1.7.2-3".
> >>
> >> I already tried this with the Debian package qemu-kvm 1.5.0+dfsg-4.
> > And it didn't work? Mind trying some debug kernel patches? I suspect
> > your CPU does something no CPU I have do, so I want to verify it.
>
>
> As soon as I remove "kvmvapic.bin" the virtual machine boots with
> qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5.
> "emulate_invalid_guest_state=0" or "emulate_invalid_guest_state=1" make
> no difference.
>
> Please send your patches.
Here it is, run with it and kvmvapic.bin present. See what is printed in
dmesg after the failure.
diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
index f4a5b3f..65488a4 100644
--- a/arch/x86/kvm/vmx.c
+++ b/arch/x86/kvm/vmx.c
@@ -3385,6 +3385,7 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
{
struct vcpu_vmx *vmx = to_vmx(vcpu);
u32 ar;
+ unsigned long rip;
if (vmx->rmode.vm86_active && seg != VCPU_SREG_LDTR) {
*var = vmx->rmode.segs[seg];
@@ -3408,6 +3409,9 @@ static void vmx_get_segment(struct kvm_vcpu *vcpu,
var->db = (ar >> 14) & 1;
var->g = (ar >> 15) & 1;
var->unusable = (ar >> 16) & 1;
+ rip = kvm_rip_read(vcpu);
+ if ((rip == 0xc101611c || rip == 0xc101611a) && seg == VCPU_SREG_FS)
+ printk("base=%p limit=%p selector=%x ar=%x\n", var->base,
var->limit, var->selector, ar);
}
static u64 vmx_get_segment_base(struct kvm_vcpu *vcpu, int seg)
--
Gleb.
--
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/20130624123049.gh18...@redhat.com
Bug#713972: linux-image-3.10-rc5-powerpc: fails to boot (screen shows "setup_arch: bootmem" and "arch: exit")
Package: src:linux Version: 3.10~rc5-1~exp1 Severity: important linux 3.10-rc5 fails to boot on this machine. This machine boots 3.2.0-1-powerpc (from wheezy) just fine. when i try to boot 3.10-rc5, grub successfully loads the kernel and the initramfs, and appears to hand off control to the kernel, but then the machine hangs for several minutes, and ultimately reboots back to openfirmware. during the hang, the screen displays a little of the openfirmware info in reverse video (black on white): . Device tree strings 0x03525000 -> 0x03525bca Device tree struct 0x03526000 -> 0x0354 Calling quiesce... returning from prom_init and then overwritten over the top of that in normal video (white on black) is the following messages (i think from the kernel): setup_arch: bootmem arch: exit these same messages come up with kernel 3.2.0-1-powerpc, but that kernel also says something about hugetlb (before the above two messages, i think it's in the dmesg output below), but then continues to boot. I haven't yet tried kernel 3.9. --dkg -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information revision: 131.0 (pvr 0008 8300) platform: PowerMac model : PowerBook2,1 machine : PowerBook2,1 motherboard : PowerBook2,1 MacRISC Power Macintosh ** PCI devices: :00:0b.0 Host bridge [0600]: Apple Inc. UniNorth AGP [106b:0020] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: agpgart-uninorth :00:10.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Device [1002:4c4e] (rev 64) (prog-if 00 [VGA controller]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- SERR- Kernel driver in use: atyfb 0001:10:0b.0 Host bridge [0600]: Apple Inc. UniNorth PCI [106b:001f] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- TAbort- SERR- TAbort- SERR- (32-bit, non-prefetchable) [disabled] [size=4K] 0002:20:0b.0 Host bridge [0600]: Apple Inc. UniNorth Internal PCI [106b:001e] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- SERR- TAbort- SERR- pn linux-doc-3.10 pn mkvmlinuz Versions of packages linux-image-3.10-rc5-powerpc is related to: pn firmware-atheros pn firmware-bnx2 pn firmware-bnx2x pn firmware-brcm80211 pn firmware-intelwimax pn firmware-ipw2x00 pn firmware-ivtv pn firmware-iwlwifi pn firmware-libertas pn firmware-linux pn firmware-linux-nonfree pn firmware-myricom pn firmware-netxen pn firmware-qlogic pn firmware-ralink pn firmware-realtek pn xen-hypervisor -- debconf information: linux-image-3.10-rc5-powerpc/postinst/missing-firmware-3.10-rc5-powerpc: linux-image-3.10-rc5-powerpc/postinst/ignoring-ramdisk: linux-image-3.10-rc5-powerpc/prerm/removing-running-kernel-3.10-rc5-powerpc: true linux-image-3.10-rc5-powerpc/postinst/depmod-error-initrd-3.10-rc5-powerpc: 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/20130624121734.2377.34247.report...@clam.lair.fifthhorseman.net
Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"
On 24.06.2013 13:47, Gleb Natapov wrote: > On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote: >> On 23.06.2013 19:36, Gleb Natapov wrote: >>> On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote: On 23.06.2013 09:51, Gleb Natapov wrote: > On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote: >>> Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94 >>> and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu >>> monitor after the hang. >> >> >> 25391454e73e3156202264eb3c473825afe4bc94 >> emulate_invalid_guest_state=0 >> > Very interesting. Looks like somewhere during TPR access FS > register gets corrupted. Can you remove /usr/share/kvm/kvmvapic.bin > and try again? This will disable some code paths during TPR access and > will narrow down the issue. Doing this, qemu complains "Could not open option rom 'kvmvapic.bin': No such file or directory", but the virtual machine boots successful with emulate_invalid_guest_state=0 and emulate_invalid_guest_state=1. >>> Hmm, I think we ate close. Can you try with upstream qemu? >>> kvmvapic.bin comes with Debian package "seabios 1.7.2-3". >> >> I already tried this with the Debian package qemu-kvm 1.5.0+dfsg-4. > And it didn't work? Mind trying some debug kernel patches? I suspect > your CPU does something no CPU I have do, so I want to verify it. As soon as I remove "kvmvapic.bin" the virtual machine boots with qemu-kvm 1.5.0. I just verified this with Linux kernel 3.10.0-rc5. "emulate_invalid_guest_state=0" or "emulate_invalid_guest_state=1" make no difference. Please send your patches. -- 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/51c834a6.7030...@sp.consulting.lsexperts.de
Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"
On Mon, Jun 24, 2013 at 01:43:26PM +0200, Stefan Pietsch wrote: > On 23.06.2013 19:36, Gleb Natapov wrote: > > On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote: > >> On 23.06.2013 09:51, Gleb Natapov wrote: > >>> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote: > > Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94 > > and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu > > monitor after the hang. > > > 25391454e73e3156202264eb3c473825afe4bc94 > emulate_invalid_guest_state=0 > > >>> Very interesting. Looks like somewhere during TPR access FS > >>> register gets corrupted. Can you remove /usr/share/kvm/kvmvapic.bin > >>> and try again? This will disable some code paths during TPR access and > >>> will narrow down the issue. > >> > >> > >> Doing this, qemu complains > >> "Could not open option rom 'kvmvapic.bin': No such file or directory", > >> but the virtual machine boots successful with > >> emulate_invalid_guest_state=0 and emulate_invalid_guest_state=1. > >> > > Hmm, I think we ate close. Can you try with upstream qemu? > > > >> kvmvapic.bin comes with Debian package "seabios 1.7.2-3". > > I already tried this with the Debian package qemu-kvm 1.5.0+dfsg-4. And it didn't work? Mind trying some debug kernel patches? I suspect your CPU does something no CPU I have do, so I want to verify it. -- Gleb. -- 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/20130624114730.gf18...@redhat.com
Bug#707257: linux-image-3.8-1-686-pae: KVM crashes with "entry failed, hardware error 0x80000021"
On 23.06.2013 19:36, Gleb Natapov wrote: > On Sun, Jun 23, 2013 at 06:51:30PM +0200, Stefan Pietsch wrote: >> On 23.06.2013 09:51, Gleb Natapov wrote: >>> On Thu, Jun 20, 2013 at 07:01:49PM +0200, Stefan Pietsch wrote: > Can you provide the output of 25391454e73e3156202264eb3c473825afe4bc94 > and emulate_invalid_guest_state=0. Also run "x/20i $pc-20" in qemu > monitor after the hang. 25391454e73e3156202264eb3c473825afe4bc94 emulate_invalid_guest_state=0 >>> Very interesting. Looks like somewhere during TPR access FS >>> register gets corrupted. Can you remove /usr/share/kvm/kvmvapic.bin >>> and try again? This will disable some code paths during TPR access and >>> will narrow down the issue. >> >> >> Doing this, qemu complains >> "Could not open option rom 'kvmvapic.bin': No such file or directory", >> but the virtual machine boots successful with >> emulate_invalid_guest_state=0 and emulate_invalid_guest_state=1. >> > Hmm, I think we ate close. Can you try with upstream qemu? > >> kvmvapic.bin comes with Debian package "seabios 1.7.2-3". I already tried this with the Debian package qemu-kvm 1.5.0+dfsg-4. -- 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/51c830de.2010...@sp.consulting.lsexperts.de
linux_3.2.46-1~bpo60+1_multi.changes ACCEPTED into squeeze-backports->backports-policy, squeeze-backports
Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Thu, 16 May 2013 13:38:45 +0100 Source: linux Binary: linux-source-3.2 linux-doc-3.2 linux-manual-3.2 linux-support-3.2.0-0.bpo.4 linux-libc-dev linux-headers-3.2.0-0.bpo.4-all linux-headers-3.2.0-0.bpo.4-all-alpha linux-headers-3.2.0-0.bpo.4-common linux-image-3.2.0-0.bpo.4-alpha-generic linux-headers-3.2.0-0.bpo.4-alpha-generic linux-image-3.2.0-0.bpo.4-alpha-smp linux-headers-3.2.0-0.bpo.4-alpha-smp linux-image-3.2.0-0.bpo.4-alpha-legacy linux-headers-3.2.0-0.bpo.4-alpha-legacy linux-headers-3.2.0-0.bpo.4-all-amd64 linux-image-3.2.0-0.bpo.4-amd64 linux-headers-3.2.0-0.bpo.4-amd64 linux-image-3.2.0-0.bpo.4-amd64-dbg xen-linux-system-3.2.0-0.bpo.4-amd64 linux-headers-3.2.0-0.bpo.4-common-rt linux-image-3.2.0-0.bpo.4-rt-amd64 linux-headers-3.2.0-0.bpo.4-rt-amd64 linux-image-3.2.0-0.bpo.4-rt-amd64-dbg linux-headers-3.2.0-0.bpo.4-all-armel linux-image-3.2.0-0.bpo.4-iop32x linux-headers-3.2.0-0.bpo.4-iop32x linux-image-3.2.0-0.bpo.4-ixp4xx linux-headers-3.2.0-0.bpo.4-ixp4xx linux-image-3.2.0-0.bpo.4-kirkwood linux-headers-3.2.0-0.bpo.4-kirkwood linux-image-3.2.0-0.bpo.4-mv78xx0 linux-headers-3.2.0-0.bpo.4-mv78xx0 linux-image-3.2.0-0.bpo.4-orion5x linux-headers-3.2.0-0.bpo.4-orion5x linux-image-3.2.0-0.bpo.4-versatile linux-headers-3.2.0-0.bpo.4-versatile linux-headers-3.2.0-0.bpo.4-all-armhf linux-image-3.2.0-0.bpo.4-mx5 linux-headers-3.2.0-0.bpo.4-mx5 linux-image-3.2.0-0.bpo.4-omap linux-headers-3.2.0-0.bpo.4-omap linux-image-3.2.0-0.bpo.4-vexpress linux-headers-3.2.0-0.bpo.4-vexpress linux-headers-3.2.0-0.bpo.4-all-hppa linux-image-3.2.0-0.bpo.4-parisc linux-headers-3.2.0-0.bpo.4-parisc linux-image-3.2.0-0.bpo.4-parisc-smp linux-headers-3.2.0-0.bpo.4-parisc-smp linux-image-3.2.0-0.bpo.4-parisc64 linux-headers-3.2.0-0.bpo.4-parisc64 linux-image-3.2.0-0.bpo.4-parisc64-smp linux-headers-3.2.0-0.bpo.4-parisc64-smp linux-headers-3.2.0-0.bpo.4-all-i386 linux-image-3.2.0-0.bpo.4-486 linux-headers-3.2.0-0.bpo.4-486 linux-image-3.2.0-0.bpo.4-686-pae linux-headers-3.2.0-0.bpo.4-686-pae linux-image-3.2.0-0.bpo.4-686-pae-dbg xen-linux-system-3.2.0-0.bpo.4-686-pae linux-image-3.2.0-0.bpo.4-rt-686-pae linux-headers-3.2.0-0.bpo.4-rt-686-pae linux-image-3.2.0-0.bpo.4-rt-686-pae-dbg linux-headers-3.2.0-0.bpo.4-all-ia64 linux-image-3.2.0-0.bpo.4-itanium linux-headers-3.2.0-0.bpo.4-itanium linux-image-3.2.0-0.bpo.4-mckinley linux-headers-3.2.0-0.bpo.4-mckinley linux-headers-3.2.0-0.bpo.4-all-m68k linux-image-3.2.0-0.bpo.4-amiga linux-headers-3.2.0-0.bpo.4-amiga linux-image-3.2.0-0.bpo.4-atari linux-headers-3.2.0-0.bpo.4-atari linux-image-3.2.0-0.bpo.4-bvme6000 linux-headers-3.2.0-0.bpo.4-bvme6000 linux-image-3.2.0-0.bpo.4-mac linux-headers-3.2.0-0.bpo.4-mac linux-image-3.2.0-0.bpo.4-mvme147 linux-headers-3.2.0-0.bpo.4-mvme147 linux-image-3.2.0-0.bpo.4-mvme16x linux-headers-3.2.0-0.bpo.4-mvme16x linux-headers-3.2.0-0.bpo.4-all-mips linux-image-3.2.0-0.bpo.4-r4k-ip22 linux-headers-3.2.0-0.bpo.4-r4k-ip22 linux-image-3.2.0-0.bpo.4-r5k-ip32 linux-headers-3.2.0-0.bpo.4-r5k-ip32 linux-image-3.2.0-0.bpo.4-sb1-bcm91250a linux-headers-3.2.0-0.bpo.4-sb1-bcm91250a linux-image-3.2.0-0.bpo.4-sb1a-bcm91480b linux-headers-3.2.0-0.bpo.4-sb1a-bcm91480b linux-image-3.2.0-0.bpo.4-4kc-malta linux-headers-3.2.0-0.bpo.4-4kc-malta linux-image-3.2.0-0.bpo.4-5kc-malta linux-headers-3.2.0-0.bpo.4-5kc-malta linux-image-3.2.0-0.bpo.4-octeon linux-headers-3.2.0-0.bpo.4-octeon linux-headers-3.2.0-0.bpo.4-all-mipsel linux-image-3.2.0-0.bpo.4-r5k-cobalt linux-headers-3.2.0-0.bpo.4-r5k-cobalt linux-image-3.2.0-0.bpo.4-loongson-2f linux-headers-3.2.0-0.bpo.4-loongson-2f linux-headers-3.2.0-0.bpo.4-all-powerpc linux-image-3.2.0-0.bpo.4-powerpc linux-headers-3.2.0-0.bpo.4-powerpc linux-image-3.2.0-0.bpo.4-powerpc-smp linux-headers-3.2.0-0.bpo.4-powerpc-smp linux-image-3.2.0-0.bpo.4-powerpc64 linux-headers-3.2.0-0.bpo.4-powerpc64 linux-headers-3.2.0-0.bpo.4-all-ppc64 linux-headers-3.2.0-0.bpo.4-all-s390 linux-image-3.2.0-0.bpo.4-s390x linux-headers-3.2.0-0.bpo.4-s390x linux-image-3.2.0-0.bpo.4-s390x-dbg linux-image-3.2.0-0.bpo.4-s390x-tape linux-headers-3.2.0-0.bpo.4-all-s390x linux-headers-3.2.0-0.bpo.4-all-sh4 linux-image-3.2.0-0.bpo.4-sh7751r linux-headers-3.2.0-0.bpo.4-sh7751r linux-image-3.2.0-0.bpo.4-sh7785lcr linux-headers-3.2.0-0.bpo.4-sh7785lcr linux-headers-3.2.0-0.bpo.4-all-sparc linux-image-3.2.0-0.bpo.4-sparc64 linux-headers-3.2.0-0.bpo.4-sparc64 linux-image-3.2.0-0.bpo.4-sparc64-smp linux-headers-3.2.0-0.bpo.4-sparc64-smp linux-headers-3.2.0-0.bpo.4-all-sparc64 Architecture: all source Version: 3.2.46-1~bpo60+1 Distribution: squeeze-backports Urgency: high Maintainer: Debian Kernel Team Changed-By: Ben Hutchings Description: linux-doc-3.2 - Linux kernel specific documentation for version 3.2 linux-headers-3.2.0-0.bpo.4-486 - Header files for Linux 3.2.0-0.bpo.4-486 linux-headers-3.2.0-0.bpo.4-4kc-malta
