Bug#631187: kernel 2.6.32-5-amd64 panics too
Hi, I confirm that some time ago kernel 2.6.32-5-amd64 began to panic too. -- 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/4e2d1f1d.6090...@inbox.ru
Bug#600487: Invalid GART PTE entry errors during bulk data transfers
On Mon, Jul 25, 2011 at 12:23:13AM +0200, Jaap Hoetmer wrote: Thanks, Ben. I am not too familiar with non-stock kernels. I am referring to Debian kernel package version 2.6.32-35, which is the current version in stable (Debian 6.0.2). The command 'dpkg -s linux-image-2.6.32-5-amd64' will show the current package version (among other things). [...] Where can I find the release notes of the 2.6.32-35 kernel? In the Debian changelog. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus signature.asc Description: Digital signature
Bug#635315: linux-doc-2.6.39: Crashes (swapping related?)
On Sun, Jul 24, 2011 at 05:39:57PM -0600, Gordon Haverland wrote: Package: linux-doc-2.6.39 Severity: normal For a while now, I've had the kernel crash. And what does this have to do with linux-doc-2.6.39? Way back when, I used to run crashme (1.2.13) and I am seeing more crashes now, on hardware that is not new. It's baffling. Memtest doesn't see a problem with RAM (booting from ubuntu CD, booting off the disk it can't find memtest). When I let BOINC run models, it was usually BOINC which triggered a crash (Climate Prediction, not SETI). It could be that the CPU is not properly cooled, or the power supply is overloaded. I've suspended BOINC from running anything until Climate Prediction gets its server running again. And still, I get crashes. The latest one on installing new stuff (aptitude safe-upgrade). The only common thread seems to be the need to swap. I've looked around Debian and kernel.org bug reports, and I don't see any that seem to be realted to swapping. How can I produce information which is useful? I'm tired of this crashing. Provide the messages logged in the crash. If they aren't written to disk, use a serial console or netconsole to capture them. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus signature.asc Description: Digital signature
Processed: reassign 635315 to src:linux-2.6, tagging 635315
Processing commands for cont...@bugs.debian.org: reassign 635315 src:linux-2.6 2.6.39-3 Bug #635315 [linux-doc-2.6.39] linux-doc-2.6.39: Crashes (swapping related?) Bug reassigned from package 'linux-doc-2.6.39' to 'src:linux-2.6'. Bug #635315 [src:linux-2.6] linux-doc-2.6.39: Crashes (swapping related?) Bug Marked as found in versions linux-2.6/2.6.39-3. tags 635315 + moreinfo Bug #635315 [src:linux-2.6] linux-doc-2.6.39: Crashes (swapping related?) Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 635315: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635315 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.13115860974697.transcr...@bugs.debian.org
Bug#600487: Invalid GART PTE entry errors during bulk data transfers
On Mon, Jul 25, 2011 at 10:21:31AM +0100, Ben Hutchings wrote: On Mon, Jul 25, 2011 at 12:23:13AM +0200, Jaap Hoetmer wrote: Thanks, Ben. I am not too familiar with non-stock kernels. I am referring to Debian kernel package version 2.6.32-35, which is the current version in stable (Debian 6.0.2). The command 'dpkg -s linux-image-2.6.32-5-amd64' will show the current package version (among other things). And /proc/version contains informations about the running kernel. Bastian -- We have found all life forms in the galaxy are capable of superior development. -- Kirk, The Gamesters of Triskelion, stardate 3211.7 -- 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/20110725093531.ga13...@wavehammer.waldi.eu.org
Bug#635341: [linux-image-2.6.39-2-amd64] eth0 unavailable after standby until reload of e1000e
Package: linux-image-2.6.39-2-amd64 Version: 2.6.39-2 Severity: normal --- Please enter the report below this line. --- When my system (Lenovo T410) resumes from standby (STR), my eth0 interface is dysfunctional (network-manager claims no cable is plugged in). Removing the e1000e module and reloading it fixes the problem. This has happened several times now, at work where I only have a wired connection. Often the machine has also been used with a wifi connection at home beforehand; don't know if this is always the case. --- System information. --- Architecture: amd64 Kernel: Linux 2.6.39-2-amd64 Debian Release: wheezy/sid 500 testing ftp.ch.debian.org 500 stable security.debian.org 500 lucid ppa.launchpad.net --- Package information. --- Depends (Version) | Installed ===-+-=== module-init-tools | 3.16-1 linux-base (= 3~) | 3.2 initramfs-tools (= 0.99) | 0.99 OR linux-initramfs-tool| Package Status (Version) | Installed =-+-=== firmware-bnx2 | firmware-bnx2x| firmware-ipw2x00 | firmware-ivtv | firmware-iwlwifi | 0.32 firmware-linux| firmware-linux-nonfree| firmware-qlogic | firmware-ralink | xen-hypervisor| Recommends (Version) | Installed ==-+-=== firmware-linux-free(= 3~) | 3 Suggests (Version) | Installed ===-+-=== linux-doc-2.6.39| grub-pc | 1.99-6 OR extlinux| OR lilo (= 22.8-8.2~) | --- Output from package bug script --- ** Version: Linux version 2.6.39-2-amd64 (Debian 2.6.39-2) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Wed Jun 8 11:01:04 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.39-2-amd64 root=UUID=0a5ba731-ddd9-4848-8bde-21b382ea74c6 ro rootfstype=ext4 nomodeset pcie_aspm=force nmi_watchdog=0 ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [41648.580058] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [41648.580064] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [41648.580916] ata1.00: ACPI cmd ef/02:00:00:00:00:a0 (SET FEATURES) succeeded [41648.580919] ata1.00: ACPI cmd f5/00:00:00:00:00:a0 (SECURITY FREEZE LOCK) filtered out [41648.580922] ata1.00: ACPI cmd ef/10:03:00:00:00:a0 (SET FEATURES) filtered out [41648.581378] ata1.00: configured for UDMA/100 [41648.598254] hdaps: initial mode latch is 0x05 [41648.598399] hdaps: setting ec_rate=250, filter_order=2 [41648.598640] PM: resume of devices complete after 2965.024 msecs [41648.605477] PM: Finishing wakeup. [41648.605479] Restarting tasks ... [41648.611454] e1000e :00:19.0: PME# enabled [41648.611734] done. [41648.611839] video LNXVIDEO:01: Restoring backlight state [41648.791984] e1000e :00:19.0: BAR 0: set to [mem 0xf240-0xf241] (PCI address [0xf240-0xf241]) [41648.791996] e1000e :00:19.0: BAR 1: set to [mem 0xf2425000-0xf2425fff] (PCI address [0xf2425000-0xf2425fff]) [41648.792006] e1000e :00:19.0: BAR 2: set to [io 0x1820-0x183f] (PCI address [0x1820-0x183f]) [41648.792041] e1000e :00:19.0: restoring config space at offset 0xf (was 0x100, writing 0x10b) [41648.792092] e1000e :00:19.0: restoring config space at offset 0x1 (was 0x10, writing 0x100107) [41648.792188] e1000e :00:19.0: PME# disabled [41648.812484] usb 2-1.1: new full speed USB device number 3 using ehci_hcd [41648.892486] e1000e :00:19.0: irq 42 for MSI/MSI-X [41648.908956] usb 2-1.1: New USB device found, idVendor=046d, idProduct=c526 [41648.908960] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [41648.908963] usb 2-1.1: Product: USB Receiver [41648.908965] usb 2-1.1: Manufacturer: Logitech [41648.91] input: Logitech USB Receiver as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input16 [41648.911236] generic-usb 0003:046D:C526.0003: input,hidraw0: USB HID v1.11 Mouse [Logitech USB Receiver] on usb-:00:1d.0-1.1/input0 [41648.913142] input: Logitech USB Receiver as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.1/input/input17 [41648.913330] generic-usb 0003:046D:C526.0004: input,hiddev0,hidraw1: USB HID v1.11 Device [Logitech USB Receiver] on usb-:00:1d.0-1.1/input1 [41648.947660] e1000e :00:19.0: irq 42 for MSI/MSI-X [41648.948175] ADDRCONF(NETDEV_UP): eth0: link is not ready [41649.036279] ADDRCONF(NETDEV_UP): wlan0: link is
Bug#635344: BUG: unable to handle kernel NULL pointer dereference
Package: linux-2.6 Version: 3.0.0-1 Severity: normal Hi! Today I did an upgrade to latest the Kernel release and after a short time had the system stopped with this: Jul 25 09:04:19 sti-nelson kernel: [ 670.769745] BUG: unable to handle kernel NULL pointer dereference at 00a0 Jul 25 09:04:19 sti-nelson kernel: [ 670.769774] IP: [81336123] down_write+0x16/0x27 Jul 25 09:04:19 sti-nelson kernel: [ 670.769787] PGD 0 Jul 25 09:04:19 sti-nelson kernel: [ 670.769792] Oops: 0002 [#1] SMP Jul 25 09:04:19 sti-nelson kernel: [ 670.769801] CPU 1 Jul 25 09:04:19 sti-nelson kernel: [ 670.769804] Modules linked in: des_generic ecb md4 hmac nls_utf8 cifs fscache ip6table_filter ip6_tables ebtable_nat ebtables powernow_k8 cpufreq_conservative cpufreq_userspa ce cpufreq_stats mperf ipt_REJECT xt_CHECKSUM iptable_mangle xt_tcpudp iptable_filter cpufreq_powersave ip_tables x_tables bridge stp ppdev lp vboxnetadp(O) vboxnetflt(O) vboxdrv(O) binfmt_misc fuse loop kvm_amd kvm usbhid hid snd_hda_codec_realtek sg nouveau ttm snd_hda_intel drm_kms_helper snd_hda_codec drm edac_core i2c_algo_bit sp5100_tco sr_mod edac_mce_amd snd_hwdep snd_pcm ohci_hcd snd_seq snd_timer snd_seq_device snd mxm_wmi i2c_piix4 i2c_core r8169 ata_generic k8temp ehci_hcd soundcore usbcore mii wmi pata_atiixp cdrom snd_page_alloc video parport_pc evdev floppy psmouse parport button processor serio_raw ext4 mbcache j bd2 crc16 dm_mod sd_mod crc_t10dif thermal ahci libahci fan thermal_sys libata scsi_mod Jul 25 09:04:19 sti-nelson kernel: [ 670.769990] Jul 25 09:04:19 sti-nelson kernel: [ 670.769994] Pid: 2738, comm: chromium Tainted: G O 3.0.0-1-amd64 #1 Itautec S.A. Infoway/SM 3321 Jul 25 09:04:19 sti-nelson kernel: [ 670.770008] RIP: 0010:[81336123] [81336123] down_write+0x16/0x27 Jul 25 09:04:19 sti-nelson kernel: [ 670.770019] RSP: 0018:88012a577ea8 EFLAGS: 00010296 Jul 25 09:04:19 sti-nelson kernel: [ 670.770025] RAX: 00a0 RBX: 00a0 RCX: fb80 Jul 25 09:04:19 sti-nelson kernel: [ 670.770032] RDX: 0001 RSI: 0003 RDI: 88012a576000 Jul 25 09:04:19 sti-nelson kernel: [ 670.770039] RBP: 00a0 R08: 7fc650822000 R09: Jul 25 09:04:19 sti-nelson kernel: [ 670.770046] R10: 7fc6720c3c18 R11: 0213 R12: 88012a4bf200 Jul 25 09:04:19 sti-nelson kernel: [ 670.770054] R13: 88011c7d8c38 R14: 7fc650822000 R15: 88011c7d8c38 Jul 25 09:04:19 sti-nelson kernel: [ 670.770061] FS: 7fc66c85a960() GS:88013fc8() knlGS:0b14c840 Jul 25 09:04:19 sti-nelson kernel: [ 670.770070] CS: 0010 DS: ES: CR0: 80050033 Jul 25 09:04:19 sti-nelson kernel: [ 670.770075] CR2: 00a0 CR3: 000130f18000 CR4: 06e0 Jul 25 09:04:19 sti-nelson kernel: [ 670.770083] DR0: DR1: DR2: Jul 25 09:04:19 sti-nelson kernel: [ 670.770090] DR3: DR6: 0ff0 DR7: 0400 Jul 25 09:04:19 sti-nelson kernel: [ 670.770097] Process chromium (pid: 2738, threadinfo 88012a576000, task 880130f54f60) Jul 25 09:04:19 sti-nelson kernel: [ 670.770105] Stack: Jul 25 09:04:19 sti-nelson kernel: [ 670.770108] 8115b236 88011c7d8c38 Jul 25 09:04:19 sti-nelson kernel: [ 670.770120] 7fc6503a2000 810d587c 88011c7d8c38 880139d99440 Jul 25 09:04:19 sti-nelson kernel: [ 670.770132] 810d6941 880139d99440 880139d99448 Jul 25 09:04:19 sti-nelson kernel: [ 670.770143] Call Trace: Jul 25 09:04:19 sti-nelson kernel: [ 670.770150] [8115b236] ? shm_close+0x26/0xa2 Jul 25 09:04:19 sti-nelson kernel: [ 670.770157] [810d587c] ? remove_vma+0x2c/0x71 Jul 25 09:04:19 sti-nelson kernel: [ 670.770164] [810d6941] ? do_munmap+0x2da/0x2f3 Jul 25 09:04:19 sti-nelson kernel: [ 670.770172] [8115c0ab] ? sys_shmdt+0x9a/0x127 Jul 25 09:04:19 sti-nelson kernel: [ 670.770182] [8133ba92] ? system_call_fastpath+0x16/0x1b Jul 25 09:04:19 sti-nelson kernel: [ 670.770188] Code: e0 fe ff ff 48 83 ec 08 89 f2 31 f6 48 83 c4 08 e9 dd ff ff ff 53 48 89 fb e8 40 f5 ff ff 48 ba 01 00 00 00 ff ff ff ff 48 89 d8 f0 48 0f c1 10 48 85 d2 74 05 e8 0e 64 e7 ff 5b c3 53 48 89 fb Jul 25 09:04:19 sti-nelson kernel: [ 670.770272] RIP [81336123] down_write+0x16/0x27 Jul 25 09:04:19 sti-nelson kernel: [ 670.770280] RSP 88012a577ea8 Jul 25 09:04:19 sti-nelson kernel: [ 670.770285] CR2: 00a0 Jul 25 09:04:19 sti-nelson kernel: [ 670.803106] ---[ end trace 386b34f32fc2281f ]--- This machine is very stable with 2.6.39-3 however. Instructions to debug and help gather more information for this are very welcome :-) Thank you! Best regards, Nelson -- Package-specific info: ** Version: Linux version
Bug#635348: FATAL: Error inserting ... (/lib/modules/3.0.0-1-486/kernel/drivers/...
Package: linux-2.6 Version: 3.0.0-1 Seen at boot: Loading cpufreq kernel modules...FATAL: Error inserting powernow_k7 (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/powernow-k7.ko): No such device FATAL: Error inserting speedstep_ich (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/speedstep-ich.ko): No such device FATAL: Error inserting acpi_cpufreq (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/acpi-cpufreq.ko): Device or resource busy FATAL: Error inserting gx_suspmod (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/gx-suspmod.ko): No such device FATAL: Error inserting powernow_k8 (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/powernow-k8.ko): No such device FATAL: Error inserting longrun (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/longrun.ko): No such device FATAL: Error inserting speedstep_smi (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/speedstep-smi.ko): No such device FATAL: Error inserting powernow_k6 (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/powernow-k6.ko): No such device FATAL: Error inserting speedstep_centrino (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/speedstep-centrino.ko): No such device FATAL: Error inserting longhaul (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/longhaul.ko): No such device FATAL: Error inserting cpufreq_nforce2 (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/cpufreq-nforce2.ko): No such device FATAL: Error inserting pcc_cpufreq (/lib/modules/3.0.0-1-486/kernel/drivers/cpufreq/pcc-cpufreq.ko): No such device done (none). -- 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/8739hu8qe2@jidanni.org
Bug#635350: page table error
Package: linux-2.6 Version: 3.0.0-1 Seen in /var/log/kern.log [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state render error detected, EIR: 0x0010 page table error PGTBL_ER: 0x0100 [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, masking render error detected, EIR: 0x0010 page table error PGTBL_ER: 0x0100 -- 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/871uxe8q0w@jidanni.org
Bug#635353: wait longer for USB disks
Package: linux-2.6 Severity: wishlist Version: 3.0.0-1 At boot this, Checking file systems...fsck from util-linux 2.19.1 fsck.ext3: Unable to resolve 'UUID=c914c362-4b46-48be-afaf-6e061825b2ed' fsck died with exit status 8 ^[[31mfailed (code 8).^[[39;49m File system check failed. A log is being saved in /var/log/fsck/checkfs if that location is writable. Please repair the file system manually. ... ^[[31mfailed!^[[39;49m A maintenance shell will now be started. CONTROL-D will terminate this shell and resume system boot. ... ^[[33m(warning).^[[39;49m Give root password for maintenance (or type Control-D to continue): is performed too fast, before the USB disks come on line. Perhaps it should wait the few extra seconds for the USB disks, or I must put some file with sleep 5 into /etc/init.d/ etc. etc. but where would be best? This is all due to this kernel? problem. Jul 25 07:25:28 jidanni3 kernel: [ 12.379058] usb 1-5: unable to read config index 0 descriptor/start: -32 Jul 25 07:25:28 jidanni3 kernel: [ 12.379232] usb 1-5: chopping to 0 config(s) Jul 25 07:25:28 jidanni3 kernel: [ 22.392216] usb 1-5: string descriptor 0 read error: -110 Jul 25 07:25:28 jidanni3 kernel: [ 22.395397] usb 1-5: New USB device found, idVendor=0951, idProduct=1606 Jul 25 07:25:28 jidanni3 kernel: [ 22.395407] usb 1-5: New USB device strings: Mfr=1, Product=2, SerialNumber=4 Jul 25 07:25:28 jidanni3 kernel: [ 22.397197] usb 1-5: no configuration chosen from 0 choices however waiting a few seconds will get it reread fine... -- 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/87wrf67aoa@jidanni.org
Bug#635348: FATAL: Error inserting ... (/lib/modules/3.0.0-1-486/kernel/drivers/...
reassign cpufrequtils 007-1 thanks On Mon, Jul 25, 2011 at 09:02:29PM +0800, jida...@jidanni.org wrote: Seen at boot: Loading cpufreq kernel modules... This init script is provided by cpufrequtils, not the kernel. Bastian -- Vulcans worship peace above all. -- McCoy, Return to Tomorrow, stardate 4768.3 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110725132719.ga16...@wavehammer.waldi.eu.org
Bug#635341: [linux-image-2.6.39-2-amd64] eth0 unavailable after standby until reload of e1000e
tags 635341 moreinfo thanks On Mon, Jul 25, 2011 at 01:46:16PM +0200, Diggory Hardy wrote: When my system (Lenovo T410) resumes from standby (STR), my eth0 interface is dysfunctional (network-manager claims no cable is plugged in). Removing the e1000e module and reloading it fixes the problem. Did this work in the past? When? Does it still happen with the latest kernel (3.0.0-1) from unstable? This has happened several times now, at work where I only have a wired connection. Often the machine has also been used with a wifi connection at home beforehand; don't know if this is always the case. Is it reproducible every time? Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, Errand of Mercy, stardate 3198.9 -- 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/20110725133305.gd16...@wavehammer.waldi.eu.org
Bug#635344: BUG: unable to handle kernel NULL pointer dereference
tags 635344 moreinfo thanks On Mon, Jul 25, 2011 at 09:36:41AM -0300, Nelson A. de Oliveira wrote: ** Tainted: O (4096) * Out-of-tree module has been loaded. You have unsupported out-of-tree modules loaded. Please try again without. Jul 25 09:04:19 sti-nelson kernel: [ 670.769745] BUG: unable to handle kernel NULL pointer dereference at 00a0 Jul 25 09:04:19 sti-nelson kernel: [ 670.769994] Pid: 2738, comm: chromium Tainted: G O 3.0.0-1-amd64 #1 Itautec S.A. Infoway/SM 3321 Jul 25 09:04:19 sti-nelson kernel: [ 670.770150] [8115b236] ? shm_close+0x26/0xa2 Jul 25 09:04:19 sti-nelson kernel: [ 670.770157] [810d587c] ? remove_vma+0x2c/0x71 Jul 25 09:04:19 sti-nelson kernel: [ 670.770164] [810d6941] ? do_munmap+0x2da/0x2f3 Jul 25 09:04:19 sti-nelson kernel: [ 670.770172] [8115c0ab] ? sys_shmdt+0x9a/0x127 Jul 25 09:04:19 sti-nelson kernel: [ 670.770182] [8133ba92] ? system_call_fastpath+0x16/0x1b This is the core memory management. No idea what this could be. Bastian -- We fight only when there is no other choice. We prefer the ways of peaceful contact. -- Kirk, Spectre of the Gun, stardate 4385.3 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110725133043.gc16...@wavehammer.waldi.eu.org
Processed: Re: Bug#635344: BUG: unable to handle kernel NULL pointer dereference
Processing commands for cont...@bugs.debian.org: tags 635344 moreinfo Bug #635344 [linux-2.6] BUG: unable to handle kernel NULL pointer dereference Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 635344: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635344 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.13116021964963.transcr...@bugs.debian.org
Processed: Re: Bug#635341: [linux-image-2.6.39-2-amd64] eth0 unavailable after standby until reload of e1000e
Processing commands for cont...@bugs.debian.org: tags 635341 moreinfo Bug #635341 [linux-image-2.6.39-2-amd64] [linux-image-2.6.39-2-amd64] eth0 unavailable after standby until reload of e1000e Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 635341: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635341 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.13116021964947.transcr...@bugs.debian.org
Bug#635350: marked as done (page table error)
Your message dated Mon, 25 Jul 2011 15:28:41 +0200 with message-id 20110725132841.gb16...@wavehammer.waldi.eu.org and subject line Re: Bug#635350: page table error has caused the Debian Bug report #635350, regarding page table error 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.) -- 635350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635350 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 3.0.0-1 Seen in /var/log/kern.log [drm] capturing error event; look for more information in /debug/dri/0/i915_error_state render error detected, EIR: 0x0010 page table error PGTBL_ER: 0x0100 [drm:i915_report_and_clear_eir] *ERROR* EIR stuck: 0x0010, masking render error detected, EIR: 0x0010 page table error PGTBL_ER: 0x0100 ---End Message--- ---BeginMessage--- This bugreport misses so much information, I'm just closing it. Use reportbug and include more informations on your own. Bastian -- Deflector shields just came on, Captain. ---End Message---
Bug#627098: linux-image-2.6.32-5-686: rndis_host fails to recognize usb device
On Fri, Jul 22, 2011 at 02:02:25AM +0200, Ben Hutchings wrote:
On Sat, 2011-07-16 at 11:59 -0400, Mark Glassberg wrote:
On Wed, Jul 13, 2011 at 12:55:44PM +, Ben Hutchings wrote:
Can you try a newer version (2.6.39 from testing/unstable or 3.0-rc6 from
experimental)?
I don't know if 2.6.39 can be used on my squeeze system, so I burned the
first cd of wheeze and installed it. The installer had problems with my
usb modem/router, so I finished the install and rebooted without it. I
then connected the usb modem/router, but the kernel and/or rndis_host
failed.
That's annoying, because we got that device working... but it looks like
I dropped the bug fix from the Debian package of 2.6.39. However the
bug fix will be back again in Linux 3.0.
I then disconnected the usb modem/router and connected the PC Port.
Again, it failed. The /var/log/messages file is attached.
Please let me know if there are any arguments which should be used with
rndis_host or any of the other modules. Also, was it necessary to install
wheeze?
It shouldn't be, but you would need to upgrade initramfs-tools and
linux-base as well as the linux-image-* package.
And finally, how do I go about using 3.0-rc6?
You would first have to add a line to /etc/apt/sources.list referring to
a mirror of the 'experimental' suite.
Please can you test the attached patch against the experimental version,
following the instructions at:
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official.
Ben.
--
Ben Hutchings
Absolutum obsoletum. (If it works, it's out of date.) - Stafford Beer
From afa0c8df93e460eabb63aa1afcc044bc000affc5 Mon Sep 17 00:00:00 2001
From: Ben Hutchings b...@decadent.org.uk
Date: Fri, 22 Jul 2011 01:56:57 +0200
Subject: [PATCH] rndis_host: Poll status before control channel on 2Wire PC
Port
Apply the RNDIS_DRIVER_DATA_POLL_STATUS quirk to this device.
Signed-off-by: Ben Hutchings b...@decadent.org.uk
---
drivers/net/usb/rndis_host.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/drivers/net/usb/rndis_host.c b/drivers/net/usb/rndis_host.c
index 255d6a4..067db14 100644
--- a/drivers/net/usb/rndis_host.c
+++ b/drivers/net/usb/rndis_host.c
@@ -610,6 +610,11 @@ static const struct usb_device_idproducts [] = {
USB_CLASS_COMM, 2 /* ACM */, 0x0ff),
.driver_info = (unsigned long) rndis_poll_status_info,
}, {
+ /* 2Wire PC Port */
+ USB_DEVICE_AND_INTERFACE_INFO(0x1630, 0x0011,
+ USB_CLASS_COMM, 2 /* ACM */, 0x0ff),
+ .driver_info = (unsigned long) rndis_poll_status_info,
+}, {
/* RNDIS is MSFT's un-official variant of CDC ACM */
USB_INTERFACE_INFO(USB_CLASS_COMM, 2 /* ACM */, 0x0ff),
.driver_info = (unsigned long) rndis_info,
--
1.7.5.4
I booted the 3.0 kernel and both devices were recognized. I then unplugged
both, removed /etc/network/interfaces, and rebooted. When I plugged in the
PC Port, I got the following messages:
[ 106.024038] usb 3-1: new full speed USB device number 2 using uhci_hcd
[ 106.203038] usb 3-1: New USB device found, idVendor=1630, idProduct=0011
[ 106.203105] usb 3-1: New USB device strings: Mfr=1, Product=2,
SerialNumber=0[ 106.203163] usb 3-1: Product: 2Wire PC Port
[ 106.203215] usb 3-1: Manufacturer: 2Wire Inc
[ 106.312267] usbcore: registered new interface driver cdc_ether
[ 106.346573] rndis_host 3-1:1.0: eth2: register 'rndis_host' at
usb-:00:1d.1-1, RNDIS device (poll status before control), 00:d0:9e:3c:25:ed
[ 106.347424] usbcore: registered new interface driver rndis_host
[ 106.432669] cfg80211: Calling CRDA to update world regulatory domain
[ 106.465011] usbcore: registered new interface driver rndis_wlan
[ 106.556970] udev[327]: renamed network interface eth2 to eth4
I then created a new /etc/network/interfaces for eth4. Unfortunately, when I
enteered ifup eth4 I got the following messages:
[ 170.280070] usb 3-1: USB disconnect, device number 2
[ 170.281850] rndis_host 3-1:1.0: eth4: unregister 'rndis_host'
usb-:00:1d.1-1, RNDIS device (poll status before control)
It looks like the kernel disconnected the device, so I couldn't configure it or
bring it up.
Mark
--
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/20110725133816.GA1242@h...@localnet.net
Processed: reassign 635353 to initramfs-tools
Processing commands for cont...@bugs.debian.org: reassign 635353 initramfs-tools Bug #635353 [linux-2.6] wait longer for USB disks Bug reassigned from package 'linux-2.6' to 'initramfs-tools'. Bug No longer marked as found in versions 3.0.0-1. thanks Stopping processing here. Please contact me if you need assistance. -- 635353: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635353 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.13116028237558.transcr...@bugs.debian.org
Bug#635362: linux-image-3.0.0-1-amd64: HDA intel: choppy sound on 3.0
Package: linux-2.6 Version: 3.0.0-1 Severity: normal Using kernel 3.0.0-1 the sound is very choppy (pulse, alsa, oss), while it is perfectly fine on 2.6.39-2 (and always was with previous versions too). As you can see on the logs, snd-hda-intel complains about: hda-intel: Invalid position buffer, using LPIB read method instead. and sometimes (not in this log, but happened a few times): hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. This looks like a pure driver regression to me since booting on 2.6.39-2 is enough to get proper sound (so I guess it's not an alsa bug or something). If you need any additional info, I'd be happy to give you them. Regards, Colomban -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-4) ) #1 SMP Sun Jul 24 02:24:44 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-3.0.0-1-amd64 root=/dev/mapper/hermione-debian ro quiet ** Tainted: IO (6144) * Working around severe firmware bug. * Out-of-tree module has been loaded. ** Kernel log: [ 21.589293] Console: switching to colour dummy device 80x25 [ 21.59] [drm] nouveau :01:00.0: Attempting to load BIOS image from PRAMIN [ 21.639043] [drm] nouveau :01:00.0: ... appears to be valid [ 21.639046] [drm] nouveau :01:00.0: BIT BIOS found [ 21.639048] [drm] nouveau :01:00.0: Bios version 60.84.5e.00 [ 21.639050] [drm] nouveau :01:00.0: TMDS table version 2.0 [ 21.639052] [drm] nouveau :01:00.0: Found Display Configuration Block version 4.0 [ 21.639054] [drm] nouveau :01:00.0: Raw DCB entry 0: 02000300 0028 [ 21.639056] [drm] nouveau :01:00.0: Raw DCB entry 1: 01000302 0030 [ 21.639057] [drm] nouveau :01:00.0: Raw DCB entry 2: 04011310 0028 [ 21.639059] [drm] nouveau :01:00.0: Raw DCB entry 3: 02011312 0030 [ 21.639061] [drm] nouveau :01:00.0: Raw DCB entry 4: 010223f1 00c0c080 [ 21.639063] [drm] nouveau :01:00.0: DCB connector table: VHER 0x40 5 14 2 [ 21.639065] [drm] nouveau :01:00.0: 0: 0x2030: type 0x30 idx 0 tag 0x08 [ 21.639067] [drm] nouveau :01:00.0: 1: 0x1130: type 0x30 idx 1 tag 0x07 [ 21.639069] [drm] nouveau :01:00.0: 2: 0x0210: type 0x10 idx 2 tag 0xff [ 21.639071] [drm] nouveau :01:00.0: 3: 0x0211: type 0x11 idx 3 tag 0xff [ 21.639073] [drm] nouveau :01:00.0: 4: 0x0213: type 0x13 idx 4 tag 0xff [ 21.639076] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset 0xC474 [ 21.662021] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset 0xC7F8 [ 21.678692] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset 0xD248 [ 21.678698] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset 0xD33A [ 21.679757] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset 0xD56D [ 21.679758] [drm] nouveau :01:00.0: Parsing VBIOS init table at offset 0xD5D2 [ 21.688052] input: ImPS/2 Logitech Wheel Mouse as /devices/platform/i8042/serio1/input/input4 [ 21.699552] [drm] nouveau :01:00.0: 0xD5D2: Condition still not met after 20ms, skipping following opcodes [ 21.699571] [drm] nouveau :01:00.0: timingset 255 does not exist [ 21.718629] [drm] nouveau :01:00.0: 1 available performance level(s) [ 21.718637] [drm] nouveau :01:00.0: 0: memory 720MHz core 600MHz shader 1450MHz fanspeed 100% [ 21.718657] [drm] nouveau :01:00.0: c: memory 702MHz core 540MHz shader 1188MHz voltage 1320mV [ 21.718800] [TTM] Zone kernel: Available graphics memory: 1961702 kiB. [ 21.718804] [TTM] Initializing pool allocator. [ 21.718828] [drm] nouveau :01:00.0: Detected 256MiB VRAM [ 21.718839] mtrr: type mismatch for d000,1000 old: write-back new: write-combining [ 21.722625] [drm] nouveau :01:00.0: 512 MiB GART (aperture) [ 21.801228] [drm] nouveau :01:00.0: DCB encoder 1 unknown [ 21.801234] [drm] nouveau :01:00.0: TV-1 has no encoders, removing [ 21.803060] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 21.803065] [drm] No driver support for vblank timestamp query. [ 21.980189] [drm] nouveau :01:00.0: allocated 1680x1050 fb: 0x4000, bo 8801321a3c00 [ 21.980286] fbcon: nouveaufb (fb0) is primary device [ 22.019164] Console: switching to colour frame buffer device 210x65 [ 22.020586] fb0: nouveaufb frame buffer device [ 22.020588] drm: registered panic notifier [ 22.020597] [drm] Initialized nouveau 0.0.16 20090420 for :01:00.0 on minor 0 [ 22.366619] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 22.31] HDA Intel :00:1b.0: irq 42 for MSI/MSI-X [ 22.366681] HDA Intel :00:1b.0: setting latency timer to 64 [ 22.688844] hda_codec: ALC889: BIOS auto-probing. [ 22.732916] HDMI status: Pin=4 Presence_Detect=0 ELD_Valid=0 [
Processed: reassign 635348 to cpufrequtils
Processing commands for cont...@bugs.debian.org: reassign 635348 cpufrequtils 007-1 Bug #635348 [linux-2.6] FATAL: Error inserting ... (/lib/modules/3.0.0-1-486/kernel/drivers/... Bug reassigned from package 'linux-2.6' to 'cpufrequtils'. Bug No longer marked as found in versions 3.0.0-1. Bug #635348 [cpufrequtils] FATAL: Error inserting ... (/lib/modules/3.0.0-1-486/kernel/drivers/... Bug Marked as found in versions cpufrequtils/007-1. thanks Stopping processing here. Please contact me if you need assistance. -- 635348: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635348 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.131160447213884.transcr...@bugs.debian.org
Bug#635371: linux-image-2.6.32-5-amd64: screen freezes when doing make -j12
Package: linux-2.6 Version: 2.6.32-35 Severity: important When compiling some libraries with gcc with all possible threads, the screen freezed and even killing processes is difficult -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=57c8b4a5-e20f-4b9e-9826-d64f14db774f ro quiet ** Not tainted ** Kernel log: [634280.081014] [drm] nouveau :02:00.0: plugged DVI-I-1 [634280.097500] [drm] nouveau :02:00.0: unplugged DVI-I-1 [634280.346850] [drm] nouveau :02:00.0: plugged DVI-I-1 [636412.946015] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.195349] [drm] nouveau :02:00.0: plugged DVI-I-1 [636413.205692] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.455160] [drm] nouveau :02:00.0: plugged DVI-I-1 [636413.471645] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.720964] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.287596] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646858.536932] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.547286] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646858.796741] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.813228] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646859.062544] [drm] nouveau :02:00.0: plugged DVI-I-1 [651926.509154] ITKImageGridTes[25101]: segfault at 8032864b0 ip 005bd5a7 sp 7fffe78343c0 error 4 in ITKImageGridTestDriver[40+89f000] [656378.662330] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656378.911637] [drm] nouveau :02:00.0: plugged DVI-I-1 [656378.921964] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656379.171443] [drm] nouveau :02:00.0: plugged DVI-I-1 [656379.187912] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656379.437235] [drm] nouveau :02:00.0: plugged DVI-I-1 [663350.630204] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663350.879522] [drm] nouveau :02:00.0: plugged DVI-I-1 [663350.889867] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663351.139337] [drm] nouveau :02:00.0: plugged DVI-I-1 [663351.155837] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663351.405177] [drm] nouveau :02:00.0: plugged DVI-I-1 [673891.744876] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673891.994213] [drm] nouveau :02:00.0: plugged DVI-I-1 [673892.004558] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673892.254022] [drm] nouveau :02:00.0: plugged DVI-I-1 [673892.270505] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673892.519820] [drm] nouveau :02:00.0: plugged DVI-I-1 [678061.951508] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.200759] [drm] nouveau :02:00.0: plugged DVI-I-1 [678062.211159] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.460627] [drm] nouveau :02:00.0: plugged DVI-I-1 [678062.477094] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.726415] [drm] nouveau :02:00.0: plugged DVI-I-1 [682679.738403] INFO: task firefox-bin:11874 blocked for more than 120 seconds. [682679.738406] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [682679.738408] firefox-bin D 88000c4cfa20 0 11874 1 0x [682679.738412] 88031e4ec6a0 0082 8802f5fefe34 [682679.738415] 8800cfc1a188 8802f5fefe18 f9e0 8802f5feffd8 [682679.738418] 00015780 00015780 880311eb2a60 880311eb2d58 [682679.738421] Call Trace: [682679.738428] [810b4c0c] ? wait_on_page_writeback_range+0xce/0x11b [682679.738442] [a011df74] ? log_wait_commit+0xbf/0x112 [jbd] [682679.738446] [81064f1a] ? autoremove_wake_function+0x0/0x2e [682679.738451] [a012e3f8] ? ext3_sync_file+0x94/0xc8 [ext3] [682679.738456] [8110bce8] ? vfs_fsync_range+0x73/0x9e [682679.738458] [8110bd92] ? do_fsync+0x28/0x39 [682679.738460] [8110bdb1] ? sys_fdatasync+0xe/0x13 [682679.738464] [81010b42] ? system_call_fastpath+0x16/0x1b [682799.653529] INFO: task firefox-bin:11874 blocked for more than 120 seconds. [682799.653532] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [682799.653533] firefox-bin D 88000c4cfa20 0 11874 1 0x [682799.653536] 88031e4ec6a0 0082 8802f5fefe34 [682799.653538] 8800cfc1a188 8802f5fefe18 f9e0 8802f5feffd8 [682799.653540] 00015780 00015780 880311eb2a60 880311eb2d58 [682799.653542] Call Trace: [682799.653549] [810b4c0c] ? wait_on_page_writeback_range+0xce/0x11b [682799.653560] [a011df74] ? log_wait_commit+0xbf/0x112 [jbd] [682799.653563] [81064f1a] ? autoremove_wake_function+0x0/0x2e [682799.653567] [a012e3f8] ? ext3_sync_file+0x94/0xc8 [ext3] [682799.653571] [8110bce8] ?
Bug#635371: marked as done (linux-image-2.6.32-5-amd64: screen freezes when doing make -j12)
Your message dated Mon, 25 Jul 2011 18:47:19 +0200 with message-id 1311612439.4301.70.camel@deadeye and subject line Re: Bug#635371: linux-image-2.6.32-5-amd64: screen freezes when doing make -j12 has caused the Debian Bug report #635371, regarding linux-image-2.6.32-5-amd64: screen freezes when doing make -j12 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.) -- 635371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635371 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-35 Severity: important When compiling some libraries with gcc with all possible threads, the screen freezed and even killing processes is difficult -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-35) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Tue Jun 14 09:42:28 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=57c8b4a5-e20f-4b9e-9826-d64f14db774f ro quiet ** Not tainted ** Kernel log: [634280.081014] [drm] nouveau :02:00.0: plugged DVI-I-1 [634280.097500] [drm] nouveau :02:00.0: unplugged DVI-I-1 [634280.346850] [drm] nouveau :02:00.0: plugged DVI-I-1 [636412.946015] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.195349] [drm] nouveau :02:00.0: plugged DVI-I-1 [636413.205692] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.455160] [drm] nouveau :02:00.0: plugged DVI-I-1 [636413.471645] [drm] nouveau :02:00.0: unplugged DVI-I-1 [636413.720964] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.287596] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646858.536932] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.547286] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646858.796741] [drm] nouveau :02:00.0: plugged DVI-I-1 [646858.813228] [drm] nouveau :02:00.0: unplugged DVI-I-1 [646859.062544] [drm] nouveau :02:00.0: plugged DVI-I-1 [651926.509154] ITKImageGridTes[25101]: segfault at 8032864b0 ip 005bd5a7 sp 7fffe78343c0 error 4 in ITKImageGridTestDriver[40+89f000] [656378.662330] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656378.911637] [drm] nouveau :02:00.0: plugged DVI-I-1 [656378.921964] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656379.171443] [drm] nouveau :02:00.0: plugged DVI-I-1 [656379.187912] [drm] nouveau :02:00.0: unplugged DVI-I-1 [656379.437235] [drm] nouveau :02:00.0: plugged DVI-I-1 [663350.630204] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663350.879522] [drm] nouveau :02:00.0: plugged DVI-I-1 [663350.889867] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663351.139337] [drm] nouveau :02:00.0: plugged DVI-I-1 [663351.155837] [drm] nouveau :02:00.0: unplugged DVI-I-1 [663351.405177] [drm] nouveau :02:00.0: plugged DVI-I-1 [673891.744876] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673891.994213] [drm] nouveau :02:00.0: plugged DVI-I-1 [673892.004558] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673892.254022] [drm] nouveau :02:00.0: plugged DVI-I-1 [673892.270505] [drm] nouveau :02:00.0: unplugged DVI-I-1 [673892.519820] [drm] nouveau :02:00.0: plugged DVI-I-1 [678061.951508] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.200759] [drm] nouveau :02:00.0: plugged DVI-I-1 [678062.211159] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.460627] [drm] nouveau :02:00.0: plugged DVI-I-1 [678062.477094] [drm] nouveau :02:00.0: unplugged DVI-I-1 [678062.726415] [drm] nouveau :02:00.0: plugged DVI-I-1 [682679.738403] INFO: task firefox-bin:11874 blocked for more than 120 seconds. [682679.738406] echo 0 /proc/sys/kernel/hung_task_timeout_secs disables this message. [682679.738408] firefox-bin D 88000c4cfa20 0 11874 1 0x [682679.738412] 88031e4ec6a0 0082 8802f5fefe34 [682679.738415] 8800cfc1a188 8802f5fefe18 f9e0 8802f5feffd8 [682679.738418] 00015780 00015780 880311eb2a60 880311eb2d58 [682679.738421] Call Trace: [682679.738428] [810b4c0c] ? wait_on_page_writeback_range+0xce/0x11b [682679.738442] [a011df74] ? log_wait_commit+0xbf/0x112 [jbd] [682679.738446] [81064f1a] ? autoremove_wake_function+0x0/0x2e [682679.738451] [a012e3f8] ? ext3_sync_file+0x94/0xc8 [ext3] [682679.738456] [8110bce8] ? vfs_fsync_range+0x73/0x9e [682679.738458] [8110bd92] ? do_fsync+0x28/0x39 [682679.738460] [8110bdb1] ? sys_fdatasync+0xe/0x13 [682679.738464] [81010b42] ?
Bug#632734: Strange
On 22/07/11 02:04 PM, Frank McCormick wrote: On 21/07/11 08:10 PM, Ben Hutchings wrote: Please always cc the bug address when replying to bug-related mails. On Sat, 2011-07-16 at 09:54 -0400, Frank McCormick wrote: On 11/07/11 12:12 AM, Ben Hutchings wrote: On Tue, 2011-07-05 at 17:29 -0400, Frank wrote: On 05/07/11 04:23 PM, Ben Hutchings wrote: On Tue, Jul 05, 2011 at 02:48:26PM -0400, Frank M wrote: I find it strange that the PAE kernel is the ONLY one which gives me any trouble. I guess it could be hardware related, but 2.6.38-1 and 2.6.38-2 have both been booting fine for months. Is there something about the PAE series that would uncover hardware faults which may have existed for a long time ? Have you tried booting those earlier versions recently? Yes I've been booting them everyday for the past month or so - the PAE series is the first time in years, literally, that I have had problems like this. We have provided kernel packages using PAE for a long time, previously labelled as '686-bigmem'. You can test linux-image-2.6.38-2-686-bigmem to check whether this bug is related to use of PAE. However, I think it is probably due to a change between Linux 2.6.38 and 2.6.39. Well I **think** the bigmem kernel now is actually the PAE kernel. I installed the bigmem kernel and it turned out to be the troublesome PAE version. Right. It has been renamed because it is now the only '686' flavour, but has different hardware requirements from the old '686' flavour. I believe the processor in your computer should support this, but could you confirm what model you have (look at the file /proc/cpuinfo)? processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.60GHz stepping : 9 cpu MHz : 2593.138 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 apicid : 0 initial apicid : 0 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cid xtpr bogomips : 5186.27 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 32 bits virtual power management: processor : 1 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Pentium(R) 4 CPU 2.60GHz stepping : 9 cpu MHz : 2593.138 cache size : 512 KB physical id : 0 siblings : 2 core id : 0 cpu cores : 1 apicid : 1 initial apicid : 1 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe pebs bts cid xtpr bogomips : 5187.60 clflush size : 64 cache_alignment : 128 address sizes : 36 bits physical, 32 bits virtual power management: That's it...it alledgedly supports PAE This sounds like there is some sort of hardware fault, but I can't see why it would only occur when using PAE. It is just possible that the circuitry for PAE is faulty, but I think that is only a very small part of the chip. Please do consider the suggestions inhttp://www.bitwizard.nl/sig11/. Will do. Well I have solved this problem..but I'm not sure I like the solution. I installed the new 3.0.0 kernel this morning and started trying changing things in the BIOS setup. Nothing worked to allow me to boot UNTIL I turned off what Intel calls hyper-threading. Now the kernel boots fine, but according to lshw-gtk, the system sees only one CPU. This is a dual-core system which was always seen by Linux as a dual core with in effect two CPU's. What's the connection between hyper-threading , and PAE which is apparently the only change in the new kernels ?? -- Cheers Frank -- 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/4e2da35b.9020...@videotron.ca
Bug#635391: linux-image-3.0.0-1-amd64: Function Do_Suspend : could not open file : /proc/acpi/sleep.
Package: linux-2.6 Version: 3.0.0-1 Severity: normal Cannot suspend to disk with acpitool -S: Function Do_Suspend : could not open file : /proc/acpi/sleep. You must have write access to /proc/acpi/sleep to suspend your computer. -- Package-specific info: ** Version: Linux version 3.0.0-1-amd64 (Debian 3.0.0-1) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-4) ) #1 SMP Sun Jul 24 0 2:24:44 UTC 2011 ** Command line: root=/dev/mapper/vgHDB-HDB6 vga=791 nouveau.modeset=0 resume=LABEL=6Y080P0.05 quiet ** Not tainted ** Kernel log: [1.848877] usbcore: registered new interface driver usb-storage [1.848879] USB Mass Storage support registered. [1.850269] scsi8 : usb-storage 1-2:1.0 [1.850367] usbcore: registered new interface driver ums-cypress [1.855223] sr0: scsi3-mmc drive: 48x/48x writer dvd-ram cd/rw xa/form2 cdda tray [1.855228] cdrom: Uniform CD-ROM driver Revision: 3.20 [1.855339] sr 2:0:0:0: Attached scsi CD-ROM sr0 [1.960088] usb 2-1: new high speed USB device number 2 using ehci_hcd [2.095554] usb 2-1: New USB device found, idVendor=13fe, idProduct=1d00 [2.095557] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [2.095560] usb 2-1: Product: DataTraveler 2.0 [2.095561] usb 2-1: Manufacturer: Kingston [2.095563] usb 2-1: SerialNumber: 5B791500042C [2.095902] scsi9 : usb-storage 2-1:1.0 [2.512097] usb 4-2: new full speed USB device number 2 using ohci_hcd [2.736128] usb 4-2: New USB device found, idVendor=051d, idProduct=0002 [2.736132] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [2.736134] usb 4-2: Product: Back-UPS RS 700G FW:856.L1 .D USB FW:L1 [2.736136] usb 4-2: Manufacturer: American Power Conversion [2.736137] usb 4-2: SerialNumber: 3B1051X26126 [2.826963] generic-usb 0003:051D:0002.0001: hiddev0,hidraw0: USB HID v1.00 Device [American Power Conversion Back-UPS RS 700G FW:856.L1 .D USB FW:L1 ] on usb-:00:04.0-2/input0 [2.827096] usbcore: registered new interface driver usbhid [2.827097] usbhid: USB HID core driver [2.851189] scsi 8:0:0:0: Direct-Access WDC WD16 00AAJB-00J3A0 PQ: 0 ANSI: 0 [2.952235] sd 8:0:0:0: Attached scsi generic sg4 type 0 [2.953639] sd 8:0:0:0: [sdd] 312581808 512-byte logical blocks: (160 GB/149 GiB) [2.954556] sd 8:0:0:0: [sdd] Write Protect is off [2.954560] sd 8:0:0:0: [sdd] Mode Sense: 27 00 00 00 [2.99] sd 8:0:0:0: [sdd] No Caching mode page present [2.955615] sd 8:0:0:0: [sdd] Assuming drive cache: write through [2.958287] sd 8:0:0:0: [sdd] No Caching mode page present [2.958343] sd 8:0:0:0: [sdd] Assuming drive cache: write through [3.028802] sdd: sdd1 sdd2 sdd3 sdd4 sdd5 sdd6 sdd7 sdd8 [3.036161] sd 8:0:0:0: [sdd] No Caching mode page present [3.036217] sd 8:0:0:0: [sdd] Assuming drive cache: write through [3.036273] sd 8:0:0:0: [sdd] Attached SCSI disk [3.040064] usb 3-3: new low speed USB device number 2 using ohci_hcd [3.097942] scsi 9:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS [3.192239] sd 9:0:0:0: Attached scsi generic sg5 type 0 [3.193407] sd 9:0:0:0: [sde] 4014080 512-byte logical blocks: (2.05 GB/1.91 GiB) [3.194805] sd 9:0:0:0: [sde] Write Protect is off [3.194809] sd 9:0:0:0: [sde] Mode Sense: 23 00 00 00 [3.195825] sd 9:0:0:0: [sde] No Caching mode page present [3.195883] sd 9:0:0:0: [sde] Assuming drive cache: write through [3.199828] sd 9:0:0:0: [sde] No Caching mode page present [3.199884] sd 9:0:0:0: [sde] Assuming drive cache: write through [3.200585] sde: sde1 [3.203816] sd 9:0:0:0: [sde] No Caching mode page present [3.203872] sd 9:0:0:0: [sde] Assuming drive cache: write through [3.203927] sd 9:0:0:0: [sde] Attached SCSI removable disk [3.241121] usb 3-3: New USB device found, idVendor=09da, idProduct=0006 [3.241125] usb 3-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [3.241127] usb 3-3: Product: USB Optical Mouse [3.241128] usb 3-3: Manufacturer: A4Tech [4.257404] device-mapper: uevent: version 1.0.3 [4.257466] device-mapper: ioctl: 4.20.0-ioctl (2011-02-02) initialised: dm-de...@redhat.com [4.724853] PM: Starting manual resume from disk [4.724857] PM: Hibernation image partition 8:21 present [4.724858] PM: Looking for hibernation image. [4.725196] PM: Image not found (code -22) [4.725199] PM: Hibernation image not present or could not be loaded. [5.803094] udevd[402]: starting version 172 [6.286936] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input1 [6.286941] ACPI: Power Button [PWRB] [6.286999] input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2 [6.287001] ACPI: Power Button [PWRF] [6.299109] ACPI: acpi_idle registered with cpuidle [6.299141] ACPI: processor limited to max C-state 1 [6.368447] wmi: Mapper
Re: [Pkg-sysvinit-devel] system hangs during shutdown...
On Sun, 24 Jul 2011, Bruce Sass wrote: On July 23, 2011 06:56:44 AM Henrique de Moraes Holschuh wrote: On Thu, 21 Jul 2011, Bruce Sass wrote: This is not a bug. NFS clients are supposed to keep on trying to reach the server, by default. You should have unmounted the directory from the NFS client(s) before shutting down the server. Ben. Sounds like a desirable behaviour when the system is coming up, but having the client hang when *going down* because a server disappeared doesn't seem right. Don't use NFS, then. It does NOT tolerate servers going away. Maybe NFSv4 is a bit better, but v3 does not let you get away with it (maybe it should for read-only mounts). It looks like NFSv4 doesn't like that happening either. Well, that kinda sucks,.. ...I'm thinking that initscripts should be smarter in that it should recognize hopeless cases and set a limit on how long the system will wait before shutting down. Fully configurable, of course. The kernel will hang the umount command. Maybe a cluster filesystem would be a better fit for your needs? They tolerate that sort of thing a lot better. -- One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie. -- The Silicon Valley Tarot Henrique Holschuh -- 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/2011072526.ga28...@khazad-dum.debian.net
Bug#635391: linux: Function Do_Suspend : could not open file : /proc/acpi/sleep.
tags 635391 + moreinfo quit Hi Hugo, hugo vanwoerkom wrote: Cannot suspend to disk with acpitool -S: Function Do_Suspend : could not open file : /proc/acpi/sleep. You must have write access to /proc/acpi/sleep to suspend your computer. A few quick questions: - are you root? - did this work with previous versions of Linux? - what is the context? Any other weird symptoms? Regards, 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/20110725195904.ga2...@elie.dc0b.debconf.org
Processed: Re: linux: Function Do_Suspend : could not open file : /proc/acpi/sleep.
Processing commands for cont...@bugs.debian.org: tags 635391 + moreinfo Bug #635391 [linux-2.6] linux-image-3.0.0-1-amd64: Function Do_Suspend : could not open file : /proc/acpi/sleep. Added tag(s) moreinfo. quit Stopping processing here. Please contact me if you need assistance. -- 635391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635391 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.131162396229363.transcr...@bugs.debian.org
Bug#635362: linux-image-3.0.0-1-amd64: HDA intel: choppy sound on 3.0
Hi, Colomban Wendling wrote: Using kernel 3.0.0-1 the sound is very choppy (pulse, alsa, oss), while it is perfectly fine on 2.6.39-2 (and always was with previous versions too). As you can see on the logs, snd-hda-intel complains about: hda-intel: Invalid position buffer, using LPIB read method instead. [...] 00:1b.0 Audio device [0403]: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio [8086:3b56] (rev 06) Thanks for reporting. A few quick questions: - does it happen immediately or only sometimes? - could you please send the full output of dmesg from booting and quickly triggering the problem with the working and non-working versions? - if it's possible to test without the virtualbox modules, does that help? Regards, 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/20110725200847.gb2...@elie.dc0b.debconf.org
Bug#635371: linux-image-2.6.32-5-amd64: screen freezes when doing make -j12
severity 635371 wishlist tags 635371 + upstream moreinfo quit Hi Arnaud, Arnaud Gelas wrote: When compiling some libraries with gcc with all possible threads, the screen freezed and even killing processes is difficult How much memory was used? Did it go into swap? Is swap on a slow disk? Is this behavior different from previous versions of the kernel? Other notable details? The memory management subsystem or perhaps the I/O scheduler (?) is known to not cope very well with low-memory situations when memory being actively used needs to be reclaimed by swapping things out. In an ideal world, we would want the system to remain responsive enough to kill something, but in practice it is hard to figure out how to do that and figure out what to keep in memory. If some details inspire a method of chiseling away at the problem, I can help direct you to an appropriate person upstream to discuss it and point out patches to test. Otherwise, I will probably close the bug, since it would not be clear how to use this knowledge to improve the kernel. Thanks for reporting. Regards, 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/20110725204437.gd2...@elie.dc0b.debconf.org
Processed: Re: linux-image-2.6.32-5-amd64: screen freezes when doing make -j12
Processing commands for cont...@bugs.debian.org:
severity 635371 wishlist
Bug #635371 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-5-amd64: screen freezes when doing make -j12
Severity set to 'wishlist' from 'important'
tags 635371 + upstream moreinfo
Bug #635371 {Done: Ben Hutchings b...@decadent.org.uk} [linux-2.6]
linux-image-2.6.32-5-amd64: screen freezes when doing make -j12
Added tag(s) upstream and moreinfo.
quit
Stopping processing here.
Please contact me if you need assistance.
--
635371: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635371
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.13116266908561.transcr...@bugs.debian.org
Bug#635391: linux: Function Do_Suspend : could not open file : /proc/acpi/sleep.
On Mon, 2011-07-25 at 21:59 +0200, Jonathan Nieder wrote: tags 635391 + moreinfo quit Hi Hugo, hugo vanwoerkom wrote: Cannot suspend to disk with acpitool -S: Function Do_Suspend : could not open file : /proc/acpi/sleep. You must have write access to /proc/acpi/sleep to suspend your computer. A few quick questions: - are you root? - did this work with previous versions of Linux? - what is the context? Any other weird symptoms? It's a bug in acpitool. /proc/acpi/sleep has been deprecated for years, and has finally been removed. (In fact, all of /proc/acpi is deprecated). Ben. signature.asc Description: This is a digitally signed message part
Processed: reassign 635391 to acpitool
Processing commands for cont...@bugs.debian.org: reassign 635391 acpitool Bug #635391 [linux-2.6] linux-image-3.0.0-1-amd64: Function Do_Suspend : could not open file : /proc/acpi/sleep. Bug reassigned from package 'linux-2.6' to 'acpitool'. Bug No longer marked as found in versions 3.0.0-1. thanks Stopping processing here. Please contact me if you need assistance. -- 635391: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=635391 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.131162894818531.transcr...@bugs.debian.org
Bug#624794: Missing support for various storage and network
A backport for the Intel 82579LM didn't make it into 6.0.2 release, is this still possibly being worked on for 6.0.3? Thanks, Ryan G Limestone Networks, Inc. -- 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/216636937abe004e8cd94ddb2ad8baa501b89dc2c...@lsnexchange.limestonenetworks.com
Bug#632734: family 15, model 2, stepping 9 is not a dual core CPU
Genuine Intel family 15 model 2 stepping 9 is a Northwood C Pentium 4 series CPU. It is a *single* core CPU with hyper-threading support. It is *not* a dual core CPU. It was first release in 2003, 8 years ago. It does not support x86-64 extensions. What happens when one boots an i686 kernel with all of these built-in 1. SMP 2. HyperThreading 3. Multi-core on a single socket, single core, HyperThreading CPU... -- Stan -- 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/4e2e322c.1030...@hardwarefreak.com
