Bug#643301: [johnmoha...@gmail.com: Re: linux-image-3.0.0-1-rt-amd64: Suspend to ram hangs]
Hello John, On Thu, Sep 29, 2011 at 12:04:38AM +1000, John O'Hagan wrote: On Tue, 27 Sep 2011 14:59:53 +0200 Uwe Kleine-König u.kleine-koe...@pengutronix.de wrote: On Tue, 27 Sep 2011 00:45:01 -0500 Jonathan Nieder jrnie...@gmail.com wrote: 3. Since hey, one can be lucky sometimes: is it possible to catch the failure as it happens, for example by not suspending the console and suspending everything else? See https://raw.github.com/torvalds/linux/master/Documentation/power/basic-pm-debugging.txt https://raw.github.com/torvalds/linux/master/Documentation/networking/netconsole.txt (or the analagously named files in the linux-doc-3.0.0 package) for hints in that direction. This is a little out of my comfort zone, but I did follow the procedure in the first link, running the sequential tests with /sys/power/pm_test. freezer, devices and platform tests all work, the failure occurs with processors, both for STR and STD. IFACT from the link, this means the problem is not with a driver but with processor states? But my laptop only has a single processor (even though in /sys/devices/system/cpu/ there is cpu0 and cpu1, only the latter has a file online mentioned in the link, is this relevant?). Did you try adding no_console_suspend to the kernel commandline? I have now: for STR, the screen goes blank so if the freeze occurs I don't get to see any messages. For STD, all messages are normal up to and including the one that says the image is being saved (didn't note the exact wording), and there it stops. As netconsole doesn't work on -rt IIRC do you can try using a serial console? Should I go ahead with a report to linux-rt-users as Jonathan has advised? You can try, but I already asked in the linux-rt irc channel and Thomas has no idea and doesn't seem to be interested to look deeper. Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- 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/20110929074352.gf6...@pengutronix.de
Bug#643741: linux-headers-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-35squeeze2-amd64-OT816k/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969!
Package: linux-headers-2.6.32-5-amd64 Version: 2.6.32-35squeeze2 Severity: critical Justification: breaks the whole system Hello, Just installed clean Debian 6.0.2 amd64 and did a reboot via shutdown -r now . This is what I am getting: [ 1619.241195] kernel BUG at /build/buildd-linux-2.6_2.6.32-35squeeze2-amd64-OT816k/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969! [ 1619.241198] invalid opcode: [#1] SMP [ 1619.241201] last sysfs file: /sys/power/state [ 1619.241203] CPU 2 [ 1619.241205] Modules linked in: acpi_cpufreq cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats parport_pc ppdev lp parport sco bridge stp bnep rfcomm l2cap bluetooth rfkill vboxnetflt vboxdrv binfmt_misc fuse loop usbhid hid snd_usb_audio uvcvideo snd_usb_lib snd_seq_midi snd_seq_midi_event videodev v4l1_compat snd_hda_codec_atihdmi snd_rawmidi v4l2_compat_ioctl32 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device radeon snd processor ttm evdev drm_kms_helper i2c_i801 drm i2c_algo_bit pcspkr asus_atk0110 i2c_core soundcore snd_page_alloc psmouse button serio_raw ext4 mbcache jbd2 crc16 sg sr_mod sd_mod crc_t10dif cdrom uhci_hcd ata_generic pata_marvell ata_piix libata atl1e ehci_hcd scsi_mod thermal thermal_sys usbcore nls_base [last unloaded: vboxnetadp] [ 1619.241266] Pid: 2400, comm: rmmod Not tainted 2.6.32-5-amd64 #1 P5QL PRO [ 1619.241268] RIP: 0010:[810e72b3] [810e72b3] kfree+0x55/0xcb [ 1619.241278] RSP: 0018:88012d8cdea8 EFLAGS: 00010246 [ 1619.241281] RAX: 0208 RBX: 000c RCX: 020001f7 [ 1619.241283] RDX: 0001 RSI: ea00041d4918 RDI: ea000380 [ 1619.241286] RBP: 8801 R08: R09: 81455f10 [ 1619.241288] R10: 88012fa24660 R11: 03c0 R12: 81078190 [ 1619.241290] R13: 7fff03473ed5 R14: R15: 0001 [ 1619.241293] FS: 7f306c12e700() GS:88000550() knlGS: [ 1619.241296] CS: 0010 DS: ES: CR0: 8005003b [ 1619.241299] CR2: 7f0257067e80 CR3: 00012e6e2000 CR4: 06e0 [ 1619.241301] DR0: DR1: DR2: [ 1619.241304] DR3: DR6: 0ff0 DR7: 0400 [ 1619.241307] Process rmmod (pid: 2400, threadinfo 88012d8cc000, task 88012d48f810) [ 1619.241308] Stack: [ 1619.241310] 000c 88012e572000 0880 81078190 [ 1619.241314] 0 a02197b0 81078b07 [ 1619.241318] 0 7fff03473ed5 a02197b0 81078e23 [ 1619.241323] Call Trace: [ 1619.241328] [81078190] ? free_sect_attrs+0x1f/0x2f [ 1619.241333] [81078b07] ? free_module+0x73/0x120 [ 1619.241337] [81078e23] ? sys_delete_module+0x216/0x258 [ 1619.241343] [812fc605] ? page_fault+0x25/0x30 [ 1619.241347] [81010b42] ? system_call_fastpath+0x16/0x1b [ 1619.241349] Code: 83 c3 08 48 83 3b 00 eb ec 48 83 fd 10 0f 86 89 00 00 00 48 89 ef e8 b9 e8 ff ff 48 89 c7 48 8b 00 84 c0 78 13 66 a9 00 c0 75 04 0f 0b eb fe 5b 5d 41 5c e9 ac 56 fd ff 48 8b 4c 24 18 4c 8b 4f [ 1619.241379] RIP [810e72b3] kfree+0x55/0xcb [ 1619.241383] RSP 88012d8cdea8 [ 1619.241386] ---[ end trace e7ed2d5edc1bd124 ]--- -- System Information: Debian Release: 6.0.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-headers-2.6.32-5-amd64 depends on: ii gcc-4.34.3.5-4 The GNU C compiler ii linux-headers-2.6.32-5 2.6.32-35squeeze2 Common header files for Linux 2.6. ii linux-kbuild-2.6.322.6.32-1 Kbuild infrastructure for Linux 2. linux-headers-2.6.32-5-amd64 recommends no packages. linux-headers-2.6.32-5-amd64 suggests no packages. -- no debconf information -- 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/20110929075057.2535.26796.reportbug@sv1
Bug#643757: linux-image-2.6.32-5-amd64: Loading acpi/processor causes hanging or reboot
Package: linux-2.6 Version: 2.6.32-35squeeze2 Severity: important Tags: d-i upstream This problem hinders the booting on (at least) this specific HW. Originally I thought this was a udev problem but some tracing revealed that the basic problem is that the machine locks up or do a spontaneous reboot when loading the kernel module acpi/processor. From a user view the booting stops when udev tries to populate the devices. If I disable the loading and do a manual modprobe the machine either locks up or sometimes do a spontaneous reboot after some seconds. I have tried to figure out more precisely what is happening but I have not managed to get a decent kernel-dump. (And this is a production machine so I had to put it back in service...) The easy fix, which I am using now is blacklist processor in /etc/modprobe.d/blacklist.conf -- Package-specific info: ** Version: Linux version 2.6.32-5-amd64 (Debian 2.6.32-35squeeze2) (da...@debian.org) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Fri Sep 9 20:23:16 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-amd64 root=UUID=a7452738-dfe6-406b-acac-9f7225991b18 ro quiet ** Not tainted ** Kernel log: [4.902298] registered panic notifier [4.902302] [drm] Initialized radeon 2.0.0 20080528 for :11:07.0 on minor 0 [5.084262] usb 1-1: new high speed USB device using ehci_hcd and address 2 [5.217398] usb 1-1: New USB device found, idVendor=8087, idProduct=0020 [5.217403] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [5.217495] usb 1-1: configuration #1 chosen from 1 choice [5.217662] hub 1-1:1.0: USB hub found [5.217768] hub 1-1:1.0: 6 ports detected [5.279923] Adding 9765880k swap on /dev/sda2. Priority:-1 extents:1 across:9765880k [5.320524] Adding 9765880k swap on /dev/sdb2. Priority:-2 extents:1 across:9765880k [5.328837] usb 2-1: new high speed USB device using ehci_hcd and address 2 [5.460475] usb 2-1: New USB device found, idVendor=8087, idProduct=0020 [5.460478] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [5.460544] usb 2-1: configuration #1 chosen from 1 choice [5.460618] hub 2-1:1.0: USB hub found [5.460721] hub 2-1:1.0: 6 ports detected [5.471162] EXT3 FS on md0, internal journal [5.560294] loop: module loaded [5.730776] usb 2-1.1: new low speed USB device using ehci_hcd and address 3 [5.830470] usb 2-1.1: New USB device found, idVendor=0518, idProduct=0001 [5.830474] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.830478] usb 2-1.1: Product: USB-compliant keyboard [5.830481] usb 2-1.1: Manufacturer: Plus More Enterprise LTD. [5.830571] usb 2-1.1: configuration #1 chosen from 1 choice [5.903352] usb 2-1.2: new full speed USB device using ehci_hcd and address 4 [5.944535] usbcore: registered new interface driver hiddev [5.947304] input: Plus More Enterprise LTD. USB-compliant keyboard as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input4 [5.947376] generic-usb 0003:0518:0001.0001: input,hidraw0: USB HID v1.10 Keyboard [Plus More Enterprise LTD. USB-compliant keyboard] on usb-:00:1d.0-1.1/input0 [5.951065] input: Plus More Enterprise LTD. USB-compliant keyboard as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.1/2-1.1:1.1/input/input5 [5.951135] generic-usb 0003:0518:0001.0002: input,hidraw1: USB HID v1.10 Mouse [Plus More Enterprise LTD. USB-compliant keyboard] on usb-:00:1d.0-1.1/input1 [5.951150] usbcore: registered new interface driver usbhid [5.951152] usbhid: v2.6:USB HID core driver [5.996056] usb 2-1.2: New USB device found, idVendor=058f, idProduct=9254 [5.996061] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [5.996065] usb 2-1.2: Product: Generic USB Hub [5.996068] usb 2-1.2: Manufacturer: ALCOR [5.996146] usb 2-1.2: configuration #1 chosen from 1 choice [5.996325] hub 2-1.2:1.0: USB hub found [5.996427] hub 2-1.2:1.0: 4 ports detected [6.266860] usb 2-1.2.1: new low speed USB device using ehci_hcd and address 5 [6.363545] usb 2-1.2.1: New USB device found, idVendor=413c, idProduct=2005 [6.363547] usb 2-1.2.1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [6.363549] usb 2-1.2.1: Product: DELL USB Keyboard [6.363551] usb 2-1.2.1: Manufacturer: DELL [6.363611] usb 2-1.2.1: configuration #1 chosen from 1 choice [6.366696] input: DELL DELL USB Keyboard as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2.1/2-1.2.1:1.0/input/input6 [6.366760] generic-usb 0003:413C:2005.0003: input,hidraw2: USB HID v1.10 Keyboard [DELL DELL USB Keyboard] on usb-:00:1d.0-1.2.1/input0 [6.438443] usb 2-1.2.2: new low speed USB device using ehci_hcd and address 6 [6.535999] usb 2-1.2.2: New USB device found, idVendor=413c, idProduct=3200 [6.536004] usb 2-1.2.2: New USB device strings: Mfr=1, Product=2,
Bug#643757: linux-image-2.6.32-5-amd64: Loading acpi/processor causes hanging or reboot
Hi Thomas, Thomas Nilsson wrote: the machine locks up or do a spontaneous reboot when loading the kernel module acpi/processor. [...] I have tried to figure out more precisely what is happening but I have not managed to get a decent kernel-dump. (And this is a production machine so I had to put it back in service...) The easy fix, which I am using now is blacklist processor in /etc/modprobe.d/blacklist.conf Could you attach the portion of the kernel log (e.g., from /var/log/kern.log*) from bootup until initialization finishes, so we can get a sense of how that normally goes? Also, if you get a chance some time to test a 3.x kernel from sid or experimental, that would be very helpful. The only packages from outside squeeze that should be needed are linux-base, initramfs-tools, and the linux image itself. 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/20110929110951.GC18192@elie
Bug#643575: linux-image-3.0.0-1-686-pae: cat /proc/interrupts crashes and freezes system when called a second time
Hi, since my previous attempt to submit further information apparently failed, I hereby re-submit my message from yestarday night: 8 Ben, Jarod, in order to confirm that lirc_serial is the bad guy, I tried to prevent the lirc modules from loading -- without success though. It seems I am too stupid to achieve a lirc-free system -- perhaps you can give me a hint what I'm doing wrong? Here's what I've tried so far: - Disabling everything that looks like pro-lirc in /etc/lirc/hardware.conf: 8 # /etc/lirc/hardware.conf # # Arguments which will be used when launching lircd LIRCD_ARGS= #Don't start lircmd even if there seems to be a good config file START_LIRCMD=false #Don't start irexec, even if a good config file seems to exist. START_IREXEC=false #Try to load appropriate kernel modules LOAD_MODULES=false # Run lircd --driver=help for a list of supported drivers. DRIVER= # If DEVICE is set to /dev/lirc and udev is in use /dev/lirc0 will be # automatically used instead DEVICE= MODULES= # Default configuration files for your hardware if any LIRCD_CONF= LIRCMD_CONF= 8 - Blacklisting lirc_device and lirc_serial in their corresponding /etc/modprobe.d/module_name.conf files (followed by depmod -ae and update-initramfs -u -k `uname -r` -v) Yet I still get messages about lirc being attemptet to load in dmesg: 8 [0.00] Initializing cgroup subsys cpuset [0.00] Initializing cgroup subsys cpu [0.00] Linux version 3.0.0-1-686-pae (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:41:03 UTC 2011 [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: - 0008f000 (usable) [0.00] BIOS-e820: 0008f000 - 0009 (reserved) [0.00] BIOS-e820: 0009 - 0009ec00 (usable) [0.00] BIOS-e820: 0009ec00 - 000a (reserved) [0.00] BIOS-e820: 000e - 0010 (reserved) [0.00] BIOS-e820: 0010 - 7ee98000 (usable) [0.00] BIOS-e820: 7ee98000 - 7eebf000 (reserved) [0.00] BIOS-e820: 7eebf000 - 7ef47000 (usable) [0.00] BIOS-e820: 7ef47000 - 7efbf000 (ACPI NVS) [0.00] BIOS-e820: 7efbf000 - 7eff1000 (usable) [0.00] BIOS-e820: 7eff1000 - 7efff000 (ACPI data) [0.00] BIOS-e820: 7efff000 - 7f00 (usable) [0.00] BIOS-e820: 7f00 - 8000 (reserved) [0.00] BIOS-e820: f800 - fc00 (reserved) [0.00] BIOS-e820: fff0 - 0001 (reserved) [0.00] NX (Execute Disable) protection: active [0.00] DMI 2.5 present. [0.00] DMI: /D525MW, BIOS MWPNT10N.86A.0083.2011.0524.1600 05/24/2011 [0.00] e820 update range: - 0001 (usable) == (reserved) [0.00] e820 remove range: 000a - 0010 (usable) [0.00] last_pfn = 0x7f000 max_arch_pfn = 0x100 [0.00] MTRR default type: uncachable [0.00] MTRR fixed ranges enabled: [0.00] 0-9 write-back [0.00] A-B uncachable [0.00] C-D write-protect [0.00] E-F uncachable [0.00] MTRR variable ranges enabled: [0.00] 0 base 0 mask F8000 write-back [0.00] 1 base 07F00 mask FFF00 uncachable [0.00] 2 base 0 mask F write-protect [0.00] 3 base 0FFF1 mask F write-protect [0.00] 4 base 0FFF2 mask F write-protect [0.00] 5 disabled [0.00] 6 disabled [0.00] x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106 [0.00] found SMP MP-table at [c00fbe70] fbe70 [0.00] initial memory mapped : 0 - 01a0 [0.00] Base memory trampoline at [c009a000] 9a000 size 16384 [0.00] init_memory_mapping: -379fe000 [0.00] 00 - 20 page 4k [0.00] 20 - 003780 page 2M [0.00] 003780 - 00379fe000 page 4k [0.00] kernel direct mapping tables up to 379fe000 @ 19fa000-1a0 [0.00] RAMDISK: 376a6000 - 37ff [0.00] Allocated new RAMDISK: 36d5c000 - 376a58ab [0.00] Move RAMDISK from 376a6000 - 37fef8aa to 36d5c000 - 376a58aa [0.00] ACPI: RSDP 000f2060 00024 (v02 INTEL ) [0.00] ACPI: XSDT 7effe120 0004C (v01 INTEL D525MW 0053 0113) [0.00] ACPI: FACP 7effd000 000F4 (v03 INTEL D525MW 0053 MSFT 010D) [0.00] ACPI: DSDT 7eff9000 03796 (v01 INTEL D525MW 0053 MSFT 010D) [0.00] ACPI: FACS 7ef87000 00040 [
Bug#643741: linux-headers-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-35squeeze2-amd64-OT816k/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969!
severity 643741 important stop On Thu, Sep 29, 2011 at 08:50:57AM +0100, Volodymyr M. Shcherbyna wrote: Package: linux-headers-2.6.32-5-amd64 Version: 2.6.32-35squeeze2 Severity: critical Justification: breaks the whole system no at max important, maybe breaks *one* box. Hello, Just installed clean Debian 6.0.2 amd64 and did a reboot via shutdown -r now . This is what I am getting: [ 1619.241195] kernel BUG at /build/buildd-linux-2.6_2.6.32-35squeeze2-amd64-OT816k/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969! [ 1619.241198] invalid opcode: [#1] SMP [ 1619.241201] last sysfs file: /sys/power/state [ 1619.241203] CPU 2 [ 1619.241205] Modules linked in: acpi_cpufreq cpufreq_conservative cpufreq_powersave cpufreq_userspace cpufreq_stats parport_pc ppdev lp parport sco bridge stp bnep rfcomm l2cap bluetooth rfkill vboxnetflt vboxdrv binfmt_misc fuse loop usbhid hid snd_usb_audio uvcvideo snd_usb_lib snd_seq_midi snd_seq_midi_event videodev v4l1_compat snd_hda_codec_atihdmi snd_rawmidi v4l2_compat_ioctl32 snd_hda_codec_realtek snd_hda_intel snd_hda_codec snd_hwdep snd_pcm snd_seq snd_timer snd_seq_device radeon snd processor ttm evdev drm_kms_helper i2c_i801 drm i2c_algo_bit pcspkr asus_atk0110 i2c_core soundcore snd_page_alloc psmouse button serio_raw ext4 mbcache jbd2 crc16 sg sr_mod sd_mod crc_t10dif cdrom uhci_hcd ata_generic pata_marvell ata_piix libata atl1e ehci_hcd scsi_mod thermal thermal_sys usbcore nls_base [last unloaded: vboxnetadp] can you retry without that vboxfoocrap. Is it reproducible then? thank you. -- maks -- 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/20110929120911.gf31...@vostochny.stro.at
Processed: Re: Bug#643741: linux-headers-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-35squeeze2-amd64-OT816k/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969!
Processing commands for cont...@bugs.debian.org: severity 643741 important Bug #643741 [linux-headers-2.6.32-5-amd64] linux-headers-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-35squeeze2-amd64-OT816k/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969! Severity set to 'important' from 'critical' stop Stopping processing here. Please contact me if you need assistance. -- 643741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643741 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.131729817929783.transcr...@bugs.debian.org
Processed: reassign 643741 to linux-2.6
Processing commands for cont...@bugs.debian.org: reassign 643741 linux-2.6 2.6.32-35squeeze2 Bug #643741 [linux-headers-2.6.32-5-amd64] linux-headers-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-35squeeze2-amd64-OT816k/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969! Bug reassigned from package 'linux-headers-2.6.32-5-amd64' to 'linux-2.6'. Bug No longer marked as found in versions 2.6.32-35squeeze2. Bug #643741 [linux-2.6] linux-headers-2.6.32-5-amd64: kernel BUG at /build/buildd-linux-2.6_2.6.32-35squeeze2-amd64-OT816k/linux-2.6-2.6.32/debian/build/source_amd64_none/mm/slub.c:2969! There is no source info for the package 'linux-2.6' at version '2.6.32-35squeeze2' with architecture '' Unable to make a source version for version '2.6.32-35squeeze2' Bug Marked as found in versions 2.6.32-35squeeze2. thanks Stopping processing here. Please contact me if you need assistance. -- 643741: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643741 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.131730129713267.transcr...@bugs.debian.org
Re: Uploading linux-2.6 (3.0.0-5)
On Thu, Sep 29, 2011 at 00:15, Ben Hutchings b...@decadent.org.uk wrote: ... Assuming that we don't find any more problems with the changes in experimental to use kernel-wedge, I will apply those to unstable as well. I'll need to upload kernel-wedge yet again with Joey's fix for the bug that affected s390. That's awesome :-) -- Otavio Salvador O.S. Systems E-mail: ota...@ossystems.com.br http://www.ossystems.com.br Mobile: +55 53 9981-7854 http://projetos.ossystems.com.br -- 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/CAP9ODKqd3X-8Speu6Hm7=pw1e45ywd5q1ynkljgq3e6nwq5...@mail.gmail.com
Bug#640391: linux-image-3.0.0-1-686-pae: ark3116 driver regression
On Thu, Sep 29, 2011 at 04:35:31PM +0200, Bart Hartgers wrote: Hi ael, I have a real RS232 port on a desktop (back at home now), so I guess I could connect from the netbook USB - ark3116 - RS232 desktop. I will have to see what cables I have, but I think I have a very old RS232 breakout box somewhere, so I can probably fix something up. I have found the breakout box. Unfortunately it is all 25 pin connectors, so I will have to dig out or make some 25 -- 9 pin cables. Make take a while... That would be great! Hopefully we can make some progress that way. I suppose I could use picoterm or similar to view the incoming data on the desktop: it is a while since I looked at those programs. I realized I made a mistake: the program I meant is called picocom. If you have a breakout-box, it would also be interesting to 'manually' toggle some signals, basically just short rxd and/or cts to gnd for a sec. That should trigger some messages in the log if the ark3116 module is loaded with debug=1. It is a very long time since I played with stty, statserial and such. So I may need to pore over man pages try and work out what I am doing. I seem to remember having using minicom at one time. I think one could set up the serial parameters from a menu, and otherwise it just worked as a terminal. Somewhere, I think I have the specification for the garmin connector, but I can trace the wires otherwise. I guess I will start there. It can't be very complicated. I suppose just using statserial while the garmin is attached to the ordinary RS232 port would at least reveal its initial state. Unfortunately a hard disc has just failed on one machine (it would have to be the boot disc..) and the latest xorg packages have decided to stop working properly on another machine, so I have my hands rather full just now... ) ael Thanks! Bart -- Bart Hartgers - New e-mail: bart.hartg...@gmail.com -- 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/20110929154741.GA2693@conquest3.conquest
Bug#643805: linux-image-3.0.0-1-686-pae: ipv4/conf/all/* entries do not work in /proc/sys/net/
Package: linux-2.6 Version: 3.0.0-3 Severity: normal Dear Maintainer, I have a vpn gateway that periodically sends icmp redirects to the hosts of my network (when renegociating tunnels), I configured hosts not to accepts reidrects by uncommenting the default directive found in sysctl.conf: net.ipv4.conf.all.accept_redirects = 0 after reboot here is the config i get in /proc/sys: cat /proc/sys/net/ipv4/conf/*/accept_redirects 0 1 1 1 1 If i try to echo the value in the proc filesystem, It's no better: root@elronde:/home/alxgomzecho 0 /proc/sys/net/ipv4/conf/all/accept_redirects root@elronde:/home/alxgomz# cat /proc/sys/net/ipv4/conf/*/accept_redirects 0 1 1 1 1 Where I expected this to put all interfaces to zero. the entry ./default/accept_redirects seems to work as expected. I have seen the same behaviour for other proc entries such as send_redirects and notices the bug #630650 that is maybe related. -- Package-specific info: ** Version: Linux version 3.0.0-1-686-pae (Debian 3.0.0-3) (b...@decadent.org.uk) (gcc version 4.5.3 (Debian 4.5.3-8) ) #1 SMP Sat Aug 27 16:41:03 UTC 2011 ** Command line: BOOT_IMAGE=/vmlinuz-3.0.0-1-686-pae root=/dev/mapper/localvg-root ro splash quiet ** Tainted: C (1024) * Module from drivers/staging has been loaded. ** Kernel log: [ 97.965216] wlan0: associated [ 97.966015] ieee80211 phy0: wl_ops_bss_info_changed: qos enabled: true (implement) [ 97.966019] ieee80211 phy0: brcmsmac: wl_ops_bss_info_changed: associated [ 97.966034] ieee80211 phy0: wl_ops_bss_info_changed: arp filtering: enabled true, count 0 (implement) [ 97.966129] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready [ 98.161428] ieee80211 phy0: wl_ops_bss_info_changed: arp filtering: enabled true, count 1 (implement) [ 104.159737] PPP generic driver version 2.4.2 [ 106.936206] PPP MPPE Compression module registered [ 108.492029] wlan0: no IPv6 routers present [ 110.528175] process `skype' is using obsolete setsockopt SO_BSDCOMPAT [ 2316.927514] usb 2-1.1.2: new high speed USB device number 7 using ehci_hcd [ 2317.019921] usb 2-1.1.2: New USB device found, idVendor=03f0, idProduct=4712 [ 2317.019929] usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2317.019936] usb 2-1.1.2: Product: Officejet 4500 G510a-f [ 2317.019941] usb 2-1.1.2: Manufacturer: HP [ 2317.019945] usb 2-1.1.2: SerialNumber: CN0BUF10CC05H2 [ 2318.171544] usb 2-1.1.2: usbfs: process 4625 (usb) did not claim interface 0 before use [ 2504.341104] usb 2-1.1.2: USB disconnect, device number 7 [ 2530.612230] usb 2-1.1.2: new high speed USB device number 8 using ehci_hcd [ 2530.704860] usb 2-1.1.2: New USB device found, idVendor=03f0, idProduct=4712 [ 2530.704867] usb 2-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2530.704871] usb 2-1.1.2: Product: Officejet 4500 G510a-f [ 2530.704875] usb 2-1.1.2: Manufacturer: HP [ 2530.704878] usb 2-1.1.2: SerialNumber: CN0BUF10CC05H2 [ 2531.794262] usb 2-1.1.2: usbfs: process 4764 (usb) did not claim interface 0 before use [ 2570.155587] usb 2-1.1.2: usbfs: process 4826 (usb) did not claim interface 0 before use [ 5983.799914] EXT4-fs (dm-1): re-mounted. Opts: errors=remount-ro,commit=0 [ 5984.607592] EXT4-fs (dm-3): re-mounted. Opts: commit=0 [ 7036.968457] usb 2-1.1.1: USB disconnect, device number 6 [13316.883146] GRE over IPv4 demultiplexor driver [13316.884641] GRE over IPv4 tunneling driver [13712.967501] oosplash.bin[11944]: segfault at 4d0 ip b75cfd6b sp bf9c0210 error 4 in libX11.so.6.3.0[b7599000+136000] [18358.128303] usb 2-1.1.1: new high speed USB device number 9 using ehci_hcd [18358.232932] usb 2-1.1.1: New USB device found, idVendor=0bb4, idProduct=0ff9 [18358.232935] usb 2-1.1.1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [18358.232937] usb 2-1.1.1: Product: Android Phone [18358.232939] usb 2-1.1.1: Manufacturer: HTC [18358.232940] usb 2-1.1.1: SerialNumber: HT9AEL901012 [18358.237673] scsi7 : usb-storage 2-1.1.1:1.0 [18359.237421] scsi 7:0:0:0: Direct-Access HTC Android Phone0100 PQ: 0 ANSI: 2 [18359.350418] sd 7:0:0:0: Attached scsi generic sg1 type 0 [18359.358702] sd 7:0:0:0: [sdb] Attached SCSI removable disk [18727.283692] device wlan0 entered promiscuous mode [18727.283710] ieee80211 phy0: FIF_PROMISC_IN_BSS [18735.330083] device wlan0 left promiscuous mode [18735.330110] ieee80211 phy0: FIF_PROMISC_IN_BSS [18741.385710] device wlan0 entered promiscuous mode [18741.387469] ieee80211 phy0: FIF_PROMISC_IN_BSS [19148.042978] device wlan0 left promiscuous mode [19148.043003] ieee80211 phy0: FIF_PROMISC_IN_BSS [19151.471815] device eth0 entered promiscuous mode [19151.482872] device eth0 left promiscuous mode [19155.870997] device wlan0 entered promiscuous mode [19155.871018] ieee80211 phy0: FIF_PROMISC_IN_BSS [19165.199802] device wlan0 left promiscuous mode [19165.199817] ieee80211 phy0: FIF_PROMISC_IN_BSS [19167.652820] device wlan0 entered promiscuous mode [19167.652842] ieee80211
Bug#605395: JMicron Technology JMB362 JMB363 SError: { DevExch } ExpressCard, sometimes fails to boot
Orson wrote: Sorry I have been short on time, but, I will try wheezy (3.0.0-1-amd64) on my hp laptop soon. I have it installed on another laptop so I will make a tar backup and put it onto my hp, adjust fstab and grub uuids and I will give my JMB363 card a try. Thanks for the update. That sounds more complicated than it needs to be --- wouldn't it be enough to grab and verify the linux-image-3.0.0-1-amd64, linux-base, and initramfs-tools .debs from packages.debian.org and then install them with dpkg -i? -- 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/20110929203414.GD18192@elie
Bug#643805: linux-image-3.0.0-1-686-pae: ipv4/conf/all/* entries do not work in /proc/sys/net/
On Thu, Sep 29, 2011 at 10:24:36PM +0200, Alexandre Chapellon wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: normal Dear Maintainer, I have a vpn gateway that periodically sends icmp redirects to the hosts of my network (when renegociating tunnels), I configured hosts not to accepts reidrects by uncommenting the default directive found in sysctl.conf: net.ipv4.conf.all.accept_redirects = 0 Settings under net.ipv4.conf.all should affect all currently existing interfaces, but not newly created interfaces. [...] If i try to echo the value in the proc filesystem, It's no better: root@elronde:/home/alxgomzecho 0 /proc/sys/net/ipv4/conf/all/accept_redirects root@elronde:/home/alxgomz# cat /proc/sys/net/ipv4/conf/*/accept_redirects 0 1 1 1 1 Where I expected this to put all interfaces to zero. That is what I would expect, too. Were any network interfaces created in between running those two commands? the entry ./default/accept_redirects seems to work as expected. Settings under net.ipv4.conf.default should affect all newly created interfaces, but not any currently existing interfaces. I have seen the same behaviour for other proc entries such as send_redirects and notices the bug #630650 that is maybe related. [...] Report #630650 is incoherent. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110929205357.gd18...@decadent.org.uk
Processed: tagging 643805
Processing commands for cont...@bugs.debian.org: tags 643805 + moreinfo Bug #643805 [linux-2.6] linux-image-3.0.0-1-686-pae: ipv4/conf/all/* entries do not work in /proc/sys/net/ Added tag(s) moreinfo. thanks Stopping processing here. Please contact me if you need assistance. -- 643805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=643805 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.131732965430576.transcr...@bugs.debian.org
Bug#643805: linux-image-3.0.0-1-686-pae: ipv4/conf/all/* entries do not work in /proc/sys/net/
2011/9/29 Ben Hutchings b...@decadent.org.uk On Thu, Sep 29, 2011 at 10:24:36PM +0200, Alexandre Chapellon wrote: Package: linux-2.6 Version: 3.0.0-3 Severity: normal Dear Maintainer, I have a vpn gateway that periodically sends icmp redirects to the hosts of my network (when renegociating tunnels), I configured hosts not to accepts reidrects by uncommenting the default directive found in sysctl.conf: net.ipv4.conf.all.accept_redirects = 0 Settings under net.ipv4.conf.all should affect all currently existing interfaces, but not newly created interfaces. [...] If i try to echo the value in the proc filesystem, It's no better: root@elronde:/home/alxgomzecho 0 /proc/sys/net/ipv4/conf/all/accept_redirects root@elronde:/home/alxgomz# cat /proc/sys/net/ipv4/conf/*/accept_redirects 0 1 1 1 1 Where I expected this to put all interfaces to zero. That is what I would expect, too. Were any network interfaces created in between running those two commands? nope, none the entry ./default/accept_redirects seems to work as expected. Settings under net.ipv4.conf.default should affect all newly created interfaces, but not any currently existing interfaces. And that's what it does. I have seen the same behaviour for other proc entries such as send_redirects and notices the bug #630650 that is maybe related. [...] Report #630650 is incoherent. Ben. -- Ben Hutchings We get into the habit of living before acquiring the habit of thinking. - Albert Camus
Bug#633526: [vserver] Bug#633526: vserver kernel breaks ssh public_key authentication on NFS
On Tue, Jul 12, 2011 at 04:27:55AM +0100, Ben Hutchings wrote: Does anyone understand this problem or have an idea of how to investigate it? we now understand the problem, and it was fixed for 3.0.4 with the following patch: http://vserver.13thfloor.at/ExperimentalT/delta-nfs-fix02.diff I'll try to provide similar patches for older kernels in the following days ... best, Herbert Ben. Forwarded Message From: Harald Dunkel harald.dun...@aixigo.de Reply-to: Harald Dunkel harald.dun...@aixigo.de, 633...@bugs.debian.org To: sub...@bugs.debian.org Subject: Bug#633526: vserver kernel breaks ssh public_key authentication on NFS Date: Mon, 11 Jul 2011 09:19:24 +0200 Package: linux-image-2.6-vserver-amd64 Version: 2.6.32+29 If I use the vserver kernel on a remote host, then I cannot login via ssh and public_key authentication. AFAICS the access rights to my authorized_keys file get corrupted. Before I try to login it shows on the remote host: # ls -l /home/hdunkel/.ssh/authorized_keys -rw--- 1 hdunkel users 1406 Jun 15 14:34 authorized_keys When I try to login I am asked for a password (although authorized_keys is set correctly). After this attempt I see on the remote host: # ls -al /home/hdunkel/.ssh/authorized_keys -rw--- 1 4294967294 4294967294 1406 Jun 15 14:34 authorized_keys sshd -d shows that sshd doesn't like this. Using the regular Squeeze kernel without vserver patch there is no such problem. /home is mounted via NFS: # cat /proc/mounts | grep /home nfs-home:/space/home /home nfs4 rw,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,port=0,timeo=600,retrans=2,sec=sys,clientaddr=172.19.96.103,minorversion=0,addr=172.19.96.215 0 0 The NFS server runs Squeeze, too. Regards Harri -- 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/20110930001047.gk8...@mail.13thfloor.at
Bug#643817: Fix for CVE-2011-2699 can result in crash in VM hosts
Package: linux-2.6 Version: 2.6.32-36 Severity: serious Tags: security patch VM guests using the virtio_net driver may take advantage of UFO (UDP fragmentation offload) which results in the VM host performing fragmentation. As discussed in http://thread.gmane.org/gmane.linux.kernel/1196272, the new IPv6 fragment ID generator will crash in this case because the expected routing context is missing. No fix is yet available, so we should revert the original fix and sort this out properly later. Ben. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20110930023142.13725.55613.reportbug@deadeye
Re: Upcoming Point Releases
On Sat, 2011-09-24 at 02:11 +0100, Ben Hutchings wrote: [...] I have not seen any bug reports against the previous 2.6.32-36, but we need to fix the FTBFS on some architectures. I will build and upload 2.6.32-37 tomorow with fixes for those and a couple more bugs. Barring serious regressions, this version should end up in the point release. There was a regression in 2.6.32-36 (#643817) as a result of a security fix (for CVE-2011-2699). It should not affect the installer. However, I think we should get updated packages into the archive and on CDs. Ben. -- Ben Hutchings Everything should be made as simple as possible, but not simpler. - Albert Einstein signature.asc Description: This is a digitally signed message part
Bug#637461: nfs-common: it worked for a while, and now again
On 09/30/2011 01:12 AM, yellow wrote: again the station does not want to mount the nfs share at boot/reboot/power on. if I do su , mount /myshare it works what to do to test and check what is going on? Could you show the contents of /etc/fstab ? Do you have logs of your system's boot that show what is happening when the other filesystems are mounted (and possibly error messages from attempts to mount /myshare)? hopefully we can get this working for you, --dkg signature.asc Description: OpenPGP digital signature
