Bug#609191: Intel 82599EB 10 Gigabit TN not supported
tags 609191 + unreproducible quit Jonathan Nieder wrote: Jonathan Nieder wrote: Aaron Porter wrote: The dual-port model of Intel's PCIe 10g baset card is not supported in squeeze kernels. Upstream support for this NIC: [...] I'm attaching a blind backport of the commit you mentioned and a couple of other commits Do you still have access to this hardware? Assuming no, marking accordingly. -- 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/20120609061311.GA8592@burratino
Processed: Re: Intel 82599EB 10 Gigabit TN not supported
Processing commands for cont...@bugs.debian.org: tags 609191 + unreproducible Bug #609191 [linux-2.6] Intel 82599EB 10 Gigabit TN not supported Added tag(s) unreproducible. quit Stopping processing here. Please contact me if you need assistance. -- 609191: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609191 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.13392224079972.transcr...@bugs.debian.org
Bug#666108: Failed to Install Debian 6.0 on Dell PERC H710P
Quoting Jonathan Nieder (jrnie...@gmail.com): First, thanks very much for writing. Let's get this fixed. :) As for your question, the short answer is: I don't know. I can provide an updated kernel to test (and would be very interested in the result), but I do not know how to tell the Debian installer to use it. d-i team: advice? This is a situation where Kenshi Muto's backported d-i (stable D-I with a backported kernel) might help: http://kmuto.jp/debian/d-i/ signature.asc Description: Digital signature
Bug#628444: Also in stable, now
To add to my previous report: of the workrounds described above, the 11n_disable suggestion does absolutely nothing for me. However, pcie_aspm=off as a boot option does greatly reduce the extent of the problem. (Sadly it doesn't eliminate it completely -- I just had a repeat of the problem apparently triggered by moving from mains to battery power. But that's the first time in a week of use since I made the change to the command line.) I'd suggest therefore that the recent change to the kernel in stable (which I believe to be the only plausible explanation for my experience) is one that affects the PCIe power saving controlled by this command line option. -- 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/CANGLxoZPLw1YZxQa=UEOBHPOPX27=e8rtqfv_vd1l8gnnd2...@mail.gmail.com
Bug#676779: linux-image-3.2.0-2-kirkwood: Please enable CONFIG_ZRAM=m
Package: linux-2.6 Version: 3.2.18-1 Severity: wishlist Dear Maintainers, i'd like to use ZRAM (a.k.a. compcache) on my pogoplug. It is possible to enable it by default? On kernelarch-x86 the feature is already enabled. $ grep -ri ZRAM linux-2.6-3.2.18/debian/config/* linux-2.6-3.2.18/debian/config/kernelarch-x86/config:## file: drivers/staging/zram/Kconfig linux-2.6-3.2.18/debian/config/kernelarch-x86/config:CONFIG_ZRAM=m Kind regards, Sebastian -- Package-specific info: ** Version: Linux version 3.2.0-2-kirkwood (Debian 3.2.18-1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-5) ) #1 Tue May 22 14:39:12 UTC 2012 ** Model information Processor : Feroceon 88FR131 rev 1 (v5l) Hardware: Seagate FreeAgent DockStar Revision: -- System Information: Debian Release: wheezy/sid APT prefers stable APT policy: (990, 'stable'), (500, 'testing') Architecture: armel (armv5tel) -- 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/20120609091714.8855.4683.reportbug@localhost
Bug#676792: dm_mod: Unknown symbol scsi_verify_blk_ioctl
Package: linux-2.6 Version: 2.6.32-45 Severity: important I have a KVM Vserver with minimal Debian 6.0 installed. It refuses to load the device mapper module. I googled this and failed. I also failed to find a Debian bug-report about this. Reinstalling the kernel package did not have any effect. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-39) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 3 03:41:26 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=/dev/vda2 ro quiet ** Not tainted ** Kernel log: [0.313134] TCP cubic registered [0.313316] NET: Registered protocol family 10 [0.314095] Mobile IPv6 [0.314101] NET: Registered protocol family 17 [0.314221] PM: Resume from disk failed. [0.314235] registered taskstats version 1 [0.314595] rtc_cmos 00:01: setting system clock to 2012-06-08 19:52:08 UTC (1339185128) [0.314631] Initalizing network drop monitor service [0.314695] Freeing unused kernel memory: 592k freed [0.314997] Write protecting the kernel read-only data: 4236k [0.333080] udev[56]: starting version 164 [0.424270] usbcore: registered new interface driver usbfs [0.424301] usbcore: registered new interface driver hub [0.424687] usbcore: registered new device driver usb [0.424890] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [0.424916] virtio-pci :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 [0.424957] virtio-pci :00:03.0: setting latency timer to 64 [0.425291] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10 [0.425309] virtio-pci :00:04.0: PCI INT A - Link[LNKD] - GSI 10 (level, high) - IRQ 10 [0.425334] virtio-pci :00:04.0: setting latency timer to 64 [0.425754] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10 [0.425760] virtio-pci :00:05.0: PCI INT A - Link[LNKA] - GSI 10 (level, high) - IRQ 10 [0.425789] virtio-pci :00:05.0: setting latency timer to 64 [0.426377] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [0.438310] uhci_hcd: USB Universal Host Controller Interface driver [0.438375] uhci_hcd :00:01.2: PCI INT D - Link[LNKD] - GSI 10 (level, high) - IRQ 10 [0.438396] uhci_hcd :00:01.2: setting latency timer to 64 [0.438410] uhci_hcd :00:01.2: UHCI Host Controller [0.438660] uhci_hcd :00:01.2: new USB bus registered, assigned bus number 1 [0.438760] uhci_hcd :00:01.2: irq 10, io base 0xc040 [0.438832] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [0.438835] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.438837] usb usb1: Product: UHCI Host Controller [0.438839] usb usb1: Manufacturer: Linux 2.6.32-5-amd64 uhci_hcd [0.438841] usb usb1: SerialNumber: :00:01.2 [0.438985] usb usb1: configuration #1 chosen from 1 choice [0.439041] hub 1-0:1.0: USB hub found [0.439049] hub 1-0:1.0: 2 ports detected [0.440375] SCSI subsystem initialized [0.440637] alloc irq_desc for 24 on node -1 [0.440639] alloc kstat_irqs on node -1 [0.440669] virtio-pci :00:04.0: irq 24 for MSI/MSI-X [0.440671] alloc irq_desc for 25 on node -1 [0.440672] alloc kstat_irqs on node -1 [0.440689] virtio-pci :00:04.0: irq 25 for MSI/MSI-X [0.458365] FDC 0 is a S82078B [0.472865] alloc irq_desc for 26 on node -1 [0.472868] alloc kstat_irqs on node -1 [0.472907] virtio-pci :00:03.0: irq 26 for MSI/MSI-X [0.472910] alloc irq_desc for 27 on node -1 [0.472911] alloc kstat_irqs on node -1 [0.472958] virtio-pci :00:03.0: irq 27 for MSI/MSI-X [0.472961] alloc irq_desc for 28 on node -1 [0.472963] alloc kstat_irqs on node -1 [0.472988] virtio-pci :00:03.0: irq 28 for MSI/MSI-X [0.473203] vda: vda1 vda2 [0.482863] libata version 3.00 loaded. [0.484849] ata_piix :00:01.1: version 2.13 [0.503740] ata_piix :00:01.1: setting latency timer to 64 [0.504395] scsi0 : ata_piix [0.504557] scsi1 : ata_piix [0.504588] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xc0a0 irq 14 [0.504590] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xc0a8 irq 15 [0.749039] usb 1-1: new full speed USB device using uhci_hcd and address 2 [0.753407] kjournald starting. Commit interval 5 seconds [0.753437] EXT3-fs: mounted filesystem with ordered data mode. [0.957888] usb 1-1: New USB device found, idVendor=0627, idProduct=0001 [0.957892] usb 1-1: New USB device strings: Mfr=1, Product=3, SerialNumber=5 [0.957895] usb 1-1: Product: QEMU USB Tablet [0.957897] usb 1-1: Manufacturer: QEMU 1.0 [0.957899] usb 1-1: SerialNumber: 42 [0.957980] usb 1-1: configuration #1 chosen from 1 choice [1.597868] udev[441]: starting version 164 [1.772673] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [
Bug#676792: marked as done (dm_mod: Unknown symbol scsi_verify_blk_ioctl)
Your message dated Sat, 09 Jun 2012 13:48:24 +0100 with message-id 1339246104.21665.148.ca...@deadeye.wl.decadent.org.uk and subject line Re: Bug#676792: dm_mod: Unknown symbol scsi_verify_blk_ioctl has caused the Debian Bug report #676792, regarding dm_mod: Unknown symbol scsi_verify_blk_ioctl 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.) -- 676792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-45 Severity: important I have a KVM Vserver with minimal Debian 6.0 installed. It refuses to load the device mapper module. I googled this and failed. I also failed to find a Debian bug-report about this. Reinstalling the kernel package did not have any effect. -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-39) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 3 03:41:26 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=/dev/vda2 ro quiet ** Not tainted ** Kernel log: [0.313134] TCP cubic registered [0.313316] NET: Registered protocol family 10 [0.314095] Mobile IPv6 [0.314101] NET: Registered protocol family 17 [0.314221] PM: Resume from disk failed. [0.314235] registered taskstats version 1 [0.314595] rtc_cmos 00:01: setting system clock to 2012-06-08 19:52:08 UTC (1339185128) [0.314631] Initalizing network drop monitor service [0.314695] Freeing unused kernel memory: 592k freed [0.314997] Write protecting the kernel read-only data: 4236k [0.333080] udev[56]: starting version 164 [0.424270] usbcore: registered new interface driver usbfs [0.424301] usbcore: registered new interface driver hub [0.424687] usbcore: registered new device driver usb [0.424890] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11 [0.424916] virtio-pci :00:03.0: PCI INT A - Link[LNKC] - GSI 11 (level, high) - IRQ 11 [0.424957] virtio-pci :00:03.0: setting latency timer to 64 [0.425291] ACPI: PCI Interrupt Link [LNKD] enabled at IRQ 10 [0.425309] virtio-pci :00:04.0: PCI INT A - Link[LNKD] - GSI 10 (level, high) - IRQ 10 [0.425334] virtio-pci :00:04.0: setting latency timer to 64 [0.425754] ACPI: PCI Interrupt Link [LNKA] enabled at IRQ 10 [0.425760] virtio-pci :00:05.0: PCI INT A - Link[LNKA] - GSI 10 (level, high) - IRQ 10 [0.425789] virtio-pci :00:05.0: setting latency timer to 64 [0.426377] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver [0.438310] uhci_hcd: USB Universal Host Controller Interface driver [0.438375] uhci_hcd :00:01.2: PCI INT D - Link[LNKD] - GSI 10 (level, high) - IRQ 10 [0.438396] uhci_hcd :00:01.2: setting latency timer to 64 [0.438410] uhci_hcd :00:01.2: UHCI Host Controller [0.438660] uhci_hcd :00:01.2: new USB bus registered, assigned bus number 1 [0.438760] uhci_hcd :00:01.2: irq 10, io base 0xc040 [0.438832] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001 [0.438835] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [0.438837] usb usb1: Product: UHCI Host Controller [0.438839] usb usb1: Manufacturer: Linux 2.6.32-5-amd64 uhci_hcd [0.438841] usb usb1: SerialNumber: :00:01.2 [0.438985] usb usb1: configuration #1 chosen from 1 choice [0.439041] hub 1-0:1.0: USB hub found [0.439049] hub 1-0:1.0: 2 ports detected [0.440375] SCSI subsystem initialized [0.440637] alloc irq_desc for 24 on node -1 [0.440639] alloc kstat_irqs on node -1 [0.440669] virtio-pci :00:04.0: irq 24 for MSI/MSI-X [0.440671] alloc irq_desc for 25 on node -1 [0.440672] alloc kstat_irqs on node -1 [0.440689] virtio-pci :00:04.0: irq 25 for MSI/MSI-X [0.458365] FDC 0 is a S82078B [0.472865] alloc irq_desc for 26 on node -1 [0.472868] alloc kstat_irqs on node -1 [0.472907] virtio-pci :00:03.0: irq 26 for MSI/MSI-X [0.472910] alloc irq_desc for 27 on node -1 [0.472911] alloc kstat_irqs on node -1 [0.472958] virtio-pci :00:03.0: irq 27 for MSI/MSI-X [0.472961] alloc irq_desc for 28 on node -1 [0.472963] alloc kstat_irqs on node -1 [0.472988] virtio-pci :00:03.0: irq 28 for MSI/MSI-X [0.473203] vda: vda1 vda2 [0.482863] libata version 3.00 loaded. [0.484849] ata_piix :00:01.1: version 2.13 [0.503740] ata_piix :00:01.1: setting latency timer to 64 [0.504395] scsi0 : ata_piix [
Bug#675602: SATA3 not detected on AsRock P55 Extreme 4 motherboard
Correction: The message at the step Load installer modules is irrelevant, as it refers to the integrated networdcard from Realtek. And further, it regards the firmware, not the driver. Yours, Per Tunedal -- 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/1339254436.2420.6.camel@Pers-debian.lions
Bug#676792: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#676792: dm_mod: Unknown symbol scsi_verify_blk_ioctl)
Indeed. I did not notice this. Now I have a new bug for you: For some reason, apt-get install --reinstall linux-image-2.6.32-5-amd64 does not write all files in /boot: v5:/boot# ll total 14M drwxr-xr-x 3 root root 4.0K Jun 9 15:09 ./ drwxr-xr-x 23 root root 4.0K Jun 8 22:31 ../ -rw-r--r-- 1 root root 1.6M May 6 11:24 System.map-2.6.32-5-amd64 -rw-r--r-- 1 root root 104K May 6 11:24 config-2.6.32-5-amd64 drwxr-xr-x 3 root root 4.0K Jun 9 15:09 grub/ -rw-r--r-- 1 root root 9.6M Jun 9 15:09 initrd.img-2.6.32-5-amd64 -rw-r--r-- 1 root root 2.4M May 6 11:18 vmlinuz-2.6.32-5-amd64 v5:/boot# You can see that vmlinuz-2.6.32-5-amd64, config-2.6.32-5-amd64 and System.map-2.6.32-5-amd64 are old, while initrd.img-2.6.32-5-amd64 has been updated. That strikes me as wrong for --reinstall. That also leaves the question of how I can upgrade these files. Do a purge and install new? Arno On Sat, Jun 09, 2012 at 12:51:32PM +, Debian Bug Tracking System wrote: This is an automatic notification regarding your Bug report which was filed against the linux-2.6 package: #676792: dm_mod: Unknown symbol scsi_verify_blk_ioctl It has been closed by Ben Hutchings b...@decadent.org.uk. Their explanation is attached below along with your original report. If this explanation is unsatisfactory and you have not received a better one in a separate message then please contact Ben Hutchings b...@decadent.org.uk by replying to this email. -- 676792: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676792 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems Received: (at 676792-done) by bugs.debian.org; 9 Jun 2012 12:48:46 + X-Spam-Checker-Version: SpamAssassin 3.3.1-bugs.debian.org_2005_01_02 (2010-03-16) on busoni.debian.org X-Spam-Level: X-Spam-Status: No, score=-12.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER, PGPSIGNATURE autolearn=ham version=3.3.1-bugs.debian.org_2005_01_02 X-Spam-Bayes: score:0. Tokens: new, 13; hammy, 151; neutral, 71; spammy, 0. spammytokens: hammytokens:0.000-+--H*c:pgp-sha512, 0.000-+--H*F:D*decadent.org.uk, 0.000-+--H*RU:sk:shadbol, 0.000-+--HX-Spam-Relays-External:sk:shadbol, 0.000-+--HX-SA-Exim-Scanned:sk:shadbol Return-path: b...@decadent.org.uk Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]) by busoni.debian.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from b...@decadent.org.uk) id 1SdL5p-0007wT-T8 for 676792-d...@bugs.debian.org; Sat, 09 Jun 2012 12:48:43 + Received: from [2001:470:1f08:1539:21c:bfff:fe03:f805] (helo=deadeye.wl.decadent.org.uk) by shadbolt.decadent.org.uk with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.72) (envelope-from b...@decadent.org.uk) id 1SdL5i-00082u-Od for 676792-d...@bugs.debian.org; Sat, 09 Jun 2012 13:48:30 +0100 Received: from ben by deadeye.wl.decadent.org.uk with local (Exim 4.77) (envelope-from b...@decadent.org.uk) id 1SdL5h-0002JU-VE for 676792-d...@bugs.debian.org; Sat, 09 Jun 2012 13:48:30 +0100 Message-ID: 1339246104.21665.148.ca...@deadeye.wl.decadent.org.uk Subject: Re: Bug#676792: dm_mod: Unknown symbol scsi_verify_blk_ioctl From: Ben Hutchings b...@decadent.org.uk To: 676792-d...@bugs.debian.org Date: Sat, 09 Jun 2012 13:48:24 +0100 In-Reply-To: 20120609114938.21326.23212.report...@vsrv18659.customer.xenway.de References: 20120609114938.21326.23212.report...@vsrv18659.customer.xenway.de Content-Type: multipart/signed; micalg=pgp-sha512; protocol=application/pgp-signature; boundary==-iOZr2muUXFyV+4pfoR30 X-Mailer: Evolution 3.2.2-1+b1 Mime-Version: 1.0 X-SA-Exim-Connect-IP: 2001:470:1f08:1539:21c:bfff:fe03:f805 X-SA-Exim-Mail-From: b...@decadent.org.uk X-SA-Exim-Scanned: No (on shadbolt.decadent.org.uk); SAEximRunCond expanded to false On Sat, 2012-06-09 at 13:49 +0200, Arno Wagner wrote: Package: linux-2.6 Version: 2.6.32-45 Severity: important I have a KVM Vserver with minimal Debian 6.0 installed. It refuses to load the device mapper module. I googled this and failed. I also failed to find a Debian bug-report about this. Reinstalling the kernel package did not have any effect. [...] -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-39) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 3 03:41:26 UTC 2011 [...] This says you are running the kernel from package version 2.6.32-39. You must reboot to complete the upgrade. If you are using an unusual boot loader configuration, for example the kernel is loaded from outside the filesystem, then you will need to copy the new kernel image (/boot/vmlinuz-2.6.32-5-amd64) to the appropriate location. Ben. -- Ben Hutchings 73.46% of all statistics are made up. Received: (at submit) by bugs.debian.org; 9 Jun 2012 11:49:39
Bug#676792: closed by Ben Hutchings b...@decadent.org.uk (Re: Bug#676792: dm_mod: Unknown symbol scsi_verify_blk_ioctl)
Just found it: A web-tool for rebooting that does not always actually reboot. Tnanks for the hints! Arno -- Arno Wagner,Dr. sc. techn., Dipl. Inform., Email: a...@wagner.name GnuPG: ID: 1E25338F FP: 0C30 5782 9D93 F785 E79C 0296 797F 6B50 1E25 338F One of the painful things about our time is that those who feel certainty are stupid, and those with any imagination and understanding are filled with doubt and indecision. -- Bertrand Russell signature.asc Description: Digital signature
Bug#676792: dm_mod: Unknown symbol scsi_verify_blk_ioctl
Arno Wagner wrote: You can see that vmlinuz-2.6.32-5-amd64, config-2.6.32-5-amd64 and System.map-2.6.32-5-amd64 are old, while initrd.img-2.6.32-5-amd64 has been updated. That strikes me as wrong for --reinstall. vmlinuz, config, and System.map are static packaged files, and initrd.img is generated at installation time. Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120609143632.GA17613@burratino
Bug#666108: Failed to Install Debian 6.0 on Dell PERC H710P
gator_...@dell.com wrote: thank you. where can i download the updated kernel? Here it is: http://alioth.debian.org/~jrnieder-guest/temp/driver-test/ Completely untested, since I don't have a 64-bit machine handy at the moment. I would be interested in hearing how it behaves on a variety of machines and RAID setups if possible. I'll also contact LSI to see if they have any advice about tests to run or additional patches to apply. Many thanks, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120609155922.GF17613@burratino
Bug#666108: Dell PERC H710P is not supported by Squeeze Standard Kernel
Hi, I am working on improving support for newer megaraid controllers in Debian squeeze's 2.6.32.y-based kernel. On top of what's in 2.6.32.y, Debian squeeze currently has the following patches applied: c35188377f12 Add poll mechanism to megaraid sas driver 72c4fd36dc7f add sysfs for AEN polling 879111224d07 Add new megaraid SAS 2 controller support to the driver 7bebf5c79cb6 allocate the application cmds to sas2 controller 0c79e681eef1 Fix the fix for fw hang caused by megaraid sas application When Buford Peek needed support for a Dell PERC H710P I provided him with the following as a quick set of patches to test: 81e403ce3c6a infrastructure to get PDs from FW 7e8a75f4dfbf Add the support for updating the OS after adding/removing the devices from FW bdc6fb8d69fa add the logical drive list to driver c978684254d1 driver fixed the device update issue f4c9a1317d32 add the IEEE SGE support to SAS2 controller 39a985547cbf Add Online Controller Reset to MegaRAID SAS drive 0d49016bbab4 Rename megaraid_sas.c to megaraid_sas_base.c 80d9da98b403 Add MSI-X support and msix_disable module parameter aeab3fd7b865 make driver PCI legacy I/O port free driver b6d5d8808b4c Use lowest memory bar for SR-IOV VF support cd50ba8ede5c Add struct megasas_instance_template changes 9c915a8c99bc Add 9565/9285 specific code The result seemed to work ok. :) But it left out at least one important fix: f575c5d3ebdc Fix instance access in megasas_reset_timer It also is not particularly minimal. After applying all of the above, the following commits still remain unapplied: 8d5682532133 tape drive support fix 044833b572b9 report system PDs to OS 7218df69e360 use the firmware boot timeout when waiting for commands a0b7736828f7 Update version number and documentation 780a3762fb92 Zero pad_0 in mfi structure 63bad45db1d4 version and documentation update 837f5fe89c84 support devices update flag 1fd106851698 Add input parameter for max_sectors 707e09bd867c Add three times Online controller reset e340c3537239 Version and documentation update 3f1530c1e1f7 Update GPL headers. eb1b12377376 Fix failure gotos 53ef2bbd2068 Add missing check_and_restore_queue_depth call 0a77066acc78 Enable MSI-X before calling megasas_init_fw e1419191d8d3 Call tasklet_schedule for MSI-X 66192dfe1e74 Fix probe_one to clear MSI-X flags in kdump f51244058963 Fix megasas_build_dcdb_fusion to not filter by TYPE_DISK eaa3c240de25 Fix megasas_build_dcdb_fusion to use correct LUN field 4c598b23807a Add CFG_CLEARED AEN f86c5424b027 Fix tasklet_init call 1ac515ef3f2f Fix fault state handling 42a8d2b34d10 Fix max_sectors for IEEE SGL ebf054b00b0a Fix iMR OCR support to work correctly 00fa2b191b4b Version and Changelog update 3f1abce4aba4 Remove MSI-X black list, use MFI_REG_STATE instead 70d031f36fa5 Remove un-used function 7e70e7336515 Check MFI_REG_STATE.fault.resetAdapter 46fd256e0558 Disable interrupts/free_irq() in megasas_shutdown() 541f90b7c6df Fix bug where AENs could be lost in probe() and resume() 495c5609700e Convert 6,10,12 byte CDB's for FastPath IO 3cc6851f9a35 Add 1078 OCR support 4f788dce0baf Version and Changelog update Questions: 1) Are any of these important fixes that should be applied to 2.6.32.y so everyone who uses a 2.6.32-based kernel can start benefitting from them? 2) Are there any important fixes to megaraid SAS 2 support which we should apply right away to Debian squeeze? 3) Is the list of patches I sent to Buford Peek for LSI Fusion support missing any dependencies or follow-up fixes? 4) Which patches do you recommend applying to support even more hardware more robustly? 5) Would you be willing to test a 2.6.32.y-based kernel with your suggested set of patches? That would be very useful to us. There is a basic kernel for testing available at http://alioth.debian.org/~jrnieder-guest/temp/driver-test/ to get the process started. Thanks for maintaining the megaraid driver well, and hope that helps. Sincerely, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120609164753.GA18761@burratino
Bug#594149: linux-image-2.6.32-5-amd64: Lid switch correct every other time; suspend every other lid close; Samsung N150-11 netbook
Hi I have a Samsung N150 Plus that exhibits this bug. I have done the test requested upstream but the bug's status is REJECTED INSUFFICIENT_DATA. I don't have the privileges to reopen the bug. -- Andrzej P -- 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/87obostop5@prochyra.name
Processed: tagging 383481
Processing commands for cont...@bugs.debian.org: tags 383481 + pending Bug #383481 [linux-2.6] Switch to nouveaufb Ignoring request to alter tags of bug #383481 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 383481: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=383481 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.133926381323293.transcr...@bugs.debian.org
Processed: tagging 609615
Processing commands for cont...@bugs.debian.org: tags 609615 + pending Bug #609615 [linux-2.6] linux-2.6: please do not build in nvidiafb on powerpc systems Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 609615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=609615 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.133926381423309.transcr...@bugs.debian.org
Processing of linux-tools_3.4-1~experimental.1_multi.changes
linux-tools_3.4-1~experimental.1_multi.changes uploaded successfully to localhost along with the files: linux-tools_3.4-1~experimental.1.dsc linux-tools_3.4.orig.tar.gz linux-tools_3.4-1~experimental.1.debian.tar.gz linux-kbuild-3.4_3.4-1~experimental.1_i386.deb linux-tools-3.4_3.4-1~experimental.1_i386.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/e1sdstj-0001du...@franck.debian.org
linux-tools_3.4-1~experimental.1_multi.changes is NEW
(new) linux-kbuild-3.4_3.4-1~experimental.1_i386.deb optional devel Kbuild infrastructure for Linux 3.4 This package provides the kbuild infrastructure for the headers packages for Linux kernel version 3.4. (new) linux-tools-3.4_3.4-1~experimental.1_i386.deb optional devel Performance analysis tools for Linux 3.4 This package contains the 'perf' performance analysis tools for Linux kernel version 3.4. . The linux-base package contains a 'perf' command which will invoke the appropriate version for the running kernel. linux-tools_3.4-1~experimental.1.debian.tar.gz to main/l/linux-tools/linux-tools_3.4-1~experimental.1.debian.tar.gz linux-tools_3.4-1~experimental.1.dsc to main/l/linux-tools/linux-tools_3.4-1~experimental.1.dsc linux-tools_3.4.orig.tar.gz to main/l/linux-tools/linux-tools_3.4.orig.tar.gz Changes: linux-tools (3.4-1~experimental.1) experimental; urgency=low . * New upstream release * Build-Depend on bison and flex, now required to build perf * Fix version insertion in perf man pages Override entries for your package: linux-tools_3.4-1~experimental.1.dsc - source devel Announcing to debian-experimental-chan...@lists.debian.org Announcing to debian-devel-chan...@lists.debian.org 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. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions. -- 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/e1sdsyb-tv...@franck.debian.org
Bug#662902: Please include the sbs-battery driver (CONFIG_BATTERY_SBS=m)
On Fri, Jun 08, 2012 at 10:43:25AM -0500, Jonathan Nieder wrote: Josh Triplett wrote: Less so, but yes. As far as I know, sbs-battery drives a superset of hardware, but bq20z75 does drive a useful subset (though one that doesn't include the hardware I actually have). Having bq20z75 in the wheezy 3.2 kernel wouldn't serve the particular purpose I had in mind for it, but it seems potentially useful. Do you know of relevant patches that could change that? (I.e., maybe this is a candidate for a driver backport.) I just reviewed the history of sbs-battery and bq20z75 carefully, and it looks like my guess does not match reality: sbs-battery and bq20z75 drive the same hardware, and the change just represents a rename. I do see a couple of fixes to sbs-battery after the renaming that seem potentially useful, but not sufficiently so to backport them unless someone needs them. - Josh Triplett -- 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/20120609213918.GA16807@leaf
linux-tools_3.4-1~experimental.1_multi.changes ACCEPTED into experimental
Accepted: linux-kbuild-3.4_3.4-1~experimental.1_i386.deb to main/l/linux-tools/linux-kbuild-3.4_3.4-1~experimental.1_i386.deb linux-tools-3.4_3.4-1~experimental.1_i386.deb to main/l/linux-tools/linux-tools-3.4_3.4-1~experimental.1_i386.deb linux-tools_3.4-1~experimental.1.debian.tar.gz to main/l/linux-tools/linux-tools_3.4-1~experimental.1.debian.tar.gz linux-tools_3.4-1~experimental.1.dsc to main/l/linux-tools/linux-tools_3.4-1~experimental.1.dsc linux-tools_3.4.orig.tar.gz to main/l/linux-tools/linux-tools_3.4.orig.tar.gz Changes: linux-tools (3.4-1~experimental.1) experimental; urgency=low . * New upstream release * Build-Depend on bison and flex, now required to build perf * Fix version insertion in perf man pages Override entries for your package: linux-kbuild-3.4_3.4-1~experimental.1_i386.deb - optional devel linux-tools-3.4_3.4-1~experimental.1_i386.deb - optional devel linux-tools_3.4-1~experimental.1.dsc - source devel Announcing to debian-experimental-chan...@lists.debian.org Announcing to debian-devel-chan...@lists.debian.org Thank you for your contribution to Debian. -- 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/e1sdtv1-0004gj...@franck.debian.org
Bug#662902: Please include the sbs-battery driver (CONFIG_BATTERY_SBS=m)
found 662902 linux-2.6/3.2.19-1 quit Josh Triplett wrote: I just reviewed the history of sbs-battery and bq20z75 carefully, and it looks like my guess does not match reality: sbs-battery and bq20z75 drive the same hardware, and the change just represents a rename. I do see a couple of fixes to sbs-battery after the renaming that seem potentially useful, but not sufficiently so to backport them unless someone needs them. Thanks. -- 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/20120609220012.GB28412@burratino
Processed: Re: Please include the sbs-battery driver (CONFIG_BATTERY_SBS=m)
Processing commands for cont...@bugs.debian.org: found 662902 linux-2.6/3.2.19-1 Bug #662902 [linux-2.6] Please include the sbs-battery driver (CONFIG_BATTERY_SBS=m) Marked as found in versions linux-2.6/3.2.19-1. quit Stopping processing here. Please contact me if you need assistance. -- 662902: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662902 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.13392792232403.transcr...@bugs.debian.org
Re: Featureset patches in linux-source package
On Mon, 2012-06-04 at 12:28 +0200, Bastian Blank wrote: On Mon, Jun 04, 2012 at 06:21:12AM +0100, Ben Hutchings wrote: Index: debian/rules.real === --- debian/rules.real (revision 19077) +++ debian/rules.real (working copy) @@ -82,18 +91,19 @@ $(call patch_cmd,all) @$(stamp) -$(STAMPS_DIR)/source_$(FEATURESET): SOURCE_DIR=$(BUILD_DIR)/source -$(STAMPS_DIR)/source_$(FEATURESET): DIR=$(BUILD_DIR)/source_$(FEATURESET) -$(STAMPS_DIR)/source_$(FEATURESET): $(STAMPS_DIR)/source +$(STAMPS_DIR)/source_%: SOURCE_DIR=$(BUILD_DIR)/source +$(STAMPS_DIR)/source_%: DIR=$(BUILD_DIR)/source_$* +$(STAMPS_DIR)/source_%: SOURCE_DIR=$(BUILD_DIR)/source +$(STAMPS_DIR)/source_%: $(STAMPS_DIR)/source You may have to set .SECONDARY: then. Otherwise the stamp file will be deleted as intermediate. I take your point. However, since we have a target pattern and not a single target, it appears we have to use .PRECIOUS instead. Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#676360: [PATCH] thp: avoid atomic64_read in pmd_read_atomic for 32bit PAE\
On Thu, Jun 07, 2012 at 11:00:33PM +0200, Andrea Arcangeli wrote:
In the x86 32bit PAE CONFIG_TRANSPARENT_HUGEPAGE=y case while holding
the mmap_sem for reading, cmpxchg8b cannot be used to read pmd
contents under Xen.
So instead of dealing only with consistent pmdvals in
pmd_none_or_trans_huge_or_clear_bad() (which would be conceptually
simpler) we let pmd_none_or_trans_huge_or_clear_bad() deal with pmdvals
where the low 32bit and high 32bit could be inconsistent (to avoid
having to use cmpxchg8b).
nods
The only guarantee we get from pmd_read_atomic is that if the low part
of the pmd was found null, the high part will be null too (so the pmd
will be considered unstable). And if the low part of the pmd is found
stable later, then it means the whole pmd was read atomically
(because after a pmd is stable, neither MADV_DONTNEED nor page faults
can alter it anymore, and we read the high part after the low part).
In the 32bit PAE x86 case, it is enough to read the low part of the
pmdval atomically to declare the pmd as stable and that's true for
THP and no THP, furthermore in the THP case we also have a barrier()
that will prevent any inconsistent pmdvals to be cached by a later
re-read of the *pmd.
Nice. Andrew, any chane you could test this patch on the affected
Xen hypervisors? Was it as easy to reproduce this on a RHEL5 (U1?)
hypervisor or is it really only on Linode and Amazon EC2?
Signed-off-by: Andrea Arcangeli aarca...@redhat.com
---
arch/x86/include/asm/pgtable-3level.h | 30 +-
include/asm-generic/pgtable.h | 10 ++
2 files changed, 27 insertions(+), 13 deletions(-)
diff --git a/arch/x86/include/asm/pgtable-3level.h
b/arch/x86/include/asm/pgtable-3level.h
index 43876f1..cb00ccc 100644
--- a/arch/x86/include/asm/pgtable-3level.h
+++ b/arch/x86/include/asm/pgtable-3level.h
@@ -47,16 +47,26 @@ static inline void native_set_pte(pte_t *ptep, pte_t pte)
* they can run pmd_offset_map_lock or pmd_trans_huge or other pmd
* operations.
*
- * Without THP if the mmap_sem is hold for reading, the
- * pmd can only transition from null to not null while pmd_read_atomic runs.
- * So there's no need of literally reading it atomically.
+ * Without THP if the mmap_sem is hold for reading, the pmd can only
+ * transition from null to not null while pmd_read_atomic runs. So
+ * we can always return atomic pmd values with this function.
*
* With THP if the mmap_sem is hold for reading, the pmd can become
- * THP or null or point to a pte (and in turn become stable) at any
- * time under pmd_read_atomic, so it's mandatory to read it atomically
- * with cmpxchg8b.
+ * trans_huge or none or point to a pte (and in turn become stable)
+ * at any time under pmd_read_atomic. We could read it really
+ * atomically here with a atomic64_read for the THP enabled case (and
+ * it would be a whole lot simpler), but to avoid using cmpxchg8b we
+ * only return an atomic pmdval if the low part of the pmdval is later
+ * found stable (i.e. pointing to a pte). And we're returning a none
+ * pmdval if the low part of the pmd is none. In some cases the high
+ * and low part of the pmdval returned may not be consistent if THP is
+ * enabled (the low part may point to previously mapped hugepage,
+ * while the high part may point to a more recently mapped hugepage),
+ * but pmd_none_or_trans_huge_or_clear_bad() only needs the low part
+ * of the pmd to be read atomically to decide if the pmd is unstable
+ * or not, with the only exception of when the low part of the pmd is
+ * zero in which case we return a none pmd.
*/
-#ifndef CONFIG_TRANSPARENT_HUGEPAGE
static inline pmd_t pmd_read_atomic(pmd_t *pmdp)
{
pmdval_t ret;
@@ -74,12 +84,6 @@ static inline pmd_t pmd_read_atomic(pmd_t *pmdp)
return (pmd_t) { ret };
}
-#else /* CONFIG_TRANSPARENT_HUGEPAGE */
-static inline pmd_t pmd_read_atomic(pmd_t *pmdp)
-{
- return (pmd_t) { atomic64_read((atomic64_t *)pmdp) };
-}
-#endif /* CONFIG_TRANSPARENT_HUGEPAGE */
static inline void native_set_pte_atomic(pte_t *ptep, pte_t pte)
{
diff --git a/include/asm-generic/pgtable.h b/include/asm-generic/pgtable.h
index ae39c4b..0ff87ec 100644
--- a/include/asm-generic/pgtable.h
+++ b/include/asm-generic/pgtable.h
@@ -484,6 +484,16 @@ static inline int
pmd_none_or_trans_huge_or_clear_bad(pmd_t *pmd)
/*
* The barrier will stabilize the pmdval in a register or on
* the stack so that it will stop changing under the code.
+ *
+ * When CONFIG_TRANSPARENT_HUGEPAGE=y on x86 32bit PAE,
+ * pmd_read_atomic is allowed to return a not atomic pmdval
+ * (for example pointing to an hugepage that has never been
+ * mapped in the pmd). The below checks will only care about
+ * the low part of the pmd with 32bit PAE x86 anyway, with the
+ * exception of pmd_none(). So the important thing
where is the code that generates debian/rules.gen
I'm pretty sure both from the name and from behaviour i've seen as i've changed other things that debian/rules.gen in the source package linux-2.6 is a generated file. However I haven't been able to figure out where the code is that generated it. Can someone give me a pointer to the relavent code. -- 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/4fd3f4a3.4010...@postgrad.manchester.ac.uk
Re: where is the code that generates debian/rules.gen
On Sun, 2012-06-10 at 02:13 +0100, peter green wrote: I'm pretty sure both from the name and from behaviour i've seen as i've changed other things that debian/rules.gen in the source package linux-2.6 is a generated file. However I haven't been able to figure out where the code is that generated it. Can someone give me a pointer to the relavent code. I've answered on IRC, but for the benefit of any other interested parties: The files debian/control and debian/rules.gen are generated by debian/bin/gencontrol.py based on the 'defines' files under debian/config, the udeb package definitions under debian/installer, and the current version in debian/changelog. You can generate them explicitly by running 'debian/rules debian/control', and other targets will usually cause them to be regenerated automatically if necessary. (And make will then fail, to ensure that we never accidentally change debian/control during auto- building.) Ben. -- Ben Hutchings The program is absolutely right; therefore, the computer must be wrong. signature.asc Description: This is a digitally signed message part
Bug#676866: linux-image-3.2.0-2-686-pae: won't boot under xen
Package: linux-2.6
Version: 3.2.19-1
Severity: important
Dear Maintainer,
* What led up to the situation?
dist-upgrade, got linux 3.2.19-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
reboot, since there's a new kernel.
* What was the outcome of this action?
won't boot up.
* What outcome did you expect instead?
boot up.
-- More information:
I was able to reproduce this so far on two DomU's running under my local
xen host.
Dom0 info:
root@xen:~# uname -a
Linux xen 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux
root@xen:~# dpkg -l | egrep xen|linux
ii console-setup-linux1.76 Linux specific part of
console-setup
ii libselinux1:amd64 2.1.9-2 SELinux runtime shared
libraries
ii libxen-4.1 4.1.2-6 Public libs for Xen
ii libxenstore3.0 4.1.2-6 Xenstore communications
library for Xen
ii linux-base 3.5 Linux image base package
ii linux-image-3.2.0-2-amd64 3.2.18-1 Linux 3.2 for 64-bit PCs
ii linux-image-amd64 3.2+44 Linux for 64-bit PCs
(meta-package)
ii util-linux 2.20.1-5 Miscellaneous system
utilities
ii xen-hypervisor-4.1-amd64 4.1.2-6 Xen Hypervisor on AMD64
ii xen-linux-system-3.2.0-2-amd64 3.2.18-1 Xen system with Linux
3.2 on 64-bit PCs (meta-package)
ii xen-linux-system-amd64 3.2+44 Xen system with Linux for
64-bit PCs (meta-package)
ii xen-utils-4.1 4.1.2-6 XEN administrative tools
ii xen-utils-common 4.1.2-6 Xen administrative tools
- common files
ii xenstore-utils 4.1.2-6 Xenstore utilities for Xen
root@xen:~#
DomU info:
Was at 3.2.18-1, stopped working when picked up 3.2.19-1.
Booted up again when I manually restored vmlinuz and initrd to 3.2.18-1.
The info below was dumped after the successful boot to 3.2.18-1.
Here is what the failure looked like:
root@xen:~# xm create -c domu-cfgs/wheezytest.cfg
Using config file ./domu-cfgs/wheezytest.cfg.
Exception AttributeError: AttributeError('_DummyThread' object has no
attribute '_Thread__block',) in module 'threading' from
'/usr/lib/python2.7/threading.pyc' ignored
Using class
'grub.GrubConf.Grub2ConfigFile' to parse /boot/grub/grub.cfg
WARNING:root:Unknown directive load_video
WARNING:root:Unknown directive terminal_output
WARNING:root:Unknown directive source
pyGRUB version 0.6
lk
x Debian GNU/Linux, with Linux 3.2.0-2-686-pae x
x Debian GNU/Linux, with Linux 3.2.0-2-686-pae (recovery mode) x
x x
x x
x x
x x
x x
x x
mj
Use the ^ and v keys to select which entry is highlighted.
Press enter to boot the selected OS, 'e' to edit the
commands before booting, 'a' to modify the kernel arguments
before booting, or 'c' for a command line.
Will boot selected entry in 1 seconds
Started domain wheezytest (id=6)
[0.405353] i8042: No controller found
[0.445719]
/build/buildd-linux-2.6_3.2.19-1-i386-c_JlIT/linux-2.6-3.2.19/debian/build/source_i386_none/drivers/rtc/hctosys.c:
unable to open rtc device (rtc0)
[0.447219] BUG: unable to handle kernel paging request at dd9c4dd8
[0.447227] IP: [c1162d5c] atomic64_read_cx8+0x4/0xc
[0.447234] *pdpt = 1d9c5027 *pde = 037c7067 *pte =
80001d9c4061
[0.447243] Oops: 0003 [#1] SMP
[0.447247] Modules linked in:
[0.447251]
[0.447253] Pid: 1, comm: init Not tainted 3.2.0-2-686-pae #1
[0.447259] EIP: 0061:[c1162d5c] EFLAGS: 00010246 CPU: 0
[0.447264] EIP is at atomic64_read_cx8+0x4/0xc
[0.447267] EAX: dd9c0e40 EBX: dd9c0e40 ECX: dd9c4dd8 EDX: dd9c4dd8
[0.447272] ESI: dd9c6498 EDI: dd9c65f8 EBP: dd9c6440 ESP: df431c98
[0.447276] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: e021
[0.447281] Process init (pid: 1, ti=df43 task=df42f900
task.ti=df43)
[0.447285] Stack:
[0.447287] c10ac623 df431d0c b776d000 dd9c6440 b776f000 b776f000
b776f000 dd9c4dd8
[0.447297] 0fcc df431d3c dd9c1010 dd9c1010
b776d000 dd9c0e40
[0.447305] dfc18060 0001 dfc18060 0001 c10c71f0 fffa
dfbe1cdc c1416080
[0.447315] Call Trace:
[0.447320] [c10ac623] ? unmap_vmas+0x234/0x65b
[0.447326] [c10c71f0] ? mem_cgroup_add_lru_list+0xe/0x84
[0.447332] [c109d6d6] ? pagevec_lru_move_fn+0x8a/0x98
[0.447337] [c109d0dd] ? add_page_to_lru_list+0x54/0x54
[0.447342] [c10aff92] ? unmap_region+0x6f/0xb2
[0.447347] [c10b06b5] ? __split_vma+0x100/0x154
[0.447352] [c10b0ae1] ? do_munmap+0x1b3/0x1fb
[0.447358] [c12bed0a] ? elf_map+0xa2/0xda
