6.1 kernel is missing CONFIG_VIRTIO_MEM (was present in 5.10)
Hi, It seem than virtio_mem module is not present in 6.1 config (It's a feature to have better memory hotplug/unplug with qemu-kvm) cat /boot/config-6.1.0-9-amd64 |grep VIRTIO_MEM # CONFIG_VIRTIO_MEM is not set Looking in 5.10 package, the dynamic module is set cat /boot/config-5.10.0-18-amd64 |grep VIRTIO_MEM CONFIG_VIRTIO_MEM=m Could it be possible to re-add it ? BTW, for my personal culture, I have looked in salsa git history, but I don't have found any reference about CONFIG_VIRTIO_MEM in bullseye branch, so how is it possible that the module was enabled on 5.10 ? Regards, Alexandre Derumier
Bug#1004347: wireless-regdb: Remove the suggestion
Package: wireless-regdb
Version: 2021.08.28
Followup-For: Bug #1004347
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu kinetic ubuntu-patch
Control: tags -1 patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to remove the obsolete
suggestion.
Thanks for considering the patch.
-- System Information:
Debian Release: bookworm/sid
APT prefers jammy-updates
APT policy: (500, 'jammy-updates'), (500, 'jammy-security'), (500, 'jammy')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.15.0-27-generic (SMP w/16 CPU threads)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL
set to en_US.UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
diff -Nru wireless-regdb-2021.08.28/debian/control
wireless-regdb-2021.08.28/debian/control
--- wireless-regdb-2021.08.28/debian/control2021-08-28 18:56:48.0
+0200
+++ wireless-regdb-2021.08.28/debian/control2022-05-12 13:10:31.0
+0200
@@ -15,7 +15,6 @@
Architecture: all
Multi-Arch: foreign
Depends: ${misc:Depends}
-Suggests: crda
Description: wireless regulatory database
This package contains the wireless regulatory database used by the Central
Regulatory Database Agent (CRDA) to configure wireless devices to operate
Bug#995466: linux-image-rt-amd64: Appears in "Obsolete and Locally Created Packages" on aptitude
Hi, On Oct 01 2021, Salvatore Bonaccorso wrote: > > Now I tried to reinstall it and it says that a source to that download > > version can't be found. There are newer versions of kernel available, > > but no "preemption real time" patches set. > > Yes that's correct. The reason is that the rt featureset has not (yet) > been re-enabled after the rebase to 5.14.y series. It might be > possible in a later upload if the version available upstream at > https://mirrors.edge.kernel.org/pub/linux/kernel/projects/rt/5.14/ > will apply on top of the version. Is there a reason to not have it enabled yet? I don't understand at a decent level how kernel works and if I really need a real time kernel here. I just have an external sound interface here and use it to record myself throught programs like ardour, using guitarix and/or rakarrak. > Regards, > Salvatore Best, Alexandre -- === Alexandre Lymberopoulos - lym...@gmail.com ===
Bug#995466: linux-image-rt-amd64: Appears in "Obsolete and Locally Created Packages" on aptitude
Package: linux-image-rt-amd64 Version: 5.10.46-4 Severity: normal Dear Maintainer, In aptitude this package appears in "Obsolete and Locally Created Packages", as well as the linux-image-5.10.0-8-rt-amd64 package versioned below. It seems that both of them should not be there since they were installed from aptitude and there is no other kernel version installed or running here. Now I tried to reinstall it and it says that a source to that download version can't be found. There are newer versions of kernel available, but no "preemption real time" patches set. Thanks in advance. Best, Alexandre -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 5.10.0-8-rt-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages linux-image-rt-amd64 depends on: ii linux-image-5.10.0-8-rt-amd64 5.10.46-4 linux-image-rt-amd64 recommends no packages. linux-image-rt-amd64 suggests no packages. -- no debconf information
Bug#968521: Update
I tried to create a new virtual machine with similar settings today and shutdown via Proxmox worked. The older virtual machine (created on 16/08) has exactly the same package versions and running kernel and was unable to shutdown via Proxmox until I reboot it today. Very strange. So it seems that this may not be a issue with the kernel but with Proxmox. Journal from Proxmox host before VM reboot: Aug 22 16:33:10 sam qm[51346]: starting task UPID:sam:C894:0239A288:5F412CA6:qmshutdown:106:root@pam: Aug 22 16:33:10 sam qm[51348]: shutdown VM 106: UPID:sam:C894:0239A288:5F412CA6:qmshutdown:106:root@pam: Aug 22 16:34:00 sam systemd[1]: Starting Proxmox VE replication runner... -- Subject: A start job for unit pvesr.service has begun execution -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit pvesr.service has begun execution. -- -- The job identifier is 358778. Aug 22 16:34:01 sam systemd[1]: pvesr.service: Succeeded. -- Subject: Unit succeeded -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- The unit pvesr.service has successfully entered the 'dead' state. Aug 22 16:34:01 sam systemd[1]: Started Proxmox VE replication runner. -- Subject: A start job for unit pvesr.service has finished successfully -- Defined-By: systemd -- Support: https://www.debian.org/support -- -- A start job for unit pvesr.service has finished successfully. -- -- The job identifier is 358778. Aug 22 16:34:57 sam qm[51348]: VM 106 qmp command failed - received interrupt Aug 22 16:34:57 sam qm[51348]: VM quit/powerdown failed Aug 22 16:34:57 sam qm[51346]: end task UPID:sam:C894:0239A288:5F412CA6:qmshutdown:106:root@pam: VM quit/powerdown failed After VM manual reboot: Aug 22 16:36:27 sam sudo[54269]: pam_unix(sudo:session): session opened for user root by erdnaxe(uid=0) Aug 22 16:36:28 sam qm[54270]: starting task UPID:sam:D400:0239F00C:5F412D6C:qmshutdown:106:root@pam: Aug 22 16:36:28 sam qm[54272]: shutdown VM 106: UPID:sam:D400:0239F00C:5F412D6C:qmshutdown:106:root@pam: Aug 22 16:36:31 sam kernel: vmbr10: port 5(tap106i0) entered disabled state Aug 22 16:36:31 sam qm[54270]: end task UPID:sam:D400:0239F00C:5F412D6C:qmshutdown:106:root@pam: OK Aug 22 16:36:31 sam sudo[54269]: pam_unix(sudo:session): session closed for user root If the problem reappear I will try to collect more information to open an issue on Proxmox side or Debian side. Sorry for the inconvenience, -- Alexandre<mailto:erdn...@crans.org>
Bug#968521: linux-image-4.19.0-10-cloud-amd64: not listening to ACPI shutdown
Package: src:linux Version: 4.19.132-1 Severity: important Dear Maintainer, When a new virtual machine is created using Debian Cloud image (debian-10-openstack-amd64.qcow2) it ships with linux-image-cloud-amd64. On the one hand, this looks nice as it deactivates many useless kernel modules, but on the other hand, our Proxmox host (using KVM) is not able to send a shutdown signal. When removing linux-image-cloud-amd64 (and linux-image-4.19.0-10-cloud-amd64) and installing linux-image-amd64, then Proxmox can shut down the virtual machine. This seems to be quite an annoying bug as it forces the user to remove a cloud-optimized kernel to be able to shut down virtual machines from the host. I expected that the Debian Cloud-optimized kernel works well with Proxmox, and it is not the case. -- Package-specific info: ** Version: Linux version 4.19.0-10-cloud-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP Debian 4.19.132-1 (2020-07-24) ** Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-10-cloud-amd64 root=UUID=42338e15-f98e-4b67-a46a-ea8f4a4225af ro nosplash text biosdevname=0 net.ifnames=0 console=tty0 console=ttyS0,115200 earlyprintk=ttyS0,115200 consoleblank=0 systemd.show_status=true ** Not tainted ** Kernel log: [1.380168] NET: Registered protocol family 17 [1.382207] mpls_gso: MPLS GSO support [1.383914] sched_clock: Marking stable (1361387673, 20661333)->(1382940204, -891198) [1.387713] registered taskstats version 1 [1.389518] Loading compiled-in X.509 certificates [1.482539] Loaded X.509 cert 'Debian Secure Boot CA: 6ccece7e4c6c0d1f6149f3dd27dfcc5cbb419ea1' [1.486021] Loaded X.509 cert 'Debian Secure Boot Signer 2020: 00b55eb3b9' [1.488780] AppArmor: AppArmor sha1 policy hashing enabled [1.491830] rtc_cmos 00:00: setting system clock to 2020-08-16 19:35:09 UTC (1597606509) [1.499376] Freeing unused kernel image memory: 1472K [1.517096] Write protecting the kernel read-only data: 16384k [1.522820] Freeing unused kernel image memory: 2028K [1.525762] Freeing unused kernel image memory: 1340K [1.528269] x86/mm: Checked W+X mappings: passed, no W+X pages found. [1.531018] x86/mm: Checking user space page tables [1.533133] x86/mm: Checked W+X mappings: passed, no W+X pages found. [1.535686] Run /init as init process [1.745256] SCSI subsystem initialized [1.763647] libata version 3.00 loaded. [1.767305] ata_piix :00:01.1: version 2.13 [1.770999] scsi host0: ata_piix [1.772101] scsi host1: ata_piix [1.772923] ata1: PATA max MWDMA2 cmd 0x1f0 ctl 0x3f6 bmdma 0xe100 irq 14 [1.774285] ata2: PATA max MWDMA2 cmd 0x170 ctl 0x376 bmdma 0xe108 irq 15 [1.783433] PCI Interrupt Link [LNKC] enabled at IRQ 11 [1.808934] PCI Interrupt Link [LNKA] enabled at IRQ 10 [1.834355] PCI Interrupt Link [LNKD] enabled at IRQ 11 [1.860095] PCI Interrupt Link [LNKB] enabled at IRQ 10 [1.896526] scsi host2: Virtio SCSI HBA [1.899003] scsi 2:0:0:0: Direct-Access QEMU QEMU HARDDISK2.5+ PQ: 0 ANSI: 5 [1.901025] scsi 2:0:0:1: Direct-Access QEMU QEMU HARDDISK2.5+ PQ: 0 ANSI: 5 [1.917925] random: fast init done [1.933879] ata1.01: NODEV after polling detection [1.934252] ata1.00: ATAPI: QEMU DVD-ROM, 2.5+, max UDMA/100 [1.936621] scsi 0:0:0:0: CD-ROMQEMU QEMU DVD-ROM 2.5+ PQ: 0 ANSI: 5 [1.946146] sd 2:0:0:0: Power-on or device reset occurred [1.947729] sd 2:0:0:1: Power-on or device reset occurred [1.949614] sd 2:0:0:0: [sda] 10485760 512-byte logical blocks: (5.37 GB/5.00 GiB) [1.951235] sd 2:0:0:0: [sda] Write Protect is off [1.951238] sd 2:0:0:1: [sdb] 33554432 512-byte logical blocks: (17.2 GB/16.0 GiB) [1.952231] sd 2:0:0:0: [sda] Mode Sense: 63 00 00 08 [1.953834] sd 2:0:0:1: [sdb] Write Protect is off [1.954824] sd 2:0:0:1: [sdb] Mode Sense: 63 00 00 08 [1.954897] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.956723] sd 2:0:0:1: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA [1.961032] sr 0:0:0:0: [sr0] scsi3-mmc drive: 4x/4x cd/rw xa/form2 tray [1.961759] sda: sda1 [1.962809] cdrom: Uniform CD-ROM driver Revision: 3.20 [1.964743] sdb: sdb1 [1.964971] sr 0:0:0:0: Attached scsi CD-ROM sr0 [1.969214] sd 2:0:0:0: [sda] Attached SCSI disk [1.970485] sd 2:0:0:1: [sdb] Attached SCSI disk [2.158540] cryptd: max_cpu_qlen set to 1000 [2.335065] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [2.574347] systemd[1]: Inserted module 'autofs4' [2.608224] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [2.616291] systemd[1]: Detected
Bug#932845: TS-219 RTC issue with Debian Buster
On 26/07/2019 11:27:11+0200, Oliver Hartkopp wrote: > Hello Uwe, > > On 26.07.19 09:27, Uwe Kleine-König wrote: > > Hello Alexandre, > > > > On Thu, Jul 25, 2019 at 04:31:49PM +0200, Oliver Hartkopp wrote: > > > On 24.07.19 09:07, Uwe Kleine-König wrote: > > > > On Tue, Jul 23, 2019 at 10:28:18PM +0200, Oliver Hartkopp wrote: > > > > > I'm running a TS-119P+ and a TS-219P II Qnap NAS with Debian Buster. > > > > > Both are now running a linux-image-4.19.0-5-marvell kernel. > > > > > > > > > > But since my update from Linux 4.9 (Stretch) to Linux 4.19 (Buster) > > > > > the > > > > > hardware clock of both boxes refuse to work. > > > > > > > > > > After some digging in kernel sources and re-installing Linux 4.9 on my > > > > > Buster setup it turns out, that a change in the kernel config causes > > > > > the > > > > > problem: > > > > > > > > > > 4.19.0-5-marvell -> CONFIG_RTC_DRV_S35390A=m (fails) > > > > > > > > > > 4.9.0-4-marvell -> CONFIG_RTC_DRV_S35390A=y(works) > > > > > > > > > > See details and solving process at: > > > > > > > > > > https://marc.info/?l=linux-arm-kernel=156390875629259=2 > > > > > > > > > > Can you please revert the Kernel config parts for the RTC in a way > > > > > that the > > > > > RTC drivers are built into the marvell-arch kernel again instead of > > > > > building > > > > > them as modules? > > > > > > > > They were switched to modules because the kernel image got too big to > > > > fit into the flash storage of some machines. I assume when we switch to > > > > built-in again the resulting problem is the bigger one. > > > > > > I don't know which is the bigger problem here. > > > > > > When the rtc driver is built as module it can not be operated with the > > > hwclock tool from the util-linux package due to the missing rtc UIE > > > support. > > > > > > You finally have no hardware clock on these machines and must wait for ntp > > > to shift time and date (my system always starts in February until ntp > > > fixes > > > the time). > > > > For me it's obvious what is the bigger problem. Either you don't have > > the correct time until ntp fixes it up for you, or others cannot install > > a kernel update and so run a vulnerable OS. > > That what I've written, NTP fixes the time for me. I have no problem with > updating my kernels - in fact I was even able to flash an older kernel to > figure out this rtc issue :-) > > > > Maybe this problem is only relevant for the S35390A and PCF8563 chip which > > > both lack the UIE support needed by hwclock. Both have only alarm triggers > > > in a minute accuracy according to the driver source code. > > > > AFAIK the rtc framework should then emulate this event somehow. > > I don't think so. When the rtc chip is not able to trigger an event with a > one second resolution - how can you emulate that? > CONFIG_RTC_INTF_DEV_UIE_EMUL emulates it by polling the RTC. -- Alexandre Belloni, Bootlin Embedded Linux and Kernel engineering https://bootlin.com
disk IO very low on debian 9.9 with kernel 4.9.0-9
Hello all, We recently found out that disk IO were very low when running debian 9.9 with the actual kernel 4.9.0-9. For example when we run this command: dd if=/dev/zero of=test bs=512 count=1000 oflag=dsync our tests show results between 40kB/s and 70kB/s at the best. We initially noticed those bad scores on our VMWare ESXi 6.0 and 6.7 platform (with a full flash SAN), but when we performed the same test on Hyper-V or Virtualbox on a PC (with SSD disk) the results were more or less the same (even worst for one them). The same test performed on a debian testing (with kernel 4.19.0-5) gives us scores between 200 and 400kB/s (the lowest was on my laptop with Virtualbox). We tried too on other linux distrib (unfortunately not with close version of kernel) and we usually got at least 50% more than the best score on debian testing :( After I compiled a new kernel for the debian 9.9 (4.19.37 from debian kernel source and 4.20.9 from kernel.org) I got results between 120 and 160kB/s. You can see the results below: root@debian9:/boot# cat /etc/debian_version && uname -sr && dd if=/dev/zero of=test3 bs=512 count=1000 oflag=dsync 9.9 Linux 4.20.9-amd64 1000+0 records in 1000+0 records out 512000 bytes (512 kB, 500 KiB) copied, 3.37676 s, 152 kB/s root@debian9:/boot# cat /etc/debian_version && uname -sr && dd if=/dev/zero of=test3 bs=512 count=1000 oflag=dsync 9.9 Linux 4.19.37-amd64 1000+0 records in 1000+0 records out 512000 bytes (512 kB, 500 KiB) copied, 4.09023 s, 125 kB/s root@debian9:~# cat /etc/debian_version && uname -sr && dd if=/dev/zero of=test3 bs=512 count=1000 oflag=dsync 9.9 Linux 4.9.0-9-amd64 1000+0 records in 1000+0 records out 512000 bytes (512 kB, 500 KiB) copied, 11.9743 s, 42.8 kB/s We didn't have time yet to install a debian 9.9 directly on a computer or a physical server directly to check if it could be linked to the virtualization, but we might give it a try next week. So did anyone of you encountered the same problem or know why it happens? Many Thanks, Regards, Alexandre
Re: Bug#854854: qcontrol: reboot/poweroff
Hi, On 16/03/2017 at 09:45:07 +0100, Uwe Kleine-König wrote: > Back then I prepared a backport to jessie (which still sits in a topic > branch in the debian-kernel repo[2]) but it seems I forgot to merge it into > the jessie kernel. > > I wonder if the better fix would be to fix this in linux-stable instead. > What do you think? > I agree that this should be backported to any stable kernel that is used by a distribution. I can ack the patch if you send one to stable@ -- Alexandre Belloni, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com
Bug#843510: linux-image-4.8.0-rc8-amd64-unsigned: Task timeout when workstation is connected
Package: src:linux Version: 4.8~rc8-1~exp1 Severity: grave Justification: renders package unusable Dear Maintainer, With my laptop (dell xps13 2015), when i connect a workstation to have ethernet connection for example, i have most task kernel timeout nov. 05 18:13:00 debian kernel: INFO: task kworker/0:1:2828 blocked for more than 120 seconds. nov. 05 18:13:00 debian kernel: Tainted: G U 4.7.0-1-amd64 #1 nov. 05 18:13:00 debian kernel: "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. nov. 05 18:13:00 debian kernel: kworker/0:1 D 88027ec16d80 0 2828 2 0x nov. 05 18:13:00 debian kernel: Workqueue: events rtl_work_func_t [r8152] nov. 05 18:13:00 debian kernel: 880270f8e040 aa40d500 88027ed96df0 88027114fcb8 nov. 05 18:13:00 debian kernel: 88027115 880274816948 880274816a08 nov. 05 18:13:00 debian kernel: 88027114fcb8 a9fd83d1 880274816898 nov. 05 18:13:00 debian kernel: Call Trace: nov. 05 18:13:00 debian kernel: [] ? schedule+0x31/0x80 nov. 05 18:13:00 debian kernel: [] ? rpm_resume+0x182/0x690 nov. 05 18:13:00 debian kernel: [] ? wake_atomic_t_function+0x60/0x60 nov. 05 18:13:00 debian kernel: [] ? rpm_resume+0x2e0/0x690 nov. 05 18:13:00 debian kernel: [] ? dequeue_entity+0x24b/0xb40 nov. 05 18:13:00 debian kernel: [] ? __pm_runtime_resume+0x47/0x70 nov. 05 18:13:00 debian kernel: [] ? usb_autopm_get_interface+0x1d/0x50 [usbcore] nov. 05 18:13:00 debian kernel: [] ? rtl_work_func_t+0x6f/0x3e2 [r8152] nov. 05 18:13:00 debian kernel: [] ? process_one_work+0x160/0x410 nov. 05 18:13:00 debian kernel: [] ? worker_thread+0x4d/0x480 nov. 05 18:13:00 debian kernel: [] ? process_one_work+0x410/0x410 nov. 05 18:13:00 debian kernel: [] ? kthread+0xcd/0xf0 nov. 05 18:13:00 debian kernel: [] ? ret_from_fork+0x1f/0x40 nov. 05 18:13:00 debian kernel: [] ? kthread_create_on_node+0x190/0x190 Nov 5 18:17:00 debian kernel: [ 2400.537014] INFO: task NetworkManager:2630 blocked for more than 120 seconds. Nov 5 18:17:00 debian kernel: [ 2400.537020] Tainted: G U 4.7.0-1-amd64 #1 Nov 5 18:17:00 debian kernel: [ 2400.537021] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 5 18:17:00 debian kernel: [ 2400.537023] NetworkManager D 88027ec96d80 0 2630 1 0x Nov 5 18:17:00 debian kernel: [ 2400.537027] 880273653040 8802752a1000 a9ec698e 0286 Nov 5 18:17:00 debian kernel: [ 2400.537030] 88005f60 88005f5ffc48 aa4d96c4 880273653040 Nov 5 18:17:00 debian kernel: [ 2400.537033] aa4d96c8 a9fd83d1 aa4d96c0 Nov 5 18:17:00 debian kernel: [ 2400.537036] Call Trace: Nov 5 18:17:00 debian kernel: [ 2400.537043] [] ? __kmalloc_reserve.isra.33+0x2e/0x80 Nov 5 18:17:00 debian kernel: [ 2400.537046] [] ? schedule+0x31/0x80 Nov 5 18:17:00 debian kernel: [ 2400.537049] [] ? schedule_preempt_disabled+0xa/0x10 Nov 5 18:17:00 debian kernel: [ 2400.537051] [] ? __mutex_lock_slowpath+0xb4/0x130 Nov 5 18:17:00 debian kernel: [ 2400.537054] [] ? mutex_lock+0x1b/0x30 Nov 5 18:17:00 debian kernel: [ 2400.537057] [] ? rtnetlink_rcv+0x15/0x30 Nov 5 18:17:00 debian kernel: [ 2400.537060] [] ? netlink_unicast+0x177/0x220 Nov 5 18:17:00 debian kernel: [ 2400.537062] [] ? netlink_sendmsg+0x2fe/0x3b0 Nov 5 18:17:00 debian kernel: [ 2400.537065] [] ? sock_sendmsg+0x30/0x40 Nov 5 18:17:00 debian kernel: [ 2400.537067] [] ? ___sys_sendmsg+0x28e/0x2a0 Nov 5 18:17:00 debian kernel: [ 2400.537072] [] ? memzero_explicit+0xe/0x10 Nov 5 18:17:00 debian kernel: [ 2400.537075] [] ? extract_buf+0xf6/0x120 Nov 5 18:17:00 debian kernel: [ 2400.537078] [] ? dput+0xbb/0x240 Nov 5 18:17:00 debian kernel: [ 2400.537081] [] ? __fput+0x164/0x1e0 Nov 5 18:17:00 debian kernel: [ 2400.537084] [] ? __sys_sendmsg+0x51/0x90 Nov 5 18:17:00 debian kernel: [ 2400.537087] [] ? system_call_fast_compare_end+0xc/0x96 Nov 5 18:17:00 debian kernel: [ 2400.537098] INFO: task DNS Res~ver #11:4128 blocked for more than 120 seconds. Nov 5 18:17:00 debian kernel: [ 2400.537100] Tainted: G U 4.7.0-1-amd64 #1 Nov 5 18:17:00 debian kernel: [ 2400.537101] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Nov 5 18:17:00 debian kernel: [ 2400.537103] DNS Res~ver #11 D 88027ec16d80 0 4128 1 0x Nov 5 18:17:00 debian kernel: [ 2400.537105] 8801b9178040 aa40d500 a9ec698e 0286 Nov 5 18:17:00 debian kernel: [ 2400.537108] 88018312c000 88018312bd38 aa4d96c4 8801b9178040 Nov 5 18:17:00 debian kernel: [ 2400.537110] aa4d96c8 a9fd83d1 aa4d96c0 Nov 5 18:17:00 debian kernel: [ 2400.537113] Call Trace: Nov 5 18:17:00 debian kernel: [ 2400.537115] [] ? __kmalloc_reserve.isra.33+0x2e/0x80 Nov 5
Bug#839158: linux-image-4.8.0-rc8-amd64-unsigned: Kernel crash randomly
Package: src:linux Version: 4.8~rc8-1~exp1 Severity: normal Dear Maintainer, Randomly my kernel crash : Sep 29 17:11:59 debian org.gtk.vfs.Daemon[3071]: A connection to the bus can't be made Sep 29 17:11:59 debian gnome-session[3075]: Unable to init server: Could not connect: Connection refused Sep 29 17:11:59 debian [20894]: Cannot open display: Sep 29 17:12:31 debian kernel: [23316.368483] [ cut here ] Sep 29 17:12:31 debian kernel: [23316.368511] WARNING: CPU: 0 PID: 2305 at /build/linux-gWtKZJ/linux-4.8~rc8/drivers/gpu/drm/i915/intel_display.c:13647 intel_atomic_commit_tail+0x10e3/0x10f0 [i915] Sep 29 17:12:31 debian kernel: [23316.368512] pipe A vblank wait timed out Sep 29 17:12:31 debian kernel: [23316.368529] Modules linked in: rfcomm(E) fuse(E) nvram(E) msr(E) xt_CHECKSUM(E) iptable_mangle(E) ipt_MASQUERADE(E) nf_nat_masquerade_ipv4(E) iptable_nat(E) nf_nat_ipv4(E) nf_nat(E) nf_conntrack_ipv4(E) nf_defrag_ipv4(E) xt_conntrack(E) nf_conntrack(E) ipt_REJECT(E) nf_reject_ipv4(E) xt_tcpudp(E) tun(E) bridge(E) stp(E) llc(E) ebtable_filter(E) ebtables(E) ip6table_filter(E) ip6_tables(E) iptable_filter(E) ip_tables(E) x_tables(E) uvcvideo(E) videobuf2_vmalloc(E) videobuf2_memops(E) videobuf2_v4l2(E) videobuf2_core(E) videodev(E) btusb(E) media(E) btrtl(E) snd_hda_codec_hdmi(E) snd_hda_codec_realtek(E) snd_hda_codec_generic(E) bnep(E) hid_multitouch(E) binfmt_misc(E) nls_ascii(E) nls_cp437(E) vfat(E) fat(E) intel_rapl(E) x86_pkg_temp_thermal(E) intel_powerclamp(E) dcdbas(E) coretemp(E) iTCO_wdt(E) iTCO_vendor_support(E) i2c_designware_platform(E) i2c_designware_core(E) kvm_intel(E) kvm(E) irqbypass(E) evdev(E) joydev(E) serio_raw(E) efi_pstore(E) snd_soc_skl(E) snd_soc_skl_ipc(E) snd_soc_sst_ipc(E) snd_soc_sst_dsp(E) snd_hda_ext_core(E) efivars(E) snd_soc_sst_match(E) snd_soc_core(E) snd_compress(E) snd_hda_intel(E) snd_hda_codec(E) snd_hda_core(E) snd_hwdep(E) snd_pcm(E) i2c_i801(E) snd_timer(E) i2c_smbus(E) snd(E) soundcore(E) brcmfmac(E) brcmutil(E) rtsx_pci_ms(E) cfg80211(E) memstick(E) i915(E) shpchp(E) drm_kms_helper(E) mei_me(E) drm(E) idma64(E) mei(E) virt_dma(E) processor_thermal_device(E) i2c_algo_bit(E) intel_soc_dts_iosf(E) intel_pch_thermal(E) intel_lpss_pci(E) wmi(E) hci_uart(E) btbcm(E) btqca(E) btintel(E) bluetooth(E) rfkill(E) video(E) intel_lpss_acpi(E) intel_lpss(E) int3403_thermal(E) int340x_thermal_zone(E) int3400_thermal(E) acpi_thermal_rel(E) battery(E) ac(E) button(E) acpi_pad(E) acpi_als(E) kfifo_buf(E) industrialio(E) tpm_tis(E) tpm_tis_core(E) tpm(E) parport_pc(E) ppdev(E) lp(E) parport(E) efivarfs(E) autofs4(E) ext4(E) crc16(E) jbd2(E) fscrypto(E) mbcache(E) algif_skcipher(E) af_alg(E) usbhid(E) dm_crypt(E) dm_mod(E) rtsx_pci_sdmmc(E) mmc_core(E) crct10dif_pclmul(E) crc32_pclmul(E) crc32c_intel(E) ghash_clmulni_intel(E) aesni_intel(E) aes_x86_64(E) lrw(E) gf128mul(E) glue_helper(E) ablk_helper(E) cryptd(E) psmouse(E) ahci(E) libahci(E) rtsx_pci(E) mfd_core(E) xhci_pci(E) nvme(E) xhci_hcd(E) nvme_core(E) libata(E) usbcore(E) usb_common(E) scsi_mod(E) fan(E) thermal(E) i2c_hid(E) hid(E) fjes(E) Sep 29 17:12:31 debian kernel: [23316.368564] CPU: 0 PID: 2305 Comm: systemd- logind Tainted: G U W E 4.8.0-rc8-amd64 #1 Debian 4.8~rc8-1~exp1 Sep 29 17:12:31 debian kernel: [23316.368565] Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.1.9 12/18/2015 Sep 29 17:12:31 debian kernel: [23316.368567] 0286 38682724 86b24c05 958f725eb8a8 Sep 29 17:12:31 debian kernel: [23316.368568] 8687c19e 958f7499 958f725eb900 Sep 29 17:12:31 debian kernel: [23316.368569] 958f714a3000 Sep 29 17:12:31 debian kernel: [23316.368570] Call Trace: Sep 29 17:12:31 debian kernel: [23316.368574] [] ? dump_stack+0x5c/0x77 Sep 29 17:12:31 debian kernel: [23316.368576] [] ? __warn+0xbe/0xe0 Sep 29 17:12:31 debian kernel: [23316.368578] [] ? warn_slowpath_fmt+0x5f/0x80 Sep 29 17:12:31 debian kernel: [23316.368580] [] ? finish_wait+0x3e/0x70 Sep 29 17:12:31 debian kernel: [23316.368597] [] ? intel_atomic_commit_tail+0x10e3/0x10f0 [i915] Sep 29 17:12:31 debian kernel: [23316.368598] [] ? wake_atomic_t_function+0x60/0x60 Sep 29 17:12:31 debian kernel: [23316.368614] [] ? intel_atomic_commit+0x438/0x560 [i915] Sep 29 17:12:31 debian kernel: [23316.368628] [] ? drm_atomic_add_affected_connectors+0x22/0xe0 [drm] Sep 29 17:12:31 debian kernel: [23316.368635] [] ? restore_fbdev_mode+0x14c/0x260 [drm_kms_helper] Sep 29 17:12:31 debian kernel: [23316.368639] [] ? drm_fb_helper_restore_fbdev_mode_unlocked+0x2e/0x70 [drm_kms_helper] Sep 29 17:12:31 debian kernel: [23316.368643] [] ? drm_fb_helper_set_par+0x29/0x50 [drm_kms_helper] Sep 29 17:12:31 debian kernel: [23316.368661] [] ? intel_fbdev_set_par+0x16/0x60 [i915] Sep 29 17:12:31 debian kernel: [23316.368664] [] ? fb_set_var+0x208/0x410 Sep 29 17:12:31 debian kernel: [23316.368666] [] ?
Bug#827283: linux-image-4.5.0-0.bpo.2-armmp: none
Package: src:linux Version: 4.5.4-1~bpo8+1 Severity: normal Dear Maintainer, I try linux-image-4.5.0-0.bpo.2-armmp and linux-image-4.5.0-0.bpo.2-armmp-lpae on LeMaker Banana Pi, unfortunately the GMAC won't work in this kernel, i get this error: [ 117.215251] libphy: PHY stmmac-0: not found [ 117.220186] eth0: Could not attach to PHY [ 117.224234] stmmac_open: Cannot attach to PHY (error: -19) As stated below. Kernel 3.16.0-4-armmp-lpae work Thanks. -- Package-specific info: ** Version: Linux version 4.5.0-0.bpo.2-armmp (debian-kernel@lists.debian.org) (gcc version 4.9.2 (Debian 4.9.2-10) ) #1 SMP Debian 4.5.4-1~bpo8+1 (2016-05-13) ** Command line: console=ttyS0,115200 quiet ** Tainted: E (8192) * Unsigned module has been loaded (currently expected). ** Kernel log: [5.710063] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.710077] usb usb2: Product: EHCI Host Controller [5.710087] usb usb2: Manufacturer: Linux 4.5.0-0.bpo.2-armmp ehci_hcd [5.710097] usb usb2: SerialNumber: 1c1c000.usb [5.716250] hub 2-0:1.0: USB hub found [5.716383] hub 2-0:1.0: 1 port detected [5.720303] ohci-platform 1c14400.usb: Generic Platform OHCI controller [5.720369] ohci-platform 1c14400.usb: new USB bus registered, assigned bus number 3 [5.722269] ohci-platform 1c14400.usb: irq 30, io mem 0x01c14400 [5.781753] usb usb3: New USB device found, idVendor=1d6b, idProduct=0001 [5.781779] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.781790] usb usb3: Product: Generic Platform OHCI controller [5.781800] usb usb3: Manufacturer: Linux 4.5.0-0.bpo.2-armmp ohci_hcd [5.781809] usb usb3: SerialNumber: 1c14400.usb [5.782916] hub 3-0:1.0: USB hub found [5.784614] hub 3-0:1.0: 1 port detected [5.789951] ohci-platform 1c1c400.usb: Generic Platform OHCI controller [5.790051] ohci-platform 1c1c400.usb: new USB bus registered, assigned bus number 4 [5.790530] ohci-platform 1c1c400.usb: irq 34, io mem 0x01c1c400 [5.849758] usb usb4: New USB device found, idVendor=1d6b, idProduct=0001 [5.849784] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [5.849795] usb usb4: Product: Generic Platform OHCI controller [5.849805] usb usb4: Manufacturer: Linux 4.5.0-0.bpo.2-armmp ohci_hcd [5.849814] usb usb4: SerialNumber: 1c1c400.usb [5.852841] hub 4-0:1.0: USB hub found [5.852950] hub 4-0:1.0: 1 port detected [5.878571] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [5.983763] systemd-journald[149]: Received request to flush runtime journal from PID 1 [5.985586] usb 1-1: new high-speed USB device number 2 using ehci-platform [6.122001] usb 1-1: New USB device found, idVendor=04e8, idProduct=6860 [6.122030] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [6.122040] usb 1-1: Product: SAMSUNG_Android [6.122050] usb 1-1: Manufacturer: SAMSUNG [6.122059] usb 1-1: SerialNumber: 474e650b [6.363290] libphy: PHY stmmac-0: not found [6.368290] eth0: Could not attach to PHY [6.372341] stmmac_open: Cannot attach to PHY (error: -19) [6.683068] libphy: PHY stmmac-0: not found [6.688077] eth0: Could not attach to PHY [6.692153] stmmac_open: Cannot attach to PHY (error: -19) [7.059096] RPC: Registered named UNIX socket transport module. [7.059124] RPC: Registered udp transport module. [7.059131] RPC: Registered tcp transport module. [7.059138] RPC: Registered tcp NFSv4.1 backchannel transport module. [7.084946] FS-Cache: Loaded [7.133567] FS-Cache: Netfs 'nfs' registered for caching [7.190755] Installing knfsd (copyright (C) 1996 o...@monad.swb.de). [ 10.004853] random: nonblocking pool is initialized [ 41.993906] EXT4-fs (mmcblk0p1): re-mounted. Opts: errors=remount-ro [ 46.434225] libphy: PHY stmmac-0: not found [ 46.439223] eth0: Could not attach to PHY [ 46.443281] stmmac_open: Cannot attach to PHY (error: -19) [ 1053.081987] libphy: PHY stmmac-0: not found [ 1053.086938] eth0: Could not attach to PHY [ 1053.090993] stmmac_open: Cannot attach to PHY (error: -19) [ 1061.144311] libphy: PHY stmmac-0: not found [ 1061.149277] eth0: Could not attach to PHY [ 1061.153330] stmmac_open: Cannot attach to PHY (error: -19) [ 1065.242647] libphy: PHY stmmac-0: not found [ 1065.247611] eth0: Could not attach to PHY [ 1065.251680] stmmac_open: Cannot attach to PHY (error: -19) [ 1073.300570] libphy: PHY stmmac-0: not found [ 1073.305573] eth0: Could not attach to PHY [ 1073.309660] stmmac_open: Cannot attach to PHY (error: -19) [ 1077.401114] libphy: PHY stmmac-0: not found [ 1077.406104] eth0: Could not attach to PHY [ 1077.410170] stmmac_open: Cannot attach to PHY (error: -19) [ 1085.459834] libphy: PHY stmmac-0: not found [ 1085.464835] eth0: Could not attach to PHY [ 1085.468925] stmmac_open:
Bug#801925: NULL pointer dereference: IP: [] sr_runtime_suspend+0xc/0x20 [sr_mod]
Hello,
>> > As this is Linux 4.3 and not 4.4, I guess this is a different problem
>> > though. Alexandre, where you able to capture the stack trace? I’d submit
>> > a new bug report with this.
>>
>> Here is a photo. Please ping me if you need to test some debugging patches.
>
> It looks like the problem occurs in blk_post_runtime_resume(). Since
> there have been recent changes to this routine, it's hard to tell
> whether you're using the most up-to-date code.
>
> In particular, the first few lines of blk_post_runtime_resume() in
> block/blk-core.c should look like this:
>
> void blk_post_runtime_resume(struct request_queue *q, int err)
> {
> if (!q->dev)
> return;
>
> The test was introduced by commit 4fd41a8552af ("SCSI: Fix NULL pointer
> dereference in runtime PM"), which was added to the mainline kernel
> between 4.3 and 4.4. I don't know what the commit ID would be for a
> .stable kernel.
Okay now I've tried with 4.4. The oops does not occur. So this is
fixed for me in 4.4.
If there is interest in backporting to 4.3, 13b438914341 ("SCSI: fix
crashes in sd and sr runtime PM") is not enough to backport. Something
in 4.4, most probably 4fd41a8552af ("SCSI: Fix NULL pointer
dereference in runtime PM") is also needed.
Thanks a lot,
Alex
Bug#812196: linux-image-4.4.0-trunk-amd64: Laptop reboot after suspend system
Package: src:linux Version: 4.4-1~exp1 Severity: grave Justification: renders package unusable Dear Maintainer, After suspend my laptop (hibernation) i have this message in syslog : Jan 21 12:16:53 debian dnsmasq[986]: no servers found in /etc/resolv.conf, will retry Jan 21 12:16:53 debian gnome-session[863]: Window manager warning: Failed to read EDID of output eDP32: Aucun fichier ou dossier de ce type Jan 21 12:16:53 debian gnome-session[863]: Window manager warning: Failed to set power save mode for output eDP32: Permission non accordée Jan 21 12:16:54 debian kernel: [ 4939.143250] brcmfmac: brcmf_cfg80211_reg_notifier: not a ISO3166 code Jan 21 12:16:54 debian kernel: [ 4939.143265] cfg80211: World regulatory domain updated: Jan 21 12:16:54 debian kernel: [ 4939.143271] cfg80211: DFS Master region: unset Jan 21 12:16:54 debian kernel: [ 4939.143276] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp), (dfs_cac_time) Jan 21 12:16:54 debian kernel: [ 4939.143286] cfg80211: (2402000 KHz - 2472000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Jan 21 12:16:54 debian kernel: [ 4939.143293] cfg80211: (2457000 KHz - 2482000 KHz @ 4 KHz), (N/A, 2000 mBm), (N/A) Jan 21 12:16:54 debian kernel: [ 4939.143299] cfg80211: (2474000 KHz - 2494000 KHz @ 2 KHz), (N/A, 2000 mBm), (N/A) Jan 21 12:16:54 debian kernel: [ 4939.143308] cfg80211: (517 KHz - 525 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (N/A) Jan 21 12:16:54 debian kernel: [ 4939.143316] cfg80211: (525 KHz - 533 KHz @ 8 KHz, 16 KHz AUTO), (N/A, 2000 mBm), (0 s) Jan 21 12:16:54 debian kernel: [ 4939.143324] cfg80211: (549 KHz - 573 KHz @ 16 KHz), (N/A, 2000 mBm), (0 s) Jan 21 12:16:54 debian kernel: [ 4939.143330] cfg80211: (5735000 KHz - 5835000 KHz @ 8 KHz), (N/A, 2000 mBm), (N/A) Jan 21 12:16:54 debian kernel: [ 4939.143337] cfg80211: (5724 KHz - 6372 KHz @ 216 KHz), (N/A, 0 mBm), (N/A) Jan 21 12:16:54 debian NetworkManager[707]: Failed to GDBus.Error:fi.w1.wpa_supplicant1.NotConnected: This interface is not connected: disconnect. Jan 21 12:16:54 debian dbus[712]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm- dispatcher.service' Jan 21 12:16:54 debian gnome-session[863]: Gjs-Message: JS LOG: An active wireless connection, in infrastructure mode, involves no access point? Jan 21 12:16:54 debian systemd[1]: Starting Network Manager Script Dispatcher Service... Jan 21 12:16:54 debian evolution.desktop[2511]: evolution-shell-Message: Network disconnected. Forced offline. Jan 21 12:16:54 debian dbus[712]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Jan 21 12:16:54 debian systemd[1]: Started Network Manager Script Dispatcher Service. Jan 21 12:16:54 debian nm-dispatcher: Dispatching action 'down' for wlp58s0 Jan 21 12:16:58 debian org.freedesktop.Telepathy.ConnectionManager.salut[1388]: tp-glib-Message: Exiting Jan 21 12:16:58 debian systemd[1]: Reached target Sleep. Jan 21 12:16:58 debian systemd[1]: Starting Suspend... Jan 21 12:16:58 debian systemd-sleep[4293]: Suspending system... When i try to resume my laptop reboot with this message in syslog : Jan 21 13:41:51 debian kernel: [0.657877] PM: Hibernation image not present or could not be loaded. Jan 21 13:41:51 debian kernel: [0.658559] Freeing unused kernel memory: 1296K (81b0b000 - 81c4f000) Jan 21 13:41:51 debian kernel: [0.658560] Write protecting the kernel read- only data: 10240k Jan 21 13:41:51 debian kernel: [0.659407] Freeing unused kernel memory: 468K (88000178b000 - 88000180) Jan 21 13:41:51 debian kernel: [0.661337] Freeing unused kernel memory: 1296K (880001abc000 - 880001c0) Jan 21 13:41:51 debian kernel: [0.661340] [ cut here ] Jan 21 13:41:51 debian kernel: [0.661343] WARNING: CPU: 2 PID: 1 at /build /linux-tEELBQ/linux-4.4/arch/x86/mm/dump_pagetables.c:225 note_page+0x5e1/0x790() Jan 21 13:41:51 debian kernel: [0.661344] x86/mm: Found insecure W+X mapping at address 8805f000/0x8805f000 Jan 21 13:41:51 debian kernel: [0.661345] Modules linked in: Jan 21 13:41:51 debian kernel: [0.661347] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.0-trunk-amd64 #1 Debian 4.4-1~exp1 Jan 21 13:41:51 debian kernel: [0.661348] Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.0.0 09/10/2015 Jan 21 13:41:51 debian kernel: [0.661348] 5b9bc4bd 812e5fb9 8802b6c4fde0 Jan 21 13:41:51 debian kernel: [0.661350] 810762ad 8802b6c4fed0 8802b6c4fe38 0004 Jan 21 13:41:51 debian kernel: [0.661351] 8802b6c4fed0 8107633c 817f1538 Jan 21 13:41:51 debian kernel: [0.661353] Call Trace: Jan 21 13:41:51 debian kernel: [0.661356] [] ? dump_stack+0x40/0x57 Jan 21 13:41:51 debian
Bug#801925: NULL pointer dereference: IP: [] sr_runtime_suspend+0xc/0x20 [sr_mod]
Hi, >> Could you please attach the debugging patch. Hopefully Alexandre, Erich, >> or I will have some spare time to build an image from it. > > Actually, this patch is an attempt at a fix. After looking more > carefully at your log pictures, I realized what the problem must be. > > It's too bad nobody was able to capture a log where the error > occurred in sr_runtime_suspend, though -- all the logs in the bug > report show sd_runtime_resume. I just tested the patch applied on top of 4.3.3 (4.3.3-6 in Debian). It still crashes at boot, but the stacktrace is different : it happens in blk_post_runtime_resume . Maybe I'm bit by a different bug or maybe the I need to try with 4.4. I'll post the captured log when I have access to a wired network. I'd be happy to provide the logs of a debugging patch. Alex
Bug#808038: error on boot
So, with kernel rc8 and nvme module enabled and i915.preliminary_hw_support=1 in my boot parameters (grub) sometime i can't boot due to error, but sometime it work (this morning 4 try to boot, 0 success) : Jan 7 10:14:06 debian kernel: [ 13.268486] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input8 Jan 7 10:14:06 debian kernel: [ 13.695176] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)! Jan 7 10:14:06 debian kernel: [ 13.711154] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)! Jan 7 10:14:06 debian kernel: [ 13.727151] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)! Jan 7 10:14:06 debian kernel: [ 13.743147] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)! Jan 7 10:14:06 debian kernel: [ 13.759146] [drm:intel_dp_aux_ch [i915]] *ERROR* dp aux hw did not signal timeout (has irq: 1)! Jan 7 10:14:06 debian kernel: [ 13.759161] [drm:intel_dp_aux_ch [i915]] *ERROR* dp_aux_ch not done status 0xad40001f [ cut here ] Jan 7 10:14:06 debian kernel: [ 13.783141] WARNING: CPU: 0 PID: 278 at /build/linux-dUKt9u/linux- 4.3.3/drivers/gpu/drm/i915/intel_dp.c:854 intel_dp_aux_ch+0x112/0x670 [i915] () Jan 7 10:14:06 debian kernel: [ 13.783141] dp_aux_ch not started status 0xad40001f Jan 7 10:14:06 debian kernel: [ 13.783165] Modules linked in: nls_utf8 nls_cp437 vfat fat snd_hda_codec_hdmi dell_led snd_hda_codec_realtek snd_hda_codec_generic intel_rapl x86_pkg _temp_thermal intel_powerclamp dell_laptop coretemp dell_wmi dcdbas joydev sparse_keymap kvm_intel kvm psmouse uvcvideo evdev i915 snd_hda_intel efi_pstore serio_raw snd _hda_codec snd_hda_core efivars snd_hwdep snd_pcm videobuf2_vmalloc videobuf2_memops snd_timer rtsx_pci_ms snd soundcore memstick videobuf2_core i2c_i801 drm_kms_helper v4l2_co mmon videodev drm media btusb processor_thermal_device mei_me btrtl shpchp tpm_tis intel_soc_dts_iosf hid_multitouch mei i2c_algo_bit iosf_mbi tpm wmi battery hci_uart btbcm bt intel bluetooth rfkill int3400_thermal video acpi_thermal_rel int3403_thermal int340x_thermal_zone acpi_pad ac button processor parport_pc ppdev lp parport efivarfs autofs4 ext 4 crc16 mbcache jbd2 algif_skcipher af_alg usbhid dm_crypt dm_mod crct10dif_pclmul crc32_pclmul crc32c_intel jitterentropy_rng rtsx_pci_sdmmc mmc_core sha256_ssse3 sha256_gener ic hmac drbg ansi_cprng aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd nvme rtsx_pci xhci_pci mfd_core xhci_hcd usbcore usb_common fan thermal i2c_hid hid Jan 7 10:14:06 debian kernel: [ 13.783180] CPU: 0 PID: 278 Comm: kworker/u8:4 Not tainted 4.3.0-1-amd64 #1 Debian 4.3.3-5 Jan 7 10:14:06 debian kernel: [ 13.783181] Hardware name: Dell Inc. XPS 13 9350/0PWNCR, BIOS 1.0.0 09/10/2015 Jan 7 10:14:06 debian kernel: [ 13.783184] Workqueue: events_unbound async_run_entry_fn Jan 7 10:14:06 debian kernel: [ 13.783186] 9fed5c92 812ddce9 8802b23cf728 Jan 7 10:14:06 debian kernel: [ 13.783186] 81072b1d ad40001f 8802b23cf780 fff0 Jan 7 10:14:06 debian kernel: [ 13.783187] 00064014 8802b2c3 81072bac a06f0210 Jan 7 10:14:06 debian kernel: [ 13.783188] Call Trace: Jan 7 10:14:06 debian kernel: [ 13.783192] [] ? dump_stack+0x40/0x57 Jan 7 10:14:06 debian kernel: [ 13.783194] [] ? warn_slowpath_common+0x7d/0xb0 Jan 7 10:14:06 debian kernel: [ 13.783195] [] ? warn_slowpath_fmt+0x5c/0x80 Jan 7 10:14:06 debian kernel: [ 13.783210] [] ? intel_dp_aux_ch+0x112/0x670 [i915] Jan 7 10:14:06 debian kernel: [ 13.783212] [] ? wake_atomic_t_function+0x60/0x60 Jan 7 10:14:06 debian kernel: [ 13.783226] [] ? intel_dp_aux_transfer+0xd0/0x1e0 [i915] Jan 7 10:14:06 debian kernel: [ 13.783242] [] ? gen9_read32+0xf4/0x2c0 [i915] Jan 7 10:14:06 debian kernel: [ 13.783246] [] ? drm_dp_dpcd_access+0x68/0x110 [drm_kms_helper] Jan 7 10:14:06 debian kernel: [ 13.783249] [] ? drm_dp_dpcd_write+0x17/0x20 [drm_kms_helper] Jan 7 10:14:06 debian kernel: [ 13.783265] [] ? intel_dp_sink_dpms+0x4a/0xe0 [i915] Jan 7 10:14:06 debian kernel: [ 13.783280] [] ? intel_ddi_pre_enable+0xff/0x310 [i915] Jan 7 10:14:06 debian kernel: [ 13.783296] [] ? haswell_crtc_enable+0x402/0xb70 [i915] Jan 7 10:14:06 debian kernel: [ 13.783310] [] ? intel_display_power_put+0xe1/0x150 [i915] Jan 7 10:14:06 debian kernel: [ 13.783326] [] ? intel_atomic_commit+0x388/0x12f0 [i915] Jan 7 10:14:06 debian kernel: [ 13.783337] [] ? drm_atomic_check_only+0x214/0x540 [drm] Jan 7 10:14:06 debian kernel: [ 13.783342] [] ? drm_atomic_helper_set_config+0x1af/0x410 [drm_kms_helper] Jan 7 10:14:06 debian kernel: [ 13.783349] [] ? drm_mode_set_config_internal+0x5e/0xf0 [drm] Jan 7 10:14:06 debian kernel: [ 13.783353] [] ? restore_fbdev_mode+0xaa/0x110
Bug#808038: Re: Bug#808038: Same problem with RC8
Thank you Hugo, i confirm that when i enabled «nvme» module in initramfs-tools/modules I have no error messages and Luks ask me my password. But once i entered i have a black screen and I can't do anything. My laptop don't boot and i must press power button to turn off and reboot on kernel 4-3... I don't know if it's a kernel problem or other problem but i don't know where i can found related logs. Thank you.
Bug#808038: same problem
I have exactly the same problem on rc6
Bug#801925: Linux Null Pointer Dereference on boot
Hi, Same here, last working debian kernel is linux-image-4.1.0-2-amd64 . Kernel hangs on early boot, after a while it notices and drops to an initramfs shell, lacking a root device. I managed to capture de OOPS using the handy netconsole module (attached). > On second thought, it seems more likely that this issue probably was > _caused_ by that commit. The fix can be found in these two emails: > > http://marc.info/?l=linux-scsi=144185206825609=2 > http://marc.info/?l=linux-scsi=144185208525611=2 > > which have not been merged yet as far as I know even though they were > submitted back in September. Those patches do not fix the problem for me. I tested using debian/bin/test-patches from the Debian Linux source. Thanks, Alex [2.561223] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [2.561719] ata2.00: ACPI cmd 00/00:00:00:00:00:a0 (NOP) rejected by device (Stat=0x51 Err=0x04) [2.561775] ata2.00: supports DRM functions and may not be fully accessible [2.565750] ata2.00: disabling queued TRIM support [2.565758] ata2.00: ATA-9: Crucial_CT256M550SSD1, MU01, max UDMA/133 [2.565762] ata2.00: 500118192 sectors, multi 16: LBA48 NCQ (depth 31/32), AA [2.570661] ata2.00: supports DRM functions and may not be fully accessible [2.579029] ata2.00: configured for UDMA/133 [2.905416] ata4: SATA link down (SStatus 0 SControl 300) [2.910964] BUG: unable to handle kernel NULL pointer dereference at 0008 [2.911135] PGD 0 [2.911215] Modules linked in: sd_mod(+) crc32c_intel ahci libahci libata xhci_pci scsi_mod xhci_hcd i915 ehci_pci ehci_hcd sdhci_pci sdhci mmc_core i2c_algo_bit drm_kms_helper usbcore usb_common e1000e ptp drm pps_core wmi thermal video button [2.911552] Hardware name: Hewlett-Packard HP ProBook 6470b/179C, BIOS 68ICE Ver. F.45 10/07/2013 [2.911665] RIP: 0010:[] [] sd_resume+0xd/0x70 [sd_mod] [2.911731] RSP: 0018:8801390a3a60 EFLAGS: 00010246 [2.911818] RDX: 0001 RSI: 880139398168 RDI: 880139398168 [2.911918] R10: 81827b86 R11: 000e R12: a0019220 [2.912017] FS: 7fc6c2e168c0() GS:88013fac() knlGS: [2.912113] CR2: 0008 CR3: 0001390c7000 CR4: 001406e0 [2.912161] Stack: [2.912247] 81403aae 880139398168 a03f2a20 [2.912382] Call Trace: [2.912470] [] ? __rpm_callback+0x2e/0x70 [2.912519] [] ? scsi_autopm_put_device+0x20/0x20 [scsi_mod] [2.912619] [] ? scsi_autopm_put_device+0x20/0x20 [scsi_mod] [2.912744] [] ? __pm_runtime_resume+0x47/0x70 [2.912848] [] ? sd_probe+0x35/0x340 [sd_mod] [2.912959] [] ? __driver_attach+0x7b/0x80 [2.913064] [] ? bus_for_each_dev+0x67/0xb0 [2.913152] [] ? 0xa0024000 [2.913190] [] ? driver_register+0x57/0xc0 [2.913312] [] ? do_one_initcall+0xb2/0x200 [2.913417] [] ? load_module+0x2173/0x2780 [2.913504] [] ? kernel_read+0x4b/0x70 [2.913623] [] ? system_call_fast_compare_end+0xc/0x67 [2.914161] RIP [] sd_resume+0xd/0x70 [sd_mod] [2.914212] RSP [2.914239] CR2: 0008 [2.916695] ---[ end trace 6a25c092cd6e126d ]---
Bug#808038: same problem on RC5
I have the same problem with linux-image-4.4.0-rc5
Bug#808038: linux-image-4.4.0-rc4-amd64: Fails to boot on kernel 4.4rc4
Package: linux-image-4.4.0-rc4-amd64 Version: 4.4~rc4-1~exp1 Severity: critical Justification: breaks the whole system Dear Maintainer, Actually, i'm usging linux-image-4.3.0-trunk-amd64 on Dell XPS 13 9350. In order to fix WiFi problem i would install linux-image-4.4.0rc4 but it makes it impossible to boot my laptop. I have this message before Luks ask passphrase : Loading, please wait... modprobe: module microcode not found in modules.dep lvmetad is not active yet, using direct activation during sysinit volume group "vg" not found Cannot process volume group vg /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Reading all physical volumes. This may take a while... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Reading all physical volumes. This may take a while... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Reading all physical volumes. This may take a while... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Reading all physical volumes. This may take a while... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. Reading all physical volumes. This may take a while... /run/lvm/lvmetad.socket: connect failed: No such file or directory WARNING: Failed to connect to lvmetad. Falling back to internal scanning. -- System Information: Debian Release: stretch/sid APT prefers stable APT policy: (1001, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 4.2.0-1-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Bug#780920: firmware-iwlwifi: iwlwifi-7260-8.ucode causes frequent network disconnections problems
Package: firmware-iwlwifi Version: 0.43 Severity: important Dear Maintainer, I use wifi with my Lenovo X240 with the Intel network controller 7260. Just below, the lspci command output : 03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 6b) Subsystem: Intel Corporation Wireless-N 7260 Flags: bus master, fast devsel, latency 0, IRQ 63 Memory at e040 (64-bit, non-prefetchable) [size=8K] Capabilities: [c8] Power Management version 3 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Capabilities: [40] Express Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Capabilities: [140] Device Serial Number 7c-7a-91-ff-ff-05-6b-e4 Capabilities: [14c] Latency Tolerance Reporting Capabilities: [154] Vendor Specific Information: ID=cafe Rev=1 Len=014 ? Kernel driver in use: iwlwifi I am running Debian Jessie x86_64. I am connecting to my wireless ADSL router (Technicolor TG789vn v3) with this options (iwconfig output) : wlan0 IEEE 802.11bgn ESSID:ManaBOX8A99EB Mode:Managed Frequency:2.412 GHz Access Point: 9C:97:26:8A:99:EB Bit Rate=1 Mb/s Tx-Power=22 dBm Retry short limit:7 RTS thr:off Fragment thr:off Encryption key:off Power Management:on Link Quality=70/70 Signal level=-34 dBm Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:71 Missed beacon:0 The Bit Rate alternate between 1 and 70 Mb/s. My issue : frequent disconnections (every 20/30mn) with complete network controller loss. I disable and enable wifi controller with the hotkey, and it works again (for 20/40mn). This is an extract of my network manager log (/var/log/daemon.log) of this issue : Mar 17 10:11:00 x240 wpa_supplicant[1145]: wlan0: CTRL-EVENT-DISCONNECTED bssid=9c:97:26:8a:99:eb reason=4 locally_generated=1 Mar 17 10:11:00 x240 NetworkManager[748]: warn Connection disconnected (reason -4) Mar 17 10:11:00 x240 wpa_supplicant[1145]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD Mar 17 10:11:00 x240 NetworkManager[748]: info (wlan0): supplicant interface state: completed - disconnected Mar 17 10:11:00 x240 NetworkManager[748]: info (wlan0): supplicant interface state: disconnected - scanning Mar 17 10:11:01 x240 wpa_supplicant[1145]: wlan0: SME: Trying to authenticate with 9c:97:26:8a:99:eb (SSID='ManaBOX8A99EB' freq=2437 MHz) Mar 17 10:11:01 x240 NetworkManager[748]: info (wlan0): supplicant interface state: scanning - authenticating Mar 17 10:11:01 x240 NetworkManager[748]: info (wlan0): supplicant interface state: authenticating - disconnected Mar 17 10:11:02 x240 NetworkManager[748]: info (wlan0): supplicant interface state: disconnected - scanning Mar 17 10:11:03 x240 wpa_supplicant[1145]: wlan0: SME: Trying to authenticate with 9c:97:26:8a:99:eb (SSID='ManaBOX8A99EB' freq=2437 MHz) Mar 17 10:11:03 x240 NetworkManager[748]: info (wlan0): supplicant interface state: scanning - authenticating Mar 17 10:11:03 x240 NetworkManager[748]: info (wlan0): supplicant interface state: authenticating - disconnected Mar 17 10:11:04 x240 NetworkManager[748]: info (wlan0): supplicant interface state: disconnected - scanning Mar 17 10:11:05 x240 wpa_supplicant[1145]: wlan0: SME: Trying to authenticate with 9c:97:26:8a:99:eb (SSID='ManaBOX8A99EB' freq=2437 MHz) Mar 17 10:11:05 x240 NetworkManager[748]: info (wlan0): supplicant interface state: scanning - authenticating Mar 17 10:11:05 x240 wpa_supplicant[1145]: wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid=ManaBOX8A99EB auth_failures=1 duration=10 reason=CONN_FAILED Mar 17 10:11:05 x240 NetworkManager[748]: info (wlan0): supplicant interface state: authenticating - disconnected Mar 17 10:11:10 x240 NetworkManager[748]: info (wlan0): supplicant interface state: disconnected - scanning Mar 17 10:11:15 x240 NetworkManager[748]: warn (wlan0): link timed out. Mar 17 10:11:15 x240 NetworkManager[748]: info (wlan0): device state change: activated - failed (reason 'ssid-not-found') [100 120 53] Mar 17 10:11:15 x240 NetworkManager[748]: info NetworkManager state is now CONNECTED_LOCAL Mar 17 10:11:15 x240 NetworkManager[748]: info NetworkManager state is now DISCONNECTED Mar 17 10:11:15 x240 NetworkManager[748]: warn Activation (wlan0) failed for connection 'ManaBOX8A99EB' Mar 17 10:11:15 x240 dbus[754]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm- dispatcher.service' Mar 17 10:11:15 x240 NetworkManager[748]: info (wlan0): device state change: failed - disconnected (reason 'none') [120 30 0] Mar 17 10:11:15 x240 NetworkManager[748]: info (wlan0): deactivating device (reason 'none') [0] Mar 17 10:11:15 x240 dbus[754]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher' Mar 17 10:11:15 x240 nm-dispatcher: Dispatching action 'down' for wlan0 Mar 17 10:11:15 x240
Bug#775217: drm/i915: Add limited color range readout for HDMI/DP ports on g4x/vlv/chv
Source: linux Severity: important Tags: upstream patch Dear Maintainers, Officiel kernel regularly spits out the following when plugged to a HDMI TV. This *may* lead to HDMI link instabilities and EDID checksum mismatchs, although I have not been able to reproduce my single occurence of broken TV output. [179305.004168] [drm:intel_pipe_config_compare] *ERROR* mismatch in limited_color_range (expected 1, found 0) [179305.004176] [ cut here ] [179305.004221] WARNING: CPU: 0 PID: 22693 at /build/linux-CMiYW9/linux-3.16.7-ckt2/drivers/gpu/drm/i915/intel_display.c:10192 check_crtc_state+0x743/0xda0 [i915]() [179305.004265] pipe state doesn't match! [179305.004268] Modules linked in: sha256_ssse3 sha256_generic dm_crypt ecb cbc algif_skcipher af_alg veth binfmt_misc cpufreq_stats cpufreq_powersave cpufreq_userspace cpufreq_conservative iptable_nat nf_nat_ipv4 ipt_REJECT iptable_mangle iptable_raw nf_conntrack_ipv4 nf_defrag_ipv4 xt_recent ip6table_nat nf_nat_ipv6 xt_comment ip6t_REJECT xt_addrtype xt_physdev xt_mark ip6table_mangle xt_tcpudp xt_CT ip6table_raw xt_multiport nf_conntrack_ipv6 nf_defrag_ipv6 ipt_ULOG xt_conntrack nf_nat_tftp nf_nat_snmp_basic nf_conntrack_snmp nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda xt_NFLOG nf_nat nfnetlink_log xt_LOG nf_conntrack_tftp nf_conntrack_sip nf_conntrack_sane nf_conntrack_proto_udplite nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nfnetlink nf_conntrack_netbios_ns nf_conntrack_broadcast nf_conntrack_irc ts_kmp nf_conntrack_h323 nf_conntrack_ftp nf_conntrack_amanda nf_conntrack ip6table_filter ip6_tab les iptable_filter ip_tables x_tables bridge stp llc iTCO_wdt iTCO_vendor_support snd_hda_codec_hdmi snd_hda_codec_via snd_hda_codec_generic ppdev snd_hda_intel snd_hda_controller snd_hda_codec snd_hwdep snd_pcm coretemp lpc_ich i915 pcspkr snd_timer evdev serio_raw video drm_kms_helper drm i2c_i801 mfd_core snd soundcore tpm_infineon i2c_algo_bit i2c_core tpm_tis tpm rng_core shpchp parport_pc parport button acpi_cpufreq processor thermal_sys loop fuse autofs4 ext4 crc16 mbcache jbd2 dm_mod raid1 md_mod sg sd_mod crc_t10dif crct10dif_generic crct10dif_common sr_mod cdrom ata_generic 8139too ata_piix 8139cp mii libata scsi_mod ehci_pci atl1c uhci_hcd ehci_hcd usbcore usb_common [179305.00] CPU: 0 PID: 22693 Comm: Xorg Tainted: GW 3.16.0-4-amd64 #1 Debian 3.16.7-ckt2-1 [179305.004448] Hardware name: MSI MS-7592/G41M-P34 (MS-7592), BIOS V25.3 03/03/2010 [179305.004451] 0009 81507263 88005a9c3a30 81065847 [179305.004457] 88007a69a058 88005a9c3a80 88007910f800 88007a69a6f8 [179305.004462] 88007910fb40 810658ac a03f8672 0018 [179305.004467] Call Trace: [179305.004478] [81507263] ? dump_stack+0x41/0x51 [179305.004485] [81065847] ? warn_slowpath_common+0x77/0x90 [179305.004490] [810658ac] ? warn_slowpath_fmt+0x4c/0x50 [179305.004517] [a0394de3] ? check_crtc_state+0x743/0xda0 [i915] [179305.004545] [a03a2e95] ? intel_modeset_check_state+0x255/0x780 [i915] [179305.004563] [a02e3554] ? _object_find+0x64/0x90 [drm] [179305.004580] [a02e8fd6] ? drm_mode_obj_set_property_ioctl+0x396/0x3b0 [drm] [179305.004596] [a02e901e] ? drm_mode_connector_property_set_ioctl+0x2e/0x40 [drm] [179305.004610] [a02d88b7] ? drm_ioctl+0x1c7/0x5b0 [drm] [179305.004621] [813ff397] ? move_addr_to_user+0xa7/0xc0 [179305.004627] [811b7d2f] ? do_vfs_ioctl+0x2cf/0x4b0 [179305.004632] [811b7f91] ? SyS_ioctl+0x81/0xa0 [179305.004637] [8150f368] ? page_fault+0x28/0x30 [179305.004643] [8150d32d] ? system_call_fast_compare_end+0x10/0x15 [179305.004646] ---[ end trace 72d92f83c05ee4fc ]--- The attached patch fixes the problem. It has been accepted upstream. Thanks, Alex -- System Information: Debian Release: 8.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) From: Alexandre Rossi alexandre.ro...@gmail.com Patch forward ported to apply with c84db77010877da6c5da119868ed54c43d59e726 (drm/i915/hdmi: fix hdmi audio state readout). From 8c875fca1a8d76665c60fa141c220cee65f44f5e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Syrj=C3=A4l=C3=A4?= ville.syrj...@linux.intel.com Date: Fri, 12 Sep 2014 15:46:29 +0300 Subject: drm/i915: Add limited color range readout for HDMI/DP ports on g4x/vlv/chv MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The limited color range knob is in the port registers on g4x and vlv/chv for HDMI, and on g4x for DP. Add the relevant code to read out the hardware state
Re: Bug report on nfs-common: nfsidmap crashes with exit status 139
Hi Ben, On Wed, Jun 26, 2013 at 9:40 PM, Ben Hutchings b...@decadent.org.uk wrote: It's a bit late for that, as you sent mail to a public mailing list. As I mentioned in the debian-devel thread, I realize only now that many emails (about 20% in our case), that are listed as package maintainers, are public mailing lists. That's unfortunate, but hopefully most reported bugs will not be security critical. There does not seem to be any way to make the kernel invoke nfsidmap with an invalid option as used in the test case, and I don't see any reason for a user to invoke it directly with untrusted input. So I don't think there is any security issue here. That's a good point, and it looks like a majority of the crashes have little security implications. The security tags will be removed before submitting the report, unless advised otherwise by the package maintainers. Thanks, Alex -- 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/CAF1AS2hHdOc+PT=OP4oDiiCcdGqBq25JTXua=g9-4sufelm...@mail.gmail.com
Bug report on nfs-common: nfsidmap crashes with exit status 139
Hi, We found a crash in nfsidmap contained in the nfs-common package. You are being contacted because your are listed as one of the maintainer of nfs-common. We are planning to submit the bug to the Debian bug tracking system in two weeks. We wanted to give you a heads-up, so that you some time to assess the seriousness of the bug before it is publicly disclosed. The bug report that will be submitted to the bug tracker is available at the following url: http://www.forallsecure.com/bug-reports/557e857e10afad31f118e3534f57d3cf7645d9fd/ This email is part of a mass bug reporting campain comprising 1,182 bugs. You might have received multiple emails from us concerning different programs. More information about the mass bug reporting is available on the debian-devel mailing list: http://lists.debian.org/debian-devel/2013/06/msg00720.html Regards, The Mayhem Team Cylab, Carnegie Mellon University -- 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/201306261746.r5qhkicl015...@smtp.andrew.cmu.edu
Bug#713800: linux-image-3.9-1-amd64: Brightness control ineffective under
Package: src:linux Version: 3.9.6-1 Severity: normal Dear Maintainer, After upgrading to linux-image-3.9-1-amd64 on my Macbook Pro (with nvidia-glx), I cannot change the brightness under KDE anymore. I already found a workaround: echo 3 /sys/class/backlight/gmux_backlight/brightness changes the brightness. Apparently the acpi_video0 is not working anymore, which is the cause of the problem. -- Package-specific info: ** Version: Linux version 3.9-1-amd64 (debian-kernel@lists.debian.org) (gcc version 4.7.3 (Debian 4.7.3-4) ) #1 SMP Debian 3.9.6-1 ** Command line: BOOT_IMAGE=/vmlinuz-3.9-1-amd64 root=UUID=e2bf20af-2b6e-4b03-a89b-2409673227ac ro quiet ** Tainted: PO (4097) * Proprietary module has been loaded. * Out-of-tree module has been loaded. ** Kernel log: [ 29.916682] Bluetooth: BNEP socket layer initialized [ 30.144487] applesmc: light sensor data length set to 10 [ 32.22] lp: driver loaded but no devices found [ 32.368281] ppdev: user-space parallel port driver [ 34.545143] tg3 :02:00.0: irq 43 for MSI/MSI-X [ 35.329394] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready [ 35.647548] brcmsmac bcma0:0: firmware: agent loaded brcm/bcm43xx-0.fw into memory [ 35.732804] brcmsmac bcma0:0: firmware: agent loaded brcm/bcm43xx_hdr-0.fw into memory [ 35.750687] brcmsmac bcma0:0: brcms_ops_bss_info_changed: qos enabled: false (implement) [ 35.750813] brcmsmac bcma0:0: brcms_ops_config: change power-save mode: false (implement) [ 35.752004] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 40.989713] tg3 :02:00.0 eth0: Link is up at 1000 Mbps, full duplex [ 40.989793] tg3 :02:00.0 eth0: Flow control is off for TX and off for RX [ 40.989817] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 52.465092] ACPI: EC: GPE storm detected(13 GPEs), transactions will use polling mode [ 259.100871] traps: ld-linux-x32.so[7201] general protection ip:f7756e9d sp:ffa389b8 error:0 in ld-2.17.so[f774+21000] [ 259.110641] traps: ld-linux-x32.so[7215] general protection ip:f773fe9d sp:ffd2eac8 error:0 in ld-2.17.so[f7729000+21000] [ 259.120857] traps: ld-linux-x32.so[7229] general protection ip:f779fe9d sp:ff96b918 error:0 in ld-2.17.so[f7789000+21000] [ 259.522516] traps: ld-linux-x32.so[7324] general protection ip:f7761e9d sp:ffd438e8 error:0 in ld-2.17.so[f774b000+21000] [ 259.533615] traps: ld-linux-x32.so[7338] general protection ip:f77b6e9d sp:ffc14968 error:0 in ld-2.17.so[f77a+21000] [ 259.544154] traps: ld-linux-x32.so[7352] general protection ip:f7703e9d sp:ffb57508 error:0 in ld-2.17.so[f76ed000+21000] [ 259.554480] traps: ld-linux-x32.so[7366] general protection ip:f77a0e9d sp:ffc4c3d8 error:0 in ld-2.17.so[f778a000+21000] [ 259.565438] traps: ld-linux-x32.so[7380] general protection ip:f77c5e9d sp:ffd09ec8 error:0 in ld-2.17.so[f77af000+21000] [ 259.576033] traps: ld-linux-x32.so[7394] general protection ip:f77a0e9d sp:ff8c1408 error:0 in ld-2.17.so[f778a000+21000] [ 259.585598] traps: ld-linux-x32.so[7408] general protection ip:f77d7e9d sp:ff947978 error:0 in ld-2.17.so[f77c1000+21000] [ 265.274924] do_general_protection: 25 callbacks suppressed [ 265.274928] traps: ld-linux-x32.so[9228] general protection ip:f77c8e9d sp:ffa28628 error:0 in ld-2.17.so[f77b2000+21000] [12185.283350] traps: ld-linux-x32.so[11952] general protection ip:f7796e9d sp:ff871d88 error:0 in ld-2.17.so[f778+21000] [12185.293125] traps: ld-linux-x32.so[11966] general protection ip:f7729e9d sp:ffac0278 error:0 in ld-2.17.so[f7713000+21000] [12185.302424] traps: ld-linux-x32.so[11980] general protection ip:f76f8e9d sp:ff87ffd8 error:0 in ld-2.17.so[f76e2000+21000] [12185.396952] traps: ld-linux-x32.so[12075] general protection ip:f76fde9d sp:ffb13ea8 error:0 in ld-2.17.so[f76e7000+21000] [12185.406515] traps: ld-linux-x32.so[12089] general protection ip:f777be9d sp:ff989ed8 error:0 in ld-2.17.so[f7765000+21000] [12185.415389] traps: ld-linux-x32.so[12103] general protection ip:f775fe9d sp:ffd985f8 error:0 in ld-2.17.so[f7749000+21000] [12185.424751] traps: ld-linux-x32.so[12117] general protection ip:f7732e9d sp:ffc50978 error:0 in ld-2.17.so[f771c000+21000] [12185.433680] traps: ld-linux-x32.so[12131] general protection ip:f777ce9d sp:fff51628 error:0 in ld-2.17.so[f7766000+21000] [12185.442345] traps: ld-linux-x32.so[12145] general protection ip:f771ce9d sp:ff993d78 error:0 in ld-2.17.so[f7706000+21000] [12450.608496] do_general_protection: 28 callbacks suppressed [12450.608500] traps: ld-linux-x32.so[15196] general protection ip:f773ae9d sp:fff86e68 error:0 in ld-2.17.so[f7724000+21000] [12450.616771] traps: ld-linux-x32.so[15210] general protection ip:f7786e9d sp:ff87b368 error:0 in ld-2.17.so[f777+21000] [12450.625820] traps: ld-linux-x32.so[15224] general protection ip:f77a0e9d sp:fff6fa68 error:0 in ld-2.17.so[f778a000+21000] [12450.717805] traps: ld-linux-x32.so[15319] general protection
Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))
On 07/06/2013 10:06, luke.leighton wrote: On Fri, Jun 7, 2013 at 8:48 AM, Vladimir Pantelic vlado...@gmail.com wrote: luke.leighton wrote: 3 days remaining on the clock. what catastrophic thing will happen when the time runs out? no catastrophe, vladimir: all that happens is that an opportunity is lost, and the result of that is that the situation remains as it is, with a major soc vendor being divorced from and isolated from the free software community, who will continue to have to shoulder the frustrating and isolated burden of responsibility of reworking over-the-fence kernel patches as best they can with the limited resources that they have. I think the question was: what will be done in 3 days that cannot be undone ? and you didn't answer that. I don't understand why your are still stating that Allwinner will never be able to get code in the mainline after Olof and Maxime told you that they are already working, at least discussing with them. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.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/51b19769.4060...@free-electrons.com
Re: Bug#643805: linux-image-3.0.0-1-686-pae: ipv4/conf/all/* entries do not work in /proc/sys/net/
Any news about this issue. The problems remains identical here: echo 0 /proc/sys/net/ipv4/conf/all/send_redirects Do not set the send_redirects (same problem on client machine with accept_redirects) of existing interfaces to 0 Furthermore I have tried setting /proc/sys/net/ipv4/conf/default/send_redirects=0 in sysctl.conf to prohibit gateway from sending thoose icmp redirects but interfaces defined in /etc/network/interfaces (in my case a bridge) have send_redirect=1 after boot completes. Which leads me to think that procs is executed after networking has been setup... and should not. One more things. On client machine I have the following when try to get the route: ip r g 172.20.0.10 172.20.0.10 via 172.17.2.1 dev wlan0 src 172.17.2.65 cache redirected ipid 0x23f0 I haven't found a way to get rid of that redirected route, except reboot (even by flushing iproute2 cache). How can I get remove such a route? Regards. -- http://www.horoa.net Alexandre Chapellon Ingénierie des systèmes open sources et réseaux. Follow me on twitter: @alxgomz http://www.twitter.com/alxgomz -- 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/4eaa4fa1.7050...@horoa.net
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#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#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
On Aug 09 2011, Jonathan Nieder wrote: Hi Alexandre, Hi Jonathan. Alexandre Lymberopoulos wrote: Getting back to the reported bug, I'll try linux-image-3.0 as soon as it gets into stable. I assume you mean sid. FWIW v3.0 migrated to testing today. It would indeed be interesting to hear if one of the ath5k fixes helped. For sure, I meant sid... I installed 3.0 as soon as it went to sid (a few days ago) and since then my wireless card seems to work properly even after resumes from hibernation and suspend. Thanks for working on this. I should thank you guys for fixing everything so fast. Sincerely, Jonathan Best regards, Alexandre -- === Alexandre Lymberopoulos - lym...@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/20110810011633.gc24...@ime.usp.br
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
On Jun 20 2011, Ben Hutchings wrote: This was a correction to the description - PAE is not supported on most Pentium M and Celeron M processors (although it may work at least partly). If the 'flags' line in /proc/cpuinfo does not include 'pae' then you should use the 486 version. Thanks for the explanation. Following it I noticed that my processor supports pae, albeit it is a Celeron M (cpu family 6, model 14, stepping 8). Getting back to the reported bug, I'll try linux-image-3.0 as soon as it gets into stable. Thanks again. Best regards, Alexandre -- === Alexandre Lymberopoulos - lym...@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/20110620111724.ga17...@ime.usp.br
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
On Jun 15 2011, maximilian attems wrote: linux image 3.0 has several ath5k related enhancements, please report back based on it. It's experimental yet. I think that I can try it when in unstable... (I'm a newbie and I'm afraid I can't revert things it they don't work). Besides that, the Celeron class was removed from supported processors in linux-image-2.6.39-2-686-pae, due to the fact it can't handle PAE and there is no 686 version of newer packages for non-PAE 686 processors (mine unfortunately is a Celeron M). thanks -- maks Thank a lot for your help and sorry for the later answer. Best Regards, Alexandre -- === Alexandre Lymberopoulos - lym...@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/20110620043400.ga12...@ime.usp.br
Bug#628184: linux-image-2.6.39-1-686-pae: ath5k module is unstable after upgrade
Package: linux-2.6 Version: 2.6.39-1 Severity: important Since upgrade from 2.6.32 to 2.6.38 and then to 2.6.39 my wireless network card became very unstable, not always connecting to my router and not always able to scan wireless networks in the nearby. The same message (link is not ready) also appears do my wired card, as you can see in the kernel log below, but after connecting the cable I get a link is ready message for my wired network card. I purged wicd (a network manager) and changed /etc/network/interface (to try to connect automatically) but the bug persists. Count on me for any further information. Thanks in advance, Alexandre -- Package-specific info: ** Version: Linux version 2.6.39-1-686-pae (Debian 2.6.39-1) (m...@debian.org) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Fri May 20 20:40:05 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.39-1-686-pae root=UUID=7391c4b5-342a-4f62-b177-748ee154ce6c ro resume=/dev/sda5 ** Not tainted ** Kernel log: [ 10.572382] hci_cmd_timer: hci0 command tx timeout [ 10.764514] ath5k :06:02.0: enabling device ( - 0002) [ 10.786531] ath5k :06:02.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 10.808800] ath5k :06:02.0: registered as 'phy0' [ 11.547425] ath: EEPROM regdomain: 0x63 [ 11.547429] ath: EEPROM indicates we should expect a direct regpair map [ 11.547434] ath: Country alpha2 being used: 00 [ 11.547437] ath: Regpair used: 0x63 [ 11.552284] ACPI Exception: AE_TIME, Returned by Handler for [EmbeddedControl] (20110316/evregion-476) [ 11.574177] ACPI Error: Method parse/execution failed [\_SB_.WMID.Z000] (Node f503c818), AE_TIME (20110316/psparse-536) [ 11.596286] ACPI Error: Method parse/execution failed [\_SB_.WMID.WMBA] (Node f503cde8), AE_TIME (20110316/psparse-536) [ 11.752723] [drm] Initialized drm 1.1.0 20060810 [ 11.827541] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x370-0x377 [ 11.851677] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3f7 0x4d0-0x4d7 [ 11.876849] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [ 11.910084] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [ 11.932325] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc7fff 0xe-0xf [ 11.953870] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [ 11.978187] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff [ 12.005458] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht' [ 12.005658] ath5k :06:02.0: wlan0: Features changed: 0x4800 - 0x4000 [ 12.037302] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [ 12.060747] ath5k phy0: Atheros AR2413 chip found (MAC: 0x78, PHY: 0x45) [ 12.327476] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 12.349113] i915 :00:02.0: setting latency timer to 64 [ 12.353804] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 12.356734] [drm] Driver supports precise vblank timestamp query. [ 12.552228] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 12.01] [drm] initialized overlay support [ 12.957485] checking generic (c000 30) vs hw (c000 1000) [ 12.957491] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver [ 12.961194] Console: switching to colour dummy device 80x25 [ 12.962313] fbcon: inteldrmfb (fb0) is primary device [ 13.000564] Console: switching to colour frame buffer device 128x48 [ 13.004986] fb0: inteldrmfb frame buffer device [ 13.005029] drm: registered panic notifier [ 13.011286] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 13.011425] HDA Intel :00:1b.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 13.011581] HDA Intel :00:1b.0: irq 44 for MSI/MSI-X [ 13.011618] HDA Intel :00:1b.0: setting latency timer to 64 [ 13.141263] hda_codec: ALC883: SKU not ready 0x41f0 [ 13.141421] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input8 [ 13.148290] input: HDA Intel Headphone as /devices/pci:00/:00:1b.0/sound/card0/input9 [ 14.987293] Adding 522108k swap on /dev/sda5. Priority:-1 extents:1 across:522108k [ 15.478896] EXT3-fs (sda6): using internal journal [ 15.611750] loop: module loaded [ 16.507312] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive! [ 18.517200] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 18.526012] ADDRCONF(NETDEV_UP): wlan0: link is not ready [ 20.599348] wlan0: direct probe to 00:18:e7:d5:39:53 (try 1/3) [ 20.747572] RPC: Registered udp transport module. [ 20.749938] RPC: Registered tcp transport module. [ 20.752285] RPC: Registered tcp NFSv4.1 backchannel
Bug#627869: linux-image-2.6.38-2-686: ath5k module is unstable after upgrade
Package: linux-2.6 Version: 2.6.38-5 Severity: grave Justification: renders package unusable Since upgrade from 2.6.32 to 2.6.38 my wireless network card became very unstable, not always connecting to my router and not always able to scan wireless networks in the nearby. The same message (link is not ready) also appears do my wired card, as you can see in the kernel log below, but I didn't use it since these messages start appearing. Count on me for any further information. Thanks in advance, Alexandre -- Package-specific info: ** Version: Linux version 2.6.38-2-686 (Debian 2.6.38-5) (b...@decadent.org.uk) (gcc version 4.4.6 (Debian 4.4.6-3) ) #1 SMP Sun May 8 14:49:45 UTC 2011 ** Command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-2-686 root=UUID=7391c4b5-342a-4f62-b177-748ee154ce6c ro resume=/dev/sda5 ** Not tainted ** Kernel log: [8.978989] Bluetooth: HCI socket layer initialized [9.066017] yenta_cardbus :06:04.0: CardBus bridge found [1025:0090] [9.084395] yenta_cardbus :06:04.0: Using CSCINT to route CSC interrupts to PCI [9.102653] yenta_cardbus :06:04.0: Routing CardBus interrupts to PCI [9.120634] yenta_cardbus :06:04.0: TI: mfunc 0x90501212, devctl 0x44 [9.213428] input: PC Speaker as /devices/platform/pcspkr/input/input6 [9.356317] leds_ss4200: no LED devices found [9.403599] Synaptics Touchpad, model: 1, fw: 6.2, id: 0x1280b1, caps: 0xa04713/0x204000/0x0 [9.455850] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio4/input/input7 [9.601118] [drm] Initialized drm 1.1.0 20060810 [9.781121] Bluetooth: Generic Bluetooth USB driver ver 0.6 [9.802229] usbcore: registered new interface driver btusb [9.951436] cfg80211: Calling CRDA to update world regulatory domain [ 10.028183] ACPI: Battery Slot [BAT1] (battery present) [ 10.177117] yenta_cardbus :06:04.0: ISA IRQ mask 0x0cf8, PCI irq 16 [ 10.195961] yenta_cardbus :06:04.0: Socket status: 3006 [ 10.214615] pci_bus :06: Raising subordinate bus# of parent bus (#06) from #07 to #0a [ 10.234467] yenta_cardbus :06:04.0: pcmcia: parent PCI bridge window: [io 0x6000-0x6fff] [ 10.253696] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x6000-0x6fff: excluding 0x6000-0x60ff 0x6400-0x64ff [ 10.279991] yenta_cardbus :06:04.0: pcmcia: parent PCI bridge window: [mem 0xd000-0xd00f] [ 10.300233] pcmcia_socket pcmcia_socket0: cs: memory probe 0xd000-0xd00f: excluding 0xd000-0xd001 [ 10.320508] yenta_cardbus :06:04.0: pcmcia: parent PCI bridge window: [mem 0x8000-0x83ff pref] [ 10.341059] pcmcia_socket pcmcia_socket0: cs: memory probe 0x8000-0x83ff: excluding 0x8000-0x83ff [ 10.598127] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [ 10.618946] i915 :00:02.0: setting latency timer to 64 [ 10.623318] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 10.626008] [drm] Driver supports precise vblank timestamp query. [ 10.698884] vgaarb: device changed decodes: PCI::00:02.0,olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 10.702079] [drm] initialized overlay support [ 10.900930] ath5k :06:02.0: enabling device ( - 0002) [ 10.903596] ath5k :06:02.0: PCI INT A - GSI 22 (level, low) - IRQ 22 [ 10.906694] ath5k :06:02.0: registered as 'phy0' [ 11.619580] ath: EEPROM regdomain: 0x63 [ 11.619584] ath: EEPROM indicates we should expect a direct regpair map [ 11.619588] ath: Country alpha2 being used: 00 [ 11.619590] ath: Regpair used: 0x63 [ 11.733833] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: excluding 0x170-0x177 0x1f0-0x1f7 0x370-0x377 [ 11.742685] checking generic (c000 30) vs hw (c000 1000) [ 11.742691] fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver [ 11.745535] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: excluding 0x3f0-0x3f7 0x4d0-0x4d7 [ 11.749091] Console: switching to colour dummy device 80x25 [ 11.749914] fbcon: inteldrmfb (fb0) is primary device [ 11.750917] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [ 11.751633] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [ 11.753112] pcmcia_socket pcmcia_socket0: cs: memory probe 0x0c-0x0f: excluding 0xc-0xc7fff 0xe-0xf [ 11.753179] pcmcia_socket pcmcia_socket0: cs: memory probe 0xa000-0xa0ff: clean. [ 11.753247] pcmcia_socket pcmcia_socket0: cs: memory probe 0x6000-0x60ff: excluding 0x6000-0x60ff [ 11.753315] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [ 11.756124] Console: switching to colour frame buffer device 128x48 [ 11.760879] fb0: inteldrmfb frame buffer device [ 11.760921] drm: registered panic notifier [ 11.761153] [drm] Initialized i915 1.6.0 20080730 for :00:02.0 on minor 0 [ 11.777418] ieee80211 phy0: Selected
Bug#626021: linux-image-2.6.38-2-686: icebp (opcode 0xf1) no longer causing a SIGTRAP, breaks Wine
Austin English austinengl...@gmail.com writes: So I think it's likely a problem in the wine selftest. I just can't find my way in that code. The address of test_stage is supposed to match some address given as argument to the test. But test_stage addr has not been read before that happens, and it's a static var. How could it match anything. Anyway, I'm definetly clueless there :) Alexandre? The address of the variable is used to check if the child process was loaded at the same address as the parent. This will generally be true only for PE binaries. Anyway it's irrelevant to the icebp check. Judging from the crash log the bug seems to be that we get a correct single step exception but %eip in the signal context is pointing to the icebp instruction instead of the following one. -- Alexandre Julliard julli...@winehq.org -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/8739kl9mj8@wine.dyndns.org
Bug#595187: Not in experimental
Hi, I haven't been able to reproduce the same problem with 2.6.36-1~experimental.1 althougth I have other problems in free_buffer_head. But I'll wait for 2.6.37 ro report on those. Alex -- 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/aanlktinw-wqdp2maa=y+ykx=ng8ecyv9adnh914t9...@mail.gmail.com
Bug#604762: more informations
i've made some tests with ubuntu kernel working kernel : linux-image-2.6.32-24-virtual freezing kernel : linux-image-2.6.32-25-virtual don't know if it's related (maybe a patch on 2.6.32-25 ubuntu kernel is also apply to debian kernel ? ) i'll try with others 2.6.32 debian kernels version, to see if i can made one to work. -- 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/1450261067.37023.1290591992632.javamail.r...@mailpro
Bug#604762: more informations again
I had rebuild debian kernel 2.6.32+28 with the patch http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commit;h=787814b206766e5a6f21aa2aac0c6685b46821d3 and now, it's booting fine. can someone push it upstream ? (ubuntu kernel in my 2nd post is unrelated,maybe it's an ubuntu patch problem) -- 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/761468736.37112.1290593212440.javamail.r...@mailpro
Bug#604762: kvm : debian squeeze smp guest not booting on amd magny-cours cpu host
Package: linux-image-amd64 Version: 2.6.32+28 we i try to boot a debian squeeze kvm guest, with more than 1 cpu on a debian squeeze kvm host, with amd magny-cours opteron (6174) after grub menu, it freeze with this message. loading please wait same config boot fine an intel xeon cpu. maybe this problem for ubuntu is related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/556480 http://git.kernel.org/?p=linux/kernel/git/stable/linux-2.6.32.y.git;a=commit;h=787814b206766e5a6f21aa2aac0c6685b46821d3 i can boot with = 2.6.33 guest kernel. -- 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/1572307498.36422.1290583322651.javamail.r...@mailpro
Bug#595187: linux-2.6: lots of OOPses on resume (NULL pointer dereference in file_ra_state_init)
Source: linux-2.6 Version: 2.6.32-21 Severity: normal Hi, Since the upgrade from 2.6.32-20 - 2.6.32-21, my laptop fails to resume properly into Xorg : the cursor only appears when I move it and there is nothing much more I can do than switching to the console, login as root and reboot. In the console, I can see a lot of OOpses that are visible in the attached log file. This did not happend with 2.6.32-20, or at least not before many suspend cycles. Here is the first of the many similar stack traces : -- Sep 1 21:29:47 annalee kernel: [ 1062.410659] BUG: unable to handle kernel NULL pointer dereference at 0020 Sep 1 21:29:47 annalee kernel: [ 1062.410665] IP: [810ba09c] file_ra_state_init+0x4/0x14 Sep 1 21:29:47 annalee kernel: [ 1062.410673] PGD 7c87e067 PUD 7c370067 PMD 0 Sep 1 21:29:47 annalee kernel: [ 1062.410678] Oops: [#1] SMP Sep 1 21:29:47 annalee kernel: [ 1062.410681] last sysfs file: /sys/devices/LNXSYSTM:00/LNXSYBUS:00/ACPI0003:00/power_supply/AC/uevent Sep 1 21:29:47 annalee kernel: [ 1062.410685] CPU 1 Sep 1 21:29:47 annalee kernel: [ 1062.410687] Modules linked in: binfmt_misc acpi_cpufreq firewire_sbp2 firewire_core crc_itu_t loop sha256_generic aes_x86_64 aes_generic cbc dm_crypt arc4 snd_hda_codec_idt ecb iwl3945 snd_hda_intel iwlcore snd_hda_codec snd_hwdep joydev mac80211 snd_pcm snd_seq snd_timer snd_seq_device led_class battery dell_laptop snd cfg80211 soundcore psmouse snd_page_alloc i2c_i801 evdev pcspkr rfkill dcdbas wmi serio_raw ac processor ext3 jbd mbcache dm_mod sd_mod crc_t10dif i915 drm_kms_helper drm ata_generic uhci_hcd i2c_algo_bit tg3 libphy thermal ata_piix button libata ehci_hcd scsi_mod i2c_core video thermal_sys output usbcore nls_base [last unloaded: scsi_wait_scan] Sep 1 21:29:47 annalee kernel: [ 1062.410739] Pid: 2798, comm: date Not tainted 2.6.32-5-amd64 #1 Latitude D630 Sep 1 21:29:47 annalee kernel: [ 1062.410742] RIP: 0010:[810ba09c] [810ba09c] file_ra_state_init+0x4/0x14 Sep 1 21:29:47 annalee kernel: [ 1062.410747] RSP: 0018:88007df39db0 EFLAGS: 00010206 Sep 1 21:29:47 annalee kernel: [ 1062.410749] RAX: RBX: RCX: 88007c89ba80 Sep 1 21:29:47 annalee kernel: [ 1062.410752] RDX: 88007c89ba80 RSI: 88007ef53798 RDI: 88007c89baf0 Sep 1 21:29:47 annalee kernel: [ 1062.410754] RBP: 88007c89ba80 R08: R09: 880037bd9c00 Sep 1 21:29:47 annalee kernel: [ 1062.410757] R10: 88007df39e48 R11: 81151385 R12: Sep 1 21:29:47 annalee kernel: [ 1062.410759] R13: 88007ef53678 R14: 0024 R15: 810eb47c Sep 1 21:29:47 annalee kernel: [ 1062.410762] FS: () GS:88000190() knlGS: Sep 1 21:29:47 annalee kernel: [ 1062.410765] CS: 0010 DS: ES: CR0: 80050033 Sep 1 21:29:47 annalee kernel: [ 1062.410768] CR2: 0020 CR3: 7c70e000 CR4: 06e0 Sep 1 21:29:47 annalee kernel: [ 1062.410770] DR0: DR1: DR2: Sep 1 21:29:47 annalee kernel: [ 1062.410773] DR3: DR6: 0ff0 DR7: 0400 Sep 1 21:29:47 annalee kernel: [ 1062.410776] Process date (pid: 2798, threadinfo 88007df38000, task 88007db662e0) Sep 1 21:29:47 annalee kernel: [ 1062.410778] Stack: Sep 1 21:29:47 annalee kernel: [ 1062.410779] 810eb991 880037bd9c00 880037a1aa00 88007a759600 Sep 1 21:29:47 annalee kernel: [ 1062.410783] 0 88007df39e48 88007df39e48 8001 Sep 1 21:29:47 annalee kernel: [ 1062.410787] 0 0024 ff9c 810f70bb 88007df39e78 Sep 1 21:29:47 annalee kernel: [ 1062.410792] Call Trace: Sep 1 21:29:47 annalee kernel: [ 1062.410797] [810eb991] ? __dentry_open+0x1c4/0x2bf Sep 1 21:29:47 annalee kernel: [ 1062.410802] [810f70bb] ? do_filp_open+0x4e4/0x94b Sep 1 21:29:47 annalee kernel: [ 1062.410806] [810e40dd] ? virt_to_head_page+0x9/0x2a Sep 1 21:29:47 annalee kernel: [ 1062.410810] [811000c5] ? alloc_fd+0x67/0x10c Sep 1 21:29:47 annalee kernel: [ 1062.410813] [810eb6fb] ? do_sys_open+0x55/0xfc Sep 1 21:29:47 annalee kernel: [ 1062.410818] [81010b42] ? system_call_fastpath+0x16/0x1b Sep 1 21:29:47 annalee kernel: [ 1062.410821] Code: 89 d8 5b 5d 41 5c c3 53 89 f3 e8 57 98 f9 ff 85 c0 75 0f 85 db 74 0b 48 c7 05 ed 86 59 00 00 00 00 00 5b c3 90 90 90 48 8b 46 68 48 8b 40 20 48 c7 47 18 ff ff ff ff 89 47 10 c3 65 8b 04 25 98 Sep 1 21:29:47 annalee kernel: [ 1062.410853] RIP [810ba09c] file_ra_state_init+0x4/0x14 Sep 1 21:29:47 annalee kernel: [ 1062.410857] RSP 88007df39db0 Sep 1 21:29:47 annalee kernel: [ 1062.410859] CR2: 0020 Sep 1 21:29:47 annalee kernel: [ 1062.410862] ---[ end trace f71fcf8b8aa10d22 ]--- Sep 1
Bug#583139: linux-2.6: no DHCP offers on r8169
Hi, For the record, after more investigation, this appears not to be related to the kernel at all (sorry) but ot a misbehaving DHCP server that only answers on broadcast. My ISP must have changed its config. $ cat /var/log/daemon.log.1 /var/log/daemon.log 2/dev/null | grep dhclient | cut -d':' -f4- | uniq -c 18225 DHCPREQUEST on eth0 to 82.224.x.y port 67 1 DHCPREQUEST on eth0 to 255.255.255.255 port 67 1 DHCPACK from 82.224.x.y 1 bound to 82.224.z.p -- renewal in 249667 seconds. 15075 DHCPREQUEST on eth0 to 82.224.x.y port 67 # dhcping -v -s 255.255.255.255 Got answer from: 82.224.x.y received from 82.224.x.y, expected from 255.255.255.255 no answer # dhcping -v -s 82.224.x.y no answer Not sure how to fix this (contact my ISP or DHCP client option), but at least this is not kernel related. Alex -- 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/aanlkti=wqnqa6wremra2lcg4fbgfb+qev_etkposa...@mail.gmail.com
Bug#583139: linux-2.6: no DHCP offers on r8169
I cannot reproduce anymore with -22lenny1. I do not understand since I had checked with another computer on the same link to rule out a failure from my ISP. I guess if I cannot reproduce through the WE, this can be closed. Cannot reproduce anymore, playing with DHCP, and -22lenny1. Sorry for the noise. Alex -- 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/aanlktinolatjwlqhs7s2nlggi310yudgrdc6cqjhv...@mail.gmail.com
Bug#583139: linux-2.6: no DHCP offers on r8169
Hi, But just to be sure, I just tested another time, and my first results are not consistent with what I found again. I've been running for about a day with 2.6.26-22 and I could not reproduce. I'll try again to upgrade to -22lenny1 tonight. I cannot reproduce anymore with -22lenny1. I do not understand since I had checked with another computer on the same link to rule out a failure from my ISP. I guess if I cannot reproduce through the WE, this can be closed. Alex -- 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/aanlktikc4vzkcntrsor0emstq4gd80pcwibrf3si2...@mail.gmail.com
Bug#583139: linux-2.6: no DHCP offers on r8169
Package: linux-2.6 Version: 2.6.26-22lenny1 Severity: important Hi, I get no DHCP offers on the r8169 device since the upgrade to 2.6.26-22lenny1. Reverting to 2.6.26-22 does not fix the problem. Reverting to 2.6.26-21lenny4 *does* fix the problem. Please contact me for more info. Alex -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-openvz-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- 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/20100525174300.6271.22266.report...@ripley0
Bug#574657: Get the same issue
hs:~# uname -a Linux hs 2.6.32-3-amd64 #1 SMP Wed Feb 24 18:07:42 UTC 2010 x86_64 GNU/Linux Can you reproduce with the latest sid kernel (install linux-image-2.6.32-5-amd64)? -- 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/aanlktikerlmxmnsicsijcxpl5ecgznypwav3cgz5d...@mail.gmail.com
Bug#574657: same here
notfound 574657 2.6.32-12 thanks I have not been able to reproduce since 2.6.32-12. Alex -- 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/aanlktind3vjbgutssykbmyxbjgp8m99riq-txkhyz...@mail.gmail.com
Bug#578676: linux-image-2.6.32-3-686: KMS fails to load at startup from time to time (macbook 2.1, intel GPU)
Package: linux-2.6 Version: 2.6.32-9 Severity: normal From time to time, when I start my macbook on squeeze, the KMS will just fail to activate, and I get the old big fonts during the boot process (another symptom is the high latency switch from the X server to the console). Usually restarting the computer will re-enable KMS. I *think* the corresponding entries in dmesg might be the following ones: [1.191365] [drm] Initialized drm 1.1.0 20060810 [1.225232] i915 :00:02.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [1.225239] i915 :00:02.0: setting latency timer to 64 [1.225257] [drm:drm_fill_in_dev] *ERROR* Cannot initialize the agpgart module. [1.225318] DRM: Fill_in_dev failed. [1.225371] i915 :00:02.0: PCI INT A disabled [1.225377] i915: probe of :00:02.0 failed with error -22 I guess lspci information will be provided by reportbug If more data is needed to identify correctly the issue, please feel free to ask me. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information not available ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile 945GM/PM/GMS, 943/940GML and 945GT Express Memory Controller Hub [8086:27a0] (rev 03) Subsystem: Intel Corporation Device [8086:7270] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Device [8086:7270] Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 16 Region 0: Memory at 5038 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at 20e0 [size=8] Region 2: Memory at 4000 (32-bit, prefetchable) [size=256M] Region 3: Memory at 5040 (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied 00:02.1 Display controller [0380]: Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller [8086:27a6] (rev 03) Subsystem: Intel Corporation Device [8086:7270] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at 5030 (32-bit, non-prefetchable) [size=512K] Capabilities: access denied 00:07.0 Performance counters [1101]: Intel Corporation Device [8086:27a3] (rev 03) Control: I/O- Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Interrupt: pin A routed to IRQ 11 Region 0: Memory at 50444000 (32-bit, non-prefetchable) [size=4K] Capabilities: access denied 00:1b.0 Audio device [0403]: Intel Corporation N10/ICH 7 Family High Definition Audio Controller [8086:27d8] (rev 02) Subsystem: SigmaTel Device [8384:7680] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 256 bytes Interrupt: pin A routed to IRQ 22 Region 0: Memory at 5044 (64-bit, non-prefetchable) [size=16K] Capabilities: access denied Kernel driver in use: HDA Intel 00:1c.0 PCI bridge [0604]: Intel Corporation N10/ICH 7 Family PCI Express Port 1 [8086:27d0] (rev 02) (prog-if 00 [Normal decode]) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 256 bytes Bus: primary=00, secondary=01, subordinate=01, sec-latency=0 I/O behind bridge: 1000-1fff Memory behind bridge: 5020-502f Prefetchable memory behind bridge: 5050-506f Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- Reset- FastB2B- PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn- Capabilities: access denied
Bug#574657: same here
notfound 574657 2.6.32-8
found 574657 2.6.32-9
found 574657 2.6.32-10
found 574657 2.6.32-11
thanks
In order to investigate, I compiled the vanilla kernel 2.6.32.{8,9,11}
and was not able to reproduce.
I can reproduce in less than 3 suspend/resume cycles using official
Debian kernel images linux-image-2.6.31-{3,4}-amd64 (all versions
since 2.6.32-9).
Therefore, I think this problem lays in the Debian specific changes
introduced in linux-2.6 version 2.6.32-9 .
I'll try to narrow down the issue to a specific patch.
Alex
--
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/k2i9b01ce9b1004080304n2b192ef0ye65cf746a3a7a...@mail.gmail.com
Bug#575056: linux-2.6: libata based drivers migration script does not migrate /etc/crypttab
Package: linux-2.6 Version: 2.6.32-10 Severity: normal Hi, The migration to libata based drivers migration went very well when I upgraded the kernel to 2.6.33-10, but the migration process forgot about /etc/crypttab where my encrypted /home info is. After manually changing it, everything was OK. The crypttab manual page does not say if cryptsetup supports UUID=, but #445189 says so. Thanks, feel free to ask for more info. Alex -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- 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/20100323071059.2842.92894.report...@annalee.sousmonlit.dyndns.org
Bug#556585: iwlagn gone bananas after a couple of hours
Quoting maximilian attems m...@stro.at: On Tue, Nov 17, 2009 at 12:08:46AM +0100, Alexandre Fournier wrote: Package: linux-image-2.6.30-2-686 Version: 2.6.30-8 This happened on a lenovo x300 using the squeeze distro, I suddendly lost the connectivity for the wireless card. I tried to reload iwlagn to no avail. Everything seems to be fine on reboot, though what firmware version are you using and please try out 2.6.31 from unstable? I use the firmware version provided by the debian squeeze package: apt-cache show firmware-iwlwifi | grep Version\|4965 Version: 0.18 Description: Binary firmware for Intel Wireless 3945, 4965 and 5000-series cards This package contains the binary firmware for Intel Wireless 3945, 4965, * Intel Wireless 4965 firmware, version 228.57.1.21 * Intel Wireless 4965 firmware, version 228.61.2.24 About which version really gets loaded: [ 12.983331] iwlagn :03:00.0: firmware: requesting iwlwifi-4965-2.ucode [ 13.016724] iwlagn :03:00.0: loaded firmware version 228.61.2.24 I can try the kernel unstable version. however: - maybe I didn't stress enough that I only experienced this bug once. - should I also upgrade the firmware-iwlwifi package ? Regards, A. Fournier -- Alexandre Fournier And we've been told so many lies We can't believe in paradise Les Thugs - As happpy as -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#556585: iwlagn gone bananas after a couple of hours
[ 9070.537123] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9070.553973] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9070.570801] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9070.584778] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. [ 9070.588477] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9070.608950] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9070.629412] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9070.650710] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9070.667926] iwlagn :03:00.0: Unable to init nic [ 9074.488073] wlan0: no probe response from AP 32:c1:2d:b1:7a:bc - disassociating [ 9074.497103] mac80211-phy0: failed to remove key (0, 32:c1:2d:b1:7a:bc) from hardware (-22) [ 9575.440038] wlan0: deauthenticating by local choice (reason=3) [ 9596.320526] e1000e :00:19.0: irq 27 for MSI/MSI-X [ 9596.376136] e1000e :00:19.0: irq 27 for MSI/MSI-X [ 9596.376720] ADDRCONF(NETDEV_UP): eth0: link is not ready [ 9596.384015] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9596.405711] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9596.426274] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9596.448009] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9596.464632] iwlagn :03:00.0: Unable to init nic [ 9599.140737] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9599.163758] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9599.184359] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9599.206079] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9599.222770] iwlagn :03:00.0: Unable to init nic [ 9635.559566] iwlagn :03:00.0: PCI INT A disabled [ 9640.348124] cfg80211: Using static regulatory domain info [ 9640.348130] cfg80211: Regulatory domain: US [ 9640.348135] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) [ 9640.348142] (2402000 KHz - 2472000 KHz @ 4 KHz), (600 mBi, 2700 mBm) [ 9640.348149] (517 KHz - 519 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 9640.348155] (519 KHz - 521 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 9640.348161] (521 KHz - 523 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 9640.348168] (523 KHz - 533 KHz @ 4 KHz), (600 mBi, 2300 mBm) [ 9640.348174] (5735000 KHz - 5835000 KHz @ 4 KHz), (600 mBi, 3000 mBm) [ 9640.348189] cfg80211: Calling CRDA for country: US [ 9640.457397] iwlagn: Intel(R) Wireless WiFi Link AGN driver for Linux, 1.3.27ks [ 9640.457402] iwlagn: Copyright(c) 2003-2009 Intel Corporation [ 9640.457482] iwlagn :03:00.0: enabling device ( - 0002) [ 9640.457496] iwlagn :03:00.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [ 9640.457514] iwlagn :03:00.0: setting latency timer to 64 [ 9640.457553] iwlagn :03:00.0: Detected Intel Wireless WiFi Link 4965AGN REV=0x [ 9640.478219] iwlagn :03:00.0: MAC is in deep sleep!. CSR_GP_CNTRL = 0x [ 9640.478224] iwlagn :03:00.0: Failed to init APMG [ 9640.478241] iwlagn :03:00.0: PCI INT A disabled [ 9640.478249] iwlagn: probe of :03:00.0 failed with error -5 If you need some additional data, please feel free to ask. Regards, A. Fournier -- Alexandre Fournier And we've been told so many lies We can't believe in paradise Les Thugs - As happpy as -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#513228: linux-2.6: please add intel AGP G41 chipset support
Package: linux-2.6
Severity: wishlist
Tags: patch
Hi,
The patch for intel AGP G41 chipset support is part of upstream 2.6.29.
It applies without modifications to Debian's 2.6.26 (provided the agp: Fix
stolen memory counting on Intel G4X has been applied before) and adds support
for this new AGP chipset. It even makes xserver-xorg-video-intel stable with
the Intel X4500HD.
Here is the patch.
Cheers,
Alex
--
commit a50ccc6c6623ab0e64f2109881e07c176b2d876f
Author: Zhenyu Wang zhenyu.z.w...@intel.com
Date: Mon Nov 17 14:39:00 2008 +0800
agp/intel: add support for G41 chipset
Signed-off-by: Zhenyu Wang zhenyu.z.w...@intel.com
Signed-off-by: Eric Anholt e...@anholt.net
Signed-off-by: Dave Airlie airl...@linux.ie
diff --git a/drivers/char/agp/intel-agp.c b/drivers/char/agp/intel-agp.c
index 9cf6e9b..7d8db5a 100644
--- a/drivers/char/agp/intel-agp.c
+++ b/drivers/char/agp/intel-agp.c
@@ -40,6 +40,8 @@
#define PCI_DEVICE_ID_INTEL_Q45_IG 0x2E12
#define PCI_DEVICE_ID_INTEL_G45_HB 0x2E20
#define PCI_DEVICE_ID_INTEL_G45_IG 0x2E22
+#define PCI_DEVICE_ID_INTEL_G41_HB 0x2E30
+#define PCI_DEVICE_ID_INTEL_G41_IG 0x2E32
/* cover 915 and 945 variants */
#define IS_I915 (agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_E7221_HB || \
@@ -63,7 +65,8 @@
#define IS_G4X (agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_IGD_E_HB || \
agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_Q45_HB || \
agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_G45_HB || \
- agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_GM45_HB)
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_GM45_HB || \
+ agp_bridge-dev-device == PCI_DEVICE_ID_INTEL_G41_HB)
extern int agp_memory_reserved;
@@ -1196,6 +1199,7 @@ static void intel_i965_get_gtt_range(int *gtt_offset, int
*gtt_size)
case PCI_DEVICE_ID_INTEL_IGD_E_HB:
case PCI_DEVICE_ID_INTEL_Q45_HB:
case PCI_DEVICE_ID_INTEL_G45_HB:
+ case PCI_DEVICE_ID_INTEL_G41_HB:
*gtt_offset = *gtt_size = MB(2);
break;
default:
@@ -2163,6 +2167,8 @@ static const struct intel_driver_description {
Q45/Q43, NULL, intel_i965_driver },
{ PCI_DEVICE_ID_INTEL_G45_HB, PCI_DEVICE_ID_INTEL_G45_IG, 0,
G45/G43, NULL, intel_i965_driver },
+ { PCI_DEVICE_ID_INTEL_G41_HB, PCI_DEVICE_ID_INTEL_G41_IG, 0,
+ G41, NULL, intel_i965_driver },
{ 0, 0, 0, NULL, NULL, NULL }
};
@@ -2360,6 +2366,7 @@ static struct pci_device_id agp_intel_pci_table[] = {
ID(PCI_DEVICE_ID_INTEL_IGD_E_HB),
ID(PCI_DEVICE_ID_INTEL_Q45_HB),
ID(PCI_DEVICE_ID_INTEL_G45_HB),
+ ID(PCI_DEVICE_ID_INTEL_G41_HB),
{ }
};
-- System Information:
Debian Release: 5.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-openvz-amd64 (SMP w/2 CPU cores)
Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#494308: Living without e100 firmware
I thought it might be useful to point out that the removal of the non-Free firmware present in the e100 driver doesn't have any effect on the (old) notebook I have that uses the e100 driver. Initially, when I first converted it to linux-libre, that didn't include that driver at all, enabling the eepro100 driver was enough to get it to work. Later on, linux-libre started replacing the blob with /*(DEBLOBBED)*/, making for an empty array of firmware code, and this cleaned-up e100 module worked just fine. So don't assume that the removal of the firmware will have a negative impact on all e100-using hardware. If my experience counts, it will have zero impact. That said, I assume the firmware must be there for some reason, even if it's just to update in-flash firmware or so. Perhaps I just don't have hardware that depends on it. Who knows? -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ Free Software Evangelist [EMAIL PROTECTED], gnu.org} FSFLA Board Member ¡Sé Libre! = http://www.fsfla.org/ Red Hat Compiler Engineer [EMAIL PROTECTED], gcc.gnu.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494009: No loss without microcode
I thought I'd point out that the cleaned-up drivers available in linux-libre work just fine on my home server that has an ATI video card. I don't know whether its absence causes any functionality degradation (my video card requirements are pretty low), but it certainly doesn't affect stability. It might be the case that my particular video card doesn't require the microcode at all, but it shouldn't be assumed that removing any of this firmware will cause any loss to every user of this driver. -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ Free Software Evangelist [EMAIL PROTECTED], gnu.org} FSFLA Board Member ¡Sé Libre! = http://www.fsfla.org/ Red Hat Compiler Engineer [EMAIL PROTECTED], gcc.gnu.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500472: maybe patch
tag 500472 patch thanks My box has been running with this patch applied for a while now, and I cannot reproduce, so I'd say this fixes the issue for me. For the record, those fixes went into 2.6.27 : http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=4dd7972d1204c3851a4092cecd2207e05eb29b09 and http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=2a5b82751f73a0bf6f604ce56d34adba6da1b246 Cheers, Alex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500472: maybe patch
Subject: Bug#500472: linux-image-2.6.26-1-openvz-amd64: NULL pointer dereference in tcp_v4_send_ack Thanks! It is a mainstream bug. Fixed patch was sent to [EMAIL PROTECTED] The patch is there : http://www.spinics.net/lists/netdev/msg76471.html But it does not apply to 2.6.26 so I tried to backport it. Here is what I could come up with (clearly not understanding what I was doing, and taking into account the fact that a follow-up says ipv6 codepath is similar) : diff --git a/net/ipv4/tcp_ipv4.c b/net/ipv4/tcp_ipv4.c index ffe869a..fffc708 100644 --- a/net/ipv4/tcp_ipv4.c +++ b/net/ipv4/tcp_ipv4.c @@ -687,7 +687,7 @@ static void tcp_v4_send_ack(struct tcp_timewait_sock *twsk, if (twsk) arg.bound_dev_if = twsk-tw_sk.tw_bound_dev_if; - ip_send_reply(dev_net(skb-dev)-ipv4.tcp_sock, skb, + ip_send_reply(dev_net(skb-dst-dev)-ipv4.tcp_sock, skb, arg, arg.iov[0].iov_len); TCP_INC_STATS_BH(TCP_MIB_OUTSEGS); diff --git a/net/ipv6/tcp_ipv6.c b/net/ipv6/tcp_ipv6.c index 40ea9c3..6d8e350 100644 --- a/net/ipv6/tcp_ipv6.c +++ b/net/ipv6/tcp_ipv6.c @@ -1094,7 +1094,7 @@ static void tcp_v6_send_ack(struct tcp_timewait_sock *tw, struct tcphdr *th = tcp_hdr(skb), *t1; struct sk_buff *buff; struct flowi fl; - struct net *net = dev_net(skb-dev); + struct net *net = dev_net(skb-dst-dev); struct sock *ctl_sk = net-ipv6.tcp_sk; unsigned int tot_len = sizeof(struct tcphdr); __be32 *topt; -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#500472: linux-image-2.6.26-1-openvz-amd64: NULL pointer dereference in tcp_v4_send_ack
Package: linux-image-2.6.26-1-openvz-amd64 Version: 2.6.26-5 Severity: important Hi, The machine freezes sometimes, repeatedly and it seems this happens under some network load in a VE. vcfgvalidate is all ok. The fail counts of user beancounters are all 0. Here is the stacktrace. Feel free to ask for more info. Alex -- [ 960.532790] BUG: unable to handle kernel NULL pointer dereference at 0450 [ 960.532790] IP: [803e9712] tcp_v4_send_ack+0x1f6/0x23e [ 960.532790] PGD 1a5ec067 PUD 1a801067 PMD 0 [ 960.532790] Oops: [1] SMP [ 960.532790] CPU: 0 [ 960.532790] Modules linked in: netconsole configfs i915 drm vzethdev vznetdev simfs vzdquota vzmon vzdev xt_TCPMSS video output ac battery ip6table_filter ip6_tables iptable_raw xt_comment xt_policy ipt_ULOG ipt_TTL ipt_ttl ipt_REJECT ipt_REDIRECT ipt_recent ipt_NETMAP ipt_MASQUERADE ipt_LOG ipt_ECN ipt_ecn ipt_CLUSTERIP ipt_ah ipt_addrtype nf_nat_tftp nf_nat_snmp_basic nf_nat_sip nf_nat_pptp nf_nat_proto_gre nf_nat_irc nf_nat_h323 nf_nat_ftp nf_nat_amanda ts_kmp nf_conntrack_amanda nf_conntrack_tftp nf_conntrack_sip nf_conntrack_proto_sctp nf_conntrack_pptp nf_conntrack_proto_gre nf_conntrack_netlink nf_conntrack_netbios_ns nf_conntrack_irc nf_conntrack_h323 nf_conntrack_ftp xt_tcpmss xt_pkttype xt_physdev xt_owner xt_NFQUEUE xt_NFLOG xt_multiport xt_MARK xt_mark xt_mac xt_limit xt_length xt_iprange xt_helper xt_hashlimit xt_DSCP xt_dscp xt_dccp xt_conntrack xt_CONNMARK xt_connmark xt_CLASSIFY xt_tcpudp xt_state iptable_nat nf_nat nf_conntrack_ipv4 nf_conntrack iptable_mangle nfnetlink iptable_filter ip_tables x_tables ipv6 eeprom cpufreq_ondemand acpi_cpufreq freq_table loop parport_pc i2c_i801 rng_core snd_hda_intel i2c_core parport snd_pcm pcspkr iTCO_wdt snd_timer snd soundcore button snd_page_alloc intel_agp evdev ext3 jbd mbcache dm_mirror dm_log dm_snapshot dm_mod sd_mod ide_cd_mod cdrom ide_disk ata_generic ata_piix 8139too libata scsi_mod dock 8139cp mii r8169 ide_pci_generic piix ide_core thermal processor fan thermal_sys [ 960.532790] Pid: 0, comm: swapper Not tainted 2.6.26-1-openvz-amd64 #1 036test001 [ 960.532790] RIP: 0010:[803e9712] [803e9712] tcp_v4_send_ack+0x1f6/0x23e [ 960.532790] RSP: 0018:805d9bf0 EFLAGS: 00010246 [ 960.532790] RAX: RBX: 81001a88a980 RCX: 0020 [ 960.532790] RDX: 805d9c40 RSI: 81001a88a980 RDI: [ 960.532790] RBP: 00027410 R08: 16a0 R09: 00027410 [ 960.532790] R10: 31ff5ed3 R11: 221928fa R12: [ 960.532790] R13: R14: 81001a88c034 R15: 81001a88a980 [ 960.532790] FS: () GS:80533000() knlGS: [ 960.532790] CS: 0010 DS: 0018 ES: 0018 CR0: 8005003b [ 960.532790] CR2: 0450 CR3: 1a5e8000 CR4: 06e0 [ 960.532790] DR0: DR1: DR2: [ 960.532790] DR3: DR6: 0ff0 DR7: 0400 [ 960.532790] Process swapper (pid: 0, veid=0, threadinfo 8056a000, task 804ee480) [ 960.532790] Stack: 5000afff 80423437 31ff5ed30ce25000 a0161080221928fa [ 960.532790] 0a080101 107402008d740200 80423437 [ 960.532790] 805d9db0 a02987ec 805d9c00 0020 [ 960.532790] Call Trace: [ 960.532790] IRQ [80423437] ? _read_lock_bh+0x9/0x19 [ 960.532790] [80423437] ? _read_lock_bh+0x9/0x19 [ 960.532790] [a02987ec] ? :ip_tables:ipt_do_table+0x515/0x581 [ 960.532790] [803ece53] ? tcp_check_req+0x14a/0x3d8 [ 960.532790] [803ea825] ? tcp_v4_do_rcv+0x387/0x4df [ 960.532790] [803ca150] ? nf_iterate+0x41/0x7d [ 960.532790] [803ecc12] ? tcp_v4_rcv+0x6f6/0x748 [ 960.532790] [803d041d] ? ip_local_deliver_finish+0x171/0x25f [ 960.532790] [803d0289] ? ip_rcv_finish+0x3a1/0x3c4 [ 960.532790] [803d087c] ? ip_rcv+0x26e/0x2c3 [ 960.532790] [803af5c7] ? netif_receive_skb+0x37b/0x44f [ 960.532790] [803b2043] ? process_backlog+0x86/0xef [ 960.532790] [803b1a6f] ? net_rx_action+0xab/0x1da [ 960.532790] [80239ddf] ? __do_softirq+0x96/0x15c [ 960.532790] [8020d3bc] ? call_softirq+0x1c/0x28 [ 960.532790] [8020f510] ? do_softirq+0x3c/0x81 [ 960.532790] [80239d05] ? irq_exit+0x81/0xc5 [ 960.532790] [8020f770] ? do_IRQ+0xb9/0xd9 [ 960.532790] [80212ca7] ? mwait_idle+0x0/0x4d [ 960.532790] [80212ca7] ? mwait_idle+0x0/0x4d [ 960.532790] [8020c55d] ? ret_from_intr+0x0/0x19 [ 960.532790] EOI [8021a9b3] ? lapic_next_event+0x0/0x13 [ 960.532790] [80212ce8] ? mwait_idle+0x41/0x4d [ 960.532790] [8020ad2b] ? cpu_idle+0x89/0xb3 [ 960.532790] [
Bug#494119: permission to copy, distribute, modify?!?
It says it's derived from AF05BDA.sys. Are you sure you, Debian or anyone has permission to copy and distribute it? And to modify it? That someone distributed it, perhaps even under the GPL, doesn't grant you permission to redistribute it, if the person who did so wans't the copyright holder. That it's just a bunch of bits written to random registers doesn't make it Free Software. In the absence of actual source code, and information to enable someone to understand what's going on so as to be able to adapt that piece of software so that it does what one wants, freedom #1 is missing. -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ Free Software Evangelist [EMAIL PROTECTED], gnu.org} FSFLA Board Member ¡Sé Libre! = http://www.fsfla.org/ Red Hat Compiler Engineer [EMAIL PROTECTED], gcc.gnu.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494104: [linux-image-2.6.26-1-686] The module has been renamed
Package: linux-image-2.6.26-1-686 Version: 2.6.26-1 --- Please enter the report below this line. --- Hi Jérémy, I've noticed it as well, It looks like the module is now named: snd_pcsp updating your blacklist should solve the issue: sudo modinfo snd_pcsp filename: /lib/modules/2.6.26-1-686/kernel/sound/drivers/pcsp/snd-pcsp.ko alias: platform:pcspkr license:GPL description:PC-Speaker driver author: Stas Sergeev [EMAIL PROTECTED] depends:snd-pcm,snd vermagic: 2.6.26-1-686 SMP mod_unload modversions 686 parm: nforce_wa:Apply NForce chipset workaround (expect bad sound) (bool) parm: index:Index value for pcsp soundcard. (int) parm: id:ID string for pcsp soundcard. (charp) parm: enable:Enable PC-Speaker sound. (bool) --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-1-686 Debian Release: lenny/sid 650 testing www.debian-multimedia.org 650 testing security.debian.org 650 testing ftp.cz.debian.org 600 unstable ftp.cz.debian.org --- Package information. --- Depends (Version) | Installed =-+-= module-init-tools | 3.4-1 initramfs-tools (= 0.55) | 0.92e OR yaird (= 0.0.13) | OR linux-initramfs-tool | -8---8---8---8---8---8---8---8---8-- Please attach the file: /tmp/reportbug-ng-linux-image-2.6.26-1-686-AztCSj.txt to the mail. I'd do it myself if the output wasn't too long to handle. Thank you! -8---8---8---8---8---8---8---8---8-- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#490701: linux-image-2.6.25-2-686: same problem here on HP-COMPAQ NX7300 notebook
Package: linux-image-2.6.25-2-686 Version: 2.6.25-6 Followup-For: Bug #490701 Regression - The status of the the battery is not detected anymore by 2.6.25 Here's what used to be detected by 2.6.24: [EMAIL PROTECTED]:~$ cat -s /proc/acpi/ac_adapter/C1BC/state /proc/acpi/ba ttery/C1BE/info /proc/acpi/battery/C1BE/state state: on-line present: yes design capacity: 3686 mAh last full capacity: 3686 mAh battery technology: rechargeable design voltage: 10800 mV design capacity warning: 185 mAh design capacity low: 37 mAh capacity granularity 1: 100 mAh capacity granularity 2: 100 mAh model number:Primary serial number: 20274 2007/05/04 battery type:LIon OEM info:Hewlett-Packard present: yes capacity state: ok charging state: charged present rate:0 mA remaining capacity: 3656 mAh present voltage: 12479 mV -- Package-specific info: -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages linux-image-2.6.25-2-686 depends on: ii debconf [debconf-2.0] 1.5.22 Debian configuration management sy ii initramfs-tools [linux-initra 0.92e tools for generating an initramfs ii module-init-tools 3.4-1 tools for managing Linux kernel mo Versions of packages linux-image-2.6.25-2-686 recommends: ii libc6-i6862.7-10 GNU C Library: Shared libraries [i -- debconf information excluded -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484365: suggestion: switch to linux-libre in main
Package: linux-2.6 Severity: normal In case you're not aware, the linux-libre project grew out of gNewSense's efforts to publish 100% Free Software extracts from the kernel distributed by kernel.org, later on picked up by BLAG and, more recently, by FSF Latin America. You might want to use it, instead of kernel.org's kernel, to get closer to compliance with your policy of shipping only Free Software in main. Whether you move the non-Free kernel you currently ship to non-free, or simply remove it, is something you should discuss and decide on your own, but I thought I'd remind you of both possibilities. linux-libre is currently available at http://www.fsfla.org/~lxoliva/fsfla/linux-libre/ There's a README in there. We're considering creating a freed-ebian repository with linux-libre-based kernels for Debian GNU/Linux in there, but we hope that, knowing how seriously you take your social contract and the freedom of your users, I thought you might want to preempt that move. In case you'd like to make such a move using an older version of Linux than those we've already deblobbed, I'd be happy to assist. Just let us know at [EMAIL PROTECTED] Hope this helps, and that Debian one more time sets an example of promoting the Free Software philosophy and caring about users' freedom. Best regards, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484365: suggestion: switch to linux-libre in main
On Jun 3, 2008, Thiemo Seufer [EMAIL PROTECTED] wrote: What are the specific instances of non-free software you found in Debian's kernel? I ran deblob-check on http://ftp.br.debian.org/debian/pool/main/l/linux-2.6/linux-2.6_2.6.25.orig.tar.gz that I found referenced as the source tarball for some linux-2.6 Debian package on some debian.org web page. Then I ran deblob-check with -C, and it printed a few megabytes. Then I deleted both the tarball and the output. I didn't find documentation about what was actually removed. You can find deblob-check as well as the much smaller deblob scripts for each upstream release at http://fsfla.org/svn/fsfla/software/linux-libre/scripts/ -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ Free Software Evangelist [EMAIL PROTECTED], gnu.org} FSFLA Board Member ¡Sé Libre! = http://www.fsfla.org/ Red Hat Compiler Engineer [EMAIL PROTECTED], gcc.gnu.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484365: closed by maximilian attems [EMAIL PROTECTED] (Re: suggestion: switch to linux-libre in main)
On Jun 3, 2008, [EMAIL PROTECTED] (Debian Bug Tracking System) wrote: first of all such suggestion are better discussed on mailing list see http://wiki.debian.org/DebianKernel I'm not really interested in taking part in a debate. I was merely offering a suggestion in the form of a bug report, as suggested by a friend of mine who's involved in Debian's development. I'll let him know the procedure he suggested was inappropriate and suggest him to follow that route. Thanks, and sorry if this caused any trouble. why did none of your effort got productive AFAICT we have produced a working 100% Free kernel, something that Debian has wished for for several years. Our goals are different from those of kernel upstream or Debian, that appear to feel a need to help hardware vendors keep their customers helpless and dependent. Catering to this kind of issue is not part of the charter of this project. and turned into upstream patches? upstream wouldn't take patches that remove the non-Free Software, and we already have the kernel we need. It wouldn't make sense for us to work more to advance goals that are actually opposite to ours. nor do you seem to work on relicensing firmware. That's also not part of the project charter. The goal of the project is to ensure there are well-maintained 100% Free Linux tarballs for anyone who wishes to take freedom seriously. Work on getting firmware relicensed as Free Software is certainly good work to do, but it's not part of this project. why does it not incorporate the upstream posted request_firmware() patches from David Woodhouse? or did i oversee them!?! Because it doens't incorporate any patches whatsoever. It tracks upstream. If David's patches are merged, our scripts will be adjusted to remove the non-Free bits from wherever they land, if they remain. If they aren't, why bother?, they don't make any difference for someone who does not want to install non-Free Software on their computers anyway, or for distros that don't want to be part of the distribution of any non-Free Software to their users. These are the use cases linux-libre is designed to serve. closing as you can only be kidding to consider yourself as appropriate linux-2.6 upstream source. I'm not kidding, but it's not really upstream. You can regard it as a filter midstream that keeps downstream from polution thrown in the river by upstream. We don't mess with the precious water, we just remove the pollutants. Now, if you prefer to keep on deviating from your own policies and counting on exceptions to ensure main can keep on containing non-Free Software, that's certainly your decision. If you'd rather duplicate this work yourselves, it might make sense to join forces, for I take it you've been trying to fix this problem for a very long time. I offered help because I thought Debian might be interested, considering its policies and all. Of course, you don't have to trust us right away. You can keep an eye for a while and see how quickly our releases come out after an upstream release, and how easily patches for upstream still apply. I've been doing that for freed-ora for a while, it's really a no-brainer. And then, should we fail you, you might as well just go back to your beloved non-free upstream :-) Your call... Best regards, and keep up the good work, -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ Free Software Evangelist [EMAIL PROTECTED], gnu.org} FSFLA Board Member ¡Sé Libre! = http://www.fsfla.org/ Red Hat Compiler Engineer [EMAIL PROTECTED], gcc.gnu.org} -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480513: PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
Package: linux-image-2.6.24-1-686 Version: 2.6.24-6 Severity: important Look like a bug of the Kernel! When i boot i've got this message : PCI: BIOS Bug: MCFG area at e000 is not E820-reserved That the result of dmesg | grep BIOS : BIOS-provided physical RAM map: BIOS-e820: - 0009a400 (usable) BIOS-e820: 0009a400 - 000a (reserved) BIOS-e820: 000e - 0010 (reserved) BIOS-e820: 0010 - 3f79 (usable) BIOS-e820: 3f79 - 3f79e000 (ACPI data) BIOS-e820: 3f79e000 - 3f7e (ACPI NVS) BIOS-e820: 3f7e - 3f7ee000 (reserved) BIOS-e820: 3f7f - 3f80 (reserved) BIOS-e820: fee0 - fee01000 (reserved) BIOS-e820: ffb0 - 0001 (reserved) PCI: BIOS Bug: MCFG area at e000 is not E820-reserved PCI: PCI BIOS revision 3.00 entry at 0xf0031, last bus=2 PnPBIOS: Disabled by ACPI PNP hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... The kernel boot normaly after that but it takes more time to boot. This bug seems know with some other distro but not in debian. It affects all debian kernel lower version. The laptop model is MSI VR420 with a Celeron 540. The reportbug log : -- Package-specific info: ** Version: Linux version 2.6.24-1-686 (Debian 2.6.24-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080308 (prerelease) (Debian 4.1.2-21)) #1 SMP Sat Apr 19 00:37:55 UTC 2008 ** Command line: root=/dev/sda3 ro quiet ** Not tainted ** Kernel log: usbcore: registered new interface driver usbhid drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver iTCO_wdt: Intel TCO WatchDog Timer Driver v1.02 (26-Jul-2007) iTCO_wdt: Found a ICH8M TCO device (Version=2, TCOBASE=0x0860) iTCO_wdt: initialized. heartbeat=30 sec (nowayout=0) ricoh-mmc: Ricoh MMC Controller disabling driver ricoh-mmc: Copyright(c) Philip Langdale ricoh-mmc: Ricoh MMC controller found at :01:04.3 [1180:0843] (rev 11) ricoh-mmc: Controller is now disabled. Real Time Clock Driver v1.12ac phy0: Selected rate control algorithm 'simple' ACPI: PCI Interrupt :00:1f.3[C] - GSI 17 (level, low) - IRQ 21 input: PC Speaker as /class/input/input7 Yenta: CardBus bridge found at :01:04.0 [1462:3783] sdhci: Secure Digital Host Controller Interface driver sdhci: Copyright(c) Pierre Ossman Yenta: ISA IRQ mask 0x0cb8, PCI irq 16 Socket status: 3006 Yenta: Raising subordinate bus# of parent bus (#01) from #02 to #05 pcmcia: parent PCI bridge I/O window: 0xc000 - 0xcfff cs: IO port probe 0xc000-0xcfff: clean. pcmcia: parent PCI bridge Memory window: 0xfde0 - 0xfe6f pcmcia: parent PCI bridge Memory window: 0xbdf0 - 0xbfef sdhci: SDHCI controller found at :01:04.2 [1180:0822] (rev 21) ACPI: PCI Interrupt :01:04.2[C] - GSI 18 (level, low) - IRQ 20 sdhci:slot0: Will use DMA mode even though HW doesn't fully claim to support it. mmc0: SDHCI at 0xfe6ff400 irq 20 DMA ACPI: PCI Interrupt :00:1b.0[A] - GSI 21 (level, low) - IRQ 18 PCI: Setting latency timer of device :00:1b.0 to 64 usbcore: registered new interface driver rt73usb hda_codec: Unknown model for ALC883, trying auto-probe from BIOS... Synaptics Touchpad, model: 1, fw: 6.2, id: 0xa5a0b1, caps: 0xa04713/0x0 input: SynPS/2 Synaptics TouchPad as /class/input/input8 cs: IO port probe 0x100-0x3af: clean. cs: IO port probe 0x3e0-0x4ff: clean. cs: IO port probe 0x820-0x8ff: clean. cs: IO port probe 0xc00-0xcf7: clean. cs: IO port probe 0xa00-0xaff: clean. si3054: cannot initialize. EXT MID = Adding 2224960k swap on /dev/sda7. Priority:-1 extents:1 across:2224960k EXT3 FS on sda3, internal journal loop: module loaded kjournald starting. Commit interval 5 seconds EXT3 FS on sda9, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on sda8, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on sda5, internal journal EXT3-fs: mounted filesystem with ordered data mode. kjournald starting. Commit interval 5 seconds EXT3 FS on sda6, internal journal EXT3-fs: mounted filesystem with ordered data mode. e1000: eth0: e1000_watchdog: NIC Link is Up 100 Mbps Full Duplex, Flow Control: RX e1000: eth0: e1000_watchdog: 10/100 speed: disabling TSO atkbd.c: Unknown key pressed (translated set 2, code 0xf7 on isa0060/serio0). atkbd.c: Use 'setkeycodes e077 keycode' to make it known. atkbd.c: Unknown key released (translated set 2, code 0xf7 on isa0060/serio0). atkbd.c: Use 'setkeycodes e077 keycode' to make it known. atkbd.c: Unknown key pressed (translated set 2, code 0xf8 on isa0060/serio0). atkbd.c: Use 'setkeycodes e078 keycode' to make it known. atkbd.c: Unknown key released (translated set 2, code 0xf8 on isa0060/serio0). atkbd.c: Use 'setkeycodes e078 keycode' to make it known. atkbd.c: Unknown key pressed
Bug#414742: Possible fix
Hi,
This is fixed for me in v2.6.19
http://bugs.freedesktop.org/show_bug.cgi?id=5085 points to
http://lkml.org/lkml/2006/10/18/68 which is commit
769751f1b920fbd9034a9764443795ce243b547d included in upstream
2.6.19-rc3
It fixes the problem for me. Can you confirm this?
commit 769751f1b920fbd9034a9764443795ce243b547d
Author: bibo,mao [EMAIL PROTECTED]
Date: Sat Oct 21 18:37:02 2006 +0200
[PATCH] x86-64: x86_64 add NX mask for PTE entry
If function change_page_attr_addr calls revert_page to revert
to original pte value, mk_pte_phys does not mask NX bit. If NX bit
is set on no NX hardware supported x86_64 machine, there is will
be RSVD type page fault and system will crash. This patch adds NX
mask bit for PTE entry.
Signed-off-by: bibo,mao [EMAIL PROTECTED]
Signed-off-by: Andi Kleen [EMAIL PROTECTED]
diff --git a/include/asm-x86_64/pgtable.h b/include/asm-x86_64/pgtable.h
index a31ab4e..1c35616 100644
--- a/include/asm-x86_64/pgtable.h
+++ b/include/asm-x86_64/pgtable.h
@@ -368,6 +368,7 @@ static inline pte_t mk_pte_phys(unsigned long physpage, pgpr
{
pte_t pte;
pte_val(pte) = physpage | pgprot_val(pgprot);
+ pte_val(pte) = __supported_pte_mask;
return pte;
}
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one
Package: linux-image-2.6.22-3-686 Version: 2.6.22-5 Severity: important Debian choose to ship the alternative firewire stack on recent kernels. Firewire maintainers are not recommending this (see http://wiki.linux1394.org/JujuMigration) yet, since this new firewire stack is incomplete. For instance, I can't do ethernet over firewire with 2.6.22, I have to go back to 2.6.18, which gives me other kind of trouble. -- Package-specific info: ** Version: Linux version 2.6.22-3-686 (Debian 2.6.22-5) ([EMAIL PROTECTED]) (gcc version 4.1.3 20071019 (prerelease) (Debian 4.1.2-17)) #1 SMP Mon Oct 22 22:11:56 UTC 2007
Bug#449272: Alternative (buggy, incomplete) firewire stack shipped instead of the stable one
2007/11/4, maximilian attems [EMAIL PROTECTED]: On Sun, Nov 04, 2007 at 02:32:46PM -0200, Alexandre Pereira Nunes wrote: Debian choose to ship the alternative firewire stack on recent kernels. Firewire maintainers are not recommending this (see http://wiki.linux1394.org/JujuMigration) yet, since this new firewire stack is incomplete. For instance, I can't do ethernet over firewire with 2.6.22, I have to go back to 2.6.18, which gives me other kind of trouble. the switch has been made some time ago. you are the *first* to holler due to ethernet over firewire! please report bug upstream on bugzilla.kernel.org and let us know your bug nr, see bottom of page http://wiki.debian.org/DebianKernelReportingBugs regards -- maks What are you talking about? The support to the stable driver wasn't dropped from the kernel (just enable CONFIG_IEEE1394), the recommended policy upstream (from the maintainer's site, see the URL from my previous post) is to enable it, the maintainer's are well aware that the experimental stack only implement a limited subset of firewire functionality, so why should I file a bug there? Note that an upstream 2.6.22 make defconfig does the right thing of selecting the stable drivers and not the experimental one, having it the other way around was a debian decision. I'm not only talking about ip over firewire, there's at least another bug filed against firewire on debian's 2.6.22 (something about an external storage device). The experimental driver is not supposed to work yet (again, see the URL). This newer stack is not expected to get stable before 2.6.24, and in order to prevent further firewire reports on the meanwhile, CONFIG_IEEE1394 should be enabled (as well as the options it brings on the menu). The experimental driver should be disabled for now. The forementioned site points out that not even the userspace library is ready, so many firewire camera programs and such won't operate on the newer stack yet.
Bug#402743: Cannot reproduce in latest svn
I installed svn snapshot 8066 from : http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/linux-image-2.6.18-4-vserver-amd64_2.6.18-9~snapshot.8066_amd64.deb and I cannot reproduce this bug. Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402707: Seems fixed in latest svn
FYI, I installed svn snapshot 8066 from : http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/linux-image-2.6.18-4-vserver-amd64_2.6.18-9~snapshot.8066_amd64.deb and I cannot reproduce this bug. Thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#402743: Upstream
Hi, I asked upstream about this and they say it is fixed in Vserver 2.0.2.2-rc9. I tried the latest version of vserver and it is indeed fixed. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396375: Going Upstream
The bug fix is about to get to upstream: http://marc.theaimsgroup.com/?l=linux-usb-develm=116240085420206w=2 - Alexandre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396375: linux-image-2.6.18-1-k7: 2.6.18 breaks usb-storage for UCR-61S2 device
Package: linux-image-2.6.18-1-k7 Version: 2.6.18-3 Severity: important Tags: patch Linux 2.6.18 introduces a conservative change that restricts the UCR-61S2 initialization fix to only a specific version of the firmware, but older versions needs that as well. The supplied patch reverses that behaviour. Upstream was notified, but in the meanwhile it would be interesting to provide this fix on debian. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-k7 Locale: LANG=pt_BR, LC_CTYPE=pt_BR (charmap=ISO-8859-1) Versions of packages linux-image-2.6.18-1-k7 depends on: ii initramfs-tools [linux-initra 0.84 tools for generating an initramfs ii module-init-tools 3.2.2-3tools for managing Linux kernel mo ii yaird [linux-initramfs-tool] 0.0.12-18 Yet Another mkInitRD Versions of packages linux-image-2.6.18-1-k7 recommends: ii libc6-i686 2.3.6.ds1-7 GNU C Library: Shared libraries [i -- debconf-show failed --- linux-source-2.6.18/drivers/usb/storage/unusual_devs.h~ 2006-10-31 11:27:17.0 -0300 +++ linux-source-2.6.18/drivers/usb/storage/unusual_devs.h 2006-10-31 11:27:17.0 -0300 @@ -1265,7 +1265,7 @@ UNUSUAL_DEV( 0x0fce, 0xe031, 0x, 0x * Tested on hardware version 1.10. * Entry is needed only for the initializer function override. */ -UNUSUAL_DEV( 0x1019, 0x0c55, 0x0110, 0x0110, +UNUSUAL_DEV( 0x1019, 0x0c55, 0x, 0x, Desknote, UCR-61S2B, US_SC_DEVICE, US_PR_DEVICE, usb_stor_ucr61s2b_init,
Bug#396375: linux-image-2.6.18-1-k7: 2.6.18 breaks usb-storage for UCR-61S2 device
dann frazier escreveu: On Tue, Oct 31, 2006 at 02:09:28PM -0300, Alexandre Pereira Nunes wrote: Thanks Alexandre, Do you have a poitner to where upstream was notified? A description of the problem has been posted on the linux-usb-devel@lists.sourceforge.net mailing list, and to Phil Dibowitz and Alan Stern, which are supposed to be the maintainers of the usb-storage unusual device list. Do you have a direct link to the archives? I couldn't find anything when searching for your name or UCR-61S2. The reason I ask is that we need to have high confidence this is going upstream before including it: http://wiki.debian.org/DebianKernelPatchAcceptanceGuidelines It seems like sourceforge archive is lagging behind. The post can be read here: http://marc.theaimsgroup.com/?l=linux-usb-develm=116230631107331w=2 But I do believe we have to wait for maintainer's position before proceding. If I have any news about that I'll update this bug report Thanks! Alexandre -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#323757: Appears to be duplicate of #323702
On Sun, Aug 21, 2005 at 11:39:59PM -0400, Barry Hawkins wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After searching through the debian-kernel list archive, this report appears to be a duplicate of #323702. I won't merge them as the debian-kernel team may prefer to do that themselves based on their judgement. For those who need a fix for this issue soon, follow the workaround mentioned in #323702, purging and reinstalling your linux-headers packages. Indeed, it does seem to be the same bug, I am merging them. Also, the bug seems to be as fixed as it is ever going to be. Its a packaging glitch, is been fixed, and there is a work around for people who had the broken package. Unstable is... unstable. Thank you very much for taking the time to investigate this and point me to the solution. I feel a bti ashamed not having done it myself. So, once again, thanks a lot. -- Alexandre Fayolle signature.asc Description: Digital signature
Bug#324368: kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h)
On Mon, 22 Aug 2005 11:50:20 +0900 Horms [EMAIL PROTECTED] wrote: Its an issue with the kernel. 2.6.10 does not compile cleanly with gcc-4.0. 2.6.10 is being debricated and is no longer supported, please consider using 2.6.12 or later. If you really need to compile 2.6.10 for some reason, please use gcc-3.3. Thanks for your reponse. Maybe you can remove this package from unstable then. Alexandre Pineau -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#324368: kernel-source-2.6.10: kernel doesn't build (gcc 4.0, fbmem.c / fb.h)
Package: kernel-source-2.6.10 Version: 2.6.10-6 Severity: important I cannot build the kernel 2.6.10 with gcc 4.0.1-3 and linux-kernel-headers_2.6.13+0rc3-1.1_i386.deb. I have the following error: In file included from drivers/video/fbmem.c:48: include/linux/fb.h:860: error: array type has incomplete element type drivers/video/fbmem.c: In function 'fb_get_buffer_offset': drivers/video/fbmem.c:178: warning: pointer targets in initialization differ in signedness make[2]: *** [drivers/video/fbmem.o] Error 1 I dont know if it's an issue in gcc, in the kernel or in kernel headers. Regards, Alexandre Pineau -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.4.27-1-386 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-source-2.6.10 depends on: ii binutils 2.16.1-2 The GNU assembler, linker and bina ii bzip2 1.0.2-5high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: mkinitrd relative path
Hi dear initrd maintainers, I'd like to make notice of a few caveats with the /usr/sbin/mkinitrd (debian version 0.1.81.1) command. 1) email address in the script header does not make mention of the [EMAIL PROTECTED] email, so I contacted Herbert Xu which is not the maintainer for Debian. 2) bug with mkinitrd relative path I ran into trouble when using mkinitrd with relative path, example : mkinitrd -o ./my_file With this line the my_file is created into /tmp/mkinitrd.XXX/my_file Then gets deleted on mkinitrd exit :-( . It took me a while to debug and see that it's a CWD related issue. I may deliver a small patch that fix this issue (keep track of CWD) if you wish. Thanks for your attention. Have a nice day :) -- Alexandre Sauvé
Bug#310352: kernel-image-2.6.11-1-k7: cannot reboot after upgrade
Package: kernel-image-2.6.11-1-k7 Version: 2.6.11-5 Severity: critical Justification: breaks the whole system after an apt-get upgrade four of my servers didn't reboot, message on the screen is : kernel can not convert a name into device number /sbin/init 360 cannot.. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-k7 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-image-2.6.11-1-k7 depends on: ii coreutils [fileutils] 5.2.1-2The GNU core utilities ii initrd-tools 0.1.80 tools to create initrd image for p ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
