Processed: reopening 517833
Processing commands for cont...@bugs.debian.org:
reopen 517833
Bug #517833 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] better
document net.ipv?.conf.all.* interface
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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: sysctl net.ipv?.conf.all.* interface broken
Processing commands for cont...@bugs.debian.org:
retitle 517833 better document net.ipv?.conf.all.* interface
Bug #517833 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] sysctl
net.ipv?.conf.all.* interface broken
Changed Bug title to 'better document net.ipv?.conf.all.* interface' from
'sysctl net.ipv?.conf.all.* interface broken'
severity 517833 wishlist
Bug #517833 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] better
document net.ipv?.conf.all.* interface
Severity set to 'wishlist' from 'important'
thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#517833: marked as done (better document net.ipv?.conf.all.* interface)
Your message dated Sun, 16 Aug 2009 11:10:24 +0200
with message-id 20090816091023.gd11...@lapse.rw.madduck.net
and subject line Re: sysctl net.ipv?.conf.all.* interface broken
has caused the Debian Bug report #517833,
regarding better document net.ipv?.conf.all.* interface
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 ow...@bugs.debian.org
immediately.)
--
517833: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517833
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-2.6
Version: 2.6.24-6~etchnhalf.8
Severity: important
Forwarded: http://marc.info/?l=linux-kernelm=123599691025508w=2
[ObFront: I wanted to make this critical and tagged security, but
until I find more information, I'll leave it as is]
seamus# head ipv6/conf/{all,eth0}/accept_ra
== ipv6/conf/all/accept_ra ==
1
== ipv6/conf/eth0/accept_ra ==
1
seamus# echo 0 | ipv6/conf/all/accept_ra
seamus# head ipv6/conf/{all,eth0}/accept_ra
== ipv6/conf/all/accept_ra ==
0
== ipv6/conf/eth0/accept_ra ==
1
ipv6/conf/echo/accept_ra should be 0 as well, but it isn't. This
applies to all ipv[46]/conf/all/* I've tried, between 2.6.24 and
2.6.28. I have not been able to try an earlier kernel.
-- System Information:
Debian Release: squeeze/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.26-1-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
.''`. martin f. krafft madd...@d.o Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Description: Digital signature (see http://martin-krafft.net/gpg/)
---End Message---
---BeginMessage---
retitle 517833 better document net.ipv?.conf.all.* interface
severity 517833 wishlist
thanks
also sprach Moritz Muehlenhoff j...@inutil.org [2009.08.13.2349 +0200]:
This has been explained in the link above to work as excepted,
closing the bug.
I think sysctl should adequately document this.
The situation is quite a mess I think (it's extremely inconsistent),
and it would be best to fix it up, but given that that's unlikely to
happen anytime soon, adequate documentation is necessary.
--
.''`. martin f. krafft madd...@d.o Related projects:
: :' : proud Debian developer http://debiansystem.info
`. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org
`- Debian - when you have better things to do than fixing systems
i wish this wish not to be granted!
-- achilles (hofstadter's geb)
---End Message---
Processed: reopening 517833
Processing commands for cont...@bugs.debian.org:
reopen 517833
Bug #517833 {Done: martin f krafft madd...@debian.org} [linux-2.6] better
document net.ipv?.conf.all.* interface
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 debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Updating from custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 to lastest 2.6.18 kernel by appying the diff file from Etch's linux-image-2.6.18-6-686 ?
Hello, I have a custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 (just patched for hardware support etc). I'm concerned with the lastest CVE-2009-2692 so I would like to update my kernel. As it was a lot of work to apply the hardware patches to the initial Etch's linux-source, I wonder if it's possible to update my already-patched-for-hardware- support-2.6.18-linux-source by applying the diff file from the lastest linux-image-2.6.18 package available for Etch ? Regards, Vianney -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Linux Kernel plans for the squeeze cycle
Heya, As announced on dda [RT1], we want to get an impression when releasing Squeeze is feasible. We have proposed a (quite ambitious) freeze in December 2009, and some developers have noted that their planned changes wouldn't be possible in this time frame. So, to find out when releasing would work for most people, it would be great if you could answer the following questions: * Which major upstream releases of the linux kernel are expected in the next two years? Which of those are material for Debian stable, which might be a bit flaky? * How many big transitions will the upcoming changes cause? When should those happen? Can we do something to make them easier? Thanks, Marc [RT1] http://lists.debian.org/debian-devel-announce/2009/07/msg1.html pgpXNXoE9r1B2.pgp Description: PGP signature
Re: Updating from custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 to lastest 2.6.18 kernel by appying the diff file from Etch's linux-image-2.6.18-6-686 ?
On Sun, 2009-08-16 at 12:11 +0200, Vianney Lejeune wrote: Hello, I have a custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 (just patched for hardware support etc). I'm concerned with the lastest CVE-2009-2692 so I would like to update my kernel. As it was a lot of work to apply the hardware patches to the initial Etch's linux-source, I wonder if it's possible to update my already-patched-for-hardware- support-2.6.18-linux-source by applying the diff file from the lastest linux-image-2.6.18 package available for Etch ? Linux 2.6.18 in etch has not yet been updated to fix this. There is a proposed patch at http://bugs.debian.org/541403#10 but I don't know whether it is correct. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Re: Updating from custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 to lastest 2.6.18 kernel by appying the diff file from Etch's linux-image-2.6.18-6-686 ?
Hello, I have a custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 (just patched for hardware support etc). I'm concerned with the lastest CVE-2009-2692 so I would like to update my kernel. As it was a lot of work to apply the hardware patches to the initial Etch's linux- source, I wonder if it's possible to update my already-patched-for-hardware- support-2.6.18-linux-source by applying the diff file from the lastest linux-image-2.6.18 package available for Etch ? Linux 2.6.18 in etch has not yet been updated to fix this. There is a proposed patch at http://bugs.debian.org/541403#10 but I don't know whether it is correct. Thank you for your reply. But technically, let's suppose that a new linux 2.6.18's Debian package is released. Can I directly apply the whole linux-2.6.18's diff file available from the Debian package webpage (http://packages.debian.org/etch/linux-image-2.6.18-6-486) to my custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 to update my kernel with all the fixes from my kernel's version to the lastest ? Regards, Vianney -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509733: Call +4470359 84852 Mr Phil Herald
1,000,000 GBP has been Awarded to you in our AWARDPROMO Please acknowledge the receipt in this mail with the details below to us for more information email phil.hera...@btinternet.com Name: Age: Country: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509733: Call +4470359 84852 Mr Phil Herald
1,000,000 GBP has been Awarded to you in our AWARDPROMO Please acknowledge the receipt in this mail with the details below to us for more information email phil.hera...@btinternet.com Name: Age: Country: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Linux Kernel plans for the squeeze cycle
On Sun, 2009-08-16 at 14:41 +0200, Marc Brockschmidt wrote: Heya, As announced on dda [RT1], we want to get an impression when releasing Squeeze is feasible. We have proposed a (quite ambitious) freeze in December 2009, and some developers have noted that their planned changes wouldn't be possible in this time frame. So, to find out when releasing would work for most people, it would be great if you could answer the following questions: * Which major upstream releases of the linux kernel are expected in the next two years? Which of those are material for Debian stable, which might be a bit flaky? There are no new major versions of the kernel. There is a new stable minor version about every 3 months, which includes all changes that were considered ready following the last release. Sub-minor versions (stable updates) fixing critical bugs are released every few weeks for the current minor version and for some prior minor versions. Long-term support for any version is left to distributors. * How many big transitions will the upcoming changes cause? When should those happen? Can we do something to make them easier? Transitions are generally gradual and we can often control them with build configuration options to enable or disable backward-compatibility features. Transitions should generally be documented in Documentation/feature-removal-schedule.txt. Looking at that now, I see the following potentially disruptive removals that may occur before squeeze freeze. I have ignored removals that I know we're ready for. - Old wireless regulatory domain configuration - user-space needs to use a new API to specify which country's rules to use; I don't know whether this is in place yet - Video4Linux API 1 - user-space should use version 2 - b43 support for firmware revision 410 - maybe we should distribute new firmware - Ability for non root users to shm_get hugetlb pages based on mlock resource limits Changes to specific drivers are less well documented and may in some cases cause real problems at upgrade time. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Re: Updating from custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 to lastest 2.6.18 kernel by appying the diff file from Etch's linux-image-2.6.18-6-686 ?
On Sun, 2009-08-16 at 16:30 +0200, Vianney Lejeune wrote: Hello, I have a custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 (just patched for hardware support etc). I'm concerned with the lastest CVE-2009-2692 so I would like to update my kernel. As it was a lot of work to apply the hardware patches to the initial Etch's linux- source, I wonder if it's possible to update my already-patched-for-hardware- support-2.6.18-linux-source by applying the diff file from the lastest linux-image-2.6.18 package available for Etch ? Linux 2.6.18 in etch has not yet been updated to fix this. There is a proposed patch at http://bugs.debian.org/541403#10 but I don't know whether it is correct. Thank you for your reply. But technically, let's suppose that a new linux 2.6.18's Debian package is released. Can I directly apply the whole linux-2.6.18's diff file available from the Debian package webpage (http://packages.debian.org/etch/linux-image-2.6.18-6-486) to my custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 to update my kernel with all the fixes from my kernel's version to the lastest ? No, the diff also contains all previous bug fixes. You would need to unpack the source package and look in debian/patches/bugfix to get a specific fix patch. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Re: Updating from custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 to lastest 2.6.18 kernel by appying the diff file from Etch's linux-image-2.6.18-6-686 ?
Hello, I have a custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 (just patched for hardware support etc). I'm concerned with the lastest CVE-2009-2692 so I would like to update my kernel. As it was a lot of work to apply the hardware patches to the initial Etch's linux- source, I wonder if it's possible to update my already-patched-for- hardware- support-2.6.18-linux-source by applying the diff file from the lastest linux-image-2.6.18 package available for Etch ? Linux 2.6.18 in etch has not yet been updated to fix this. There is a proposed patch at http://bugs.debian.org/541403#10 but I don't know whether it is correct. Thank you for your reply. But technically, let's suppose that a new linux 2.6.18's Debian package is released. Can I directly apply the whole linux-2.6.18's diff file available from the Debian package webpage (http://packages.debian.org/etch/linux-image-2.6.18-6-486) to my custom linux-source-2.6.18-2.6.18.dfsg.1-23etch1 to update my kernel with all the fixes from my kernel's version to the lastest ? No, the diff also contains all previous bug fixes. You would need to unpack the source package and look in debian/patches/bugfix to get a specific fix patch. So if I want to update to get all the bugfixes until now, I have to apply the diff file from the lastest Etch's kernel webpage to my 2 years' old custom kernel source and I'm done ? Thanks a lot, Vianney -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541828: linux-2.6: Please export symbols for aufs2 (or unionfs2).
Package: linux-2.6
Severity: wishlist
Tags: patch
Currently, we are shipping aufs1 in Debian unstable, which is
not supported upstream anymore since January 2009. This is a
bad situation.
We now have 3 options:
1) Ship aufs2 (which requires 18 symbol exports in the kernel)
2) Ship unionfs2 (which requires 4 symbol exports in the kernel)
3) Ship no kernel-based union filesystem
Option 1 (aufs2):
The straight-forward way from aufs would be to migrate to
aufs2. This option has been chosen by projects like Ubuntu
and is preferred by the Debian Live team.
In comparison to unionfs2, aufs2 has several disadvantages;
it is much larger and thus harder to maintain, it requires
many more exports.
Choosing this option would also allow us to implement option
2 at the same time, as aufs2's symbol export patch is basically
a superset of unionfs2's one.
Option 2 (unionfs2):
UnionFS has been dropped from Debian in the past, because its
maintainer favoured aufs1. The benefit of aufs1 is the much
smaller codebase, the small number of to-be-exported symbols.
Option 3 (not kernel-based, performance ISSUES):
This option may have a large negative impact on the performance
of Debian Live and is not acceptable for them. It was used by
Ubuntu for a short time during their 'karmic' alpha cycle, but
replaced by aufs2.
All in all, I would like you to apply the attached patch
(aufs2-standalone.diff) to the kernel, so we can continue with
option 1. If you think that this option is not acceptable, please
apply unionfs.diff so we can implement option 2.
We could get Unionfs working without any kernel patches at all,
but it would certainly cause security problems, like ignored
file permissions.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (350, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.30-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
Julian Andres Klode - Debian Developer, Ubuntu Member
See http://wiki.debian.org/JulianAndresKlode and http://jak-linux.org/.
aufs2 standalone patch for linux-2.6.30
diff --git a/fs/namei.c b/fs/namei.c
index 967c3db..64a5060 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -337,6 +337,7 @@ int deny_write_access(struct file * file)
return 0;
}
+EXPORT_SYMBOL(deny_write_access);
/**
* path_get - get a reference to a path
@@ -1200,7 +1201,7 @@ out:
* needs parent already locked. Doesn't follow mounts.
* SMP-safe.
*/
-static struct dentry *lookup_hash(struct nameidata *nd)
+struct dentry *lookup_hash(struct nameidata *nd)
{
int err;
@@ -1209,8 +1210,9 @@ static struct dentry *lookup_hash(struct nameidata *nd)
return ERR_PTR(err);
return __lookup_hash(nd-last, nd-path.dentry, nd);
}
+EXPORT_SYMBOL(lookup_hash);
-static int __lookup_one_len(const char *name, struct qstr *this,
+int __lookup_one_len(const char *name, struct qstr *this,
struct dentry *base, int len)
{
unsigned long hash;
@@ -1231,6 +1233,7 @@ static int __lookup_one_len(const char *name, struct qstr *this,
this-hash = end_name_hash(hash);
return 0;
}
+EXPORT_SYMBOL(__lookup_one_len);
/**
* lookup_one_len - filesystem helper to lookup single pathname component
diff --git a/fs/namespace.c b/fs/namespace.c
index 134d494..5a6d038 100644
--- a/fs/namespace.c
+++ b/fs/namespace.c
@@ -38,6 +38,7 @@
/* spinlock for vfsmount related operations, inplace of dcache_lock */
__cacheline_aligned_in_smp DEFINE_SPINLOCK(vfsmount_lock);
+EXPORT_SYMBOL(vfsmount_lock);
static int event;
static DEFINE_IDA(mnt_id_ida);
diff --git a/fs/open.c b/fs/open.c
index bdfbf03..81c39b3 100644
--- a/fs/open.c
+++ b/fs/open.c
@@ -221,6 +221,7 @@ int do_truncate(struct dentry *dentry, loff_t length, unsigned int time_attrs,
mutex_unlock(dentry-d_inode-i_mutex);
return err;
}
+EXPORT_SYMBOL(do_truncate);
static long do_sys_truncate(const char __user *pathname, loff_t length)
{
diff --git a/fs/splice.c b/fs/splice.c
index 666953d..fbc3f77 100644
--- a/fs/splice.c
+++ b/fs/splice.c
@@ -905,8 +905,8 @@ EXPORT_SYMBOL(generic_splice_sendpage);
/*
* Attempt to initiate a splice from pipe to file.
*/
-static long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
- loff_t *ppos, size_t len, unsigned int flags)
+long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
+ loff_t *ppos, size_t len, unsigned int flags)
{
int ret;
@@ -925,13 +925,14 @@ static long do_splice_from(struct pipe_inode_info *pipe, struct file *out,
return out-f_op-splice_write(pipe, out, ppos, len, flags);
}
+EXPORT_SYMBOL(do_splice_from);
/*
* Attempt to initiate a splice from a file to a pipe.
*/
-static long do_splice_to(struct file *in, loff_t *ppos,
- struct pipe_inode_info *pipe, size_t len,
- unsigned int flags)
+long do_splice_to(struct file *in, loff_t *ppos,
+ struct pipe_inode_info *pipe, size_t
Bug#490694: Invalid ROM signature??
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I was able to get my hands on another powermac, approximately the same vintage, to experiment with and discovered that a (locally built) 2.6.25 kernel will boot on it (which is doesn't on my machine, with the oops assoc with this bug). However it does have in its dmesg at the (bug) corresponding point, the following,: aty128fb: Invalid ROM signature should be 0xaa55 aty128fb: BIOS not located, guessing timings. So, although it is a different machine, possibly are some memory conflicts/bad_data associated with the aty128fb driver causing the oops? Additionally, the PCI device being probed at that point is the agp card, e.g. 0001:11:04.0 VGA compatible controller: ATI Technologies Inc Rage 128 RE/SG A locally built 2.6.24.7 kernel works just fine. - -jeff -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqIIMEACgkQMfiP4rwHDZyeQwCfcjp/aHqtemTBzq++9+hYlh9p ACoAmQGMyieWqtGlpBphmkbhwwmj3Gkg =fyKp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541830: linux-image-2.6.30-1-686: Failed to load firmware radeon/R300_cp.bin
Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: normal from dmesg, it shows: radeon_cp: Failed to load firmware radeon/R300_cp.bin [drm:radeon_do_init_cp] *ERROR* Failed to load firmware! my laptop's video card is ATI Mobility Radeon X300 when my kernel is 2.6.26, the radeon dri is fine and direct rendering is available.However, I upgraded the kernel several days ago, and the error message showed as above when booting and from X.Org.log, the rendering is disabled. I used locate radeon to search that bin file and can not find it. -- Package-specific info: ** Version: Linux version 2.6.30-1-686 (Debian 2.6.30-5) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-15) ) #1 SMP Mon Aug 3 16:18:30 UTC 2009 ** Command line: root=/dev/sda1 ro quiet ** Not tainted ** Kernel log: [4.602455] Marking TSC unstable due to TSC halts in idle [4.602534] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3]) [4.602565] processor ACPI_CPU:00: registered as cooling_device0 [4.602569] ACPI: Processor [CPU0] (supports 8 throttling states) [4.696419] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2 [4.696968] ACPI: Lid Switch [LID] [4.697028] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3 [4.697036] ACPI: Power Button [PBTN] [4.697088] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4 [4.697092] ACPI: Sleep Button [SBTN] [4.776167] lib80211: common routines for IEEE802.11 drivers [4.776171] lib80211_crypt: registered algorithm 'NULL' [4.884553] input: PC Speaker as /devices/platform/pcspkr/input/input5 [4.996414] ACPI: Battery Slot [BAT0] (battery present) [5.015243] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [5.119388] yenta_cardbus :03:01.0: CardBus bridge found [1028:0188] [5.124022] Clocksource tsc unstable (delta = -324053240 ns) [5.195532] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input6 [5.213387] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input7 [5.243860] intel_rng: FWH not detected [5.245148] yenta_cardbus :03:01.0: ISA IRQ mask 0x0cb8, PCI irq 19 [5.245153] yenta_cardbus :03:01.0: Socket status: 3006 [5.245157] pci_bus :03: Raising subordinate bus# of parent bus (#03) from #04 to #07 [5.245165] yenta_cardbus :03:01.0: pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff [5.245169] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x2000-0x2fff: clean. [5.245381] yenta_cardbus :03:01.0: pcmcia: parent PCI bridge Memory window: 0xdfc0 - 0xdfcf [5.245385] yenta_cardbus :03:01.0: pcmcia: parent PCI bridge Memory window: 0x8800 - 0x8bff [5.642453] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. [5.644214] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean. [5.644931] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [5.645540] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [5.646299] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [5.707893] ieee80211: 802.11 data/management/control stack, git-1.1.13 [5.707896] ieee80211: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [5.775268] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [5.775272] ipw2200: Copyright(c) 2003-2006 Intel Corporation [5.775336] ipw2200 :03:03.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [5.776241] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [5.776286] ipw2200 :03:03.0: firmware: requesting ipw2200-bss.fw [5.938305] Intel ICH :00:1e.2: PCI INT A - GSI 16 (level, low) - IRQ 16 [5.938341] Intel ICH :00:1e.2: setting latency timer to 64 [6.098958] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels) [6.764035] intel8x0_measure_ac97_clock: measured 55307 usecs (2665 samples) [6.764039] intel8x0: clocking to 48000 [6.764683] Intel ICH Modem :00:1e.3: PCI INT B - GSI 17 (level, low) - IRQ 17 [6.764700] Intel ICH Modem :00:1e.3: setting latency timer to 64 [6.868056] MC'97 1 converters and GPIO not ready (0xff00) [8.598736] Adding 1967888k swap on /dev/sda6. Priority:-1 extents:1 across:1967888k [9.598780] loop: module loaded [9.844679] REISERFS (device sda5): found reiserfs format 3.6 with standard journal [9.844728] REISERFS (device sda5): using ordered data mode [9.845014] REISERFS (device sda5): journal params: device sda5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 [9.845363] REISERFS (device sda5): checking transaction log (sda5) [9.942285] REISERFS (device sda5): Using r5 hash to sort names [ 11.512976] ADDRCONF(NETDEV_UP): eth0:
Processing of linux-2.6.24_2.6.24-6~etchnhalf.8etch3_i386.changes
Upload to ftp.upload.debian.org failed Error messages: Could not create file. The upload will be retried in 0:30:00 Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of linux-2.6.24_2.6.24-6~etchnhalf.8etch3_i386.changes
linux-source-2.6.24_2.6.24-6~etchnhalf.8etch3_all.deb has incorrect size; deleting it linux-support-2.6.24-etchnhalf.1_2.6.24-6~etchnhalf.8etch3_all.deb doesn't exist linux-tree-2.6.24_2.6.24-6~etchnhalf.8etch3_all.deb doesn't exist linux-image-2.6.24-etchnhalf.1-486_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-headers-2.6.24-etchnhalf.1-486_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-image-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-headers-2.6.24-etchnhalf.1-686_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-image-2.6.24-etchnhalf.1-686-bigmem_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-headers-2.6.24-etchnhalf.1-686-bigmem_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-image-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-headers-2.6.24-etchnhalf.1-amd64_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-headers-2.6.24-etchnhalf.1-common_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-headers-2.6.24-etchnhalf.1-all_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist linux-headers-2.6.24-etchnhalf.1-all-i386_2.6.24-6~etchnhalf.8etch3_i386.deb doesn't exist Due to the errors above, the .changes file couldn't be processed. Please fix the problems for the upload to happen. Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of linux-2.6.24_2.6.24-6~etchnhalf.8etch3_i386.changes
/linux-2.6.24_2.6.24-6~etchnhalf.8etch3_i386.changes is already present on target host: -rw---S--- 1 1518 802 8313 Aug 16 16:54 linux-2.6.24_2.6.24-6~etchnhalf.8etch3_i386.changes Either you already uploaded it, or someone else came first. Job linux-2.6.24_2.6.24-6~etchnhalf.8etch3_i386.changes removed. Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541830: marked as done (linux-image-2.6.30-1-686: Failed to load firmware radeon/R300_cp.bin)
Your message dated Sun, 16 Aug 2009 18:31:08 +0100 with message-id 1250443868.21652.189.ca...@localhost and subject line Re: Bug#541830: linux-image-2.6.30-1-686: Failed to load firmware radeon/R300_cp.bin has caused the Debian Bug report #541830, regarding linux-image-2.6.30-1-686: Failed to load firmware radeon/R300_cp.bin 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 ow...@bugs.debian.org immediately.) -- 541830: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541830 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-1-686 Version: 2.6.30-5 Severity: normal from dmesg, it shows: radeon_cp: Failed to load firmware radeon/R300_cp.bin [drm:radeon_do_init_cp] *ERROR* Failed to load firmware! my laptop's video card is ATI Mobility Radeon X300 when my kernel is 2.6.26, the radeon dri is fine and direct rendering is available.However, I upgraded the kernel several days ago, and the error message showed as above when booting and from X.Org.log, the rendering is disabled. I used locate radeon to search that bin file and can not find it. -- Package-specific info: ** Version: Linux version 2.6.30-1-686 (Debian 2.6.30-5) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-15) ) #1 SMP Mon Aug 3 16:18:30 UTC 2009 ** Command line: root=/dev/sda1 ro quiet ** Not tainted ** Kernel log: [4.602455] Marking TSC unstable due to TSC halts in idle [4.602534] ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3] C4[C3]) [4.602565] processor ACPI_CPU:00: registered as cooling_device0 [4.602569] ACPI: Processor [CPU0] (supports 8 throttling states) [4.696419] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input2 [4.696968] ACPI: Lid Switch [LID] [4.697028] input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3 [4.697036] ACPI: Power Button [PBTN] [4.697088] input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4 [4.697092] ACPI: Sleep Button [SBTN] [4.776167] lib80211: common routines for IEEE802.11 drivers [4.776171] lib80211_crypt: registered algorithm 'NULL' [4.884553] input: PC Speaker as /devices/platform/pcspkr/input/input5 [4.996414] ACPI: Battery Slot [BAT0] (battery present) [5.015243] dcdbas dcdbas: Dell Systems Management Base Driver (version 5.6.0-3.2) [5.119388] yenta_cardbus :03:01.0: CardBus bridge found [1028:0188] [5.124022] Clocksource tsc unstable (delta = -324053240 ns) [5.195532] input: PS/2 Mouse as /devices/platform/i8042/serio1/input/input6 [5.213387] input: AlpsPS/2 ALPS GlidePoint as /devices/platform/i8042/serio1/input/input7 [5.243860] intel_rng: FWH not detected [5.245148] yenta_cardbus :03:01.0: ISA IRQ mask 0x0cb8, PCI irq 19 [5.245153] yenta_cardbus :03:01.0: Socket status: 3006 [5.245157] pci_bus :03: Raising subordinate bus# of parent bus (#03) from #04 to #07 [5.245165] yenta_cardbus :03:01.0: pcmcia: parent PCI bridge I/O window: 0x2000 - 0x2fff [5.245169] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x2000-0x2fff: clean. [5.245381] yenta_cardbus :03:01.0: pcmcia: parent PCI bridge Memory window: 0xdfc0 - 0xdfcf [5.245385] yenta_cardbus :03:01.0: pcmcia: parent PCI bridge Memory window: 0x8800 - 0x8bff [5.642453] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x100-0x3af: clean. [5.644214] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x3e0-0x4ff: clean. [5.644931] pcmcia_socket pcmcia_socket0: cs: IO port probe 0x820-0x8ff: clean. [5.645540] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xc00-0xcf7: clean. [5.646299] pcmcia_socket pcmcia_socket0: cs: IO port probe 0xa00-0xaff: clean. [5.707893] ieee80211: 802.11 data/management/control stack, git-1.1.13 [5.707896] ieee80211: Copyright (C) 2004-2005 Intel Corporation jketr...@linux.intel.com [5.775268] ipw2200: Intel(R) PRO/Wireless 2200/2915 Network Driver, 1.2.2kmprq [5.775272] ipw2200: Copyright(c) 2003-2006 Intel Corporation [5.775336] ipw2200 :03:03.0: PCI INT A - GSI 17 (level, low) - IRQ 17 [5.776241] ipw2200: Detected Intel PRO/Wireless 2200BG Network Connection [5.776286] ipw2200 :03:03.0: firmware: requesting ipw2200-bss.fw [5.938305] Intel ICH :00:1e.2: PCI INT A - GSI 16 (level, low) - IRQ 16 [5.938341] Intel ICH :00:1e.2: setting latency timer to 64 [6.098958] ipw2200: Detected geography ZZD (13 802.11bg channels, 0 802.11a channels) [6.764035] intel8x0_measure_ac97_clock: measured 55307 usecs
Bug#381351: initramfs-tools: This also happens when SCSI is not settled yet, patch included which works around the problem.
m...@linux.it (Marco d'Itri) writes: I am ready to apply this change but I am unsure about a detail: is there any reason to run udevadm settle a second time before scsi_wait_scan is loaded? You told me it was racy to check for /sys/bus/scsi otherwise, see http://lists.debian.org/debian-boot/2009/06/msg00105.html for the final patch. Of course you are welcome to drop the debugging output and organize the stuff into an list. udevadm trigger #udevadm settle || true if [ -d /sys/bus/scsi ]; then modprobe -q scsi_wait_scan modprobe -r scsi_wait_scan fi udevadm settle || true Does d-i need this too? D-i itself does not particularly need it, because it usually takes long enough to reach the partman step. In theory, maybe it's possible for a preseeded install on a very slow-scanning bus to win the race, and then I don't know offhand if any steps are taken to wait for the devices before partitioning (but I doubt it). Maybe debian-boot has something to add. -- Thanks, Feri. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Re: Linux Kernel plans for the squeeze cycle
There are also some potentially disruptive changes that have already happened since lenny: Separation of firmware This will cause some regressions in hardware support if people do not install the separate firmware package(s). Users need to be made aware of this at upgrade time. There is a bug requesting an automated warning based on driver/hardware detection (#541702). Removal of OpenVZ, Vserver and Xen packages These are large and intrusive patches which require significant upstream effort to adapt to each new kernel version. As a result, they generally lag availability of new kernel versions and may take much longer to stabilise, so they can only be frozen some time after the standard kernel. There is also no guarantee that the upstream projects will continue to support the kernel version we release with. For example, official Xen releases are still based on 2.6.18 with huge changes (though they will apparently move to a newer version soon). Although we were able to use SUSE's forward-port of Xen to 2.6.26, SLE 11 was eventually released with 2.6.27 and so we are on our own with 2.6.26+Xen. Currently, no-one appears to be ready to maintain these variants in squeeze. Ben. -- Ben Hutchings Power corrupts. Absolute power is kind of neat. - John Lehman, Secretary of the US Navy 1981-1987 signature.asc Description: This is a digitally signed message part
Processing of linux-2.6_2.6.18.dfsg.1-24etch3_i386.changes
linux-2.6_2.6.18.dfsg.1-24etch3_i386.changes uploaded successfully to ftp.upload.debian.org along with the files: linux-2.6_2.6.18.dfsg.1-24etch3.dsc linux-2.6_2.6.18.dfsg.1-24etch3.diff.gz linux-doc-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-manual-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-patch-debian-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-source-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-support-2.6.18-6_2.6.18.dfsg.1-24etch3_all.deb linux-tree-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-486_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-486_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-686_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-k7_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch3_i386.deb linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch3_i386.deb xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb xen-linux-system-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processing of linux-2.6_2.6.18.dfsg.1-24etch3_i386.changes
linux-2.6_2.6.18.dfsg.1-24etch3_i386.changes uploaded successfully to localhost along with the files: linux-2.6_2.6.18.dfsg.1-24etch3.dsc linux-2.6_2.6.18.dfsg.1-24etch3.diff.gz linux-doc-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-manual-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-patch-debian-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-source-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-support-2.6.18-6_2.6.18.dfsg.1-24etch3_all.deb linux-tree-2.6.18_2.6.18.dfsg.1-24etch3_all.deb linux-headers-2.6.18-6-all_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-all-i386_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-486_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-486_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-686_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-k7_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-k7_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-686-bigmem_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-686-bigmem_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-amd64_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-amd64_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-vserver_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-vserver-k7_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-vserver-k7_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-xen_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch3_i386.deb linux-modules-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch3_i386.deb xen-linux-system-2.6.18-6-xen-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-xen-vserver_2.6.18.dfsg.1-24etch3_i386.deb linux-image-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb linux-modules-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb linux-headers-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb xen-linux-system-2.6.18-6-xen-vserver-686_2.6.18.dfsg.1-24etch3_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#490694: Extra video card seems to be the problem
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, After doing a lspci -vt and noticing the extra video card that I've not used for years, i.e. forgot totally about it, I tried the 2.6.25 kernel with the extra video card removed (0001:11:04.0). It booted just fine. Then I installed the recent 2.6.26-2 kernel and it booted okay too. FYI: the output of the lspci -vt with both cards installed is: - -+-[0002:21]-+-0b.0 Apple Computer Inc. UniNorth Internal PCI | \-0f.0 Apple Computer Inc. UniNorth GMAC (Sun GEM) +-[0001:10]-+-0b.0 Apple Computer Inc. UniNorth PCI | \-0d.0-[0001:11]--+-02.0 Adaptec AHA-7850 | +-04.0 ATI Technologies Inc Rage 128 RE/SG | +-07.0 Apple Computer Inc. KeyLargo Mac I/O | +-08.0 Apple Computer Inc. KeyLargo USB | +-09.0 Apple Computer Inc. KeyLargo USB | \-0a.0 Texas Instruments TSB12LV23 IEEE-1394 Controller \-[:00]-+-0b.0 Apple Computer Inc. UniNorth AGP \-10.0 ATI Technologies Inc Rage 128 PF/PRO AGP 4x TMDS Let me know what info is needed to fix this problem. - -jeff -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkqIT2IACgkQMfiP4rwHDZw5RwCaA+dDNjoj53g/Y92o8nIkiqzG s3IAn37/nmJvNBFniBmzuEu8VSP27W+y =4BxU -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541234: Re: Bug#541234: initramfs-tools: legacylvm misses 'lvm' required by cryptroot
[ don't drop bug report on cc, this is not a private communication ] On Sun, Aug 16, 2009 at 07:00:11PM +0100, Robert Burrell Donkin wrote: maximilian attems wrote: Version: 0.93.3 On Wed, Aug 12, 2009 at 06:01:16PM +0100, Robert Burrell Donkin wrote: Package: initramfs-tools Version: 0.92o Severity: important Tags: patch this is old stable stuff. and i don't share the assesment of the severity. silly me - to think that problem which rendered the system unbootable after upgrade was important... indeed it is up to the maintainer to assess severity. considering the use case the *one* unbootable box is of course bad for the user in question but in comparison to thousands of others that are working aboves severity is inflated. also it is already quite some time since lenny was released if aboves is an repeatable bug it would already have touched others. legacylvm is only there for upgrade from etch to lenny which doesn't work due to this bug no, again the error is not on initramfs-tools side as legacylvm has nothing todo with encrypted root. all those hook scripts are in the hand of the cryptsetup maintainers. any trouble beyond should be solved in the lvm2 boot hook itself. the upgrade process does not install lvm2 well i haver zero idea why your box didn't have lvm2 installed, nor did you provide info why it wasn't? but whatever, i'll just blog about the issue and your great call not to bother fixing the clear bug which broke the etch-lenny upgrade for me even when given a patch... whatever you feel apropriate. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
linux-2.6_2.6.18.dfsg.1-24etch3_i386.changes REJECTED
Mapping oldstable-security to oldstable-proposed-updates. Rejected: linux-2.6_2.6.18.dfsg.1-24etch3.dsc: old version (2.6.18.dfsg.1-26) in oldstable-proposed-updates = new version (2.6.18.dfsg.1-24etch3) targeted at oldstable-proposed-updates. === Please feel free to respond to this email if you don't understand why your files were rejected, or if you upload new files which address our concerns. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tags 541864 patch
Processing commands for cont...@bugs.debian.org: tags 541864 patch Bug #541864 [initramfs-tools] [PATCH] write blacklisted modules to /etc/modprobe.d/initramfs.conf Added tag(s) patch. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541864: [PATCH] write blacklisted modules to /etc/modprobe.d/initramfs.conf
Package: initramfs-tools
Newer modprobe will only look at .conf files.
---
scripts/init-premount/blacklist |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/scripts/init-premount/blacklist b/scripts/init-premount/blacklist
index 1dd9dbc..2164906 100755
--- a/scripts/init-premount/blacklist
+++ b/scripts/init-premount/blacklist
@@ -21,5 +21,5 @@ esac
# write blacklist to modprobe.d
IFS=','
for b in ${blacklist}; do
- echo blacklist $b /etc/modprobe.d/initramfs
+ echo blacklist $b /etc/modprobe.d/initramfs.conf
done
--
1.6.3.3
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541864: [PATCH] move blacklist script from init-premount to init-top
To have it take effect as early as possible.
Signed-off-by: Tormod Volden debian.tor...@gmail.com
---
Now that I am looking at it, wouldn't it make sense to build the
blacklist file already in init-top? I don't see why init-premount
was chosen instead, but maybe I am missing something.
This patch is on top of the previous one.
Tormod
scripts/init-premount/blacklist | 25 -
scripts/init-top/blacklist | 25 +
2 files changed, 25 insertions(+), 25 deletions(-)
delete mode 100755 scripts/init-premount/blacklist
create mode 100755 scripts/init-top/blacklist
diff --git a/scripts/init-premount/blacklist b/scripts/init-premount/blacklist
deleted file mode 100755
index 2164906..000
--- a/scripts/init-premount/blacklist
+++ /dev/null
@@ -1,25 +0,0 @@
-#!/bin/sh
-
-PREREQ=
-
-prereqs()
-{
- echo $PREREQ
-}
-
-case $1 in
-# get pre-requisites
-prereqs)
- prereqs
- exit 0
- ;;
-esac
-
-# sanity check
-[ -z ${blacklist} ] exit 0
-
-# write blacklist to modprobe.d
-IFS=','
-for b in ${blacklist}; do
- echo blacklist $b /etc/modprobe.d/initramfs.conf
-done
diff --git a/scripts/init-top/blacklist b/scripts/init-top/blacklist
new file mode 100755
index 000..2164906
--- /dev/null
+++ b/scripts/init-top/blacklist
@@ -0,0 +1,25 @@
+#!/bin/sh
+
+PREREQ=
+
+prereqs()
+{
+ echo $PREREQ
+}
+
+case $1 in
+# get pre-requisites
+prereqs)
+ prereqs
+ exit 0
+ ;;
+esac
+
+# sanity check
+[ -z ${blacklist} ] exit 0
+
+# write blacklist to modprobe.d
+IFS=','
+for b in ${blacklist}; do
+ echo blacklist $b /etc/modprobe.d/initramfs.conf
+done
--
1.6.3.3
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#534635: linux-image-2.6.30-1-686: Intel xorg driver problems
Package: linux-image-2.6.30-1-686 Severity: normal fixed 534635 2.6.30-2 thanks I think we can mark this bug fixed, since the mentioned commit was included in 2.6.30.1 and thus in the -2 debian package. I'm still seeing the occasional xorg crash after resuming - most often like one minute after resuming - where the best I can do is to use SysRq-unRaw, Ctrl+Alt+Delete to shutdown which works in about 1/3 xorg crashes. It never happens on a fresh system, only after at least one suspend/resume cycle (5 resumes for the latest crash). I couldn't get any error message so far. But I believe this is a different issue, which might be in Xorg, not in the kernel itself. -- Package-specific info: ** Version: Linux version 2.6.30-1-686 (Debian 2.6.30-5) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-15) ) #1 SMP Mon Aug 3 16:18:30 UTC 2009 ** Command line: root=/dev/mapper/cryptroot ro quiet ** Not tainted ** PCI devices: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:01d8] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 16 Region 0: Memory at eff0 (32-bit, non-prefetchable) [size=512K] Region 1: I/O ports at eff8 [size=8] Region 2: Memory at d000 (32-bit, prefetchable) [size=256M] Region 3: Memory at efec (32-bit, non-prefetchable) [size=256K] Expansion ROM at unassigned [disabled] Capabilities: access denied -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages linux-image-2.6.30-1-686 depends on: ii debconf [debconf-2.0] 1.5.27 Debian configuration management sy ii initramfs-tools [linux-initra 0.93.4 tools for generating an initramfs ii module-init-tools 3.9-2 tools for managing Linux kernel mo Versions of packages linux-image-2.6.30-1-686 recommends: ii libc6-i6862.9-24 GNU C Library: Shared libraries [i Versions of packages linux-image-2.6.30-1-686 suggests: ii grub 0.97-56GRand Unified Bootloader (dummy pa ii grub-legacy [grub]0.97-56GRand Unified Bootloader (Legacy v pn linux-doc-2.6.30 none (no description available) -- debconf information excluded -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509733: Call +4470359 84852 Mr Phil Herald
1,000,000 GBP has been Awarded to you in our AWARDPROMO Please acknowledge the receipt in this mail with the details below to us for more information email phil.hera...@btinternet.com Name: Age: Country: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#509733: Call +4470359 84852 Mr Phil Herald
1,000,000 GBP has been Awarded to you in our AWARDPROMO Please acknowledge the receipt in this mail with the details below to us for more information email phil.hera...@btinternet.com Name: Age: Country: -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 464197
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny3 tags 464197 + pending Bug #464197 [linux-2.6] snd-cs46xx.ko module seems to be missing from linux-image-2.6.24-1-686 Bug #430017 [linux-2.6] kernel: Recording silence, chipset: Cirrus Logic CS 4614/22/24 [CrystalClear SoundFusion Audio Accelerator] Bug #455092 [linux-2.6] Please continue to provide cs46xx sound module Bug #462035 [linux-2.6] linux-image-2.6.23-1-686: snd_cs46xx missing Bug #468151 [linux-2.6] Files missing for SND_CS46XX module Bug #476672 [linux-2.6] linux-image-2.6.24-1-686: alsa snd-cs46xx module missing (all linux-image packages) Bug #477409 [linux-2.6] linux-image-2.6.24-1-686: Sound stopped working with new kernel Bug #493924 [linux-2.6] linux-image-2.6.25-2-686: driver snd-cs46xx.ko should be compiled by default. Bug #493926 [linux-2.6] linux-image-2.6.26-1-686: driver snd-cs46xx.ko should be compiled by default. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. Added tag(s) pending. 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 debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Bug#534635: linux-image-2.6.30-1-686: Intel xorg driver problems
Processing commands for cont...@bugs.debian.org: Package: linux-image-2.6.30-1-686 Limiting to bugs with field 'package' containing at least one of 'linux-image-2.6.30-1-686' Limit currently set to 'package':'linux-image-2.6.30-1-686' Severity: normal Unknown command or malformed arguments to command. fixed 534635 2.6.30-2 Bug #534635 [linux-image-2.6.30-1-686] linux-image-2.6.30-1-686: xorg crashes after resume on intel There is no source info for the package 'linux-image-2.6.30-1-686' at version '2.6.30-2' with architecture '' Unable to make a source version for version '2.6.30-2' Bug Marked as fixed in versions 2.6.30-2. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#495045: iptables: modprobe ip_queue - FATAL: Error inserting ip_queue: Device or resource busy
After some updates in Lenny this bug is disappear. At now module loads normally without errors: $ sudo modprobe ip_queue WARNING: All config files need .conf: /etc/modprobe.d/nvidia-kernel-nkc, it will be ignored in a future release. I think we can close this bug.
