Bug#447575: linux-image-2.6.22-2-686: Please enable CONFIG_FB_I810_GTF
Package: linux-image-2.6.22-2-686 Version: 2.6.22-4 Severity: normal Please enable option CONFIG_FB_I810_GTF in kernel config. Without it i810fb can set refresh rates 60hz only with 640x480. -- Package-specific info: ** Version: Linux version 2.6.22-2-686 (Debian 2.6.22-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Fri Aug 31 00:24:01 UTC 2007 ** Not tainted ** Loaded modules: Module Size Used by tun10560 1 i810fb 30652 1 vgastate8256 1 i810fb ipt_MASQUERADE 3616 1 xt_helper 2752 1 xt_MARK 2240 2 ipt_LOG 5952 3 nf_conntrack_ftp9664 0 ipt_REDIRECT2048 3 xt_limit2592 3 xt_tcpudp 3072 139 xt_state2432 3 iptable_mangle 2784 1 iptable_nat 7204 1 nf_nat 17964 3 ipt_MASQUERADE,ipt_REDIRECT,iptable_nat nf_conntrack_ipv4 17772 6 iptable_nat nf_conntrack 60424 7 ipt_MASQUERADE,xt_helper,nf_conntrack_ftp,xt_state,iptable_nat,nf_nat,nf_conntrack_ipv4 nfnetlink 5752 3 nf_nat,nf_conntrack_ipv4,nf_conntrack iptable_filter 2944 1 ip_tables 12260 3 iptable_mangle,iptable_nat,iptable_filter x_tables 14372 10 ipt_MASQUERADE,xt_helper,xt_MARK,ipt_LOG,ipt_REDIRECT,xt_limit,xt_tcpudp,xt_state,iptable_nat,ip_tables cls_route 6624 0 cls_u32 7748 2 cls_fw 5312 1 sch_sfq 5664 11 sch_htb16256 2 rpcsec_gss_krb5 7976 0 auth_rpcgss37408 3 rpcsec_gss_krb5 nfs 224428 0 ipv6 236964 40 nfsd 202800 17 exportfs5472 1 nfsd lockd 60456 3 nfs,nfsd nfs_acl 3520 2 nfs,nfsd sunrpc157852 16 rpcsec_gss_krb5,auth_rpcgss,nfs,nfsd,lockd,nfs_acl reiserfs 220320 4 ext3 121224 6 jbd55336 1 ext3 ext2 60232 1 mbcache 8260 2 ext3,ext2 ide_cd 36416 0 cdrom 32832 1 ide_cd tsdev 7968 0 pcspkr 3104 0 snd_intel8x0 32124 0 parport_pc 33796 0 psmouse36016 0 snd_ac97_codec 92836 1 snd_intel8x0 parport33960 1 parport_pc ac97_bus2272 1 snd_ac97_codec snd_pcm72324 2 snd_intel8x0,snd_ac97_codec snd_timer 21028 1 snd_pcm snd48324 4 snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer soundcore 7520 1 snd snd_page_alloc 9512 2 snd_intel8x0,snd_pcm serio_raw 6692 0 i2c_i8018656 0 rtc12856 0 i2c_core 23552 1 i2c_i801 intel_agp 23188 1 agpgart31912 2 i810fb,intel_agp iTCO_wdt9924 0 shpchp 31060 0 pci_hotplug29184 1 shpchp evdev 9312 0 xfs 503128 2 dm_mirror 20928 0 dm_snapshot16516 0 dm_mod 52160 25 dm_mirror,dm_snapshot ide_disk 16512 8 ata_generic 7556 0 libata115664 1 ata_generic scsi_mod 136620 1 libata e100 33644 0 8139too25536 0 mii 5280 2 e100,8139too uhci_hcd 22960 0 usbcore 125096 2 uhci_hcd piix8868 0 [permanent] generic 4836 0 [permanent] ide_core 113764 4 ide_cd,ide_disk,piix,generic thermal13416 0 processor 31016 1 thermal fan 4836 0 ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation 82815 815 Chipset Host Bridge and Memory Controller Hub [8086:1130] (rev 04) Subsystem: Siemens Nixdorf AG Unknown device [110a:005a] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- Latency: 0 Capabilities: access denied 00:02.0 VGA compatible controller [0300]: Intel Corporation 82815 CGC [Chipset Graphics Controller] [8086:1132] (rev 04) (prog-if 00 [VGA]) Subsystem: Siemens Nixdorf AG Unknown device [110a:004c] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- Latency: 0 Interrupt: pin A routed to IRQ 20 Region 0: Memory at f800 (32-bit, prefetchable) [size=64M] Region 1: Memory at
Bug#420241: not fixed in 2.6.20
reassign 420241 quota found 3.14-7 closed 3.15-4 thanks Edquota segfaults, quota command results: # quota -u 1500 quota: error while getting quota from /dev/sda7 for #1500 (id 1500): Success Bastian Blank wrote: Fixed in 2.6.20, not fixed in 2.6.18. I'm afraid this is not right. I got the exact same problem as detailed above both with the standard etch kernel, as with the 2.6.21 kernel from bpo. So it's not fixed by using a newer kernel. But rather, when taking the unstable package of quota (3.15-4), building it for and installing it on my etch system (with the kernel reverted to 2.6.18-5), the problem disappears. I'm therefore reassigning this bug to the quota package, for reference for those also experiencing the bug in stable, but marked as fixed in the latest sid version. Let me know if there's a problem with that. Thijs
Processed (with 2 errors): not fixed in 2.6.20
Processing commands for [EMAIL PROTECTED]: reassign 420241 quota Bug#420241: quota: error while getting quota: Success Bug reassigned from package `linux-2.6' to `quota'. found 3.14-7 Unknown command or malformed arguments to command. closed 3.15-4 Unknown command or malformed arguments to command. 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#447549: linux-2.6: orinoco.c printk messages flood terminal
On Mon, 22 Oct 2007, Michael Gilbert wrote: i am at a location where a nearby wireless router comes in and out of range, so i get a ton of eth2: New link status: AP Out of Range (0004) and eth2: New link status: AP In Range (0005) messages on the active terminal. this makes it difficult to work (especially in vi). i found a solution using cat 6 /proc/sys/kernel/printk to suppress KERN_INFO and KERN_DEBUG level printk messages. i'm sure there are many other users out there that are annoyed by the current behavior. would it be feasible to have level 6 as the default printk level in debian rather than 7? hiding info, i'm sorry but that's not what people expect from debian, another possible solution would be for orinoco.c (which contains the code that prints these messages) to use the KERN_DEBUG printk level instead of KERN_INFO. i'm wondering why you are reporting this as bug against debian linux-images we have no orinoco specific patch. please discuss that issue upstream on [EMAIL PROTECTED] - any upstream change will directly land into debian. thanks best regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447611: update-initramfs triggerisation
Source: initramfs-tools Version: 0.91b Severity: wishlist Tags: patch The attached patch triggerises the invocation of mkinitramfs by package maintainer scripts via update-initramfs. By `triggerises' I mean that the patch arranges for the formulaic update-initramfs invocations by maintainer scripts (eg of udev, kernel packages, etc.) to call dpkg-trigger instead of actually doing the work of update-initramfs and mkinitramfs. update-initramfs and hence mkinitramfs will be actually run out of initramfs-tools's postinst script during trigger processing. The consequence is that all of the initramfs updates during a dpkg run are deferred, and instead the update is done once at the end. This is achieved by new code in update-initramfs. This detects the formulaic invocation by a maintscript, and exec's dpkg-trigger instead (if the conditions are favourable). An alternative approach would be to change all of the packages not to call update-initramfs but instead to call a new script but this would involve a much more complicated and lengthy transition for no significant benefit. The patch is safe to use with a non-triggers-supporting dpkg and in all transitional states: where the trigger system is not properly set up yet, update-initramfs does its work as normal. Note that sid's dpkg does not yet have the triggers patch merged but there has been extensive discussion of the design and interfaces for triggers and the API should IMO be considered stable. These changes have been tested and released as part of Ubuntu 7.10 aka `gutsy gibbon'. The patch below is the consilidation of the results of our testing. So we believe that this patch can and should be safely applied to sid's initramfs-tools straight away. Ian. diff -ruN ../orig/initramfs-tools-0.85eubuntu16/debian/changelog initramfs-tools-0.85eubuntu18/debian/changelog --- ../orig/initramfs-tools-0.85eubuntu16/debian/changelog 2007-07-31 06:31:15.0 +0100 +++ initramfs-tools-0.85eubuntu18/debian/changelog 2007-08-24 15:45:43.0 +0100 @@ -1,3 +1,19 @@ +initramfs-tools (0.85eubuntu18) gutsy; urgency=low + + * Use dpkg-trigger even in our own postinst, unless we're doing +trigger processing or the running dpkg version doesn't support +reflexive triggers. This reduces update-initramfs runs from two per +upgrade batch to one per batch. + + -- Ian Jackson [EMAIL PROTECTED] Fri, 24 Aug 2007 15:45:38 +0100 + +initramfs-tools (0.85eubuntu17) gutsy; urgency=low + + * Use dpkg-trigger (if available and operational) to save on +calls to update-initramfs. + + -- Ian Jackson [EMAIL PROTECTED] Thu, 16 Aug 2007 16:03:52 +0100 + initramfs-tools (0.85eubuntu16) gutsy; urgency=low * Load thermal modules on lpia as well. This may need to change in diff -ruN ../orig/initramfs-tools-0.85eubuntu16/debian/initramfs-tools.postinst initramfs-tools-0.85eubuntu18/debian/initramfs-tools.postinst --- ../orig/initramfs-tools-0.85eubuntu16/debian/initramfs-tools.postinst 2006-12-21 23:32:07.0 + +++ initramfs-tools-0.85eubuntu18/debian/initramfs-tools.postinst 2007-08-24 15:45:02.0 +0100 @@ -25,9 +25,16 @@ -# Regenerate initramfs on upgrade -if [ $1 = configure ] [ -n $2 ]; then +# Regenerate initramfs whenever we go to dpkg state `installed' + +if [ x$1 != xtriggered ] \ + dpkg --compare-versions $DPKG_RUNNING_VERSION ge '1.14.5ubuntu10~~' +then update-initramfs -u + # ... this activates the trigger, if triggers are working +else + DPKG_MAINTSCRIPT_PACKAGE='' update-initramfs -u + # ... force it to actually happen fi #DEBHELPER# diff -ruN ../orig/initramfs-tools-0.85eubuntu16/debian/initramfs-tools.triggers initramfs-tools-0.85eubuntu18/debian/initramfs-tools.triggers --- ../orig/initramfs-tools-0.85eubuntu16/debian/initramfs-tools.triggers 1970-01-01 01:00:00.0 +0100 +++ initramfs-tools-0.85eubuntu18/debian/initramfs-tools.triggers 2007-08-16 16:03:05.0 +0100 @@ -0,0 +1 @@ +interest update-initramfs diff -ruN ../orig/initramfs-tools-0.85eubuntu16/debian/rules initramfs-tools-0.85eubuntu18/debian/rules --- ../orig/initramfs-tools-0.85eubuntu16/debian/rules 2006-12-21 23:32:07.0 + +++ initramfs-tools-0.85eubuntu18/debian/rules 2007-08-16 16:10:49.0 +0100 @@ -8,3 +8,7 @@ for x in `find scripts/ -maxdepth 1 -type d | tail -n+2`; do \ chmod -R +x $$x; \ done + +binary-install/initramfs-tools:: + install -m 644 -o 0 -g 0 debian/initramfs-tools.triggers \ + debian/initramfs-tools/DEBIAN/triggers diff -ruN ../orig/initramfs-tools-0.85eubuntu16/update-initramfs initramfs-tools-0.85eubuntu18/update-initramfs --- ../orig/initramfs-tools-0.85eubuntu16/update-initramfs 2007-04-10 16:07:41.0 +0100 +++ initramfs-tools-0.85eubuntu18/update-initramfs 2007-08-16 16:56:23.0 +0100 @@ -4,11 +4,24 @@ BOOTDIR=/boot
Some of your Debian packages might need attention
Dear Debian Kernel Team, The following possible problem(s) were detected in the package(s) you maintain in Debian: === linux-2.6: = This package has 9 RC bug(s) more than 21 days old: - #242866 http://bugs.debian.org/242866 drivers containing firmware blobs - #243022 http://bugs.debian.org/243022 ymfpci_image.h: Sourceless microcode without permission to redistribute - #383403 http://bugs.debian.org/383403 linux-2.6: includes nondistributable and non-free binary firmware - #412950 http://bugs.debian.org/412950 linux-2.6: [legal] the current kernel tarball doesn't respect the GR 2006-007 - #417121 http://bugs.debian.org/417121 pcmciautils: Data Corruption while using Texas Instrument PCI7420 --CardBus - #423040 http://bugs.debian.org/423040 Source package contains non-free IETF RFC/I-D - #430984 http://bugs.debian.org/430984 pthreads issue with libc6 - #433187 http://bugs.debian.org/433187 linux-2.6 - [sparc64-smp] produces unkillable processes - #440445 http://bugs.debian.org/440445 linux-2.6 - dies after some time on t2000 since .22 This is an automated mail. These mails are sent monthly. For more information about these mails, refer to http://wiki.debian.org/qa.debian.org/DdpoByMail We are sorry if this mail was useless for you. If you think it was avoidable (that we can detect easily that the problems weren't actually problems), please reply to it and let us know. If you don't want to receive this type of mail any more, you can reply to this mail and use one of the following commands at the beginning of the mail: - unsubscribe email You will no longer receive any mail for any package - ignore package email You will no longer receive information about that package in those mails. So if that package is the only one with problems, you won't receive anything. - ignore bug email You will no longer receive information about this bug. All commands are manually processed, but you will receive confirmation. The commands are just here so that we know precisely what you want. A more detailed status of your packages is available from the DDPO. See: http://qa.debian.org/[EMAIL PROTECTED] Don't hesitate to reply to this mail if you have questions. The wiki page will be updated with useful information. -- DDPOMail, run by Lucas Nussbaum -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#447611: update-initramfs triggerisation
Processing commands for [EMAIL PROTECTED]: tags 447611 -patch Bug#447611: update-initramfs triggerisation Tags were: patch Tags removed: patch stop 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#447611: update-initramfs triggerisation
tags 447611 -patch
stop
On Mon, 22 Oct 2007, Ian Jackson wrote:
The attached patch triggerises the invocation of mkinitramfs by
package maintainer scripts via update-initramfs.
snipp long desc
thanks for the long description.
i'm following dpkg git, once this cool feature is merged,
i'm happy to apply a patch using it. i didn't see it merged in
the master tree yet. as i didn't follow the dpkg discsussions
i don't know current status.
diff -ruN ../orig/initramfs-tools-0.85eubuntu16/debian/changelog
initramfs-tools-0.85eubuntu18/debian/changelog
--- ../orig/initramfs-tools-0.85eubuntu16/debian/changelog2007-07-31
06:31:15.0 +0100
+++ initramfs-tools-0.85eubuntu18/debian/changelog2007-08-24
15:45:43.0 +0100
@@ -1,3 +1,19 @@
+initramfs-tools (0.85eubuntu18) gutsy; urgency=low
+
+ * Use dpkg-trigger even in our own postinst, unless we're doing
+trigger processing or the running dpkg version doesn't support
+reflexive triggers. This reduces update-initramfs runs from two per
+upgrade batch to one per batch.
+
+ -- Ian Jackson [EMAIL PROTECTED] Fri, 24 Aug 2007 15:45:38 +0100
+
+initramfs-tools (0.85eubuntu17) gutsy; urgency=low
+
+ * Use dpkg-trigger (if available and operational) to save on
+calls to update-initramfs.
+
+ -- Ian Jackson [EMAIL PROTECTED] Thu, 16 Aug 2007 16:03:52 +0100
+
initramfs-tools (0.85eubuntu16) gutsy; urgency=low
* Load thermal modules on lpia as well. This may need to change in
need to get a deeper look in git-dch as debian changelog only generates
conflicts, better snipped for now also as ubuntu specific:
patching file debian/changelog
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file debian/changelog.rej
diff -ruN
../orig/initramfs-tools-0.85eubuntu16/debian/initramfs-tools.postinst
initramfs-tools-0.85eubuntu18/debian/initramfs-tools.postinst
--- ../orig/initramfs-tools-0.85eubuntu16/debian/initramfs-tools.postinst
2006-12-21 23:32:07.0 +
+++ initramfs-tools-0.85eubuntu18/debian/initramfs-tools.postinst
2007-08-24 15:45:02.0 +0100
@@ -25,9 +25,16 @@
-# Regenerate initramfs on upgrade
-if [ $1 = configure ] [ -n $2 ]; then
+# Regenerate initramfs whenever we go to dpkg state `installed'
+
+if [ x$1 != xtriggered ] \
if [ $1 != triggered ] \
seems more readable, don't know why the oldstyle x$string = string
remains in usage?
+ dpkg --compare-versions $DPKG_RUNNING_VERSION ge '1.14.5ubuntu10~~'
+then
ubuntu specific, would with high probab trigger on the wrong versions,
also why is this needed?
has there been a buggy dpkg trigger support!?
update-initramfs -u
+ # ... this activates the trigger, if triggers are working
please comment before command.
+else
+ DPKG_MAINTSCRIPT_PACKAGE='' update-initramfs -u
+ # ... force it to actually happen
fi
same
#DEBHELPER#
diff -ruN
../orig/initramfs-tools-0.85eubuntu16/debian/initramfs-tools.triggers
initramfs-tools-0.85eubuntu18/debian/initramfs-tools.triggers
--- ../orig/initramfs-tools-0.85eubuntu16/debian/initramfs-tools.triggers
1970-01-01 01:00:00.0 +0100
+++ initramfs-tools-0.85eubuntu18/debian/initramfs-tools.triggers
2007-08-16 16:03:05.0 +0100
@@ -0,0 +1 @@
+interest update-initramfs
interest ???
please short comment above why this specific choice?
diff -ruN ../orig/initramfs-tools-0.85eubuntu16/debian/rules
initramfs-tools-0.85eubuntu18/debian/rules
--- ../orig/initramfs-tools-0.85eubuntu16/debian/rules2006-12-21
23:32:07.0 +
+++ initramfs-tools-0.85eubuntu18/debian/rules2007-08-16
16:10:49.0 +0100
@@ -8,3 +8,7 @@
for x in `find scripts/ -maxdepth 1 -type d | tail -n+2`; do \
chmod -R +x $$x; \
done
+
+binary-install/initramfs-tools::
+ install -m 644 -o 0 -g 0 debian/initramfs-tools.triggers \
+ debian/initramfs-tools/DEBIAN/triggers
no i-t uses cdbs,
please add to debian/initramfs-tools.install
but maybe i misread and there is no cdbs support for that yet??
diff -ruN ../orig/initramfs-tools-0.85eubuntu16/update-initramfs
initramfs-tools-0.85eubuntu18/update-initramfs
--- ../orig/initramfs-tools-0.85eubuntu16/update-initramfs2007-04-10
16:07:41.0 +0100
+++ initramfs-tools-0.85eubuntu18/update-initramfs2007-08-16
16:56:23.0 +0100
@@ -4,11 +4,24 @@
BOOTDIR=/boot
CONF=/etc/initramfs-tools/update-initramfs.conf
KPKGCONF=/etc/kernel-img.conf
+USETRIGGERS=true
set -e
[ -r ${CONF} ] . ${CONF}
+if $USETRIGGERS \
+ test x$DPKG_MAINTSCRIPT_PACKAGE != x \
+ test $# = 1 \
+ test x$1 = x-u \
+ dpkg-trigger --check-supported 2/dev/null
why not using built-ins?
if [ -n $USETRIGGERS ]
Bug#447611: update-initramfs triggerisation
maximilian attems wrote: no i-t uses cdbs, please add to debian/initramfs-tools.install but maybe i misread and there is no cdbs support for that yet?? More simply, debhelper supports it as of version 5.0.59. -- see shy jo signature.asc Description: Digital signature
Bug#447611: update-initramfs triggerisation
Ian Jackson wrote: Content-Description: message body text + test x$DPKG_MAINTSCRIPT_PACKAGE != x \ I take it that this is a magic flag variable set by dpkg when running a postinst? J/C. -- see shy jo signature.asc Description: Digital signature
linux-2.6_2.6.22-5_amd64.changes ACCEPTED
Accepted: linux-2.6_2.6.22-5.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.22-5.diff.gz linux-2.6_2.6.22-5.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.22-5.dsc linux-doc-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.22_2.6.22-5_all.deb linux-headers-2.6.22-3-all-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-all-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-all_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-all_2.6.22-5_amd64.deb linux-headers-2.6.22-3-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-vserver_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver_2.6.22-5_amd64.deb linux-headers-2.6.22-3_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3_2.6.22-5_amd64.deb linux-image-2.6.22-3-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-amd64_2.6.22-5_amd64.deb linux-image-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb linux-libc-dev_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.22-5_amd64.deb linux-manual-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.22_2.6.22-5_all.deb linux-patch-debian-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.22_2.6.22-5_all.deb linux-source-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-source-2.6.22_2.6.22-5_all.deb linux-support-2.6.22-3_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-support-2.6.22-3_2.6.22-5_all.deb linux-tree-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.22_2.6.22-5_all.deb Override entries for your package: linux-2.6_2.6.22-5.dsc - optional devel linux-doc-2.6.22_2.6.22-5_all.deb - optional doc linux-headers-2.6.22-3-all-amd64_2.6.22-5_amd64.deb - optional devel linux-headers-2.6.22-3-all_2.6.22-5_amd64.deb - optional devel linux-headers-2.6.22-3-amd64_2.6.22-5_amd64.deb - optional devel linux-headers-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb - optional devel linux-headers-2.6.22-3-vserver_2.6.22-5_amd64.deb - optional devel linux-headers-2.6.22-3_2.6.22-5_amd64.deb - optional devel linux-image-2.6.22-3-amd64_2.6.22-5_amd64.deb - optional admin linux-image-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb - optional admin linux-libc-dev_2.6.22-5_amd64.deb - optional devel linux-manual-2.6.22_2.6.22-5_all.deb - optional doc linux-patch-debian-2.6.22_2.6.22-5_all.deb - optional devel linux-source-2.6.22_2.6.22-5_all.deb - optional devel linux-support-2.6.22-3_2.6.22-5_all.deb - optional devel linux-tree-2.6.22_2.6.22-5_all.deb - optional devel Announcing to [EMAIL PROTECTED] Closing bugs: 411813 413311 444104 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#411813: marked as done (linux-2.6/alpha: math-emu built as a module, should be built-in)
Your message dated Mon, 22 Oct 2007 19:44:43 + with message-id [EMAIL PROTECTED] and subject line Bug#411813: fixed in linux-2.6 2.6.22-5 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-2.6 Version: 2.6.18-7 Severity: important Throughout the 2.6 kernel series, users of alpha systems of ev56-class and below have been reporting problems with certain fp operations not working correctly that did work when using 2.4 kernels[1]. The source of this behavior has recently been identified[2] -- the math-emu driver is configured as a module instead of being built-in, which it never was before, and without this driver the kernel doesn't provide complete IEEE semantics. The upstream description of this config option says: This option is required for IEEE compliant floating point arithmetic on the Alpha. The only time you would ever not say Y is to say M in order to debug the code. Say Y unless you know what you are doing. Not only that, it's not even *possible* to disable this driver when building an SMP kernel. So the behavior is inconsistent between the SMP and UP alpha kernel images; upstream discourages modularizing this driver at all except for debugging; there is definitely a wide range of hardware where one would never want to have this driver disabled as it will break fp math; and users aren't going to know to look for this module. Unless someone has a good reason why this should be built as a module, I plan to update the configs for inclusion in the -11 upload. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ [1] http://lists.debian.org/debian-alpha/2006/06/msg00073.html [2] http://lists.debian.org/debian-alpha/2007/02/msg00016.html ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.22-5 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.22-5.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.22-5.diff.gz linux-2.6_2.6.22-5.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.22-5.dsc linux-doc-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.22_2.6.22-5_all.deb linux-headers-2.6.22-3-all-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-all-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-all_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-all_2.6.22-5_amd64.deb linux-headers-2.6.22-3-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-vserver_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver_2.6.22-5_amd64.deb linux-headers-2.6.22-3_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3_2.6.22-5_amd64.deb linux-image-2.6.22-3-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-amd64_2.6.22-5_amd64.deb linux-image-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb linux-libc-dev_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.22-5_amd64.deb linux-manual-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.22_2.6.22-5_all.deb linux-patch-debian-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.22_2.6.22-5_all.deb linux-source-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-source-2.6.22_2.6.22-5_all.deb linux-support-2.6.22-3_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-support-2.6.22-3_2.6.22-5_all.deb linux-tree-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.22_2.6.22-5_all.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. Maximilian Attems [EMAIL PROTECTED] (supplier of updated linux-2.6 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the
Bug#444104: marked as done (Kernel crashes on boot on IP32 (SGI O2))
Your message dated Mon, 22 Oct 2007 19:44:43 + with message-id [EMAIL PROTECTED] and subject line Bug#444104: fixed in linux-2.6 2.6.22-5 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-2.6 Version: 2.6.20-1 Severity: serious Our IP32 kernel crashes on boot since 2.6.20. This is because we use CONFIG_BUILD_ELF64 tha accidentally got broken upstream. There's a fix upstream for this in 2.6.23. I'll backport http://www.linux-mips.org/g/linux/db423f6e to 2.6.22 and put it into SVN. -- Martin Michlmayr http://www.cyrius.com/ ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.22-5 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.22-5.diff.gz to pool/main/l/linux-2.6/linux-2.6_2.6.22-5.diff.gz linux-2.6_2.6.22-5.dsc to pool/main/l/linux-2.6/linux-2.6_2.6.22-5.dsc linux-doc-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-doc-2.6.22_2.6.22-5_all.deb linux-headers-2.6.22-3-all-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-all-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-all_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-all_2.6.22-5_amd64.deb linux-headers-2.6.22-3-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb linux-headers-2.6.22-3-vserver_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3-vserver_2.6.22-5_amd64.deb linux-headers-2.6.22-3_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-headers-2.6.22-3_2.6.22-5_amd64.deb linux-image-2.6.22-3-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-amd64_2.6.22-5_amd64.deb linux-image-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-image-2.6.22-3-vserver-amd64_2.6.22-5_amd64.deb linux-libc-dev_2.6.22-5_amd64.deb to pool/main/l/linux-2.6/linux-libc-dev_2.6.22-5_amd64.deb linux-manual-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-manual-2.6.22_2.6.22-5_all.deb linux-patch-debian-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-patch-debian-2.6.22_2.6.22-5_all.deb linux-source-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-source-2.6.22_2.6.22-5_all.deb linux-support-2.6.22-3_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-support-2.6.22-3_2.6.22-5_all.deb linux-tree-2.6.22_2.6.22-5_all.deb to pool/main/l/linux-2.6/linux-tree-2.6.22_2.6.22-5_all.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. Maximilian Attems [EMAIL PROTECTED] (supplier of updated linux-2.6 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: Thu, 11 Oct 2007 13:31:38 + Source: linux-2.6 Binary: linux-image-2.6.22-3-sb1-bcm91250a linux-image-2.6.22-3-powerpc-miboot linux-headers-2.6.22-3-all-i386 linux-image-2.6.22-3-vserver-powerpc64 linux-support-2.6.22-3 linux-headers-2.6.22-3-parisc64 linux-image-2.6.22-3-s390 linux-headers-2.6.22-3-all-armel linux-image-2.6.22-3-footbridge linux-headers-2.6.22-3-vserver-amd64 linux-headers-2.6.22-3-686 linux-image-2.6.22-3-amiga linux-image-2.6.22-3-vserver-k7 linux-image-2.6.22-3-sb1a-bcm91480b linux-headers-2.6.22-3-all-ia64 linux-image-2.6.22-3-alpha-smp linux-headers-2.6.22-3-r5k-cobalt linux-image-2.6.22-3-ixp4xx linux-image-2.6.22-3-parisc64 linux-headers-2.6.22-3-powerpc linux-headers-2.6.22-3-all-arm linux-headers-2.6.22-3-parisc-smp linux-headers-2.6.22-3-amd64 linux-image-2.6.22-3-vserver-amd64 linux-image-2.6.22-3-vserver-powerpc linux-headers-2.6.22-3-all-m68k linux-headers-2.6.22-3-ixp4xx linux-image-2.6.22-3-alpha-generic linux-headers-2.6.22-3-sparc64 linux-headers-2.6.22-3-powerpc-miboot linux-image-2.6.22-3-vserver-alpha linux-image-2.6.22-3-s390x linux-image-2.6.22-3-4kc-malta linux-headers-2.6.22-3-vserver-k7 linux-headers-2.6.22-3-s390 linux-headers-2.6.22-3-mac
Bug#447659: linux-image-2.6.22-2-686: Since .21, loaded but unused (no devices attached) firewire_ohci, pcmcia prevents uswsusp
Package: linux-image-2.6.22-2-686 Version: 2.6.22-4 Severity: minor Since .21, with which I never had this problem, I have experienced uswsusp failures because of either of these drivers, despite never having devices of either sort attached. I can work around it by blacklisting the modules, but that would no longer be great if I did want to use either sort of device! -- Package-specific info: ** Version: Linux version 2.6.22-2-686 (Debian 2.6.22-4) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070812 (prerelease) (Debian 4.1.2-15)) #1 SMP Fri Aug 31 00:24:01 UTC 2007 ** Not tainted ** Kernel log: PM: Writing back config space on device :01:08.0 at offset 1 (was 290, writing 2900117) pnp: Failed to activate device 00:03. pnp: Failed to activate device 00:04. pnp: Failed to activate device 00:0b. hda: selected mode 0x45 Restarting tasks ... done. swsusp: Basic memory bitmaps freed swsusp: Basic memory bitmaps created Stopping tasks ... done. Shrinking memory... -\|done (11557 pages freed) Freed 46228 kbytes in 0.16 seconds (288.92 MB/s) Suspending console(s) usb_device usbdev4.1: PM: suspend 0-1, parent usb4 already 2 usb_endpoint usbdev4.1_ep81: PM: suspend 0-1, parent 4-0:1.0 already 2 hub 4-0:1.0: PM: suspend 2-1, parent usb4 already 2 usb_endpoint usbdev4.1_ep00: PM: suspend 0-1, parent usb4 already 2 usb_device usbdev3.1: PM: suspend 0-1, parent usb3 already 2 usb_endpoint usbdev3.1_ep81: PM: suspend 0-1, parent 3-0:1.0 already 2 hub 3-0:1.0: PM: suspend 2-1, parent usb3 already 2 usb_endpoint usbdev3.1_ep00: PM: suspend 0-1, parent usb3 already 2 usb_device usbdev2.1: PM: suspend 0-1, parent usb2 already 2 usb_endpoint usbdev2.1_ep81: PM: suspend 0-1, parent 2-0:1.0 already 2 hub 2-0:1.0: PM: suspend 2-1, parent usb2 already 2 usb_endpoint usbdev2.1_ep00: PM: suspend 0-1, parent usb2 already 2 usb_device usbdev1.1: PM: suspend 0-1, parent usb1 already 2 usb_endpoint usbdev1.1_ep81: PM: suspend 0-1, parent 1-0:1.0 already 2 hub 1-0:1.0: PM: suspend 2-1, parent usb1 already 2 usb_endpoint usbdev1.1_ep00: PM: suspend 0-1, parent usb1 already 2 ACPI: PCI interrupt for device :00:1f.6 disabled ACPI: PCI interrupt for device :00:1f.5 disabled ACPI: PCI interrupt for device :00:1d.7 disabled ACPI: PCI interrupt for device :00:1d.2 disabled ACPI: PCI interrupt for device :00:1d.1 disabled ACPI: PCI interrupt for device :00:1d.0 disabled Disabling non-boot CPUs ... swsusp: critical section: swsusp: Need to copy 62578 pages Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. ACPI: Transitioning device [FN00] to D3 ACPI: Transitioning device [FN00] to D3 ACPI: PCI Interrupt :00:02.0[A] - GSI 16 (level, low) - IRQ 17 ACPI: PCI Interrupt :00:1d.0[A] - GSI 16 (level, low) - IRQ 17 PCI: Setting latency timer of device :00:1d.0 to 64 usb usb1: root hub lost power or was reset ACPI: PCI Interrupt :00:1d.1[B] - GSI 19 (level, low) - IRQ 18 PCI: Setting latency timer of device :00:1d.1 to 64 usb usb2: root hub lost power or was reset ACPI: PCI Interrupt :00:1d.2[C] - GSI 18 (level, low) - IRQ 19 PCI: Setting latency timer of device :00:1d.2 to 64 usb usb3: root hub lost power or was reset ACPI: PCI Interrupt :00:1d.7[D] - GSI 23 (level, low) - IRQ 20 PCI: Setting latency timer of device :00:1d.7 to 64 usb usb4: root hub lost power or was reset ehci_hcd :00:1d.7: debug port 1 PCI: cache line size of 32 is not supported by device :00:1d.7 PM: Writing back config space on device :00:1e.0 at offset 6 (was 40010100, writing 40050100) PCI: Setting latency timer of device :00:1e.0 to 64 ACPI: PCI Interrupt :00:1f.1[A] - GSI 18 (level, low) - IRQ 19 PM: Writing back config space on device :00:1f.5 at offset 1 (was 295, writing 293) ACPI: PCI Interrupt :00:1f.5[B] - GSI 17 (level, low) - IRQ 16 PCI: Setting latency timer of device :00:1f.5 to 64 ACPI: PCI Interrupt :00:1f.6[B] - GSI 17 (level, low) - IRQ 16 PCI: Setting latency timer of device :00:1f.6 to 64 PCMCIA: socket dee98440: *** DANGER *** unable to remove socket power ACPI: PCI Interrupt :01:03.1[B] - GSI 18 (level, low) - IRQ 19 PM: Writing back config space on device :01:05.0 at offset 1 (was 2900116, writing 2900112) PM: Writing back config space on device :01:08.0 at offset f (was 38080100, writing 38080105) PM: Writing back config space on device :01:08.0 at offset 5 (was 1, writing cc01) PM: Writing back config space on device :01:08.0 at offset 4 (was 0, writing fe8fe000) PM: Writing back config space on device :01:08.0 at offset 3 (was 0, writing 4010) PM: Writing back config space on device :01:08.0 at offset 1 (was 290, writing 2900117) pnp: Failed to activate device 00:03. pnp: Failed to activate device 00:04. pnp: Failed to activate device 00:0b. hda: selected mode 0x45 Restarting tasks ... done. swsusp: Basic memory bitmaps freed ipw2100: Intel(R)
Bug#447659: linux-image-2.6.22-2-686: Since .21, loaded but unused (no devices attached) firewire_ohci, pcmcia prevents uswsusp
On Mon, Oct 22, 2007 at 10:53:50PM +0100, Reuben Thomas wrote: Package: linux-image-2.6.22-2-686 Version: 2.6.22-4 Severity: minor Since .21, with which I never had this problem, I have experienced uswsusp failures because of either of these drivers, despite never having devices of either sort attached. I can work around it by blacklisting the modules, but that would no longer be great if I did want to use either sort of device! hmmm firewire based on 2.6.22 is old can you please try newer trunk 2.6.23, it has allmost latest firewire git and worked well for all the firewire bug reports. see trunk snapshots apt lines - http://wiki.debian.org/DebianKernel regards -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#447549: linux-2.6: orinoco.c printk messages flood terminal
would it be feasible to have level 6 as the default printk level in debian rather than 7? hiding info, i'm sorry but that's not what people expect from debian, info is not being hidden -- it will still be fully available via dmesg. and if someone really wants/needs this level of verbosity in their terminal, they can certainly increase the printk level back to 7. the point is to reduce the annoyance to average users. another possible solution would be for orinoco.c (which contains the code that prints these messages) to use the KERN_DEBUG printk level instead of KERN_INFO. i'm wondering why you are reporting this as bug against debian linux-images we have no orinoco specific patch. please discuss that issue upstream on [EMAIL PROTECTED] - any upstream change will directly land into debian. i reported it here because this is an alternative to the first suggestion above (changing the debian default kernel printk level). i figured it was up to the kernel maintainers to determine the correct solution. maybe the appropriate solution should be for orinoco.c to only print messages to dmesg, rather than to the shell as well as dmesg? i am not really that familiar with the kernel -- is there an alternative to printk that would do this? i will also take this upstream. thanks. mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Meeting for etch and a half
(sorry for the nasty cross-posting) hey, Now that 2.6.23 is out and the proposed timeframe for etch 1/2 is just over two months away, its probably a good time to start making some progress on an etch 1/2. Perhaps we should start with an IRC meeting? I've created a wiki page here with an initial stab at an agenda, starting with Is it still a good idea?: http://wiki.debian.org/EtchAndAHalf If we have consensus is to proceed, then I'd like to see if we can come up with a list of next steps. I'll be travelling Thur-Monday of this week, so Wednesday is the only day I can do this week, but next week is pretty open. If you're interested in attending, please mark available times here: http://www.doodle.ch/wa4r43rq55uif8rf -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: please file bugs against the right package
Processing commands for [EMAIL PROTECTED]: reassign 447682 linux-2.6 Bug#447682: RFP: linux-source-2.6.23 needed Bug reassigned from package `wnpp' to `linux-2.6'. retitle 447682 linux-2.6: please package new upstream version (2.6.23) Bug#447682: RFP: linux-source-2.6.23 needed Changed Bug title to `linux-2.6: please package new upstream version (2.6.23)' from `RFP: linux-source-2.6.23 needed'. 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]
