Re: Please Add Marvell mv78xx0 flavour
On Thu, Feb 02, 2012 at 03:34:35AM +, Ben Hutchings wrote: On Wed, 2012-02-01 at 14:55 +, Steve McIntyre wrote: On Thu, Jan 26, 2012 at 04:20:20AM +, Steve McIntyre wrote: On Thu, Jan 26, 2012 at 03:36:53AM +, Ben Hutchings wrote: On Wed, 2012-01-25 at 15:49 +, Steve McIntyre wrote: Following up on the conversation from last week... Attached is a diff for squeeze. This kernel boots and runs fine on arne.debian.org, just tested. The diff between the new config.mv78xx0 and config.orion5x is tiny (mostly comments), but they're not compatible as a single flavour: Right. But I look at these two configurations and cannot understand the reasoning behind the driver selection. They have PCI, but a lot of PCI drivers disabled. I assume this is because there are no PCI slots? If that is the case then there are a whole lot more PCI drivers that cannot be used and should be disabled, which will cut the compile time down significantly. Ah, no. They have PCI slots and could probably support most PCI things, I just didn't consider that so far, basing on config.orion5x. Is it preferred to add everything that might work for these boards, or acceptable to go for a more minimal config to help reduce build time? Ping? I will apply your configuration to unstable now, but I think we need to review which drivers should be enabled. I realise you're trying to match the existing 'orion5x' but let's not compound the mistake. OK, no problem. Let's talk about that at some point soon. Or... is it just as simple as adding all the PCI-based options? If you still want this flavour to be added to stable as well then, as with any stable update, you need to open a bug report. Fine. Your descriptions weren't consistent. The flavour is 'mv78xx0' but you used 'DB-78x00-DP' (1 x) in the long description. Then the short description said 'Feroceon', but that's just the CPU core and it is also used in the kirkwood and orion5x flavours. So I changed those all to '78xx0'. Cool, thanks! -- Steve McIntyre, Cambridge, UK.st...@einval.com Mature Sporty Personal More Innovation More Adult A Man in Dandism Powered Midship Specialty -- 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/20120203135858.gj5...@einval.com
Bug#658578: linux-image-2.6.32-5-amd64: Random kernel panic when inserting USB stick
Package: linux-2.6 Version: 2.6.32-41 Severity: normal Panic occurs randomly (say, 1/10). Reproduces with different sticks, including USB card reader and USB 3G modem w/reader. Bug is mostly similar to #634023. Trace from netconsole: [ 282.236599] BUG: unable to handle kernel NULL pointer dereference at 0040 [ 282.240562] IP: [811761d0] elv_queue_empty+0x13/0x25 [ 282.240562] PGD 23c662067 PUD 23c663067 PMD 0 [ 282.240562] Oops: [#1] SMP [ 282.240562] last sysfs file: /sys/devices/pci:00/:00:13.0/usb5/5-2/5-2:1.0/host15/target15:0:0/15:0:0:0/bsg/15:0:0:0/uevent [ 282.240562] CPU 0 [ 282.240562] Modules linked in: netconsole configfs ipt_MASQUERADE iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 ip_tables x_tables ppp_deflate zlib_deflate bsd_comp ppp_async crc_ccitt vboxnetadp vboxnetflt vboxdrv fuse ppp_generic slhc it87 hwmon_vid loop snd_hda_codec_realtek snd_hda_intel snd_ca0106 snd_hda_codec snd_ac97_codec snd_hwdep ac97_bus snd_pcm_oss snd_mixer_oss snd_pcm snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_timer snd_seq_device snd option usb_wwan soundcore k10temp snd_page_alloc edac_core psmouse wmi usbserial nvidia(P) serio_raw pcspkr i2c_piix4 evdev i2c_core edac_mce_amd button processor ext4 mbcache jbd2 crc16 dm_mod raid1 md_mod sd_mod crc_t10dif ata_generic usb_storage ohci_hcd pata_atiixp ahci ehci_hcd thermal usbcore nls_base r8169 thermal_sys mii libata scsi_mod [last unloaded: scsi_wait_scan] [ 282.240562] Pid: 4, comm: ksoftirqd/0 Tainted: P 2.6.32-5-amd64 #1 GA-MA770T-UD3 [ 282.240562] RIP: 0010:[811761d0] [811761d0] elv_queue_empty+0x13/0x25 [ 282.240562] RSP: 0018:880008a03e00 EFLAGS: 00010046 [ 282.240562] RAX: RBX: 88023c3e34e0 RCX: 0009 [ 282.240562] RDX: 0001 RSI: 0292 RDI: 88023c3e34e0 [ 282.240562] RBP: 88023de3d800 R08: R09: 88023f06b880 [ 282.240562] R10: 08a160c0 R11: 88023da53b90 R12: 0292 [ 282.240562] R13: 88023de3d840 R14: 0296 R15: 880008a03e48 [ 282.240562] FS: 7f0e12262700() GS:880008a0() knlGS: [ 282.240562] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [ 282.240562] CR2: 0040 CR3: 00023c4d7000 CR4: 06f0 [ 282.240562] DR0: DR1: DR2: [ 282.240562] DR3: DR6: 0ff0 DR7: 0400 [ 282.240562] Process ksoftirqd/0 (pid: 4, threadinfo 88023f076000, task 88023f069530) [ 282.240562] Stack: [ 282.240562] 8117f073 88023c3e34e0 8117f163 88023c13a500 [ 282.240562] 0 88023e223428 880008a03e48 a0005885 0004 [ 282.240562] 0 88023c3e34e0 880008a03e48 880008a03e48 88023de3d828 [ 282.240562] Call Trace: [ 282.240562] IRQ [ 282.240562] [8117f073] ? __blk_run_queue+0x1a/0x66 [ 282.240562] [8117f163] ? blk_run_queue+0x21/0x35 [ 282.240562] [a0005885] ? scsi_run_queue+0x2ce/0x36f [scsi_mod] [ 282.240562] [a000667f] ? scsi_next_command+0x2d/0x39 [scsi_mod] [ 282.240562] [a000718a] ? scsi_io_completion+0x3d1/0x3fa [scsi_mod] [ 282.240562] [81183086] ? blk_done_softirq+0x6e/0x7b [ 282.570850] sd 15:0:0:0: [sdc] 3842048 512-byte logical blocks: (1.96 GB/1.83 GiB) [ 282.240562] [81053dc7] ? __do_softirq+0xdd/0x1a6 [ 282.580845] sd 15:0:0:0: [sdc] Write Protect is off [ 282.580847] sd 15:0:0:0: [sdc] Mode Sense: 03 00 00 00 [ 282.580849] sd 15:0:0:0: [sdc] Assuming drive cache: write through [ 282.240562] [81011cac] ? call_softirq+0x1c/0x30 [ 282.240562] EOI [ 282.240562] [8101322b] ? do_softirq+0x3f/0x7c [ 282.240562] [810539ee] ? ksoftirqd+0x5f/0xd3 [ 282.614858] sd 15:0:0:0: [sdc] Assuming drive cache: write through [ 282.614862] sdc: sdc1 [ 282.240562] [8105398f] ? ksoftirqd+0x0/0xd3 [ 282.240562] [81064d5d] ? kthread+0x79/0x81 [ 282.240562] [81011baa] ? child_rip+0xa/0x20 [ 282.240562] [81064ce4] ? kthread+0x0/0x81 [ 282.240562] [81011ba0] ? child_rip+0x0/0x20 [ 282.240562] Code: 83 80 00 00 00 00 00 00 00 ff 8d b0 03 00 00 4c 89 65 10 5b 5d 41 5c c3 31 d2 48 39 3f 48 8b 47 18 75 17 48 8b 00 ba 01 00 00 00 48 8b 40 40 48 85 c0 74 06 49 89 c3 41 ff e3 89 d0 c3 48 8b 47 [ 282.240562] RIP [811761d0] elv_queue_empty+0x13/0x25 [ 282.240562] RSP 880008a03e00 [ 282.240562] CR2: 0040 [ 282.240562] ---[ end trace 1f884421431c9a65 ]--- [ 282.240562] Kernel panic - not syncing: Fatal exception in interrupt [ 282.240562] Pid: 4, comm: ksoftirqd/0 Tainted: P D2.6.32-5-amd64 #1 [ 282.240562] Call Trace: [ 282.240562] IRQ [812fade7] ? panic+0x86/0x143 [ 282.240562] [81068740] ? up+0xe/0x37 [ 282.240562]
Bug#620297: Meet singles in your town for hook ups.
Meet singles in your town for hook ups. https://docs.google.com/document/d/17wRuRJJRoDkImW7JHIaG1EEYXJo-yYQFo1UHYXENcz8/edit If you would like to not be contacted by us in the future please press on the link below: https://docs.google.com/document/d/1g0QGFiPISTibyOMoBFk21sKG0w9mSOmUv1tRQLlnWXw/edit or write to: P.O. Box 74, 15 St. Vancouver, Canada -- 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/20120204062853.22...@web001.nyc1.bluetie.com
Re: [PATCH] kbuild: Fix link to headers in 'make deb-pkg'
adding bwh + debian-kernel On Mon, 23 Jan 2012, Michal Marek wrote: (adding max to CC) On 23.1.2012 12:40, Joerg Roedel wrote: The Link to the kernel header files in the debian packages point to the original build directory. This is a bad choice if the packages were installed on a different machine. Fix this in by manually re-creating the link in the builddeb script. With this patch applied the lib/modules/$version dir always exists, so move the $ARCH = um check out of the modules check too. Signed-off-by: Joerg Roedel joerg.roe...@amd.com --- scripts/package/builddeb | 13 + 1 files changed, 9 insertions(+), 4 deletions(-) diff --git a/scripts/package/builddeb b/scripts/package/builddeb index f6cbc3d..46f63dc 100644 --- a/scripts/package/builddeb +++ b/scripts/package/builddeb @@ -91,6 +91,7 @@ fi rm -rf $tmpdir $fwdir $kernel_headers_dir $libc_headers_dir mkdir -m 755 -p $tmpdir/DEBIAN mkdir -p $tmpdir/lib $tmpdir/boot $tmpdir/usr/share/doc/$packagename +mkdir -p $tmpdir/lib/modules/$version mkdir -m 755 -p $fwdir/DEBIAN mkdir -p $fwdir/lib $fwdir/usr/share/doc/$fwpackagename mkdir -m 755 -p $libc_headers_dir/DEBIAN @@ -121,10 +122,14 @@ fi if grep -q '^CONFIG_MODULES=y' .config ; then INSTALL_MOD_PATH=$tmpdir make KBUILD_SRC= modules_install - if [ $ARCH = um ] ; then - mv $tmpdir/lib/modules/$version/* $tmpdir/usr/lib/uml/modules/$version/ - rmdir $tmpdir/lib/modules/$version - fi +fi + +# Make sure link to the headers is correct +ln -snf /usr/src/$kernel_headers_packagename $tmpdir/lib/modules/$version/build + +if [ $ARCH = um ] ; then + mv $tmpdir/lib/modules/$version/* $tmpdir/usr/lib/uml/modules/$version/ + rmdir $tmpdir/lib/modules/$version fi make headers_check I'm a bit sceptical that it is correct, but passing on to Ben Hutchings, as I never used external modules. He did quite some cleanup in this confusing area, lately for the upcoming debian release. -- 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/20120204143449.ga28...@stro.at
Bug#658618: 3c589_cs: media types 10base2 and 10baseT are switched
Package: linux-2.6 Version: 3.1.8-2 Severity: normal When using /sbin/ifconfig to configure the media type of a 3Com PCMCIA network device, the parameters are switched around. ifconfig eth1 media 10base2 selects 10baseT while ifconfig eth1 media 10baseT selects 10base2. The driver prints out the correct interface in dmesg after running these commands. -- Package-specific info: ** Version: Linux version 3.1.0-1-amd64 (Debian 3.1.8-2) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-11) ) #1 SMP Tue Jan 10 05:01:58 UTC 2012 ** Command line: initrd=/initrd.img root=LABEL=ROOT quiet BOOT_IMAGE=/vmlinuz ** Tainted: W (512) * Taint on warning. ** Kernel log: [720827.368056] 3c589_cs 0.0: eth1: coax cable ok [720828.368065] 3c589_cs 0.0: eth1: coax cable problem [720834.368051] 3c589_cs 0.0: eth1: coax cable ok [720835.368075] 3c589_cs 0.0: eth1: coax cable problem [720836.368045] 3c589_cs 0.0: eth1: coax cable ok [720838.368068] 3c589_cs 0.0: eth1: coax cable problem [720842.368062] 3c589_cs 0.0: eth1: coax cable ok [720851.368095] 3c589_cs 0.0: eth1: coax cable problem [720852.370435] 3c589_cs 0.0: eth1: coax cable ok [720856.368076] 3c589_cs 0.0: eth1: coax cable problem [720857.368060] 3c589_cs 0.0: eth1: coax cable ok [720860.368074] 3c589_cs 0.0: eth1: coax cable problem [720861.368064] 3c589_cs 0.0: eth1: coax cable ok [720862.368069] 3c589_cs 0.0: eth1: coax cable problem [720864.368062] 3c589_cs 0.0: eth1: coax cable ok [720874.368100] 3c589_cs 0.0: eth1: coax cable problem [720877.368070] 3c589_cs 0.0: eth1: coax cable ok [720878.368100] 3c589_cs 0.0: eth1: coax cable problem [720902.368055] 3c589_cs 0.0: eth1: coax cable ok [720916.368076] 3c589_cs 0.0: eth1: coax cable problem [720925.368066] 3c589_cs 0.0: eth1: coax cable ok [720992.376075] 3c589_cs 0.0: eth1: coax cable problem [720993.376063] 3c589_cs 0.0: eth1: coax cable ok [721000.376060] 3c589_cs 0.0: eth1: coax cable problem [721002.376055] 3c589_cs 0.0: eth1: coax cable ok [721007.376050] 3c589_cs 0.0: eth1: coax cable problem [721008.376075] 3c589_cs 0.0: eth1: coax cable ok [721009.376095] 3c589_cs 0.0: eth1: coax cable problem [721026.376062] 3c589_cs 0.0: eth1: coax cable ok [721029.376060] 3c589_cs 0.0: eth1: coax cable problem [721030.376055] 3c589_cs 0.0: eth1: coax cable ok [721039.376062] 3c589_cs 0.0: eth1: coax cable problem [721041.376068] 3c589_cs 0.0: eth1: coax cable ok [721046.376061] 3c589_cs 0.0: eth1: coax cable problem [721047.376057] 3c589_cs 0.0: eth1: coax cable ok [721049.376069] 3c589_cs 0.0: eth1: coax cable problem [721051.376061] 3c589_cs 0.0: eth1: coax cable ok [721052.376072] 3c589_cs 0.0: eth1: coax cable problem [721056.376049] 3c589_cs 0.0: eth1: coax cable ok [721058.376069] 3c589_cs 0.0: eth1: coax cable problem [721061.376048] 3c589_cs 0.0: eth1: coax cable ok [721064.376066] 3c589_cs 0.0: eth1: coax cable problem [721065.376070] 3c589_cs 0.0: eth1: coax cable ok [721069.376097] 3c589_cs 0.0: eth1: coax cable problem [721070.376087] 3c589_cs 0.0: eth1: coax cable ok [721079.376080] 3c589_cs 0.0: eth1: coax cable problem [721083.376059] 3c589_cs 0.0: eth1: coax cable ok [721085.376069] 3c589_cs 0.0: eth1: coax cable problem [721092.376050] 3c589_cs 0.0: eth1: coax cable ok [721097.376059] 3c589_cs 0.0: eth1: coax cable problem [721101.376056] 3c589_cs 0.0: eth1: coax cable ok [721105.376065] 3c589_cs 0.0: eth1: coax cable problem [721106.376044] 3c589_cs 0.0: eth1: coax cable ok [721107.376072] 3c589_cs 0.0: eth1: coax cable problem [721108.376066] 3c589_cs 0.0: eth1: coax cable ok [72.376073] 3c589_cs 0.0: eth1: coax cable problem [721113.376036] 3c589_cs 0.0: eth1: coax cable ok [721115.376077] 3c589_cs 0.0: eth1: coax cable problem [721117.376056] 3c589_cs 0.0: eth1: coax cable ok [721120.376060] 3c589_cs 0.0: eth1: coax cable problem [721121.376038] 3c589_cs 0.0: eth1: coax cable ok [721127.376084] 3c589_cs 0.0: eth1: coax cable problem [721128.376080] 3c589_cs 0.0: eth1: coax cable ok [721130.376075] 3c589_cs 0.0: eth1: coax cable problem [721131.376052] 3c589_cs 0.0: eth1: coax cable ok [721137.376068] 3c589_cs 0.0: eth1: coax cable problem [721138.376045] 3c589_cs 0.0: eth1: coax cable ok [721148.376066] 3c589_cs 0.0: eth1: coax cable problem [721151.376058] 3c589_cs 0.0: eth1: coax cable ok [721152.376060] 3c589_cs 0.0: eth1: coax cable problem [721164.376071] 3c589_cs 0.0: eth1: coax cable ok [721166.376095] 3c589_cs 0.0: eth1: coax cable problem [721168.376055] 3c589_cs 0.0: eth1: coax cable ok [721173.376117] 3c589_cs 0.0: eth1: coax cable problem [721176.376079] 3c589_cs 0.0: eth1: coax cable ok [721177.376065] 3c589_cs 0.0: eth1: coax cable problem [721188.376059] 3c589_cs 0.0: eth1: coax cable ok [721189.376090] 3c589_cs 0.0: eth1: coax cable problem [721192.380041] 3c589_cs 0.0: eth1: coax cable ok [721198.915163] vlc[15041]: segfault at 70048d90 ip 7fda80842cb4 sp 7fda6ccbcfb0 error 4 in libdvdread.so.4.2.0[7fda8083f000+23000] [721235.086164] vlc[15075]:
Bug#657497: nfs-common: Exec permission denied
On 02/04/12 01:47, Tony Houghton wrote: Sorry about the lack of response. On Thu, 26 Jan 2012 22:14:41 + Ben Hutchingsb...@decadent.org.uk wrote: I assume you upgraded the client and not the server? Which was the previous version? (/var/log/dpkg.log should show this.) Did you upgrade the kernel at the same time? If so, what were the old and new package versions? Client and server were both upgraded from 1:1.2.5-3 to 1:1.2.5-4 on the same day. ls -l shows the x bit is still set, but I get permission denied when I try to run them, and bash's autocompletion also seems to know they're not executable because it doesn't expand them when I press Tab. I've tried adding 'exec' to fstab options but it didn't help. The same thing happens whether I use mount or pmount as a normal user or mount as root. Are all 'x' permission bits set? Do you also have read permission for the executables? ~ $ ls -l /media/htpc/hdvb/mscript.py -rwxr-xr-x 1 nobody nogroup 376 Jan 11 12:54 /media/htpc/hdvb/mscript.py ~ $ /media/htpc/hdvb/mscript.py bash: /media/htpc/hdvb/mscript.py: Permission denied I overlooked the nobody nogroup before. Is that normal? The UIDs are the same on both PCs and I can write to the file despite the discrepancy in the user and group names. Here I have to restart the idmapd service to get the names properly. -- 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/4f2d0ebb.5050...@gmail.com
Bug#658578: linux-image-2.6.32-5-amd64: Random kernel panic when inserting USB stick
On 02/04/12 16:21, Sergej Kochnev wrote: 0/usb5/5-2/5-2:1.0/host15/target15:0:0/15:0:0:0/bsg/15:0:0:0/uevent [ 282.240562] CPU 0 Try testing with one of the backported kernels. -- 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/4f2d0f96.8050...@gmail.com
Processed: unmerging 656724
Processing commands for cont...@bugs.debian.org: unmerge 656724 Bug#656724: linux-image-3.2.0-1-amd64: After installing this kernel syslogd reports a call trace always the same: Code: c0 89 c5 ... Bug#657526: linux-image-3.2.0-1-686-pae crashes after 50+ seconds Bug#657612: linux-image-3.2.0-1-amd64: scheduling while atomic: swapper/2/0/0x1100 Disconnected #656724 from all other report(s). thanks Stopping processing here. Please contact me if you need assistance. -- 657612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657612 657526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657526 656724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656724 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.132837409516434.transcr...@bugs.debian.org
Processed: unmerging 657526
Processing commands for cont...@bugs.debian.org: # unmerged wrong bug, merge 656724 657612 unmerge 657526 Bug#657526: linux-image-3.2.0-1-686-pae crashes after 50+ seconds Bug#657612: linux-image-3.2.0-1-amd64: scheduling while atomic: swapper/2/0/0x1100 Disconnected #657526 from all other report(s). thanks Stopping processing here. Please contact me if you need assistance. -- 657612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657612 657526: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657526 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.132837447118349.transcr...@bugs.debian.org
Processed: merging 656724 657612
Processing commands for cont...@bugs.debian.org: # damn I'm good at this merge 656724 657612 Bug#656724: linux-image-3.2.0-1-amd64: After installing this kernel syslogd reports a call trace always the same: Code: c0 89 c5 ... Bug#657612: linux-image-3.2.0-1-amd64: scheduling while atomic: swapper/2/0/0x1100 Merged 656724 657612. thanks Stopping processing here. Please contact me if you need assistance. -- 657612: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=657612 656724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656724 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.132837472720523.transcr...@bugs.debian.org
Processed: tagging 658164
Processing commands for cont...@bugs.debian.org: tags 658164 + pending Bug #658164 [linux-2.6] linux-image-3.1.0-1-amd64: Baud rate of FTDI USB-to-serial converter not initialized Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 658164: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658164 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.132837605128243.transcr...@bugs.debian.org
Processed: tagging 656724
Processing commands for cont...@bugs.debian.org: tags 656724 + pending Bug #656724 [linux-2.6] linux-image-3.2.0-1-amd64: After installing this kernel syslogd reports a call trace always the same: Code: c0 89 c5 ... Bug #657612 [linux-2.6] linux-image-3.2.0-1-amd64: scheduling while atomic: swapper/2/0/0x1100 Added tag(s) pending. Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 656724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656724 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.132837605328260.transcr...@bugs.debian.org
Uploading linux-2.6 (3.2.4-1)
On Tue, 2012-01-31 at 14:06 +, Ben Hutchings wrote: I intend to upload linux-2.6 version 3.2.2-1 to unstable shortly. This should fix the FTBFS on armel and various other bugs. SUBLEVEL = 4 And maybe we can fix the FTBFS on mips and finally get 3.2 into testing. Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Re: Uploading linux-2.6 (3.2.4-1)
On Sat, 2012-02-04 at 18:38 +0100, Ben Hutchings wrote: On Tue, 2012-01-31 at 14:06 +, Ben Hutchings wrote: I intend to upload linux-2.6 version 3.2.2-1 to unstable shortly. This should fix the FTBFS on armel and various other bugs. SUBLEVEL = 4 And maybe we can fix the FTBFS on mips and finally get 3.2 into testing. Well it looks like I won't be able to run a build until Monday as wake-on-LAN failed. Anyone else got the time to do this? Ben. -- Ben Hutchings The generation of random numbers is too important to be left to chance. - Robert Coveyou signature.asc Description: This is a digitally signed message part
Re: [bisected] Unstable desktop experience with kernel 2.6.38. PulseAudio involved
Hi, Just to let you know that, as could have been guessed from my initial post (http://lists.debian.org/debian-ia64/2012/01/msg00016.html), PulseAudio is involved. Uninstalling pulseaudio, pulseaudio-esound-compat, pulseaudio-module-x11, pulseaudio-utils and gstreamer0.10-pulseaudio packages fixes the issue. Obviously, you get no more sound :-(. Is there something in PulseAudio source code that hasn't been updated (maybe only on IA-64?) following commit 37a9d912b24f96a0591773e6e6c3642991ae5a70 (futex: Sanitize cmpxchg_futex_value_locked API)? The bad news: I can't provide more information at this time as all the programs that I've tried to ran through gdb (most notably iceweasel and gnome-terminal as they were my easy to reproduce scenarii) are receiving SIGTRAP signal, and bt full reports No symbol table info available. I however have debug packages installed. Émeric Le 28 janvier 2012 20:21, Patrick Baggett baggett.patr...@gmail.com a écrit : From looking at: http://neil.brown.name/git?p=linux-2.6;a=blobdiff;f=arch/ia64/include/asm/futex.h;h=b0728404dad05c9349aea95d4e28b91b1b363a21;hp=c7f0f062239cd541112ecbe10cdd34dc54672eec;hb=37a9d912b24f96a0591773e6e6c3642991ae5a70;hpb=522d7decc0370070448a8c28982c8dfd8970489e It doesn't look like the return value (r8) is actually being set beyond initialized to 0. If there is some ia64 instruction that modifies it, GCC doesn't know about it from the inline assembly (r8 doesn't appear in the inputs/outputs list). From looking at the x86 version (agh, inline asm is hard to parse), it does modify the return value based on whether the comparison was a success or not, and the return value is certainly used by the callers. Patrick On Sat, Jan 28, 2012 at 6:43 AM, Émeric Maschino emeric.masch...@gmail.com wrote: Hi, Just to let you know that I've bisected this issue to commit 37a9d912b24f96a0591773e6e6c3642991ae5a70 (futex: Sanitize cmpxchg_futex_value_locked API). Émeric Le 17 janvier 2012 23:11, Émeric Maschino emeric.masch...@gmail.com a écrit : Hi, Since there's a workaround allowing us to go kernel 2.6.38 (http://lists.debian.org/debian-ia64/2012/01/msg00013.html), I obviously updated my Testing system to current linux-image-3.1.0-1-mckinley_3.1.8-2_ia64.deb. Well, graphical desktop experience is _unstable_. When I say desktop experience, I'm talking about basic desktop tasks, not fancy OpenGL rendering. I have at least two reproducible scenari (I'm running Gnome Classic): - random X restart while typing into a GNOME terminal window - Iceweasel killed when I try to click on the Back button or while trying to click on the Edit menu. For the latter one, I managed to get a stack trace with gdb, before gdb itself core dumped (huge core available if interested!) or X is restarted... It seems that something goes wrong with PulseAudio when running kernel 3.1: Program received signal SIGABRT, Aborted. [Switching to Thread 0x7002b5231e0 (LWP 2282)] 0xa0040721 in __kernel_syscall_via_break () Thread 19 (Thread 0x7002b5231e0 (LWP 2282)): #0 0xa0040721 in __kernel_syscall_via_break () No symbol table info available. #1 0x2031a900 in raise () from /lib/ia64-linux-gnu/libc.so.6.1 No symbol table info available. #2 0x20322eb0 in abort () from /lib/ia64-linux-gnu/libc.so.6.1 No symbol table info available. #3 0x07001612a310 in pa_mutex_unlock () from /usr/lib/ia64-linux-gnu/libpulsecommon-1.0.so No symbol table info available. #4 0x07001604f8b0 in poll_func () from /usr/lib/ia64-linux-gnu/libpulse.so.0 No symbol table info available. Rebooting my Testing system with good old kernel 2.6.38-5 brings a stable desktop experience back. I've performed regression testing: the issue is already there with linux-image-2.6.39-rc4-mckinley_2.6.39~rc4-1~experimental.1_ia64.deb, the immediate successor to linux-image-2.6.38-2-mckinley_2.6.38-5_ia64.deb in snapshot.debian.org. Latest available linux-image-3.2.0-rc7-mckinley_3.2~rc7-1~experimental.1_ia64.deb still provides unstable desktop experience. Does this sound familiar to someone? Is this problem already known and reported somewhere or is it worth filing a bug and going the git bisect route? Émeric -- To UNSUBSCRIBE, email to debian-ia64-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caa9xbm5gw5tzfovtzykk8e8u6wkdfbeqrhblm_as9qq7...@mail.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/CAA9xbM4Jei9UnEQ+aX5Arh8=ftj2deopu5sopt8nrgiygoo...@mail.gmail.com
Bug#637199: [stanislav.maslov...@gmail.com: Re: oops when disconnecting an external hdd still mounted]
Forwarding to the bug log. ---BeginMessage--- Hello, Strange, I remember seeing this request and also checking that the bug was reprodicible without loaded virtualbox modules. Did I just forget to to write a reply?... Unfortunately, now I do not have any 32 bit installation of squeeze available for testing, and that laptop on which the bug was found and reported is several thousands kilometers away from my current location. I have just tested 2.6.32 from squeeze on a 64 bit installation of wheezy and the bug was not reproducible on this system. On Sat, Feb 04, 2012 at 01:15:11AM -0600, Jonathan Nieder wrote: Jonathan Nieder wrote: Can you reproduce this without the virtualbox drivers? Closing due to lack of response, but please don't hesitate to write if you have any more information about this, and we can revisit it. Sorry for the trouble, Jonathan -- Stanislav ---End Message---
Bug#637199: oops when disconnecting an external hdd still mounted
Stanislav Maslovski wrote: Strange, I remember seeing this request and also checking that the bug was reprodicible without loaded virtualbox modules. Did I just forget to to write a reply?... Unfortunately, now I do not have any 32 bit installation of squeeze available for testing, and that laptop on which the bug was found and reported is several thousands kilometers away from my current location. I have just tested 2.6.32 from squeeze on a 64 bit installation of wheezy and the bug was not reproducible on this system. Thanks for the update. For reference, here's the relevant log snippet: | [ 154.195805] usb 2-4: USB disconnect, address 4 | [ 163.641193] BUG: unable to handle kernel paging request at 00def000 | [ 163.641205] IP: [c1140c27] __percpu_counter_add+0x21/0x6d | [ 163.641221] *pde = | [ 163.641227] Oops: [#1] SMP | [ 163.641234] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0A:00/power_supply/BAT0/present | [ 163.641242] Modules linked in: ext3 jbd usb_storage acpi_cpufreq cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_powersave ipx p8023 parport_pc ppdev lp parport autofs4 vboxnetadp vboxnetflt vboxdrv binfmt_misc fuse dm_crypt dm_mod cls_fw sch_sfq sch_prio tun tcp_westwood iptable_raw ipt_LOG xt_limit xt_state iptable_filter ipt_MASQUERADE ipt_NETMAP iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack nf_defrag_ipv4 xt_length xt_tcpudp xt_dscp xt_MARK xt_owner iptable_mangle ip_tables x_tables coretemp firewire_sbp2 loop snd_hda_codec_idt usbhid hid arc4 btusb bluetooth ecb snd_hda_intel snd_hda_codec b43 rng_core snd_hwdep mac80211 snd_pcm snd_seq uvcvideo snd_timer snd_seq_device sg videodev sr_mod v4l1_compat snd cfg80211 sdhci_pci cdrom ssb joydev ata_generic sdhci firewire_ohci soundcore uhci_hcd pcmcia mmc_core firewire_core pcmcia_core snd_page_alloc ehci_hcd i2c_i801 dell_laptop crc_itu_t ata_piix tg3 psmouse led_class video ricoh_mmc rfkill i2c_core usbcore nl | s_base button ac battery libphy processor serio_raw output wmi evdev dcdbas ext4 mbcache jbd2 crc16 sd_mod crc_t10dif ahci libata scsi_mod thermal thermal_sys uvesafb cn | [ 163.641470] | [ 163.641478] Pid: 3315, comm: umount Not tainted (2.6.32-5-686 #1) Vostro 1400 | [ 163.641485] EIP: 0060:[c1140c27] EFLAGS: 00010006 CPU: 1 | [ 163.641493] EIP is at __percpu_counter_add+0x21/0x6d | [ 163.641498] EAX: 0001 EBX: f66534cc ECX: EDX: 0001 | [ 163.641505] ESI: f6823528 EDI: 00def000 EBP: 0010 ESP: f6503efc | [ 163.641510] DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 | [ 163.641518] Process umount (pid: 3315, ti=f6502000 task=f6fbeec0 task.ti=f6502000) | [ 163.641522] Stack: | [ 163.641526] f66534cc f6fbeec0 f6823528 f4dbc780 c108d515 0010 | [ 163.641540] 0 c1a747c0 c10cded2 ed1be400 f6f6f600 f6f6fc00 f84b4363 f6f6fc00 f84ba5b0 | [ 163.641555] 0 f84bde0c f4dbc780 c10b4e64 f6823400 0003 c10b4efe f6f6fc00 c10e3732 | [ 163.641571] Call Trace: | [ 163.641584] [c108d515] ? account_page_dirtied+0x2f/0x4b | [ 163.641595] [c10cded2] ? __set_page_dirty+0x44/0x82 | [ 163.641611] [f84b4363] ? ext3_put_super+0x69/0x1b6 [ext3] | [ 163.641622] [c10b4e64] ? generic_shutdown_super+0x46/0xc6 | [ 163.641632] [c10b4efe] ? kill_block_super+0x1a/0x2c | [ 163.641641] [c10e3732] ? vfs_quota_off+0x0/0xd | [ 163.641650] [c10b549b] ? deactivate_super+0x4a/0x5f | [ 163.641660] [c10c5487] ? sys_umount+0x2a5/0x2cb | [ 163.641669] [c10c54b8] ? sys_oldumount+0xb/0xe | [ 163.641680] [c10030fb] ? sysenter_do_call+0x12/0x28 | [ 163.641685] Code: ce 12 00 31 d2 89 d0 5b 5e c3 55 57 56 53 83 ec 04 89 04 24 8b 1c 24 64 a1 54 39 41 c1 8b 6c 24 18 8b 7b 14 03 3c 85 30 7d 3b c1 8b 07 89 c3 89 c6 c1 fe 1f 89 e8 01 d3 11 ce 99 39 d6 7f 15 7c | [ 163.641769] EIP: [c1140c27] __percpu_counter_add+0x21/0x6d SS:ESP 0068:f6503efc | [ 163.641781] CR2: 00def000 Not sure what would have triggered this. I'd like it to be fixed by v2.6.32.42~84 (block: add proper state guards to __elv_next_request) or some nearby fix applied in 2.6.32-36, but the symptoms don't match so well. Anyway, if you are able to reproduce this again (by using 2.6.32-35 from snapshot.debian.org, or if you get access to the relevant machine again), that would be very useful. Ciao, 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/20120204192316.GC22928@burratino
Bug#656331: RTL8168b/8111b with ASUS M2A-VM (SB600): Network device stays down after resume
found 656331 3.2.2-1 quit Dear Linux folks, Am Mittwoch, den 18.01.2012, 15:50 + schrieb Ben Hutchings: On Wed, 2012-01-18 at 16:32 +0100, Paul Menzel wrote: Am Mittwoch, den 18.01.2012, 15:03 + schrieb Ben Hutchings: On Wed, 2012-01-18 at 15:15 +0100, Paul Menzel wrote: Package: linux-2.6 Version: 3.1.8-2 Severity: normal suspending and resuming a lot, it happens once to me, that the network device did not come back correctly. I experienced this problem (only) three times until now. If I remember correctly the last time with 3.2.1. I still do not know how to reproduce this. The work around is to unplug and replug the network cable or to unload the module and load it again. [...] Some of the RTL81xx gigabit Ethernet controllers need a firmware patch to be reliable. I can't tell whether you have one of these. Are there any kernel log messages about requesting a firmware file for the NIC? If so, does installing firmware-realtek fix the problem? There are no Linux messages requesting the firmware. OK. And not being able to trigger I probably just have to wait that it happens again. Can I increase some log level to capture more information next time? Or since this could be a firmware bug Linux cannot do anything about this? No, it's probably something that can be fixed in the driver. That sounds promising. It would be great if this could be fixed. Please tell me how I can get you better debugging information next time this happens. $ dmesg | grep -i firmware $ dmesg | grep 8169 [1.109369] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [1.109417] r8169 :02:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [1.109452] r8169 :02:00.0: setting latency timer to 64 [1.109511] r8169 :02:00.0: irq 41 for MSI/MSI-X [1.110094] r8169 :02:00.0: eth0: RTL8168b/8111b at 0xc9364000, 00:1e:8c:aa:1d:b5, XID 1800 IRQ 41 [...] Right, this variant doesn't need a firmware patch. Please can you re-send your bug report to: […] Be sure to include the log messages from your second mail. Please find the messages from the Linux kernel ring buffer (`dmesg`) attached at the end. Thanks, Paul [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656331 $ dmesg | grep -i firmware $ dmesg | grep 8169 [1.109369] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded [1.109417] r8169 :02:00.0: PCI INT A - GSI 19 (level, low) - IRQ 19 [1.109452] r8169 :02:00.0: setting latency timer to 64 [1.109511] r8169 :02:00.0: irq 41 for MSI/MSI-X [1.110094] r8169 :02:00.0: eth0: RTL8168b/8111b at 0xc9364000, 00:1e:8c:aa:1d:b5, XID 1800 IRQ 41 [ 299.062777] r8169 :02:00.0: eth0: link down [ 300.770805] r8169 :02:00.0: eth0: link up [ 3287.250629] r8169 :02:00.0: PME# enabled [ 3287.397826] r8169 :02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [ 3287.397841] r8169 :02:00.0: restoring config space at offset 0x6 (was 0x4, writing 0xfdfff004) [ 3287.397848] r8169 :02:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xdc01) [ 3287.397853] r8169 :02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [ 3287.397860] r8169 :02:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 3287.398443] r8169 :02:00.0: PME# disabled [ 3314.429403] r8169 :02:00.0: eth0: link down [ 3314.429432] r8169 :02:00.0: eth0: link down [ 3316.043306] r8169 :02:00.0: eth0: link up [ 4821.512812] r8169 :02:00.0: PME# enabled [ 4821.661948] r8169 :02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [ 4821.661963] r8169 :02:00.0: restoring config space at offset 0x6 (was 0x4, writing 0xfdfff004) [ 4821.661969] r8169 :02:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xdc01) [ 4821.661975] r8169 :02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [ 4821.661981] r8169 :02:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 4821.662532] r8169 :02:00.0: PME# disabled [ 4839.563375] r8169 :02:00.0: eth0: link down [ 4839.563398] r8169 :02:00.0: eth0: link down [ 4841.198305] r8169 :02:00.0: eth0: link up [ 7732.802716] r8169 :02:00.0: PME# enabled [ 7732.910146] r8169 :02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a) [ 7732.910161] r8169 :02:00.0: restoring config space at offset 0x6 (was 0x4, writing 0xfdfff004) [ 7732.910168] r8169 :02:00.0: restoring config space at offset 0x4 (was 0x1, writing 0xdc01) [ 7732.910173] r8169 :02:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x8) [ 7732.910180] r8169 :02:00.0: restoring config space at offset 0x1 (was 0x10, writing 0x100407) [ 7732.910733] r8169 :02:00.0: PME# disabled [ 7761.865970] r8169 :02:00.0: eth0:
Processed: Re: Bug#656331: RTL8168b/8111b with ASUS M2A-VM (SB600): Network device stays down after resume
Processing commands for cont...@bugs.debian.org: found 656331 3.2.2-1 Bug #656331 [linux-2.6] r8169 with ASUS M2A-VM (SB600): Network device stays down after resume There is no source info for the package 'linux-2.6' at version '3.2.2-1' with architecture '' Unable to make a source version for version '3.2.2-1' Bug Marked as found in versions 3.2.2-1. quit Stopping processing here. Please contact me if you need assistance. -- 656331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=656331 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.132838357513392.transcr...@bugs.debian.org
Bug#649033: [PATCH] tpm_tis: add delay after aborting command
tags 649033 + pending quit Stefan Berger wrote: On Fri, Jan 20, 2012 at 01:19:54AM -0600, Jonathan Nieder wrote: So it looks like this is fixed by v3.3-rc1~105^2^2~13^2~4 (tpm_tis: add delay after aborting command, 2011-11-11). [...] I take it's not a problem in a Debian 3.0 kernel (since the culprit patch only appeared in 3.1-rc1). We will submit the relevant patch(es) to the 3.2.x stable kernel. Fixed in 3.2.3. Kernel team, please apply the following patch to mark it so. Thanks, Jonathan Index: debian/changelog === --- debian/changelog(revision 18664) +++ debian/changelog(working copy) @@ -7,6 +7,7 @@ - eCryptfs: Make truncate path killable - eCryptfs: Check inode changes in setattr - drm/i915: paper over missed irq issues with force wake voodoo +- tpm_tis: add delay after aborting command (Closes: #649033) - USB: ftdi_sio: fix initial baud rate (Closes: #658164) - USB: Realtek cr: fix autopm scheduling while atomic (Closes: #656724) -- 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/20120204195037.GA2116@burratino
Processed: Re: [PATCH] tpm_tis: add delay after aborting command
Processing commands for cont...@bugs.debian.org: tags 649033 + pending Bug #649033 [linux-2.6] tpm_tis: hang during initialization (udevd: timeout: killing '/sbin/modprobe -b acpi:SMO1200:PNP0C31:') Added tag(s) pending. quit Stopping processing here. Please contact me if you need assistance. -- 649033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=649033 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.132838507922082.transcr...@bugs.debian.org
Bug#658294: [3.1 - 3.2.2 regression] No more sound
tags 658294 + pending quit Jonathan Nieder wrote: The patch is part of v3.3-rc2 and has been queued by Greg for inclusion in version 3.2.3. ... and here's a quick patch to mark it so. Index: debian/changelog === --- debian/changelog(revision 18664) +++ debian/changelog(working copy) @@ -7,9 +7,11 @@ - eCryptfs: Make truncate path killable - eCryptfs: Check inode changes in setattr - drm/i915: paper over missed irq issues with force wake voodoo - tpm_tis: add delay after aborting command (Closes: #649033) - USB: ftdi_sio: fix initial baud rate (Closes: #658164) - USB: Realtek cr: fix autopm scheduling while atomic (Closes: #656724) +- ALSA: hda - Fix silent outputs from docking-station jacks of Dell + laptops (Closes: #658294) [ Ben Hutchings ] * [armel] Add mv78xx0 flavour; thanks to Steve McIntyre for the config -- 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/20120204200352.GA15778@burratino
Processed: Re: [3.1 - 3.2.2 regression] No more sound
Processing commands for cont...@bugs.debian.org: tags 658294 + pending Bug #658294 [linux-2.6] [linux-2.6] linux-image-3.2.0-1-amd64: No more sound Added tag(s) pending. quit Stopping processing here. Please contact me if you need assistance. -- 658294: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658294 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.132838586927955.transcr...@bugs.debian.org
Bug#620297: base: vmstat and /proc/loadavg disagree
found 620297 linux-2.6/3.2.2-1 quit Aman Gupta wrote: I tested the following kernels in tickless mode (CONFIG_NO_HZ=y), and they all contain the same load average reporting issue: 2.6.37-rc5-cure-more 2.6.39.4 3.2.2 3.2.4 Ah, excellent. ;-) Please report this to linux-ker...@vger.kernel.org, cc-ing Peter Zijlstra pet...@infradead.org, Chase Douglas chase.doug...@canonical.com, Damien Wyart damien.wy...@free.fr, Kyle McMartin k...@redhat.com, Venkatesh Pallipadi ve...@google.com, and either me or this bug log so we can track it. Be sure to mention: - steps to reproduce - expected results, actual results, and how the difference indicates a bug - which kernel versions and configurations you have tested and results for each - dmesg output from booting an affected kernel, as an attachment - any other thoughts or weird observations - a link to http://bugs.debian.org/620297 for the full story They may have ideas for commands or patches to try to help track the problem down. Sorry for the trouble, and hope that helps, Jonathan -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120204210951.GA3278@burratino
Processed: Re: base: vmstat and /proc/loadavg disagree
Processing commands for cont...@bugs.debian.org: found 620297 linux-2.6/3.2.2-1 Bug #620297 [linux-2.6] base: vmstat and /proc/loadavg disagree Bug Marked as found in versions linux-2.6/3.2.2-1. quit Stopping processing here. Please contact me if you need assistance. -- 620297: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=620297 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.132838988216891.transcr...@bugs.debian.org
Bug#658662: drm/i915: no signal via DisplayPort on Sandy Bridge since Linux 3.2
Package: linux-2.6 Version: 3.2.2-1 Severity: important Tags: upstream Dear Maintainer, Since upgrading to linux-image-3.2.0-1-amd64, an external display connected via DisplayPort to a Sandy Bridge onboard graphics card stopped working, and instead turns off reporting “DP no signal”. With linux-image-3.1.0-1-amd64, the same display connected via the DisplayPort works fine. After powering both the display and the machine, the display first turns on when the i915 kernel module is loaded upon boot. It shows the console with boot messages at the maximum display resolution (1920x1080). Then the X server starts, and the external display switches to a lower resolution (1024x768), which seems to be the default setting of the X server. After login, I manually switch to the maximum resolution (1920x1080) using the command “xrandr --output DP1 --auto”. With linux-image-3.2.0-1-amd64, after powering both the display and the machine, the display remains dark during boot, even when the i915 kernel module is loaded. The display first turns on only when the X server is loaded, with the default resolution 1024x768. After login, I manually switch to 1920x1080, but then the display reports “DP no signal” and turns *off*. To summarize: The external display connected via DisplayPort works fine with Linux 3.1, while, with Linux 3.2, it works with lower (non-native) resolutions and fails with the maximum (native) resolution. I noticed one peculiarity: It is possible to have a working external display by booting into Linux 3.1 first, and then rebooting into Linux 3.2 *without interrupting the power supply of the display*. However, as soon as I power-cycle the display while under Linux 3.2, it stops working again. There is a recent thread by Keith Packard with DisplayPort-related patches: https://lkml.org/lkml/2012/1/25/204 I tested both a kernel with only patch 1/2, as well as a kernel with both patches 1/2 and 2/2 applied, based on the Debian kernel source and using the test-patches script. Both kernels showed the same faulty behaviour, i.e. the external display remains dark at the native resolution. If there are other potential fixes I could test, please let me know. Thanks, Peter -- xrandr: Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192 LVDS1 connected 1366x768+0+0 (normal left inverted right x axis y axis) 277mm x 156mm 1366x768 60.0*+ 1360x768 59.8 60.0 1024x768 60.0 800x60060.3 56.2 640x48059.9 VGA1 disconnected (normal left inverted right x axis y axis) HDMI1 disconnected (normal left inverted right x axis y axis) DP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 477mm x 268mm 1920x1080 60.0*+ 1680x1050 60.0 1600x900 60.0 1280x1024 60.0 1280x800 59.8 1280x720 60.0 1024x768 60.0 800x60060.3 640x48060.0 HDMI2 disconnected (normal left inverted right x axis y axis) HDMI3 disconnected (normal left inverted right x axis y axis) DP2 disconnected (normal left inverted right x axis y axis) DP3 disconnected (normal left inverted right x axis y axis) -- Package-specific info: ** Version: Linux version 3.2.0-1-amd64 (Debian 3.2.2-1) (b...@decadent.org.uk) (gcc version 4.6.2 (Debian 4.6.2-12) ) #1 SMP Wed Feb 1 08:56:58 UTC 2012 ** Command line: BOOT_IMAGE=/vmlinuz-3.2.0-1-amd64 root=/dev/mapper/vg-root ro pcie_aspm=force i915.i915_enable_rc6=1 i915.i915_enable_fbc=1 i915.lvds_downclock=1 ** Not tainted ** Kernel log: [ 20.446802] [drm] Initialized drm 1.1.0 20060810 [ 20.910637] IBM TrackPoint firmware: 0x0e, buttons: 3/3 [ 20.928577] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/input/input4 [ 20.948229] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input5 [ 20.953169] HDMI status: Codec=3 Pin=5 Presence_Detect=0 ELD_Valid=0 [ 20.953416] HDMI status: Codec=3 Pin=6 Presence_Detect=0 ELD_Valid=0 [ 20.953667] HDMI status: Codec=3 Pin=7 Presence_Detect=0 ELD_Valid=0 [ 20.953878] input: HDA Intel PCH HDMI/DP,pcm=8 as /devices/pci:00/:00:1b.0/sound/card0/input6 [ 20.954053] input: HDA Intel PCH HDMI/DP,pcm=7 as /devices/pci:00/:00:1b.0/sound/card0/input7 [ 20.954225] input: HDA Intel PCH HDMI/DP,pcm=3 as /devices/pci:00/:00:1b.0/sound/card0/input8 [ 20.955314] i915 :00:02.0: power state changed by ACPI to D0 [ 20.955380] i915 :00:02.0: power state changed by ACPI to D0 [ 20.955446] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 20.955510] i915 :00:02.0: setting latency timer to 64 [ 20.983994] mtrr: no more MTRRs available [ 20.984054] [drm] MTRR allocation failed. Graphics performance may suffer. [ 20.984497] i915 :00:02.0: irq 51 for MSI/MSI-X [ 20.984501] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 20.984562] [drm] Driver supports precise vblank timestamp
Bug#658670: [2.6.32 - 3.1.8 regression] 3w-9xxx abnormally slows the system down
Hi Csaba, Csaba GAAL wrote: At first it seemed that I have found a bug in GNU Parted [...] “Unable to determine the size and length of /dev/sd[a-b][0-6]” [...] You are taking a long time to get to the point. ;-) I suppose after we deal with this speed regression, it will be useful to revisit that message and see if it can be eliminated. [...] http://lists.debian.org/debian-user/2011/12/msg00153.html [...] With returning to the kernel in linux-image-2.6.32-5-amd64 also did the speed. This also confirms that the speed degradation with 3.1.0-1-amd64 kernel has nothing to do with [...] If I understand correctly, you are reporting a speed regression between 2.6.32.y and 3.1.8-2. Thanks for finding it. Could you try versions 2.6.34-1~experimental.2 and 2.6.35~rc4-1~experimental.1 from http://snapshot.debian.org/, to hopefully narrow down the regression range? 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/20120205061017.GA1870@burratino
