linux-2.6_2.6.18.dfsg.1-23_i386.changes ACCEPTED
Accepted: linux-2.6_2.6.18.dfsg.1-23.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-23.diff.gz linux-2.6_2.6.18.dfsg.1-23.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-23.dsc linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb linux-headers-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-manual-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.18_2.6.18.dfsg.1-23_all.deb linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-patch-debian-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.18_2.6.18.dfsg.1-23_all.deb linux-source-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-source-2.6.18_2.6.18.dfsg.1-23_all.deb linux-support-2.6.18-6_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-support-2.6.18-6_2.6.18.dfsg.1-23_all.deb linux-tree-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.18_2.6.18.dfsg.1-23_all.deb xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb xen-linux-system-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/xen-linux-system-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb Override entries for your package: linux-2.6_2.6.18.dfsg.1-23.dsc - optional devel linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb
Bug#445987: marked as done (linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU)
Your message dated Wed, 15 Oct 2008 07:52:27 + with message-id [EMAIL PROTECTED] and subject line Bug#445987: fixed in user-mode-linux 2.6.18-1um-2etch.23 has caused the Debian Bug report #445987, regarding linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 445987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445987 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-5-xen-amd64 Version: 2.6.18.dfsg.1-13etch4 Severity: normal I have exported (or whatever you call it) all USB ports on my XEN server to one of the domU instances. I've been using an USB connected printer for some time without problems. However, today I plugged in an USB CD writer. And the oops below came out with the writer unusable. And the XEN is 3.0.3 from etch. From dpkg: ii xen-hypervisor-3.0.3-1-amd64 3.0.3-0-2 The Xen Hypervisor on AMD64 Oct 9 14:23:39 suzy2 kernel: SCSI subsystem initialized Oct 9 14:23:39 suzy2 kernel: Initializing USB Mass Storage driver... Oct 9 14:23:39 suzy2 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Oct 9 14:23:39 suzy2 kernel: usbcore: registered new driver usb-storage Oct 9 14:23:39 suzy2 kernel: USB Mass Storage support registered. Oct 9 14:23:39 suzy2 kernel: usb-storage: device found at 3 Oct 9 14:23:39 suzy2 kernel: usb-storage: waiting for device to settle before scanning Oct 9 14:23:44 suzy2 kernel: Unable to handle kernel NULL pointer dereference at 0078 RIP: Oct 9 14:23:44 suzy2 kernel: [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: PGD 2d33d067 PUD 2ca54067 PMD 0 Oct 9 14:23:44 suzy2 kernel: Oops: [1] SMP Oct 9 14:23:44 suzy2 kernel: CPU 0 Oct 9 14:23:44 suzy2 kernel: Modules linked in: usb_storage scsi_mod ide_core nfsd exportfs ipv6 ppdev parport_pc lp parport nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_mod evdev pcspkr usblp 8250 serial_core ext3 jbd mbcache ehci_hcd uhci_hcd Oct 9 14:23:44 suzy2 kernel: Pid: 3423, comm: usb-stor-scan Not tainted 2.6.18-4-xen-amd64 #1 Oct 9 14:23:44 suzy2 kernel: RIP: e030:[881e23a2] [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: RSP: e02b:8800214c7ca8 EFLAGS: 00010246 Oct 9 14:23:44 suzy2 kernel: RAX: RBX: 880033cce088 RCX: 0071 Oct 9 14:23:44 suzy2 kernel: RDX: 0067 RSI: 00f0 RDI: 880022ea5800 Oct 9 14:23:44 suzy2 kernel: RBP: 880022ea5800 R08: 880034023000 R09: 0014 Oct 9 14:23:44 suzy2 kernel: R10: 881e38d0 R11: 0048 R12: 880028c2e028 Oct 9 14:23:44 suzy2 kernel: R13: 880022ea5800 R14: R15: 880028c2e000 Oct 9 14:23:44 suzy2 kernel: FS: 2b97072425c0() GS:804c4000() knlGS: Oct 9 14:23:44 suzy2 kernel: CS: e033 DS: ES: Oct 9 14:23:44 suzy2 kernel: Process usb-stor-scan (pid: 3423, threadinfo 8800214c6000, task 88003406a080) Oct 9 14:23:44 suzy2 kernel: Stack: 881e29f2 880022afb800 880022afb800 880028c2e000 Oct 9 14:23:44 suzy2 kernel: 881e4641 880022ea5968 0001881de1fe 880022ea5800 Oct 9 14:23:44 suzy2 kernel: Oct 9 14:23:44 suzy2 kernel: Call Trace: Oct 9 14:23:44 suzy2 kernel: [881e29f2] :scsi_mod:scsi_alloc_queue+0x65/0xb6 Oct 9 14:23:44 suzy2 kernel: [881e4641] :scsi_mod:scsi_alloc_sdev+0x12e/0x1d2 Oct 9 14:23:44 suzy2 kernel: [881e4870] :scsi_mod:scsi_probe_and_add_lun+0x10d/0x9c6 Oct 9 14:23:44 suzy2 kernel: [881e546c] :scsi_mod:scsi_alloc_target+0x21e/0x327 Oct 9 14:23:44 suzy2 kernel: [881e56b8] :scsi_mod:__scsi_scan_target+0xc3/0x5e7 Oct 9 14:23:44 suzy2 kernel: [8026084e] _spin_lock_irq+0x9/0x14 Oct 9 14:23:44 suzy2 kernel: [8025f1a8] wait_for_completion_interruptible_timeout+0x140/0x14e Oct 9 14:23:44 suzy2 kernel: [8027d487] default_wake_function+0x0/0xe Oct 9 14:23:44 suzy2 kernel: [881e5c21] :scsi_mod:scsi_scan_channel+0x45/0x70 Oct 9 14:23:44 suzy2 kernel: [881e5d0c] :scsi_mod:scsi_scan_host_selected+0xc0/0xfb Oct 9 14:23:44 suzy2 kernel: [802901a5] keventd_create_kthread+0x0/0x61 Oct 9 14:23:44 suzy2 kernel: [882074c9] :usb_storage:usb_stor_scan_thread+0x12e/0x156 Oct 9 14:23:44 suzy2 kernel: [80290368] autoremove_wake_function+0x0/0x2e Oct 9 14:23:44
Bug#498309: marked as done (xfs filesystem corruption due to attr2 bug)
Your message dated Wed, 15 Oct 2008 07:52:27 + with message-id [EMAIL PROTECTED] and subject line Bug#498309: fixed in user-mode-linux 2.6.18-1um-2etch.23 has caused the Debian Bug report #498309, regarding xfs filesystem corruption due to attr2 bug to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 498309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498309 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.18+6etch3 I've lost 2 xfs filesystems this weekend after adding lots of acls to many files. With some help from the people of the xfs IRC channel, I could nail it down to a problem with xfs an attr2. It seems that the debian 2.6.18 kernel is missing a very important bugfix. The bug report originally comes from red hat: https://bugzilla.redhat.com/show_bug.cgi?id=212201 This is what I found in the archibes of the xfs mailing list: http://www.linux.sgi.com/archives/xfs/2006-12/msg00104.html The filesystems that crashed had a size of 2 TB and 6 TB. xfs_repair couldn't help much. In the end I had to restore the data from the last backup. I know that packages in the stable release are only updated with important (security) fixes. But this bug can (did) cause data loss and would be worth a fix. Ralf ---End Message--- ---BeginMessage--- Source: user-mode-linux Source-Version: 2.6.18-1um-2etch.23 We believe that the bug you reported is fixed in the latest version of user-mode-linux, which is due to be installed in the Debian FTP archive: user-mode-linux_2.6.18-1um-2etch.23.diff.gz to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.23.diff.gz user-mode-linux_2.6.18-1um-2etch.23.dsc to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.23.dsc user-mode-linux_2.6.18-1um-2etch.23_i386.deb to pool/main/u/user-mode-linux/user-mode-linux_2.6.18-1um-2etch.23_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated user-mode-linux package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 13 Oct 2008 17:47:53 -0600 Source: user-mode-linux Binary: user-mode-linux Architecture: source i386 Version: 2.6.18-1um-2etch.23 Distribution: stable Urgency: high Maintainer: User Mode Linux Maintainers [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: user-mode-linux - User-mode Linux (kernel) Closes: 445987 498309 Changes: user-mode-linux (2.6.18-1um-2etch.23) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-23: [ Ian Campbell ] * Fix DMA crash under Xen when no IOMMU is present (closes: #445987) . [ dann frazier ] * [xfs] Fix attr2 corruption with btree data extents (closes: #498309) Files: 4fa86f3f3b7ef615787582605c693537 877 misc extra user-mode-linux_2.6.18-1um-2etch.23.dsc 5d833925bf8183f9ed081b6acba4a033 18628 misc extra user-mode-linux_2.6.18-1um-2etch.23.diff.gz fe002e862a48d4b1a66130b104cacf1c 25589992 misc extra user-mode-linux_2.6.18-1um-2etch.23_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFI9QMlhuANDBmkLRkRAv0HAKCR6/fMO384djKX/9AMVLrasWeR7QCfeinI 5rh/Y+4uMsRUxgwmfksvdos= =WqaV -END PGP SIGNATURE- ---End Message---
Bug#498309: marked as done (xfs filesystem corruption due to attr2 bug)
Your message dated Wed, 15 Oct 2008 07:52:20 + with message-id [EMAIL PROTECTED] and subject line Bug#498309: fixed in fai-kernels 1.17+etch.23 has caused the Debian Bug report #498309, regarding xfs filesystem corruption due to attr2 bug to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 498309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498309 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.18+6etch3 I've lost 2 xfs filesystems this weekend after adding lots of acls to many files. With some help from the people of the xfs IRC channel, I could nail it down to a problem with xfs an attr2. It seems that the debian 2.6.18 kernel is missing a very important bugfix. The bug report originally comes from red hat: https://bugzilla.redhat.com/show_bug.cgi?id=212201 This is what I found in the archibes of the xfs mailing list: http://www.linux.sgi.com/archives/xfs/2006-12/msg00104.html The filesystems that crashed had a size of 2 TB and 6 TB. xfs_repair couldn't help much. In the end I had to restore the data from the last backup. I know that packages in the stable release are only updated with important (security) fixes. But this bug can (did) cause data loss and would be worth a fix. Ralf ---End Message--- ---BeginMessage--- Source: fai-kernels Source-Version: 1.17+etch.23 We believe that the bug you reported is fixed in the latest version of fai-kernels, which is due to be installed in the Debian FTP archive: fai-kernels_1.17+etch.23.dsc to pool/main/f/fai-kernels/fai-kernels_1.17+etch.23.dsc fai-kernels_1.17+etch.23.tar.gz to pool/main/f/fai-kernels/fai-kernels_1.17+etch.23.tar.gz fai-kernels_1.17+etch.23_i386.deb to pool/main/f/fai-kernels/fai-kernels_1.17+etch.23_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. dann frazier [EMAIL PROTECTED] (supplier of updated fai-kernels package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 13 Oct 2008 17:52:29 -0600 Source: fai-kernels Binary: fai-kernels Architecture: source i386 Version: 1.17+etch.23 Distribution: stable Urgency: high Maintainer: Holger Levsen [EMAIL PROTECTED] Changed-By: dann frazier [EMAIL PROTECTED] Description: fai-kernels - special kernels for FAI (Fully Automatic Installation) Closes: 445987 498309 Changes: fai-kernels (1.17+etch.23) stable; urgency=high . * Rebuild against linux-source-2.6.18_2.6.18.dfsg.1-23: [ Ian Campbell ] * Fix DMA crash under Xen when no IOMMU is present (closes: #445987) . [ dann frazier ] * [xfs] Fix attr2 corruption with btree data extents (closes: #498309) Files: c0560675eb1281154c3e4663bbb78aa8 725 admin extra fai-kernels_1.17+etch.23.dsc a3a13ca0e0a745d9732637937465 57048 admin extra fai-kernels_1.17+etch.23.tar.gz 93cb3f9580aa9cfc80143d2adcb1fb04 5506466 admin extra fai-kernels_1.17+etch.23_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iD8DBQFI9QMIhuANDBmkLRkRAs8yAJ4t2lt20KcxNyJhFW5C4DnKcjnNfwCghcHr Ul1nCHpY3EZZPCH3JnAK1iA= =V6yq -END PGP SIGNATURE- ---End Message---
Bug#498309: marked as done (xfs filesystem corruption due to attr2 bug)
Your message dated Wed, 15 Oct 2008 07:52:25 + with message-id [EMAIL PROTECTED] and subject line Bug#498309: fixed in linux-2.6 2.6.18.dfsg.1-23 has caused the Debian Bug report #498309, regarding xfs filesystem corruption due to attr2 bug to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 498309: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=498309 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6-amd64 Version: 2.6.18+6etch3 I've lost 2 xfs filesystems this weekend after adding lots of acls to many files. With some help from the people of the xfs IRC channel, I could nail it down to a problem with xfs an attr2. It seems that the debian 2.6.18 kernel is missing a very important bugfix. The bug report originally comes from red hat: https://bugzilla.redhat.com/show_bug.cgi?id=212201 This is what I found in the archibes of the xfs mailing list: http://www.linux.sgi.com/archives/xfs/2006-12/msg00104.html The filesystems that crashed had a size of 2 TB and 6 TB. xfs_repair couldn't help much. In the end I had to restore the data from the last backup. I know that packages in the stable release are only updated with important (security) fixes. But this bug can (did) cause data loss and would be worth a fix. Ralf ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.18.dfsg.1-23 We believe that the bug you reported is fixed in the latest version of linux-2.6, which is due to be installed in the Debian FTP archive: linux-2.6_2.6.18.dfsg.1-23.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-23.diff.gz linux-2.6_2.6.18.dfsg.1-23.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.18.dfsg.1-23.dsc linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.18_2.6.18.dfsg.1-23_all.deb linux-headers-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-all_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-23_i386.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-headers-2.6.18-6_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-486_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-686_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-23_i386.deb linux-image-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb to pool/main/l/linux-2.6/linux-image-2.6.18-6-k7_2.6.18.dfsg.1-23_i386.deb
Bug#445987: marked as done (linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU)
Your message dated Wed, 15 Oct 2008 07:52:25 + with message-id [EMAIL PROTECTED] and subject line Bug#445987: fixed in linux-2.6 2.6.18.dfsg.1-23 has caused the Debian Bug report #445987, regarding linux-image-2.6.18-5-xen-amd64: OOPS with USB storage in xen domU to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 445987: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=445987 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: linux-image-2.6.18-5-xen-amd64 Version: 2.6.18.dfsg.1-13etch4 Severity: normal I have exported (or whatever you call it) all USB ports on my XEN server to one of the domU instances. I've been using an USB connected printer for some time without problems. However, today I plugged in an USB CD writer. And the oops below came out with the writer unusable. And the XEN is 3.0.3 from etch. From dpkg: ii xen-hypervisor-3.0.3-1-amd64 3.0.3-0-2 The Xen Hypervisor on AMD64 Oct 9 14:23:39 suzy2 kernel: SCSI subsystem initialized Oct 9 14:23:39 suzy2 kernel: Initializing USB Mass Storage driver... Oct 9 14:23:39 suzy2 kernel: scsi0 : SCSI emulation for USB Mass Storage devices Oct 9 14:23:39 suzy2 kernel: usbcore: registered new driver usb-storage Oct 9 14:23:39 suzy2 kernel: USB Mass Storage support registered. Oct 9 14:23:39 suzy2 kernel: usb-storage: device found at 3 Oct 9 14:23:39 suzy2 kernel: usb-storage: waiting for device to settle before scanning Oct 9 14:23:44 suzy2 kernel: Unable to handle kernel NULL pointer dereference at 0078 RIP: Oct 9 14:23:44 suzy2 kernel: [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: PGD 2d33d067 PUD 2ca54067 PMD 0 Oct 9 14:23:44 suzy2 kernel: Oops: [1] SMP Oct 9 14:23:44 suzy2 kernel: CPU 0 Oct 9 14:23:44 suzy2 kernel: Modules linked in: usb_storage scsi_mod ide_core nfsd exportfs ipv6 ppdev parport_pc lp parport nfs lockd nfs_acl sunrpc dm_snapshot dm_mirror dm_mod evdev pcspkr usblp 8250 serial_core ext3 jbd mbcache ehci_hcd uhci_hcd Oct 9 14:23:44 suzy2 kernel: Pid: 3423, comm: usb-stor-scan Not tainted 2.6.18-4-xen-amd64 #1 Oct 9 14:23:44 suzy2 kernel: RIP: e030:[881e23a2] [881e23a2] :scsi_mod:scsi_calculate_bounce_limit+0x15/0x49 Oct 9 14:23:44 suzy2 kernel: RSP: e02b:8800214c7ca8 EFLAGS: 00010246 Oct 9 14:23:44 suzy2 kernel: RAX: RBX: 880033cce088 RCX: 0071 Oct 9 14:23:44 suzy2 kernel: RDX: 0067 RSI: 00f0 RDI: 880022ea5800 Oct 9 14:23:44 suzy2 kernel: RBP: 880022ea5800 R08: 880034023000 R09: 0014 Oct 9 14:23:44 suzy2 kernel: R10: 881e38d0 R11: 0048 R12: 880028c2e028 Oct 9 14:23:44 suzy2 kernel: R13: 880022ea5800 R14: R15: 880028c2e000 Oct 9 14:23:44 suzy2 kernel: FS: 2b97072425c0() GS:804c4000() knlGS: Oct 9 14:23:44 suzy2 kernel: CS: e033 DS: ES: Oct 9 14:23:44 suzy2 kernel: Process usb-stor-scan (pid: 3423, threadinfo 8800214c6000, task 88003406a080) Oct 9 14:23:44 suzy2 kernel: Stack: 881e29f2 880022afb800 880022afb800 880028c2e000 Oct 9 14:23:44 suzy2 kernel: 881e4641 880022ea5968 0001881de1fe 880022ea5800 Oct 9 14:23:44 suzy2 kernel: Oct 9 14:23:44 suzy2 kernel: Call Trace: Oct 9 14:23:44 suzy2 kernel: [881e29f2] :scsi_mod:scsi_alloc_queue+0x65/0xb6 Oct 9 14:23:44 suzy2 kernel: [881e4641] :scsi_mod:scsi_alloc_sdev+0x12e/0x1d2 Oct 9 14:23:44 suzy2 kernel: [881e4870] :scsi_mod:scsi_probe_and_add_lun+0x10d/0x9c6 Oct 9 14:23:44 suzy2 kernel: [881e546c] :scsi_mod:scsi_alloc_target+0x21e/0x327 Oct 9 14:23:44 suzy2 kernel: [881e56b8] :scsi_mod:__scsi_scan_target+0xc3/0x5e7 Oct 9 14:23:44 suzy2 kernel: [8026084e] _spin_lock_irq+0x9/0x14 Oct 9 14:23:44 suzy2 kernel: [8025f1a8] wait_for_completion_interruptible_timeout+0x140/0x14e Oct 9 14:23:44 suzy2 kernel: [8027d487] default_wake_function+0x0/0xe Oct 9 14:23:44 suzy2 kernel: [881e5c21] :scsi_mod:scsi_scan_channel+0x45/0x70 Oct 9 14:23:44 suzy2 kernel: [881e5d0c] :scsi_mod:scsi_scan_host_selected+0xc0/0xfb Oct 9 14:23:44 suzy2 kernel: [802901a5] keventd_create_kthread+0x0/0x61 Oct 9 14:23:44 suzy2 kernel: [882074c9] :usb_storage:usb_stor_scan_thread+0x12e/0x156 Oct 9 14:23:44 suzy2 kernel: [80290368] autoremove_wake_function+0x0/0x2e Oct 9 14:23:44 suzy2
Bug#486168: Success, please close bug report.
I have managed to get a recent daily i386 installer to work. The box has been used as a digital video server in a travelling exhibition, and the BIOS had been reset with a memory hole. This did not affect the installation when the i486 kernel was selected but hung during re-boot when the (correct) 686 kernel was selected. The re-boot continued normally after removing the memory hole and re-installing with the 686 kernel using a recent daily installer. -- Chris Bell -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Kernel 2.6.26 and RT patch
Hi you all, I recently compiled my own 2.6.26 kernel applying the Ingo Molnar's rt patch and Processor type and features - Preemption Mode - Complete Preemption (Real-Time) - Y Processor type and features - Timer frequency - 1000 HZ - Y enable deadline as the default IO scheduler enable HPET timer support enable enhanced real time clock support enable the high precision event timer The system boots and everything seems to be ok but after launchig qjackctl the jackd daemon doesn't stops anymore. If I try to stop it using qjackctl gui it refuses to shutdown and from bash happens the same. The result is I can't kill jackd using kill -9 PID The jackd daemon is listed in the ouptput of `ps -ax` with a 'DLs' staus and I can't start/restart it anymore, no way to make it work but reboot... Everything it's ok with 2.6.26 generic... but no RT My box: amd64 dual core running debian lenny Can anyone help? regards raffaele
Bug#494010: Source for dsp56k firmware
On Wed, Oct 15, 2008 at 03:16:56AM +0100, Ben Hutchings wrote: It's for a Motorola 56000 (aka DSP56000 or DSP56K) processor, which is a different architecture but maybe with some similarities. I doubt we have any of the necessary tools but the code is short enough to hand- assemble. I found an assembler, a56 (see http://www.zdomain.com/a56.html), which seems to be DFSG-free (BSD-style license). I'll see about packaging it. -- Robert Millan The DRM opt-in fallacy: Your data belongs to us. We will decide when (and how) you may access your data; but nobody's threatening your freedom: we still allow you to remove your data and not access it at all. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502326: linux-image-2.6.26-1-686: crash in iwl3945
Package: linux-image-2.6.26-1-686 Version: 2.6.26-8 Severity: important My thinkpad X300 has recently developed a rather unpleasant case of instability related to the iwl3945 driver. This bug may be identical to #500914, though the symptoms, including stack trace, are slightly different. Unlike #500914, there's no reason to think that this bug is related to proximity to the access point, as mine is pretty much right outside my door. Also, the crash doesn't happen on boot, but usually happens within about 30 minutes or so. lspci -v reports this wireless interface as 03:00.0 Network controller: Intel Corporation PRO/Wireless 4965 AG or AGN Network Connection (rev 61) Subsystem: Intel Corporation Lenovo ThinkPad T51 Flags: fast devsel, IRQ 17 Memory at f9f0 (64-bit, non-prefetchable) [size=8K] Capabilities: access denied Kernel driver in use: iwl4965 Kernel modules: iwl4965 Kernel output follows: [ 878.071717] iwl4965: Error wrong command queue 63 command id 0x0 [ 878.071717] [ cut here ] [ 878.071717] kernel BUG at drivers/net/wireless/iwlwifi/iwl4965-base.c:3465! [ 878.071717] invalid opcode: [#1] SMP [ 878.071717] Modules linked in: i915 drm rfcomm l2cap bluetooth uinput ppdev parport_pc lp parport ipv6 acpi_cpufreq cpufreq_powersave cpufreq_stats cpufreq_userspace cpufreq_conservative cpufreq_ondemand freq_table netconsole configfs fuse loop joydev snd_hda_intel snd_seq_dummy snd_pcm_oss snd_mixer_oss snd_seq_oss arc4 snd_seq_midi snd_rawmidi snd_pcm ecb crypto_blkcipher psmouse serio_raw snd_seq_midi_event pcspkr i2c_i801 i2c_core iTCO_wdt snd_seq iwl4965 firmware_class iwlcore rfkill mac80211 cfg80211 snd_timer snd_seq_device snd soundcore snd_page_alloc ac battery bay video output button intel_agp agpgart evdev thinkpad_acpi led_class nvram ext3 jbd mbcache ide_cd_mod cdrom sd_mod piix ide_pci_generic ide_core ahci ata_generic libata scsi_mod dock ehci_hcd uhci_hcd usbcore e1000e thermal processor fan thermal_sys [ 878.071717] [ 878.071717] Pid: 0, comm: swapper Not tainted (2.6.26-1-686 #1) [ 878.071717] EIP: 0060:[f8ad9762] EFLAGS: 00010092 CPU: 1 [ 878.071717] EIP is at iwl4965_irq_tasklet+0x2db/0x4de [iwl4965] [ 878.071717] EAX: 0047 EBX: f16b4000 ECX: EDX: 0092 [ 878.071717] ESI: 0001 EDI: f7599020 EBP: f759a058 ESP: f7493ec8 [ 878.071717] DS: 007b ES: 007b FS: 00d8 GS: SS: 0068 [ 878.071717] Process swapper (pid: 0, ti=f7492000 task=f748f520 task.ti=f7492000) [ 878.071717] Stack: 4001 0282 c010fca5 316b4000 0008 005b 005c [ 878.071717]f7599aa0 0006d38c 8000 f759f110 000a 0001 [ 878.071717]c0126867 0001 c036da68 c0126419 0046 c0372de0 00da [ 878.071717] Call Trace: [ 878.071717] [c010fca5] lapic_next_event+0xc/0x10 [ 878.071717] [c0126867] tasklet_action+0x68/0xd0 [ 878.071717] [c0126419] __do_softirq+0x66/0xd3 [ 878.071717] [c01264cb] do_softirq+0x45/0x53 [ 878.071717] [c0126782] irq_exit+0x35/0x67 [ 878.071717] [c0105f3f] do_IRQ+0x52/0x63 [ 878.071717] [c01042a7] common_interrupt+0x23/0x28 [ 878.071717] [c01300d8] module_param_sysfs_remove+0xf/0x23 [ 878.071717] [f884a097] acpi_idle_enter_bm+0x2a9/0x317 [processor] [ 878.071717] [c02495a9] cpuidle_idle_call+0x5b/0x86 [ 878.071717] [c024954e] cpuidle_idle_call+0x0/0x86 [ 878.071717] [c01025ce] cpu_idle+0xab/0xcb [ 878.071717] === [ 878.071717] Code: 8b 88 a8 00 00 00 66 8b 41 06 0f b6 d4 81 e2 bf 00 00 00 83 fa 04 74 17 0f b6 41 04 50 52 68 df 2d ae f8 e8 f0 95 64 c7 83 c4 0c 0f 0b eb fe 0f b6 d0 f6 c4 40 89 54 24 28 8b 87 b0 23 00 00 75 [ 878.071717] EIP: [f8ad9762] iwl4965_irq_tasklet+0x2db/0x4de [iwl4965] SS:ESP 0068:f7493ec8 [ 878.071717] Kernel panic - not syncing: Fatal exception in interrupt -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-8) ([EMAIL PROTECTED]) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Thu Oct 9 15:18:09 UTC 2008 ** Command line: root=/dev/sda1 ro quiet vga=791 quiet ** Not tainted ** Kernel log: [7.526021] Registered led device: tpacpi::dock_batt [7.526021] Registered led device: tpacpi::unknown_led [7.526021] Registered led device: tpacpi::standby [7.529644] thinkpad_acpi: Lenovo BIOS switched to ACPI backlight control mode [7.529644] thinkpad_acpi: standard ACPI backlight interface available, not loading native one... [7.529644] input: ThinkPad Extra Buttons as /class/input/input1 [7.862017] input: Power Button (FF) as /class/input/input2 [7.908595] Linux agpgart interface v0.103 [7.910076] ACPI: Power Button (FF) [PWRF] [7.910163] input: Lid Switch as /class/input/input3 [7.937991] agpgart: Detected an Intel 965GM Chipset. [7.937991] agpgart: Detected 7676K stolen memory. [7.942542] ACPI: Lid Switch [LID] [
linux-2.6 2.6.26-8 MIGRATED to testing
FYI: The status of the linux-2.6 source package in Debian's testing distribution has changed. Previous version: 2.6.26-5 Current version: 2.6.26-8 -- This email is automatically generated; the Debian Release Team [EMAIL PROTECTED] is responsible. See http://release.debian.org/testing-watch/ for more information. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#499366: 4gb seg fixup not fixed in 2.7-14?
On Wed, Oct 15, 2008 at 12:19:49 +0200 Bastian Blank wrote: On Wed, Oct 15, 2008 at 08:55:01AM +0200, Aurelien Jarno wrote: Given how Xen works, a lot of people are not able to change their kernel. This is incorrect. There are now two possibilities to use the guest supplied kernels and the whole bunch of enterprise distributions never really supported it otherwise. One of them can even be considered safe. Could you please provide pointers to these two possibilities? And which one is considered safe? IMHO it is a really bad idea to not support Xen kernels from Etch. I don't know how. The way the kernel in Etch responds to the problem is also not pretty, but this was not really clear at that time of the Etch release. Could you please clarify what's the current (or emerging) best practice for running Xen with Debian? The latest I know of: for dom0: Lenny with the Etch kernel for domU: Lenny This libc update breaks dom0, and xen-linux-system-2.6.26-1-xen-686 from unstable doesn't boot for me either. Should it? -- Thanks, Feri. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging 494010
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.26 tags 494010 - patch Bug#494010: binary firmware in drivers/char/dsp56k.c Tags were: patch fixed-upstream help Tags removed: patch End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#499366: 4gb seg fixup not fixed in 2.7-14?
On Wed, Oct 15, 2008 at 14:45:21 +0200 Ferenc Wagner wrote: xen-linux-system-2.6.26-1-xen-686 from unstable doesn't boot for me either. Should it? It actually does, I was misguided by the hvc vs xvc vs serial console flow control issues. Unfortunately qla2xxx is still broken, but that belongs to another bug report. So this answers my question about the preferred Debian Xen dom0 setup. Thanks for bringing things to this point! -- Feri. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502326: Acknowledgement (linux-image-2.6.26-1-686: crash in iwl3945)
And of course, the bug report should have mentioned iwl4965, not 3945. Retitled accordingly. noah signature.asc Description: Digital signature
Processed: fixing title
Processing commands for [EMAIL PROTECTED]: retitle 502326 linux-image-2.6.26-1-686: crash in iwl4965 Bug#502326: linux-image-2.6.26-1-686: crash in iwl3945 Changed Bug title to `linux-image-2.6.26-1-686: crash in iwl4965' from `linux-image-2.6.26-1-686: crash in iwl3945'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#497621: that's the kernel limit
Hi, I think NR_CPUS is a compile-time upper limit on the number of CPUs a given kernel can handle. It does not reflect the actual number of CPUs the kernel is running on. So this isn't a bug. -- Cheers, Feri. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502346: virtualbox-ose-modules package older than virtualbox-ose
Package: virtualbox-ose-modules-2.6.26-1-amd64
Version: 2.6.26+1.6.2-dfsg-4
Severity: serious
The virtualbox-ose has been updated recently to version 1.6.6, but the
kernel-modules package for VBox (virtualbox-ose-modules) hasn't.
This makes VBox unusable - when trying to start a virtual machine, I get
such error:
The version of the VirtualBox kernel modules and the version of
VirtualBox application are not matching. You can correct this by either
installing the correct virtualbox-ose-modules package (if available)
through apt-get or by building it manually with: module-assistant
auto-install virtualbox-ose.
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).
Kod Wyniku: 0x80004005
Komponent: Console
Interfejs: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
Please create packages with new version of modules.
Sylwester pod palmami!
Egipt już od 1672 zł.
Sprawdź nasze propozycje.
http://klik.wp.pl/?adr=http%3A%2F%2Fwycieczki.wp.plsid=521
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502346: marked as done (virtualbox-ose-modules package older than virtualbox-ose)
Your message dated Wed, 15 Oct 2008 22:12:37 +0200
with message-id [EMAIL PROTECTED]
and subject line Re: Bug#502346: virtualbox-ose-modules package older than
virtualbox-ose
has caused the Debian Bug report #502346,
regarding virtualbox-ose-modules package older than virtualbox-ose
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
502346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=502346
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
---BeginMessage---
Package: virtualbox-ose-modules-2.6.26-1-amd64
Version: 2.6.26+1.6.2-dfsg-4
Severity: serious
The virtualbox-ose has been updated recently to version 1.6.6, but the
kernel-modules package for VBox (virtualbox-ose-modules) hasn't.
This makes VBox unusable - when trying to start a virtual machine, I get
such error:
The version of the VirtualBox kernel modules and the version of
VirtualBox application are not matching. You can correct this by either
installing the correct virtualbox-ose-modules package (if available)
through apt-get or by building it manually with: module-assistant
auto-install virtualbox-ose.
VBox status code: -1912 (VERR_VM_DRIVER_VERSION_MISMATCH).
Kod Wyniku: 0x80004005
Komponent: Console
Interfejs: IConsole {d5a1cbda-f5d7-4824-9afe-d640c94c7dcf}
Please create packages with new version of modules.
Sylwester pod palmami!
Egipt już od 1672 zł.
Sprawdź nasze propozycje.
http://klik.wp.pl/?adr=http%3A%2F%2Fwycieczki.wp.plsid=521
---End Message---
---BeginMessage---
Tomasz Ka%u017Amierczak
This makes VBox unusable
no, it doesn't..
You can correct this by either
installing the correct virtualbox-ose-modules package (if available)
through apt-get or by building it manually with: module-assistant
auto-install virtualbox-ose.
as the message says - /either/ install the prebuilt module, /or/ build
it yourself with m-a.
--
Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist
Email: [EMAIL PROTECTED]
Internet: http://people.panthera-systems.net/~daniel-baumann/
---End Message---
Bug#498536: Still no qla2xxx on -xen-686 (2.6.26-9~snapshot.12311)
Ferenc Wagner [EMAIL PROTECTED] writes: Bastian Blank [EMAIL PROTECTED] writes: On Thu, Sep 25, 2008 at 06:43:38PM +0200, Ferenc Wagner wrote: I can see this oops with linux-image-2.6.26-1-686 2.6.26-5. Is there a .deb available with the fix for testing? I couldn't get the info out of the SVN logs. There are snapshots available for several arches, see http://wiki.debian.org/DebianKernel. Thanks, I know about the snapshots, what I don't know is which of them contains the fix for this bug, if any. I didn't find any mention in the SVN logs, neither in the Linux 2.6.26.[45] changelogs. As 2.6.26-9~snapshot.12311 seems to contain 2.6.26.6, I gave it a try (the Xen flavor, actually, but it does not seem to matter): qla2xxx :01:06.0: Found an ISP2200, irq 16, iobase 0xd102c000 qla2xxx :01:06.0: Configuring PCI space... qla2xxx :01:06.0: Configure NVRAM parameters... udev: renamed network interface eth0 to eth-gb1 qla2xxx :01:06.0: Verifying loaded RISC code... udev: renamed network interface eth1 to eth-gb2 firmware: requesting ql2200_fw.bin qla2xxx :01:06.0: Allocated (252 KB) for firmware dump... scsi1 : qla2xxx qla2xxx :01:06.0: QLogic Fibre Channel HBA Driver: 8.02.01-k4 QLogic QLA22xx - ISP2200: PCI (66 MHz) @ :01:06.0 hdma-, host#=1, fw=2.02.08 TP qla2xxx :01:06.0: LIP reset occured (f7f7). qla2xxx :01:06.0: LOOP UP detected (1 Gbps). BUG: unable to handle kernel NULL pointer dereference at IP: [d113fd3e] :qla2xxx:qla2x00_prep_ms_fdmi_iocb+0x1d/0xa4 *pdpt = Oops: 0002 [#1] SMP Modules linked in: ata_generic(+) libata dock floppy aic7xxx(+) qla2xxx firmware_class scsi_transport_fc scsi_transport_spi scsi_tgt ohci_hcd tg3 scsi_mod usbcore serverworks ide_pci_generic ide_core thermal processor fan thermal_sys Pid: 979, comm: qla2xxx_1_dpc Not tainted (2.6.26-1-xen-686 #1) EIP: 0061:[d113fd3e] EFLAGS: 00010246 CPU: 1 EIP is at qla2x00_prep_ms_fdmi_iocb+0x1d/0xa4 [qla2xxx] EAX: EBX: ECX: 0010 EDX: ESI: ce2bc34c EDI: EBP: ESP: cfd5be68 DS: 007b ES: 007b FS: 00d8 GS: SS: 0069 Process qla2xxx_1_dpc (pid: 979, ti=cfd5a000 task=ceb93a80 task.ti=cfd5a000) Stack: 0010 d1155ac0 ce2bc34c ce2bc34c d113f099 86c6071e 0200 0a19 c0126498 ceb93a80 ce2bc34c ce2bc34c d113f45d 0063 001e ce2bd500 ce2bc34c 0100 001e ce2bc300 ce2bd42c Call Trace: [d113f099] qla2x00_fdmi_rhba+0x19/0x3be [qla2xxx] [c0126498] process_timeout+0x0/0x5 [d113f45d] qla2x00_fdmi_register+0x1f/0x3c1 [qla2xxx] [d1134ab7] qla2x00_configure_loop+0x5ea/0xfab [qla2xxx] [d1138e2f] qla2x00_mailbox_command+0x4cb/0x515 [qla2xxx] [d1139ea3] qla2x00_get_retry_cnt+0x3c/0xb7 [qla2xxx] [c0116839] __wake_up+0x29/0x39 [d11354cd] qla2x00_loop_resync+0x55/0x9e [qla2xxx] [d11326d0] qla2x00_do_dpc+0x433/0x4bf [qla2xxx] [d113229d] qla2x00_do_dpc+0x0/0x4bf [qla2xxx] [c012eb85] kthread+0x38/0x5f [c012eb4d] kthread+0x0/0x5f [c0104267] kernel_thread_helper+0x7/0x10 === Code: 10 88 41 0e 83 c4 18 89 c8 5b 5e 5f 5d c3 55 89 d5 57 56 89 c6 53 83 ec 04 89 0c 24 8b 98 6c 11 00 00 b9 10 00 00 00 31 c0 89 df f3 ab c6 03 29 c6 43 01 01 8b EIP: [d113fd3e] qla2x00_prep_ms_fdmi_iocb+0x1d/0xa4 [qla2xxx] SS:ESP 0069:cfd5be68 ---[ end trace 7ae2fc3608e49da2 ]--- The message is very similar to that of 2.6.26-8 (both -xen-686 and -686 flavors). This happens of every single boot. -- Regards, Feri. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495685: [#495685] firmware-iwlwifi: microcode error
In data martedì 2008-10-14 20:49:17 +0200, Stefano Sabatini ha scritto: In data lunedì 2008-10-06 19:45:36 +0200, Didier Raboud ha scritto: Le mardi 19 août 2008 19:02:56 Stefano Sabatini, vous avez écrit : Package: firmware-iwlwifi Version: 0.12 Severity: grave Justification: renders package unusable I got this when I try to load iwl3945: When I try the command: modprobe iwl3945 it hangs for half a minute, then I get this error: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 iwl3945: Could not read microcode: -2 ACPI: PCI interrupt for device :10:00.0 disabled iwl3945: probe of :10:00.0 failed with error -2 I'm using firmware-iwlwifi 0.12, with a linux-2.6.24 i686 debian custom kernel. Regards. Hi, a new firmware-iwlwifi package is available in unstable. Please try this new package and update your linux-image to get the latest iwlwifi driver and report back if the problem is still alive. N.B. I don't get any error with the firmware... Regards, Updated to iwlwifi-firmware 0.13. [EMAIL PROTECTED] ~ uname -a Linux geppetto 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED] ~ sudo modprobe -r iwl3945 [EMAIL PROTECTED] ~ sudo modprobe iwl3945 with dmesg I get: [ 332.178973] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks [ 332.178973] iwl3945: Copyright(c) 2003-2008 Intel Corporation [ 332.178973] ACPI: PCI Interrupt :10:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 332.178973] PCI: Setting latency timer of device :10:00.0 to 64 [ 332.178973] iwl3945: Detected Intel Wireless WiFi Link 3945ABG [ 332.218972] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels [ 332.218972] phy0: Selected rate control algorithm 'iwl-3945-rs' [EMAIL PROTECTED] ~ sudo iwconfig lono wireless extensions. eth1 no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11 ESSID: Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=0 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 So the module looks correctly loaded. [EMAIL PROTECTED] ~ sudo iwlist wlan0 scanning Here it hangs for 30 seconds more or less, then I get this: wlan0 Interface doesn't support scanning : Network is down From dmesg: [ 372.025418] firmware: requesting iwlwifi-3945-1.ucode [ 432.097666] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 432.097676] iwl3945: Could not read microcode: -2 [EMAIL PROTECTED] ~ locate iwlwifi-3945-1.ucode /lib/firmware/iwlwifi-3945-1.ucode Hints will be highly appreciated. And the problem was... udevd was dead, so it couldn't load the firmware. It took me a good guessing effort for realizing that firmware is loaded by udev, I was indeed experiencing the same loading firmware problem with another module and finally I read something about the firmware being loaded by udev. Please improve the behaviour of the module so that it will check for the presence of udevd and tell explicitely if it isn't present rather than hang forever trying to load the firmware. Anyway, bug report has to be considered closed, now I have to understand why udevd was dying... Thanks, regards. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#495685: marked as done (firmware-iwlwifi: microcode error)
Your message dated Wed, 15 Oct 2008 16:46:33 -0600 with message-id [EMAIL PROTECTED] and subject line Re: Bug#495685: [#495685] firmware-iwlwifi: microcode error has caused the Debian Bug report #495685, regarding firmware-iwlwifi: microcode error to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [EMAIL PROTECTED] immediately.) -- 495685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=495685 Debian Bug Tracking System Contact [EMAIL PROTECTED] with problems ---BeginMessage--- Package: firmware-iwlwifi Version: 0.12 Severity: grave Justification: renders package unusable I got this when I try to load iwl3945: When I try the command: modprobe iwl3945 it hangs for half a minute, then I get this error: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 iwl3945: Could not read microcode: -2 ACPI: PCI interrupt for device :10:00.0 disabled iwl3945: probe of :10:00.0 failed with error -2 I'm using firmware-iwlwifi 0.12, with a linux-2.6.24 i686 debian custom kernel. Regards. -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.24-etchnhalf.1-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information ---End Message--- ---BeginMessage--- On Thu, Oct 16, 2008 at 12:16:54AM +0200, Stefano Sabatini wrote: In data marted? 2008-10-14 20:49:17 +0200, Stefano Sabatini ha scritto: In data luned? 2008-10-06 19:45:36 +0200, Didier Raboud ha scritto: Le mardi 19 ao?t 2008 19:02:56 Stefano Sabatini, vous avez ?crit?: Package: firmware-iwlwifi Version: 0.12 Severity: grave Justification: renders package unusable I got this when I try to load iwl3945: When I try the command: modprobe iwl3945 it hangs for half a minute, then I get this error: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 iwl3945: Could not read microcode: -2 ACPI: PCI interrupt for device :10:00.0 disabled iwl3945: probe of :10:00.0 failed with error -2 I'm using firmware-iwlwifi 0.12, with a linux-2.6.24 i686 debian custom kernel. Regards. Hi, a new firmware-iwlwifi package is available in unstable. Please try this new package and update your linux-image to get the latest iwlwifi driver and report back if the problem is still alive. N.B. I don't get any error with the firmware... Regards, Updated to iwlwifi-firmware 0.13. [EMAIL PROTECTED] ~ uname -a Linux geppetto 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED] ~ sudo modprobe -r iwl3945 [EMAIL PROTECTED] ~ sudo modprobe iwl3945 with dmesg I get: [ 332.178973] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks [ 332.178973] iwl3945: Copyright(c) 2003-2008 Intel Corporation [ 332.178973] ACPI: PCI Interrupt :10:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 332.178973] PCI: Setting latency timer of device :10:00.0 to 64 [ 332.178973] iwl3945: Detected Intel Wireless WiFi Link 3945ABG [ 332.218972] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels [ 332.218972] phy0: Selected rate control algorithm 'iwl-3945-rs' [EMAIL PROTECTED] ~ sudo iwconfig lono wireless extensions. eth1 no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11 ESSID: Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=0 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 So the module looks correctly loaded. [EMAIL PROTECTED] ~ sudo iwlist wlan0 scanning Here it hangs for 30 seconds more or less, then I get this: wlan0 Interface doesn't support scanning : Network is down From dmesg: [ 372.025418] firmware: requesting iwlwifi-3945-1.ucode [ 432.097666] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 432.097676] iwl3945: Could not read microcode: -2 [EMAIL PROTECTED] ~ locate iwlwifi-3945-1.ucode
Bug#502362: kernel 2.6.26 x86_64: some ioctls not mapped from 32bit userland
Package: linux-image-2.6.26-1-amd64
Version: 2.6.26-8
Hello,
while testing 64bit kernel under 32bit userland I found some ioctls that
definitely work on a 32bit kernel and are likely just not correctly
mapped:
ioctl32(hdparm:7607): Unknown cmd fd(3) cmd(031c){t:03;sz:0} arg()
on /dev/hda
HDIO_DRIVE_RESET - hdparm -w /dev/hda
That's not funny, I cannot reset IDE devices anymore.
ioctl32(conserver:4500): Unknown cmd fd(5) cmd(530b){t:'S';sz:0}
arg(0806b17e) on /dev/ttyS5
This one is probably safe - I just have no idea, why (and where)
conserver does CDROM ioctls on a tty - maybe some probing
thingy.
compat_ioctl32: VIDIOC_QUERYCAPioctl32(v4lctl:6890): Unknown cmd fd(5)
cmd(80585600){t:'V';sz:88} arg(097847b0) on /dev/video0
compat_ioctl32: VIDIOC_S_EXT_CTRLSioctl32(vlc:8081): Unknown cmd fd(7)
cmd(c0185648){t:'V';sz:24} arg(f37fe940) on /dev/video0
compat_ioctl32: VIDIOC_ENUM_FRAMEINTERVALSioctl32(vlc:8081): Unknown cmd fd(7)
cmd(c034564b){t:'V';sz:52} arg(f37fee90) on /dev/video0
Those are strange, they seem to be mapped correctly and
transmitted to video4linux compat_ioctl32 but the V4L1-V4L2
re-mapping done there seems to be broken...
regards
Mario
--
There are two major products that come from Berkeley: LSD and UNIX.
We don't believe this to be a coincidence.-- Jeremy S. Anderson
signature.asc
Description: Digital signature
Bug#495685: [#495685] firmware-iwlwifi: microcode error
On Thu, Oct 16, 2008 at 12:16:54AM +0200, Stefano Sabatini wrote: In data marted? 2008-10-14 20:49:17 +0200, Stefano Sabatini ha scritto: In data luned? 2008-10-06 19:45:36 +0200, Didier Raboud ha scritto: Le mardi 19 ao?t 2008 19:02:56 Stefano Sabatini, vous avez ?crit?: Package: firmware-iwlwifi Version: 0.12 Severity: grave Justification: renders package unusable I got this when I try to load iwl3945: When I try the command: modprobe iwl3945 it hangs for half a minute, then I get this error: iwl3945: Detected Intel PRO/Wireless 3945ABG Network Connection iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 iwl3945: Could not read microcode: -2 ACPI: PCI interrupt for device :10:00.0 disabled iwl3945: probe of :10:00.0 failed with error -2 I'm using firmware-iwlwifi 0.12, with a linux-2.6.24 i686 debian custom kernel. Regards. Hi, a new firmware-iwlwifi package is available in unstable. Please try this new package and update your linux-image to get the latest iwlwifi driver and report back if the problem is still alive. N.B. I don't get any error with the firmware... Regards, Updated to iwlwifi-firmware 0.13. [EMAIL PROTECTED] ~ uname -a Linux geppetto 2.6.26-1-686 #1 SMP Thu Oct 9 15:18:09 UTC 2008 i686 GNU/Linux [EMAIL PROTECTED] ~ sudo modprobe -r iwl3945 [EMAIL PROTECTED] ~ sudo modprobe iwl3945 with dmesg I get: [ 332.178973] iwl3945: Intel(R) PRO/Wireless 3945ABG/BG Network Connection driver for Linux, 1.2.26ks [ 332.178973] iwl3945: Copyright(c) 2003-2008 Intel Corporation [ 332.178973] ACPI: PCI Interrupt :10:00.0[A] - GSI 17 (level, low) - IRQ 17 [ 332.178973] PCI: Setting latency timer of device :10:00.0 to 64 [ 332.178973] iwl3945: Detected Intel Wireless WiFi Link 3945ABG [ 332.218972] iwl3945: Tunable channels: 13 802.11bg, 23 802.11a channels [ 332.218972] phy0: Selected rate control algorithm 'iwl-3945-rs' [EMAIL PROTECTED] ~ sudo iwconfig lono wireless extensions. eth1 no wireless extensions. wmaster0 no wireless extensions. wlan0 IEEE 802.11 ESSID: Mode:Managed Frequency:2.412 GHz Access Point: Not-Associated Tx-Power=0 dBm Retry min limit:7 RTS thr:off Fragment thr=2352 B Encryption key:off Link Quality:0 Signal level:0 Noise level:0 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0 So the module looks correctly loaded. [EMAIL PROTECTED] ~ sudo iwlist wlan0 scanning Here it hangs for 30 seconds more or less, then I get this: wlan0 Interface doesn't support scanning : Network is down From dmesg: [ 372.025418] firmware: requesting iwlwifi-3945-1.ucode [ 432.097666] iwl3945: iwlwifi-3945-1.ucode firmware file req failed: Reason -2 [ 432.097676] iwl3945: Could not read microcode: -2 [EMAIL PROTECTED] ~ locate iwlwifi-3945-1.ucode /lib/firmware/iwlwifi-3945-1.ucode Hints will be highly appreciated. And the problem was... udevd was dead, so it couldn't load the firmware. It took me a good guessing effort for realizing that firmware is loaded by udev, I was indeed experiencing the same loading firmware problem with another module and finally I read something about the firmware being loaded by udev. Please improve the behaviour of the module so that it will check for the presence of udevd and tell explicitely if it isn't present rather than hang forever trying to load the firmware. Anyway, bug report has to be considered closed, now I have to understand why udevd was dying... Thanks for the followup! Thanks, regards. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#494010: Source for dsp56k firmware
On Wed, Oct 15, 2008 at 07:49:19PM +0200, Robert Millan wrote: On Wed, Oct 15, 2008 at 06:12:23PM +0200, Robert Millan wrote: On Wed, Oct 15, 2008 at 03:16:56AM +0100, Ben Hutchings wrote: It's for a Motorola 56000 (aka DSP56000 or DSP56K) processor, which is a different architecture but maybe with some similarities. I doubt we have any of the necessary tools but the code is short enough to hand- assemble. I found an assembler, a56 (see http://www.zdomain.com/a56.html), which seems to be DFSG-free (BSD-style license). I'll see about packaging it. Gah, there's a bit more to this: - First I had to run frodos on bootstrap.asm to cleanup the CRLF. I think that's introduced by the BTS. - Attached patch fixes a few errors spit by a56. I think my other two fixes are correct, but I have no idea what the '' / '' candy is supposed to do (hints?). According to the assembler reference manual http://www.freescale.com/files/dsp/doc/ref_manual/DSPASMRM.pdf they mean: - I/O short addressing mode force operator - Short addressing mode force operator - Long addressing mode force operator - Resulting offsets doen't match with the blob. I still haven't figured out how are program code offsets mapped to the output file, but some parts don't match. For example, the blob has a jump (0C 00 40) to 0x40 (and so does a56 output, at offset 0x0 in both cases), but then code from the blob continues at 0xc0, unlike code from a56 which continues at 0x40. Is there some trick to this? It's a 24-bit processor and uses word-addressing, not byte-addressing. Ben. -- Ben Hutchings Never put off till tomorrow what you can avoid all together. signature.asc Description: Digital signature
Bug#381719: Still happening with 2.6.26-8
Howdy, I'm still experiencing this problem with 2.6.26-8. Should I report it upstream or should I reproduce it with a pristine upstream kernel first? -- Matt http://ftbfs.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#501960: git bisect
git bisect points to the following commit: 3971e1a917548977cff71418a7c3575ffbc9571f is first bad commit commit 3971e1a917548977cff71418a7c3575ffbc9571f Author: Alex Nixon [EMAIL PROTECTED] Date: Tue Jul 29 22:33:03 2008 -0700 VFS: increase pseudo-filesystem block size to PAGE_SIZE This commit: commit ba52de123d454b57369f291348266d86f4b35070 Author: Theodore Ts'o [EMAIL PROTECTED] Date: Wed Sep 27 01:50:49 2006 -0700 [PATCH] inode-diet: Eliminate i_blksize from the inode structure caused the block size used by pseudo-filesystems to decrease from PAGE_SIZE to 1024 leading to a doubling of the number of context switches during a kernbench run. Signed-off-by: Alex Nixon [EMAIL PROTECTED] Cc: Andi Kleen [EMAIL PROTECTED] Cc: Jeremy Fitzhardinge [EMAIL PROTECTED] Cc: Peter Zijlstra [EMAIL PROTECTED] Cc: Ingo Molnar [EMAIL PROTECTED] Cc: Ian Campbell [EMAIL PROTECTED] Cc: Theodore Ts'o [EMAIL PROTECTED] Cc: Alexander Viro [EMAIL PROTECTED] Cc: Hugh Dickins [EMAIL PROTECTED] Cc: Jens Axboe [EMAIL PROTECTED] Cc: [EMAIL PROTECTED] [2.6.25.x, 2.6.26.x] Signed-off-by: Andrew Morton [EMAIL PROTECTED] Signed-off-by: Linus Torvalds [EMAIL PROTECTED] :04 04 96f34c51d3eb7e47f101f5cbfa15ae2a6f39480f 900bf1fe7100529521a97c56440185686ce7453d M fs -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#502366: [linux-image-2.6-amd64] please enable custom DSDT adding to initrd (initramfs)
Package: linux-image-2.6-amd64 Severity: wishlist --- Please enter the report below this line. --- i have issues with my ACPI DSDT table and i wish to update it regularly/automatically for the generic Debian kernel and not make a custom kernel. so please see if you can add the kernel patch that allows the insertion / adding of a custom DSDT table to the initrd (initramfs) file without the need to compile a custom kernel. see patch : http://gaugusch.at/kernel.shtml kindly, Nadav :-) --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-1-amd64 Debian Release: lenny/sid 500 unstablewww.debian-multimedia.org 500 unstablesnapshots.ekiga.net 500 unstablemirror.isoc.org.il 500 unstabledeb.opera.com 500 testing security.debian.org 500 stable ftp.debian-unofficial.org 500 kernel-dists-trunk kernel-archive.buildserver.net 101 experimentalftp.de.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== | -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
