Bug#567468: md homehost
On Thu, 25 Feb 2010 08:16:14 +0100 Goswin von Brederlow goswin-...@web.de wrote: Neil Brown ne...@suse.de writes: On Wed, 24 Feb 2010 14:41:16 +0100 Goswin von Brederlow goswin-...@web.de wrote: Neil Brown ne...@suse.de writes: On Tue, 23 Feb 2010 07:27:00 +0100 martin f krafft madd...@madduck.net wrote: The only issue homehost protects against, I think, is machines that use /dev/md0 directly from grub.conf or fstab. That is exactly correct. If no code or config file depends on a name like /dev/mdX or /dev/md/foo, then you don't need to be concerned about the whole homehost thing. You can either mount by fs-uuid, or mount e.g. /dev/disk/by-id/md-uuid-8fd0af3f:4fbb94ea:12cc2127:f9855db5 What if you have two raids (one local, one from the other hosts that broke down) and both have LVM on it with /dev/vg/root? Shouldn't it only assemble the local raid (as md0 or whatever) and then only start the local volume group? If it assembles the remote raid as /dev/md127 as well then lvm will have problems and the boot will likely (even randomly) go wrong since only one VG can be activated. I think it is pretty common for admins to configure LVM to the same volume group name on different systems. So if you consider raids being pluged into other systems please keep this in mind. You are entirely correct. However lvm problems are not my problems. It has always been my position that the best way to configure md is to explicitly list your arrays in mdadm.conf. But people seem to not like this and want it to all be 'automatic'. So I do my best to make it as automatic as possible but still remove as many of the possible confusion that this can cause as possible. But I cannot remove them all. If you move disks around and boot and lvm gets confused because there are two things call /dev/vg/root, then I'm sorry but there is nothing I can do about that. If you had an mdadm.conf which listed you md arrays, and had auto -all then you can be sure that mdadm would not be contributing to this problem. NeilBrown Yes you can do something about it: Only start the raid arrays with the correct homehost. This is what 'homehost' originally did, but I got a lot of push-back on that. I added the auto line in mdadm.conf so that the admin could choose what happens. If the particular metadata type is enabled on the auto line, the the array is assembled with a random name. If it is disabled, it is not assembled at all (unless explicitly listed in mdadm.conf). I'm not sure exactly how 'auto' interacts with 'homehost'. The documentation I wrote only talks about arrays listed in mdadm.conf or on the command line, not arrays with a valid homehost. I guess I should check. I think I want auto -all to still assemble arrays with a valid homehost. I'll confirm that before I release 3.1.2. If the homehost is only used to decide wether the prefered minor in the metadata is used for the device name then I feel the feature is entirely useless. It would only help in stupid configurations, i.e. when you use the device name directly. Yes. Another scenario where starting a raid with the wrong homehost would be bad is when the raid is degraded and you have a global spare. You probably wouldn't want the global spare of one host to be used to repair a raid of another host. I only support global spares that are explicitly listed in mdadm.conf, so currently this couldn't happen. One day some one is going to ask for auto-configure global spares. Then I'll have to worry about this (or just say no). MfG Goswin PS: If a raid is not listed in mdadm.conf doesn't it currently start too but the name can be random? It depends on the auto line in mdadm.conf Thanks, NeilBrown -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225184658.4df16...@notabene.brown
Bug#571301: Resolved
I've tracked this issue in this instance down to faulty round IDE cables. I replaced the cables, problem solved. I've seen this A LOT lately however and its mentioned in #550005 so I'm not sure if this is the case for every occurrence of lockups during disk-detect, but it was in this case. You can close this bug.
Bug#556030: BUG: soft lockup - CPU#1 stuck for 61s! [java:7582]
hi, i recently started to have the same error-message after a power-blackout. i am running kernel 2.6.32-trunk on a testing/unstable-system for a while now and didn't have any problems before. however, yesterday the computer started showing this error (without the java-part) after running in console for two hours. the mouse was still usable, keyboard-leds responded to their lock-keys, however, no keyboard-input was accepted. after a new boot today, i got a kernel-oops and a reboot some seconds later, so i suspect broken hardware here. maybe overheat is a problem, too, although that should be prevented by my bios which is set to emergency-shutdown and warn at the lowest possible values (i believe it's 65°C for warning and 70°C for shutdown). memtest86+ has been running for more than an hour without problems now, though. probably it uses only the first core? i don't know if this info is helpful at all, but still wanted to let you know. kind regards, patric -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4a02a0311002250040r1ee8ebe1sabf0a6166fb7a...@mail.gmail.com
Bug#567468: md homehost
On Wed, Feb 24, 2010 at 11:46 PM, Neil Brown ne...@suse.de wrote:
On Thu, 25 Feb 2010 08:16:14 +0100
Goswin von Brederlow goswin-...@web.de wrote:
Neil Brown ne...@suse.de writes:
On Wed, 24 Feb 2010 14:41:16 +0100
Goswin von Brederlow goswin-...@web.de wrote:
Neil Brown ne...@suse.de writes:
On Tue, 23 Feb 2010 07:27:00 +0100
martin f krafft madd...@madduck.net wrote:
The only issue homehost protects against, I think, is machines that
use /dev/md0 directly from grub.conf or fstab.
That is exactly correct. If no code or config file depends on a name
like
/dev/mdX or /dev/md/foo, then you don't need to be concerned about the
whole
homehost thing.
You can either mount by fs-uuid, or mount e.g.
/dev/disk/by-id/md-uuid-8fd0af3f:4fbb94ea:12cc2127:f9855db5
What if you have two raids (one local, one from the other hosts that
broke down) and both have LVM on it with /dev/vg/root?
Shouldn't it only assemble the local raid (as md0 or whatever) and then
only start the local volume group? If it assembles the remote raid as
/dev/md127 as well then lvm will have problems and the boot will likely
(even randomly) go wrong since only one VG can be activated.
I think it is pretty common for admins to configure LVM to the same
volume group name on different systems. So if you consider raids being
pluged into other systems please keep this in mind.
You are entirely correct. However lvm problems are not my problems.
It has always been my position that the best way to configure md is to
explicitly list your arrays in mdadm.conf. But people seem to not like
this
and want it to all be 'automatic'. So I do my best to make it as automatic
as possible but still remove as many of the possible confusion that this
can
cause as possible. But I cannot remove them all.
If you move disks around and boot and lvm gets confused because there are
two
things call /dev/vg/root, then I'm sorry but there is nothing I can do
about that. If you had an mdadm.conf which listed you md arrays, and had
auto -all
then you can be sure that mdadm would not be contributing to this problem.
NeilBrown
Yes you can do something about it: Only start the raid arrays with the
correct homehost.
This is what 'homehost' originally did, but I got a lot of push-back on that.
I added the auto line in mdadm.conf so that the admin could choose what
happens.
If the particular metadata type is enabled on the auto line, the the array is
assembled with a random name. If it is disabled, it is not assembled at all
(unless explicitly listed in mdadm.conf).
I'm not sure exactly how 'auto' interacts with 'homehost'. The documentation
I wrote only talks about arrays listed in mdadm.conf or on the command line,
not arrays with a valid homehost. I guess I should check. I think I want
auto -all to still assemble arrays with a valid homehost. I'll confirm
that before I release 3.1.2.
If the homehost is only used to decide wether the prefered minor in the
metadata is used for the device name then I feel the feature is entirely
useless. It would only help in stupid configurations, i.e. when you
use the device name directly.
Yes.
Another scenario where starting a raid with the wrong homehost would be
bad is when the raid is degraded and you have a global spare. You
probably wouldn't want the global spare of one host to be used to repair
a raid of another host.
I only support global spares that are explicitly listed in mdadm.conf, so
currently this couldn't happen. One day some one is going to ask for
auto-configure global spares. Then I'll have to worry about this (or just
say no).
MfG
Goswin
PS: If a raid is not listed in mdadm.conf doesn't it currently start too
but the name can be random?
It depends on the auto line in mdadm.conf
Thanks,
NeilBrown
--
To unsubscribe from this list: send the line unsubscribe linux-raid in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I've always tried to assign volume-groups a host-unique name anyway.
Though I don't currently run enough systems to demand a formal
approach, I imagine a dedicated hostname within the VG name would
work. You could then use a pattern like sys-${HOSTNAME} or sys-*/ to
obtain the hostname on a nominal basis; though obviously if working on
multiple 'system' volume groups at a time the * method fails...
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/4877c76c1002250033o714913dcnaf8970c9aca5e...@mail.gmail.com
Re: Backporting HIGHPTE option patch from tip.git
On Thu, Feb 25, 2010 at 07:33:26AM +, Ian Campbell wrote: Is it acceptable to backport http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commitdiff;h=a73a040e3b18521f83e726abacc2f3992a148388 into the sid kernel? Will it show up in Linus tree any time soon? The followup Xen patch is http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=9be6abceadd654543648b799ae430f30e09959ac and disables HIGHPTE when running under Xen. It prevents crashes under load due to HIGHPTE races which cannot be otherwise (easily) avoided under Xen. The commit message does not describe why, and it is not obvious to me. I'm not sure, but I think this should be possible to do via stable after both patches landed where they belong. Bastian -- I'm a soldier, not a diplomat. I can only tell the truth. -- Kirk, Errand of Mercy, stardate 3198.9 signature.asc Description: Digital signature
2.6.33 experimental upload
plan to do asap, latest friday 12 UT 3 known issues, but no blockers: * sync with 2.6.32-9 * libata switch * dilinger wanted to review OLPC config settings -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225101500.go15...@baikonur.stro.at
Bug#567204: serious filesystem corruption with bigmem kernels
On Thu, Feb 18, 2010 at 01:21:22AM +, Ben Hutchings wrote: On Mon, 2010-02-01 at 15:55 +0100, M. Dietrich wrote: Package: linux-image-686-bigmem Severity: normal i started a reportbug run with the real kernel name. this is the outcome: I can't see any obvious suspect here. Therefore, please file a bug report upstream at http://bugzilla.kernel.org, selecting product 'Platform Specific/Hardware', component 'i386', and providing the same information in your report here. Let us know the bug number so we can track it. close the bug i encountered file system corruption with a non-bigmem kernel today i don't now what's going on will now check the hd best regards sorry for the turbulence, michael -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225103038.ga4...@emdete.de
Processed: tagging 571019
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 571019 + pending
Bug #571019 {Done: maximilian attems m...@debian.org} [linux-2.6] /dev/ttyS1
on openrd-base not working
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
Archive:
http://lists.debian.org/handler.s.c.126709570125297.transcr...@bugs.debian.org
Processed: tagging 508108
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 508108 + pending
Bug #508108 {Done: maximilian attems m...@debian.org} [linux-2.6] Please
enable XVR-500 and XVR-2500 fb drivers for sparc
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
Archive:
http://lists.debian.org/handler.s.c.126709567324881.transcr...@bugs.debian.org
Processed: tagging 566726
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 566726 + pending
Bug #566726 {Done: maximilian attems m...@debian.org} [linux-source-2.6.32]
linux-source-2.6.32: compile fails with multiple definition of `ieee80211_
errors
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
Archive:
http://lists.debian.org/handler.s.c.126709568425057.transcr...@bugs.debian.org
Processed: tagging 550562
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 550562 + pending
Bug #550562 {Done: maximilian attems m...@debian.org} [linux-2.6] radeon:
system freeze on some OpenGl functions
Bug #550977 {Done: maximilian attems m...@debian.org} [linux-2.6] radeon DRI
driver corrupts memory
Bug #559037 {Done: maximilian attems m...@debian.org} [linux-2.6] radeon DRI
driver corrupts memory
Bug #560126 {Done: maximilian attems m...@debian.org} [linux-2.6]
xserver-xorg-video-radeon: Launching GL Apps Corrupts System
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
Archive:
http://lists.debian.org/handler.s.c.126709569325172.transcr...@bugs.debian.org
Processed: tagging 570407
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 570407 + pending
Bug #570407 {Done: maximilian attems m...@debian.org} [linux-2.6] ubifs
errors on OpenRD
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
Archive:
http://lists.debian.org/handler.s.c.126709569725241.transcr...@bugs.debian.org
Processed: tagging 567747
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 567747 + pending
Bug #567747 {Done: maximilian attems m...@debian.org} [linux-2.6] KMS/i945
fails to find LVDS
Bug #569314 {Done: maximilian attems m...@debian.org} [linux-2.6]
/etc/modprobe.d/i915-kms.conf: startx results in a black screen permanently
turned off until reboot
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
Archive:
http://lists.debian.org/handler.s.c.126709567924965.transcr...@bugs.debian.org
Bug#534978: clock drift in Xen domU with clocksource=xen
Hi, Markus Hochholdinger wrote: Here is my solution to this problem, lenny xen kernel: * dom0 with clocksource=jiffies and /proc/sys/xen/independent_wallclock=0 * domU with clocksource=jiffies and /proc/sys/xen/independent_wallclock=0 Using jiffies as a clock source is not a solution, it's a workaround, because its resolution (CONFIG_HZ^1) is not good enough for reading microseconds, that is, time with microseconds will become just monotonic. This will cause problems for any program that wants its time readouts to be strictly increasing, as real-world time usually is :) In other words you will get this (real example from a while ago): % i=0; while :; do i=$((i+1)); if [ $i = 20 ]; then break; fi; date --rfc-3339=ns; done 2009-09-23 13:35:13.123400807+02:00 2009-09-23 13:35:13.127400857+02:00 2009-09-23 13:35:13.131400906+02:00 2009-09-23 13:35:13.135400956+02:00 2009-09-23 13:35:13.139401005+02:00 2009-09-23 13:35:13.143401055+02:00 2009-09-23 13:35:13.147401104+02:00 2009-09-23 13:35:13.151401154+02:00 2009-09-23 13:35:13.151401154+02:00 2009-09-23 13:35:13.155401203+02:00 2009-09-23 13:35:13.155401203+02:00 2009-09-23 13:35:13.159401253+02:00 2009-09-23 13:35:13.163401302+02:00 2009-09-23 13:35:13.167401352+02:00 2009-09-23 13:35:13.171401401+02:00 2009-09-23 13:35:13.171401401+02:00 2009-09-23 13:35:13.175401451+02:00 2009-09-23 13:35:13.179401500+02:00 2009-09-23 13:35:13.183401550+02:00 In my case this manifested itself when some PHP profiling via microtime() suddenly became useless, and it also caused occasional PostgreSQL errors with tables that had timestamp columns as keys, since it became possible for two independent transactions to come in at the exact same time. Having said that, if one doesn't switch to jiffies but wants to use live migration, that ends up being hampered by the Time went backwards problem. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225111854.ga18...@orion.carnet.hr
Bug#567468: md homehost
On Thu, Feb 25, 2010 at 08:16:14AM +0100, Goswin von Brederlow wrote: Yes you can do something about it: Only start the raid arrays with the correct homehost. I agree with you that auto-assembling devices with non-matching homehost (and unknown UUID) is probably not the best idea. If the homehost is only used to decide wether the prefered minor in the metadata is used for the device name then I feel the feature is entirely useless. It would only help in stupid configurations, i.e. when you use the device name directly. I don't think this is a stupid configuration. md was one of the first subsystems providing stable device names and I think they are widely used - alone for historical reasons. I personally feel way better relying on md device names than on some UUIDs. The former are just far more stable than some UUID of some filesystem which changes every time you re-create it. UUIDs of md devices do change as well if you re-create them, but their name remains. Yes, I'm aware of filesystem labels, but they rise the same problems as md devices without homehost attribute. Mario -- There are trivial truths and the great truths. The opposite of a trivial truth is plainly false. The opposite of a great truth is also true. -- Niels Bohr signature.asc Description: Digital signature
Bug#534978: clock drift in Xen domU with clocksource=xen
On Thu, Feb 25, 2010 at 01:33:05PM +0100, Bastian Blank wrote: On Thu, Feb 25, 2010 at 12:18:54PM +0100, Josip Rodin wrote: Using jiffies as a clock source is not a solution, it's a workaround, because its resolution (CONFIG_HZ^1) is not good enough for reading microseconds, that is, time with microseconds will become just monotonic. This will cause problems for any program that wants its time readouts to be strictly increasing, as real-world time usually is :) No. The time resolution is not defined and within one step it will always provide the same value. What? :) The problem here is that a time readout function provides the same value across *two* steps. A monotonic function is one which allows for that. A strictly increasing function is one which does not. Most of the time, just monotonic is okay, but not always. and it also caused occasional PostgreSQL errors with tables that had timestamp columns as keys, since it became possible for two independent transactions to come in at the exact same time. Äh, where is documented, that this supposed to work anyway? The key column has a unique constraint and a default value of current timestamp. Even if two perfectly concurrent writers come in to add a new record, it's still logical to expect for them to be serialized to a minimal extent, because the database itself is explicitly instructed to input all values and maintain their uniqueness. The expectation that all updates take at least one minimal unit of time is perhaps not theoretically valid, but it's certainly like that in the real world (every action takes *some* perceivable time). -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225132755.ga11...@orion.carnet.hr
Processed: closing 571301
Processing commands for cont...@bugs.debian.org: # acknowledged by submitter as hardware problem close 571301 Bug#571301: Hung on Disk-Detect in 5.0.4 stable netinstall for AMD64 'close' is deprecated; see http://www.debian.org/Bugs/Developer#closing. Bug closed, send any further explanations to Scott Nanni envee...@gmail.com 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 Archive: http://lists.debian.org/handler.s.c.126710491225116.transcr...@bugs.debian.org
Bug#534978: clock drift in Xen domU with clocksource=xen
On Thu, Feb 25, 2010 at 12:18:54PM +0100, Josip Rodin wrote: Using jiffies as a clock source is not a solution, it's a workaround, because its resolution (CONFIG_HZ^1) is not good enough for reading microseconds, that is, time with microseconds will become just monotonic. This will cause problems for any program that wants its time readouts to be strictly increasing, as real-world time usually is :) No. The time resolution is not defined and within one step it will always provide the same value. and it also caused occasional PostgreSQL errors with tables that had timestamp columns as keys, since it became possible for two independent transactions to come in at the exact same time. Äh, where is documented, that this supposed to work anyway? Bastian -- Killing is stupid; useless! -- McCoy, A Private Little War, stardate 4211.8 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225123305.ga3...@wavehammer.waldi.eu.org
Bug#534978: clock drift in Xen domU with clocksource=xen
On Thu, Feb 25, 2010 at 02:27:55PM +0100, Josip Rodin wrote: No. The time resolution is not defined and within one step it will always provide the same value. What? :) The problem here is that a time readout function provides the same value across *two* steps. A monotonic function is one which allows for that. A strictly increasing function is one which does not. Most of the time, just monotonic is okay, but not always. No, the time is only monotone, not strictly monotone. (With discreet values, it is not possible to make it strictly monotone.) and it also caused occasional PostgreSQL errors with tables that had timestamp columns as keys, since it became possible for two independent transactions to come in at the exact same time. Äh, where is documented, that this supposed to work anyway? The key column has a unique constraint and a default value of current timestamp. Even if two perfectly concurrent writers come in to add a new record, it's still logical to expect for them to be serialized to a minimal extent, because the database itself is explicitly instructed to input all values and maintain their uniqueness. The expectation that all updates take at least one minimal unit of time is perhaps not theoretically valid, but it's certainly like that in the real world (every action takes *some* perceivable time). Wrong answer. Where is this documented as working in the postgresql documentation? Bastian -- Not one hundred percent efficient, of course ... but nothing ever is. -- Kirk, Metamorphosis, stardate 3219.8 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225140141.ga14...@wavehammer.waldi.eu.org
Re: Backporting HIGHPTE option patch from tip.git
On Thu, 2010-02-25 at 10:18 +0100, Bastian Blank wrote: On Thu, Feb 25, 2010 at 07:33:26AM +, Ian Campbell wrote: Is it acceptable to backport http://git.kernel.org/?p=linux/kernel/git/tip/linux-2.6-tip.git;a=commitdiff;h=a73a040e3b18521f83e726abacc2f3992a148388 into the sid kernel? Will it show up in Linus tree any time soon? Hopefully in the 2.6.33 merge window but I will check with x86 maintainers. The followup Xen patch is http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commitdiff;h=9be6abceadd654543648b799ae430f30e09959ac and disables HIGHPTE when running under Xen. It prevents crashes under load due to HIGHPTE races which cannot be otherwise (easily) avoided under Xen. The commit message does not describe why, and it is not obvious to me. It's a race between pinning a page and kmap/kunmap. There's a path in the pagefault code where the kernel breaks its own locking rules by kmapping a high pte page without holding the pagetable lock which breaks Xen's ability to track the pinned/unpinned state of the page. (I'm going to ask Jeremy to update the commit to include this paragraph of explanation). Jeremy gave some explanation in: http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00921.html (which I've blatantly stolen above) The thread which led to the patch is [Xen-devel] dom0 pvops crash and [Xen-devel] Xen pvops kernel CONFIG_HIGHPTE race/crash involving Pasi Kärkkäinen. It's quite long but the final conclusion starts at: http://lists.xensource.com/archives/html/xen-devel/2010-02/msg00403.html That thread starts at: http://lists.xensource.com/archives/html/xen-devel/2010-01/msg00902.html and there is an older version of the same issue at: http://lists.xensource.com/archives/html/xen-devel/2009-06/msg00519.html I'm not sure, but I think this should be possible to do via stable after both patches landed where they belong. OK will go that route assuming I get confirmation that the patch is destined for 2.3.32. If not then would a backport be appropriate? Ian. -- Ian Campbell Current Noise: Autopsy - Pagan Saviour (Live '90) Q: Why haven't you graduated yet? A: Well, Dad, I could have finished years ago, but I wanted my dissertation to rhyme. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1267109053.11737.10729.ca...@zakaz.uk.xensource.com
Bug#570252: linux-image-2.6.32-2-vserver-amd64: unable to boot with blank screen and keyboard frozen
A recent update of another package, not linux-image-2.6.32-2-vserver-amd64, appears to have resolved this issue. The problem appears to have been the mode switching of the console. The scenario is: 1) boot with the initrd, 2) decrypt the root partition, 3) mount the root partition, 4) switch console mode (previously screen went blank, now font is smaller) 5) prompt for decrypting of remaining logical volumes. (previously invisible) I think we can close the bug except you might want to consider delaying the console mode switching to after all the volumes are mounted. This would make the boot process more robust. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201002250941.04410.jp.lej...@quoininc.com
Bug#534978: clock drift in Xen domU with clocksource=xen
On Thu, Feb 25, 2010 at 03:01:41PM +0100, Bastian Blank wrote: No. The time resolution is not defined and within one step it will always provide the same value. What? :) The problem here is that a time readout function provides the same value across *two* steps. A monotonic function is one which allows for that. A strictly increasing function is one which does not. Most of the time, just monotonic is okay, but not always. No, the time is only monotone, not strictly monotone. (With discreet values, it is not possible to make it strictly monotone.) You mean discrete. It's impossible to make it strictly monotone in the resolution that is smaller than the smallest unit of time (or one that converges into zero). But anyway, the problem isn't just the monotonicity, it's simply that e.g. with HZ of 250, a jiffie takes 4ms, so if you need to do anything with something that takes a comparable amount of time, you're shit outta luck. and it also caused occasional PostgreSQL errors with tables that had timestamp columns as keys, since it became possible for two independent transactions to come in at the exact same time. Äh, where is documented, that this supposed to work anyway? The key column has a unique constraint and a default value of current timestamp. Even if two perfectly concurrent writers come in to add a new record, it's still logical to expect for them to be serialized to a minimal extent, because the database itself is explicitly instructed to input all values and maintain their uniqueness. The expectation that all updates take at least one minimal unit of time is perhaps not theoretically valid, but it's certainly like that in the real world (every action takes *some* perceivable time). Wrong answer. Where is this documented as working in the postgresql documentation? I have no idea. Why would I need an exact documentation of this use case? The unique and default key parameters, and the definition of the timestamp data type are documented. Indeed, I just checked and the resolution of a timestamp is explicitly documented as 1 microsecond, so if the underlying system has a resolution of 4000 microseconds, that simply precludes it. If you're trying to argue that nobody should be using anything using microseconds because they're not supported by clocksource=jiffies, well, then we might as well cease this pointless discussion. -- 2. That which causes joy or happiness. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225150156.ga...@orion.carnet.hr
Bug#570252: marked as done (linux-image-2.6.32-2-vserver-amd64: unable to boot with blank screen and keyboard frozen)
Your message dated Thu, 25 Feb 2010 15:59:10 +0100 with message-id 20100225145910.gq15...@baikonur.stro.at and subject line Re: Bug#570252: linux-image-2.6.32-2-vserver-amd64: unable to boot with blank screen and keyboard frozen has caused the Debian Bug report #570252, regarding linux-image-2.6.32-2-vserver-amd64: unable to boot with blank screen and keyboard frozen 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.) -- 570252: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=570252 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.32-8 Severity: critical Justification: breaks the whole system grub-pc successfully loads the initrd images. After decrypting the root file system, the boot fails with the screen going blank and system unresponsive (keycap and Ctrl-Alt-Delete have no effect). The last visible line appears to be something related to [drm]. The linux-image-2.6.32-2-amd64 has the same problem. I am able to boot successfully boot using linux-image-2.6.30-2-amd64. -- Package-specific info: ** Kernel log: boot messages should be attached ** Model information sys_vendor: Dell Inc. product_name: Vostro 1500 product_version: chassis_vendor: Dell Inc. chassis_version: bios_vendor: Dell Inc. bios_version: A06 board_vendor: Dell Inc. board_name: 0NX907 board_version: ** PCI devices: 00:00.0 Host bridge [0600]: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub [8086:2a00] (rev 0c) Subsystem: Dell Device [1028:0228] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort+ SERR- PERR- INTx- Latency: 0 Capabilities: access denied Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a02] (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:0228] 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 29 Region 0: Memory at fea0 (64-bit, non-prefetchable) [size=1M] Region 2: Memory at e000 (64-bit, prefetchable) [size=256M] Region 4: I/O ports at eff8 [size=8] Expansion ROM at unassigned [disabled] Capabilities: access denied Kernel driver in use: i915 00:02.1 Display controller [0380]: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller [8086:2a03] (rev 0c) Subsystem: Dell Device [1028:0228] Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Region 0: Memory at feb0 (64-bit, non-prefetchable) [size=1M] Capabilities: access denied 00:1a.0 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 [8086:2834] (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Device [1028:0228] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin A routed to IRQ 20 Region 4: I/O ports at 6f20 [size=32] Kernel driver in use: uhci_hcd 00:1a.1 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 [8086:2835] (rev 02) (prog-if 00 [UHCI]) Subsystem: Dell Device [1028:0228] Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0 Interrupt: pin B routed to IRQ 21 Region 4: I/O ports at 6f00 [size=32] Kernel driver in use: uhci_hcd 00:1a.7 USB Controller [0c03]: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 [8086:283a] (rev 02) (prog-if 20 [EHCI]) Subsystem: Dell Device [1028:0228] Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium TAbort-
Bug#571459: linux-image-2.6.32-2-686: Mount as empty a smb alfresco share, but 2.6.30 do it fine
Package: linux-2.6 Version: 2.6.32-8 Severity: normal Hi, Today I tried to mount a share from alfresco via smbfs. With older linux-image versions (I can test it with 2.6.30 for example): mount -t smbfs //alfresco/share ~/alfresco works fine and ls ~/alfresco show me all my files But with this kernel 2.6.32-8: mount -t smbfs //alfresco/share ~/alfresco seems to work fine but ls ~/alfresco doesn't show me any file and I can't access to them I would try with a newer kernel, but kernel-archive.buildserver.net is down, at least this tell our wiki (w.d.o/DebianKernel) I have too a PDC which samba, and its shares are working when I access to them with the two kernels (2.6.32 and 2.6.30). I'm afraid it could be an alfresco issue :(, but like it works with 2.6.30 kernel version, I'm opening this bug. Thank you very much -- Package-specific info: ** Version: Linux version 2.6.32-2-686 (Debian 2.6.32-8) (b...@decadent.org.uk) (gcc version 4.3.4 (Debian 4.3.4-6) ) #1 SMP Thu Feb 11 04:08:42 UTC 2010 ** Command line: BOOT_IMAGE=/vmlinuz-2.6.32-2-686 root=/dev/mapper/delorian-root ro quiet ** Tainted: P (1) * Proprietary module has been loaded. ** Kernel log: [3.616063] usb 3-1: new full speed USB device using uhci_hcd and address 2 [3.643900] PM: Starting manual resume from disk [3.643905] PM: Resume from partition 254:1 [3.643908] PM: Checking hibernation image. [3.644072] PM: Error -22 checking image file [3.644076] PM: Resume from disk failed. [3.668785] kjournald starting. Commit interval 5 seconds [3.668799] EXT3-fs: mounted filesystem with ordered data mode. [3.762307] usb 3-1: New USB device found, idVendor=047f, idProduct=c001 [3.762314] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0 [3.762439] usb 3-1: configuration #1 chosen from 1 choice [5.065247] udev: starting version 151 [5.375332] ACPI: SSDT 5ffe2b27 00453 (v01 COMPAQ CPU_TM2 0001 MSFT 010E) [5.375765] processor LNXCPU:00: registered as cooling_device0 [5.376043] processor LNXCPU:01: registered as cooling_device1 [5.378574] input: PC Speaker as /devices/platform/pcspkr/input/input3 [5.412751] parport_pc 00:07: reported by Plug and Play ACPI [5.413107] parport0: PC-style at 0x378 (0x778), irq 7 [PCSPP,TRISTATE] [5.493623] ACPI: WMI: Mapper loaded [5.664936] intel_rng: Firmware space is locked read-only. If you can't or [5.664939] intel_rng: don't want to disable this in firmware setup, and if [5.664941] intel_rng: you are certain that your system has a functional [5.664942] intel_rng: RNG, try using the 'no_fwh_detect' option. [5.818603] usbcore: registered new interface driver hiddev [5.822610] input: HID 047f:c001 as /devices/pci:00/:00:1d.1/usb3/3-1/3-1:1.3/input/input4 [5.822715] generic-usb 0003:047F:C001.0001: input,hidraw0: USB HID v1.00 Device [HID 047f:c001] on usb-:00:1d.1-1/input3 [5.822744] usbcore: registered new interface driver usbhid [5.822748] usbhid: v2.6:USB HID core driver [6.149578] input: ImPS/2 Generic Wheel Mouse as /devices/platform/i8042/serio1/input/input5 [6.170870] nvidia: module license 'NVIDIA' taints kernel. [6.170876] Disabling lock debugging due to kernel taint [6.878130] HDA Intel :00:1b.0: PCI INT A - GSI 21 (level, low) - IRQ 21 [6.878163] HDA Intel :00:1b.0: setting latency timer to 64 [6.948782] usbcore: registered new interface driver snd-usb-audio [6.967330] input: HDA Digital PCBeep as /devices/pci:00/:00:1b.0/input/input6 [7.035693] nvidia :01:00.0: PCI INT A - GSI 16 (level, low) - IRQ 16 [7.035703] nvidia :01:00.0: setting latency timer to 64 [7.035927] NVRM: loading NVIDIA UNIX x86 Kernel Module 190.53 Tue Dec 8 18:51:41 PST 2009 [9.354537] EXT3 FS on dm-0, internal journal [9.449650] loop: module loaded [9.480534] smsc47b397: found SMSC SCH5307-NS (base address 0x0480, revision 0) [9.520621] vboxdrv: Trying to deactivate the NMI watchdog permanently... [9.520625] vboxdrv: Successfully done. [9.520628] vboxdrv: Found 2 processor cores. [9.521197] vboxdrv: fAsync=0 offMin=0x915 offMax=0x3480 [9.521255] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. [9.521258] vboxdrv: Successfully loaded version 3.1.4_OSE (interface 0x0011). [ 10.745840] kjournald starting. Commit interval 5 seconds [ 10.746013] EXT3 FS on sda1, internal journal [ 10.746021] EXT3-fs: mounted filesystem with ordered data mode. [ 10.797273] kjournald starting. Commit interval 5 seconds [ 10.797513] EXT3 FS on dm-5, internal journal [ 10.797519] EXT3-fs: mounted filesystem with ordered data mode. [ 10.826649] kjournald starting. Commit interval 5 seconds [ 10.826878] EXT3 FS on dm-2, internal journal [ 10.826885] EXT3-fs: mounted filesystem with ordered data mode. [ 10.844095] kjournald starting. Commit interval 5
Bug#571465: linux-image-2.6.32-2-amd64: Kernel WARNING from wdev_cleanup_work when hibernating
Package: linux-2.6 Version: 2.6.32-8 Severity: normal My laptop hibernated due to low battery last night, and this morning after un-hibernating it I noticed the signs of an oops mentioned in my terminal window. Digging through the kernel log, I found these, one during hibernate and the other during un-hibernate: Feb 25 05:02:10 feather kernel: [42744.419370] [ cut here ] Feb 25 05:02:10 feather kernel: [42744.419393] WARNING: at /build/buildd-linux-2.6_2.6.32-8-amd64-DCxXqz/linux-2.6-2.6.32/debian/build/source_amd64_none/net/wi reless/core.c:614 wdev_cleanup_work+0x49/0xb3 [cfg80211]() Feb 25 05:02:10 feather kernel: [42744.419401] Hardware name: 7454CTO Feb 25 05:02:10 feather kernel: [42744.419404] Modules linked in: iwlagn iwlcore mac80211 cfg80211 ppdev lp parport sco bridge stp btusb bnep rfcomm l2cap crc1 6 bluetooth acpi_cpufreq cpufreq_userspace cpufreq_powersave cpufreq_stats kvm_intel cpufreq_conservative kvm fuse loop snd_hda_codec_conexant arc4 ecb uvcvide o snd_hda_intel snd_hda_codec snd_hwdep snd_pcm videodev snd_seq v4l1_compat snd_timer snd_seq_device v4l2_compat_ioctl32 snd thinkpad_acpi ac led_class batter y nvram psmouse serio_raw rfkill i2c_i801 wmi soundcore evdev snd_page_alloc processor ext3 jbd mbcache sd_mod crc_t10dif ahci uhci_hcd i915 drm_kms_helper ehc i_hcd drm i2c_algo_bit e1000e libata scsi_mod button i2c_core video output usbcore nls_base intel_agp thermal fan thermal_sys [last unloaded: cfg80211] Feb 25 05:02:10 feather kernel: [42744.419547] Pid: 10, comm: events/1 Not tainted 2.6.32-2-amd64 #1 Feb 25 05:02:10 feather kernel: [42744.419552] Call Trace: Feb 25 05:02:10 feather kernel: [42744.419566] [a03e24f7] ? wdev_cleanup_work+0x49/0xb3 [cfg80211] Feb 25 05:02:10 feather kernel: [42744.419579] [a03e24f7] ? wdev_cleanup_work+0x49/0xb3 [cfg80211] Feb 25 05:02:10 feather kernel: [42744.419590] [8104dbe8] ? warn_slowpath_common+0x77/0xa3 Feb 25 05:02:10 feather kernel: [42744.419603] [a03e24f7] ? wdev_cleanup_work+0x49/0xb3 [cfg80211] Feb 25 05:02:10 feather kernel: [42744.419613] [81061473] ? worker_thread+0x188/0x21d Feb 25 05:02:10 feather kernel: [42744.419625] [a03e24ae] ? wdev_cleanup_work+0x0/0xb3 [cfg80211] Feb 25 05:02:10 feather kernel: [42744.419635] [81064a5e] ? autoremove_wake_function+0x0/0x2e Feb 25 05:02:10 feather kernel: [42744.419643] [810612eb] ? worker_thread+0x0/0x21d Feb 25 05:02:10 feather kernel: [42744.419650] [81064791] ? kthread+0x79/0x81 Feb 25 05:02:10 feather kernel: [42744.419660] [81011baa] ? child_rip+0xa/0x20 Feb 25 05:02:10 feather kernel: [42744.419667] [81064718] ? kthread+0x0/0x81 Feb 25 05:02:10 feather kernel: [42744.419674] [81011ba0] ? child_rip+0x0/0x20 Feb 25 05:02:10 feather kernel: [42744.419679] ---[ end trace 240fa69dfbf9d219 ]--- Feb 25 07:22:39 feather kernel: [42747.551961] Restarting tasks ... done. Feb 25 07:22:39 feather kernel: [42747.588358] PM: Basic memory bitmaps freed Feb 25 07:22:40 feather kernel: [42747.627928] BUG: unable to handle kernel NULL pointer dereference at 0020 Feb 25 07:22:40 feather kernel: [42747.627935] IP: [8113d11e] sysfs_open_file+0x33/0x2aa Feb 25 07:22:40 feather kernel: [42747.627945] PGD 123283067 PUD 123282067 PMD 0 Feb 25 07:22:40 feather kernel: [42747.627950] Oops: [#1] SMP Feb 25 07:22:40 feather kernel: [42747.627954] last sysfs file: /sys/devices/virtual/bdi/7:6/uevent Feb 25 07:22:40 feather kernel: [42747.627957] CPU 0 Feb 25 07:22:40 feather kernel: [42747.627959] Modules linked in: iwlagn iwlcore mac80211 cfg80211 ppdev lp parport sco bridge stp btusb bnep rfcomm l2cap crc16 bluetooth acpi_cpufreq cpufreq_userspace cpufreq_powersave cpufreq_stats kvm_intel cpufreq_conservative kvm fuse loop snd_hda_codec_conexant arc4 ecb uvcvideo snd_hda_intel snd_hda_codec snd_hwdep snd_pcm videodev snd_seq v4l1_compat snd_timer snd_seq_device v4l2_compat_ioctl32 snd thinkpad_acpi ac led_class battery nvram psmouse serio_raw rfkill i2c_i801 wmi soundcore evdev snd_page_alloc processor ext3 jbd mbcache sd_mod crc_t10dif ahci uhci_hcd i915 drm_kms_helper ehci_hcd drm i2c_algo_bit e1000e libata scsi_mod button i2c_core video output usbcore nls_base intel_agp thermal fan thermal_sys [last unloaded: cfg80211] Feb 25 07:22:40 feather kernel: [42747.628006] Pid: 5535, comm: udev-acl.ck Tainted: GW 2.6.32-2-amd64 #1 7454CTO Feb 25 07:22:40 feather kernel: [42747.628006] RIP: 0010:[8113d11e] [8113d11e] sysfs_open_file+0x33/0x2aa Feb 25 07:22:40 feather kernel: [42747.628006] RSP: 0018:880139cadd78 EFLAGS: 00010296 Feb 25 07:22:40 feather kernel: [42747.628006] RAX: RBX: RCX: 88013abe79c0 Feb 25 07:22:40 feather kernel: [42747.628006] RDX: 1000 RSI: 816410d0 RDI: 88013abe79d0 Feb 25 07:22:40 feather
Bug#533903: initramfs-tools: support different compression tools in mkinitramfs
Hello Maximilian, maximilian attems (Tue, Feb 23, 2010 at 12:00:14AM +0100): [..] hmm there i'm not sure that it is update-initramfs job. I'd prefer to have it in /etc/initramfs-tools/initramfs.conf and have mkinitramfs deal directly with it. then you also don't have to take care about the arg passing. update-initramfs has not many arguments and thus tries to stay user friendly. mkinitramfs is the low level interface. [..] would you care to rediff that according to aboves comment, to deal with it in mkinitramfs? also just fall back on current default if the input is undefined or strange of tha config option. [..] yeah thats no problem at all, I just grabbed the 2.6.33 sources and theres LZO support as well. Will rediff it ths weekend and let mkinitramfs do the job instead. best regards Bert Schulze -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225162942.ga4...@m.home
Bug#571305: Swarm does not boot on .32 anymore.
Sebastian Andrzej Siewior wrote: Package: linux-image-2.6.32-9-sb1-bcm91250a Version: 2.6.32-5 Severity: serious Tags: patch fixed-upstream Swarm will hang during boot and all you see is: |[0.00] Primary data cache 32kB, 4-way, PIPT, no aliases, linesize 32 bytes |*Exception 32: EPC=8069E50C, Cause=00809034 (TrapExc ) |RA=8069E498, VAddr=20022038 | |0 ($00) = AT ($01) = |v0 ($02) = 0001 v1 ($03) = 0080 |a0 ($04) = 806AD5D8 a1 ($05) = 0003 |a2 ($06) = 0080 a3 ($07) = 806ACC5C |t0 ($08) = 806ADE50 t1 ($09) = 806B |t2 ($10) = 80633DB0 t3 ($11) = A000 |t4 ($12) = t5 ($13) = 8010583C |t6 ($14) = 80633B60 t7 ($15) = 0020 |s0 ($16) = 806ACBD0 s1 ($17) = 806A |s2 ($18) = 806ACBD0 s3 ($19) = 806B |s4 ($20) = 806B s5 ($21) = 806B |s6 ($22) = 806ACDD0 s7 ($23) = 806AD5D0 |t8 ($24) = 0003 t9 ($25) = 8069F910 |k0 ($26) = 806E55DC k1 ($27) = 000F |gp ($28) = 8063 sp ($29) = 80633DA0 |fp ($30) = 80633DB0 ra ($31) = 8069E498 | Some register may vary :) I consider 2.6.32-9 as not fixed because I don't see the following patch there which is upstream commit abbdc3d aka (MIPS: Cleanup forgotten label_module_alloc in tlbex.c). Sebastian [Adding sta...@kernel.org to CC] Greg, please merge abbdc3d88aa2d5c937b21044c336bcd056c1732f into the next 2.6.32.x update round. Original report in the Debian BTS: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571305 Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225163150.ga23...@inutil.org
Bug#567204: marked as done (linux-image-686-bigmem: serious filesystem corruption with bigmem kernels)
Your message dated Thu, 25 Feb 2010 17:56:07 +0100 with message-id 20100225165607.ga2...@galadriel.inutil.org and subject line Re: Bug#567204: serious filesystem corruption with bigmem kernels has caused the Debian Bug report #567204, regarding linux-image-686-bigmem: serious filesystem corruption with bigmem kernels 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.) -- 567204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=567204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-686-bigmem Severity: grave Justification: renders package unusable my system had serious filesystem corruption with several -bigmem kernel in the past (from 2.6.28 to 2.6.32). git first discovered the problem because it complained about corruption in the repo. a filesystem check found lots of double allocated blocks and other problems. i use a ext3 filesystem. i first thought its related to suspend/resume so i didn't suspend anymore - file corruption still occured. so i switched from a -bigmem kernel to a normal kernel with same version and even after heavy usage (cross compile openwrt) no corruption was found. for sure i can't guarantee that this isn't related to some hardware fault like broken ram or the like but i checked ram with memtest86+. please adjust Severity and/or Justification if i choosed that wrong. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-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/bash ---End Message--- ---BeginMessage--- On Thu, Feb 25, 2010 at 11:30:38AM +0100, M. Dietrich wrote: On Thu, Feb 18, 2010 at 01:21:22AM +, Ben Hutchings wrote: On Mon, 2010-02-01 at 15:55 +0100, M. Dietrich wrote: Package: linux-image-686-bigmem Severity: normal i started a reportbug run with the real kernel name. this is the outcome: I can't see any obvious suspect here. Therefore, please file a bug report upstream at http://bugzilla.kernel.org, selecting product 'Platform Specific/Hardware', component 'i386', and providing the same information in your report here. Let us know the bug number so we can track it. close the bug i encountered file system corruption with a non-bigmem kernel today i don't now what's going on will now check the hd Ok, closing. Cheers, Moritz ---End Message---
Bug#533903: initramfs-tools: support different compression tools in mkinitramfs
hello Bert, On Thu, Feb 25, 2010 at 05:29:42PM +0100, bert schulze wrote: yeah thats no problem at all, I just grabbed the 2.6.33 sources and theres LZO support as well. Will rediff it ths weekend and let mkinitramfs do the job instead. cool, beware that initramfs-tools saw a bit of activity lately, so please patch against latest git and not 0.93.4 http://git.debian.org/?p=kernel/initramfs-tools.git;a=summary git clone git://git.debian.org/kernel/initramfs-tools.git thanks -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225163255.gr15...@baikonur.stro.at
Processed: Re: [linux-image-2.6.26-1-amd64] report_bad_irq (while in screensaver)
Processing commands for cont...@bugs.debian.org: tags 518046 moreinfo Bug #518046 [linux-2.6] [linux-image-2.6.26-1-amd64] report_bad_irq (while in screensaver) Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126712097728357.transcr...@bugs.debian.org
Bug#520667: linux-image-2.6.26-1-686: No warning when half-open TCP queue is full
On Thu, 25 Feb 2010, Olaf van der Spek wrote: On Thu, Feb 25, 2010 at 7:09 PM, Moritz Muehlenhoff j...@inutil.org wrote: On Sat, Mar 21, 2009 at 07:47:36PM +0100, Olaf van der Spek wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-13lenny2 Severity: normal Hi, When the half-open TCP connection queue is full and syn cookies are enabled, you get a message like kernel: possible SYN flooding on port 2710. Sending cookies. However when syn cookies are disabled, you don't get any message (in kern.log), although connections to your server are timing out. Could such a message be added? Maybe with a suggestion to increase the size of that queue or to enable syn cookies. That should be discussed with the upstream developers, the Debian BTS is not the best way to change this. You can reach them at linux-...@vger.kernel.org Hi Linux net devs, See this issue reported in the Debian BTS. Wrong list. You want linux-netdev. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.lnx.4.64.1002251352260.8...@e-smith.charlieb.ott.istop.com
Bug#521944: linux-image-2.6.29-1-686: Excessive number of interrupts from hrtimer_start_expires
On 25 February 2010 18:15, Moritz Muehlenhoff j...@inutil.org wrote: Did you report this at http://bugzilla.kernel.org ? Haven't yet. Somewhere on the todo list... Tom -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/243a9cc1002251016ya4a1e22oa2b84d229aab0...@mail.gmail.com
Processed: Re: Confirmation
Processing commands for cont...@bugs.debian.org: tags 536594 moreinfo Bug #536594 [linux-2.6] linux-image-2.6.30-1-686: PCMCIA failure Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126712278920250.transcr...@bugs.debian.org
Bug#520667: linux-image-2.6.26-1-686: No warning when half-open TCP queue is full
On Sat, Mar 21, 2009 at 07:47:36PM +0100, Olaf van der Spek wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-13lenny2 Severity: normal Hi, When the half-open TCP connection queue is full and syn cookies are enabled, you get a message like kernel: possible SYN flooding on port 2710. Sending cookies. However when syn cookies are disabled, you don't get any message (in kern.log), although connections to your server are timing out. Could such a message be added? Maybe with a suggestion to increase the size of that queue or to enable syn cookies. That should be discussed with the upstream developers, the Debian BTS is not the best way to change this. You can reach them at linux-...@vger.kernel.org Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225180939.ga3...@galadriel.inutil.org
Bug#521548: linux-image-2.6.29-1-amd64: laptop toshiba qosmio g30 fails to boot with 2.6.28 and 2.6.29 kernels)
On Sat, Feb 13, 2010 at 08:13:54PM +0100, maximilian attems wrote: On Sat, Feb 13, 2010 at 06:40:09PM +0100, Fathi Boudra wrote: aboves is again zero info. so please pin down which script is faulty in runlevel 2, come on I'd expect a bit more from a debian dev then a casual user. now that you have removed hal, should be one less to check ;) it's kvm. I removed kvm and kvm-source package and successfully boot with 2.6.32. reassign ? no please report upstream that loading kvm modules hang your box on bugzilla.kernel.org and let us know the bug nr so that we can track it. upstream will probably need your 2.6.32 dmesg and you can mention since which kernel version aboves happens. thanks for your feedback. Did you report this upstream? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225181231.ga4...@galadriel.inutil.org
Processed: Re: 2.6.26.8 and hpet=force works
Processing commands for cont...@bugs.debian.org: tags 521615 moreinfo Bug #521615 [linux-2.6] linux-image-2.6.26-1-686: Clock hangs for exactly 300 seconds Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.12671216634122.transcr...@bugs.debian.org
Bug#520667: linux-image-2.6.26-1-686: No warning when half-open TCP queue is full
On Thu, Feb 25, 2010 at 7:52 PM, Charlie Brady charl...@budge.apana.org.au wrote: On Thu, 25 Feb 2010, Olaf van der Spek wrote: On Thu, Feb 25, 2010 at 7:09 PM, Moritz Muehlenhoff j...@inutil.org wrote: On Sat, Mar 21, 2009 at 07:47:36PM +0100, Olaf van der Spek wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-13lenny2 Severity: normal Hi, When the half-open TCP connection queue is full and syn cookies are enabled, you get a message like kernel: possible SYN flooding on port 2710. Sending cookies. However when syn cookies are disabled, you don't get any message (in kern.log), although connections to your server are timing out. Could such a message be added? Maybe with a suggestion to increase the size of that queue or to enable syn cookies. That should be discussed with the upstream developers, the Debian BTS is not the best way to change this. You can reach them at linux-...@vger.kernel.org Hi Linux net devs, See this issue reported in the Debian BTS. Wrong list. You want linux-netdev. Oops, trying again. Olaf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/b2cc26e41002251055q5510a733j261e4a8af8eda...@mail.gmail.com
linux-2.6_2.6.33-1~experimental.1_amd64.changes ACCEPTED
Accepted: firmware-linux-free_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.33-1~experimental.1_all.deb linux-2.6_2.6.33-1~experimental.1.diff.gz to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.1.diff.gz linux-2.6_2.6.33-1~experimental.1.dsc to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.1.dsc linux-2.6_2.6.33.orig.tar.gz to main/l/linux-2.6/linux-2.6_2.6.33.orig.tar.gz linux-base_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-base_2.6.33-1~experimental.1_all.deb linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb linux-headers-2.6.33-2-common_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.33-2-common_2.6.33-1~experimental.1_amd64.deb linux-image-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb linux-libc-dev_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.33-1~experimental.1_amd64.deb linux-manual-2.6.33_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-manual-2.6.33_2.6.33-1~experimental.1_all.deb linux-patch-debian-2.6.33_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.33_2.6.33-1~experimental.1_all.deb linux-source-2.6.33_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.33_2.6.33-1~experimental.1_all.deb linux-support-2.6.33-2_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-support-2.6.33-2_2.6.33-1~experimental.1_all.deb Override entries for your package: firmware-linux-free_2.6.33-1~experimental.1_all.deb - optional kernel linux-2.6_2.6.33-1~experimental.1.dsc - source devel linux-base_2.6.33-1~experimental.1_all.deb - optional kernel linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb - optional doc linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb - optional kernel linux-headers-2.6.33-2-common_2.6.33-1~experimental.1_amd64.deb - optional kernel linux-image-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb - optional kernel linux-libc-dev_2.6.33-1~experimental.1_amd64.deb - optional devel linux-manual-2.6.33_2.6.33-1~experimental.1_all.deb - optional doc linux-patch-debian-2.6.33_2.6.33-1~experimental.1_all.deb - optional kernel linux-source-2.6.33_2.6.33-1~experimental.1_all.deb - optional kernel linux-support-2.6.33-2_2.6.33-1~experimental.1_all.deb - optional devel Announcing to debian-devel-chan...@lists.debian.org Closing bugs: 444182 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/e1nkj4j-0001sr...@ries.debian.org
Bug#521080: marked as done (base: Error installing bay notify handler)
Your message dated Thu, 25 Feb 2010 19:10:35 +0100 with message-id 20100225181035.ga4...@galadriel.inutil.org and subject line Re: base: Error installing bay notify handler has caused the Debian Bug report #521080, regarding base: Error installing bay notify handler 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.) -- 521080: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521080 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: base Severity: normal The bay notify handler fails to install on my IBM T61 7662-CTO the battery installed in the bay appears to be functioning as a battery but is not identified by ACPI and as such is not displayed in battery utilities. $dmesg|grep -i acpi [0.00] BIOS-e820: 7deb - 7decc000 (ACPI data) [0.00] BIOS-e820: 7decc000 - 7df0 (ACPI NVS) [0.00] ACPI: RSDP 000F68D0, 0024 (r2 LENOVO) [0.00] ACPI: XSDT 7DEBB77F, 009C (r1 LENOVO TP-7L2190 LTP 0) [0.00] ACPI: FACP 7DEBB900, 00F4 (r3 LENOVO TP-7L2190 LNVO 1) [0.00] ACPI Warning (tbfadt-0442): Optional field Gpe1Block has zero address or length: 102C/0 [20080321] [0.00] ACPI: DSDT 7DEBBD1D, FED1 (r1 LENOVO TP-7L2190 MSFT 300) [0.00] ACPI: FACS 7DEE4000, 0040 [0.00] ACPI: SSDT 7DEBBAB4, 0269 (r1 LENOVO TP-7L2190 MSFT 300) [0.00] ACPI: ECDT 7DECBBEE, 0052 (r1 LENOVO TP-7L2190 LNVO 1) [0.00] ACPI: TCPA 7DECBC40, 0032 (r2 LENOVO TP-7L2190 LNVO 1) [0.00] ACPI: APIC 7DECBC72, 0068 (r1 LENOVO TP-7L2190 LNVO 1) [0.00] ACPI: MCFG 7DECBCDA, 003C (r1 LENOVO TP-7L2190 LNVO 1) [0.00] ACPI: HPET 7DECBD16, 0038 (r1 LENOVO TP-7L2190 LNVO 1) [0.00] ACPI: SLIC 7DECBDF0, 0176 (r1 LENOVO TP-7L2190 LTP 0) [0.00] ACPI: BOOT 7DECBF66, 0028 (r1 LENOVO TP-7L2190 LTP 1) [0.00] ACPI: ASF! 7DECBF8E, 0072 (r16 LENOVO TP-7L2190 PTL 1) [0.00] ACPI: SSDT 7DEE26D9, 025F (r1 LENOVO TP-7L2190 INTL 20050513) [0.00] ACPI: SSDT 7DEE2938, 00A6 (r1 LENOVO TP-7L2190 INTL 20050513) [0.00] ACPI: SSDT 7DEE29DE, 04F7 (r1 LENOVO TP-7L2190 INTL 20050513) [0.00] ACPI: SSDT 7DEE2ED5, 08BD (r1 LENOVO TP-7L2190 INTL 20050513) [0.00] ACPI: SSDT 7DEE3792, 069C (r1 LENOVO TP-7L2190 INTL 20050513) [0.00] ACPI: DMI detected: Lenovo ThinkPad T61 [0.00] ACPI: Added _OSI(Linux) [0.00] ACPI: PM-Timer IO Port: 0x1008 [0.00] ACPI: Local APIC address 0xfee0 [0.00] ACPI: LAPIC (acpi_id[0x00] lapic_id[0x00] enabled) [0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x01] enabled) [0.00] ACPI: LAPIC_NMI (acpi_id[0x00] high edge lint[0x1]) [0.00] ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1]) [0.00] ACPI: IOAPIC (id[0x01] address[0xfec0] gsi_base[0]) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl) [0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level) [0.00] ACPI: IRQ0 used by override. [0.00] ACPI: IRQ2 used by override. [0.00] ACPI: IRQ9 used by override. [0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0 [0.00] Using ACPI (MADT) for SMP configuration information [0.084005] ACPI: Core revision 20080321 [0.248015] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it [0.248015] ACPI: bus type pci registered [0.252015] ACPI: EC: EC description table is found, configuring boot EC [0.260016] ACPI: BIOS _OSI(Linux) query honored via DMI [0.260016] ACPI: EC: non-query interrupt received, switching to interrupt mode [0.287622] ACPI: Interpreter enabled [0.287625] ACPI: (supports S0 S3 S4 S5) [0.287642] ACPI: Using IOAPIC for interrupt routing [0.309851] ACPI: EC: GPE = 0x12, I/O: command/status = 0x66, data = 0x62 [0.309851] ACPI: EC: driver started in interrupt mode [0.309851] ACPI: PCI Root Bridge [PCI0] (:00) [0.309851] pci :00:1f.0: quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO [0.311715] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT] [0.312051] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.AGP_._PRT] [0.312191] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP0._PRT] [0.312344] ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT] [
Bug#535959: marked as done (linux-2.6: Please enable libata for PATA/piix)
Your message dated Thu, 25 Feb 2010 19:08:15 + with message-id e1nkj4j-0001sx...@ries.debian.org and subject line Bug#444182: fixed in linux-2.6 2.6.33-1~experimental.1 has caused the Debian Bug report #444182, regarding linux-2.6: Please enable libata for PATA/piix 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.) -- 444182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444182 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Severity: normal Hi, currently the Debian linux package explicitly disables libata for ata_piix via debian/patches/debian/drivers-ata-ata_piix-postpone-pata.patch. which means that the old IDE subsystem is used for this chipset. I'd like to see this patch removed, so libata is used by default. Cheers, Michael -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.30-1-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: linux-2.6 Source-Version: 2.6.33-1~experimental.1 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: firmware-linux-free_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/firmware-linux-free_2.6.33-1~experimental.1_all.deb linux-2.6_2.6.33-1~experimental.1.diff.gz to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.1.diff.gz linux-2.6_2.6.33-1~experimental.1.dsc to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.1.dsc linux-2.6_2.6.33.orig.tar.gz to main/l/linux-2.6/linux-2.6_2.6.33.orig.tar.gz linux-base_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-base_2.6.33-1~experimental.1_all.deb linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb linux-headers-2.6.33-2-common_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-headers-2.6.33-2-common_2.6.33-1~experimental.1_amd64.deb linux-image-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-image-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb linux-libc-dev_2.6.33-1~experimental.1_amd64.deb to main/l/linux-2.6/linux-libc-dev_2.6.33-1~experimental.1_amd64.deb linux-manual-2.6.33_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-manual-2.6.33_2.6.33-1~experimental.1_all.deb linux-patch-debian-2.6.33_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-patch-debian-2.6.33_2.6.33-1~experimental.1_all.deb linux-source-2.6.33_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-source-2.6.33_2.6.33-1~experimental.1_all.deb linux-support-2.6.33-2_2.6.33-1~experimental.1_all.deb to main/l/linux-2.6/linux-support-2.6.33-2_2.6.33-1~experimental.1_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 444...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. maximilian attems m...@debian.org (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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 25 Feb 2010 15:21:38 +0100 Source: linux-2.6 Binary: linux-source-2.6.33 linux-doc-2.6.33 linux-manual-2.6.33 linux-patch-debian-2.6.33 firmware-linux-free linux-support-2.6.33-2 linux-base linux-libc-dev linux-headers-2.6.33-2-all linux-headers-2.6.33-2-all-alpha linux-headers-2.6.33-2-common linux-image-2.6.33-2-alpha-generic linux-headers-2.6.33-2-alpha-generic linux-image-2.6.33-2-alpha-smp linux-headers-2.6.33-2-alpha-smp linux-image-2.6.33-2-alpha-legacy linux-headers-2.6.33-2-alpha-legacy linux-headers-2.6.33-2-all-amd64 linux-image-2.6.33-2-amd64
Bug#536413: marked as done (linux-libc-dev: fails on upgrade)
Your message dated Thu, 25 Feb 2010 19:30:57 +0100 with message-id 20100225183057.ga7...@galadriel.inutil.org and subject line Re: Bug#536413: linux-libc-dev: fails on upgrade has caused the Debian Bug report #536413, regarding linux-libc-dev: fails on upgrade 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.) -- 536413: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=536413 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-libc-dev Version: 2.6.30-1 Severity: normal Preparing to replace linux-libc-dev 2.6.30-1 (using .../linux-libc-dev_2.6.31~rc2-1~experimental.1~snapshot.13905_i386.deb) ... Unpacking replacement linux-libc-dev ... dpkg: error processing /var/cache/apt/archives/linux-libc-dev_2.6.31~rc2-1~experimental.1~snapshot.13905_i386.deb (--unpack): trying to overwrite `/usr/include/scsi/scsi.h', which is also in package libc6-dev dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/linux-libc-dev_2.6.31~rc2-1~experimental.1~snapshot.13905_i386.deb E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: -- 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-bigmem (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash -- no debconf information ---End Message--- ---BeginMessage--- On Thu, Jul 09, 2009 at 10:54:18PM +0100, Ben Hutchings wrote: On Thu, 2009-07-09 at 18:50 +0100, Ben Whyte wrote: Package: linux-libc-dev Version: 2.6.30-1 Not this version. Severity: normal Preparing to replace linux-libc-dev 2.6.30-1 (using .../linux-libc-dev_2.6.31~rc2-1~experimental.1~snapshot.13905_i386.deb) ... Unpacking replacement linux-libc-dev ... dpkg: error processing /var/cache/apt/archives/linux-libc-dev_2.6.31~rc2-1~experimental.1~snapshot.13905_i386.deb (--unpack): trying to overwrite `/usr/include/scsi/scsi.h', which is also in package libc6-dev [...] This is a known problem with 2.6.31-rc2 and it is likely to be resolved upstream before 2.6.31. Should be fixed, closing. Cheers, Moritz ---End Message---
Bug#565696: initramfs-tools: Support for AoE
That sounds like a better idea. I'll try to set up an iSCSI root VM as well. Cheers, C.J. On Thu, 2010-02-25 at 18:22 +0100, maximilian attems wrote: On Wed, 24 Feb 2010, C.J. Adams-Collier wrote: Yeah, I have some revisions. I don't want that version going in to an official repository. Mostly I wanted to open a dialogue. cool. I'm using the modified version in order to build an initrd for use in a KVM virtual server. I did a write-up: http://wp.colliertech.org/cj/?p=678 Basically, the idea is to make it possible to do diskless virtual machines with a minimum of fuss. I can't think of any easy way to make all the moving parts fit together. I'm wrapping up an unrelated project at work, but I expect I'll have a bit more time to poke at this in the near future. well i could ship it in examples section then AoE people would just have to copy over or you could add it to a special aoe package. iscsi or such seems in wider use, thus higher priority, don't know if exerternal package does provide some boot scripts. kind regards signature.asc Description: This is a digitally signed message part
Bug#521944: linux-image-2.6.29-1-686: Excessive number of interrupts from hrtimer_start_expires
On Tue, Feb 16, 2010 at 04:46:31AM +, Ben Hutchings wrote:
On Sat, 2010-02-06 at 09:31 +, Tom Parker wrote:
On 2 February 2010 21:16, maximilian attems m...@stro.at wrote:
Squeeze will release with 2.6.32 can anyone of you still
reproduce this?
also please make sure to use latest powertop, aka
ii powertop 1.13~pre201001 Linux tool to find out what is using
power
palf...@drone:[~] dpkg -l |grep powertop
ii powertop 1.13~pre20100125-1
Linux tool to find out what is using power
o
palf...@drone:[~] uname -a
Linux drone 2.6.32-1-686 #1 SMP Mon Feb 1 01:37:26 UTC 2010 i686 GNU/Linux
Attached is powertop.log ('powertop -d') and top.log('top -b -n 1')
As you can see, the major wakeup is still Load balancing tick, which
I'm guessing is a translated name for hrtimer_start_expires? I think
the ACPI estimate of 1.1W is a little off though...
hrtimer_start_expires() is a generic function in the kernel to schedule
a wakeup by the high-resolution timer. In 2.6.32 it is an inline
function that calls hrtimer_start_range_ns(). Powertop recognises and
relabels some specific calling sequences, including this one.
If I understand correctly, these are scheduler ticks that periodically
interrupt the running task (preemption). However, on a kernel compiled
with the NOHZ option (as Debian's kernel images are) this should never
wake the system up - scheduler ticks are disabled when there are no
tasks ready to run and no other timers due to expire before the next
tick.
I can only suggest you report this upstream at
http://bugzilla.kernel.org. Use product 'Process Management',
component 'Scheduler'. Let us know the bug number so we can track it.
Did you report this at http://bugzilla.kernel.org ?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100225181542.ga5...@galadriel.inutil.org
Bug#521135: marked as done (BUG: unable to handle kernel NULL pointer dereference at 00000054)
Your message dated Thu, 25 Feb 2010 19:11:16 +0100 with message-id 20100225181116.ga4...@galadriel.inutil.org and subject line Re: Bug#521135: BUG: unable to handle kernel NULL pointer dereference at 0054 has caused the Debian Bug report #521135, regarding BUG: unable to handle kernel NULL pointer dereference at 0054 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.) -- 521135: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=521135 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.28-1-686 Version: 2.6.28-1 Severity: normal Hello, The rfcomm module induced a kernel BUG when booting. This is the first time it happened, so I don't know precisely what triggered it on this particular boot. --Joe Mar 24 22:37:11 wakko hcid[3727]: Bluetooth HCI daemon Mar 24 22:37:11 wakko hcid[3727]: Parsing /etc/bluetooth/main.conf failed: No such file or directory Mar 24 22:37:11 wakko hcid[3727]: Starting SDP server Mar 24 22:37:11 wakko kernel: [ 72.998994] Bluetooth: L2CAP ver 2.11 Mar 24 22:37:11 wakko kernel: [ 73.00] Bluetooth: L2CAP socket layer initialized Mar 24 22:37:11 wakko kernel: [ 73.057972] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 Mar 24 22:37:11 wakko hidd[3740]: Bluetooth HID daemon Mar 24 22:37:11 wakko kernel: [ 73.088431] usbcore: registered new interface driver hiddev Mar 24 22:37:11 wakko kernel: [ 73.099734] usbcore: registered new interface driver usbhid Mar 24 22:37:11 wakko kernel: [ 73.110965] usbhid: v2.6:USB HID core driver Mar 24 22:37:11 wakko hcid[3727]: Unix socket created: 11 Mar 24 22:37:11 wakko modprobe: FATAL: Error inserting hid_dummy (/lib/modules/2.6.28-1-686/kernel/drivers/hid/hid-dummy.ko): Input/output error Mar 24 22:37:12 wakko kernel: [ 73.359053] Bluetooth: RFCOMM socket layer initialized Mar 24 22:37:12 wakko kernel: [ 73.361564] BUG: unable to handle kernel NULL pointer dereference at 0054 Mar 24 22:37:12 wakko kernel: [ 73.361570] IP: [c0241e37] tty_register_device+0xe/0xb9 Mar 24 22:37:12 wakko kernel: [ 73.361583] *pde = Mar 24 22:37:12 wakko kernel: [ 73.361589] Oops: [#1] SMP Mar 24 22:37:12 wakko kernel: [ 73.361593] last sysfs file: /sys/module/l2cap/initstate Mar 24 22:37:12 wakko kernel: [ 73.361598] Dumping ftrace buffer: Mar 24 22:37:12 wakko kernel: [ 73.361603](ftrace buffer empty) Mar 24 22:37:12 wakko kernel: [ 73.361605] Modules linked in: rfcomm(+) hid_dell hid_pl hid_cypress hid_zpff hid_gyration hid_bright hid_sony hid_samsung hid_microsoft hid_tmff hid_monterey hid_ezkey hid_apple hid_a4tech hid_logitech usbhid ff_memless hid_cherry hid_sunplus hid_petalynx hid_belkin hid_chicony hidp hid l2cap binfmt_misc autofs4 ipv6 fuse nls_utf8 ntfs nls_base snd_seq_dummy snd_seq_oss snd_seq_midi snd_rawmidi snd_seq_midi_event snd_seq snd_seq_device firewire_sbp2 loop pcmcia thinkpad_acpi rfkill nvram arc4 ecb serio_raw pcspkr evdev psmouse i2c_i801 i2c_core ath5k iTCO_wdt mac80211 yenta_socket rsrc_nonstatic pcmcia_core led_class cfg80211 ac battery btusb bluetooth video output snd_hda_intel snd_pcm_oss snd_mixer_oss snd_pcm intel_agp wmi snd_timer button agpgart snd soundcore snd_page_alloc ext3 jbd mbcache dm_mirror dm_region_hash dm_log dm_snapshot dm_mod ide_cd_mod cdrom uhci_hcd ata_generic sd_mod crc_t10dif ide_pci_generic ahci piix libata scsi_mod firewire_ohci ide_core firewire_core Mar 24 22:37:12 wakko kernel: crc_itu_t ehci_hcd usbcore e1000e thermal processor fan thermal_sys Mar 24 22:37:12 wakko kernel: [ 73.361724] Mar 24 22:37:12 wakko kernel: [ 73.361729] Pid: 3797, comm: rfcomm Not tainted (2.6.28-1-686 #1) 7658CTO Mar 24 22:37:12 wakko kernel: [ 73.361734] EIP: 0060:[c0241e37] EFLAGS: 00010286 CPU: 1 Mar 24 22:37:12 wakko kernel: [ 73.361740] EIP is at tty_register_device+0xe/0xb9 Mar 24 22:37:12 wakko kernel: [ 73.361744] EAX: EBX: ECX: EDX: Mar 24 22:37:12 wakko kernel: [ 73.361748] ESI: f6a8b440 EDI: EBP: f57050c0 ESP: f573fe74 Mar 24 22:37:12 wakko kernel: [ 73.361752] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 Mar 24 22:37:12 wakko kernel: [ 73.361757] Process rfcomm (pid: 3797, ti=f573e000 task=f6b08ac0 task.ti=f573e000) Mar 24 22:37:12 wakko kernel: [ 73.361760] Stack: Mar 24 22:37:12 wakko kernel: [ 73.361762] 0003 f6b08ac0 000c Mar 24 22:37:12 wakko kernel: [ 73.361771] f899b69c f6a8b440 ffe9 f57050c0 Mar 24 22:37:12 wakko
Bug#518046: [linux-image-2.6.26-1-amd64] report_bad_irq (while in screensaver)
tags 518046 moreinfo thanks On Tue, Mar 03, 2009 at 10:05:15PM +0200, Nadav Kavalerchik wrote: Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-13 Severity: normal --- Please enter the report below this line. --- recently, ever time i get back to the computer which is in screensaver mode and i get this error in the /var/log/messages : kernel: [12466.291495] Pid: 0, comm: swapper Tainted: P 2.6.26-1- amd64 #1 kernel: [12466.291495] kernel: [12466.291495] Call Trace: kernel: [12466.291495] IRQ [8026c6c3] __report_bad_irq+0x30/0x72 kernel: [12466.291495] [8026c902] note_interrupt+0x1fd/0x23b kernel: [12466.291495] [8026d18b] handle_fasteoi_irq+0xa5/0xc8 kernel: [12466.291495] [8020f5e4] do_IRQ+0x6d/0xd9 kernel: [12466.291495] [8020c46d] ret_from_intr+0x0/0x19 kernel: [12466.291495] EOI [a006e26d] :processor:acpi_idle_enter_bm+0x2b3/0x327 kernel: [12466.291495] [803aa0e4] cpuidle_idle_call+0x7a/0xb2 kernel: [12466.291495] [803aa06a] cpuidle_idle_call+0x0/0xb2 kernel: [12466.291495] [8020ac79] cpu_idle+0x89/0xb3 kernel: [12466.291495] system seems functional but maybe i am missing something ? Does this also occur without the closed source kernel module loaded? Can you try with a current kernel? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225180243.ga2...@galadriel.inutil.org
Bug#521615: 2.6.26.8 and hpet=force works
tags 521615 moreinfo thanks On Mon, Mar 30, 2009 at 11:49:27PM +0200, Henrik wrote: Hello Maximilian, it has to be a debian patch which messes up my system time. I'll figure out some patches of the patchset next days. These snapshots are a great deal (thx), but I first want to find out whats up with this bug. If it can be fixed in Lenny that would be a great thing for many laptop users. Watch out for this network-bug in 2.6.29 which is atm is only fixed in git. This makes ping localhost fail :-O Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225181412.ga4...@galadriel.inutil.org
Processed: Re: Netdev watchdog timeout
Processing commands for cont...@bugs.debian.org: tags 519292 moreinfo Bug #519292 [linux-source-2.6.26] Netdev watchdog timeout Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.12671210806697.transcr...@bugs.debian.org
Bug#536183: Can't change CPU scaling governor after .29 to .30 upgrade.
tags 536183 moreinfo thanks On Wed, Jul 08, 2009 at 12:16:58PM +1000, Trent W. Buck wrote: Package: linux-image-2.6.30-1-686 Version: 2.6.30-1 Severity: normal After upgrading from .29 to .30, I can no longer change my CPU frequency scaling governor: # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_governors ondemand performance # printf ondemand /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor # cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor performance This is super annoying. I am using an EeePC 701 with a Celeron CPU. Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225182743.ga6...@galadriel.inutil.org
Bug#520667: linux-image-2.6.26-1-686: No warning when half-open TCP queue is full
On Thu, Feb 25, 2010 at 7:09 PM, Moritz Muehlenhoff j...@inutil.org wrote: On Sat, Mar 21, 2009 at 07:47:36PM +0100, Olaf van der Spek wrote: Package: linux-image-2.6.26-1-686 Version: 2.6.26-13lenny2 Severity: normal Hi, When the half-open TCP connection queue is full and syn cookies are enabled, you get a message like kernel: possible SYN flooding on port 2710. Sending cookies. However when syn cookies are disabled, you don't get any message (in kern.log), although connections to your server are timing out. Could such a message be added? Maybe with a suggestion to increase the size of that queue or to enable syn cookies. That should be discussed with the upstream developers, the Debian BTS is not the best way to change this. You can reach them at linux-...@vger.kernel.org Hi Linux net devs, See this issue reported in the Debian BTS. Olaf -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/b2cc26e41002251043r6cdf1134ic39f6abae...@mail.gmail.com
Bug#463833: marked as done (SantaRosa PATA don't managed by ata_piix)
Your message dated Thu, 25 Feb 2010 19:08:15 +
with message-id e1nkj4j-0001sx...@ries.debian.org
and subject line Bug#444182: fixed in linux-2.6 2.6.33-1~experimental.1
has caused the Debian Bug report #444182,
regarding SantaRosa PATA don't managed by ata_piix
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.)
--
444182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Package: linux-image-2.6.24-1-amd64
Version: 2.6.24-2
Severity: important
As in the 2.6.23 debian's kernels, the PATA controller in the SantaRosa
chipset (8086:2850) is non managed by the ata_piix kernel driver.
On the Lenovo Thinkpad R61 (but I know for sure there are other Notebook
suffering of the same problem), the DVD-Writer cannot work with the old piix
modules. If I load the piix module the dvd drive is recognized but it's
unusable. The kernel log gets filled with hda: set_drive_speed_status:
status=0x51 errors.
It would be better if the user has the option to choose the module to load,
as with the vanilla kernel.
Please drop the drivers-ata-ata_piix-postpone-pata.patch.bz2 patch from the
Debian Kernel; it's anachronistic.
- --- dmesg on piix load ---
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
pnp: the driver 'ide' has been registered
ICH8M: IDE controller (0x8086:0x2850 rev 0x03) at PCI slot :00:1f.1
ACPI: PCI Interrupt :00:1f.1[C] - GSI 16 (level, low) - IRQ 16
ICH8M: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0x1c00-0x1c07, BIOS settings: hda:DMA, hdb:pio
ICH8M: IDE port disabled
Probing IDE interface ide0...
hda: MATSHITADVD-RAM UJ-850, ATAPI CD/DVD-ROM drive
hda: host max PIO4 wanted PIO255(auto-tune) selected PIO4
hda: set_drive_speed_status: status=0x51 { DriveReady SeekComplete Error }
hda: set_drive_speed_status: error=0x04 { AbortedCommand }
hda: UDMA/33 mode selected
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
- --- System information. ---
Architecture: amd64
Kernel: Linux 2.6.24-1-amd64
Debian Release: lenny/sid
500 unstablewww.debian-multimedia.org
500 unstableftp.de.debian.org
500 testing www.debian-multimedia.org
500 testing ftp.de.debian.org
500 stable ftp.de.debian.org
1 experimentalftp.de.debian.org
- --- Package information. ---
Depends (Version) | Installed
===-+-===
initramfs-tools (= 0.55) | 0.91d
OR yaird(= 0.0.12-8) |
OR linux-initramfs-tool|
module-init-tools | 3.3-pre11-4
- --
Flavio Visentin
GPG Key: http://www.zipman.it/gpgkey.asc
There are only 10 types of people in this world:
those who understand binary, and those who don't.
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHpgEAusUmHkh1cnoRApp2AKCD9NnORTJ7CMVDJQAbkLa/fYY0vwCgiNq3
YS3WzzFuiULWaAaJkNLb5MY=
=4Oc1
-END PGP SIGNATURE-
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.33-1~experimental.1
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:
firmware-linux-free_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/firmware-linux-free_2.6.33-1~experimental.1_all.deb
linux-2.6_2.6.33-1~experimental.1.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.1.diff.gz
linux-2.6_2.6.33-1~experimental.1.dsc
to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.1.dsc
linux-2.6_2.6.33.orig.tar.gz
to main/l/linux-2.6/linux-2.6_2.6.33.orig.tar.gz
linux-base_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/linux-base_2.6.33-1~experimental.1_all.deb
linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb
linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb
linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb
linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb
linux-headers-2.6.33-2-common_2.6.33-1~experimental.1_amd64.deb
to
Bug#520256: Fwd: Bug#520256: linux-image-2.6.26-1-686: I lost the sound after each reboot, after etch to lenny dist-upgrade and krnel
tags 520256 moreinfo thanks On Fri, Mar 20, 2009 at 01:18:45AM +0100, yellow protoss wrote: HI Max I returned to the 2.26 kernel So I added at teh boot of teh machine: /etc/init.d/alsa reload ons$ uptime 01:09:52 up 1 day, 4:59, 3 users, load average: 0.14, 0.18, 0.12 I didnt reboot yet the box. We'll see at the reboot (dont know when already, since it runs no X) Prob: i cant install my webcam with it. since its not perfectly compiled, this default debian kernel :( Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225180531.ga3...@galadriel.inutil.org
Processed: Re: Can't change CPU scaling governor after .29 to .30 upgrade.
Processing commands for cont...@bugs.debian.org: tags 536183 moreinfo Bug #536183 [linux-2.6] Can't change CPU scaling governor after .29 to .30 upgrade. Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126712247516953.transcr...@bugs.debian.org
Bug#536594: Confirmation
tags 536594 moreinfo thanks On Sat, Aug 15, 2009 at 11:03:42AM -0500, Krzysztof Drewniak wrote: I'd like to confirm this bug on a D-Link DWL-650 PCMICA card. For me, if the card is inserted (during boot of otherwise) messages similar to the ones already in the bug log are displayed and the system freezes, requiring a hard reboot. This bug is also confirmed Linus's kernel 2.6.30.4 using the 2.6.30-1-686 .config and make-kpkg, so this might be an upstream issue (or not). Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225183254.ga8...@galadriel.inutil.org
Bug#444182: marked as done (linux-source-2.6.22: drivers-ata-ata_piix-postpone-pata.patch prevents my dvd writer to be detected)
Your message dated Thu, 25 Feb 2010 19:08:15 +
with message-id e1nkj4j-0001sx...@ries.debian.org
and subject line Bug#444182: fixed in linux-2.6 2.6.33-1~experimental.1
has caused the Debian Bug report #444182,
regarding linux-source-2.6.22: drivers-ata-ata_piix-postpone-pata.patch
prevents my dvd writer to be detected
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.)
--
444182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444182
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: linux-source-2.6.22
Version: 2.6.22-4
Severity: important
*** Please type your report below this line ***
Hi,
The above mentioned patch does not work correctly with my HP nw8440
laptop. The laptop's sata port is correctly handled by the ahci
module, however the pata port is not detected by ata_piix.
When I readd the deleted line
{ 0x8086, 0x27DF, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich_pata_133 },
to the piix_pci_tbl[] in drivers/ata/ata_piix.c, it fixes the problem.
Please consider updating the patch.
Thanks, Laszlo
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.22-ml3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages linux-source-2.6.22 depends on:
ii binutils 2.18~cvs20070812-1 The GNU assembler, linker and bina
ii bzip2 1.0.3-7high-quality block-sorting file co
Versions of packages linux-source-2.6.22 recommends:
ii gcc 4:4.1.2-8 The GNU C compiler
ii libc6-dev [libc-dev] 2.6.1-1+b1 GNU C Library: Development Librari
ii make 3.81-2 The GNU version of the make util
-- no debconf information
---End Message---
---BeginMessage---
Source: linux-2.6
Source-Version: 2.6.33-1~experimental.1
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:
firmware-linux-free_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/firmware-linux-free_2.6.33-1~experimental.1_all.deb
linux-2.6_2.6.33-1~experimental.1.diff.gz
to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.1.diff.gz
linux-2.6_2.6.33-1~experimental.1.dsc
to main/l/linux-2.6/linux-2.6_2.6.33-1~experimental.1.dsc
linux-2.6_2.6.33.orig.tar.gz
to main/l/linux-2.6/linux-2.6_2.6.33.orig.tar.gz
linux-base_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/linux-base_2.6.33-1~experimental.1_all.deb
linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/linux-doc-2.6.33_2.6.33-1~experimental.1_all.deb
linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.33-2-all-amd64_2.6.33-1~experimental.1_amd64.deb
linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.33-2-all_2.6.33-1~experimental.1_amd64.deb
linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb
linux-headers-2.6.33-2-common_2.6.33-1~experimental.1_amd64.deb
to
main/l/linux-2.6/linux-headers-2.6.33-2-common_2.6.33-1~experimental.1_amd64.deb
linux-image-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb
to
main/l/linux-2.6/linux-image-2.6.33-2-amd64_2.6.33-1~experimental.1_amd64.deb
linux-libc-dev_2.6.33-1~experimental.1_amd64.deb
to main/l/linux-2.6/linux-libc-dev_2.6.33-1~experimental.1_amd64.deb
linux-manual-2.6.33_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/linux-manual-2.6.33_2.6.33-1~experimental.1_all.deb
linux-patch-debian-2.6.33_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/linux-patch-debian-2.6.33_2.6.33-1~experimental.1_all.deb
linux-source-2.6.33_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/linux-source-2.6.33_2.6.33-1~experimental.1_all.deb
linux-support-2.6.33-2_2.6.33-1~experimental.1_all.deb
to main/l/linux-2.6/linux-support-2.6.33-2_2.6.33-1~experimental.1_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 444...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
maximilian attems m...@debian.org (supplier of updated linux-2.6 package)
(This message was generated automatically at their request; if you
believe that
Bug#536240: linux-image-2.6.30-1-686: kacpid kacpi_notify use CPU cycles when lid closed on Acer Aspire One
On Sat, Feb 13, 2010 at 12:22:43PM +0100, maximilian attems wrote: On Wed, 08 Jul 2009, ?? wrote: When the lid is closed on my Acer Aspire One (D150-1577), kacpid and kacpi_notify both make very active use of the CPU. I cannot find any evidence of a repeating lid event in my logs as suggested by similar problems had by others. Also, my DSDT appears to have the relevant clause to prevent this. This happens with 2.6.29 and 2.6.30 images from debian unstable, as well as my own 2.6.30.1 kernel. I have the latest acpi packages, and it was happening with slightly older ones too. can you reproduce that with 2.6.32 latest from unstable? if yes please notify upstream in bugzilla.kernel.org and let us know the bugnr. thanks for your report. Did you report this at bugzilla.kernel.org ? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225182836.ga6...@galadriel.inutil.org
Processed: Re: Fwd: Bug#520256: linux-image-2.6.26-1-686: I lost the sound after each reboot, after etch to lenny dist-upgrade and krnel
Processing commands for cont...@bugs.debian.org: tags 520256 moreinfo Bug #520256 [linux-2.6] linux-image-2.6.26-1-686: I lost the sound after each reboot, after etch to lenny dist-upgrade and krnel Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126712114213053.transcr...@bugs.debian.org
Bug#519292: Netdev watchdog timeout
tags 519292 moreinfo thanks On Wed, Mar 11, 2009 at 06:41:30PM +0100, Mr. P|pex wrote: Package: linux-source-2.6.26 Version: 2.6.26 After some hours when I copy big file between in the local net or when use azureus the device network eth0 go down. I need to restart the networking service in order to to go up the eth0. After some minutes the net device go down again. I have PCI net IP1000A. Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225180428.ga2...@galadriel.inutil.org
Bug#533440: marked as done (linux-image-2.6.26-2-686: pl2303 causes warn_on_slowpath)
Your message dated Thu, 25 Feb 2010 19:18:04 +0100 with message-id 20100225181804.ga5...@galadriel.inutil.org and subject line Re: linux-image-2.6.26-2-686: pl2303 causes warn_on_slowpath has caused the Debian Bug report #533440, regarding linux-image-2.6.26-2-686: pl2303 causes warn_on_slowpath 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.) -- 533440: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533440 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-15lenny3 Severity: normal Machine has two pl2303 based usb to serial adapters. Kernel logs periodic warn_on_slowpath warnings. Bug should be fixed in 2.6.28 - but lenny has 2.6.26 - maybe the fix can be backported? -- Package-specific info: ** Version: Linux version 2.6.26-2-686 (Debian 2.6.26-15lenny3) (da...@debian.org) (gcc version 4.1.3 20080704 (prerelease) (Debian 4.1.2-25)) #1 SMP Thu May 28 15:39:35 UTC 2009 ** Command line: root=/dev/md0 ro ** Tainted: G W (512) ** Kernel log: [26302.490254] [c012f689] worker_thread+0x0/0xbd [26302.490264] [c012f73c] worker_thread+0xb3/0xbd [26302.490275] [c013194c] autoremove_wake_function+0x0/0x2d [26302.490293] [c013188b] kthread+0x38/0x5d [26302.490300] [c0131853] kthread+0x0/0x5d [26302.490310] [c01044f3] kernel_thread_helper+0x7/0x10 [26302.490330] === [26302.490336] ---[ end trace cb053aff72c2f311 ]--- [26302.490351] [ cut here ] [26302.490355] WARNING: at drivers/usb/serial/usb-serial.c:307 serial_write+0x58/0x6f [usbserial]() [26302.490359] Modules linked in: pl2303 sch_sfq cls_u32 sch_htb xt_state xt_tcpudp ipt_LOG xt_limit iptable_nat iptable_filter ip_tables x_tables ipv6 reiserfs dm_snapshot dm_mirror dm_log dm_mod nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_conntrack_ftp nf_conntrack w83627ehf hwmon_vid eeprom snd_pcm snd_timer snd soundcore snd_page_alloc iTCO_wdt serio_raw i2c_i801 psmouse i2c_core pcspkr rng_core usbserial button intel_agp agpgart evdev ext3 jbd mbcache raid1 md_mod sd_mod ata_piix ata_generic libata scsi_mod dock e100 mii ide_pci_generic ehci_hcd uhci_hcd usbcore e1000e thermal processor fan thermal_sys piix ide_core [last unloaded: pl2303] [26302.490431] Pid: 9, comm: events/0 Tainted: GW 2.6.26-2-686 #1 [26302.490438] [c01225d3] warn_on_slowpath+0x40/0x66 [26302.490470] [c01395ad] tick_program_event+0x1f/0x23 [26302.490482] [c01360bc] getnstimeofday+0x37/0xbc [26302.490494] [c0134532] ktime_get_ts+0x22/0x49 [26302.490514] [c01188fe] enqueue_task+0x52/0x5d [26302.490524] [c0118924] activate_task+0x1b/0x26 [26302.490532] [c011b6c5] try_to_wake_up+0xe8/0xf1 [26302.490546] [c01184a9] __wake_up_common+0x2e/0x58 [26302.490557] [f897b2bc] serial_write+0x58/0x6f [usbserial] [26302.490573] [c022175b] tty_put_char+0x22/0x25 [26302.490582] [c02253fc] opost+0x185/0x19b [26302.490593] [c0225bc7] n_tty_receive_buf+0x28d/0xc7d [26302.490671] [c01265d9] __do_softirq+0x66/0xd3 [26302.490687] [c01dfd28] rb_insert_color+0x4c/0xad [26302.490700] [c0118ce7] update_curr+0x47/0x79 [26302.490713] [c0119d7a] dequeue_entity+0x13/0x9b [26302.490721] [c0119c6b] __dequeue_entity+0x1f/0x71 [26302.490733] [c010296e] __switch_to+0xa5/0x125 [26302.490741] [c011d408] hrtick_set+0x7a/0xd8 [26302.490758] [c02221ad] flush_to_ldisc+0xd6/0x160 [26302.490774] [c02220d7] flush_to_ldisc+0x0/0x160 [26302.490781] [c012efae] run_workqueue+0x74/0xf2 [26302.490788] [c012f689] worker_thread+0x0/0xbd [26302.490794] [c012f73c] worker_thread+0xb3/0xbd [26302.490802] [c013194c] autoremove_wake_function+0x0/0x2d [26302.490814] [c013188b] kthread+0x38/0x5d [26302.490819] [c0131853] kthread+0x0/0x5d [26302.490825] [c01044f3] kernel_thread_helper+0x7/0x10 [26302.490839] === [26302.490842] ---[ end trace cb053aff72c2f311 ]--- [26620.797052] [ cut here ] [26620.797061] WARNING: at drivers/usb/serial/usb-serial.c:320 serial_write_room+0x41/0x4d [usbserial]() [26620.797093] Modules linked in: pl2303 sch_sfq cls_u32 sch_htb xt_state xt_tcpudp ipt_LOG xt_limit iptable_nat iptable_filter ip_tables x_tables ipv6 reiserfs dm_snapshot dm_mirror dm_log dm_mod nf_nat_ftp nf_nat nf_conntrack_ipv4 nf_conntrack_ftp nf_conntrack w83627ehf hwmon_vid eeprom snd_pcm snd_timer snd soundcore snd_page_alloc iTCO_wdt serio_raw i2c_i801 psmouse i2c_core pcspkr rng_core usbserial button intel_agp agpgart evdev ext3 jbd mbcache raid1 md_mod sd_mod ata_piix ata_generic libata scsi_mod dock e100 mii ide_pci_generic ehci_hcd uhci_hcd usbcore
Bug#536896: linux-image-2.6.26-2-amd64: audio popping with gstreamer using apps when using amd64 kernel and i386 userspace
tags 536896 moreinfo
thanks
On Tue, Jul 14, 2009 at 09:57:54PM +0800, James Andrewartha wrote:
Package: linux-image-2.6.26-2-amd64
Version: 2.6.26-17
Severity: normal
All audio from gstreamer-using apps (eg Totem and Banshee) pops when I use a
2.6.{25,26,28,30} amd64 kernel and i386 userspace. 2.6.24-etchnhalf.1-amd64
does not have this problem, nor does 2.6.26-2-686. It doesn't occur when using
non-gstreamer apps like mplayer or mpd, nor with various gst-launch pipelines
suggested by #gstreamer like gst-launch playbin uri=file:///home/trs80/a.mp3
Hi,
The next release of Debian (6.0, code name Squeeze) will be based
on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell
us whether the problem persists. If so, we should report it upstream
to the kernel.org developers.
The 2.6.32 kernel is available from packages.debian.org and can
be installed in both Debian stable, testing and unstable
installations.
Thanks,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100225183435.ga8...@galadriel.inutil.org
Bug#535070: marked as done (linux-image-2.6.29-1-686: cannot load ali-ircc)
Your message dated Thu, 25 Feb 2010 19:19:31 +0100 with message-id 20100225181931.ga5...@galadriel.inutil.org and subject line Re: linux-image-2.6.29-1-686: cannot load ali-ircc has caused the Debian Bug report #535070, regarding linux-image-2.6.29-1-686: cannot load ali-ircc 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.) -- 535070: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=535070 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.29-1-686 Version: 2.6.29-3 Severity: normal The 0x3e8 address is in /sys/devices/pnp0/00:03/options Dependent: 00 - Priority acceptable port 0x3e8-0x3e8, align 0x0, size 0x8, 16-bit address decoding irq 3,4,5,7 High-Edge dma 1,3 8-bit compatible Dependent: 01 - Priority acceptable port 0x2e8-0x2e8, align 0x0, size 0x8, 16-bit address decoding irq 3,4,5,7 High-Edge dma 1,3 8-bit compatible Dependent: 02 - Priority acceptable port 0x3f8-0x3f8, align 0x0, size 0x8, 16-bit address decoding irq 3,4,5,7 High-Edge dma 1,3 8-bit compatible Dependent: 03 - Priority acceptable port 0x2f8-0x2f8, align 0x0, size 0x8, 16-bit address decoding irq 3,4,5,7 High-Edge dma 1,3 8-bit compatible The device indeed seems to be the IR port (ALi 5123) /sys/devices/pnp0/00:03/id ALI5123 PNP0510 there is no /sys/devices/pnp0/00:03/driver -- Package-specific info: ** Version: Linux version 2.6.29-1-686 (Debian 2.6.29-3) (m...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-8) ) #1 SMP Fri Apr 17 14:35:16 UTC 2009 ** Command line: root=/dev/mapper/nc4010-root ro video=radeonfb ** Tainted: G W (512) ** Kernel log: [341424.756906] ali-ircc, driver loaded (Benjamin Kong) [341424.756930] ali_ircc_open(), can't get iobase of 0x3e8 ** Loaded modules: Module Size Used by sco 8676 2 bridge 39864 0 stp 2092 1 bridge bnep 10848 2 hci_uart 14864 0 ath5k 96892 0 mac80211 135592 1 ath5k ehci_hcd 29936 0 button 5672 0 irtty_sir 4116 0 sir_dev10812 1 irtty_sir irda 95336 1 sir_dev crc_ccitt 1800 1 irda rfcomm 29636 4 l2cap 17072 16 bnep,rfcomm isofs 27408 2 zlib_inflate 13468 1 isofs nls_iso8859_1 3648 0 nls_cp437 5304 0 vfat8672 0 fat41688 1 vfat sd_mod 28252 0 crc_t10dif 1616 1 sd_mod usb_storage83460 0 nls_utf81472 2 cifs 254752 0 nls_base6508 7 isofs,nls_iso8859_1,nls_cp437,vfat,fat,nls_utf8,cifs wacom 17752 0 binfmt_misc 7168 1 radeon102684 0 drm 133260 1 radeon ppdev 6224 0 lp 7872 0 acpi_cpufreq6868 0 cpufreq_conservative 5456 0 cpufreq_userspace 2748 0 cpufreq_stats 3588 0 cpufreq_powersave 1276 0 ipv6 232468 28 loop 12988 4 joydev 8560 0 snd_ali545116348 1 snd_ac97_codec 91260 1 snd_ali5451 pcmcia 23312 0 ac97_bus1444 1 snd_ac97_codec snd_pcm_oss31708 0 snd_mixer_oss 12000 1 snd_pcm_oss snd_pcm62708 3 snd_ali5451,snd_ac97_codec,snd_pcm_oss evdev 8160 11 snd_seq_dummy 2368 0 serio_raw 4544 0 psmouse36628 0 pcspkr 2092 0 i2c_ali15x3 5792 0 arc41544 2 btusb 10156 2 bluetooth 46052 10 sco,bnep,hci_uart,rfcomm,l2cap,btusb ecb 2352 2 snd_seq_oss24756 0 snd_seq_midi5448 0 snd_rawmidi18544 1 snd_seq_midi parport_pc 22020 1 parport30868 3 ppdev,lp,parport_pc snd_seq_midi_event 6072 2 snd_seq_oss,snd_seq_midi snd_seq42120 6 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event i2c_ali1535 5300 0 snd_timer 17808 2 snd_pcm,snd_seq snd_seq_device 6108 5 snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq container 3152 0 video 16348 0 output 2504 1 video snd48420 12
Processed: bug 571465 is forwarded to linux-wirel...@vger.kernel.org
Processing commands for cont...@bugs.debian.org: # Automatically generated email from bts, devscripts version 2.10.35lenny7 forwarded 571465 linux-wirel...@vger.kernel.org Bug #571465 [linux-2.6] linux-image-2.6.32-2-amd64: Kernel WARNING from wdev_cleanup_work when hibernating Set Bug forwarded-to-address to 'linux-wirel...@vger.kernel.org'. 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 Archive: http://lists.debian.org/handler.s.c.126712870725911.transcr...@bugs.debian.org
Bug#571465: linux-image-2.6.32-2-amd64: Kernel WARNING from wdev_cleanup_work when hibernating
On Thu, Feb 25, 2010 at 07:57:00AM -0800, Josh Triplett wrote: Package: linux-2.6 Version: 2.6.32-8 Severity: normal My laptop hibernated due to low battery last night, and this morning after un-hibernating it I noticed the signs of an oops mentioned in my terminal window. Digging through the kernel log, I found these, one during hibernate and the other during un-hibernate: Let's see if linux-wireless can make anything of this. Ben. Feb 25 05:02:10 feather kernel: [42744.419370] [ cut here ] Feb 25 05:02:10 feather kernel: [42744.419393] WARNING: at /build/buildd-linux-2.6_2.6.32-8-amd64-DCxXqz/linux-2.6-2.6.32/debian/build/source_amd64_none/net/wi reless/core.c:614 wdev_cleanup_work+0x49/0xb3 [cfg80211]() Feb 25 05:02:10 feather kernel: [42744.419401] Hardware name: 7454CTO Feb 25 05:02:10 feather kernel: [42744.419404] Modules linked in: iwlagn iwlcore mac80211 cfg80211 ppdev lp parport sco bridge stp btusb bnep rfcomm l2cap crc1 6 bluetooth acpi_cpufreq cpufreq_userspace cpufreq_powersave cpufreq_stats kvm_intel cpufreq_conservative kvm fuse loop snd_hda_codec_conexant arc4 ecb uvcvide o snd_hda_intel snd_hda_codec snd_hwdep snd_pcm videodev snd_seq v4l1_compat snd_timer snd_seq_device v4l2_compat_ioctl32 snd thinkpad_acpi ac led_class batter y nvram psmouse serio_raw rfkill i2c_i801 wmi soundcore evdev snd_page_alloc processor ext3 jbd mbcache sd_mod crc_t10dif ahci uhci_hcd i915 drm_kms_helper ehc i_hcd drm i2c_algo_bit e1000e libata scsi_mod button i2c_core video output usbcore nls_base intel_agp thermal fan thermal_sys [last unloaded: cfg80211] Feb 25 05:02:10 feather kernel: [42744.419547] Pid: 10, comm: events/1 Not tainted 2.6.32-2-amd64 #1 Feb 25 05:02:10 feather kernel: [42744.419552] Call Trace: Feb 25 05:02:10 feather kernel: [42744.419566] [a03e24f7] ? wdev_cleanup_work+0x49/0xb3 [cfg80211] Feb 25 05:02:10 feather kernel: [42744.419579] [a03e24f7] ? wdev_cleanup_work+0x49/0xb3 [cfg80211] Feb 25 05:02:10 feather kernel: [42744.419590] [8104dbe8] ? warn_slowpath_common+0x77/0xa3 Feb 25 05:02:10 feather kernel: [42744.419603] [a03e24f7] ? wdev_cleanup_work+0x49/0xb3 [cfg80211] Feb 25 05:02:10 feather kernel: [42744.419613] [81061473] ? worker_thread+0x188/0x21d Feb 25 05:02:10 feather kernel: [42744.419625] [a03e24ae] ? wdev_cleanup_work+0x0/0xb3 [cfg80211] Feb 25 05:02:10 feather kernel: [42744.419635] [81064a5e] ? autoremove_wake_function+0x0/0x2e Feb 25 05:02:10 feather kernel: [42744.419643] [810612eb] ? worker_thread+0x0/0x21d Feb 25 05:02:10 feather kernel: [42744.419650] [81064791] ? kthread+0x79/0x81 Feb 25 05:02:10 feather kernel: [42744.419660] [81011baa] ? child_rip+0xa/0x20 Feb 25 05:02:10 feather kernel: [42744.419667] [81064718] ? kthread+0x0/0x81 Feb 25 05:02:10 feather kernel: [42744.419674] [81011ba0] ? child_rip+0x0/0x20 Feb 25 05:02:10 feather kernel: [42744.419679] ---[ end trace 240fa69dfbf9d219 ]--- Feb 25 07:22:39 feather kernel: [42747.551961] Restarting tasks ... done. Feb 25 07:22:39 feather kernel: [42747.588358] PM: Basic memory bitmaps freed Feb 25 07:22:40 feather kernel: [42747.627928] BUG: unable to handle kernel NULL pointer dereference at 0020 Feb 25 07:22:40 feather kernel: [42747.627935] IP: [8113d11e] sysfs_open_file+0x33/0x2aa Feb 25 07:22:40 feather kernel: [42747.627945] PGD 123283067 PUD 123282067 PMD 0 Feb 25 07:22:40 feather kernel: [42747.627950] Oops: [#1] SMP Feb 25 07:22:40 feather kernel: [42747.627954] last sysfs file: /sys/devices/virtual/bdi/7:6/uevent Feb 25 07:22:40 feather kernel: [42747.627957] CPU 0 Feb 25 07:22:40 feather kernel: [42747.627959] Modules linked in: iwlagn iwlcore mac80211 cfg80211 ppdev lp parport sco bridge stp btusb bnep rfcomm l2cap crc16 bluetooth acpi_cpufreq cpufreq_userspace cpufreq_powersave cpufreq_stats kvm_intel cpufreq_conservative kvm fuse loop snd_hda_codec_conexant arc4 ecb uvcvideo snd_hda_intel snd_hda_codec snd_hwdep snd_pcm videodev snd_seq v4l1_compat snd_timer snd_seq_device v4l2_compat_ioctl32 snd thinkpad_acpi ac led_class battery nvram psmouse serio_raw rfkill i2c_i801 wmi soundcore evdev snd_page_alloc processor ext3 jbd mbcache sd_mod crc_t10dif ahci uhci_hcd i915 drm_kms_helper ehci_hcd drm i2c_algo_bit e1000e libata scsi_mod button i2c_core video output usbcore nls_base intel_agp thermal fan thermal_sys [last unloaded: cfg80211] Feb 25 07:22:40 feather kernel: [42747.628006] Pid: 5535, comm: udev-acl.ck Tainted: GW 2.6.32-2-amd64 #1 7454CTO Feb 25 07:22:40 feather kernel: [42747.628006] RIP: 0010:[8113d11e] [8113d11e] sysfs_open_file+0x33/0x2aa Feb 25 07:22:40 feather kernel: [42747.628006] RSP: 0018:880139cadd78 EFLAGS: 00010296 Feb 25 07:22:40 feather kernel:
Bug#571533: Lenny's Kernel does not support ICH8 SATA controller
Package: linux-image-2.6.26-2-686 Version: 2.6.26-21lenny3 We have a IBM server (IBM Systemx 3250M3) which have an Intel ICH8 SATA controller. When I try to install Debian Lenny on this server, the running kernel doesn't see the hard drives. I've install another GNU Linux System with a kernel more recent and I've take this information. PCI-ID of this controller : 8086:3B20 This is the result of lshw command for the SATA controller : *-ide:0 description: IDE interface product: 5 Series/3400 Series Chipset 4 port SATA IDE Controller [8086:3B20] vendor: Intel Corporation [8086] physical id: 1f.2 bus info: p...@:00:1f.2 logical name: scsi0 logical name: scsi1 version: 05 width: 32 bits clock: 66MHz capabilities: ide pm bus_master cap_list emulated configuration: driver=ata_piix latency=0 resources: irq:19 ioport:3078(size=8) ioport:308c(size=4) ioport:3070(size=8) ioport:3088(size=4) ioport:3050(size=16) ioport:3040(size=16) In the ata_piix driver, this ID was introduced since the 2.6.27. Is it usual to ask for a driver backport into the current kernel version ? Thank you by advance. Regards, -- Laurent GUINCHARD Orange Business Services Direction Internet et Hebergement 13 rue de Javel 75015 Paris E-mail : l...@oleane.net -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225203945.5be2b...@morpheus
Processed: reopening 444182
Processing commands for cont...@bugs.debian.org:
reopen 444182
Bug #444182 {Done: maximilian attems m...@debian.org} [linux-2.6]
linux-source-2.6.22: drivers-ata-ata_piix-postpone-pata.patch prevents my dvd
writer to be detected
Bug #463833 {Done: maximilian attems m...@debian.org} [linux-2.6] SantaRosa
PATA don't managed by ata_piix
Bug #535959 {Done: maximilian attems m...@debian.org} [linux-2.6] linux-2.6:
Please enable libata for PATA/piix
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
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
Archive:
http://lists.debian.org/handler.s.c.12671297323833.transcr...@bugs.debian.org
Bug#534690: marked as done (linux-image-2.6.30-1-686: unable to unmount a loop device)
Your message dated Thu, 25 Feb 2010 21:33:59 +0100 with message-id 20100225203359.ga3...@galadriel.inutil.org and subject line Re: Bug#534690: linux-image-2.6.30-1-686: unable to unmount a loop device has caused the Debian Bug report #534690, regarding linux-image-2.6.30-1-686: unable to unmount a loop device 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.) -- 534690: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534690 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-1-686 Version: 2.6.30-1 Severity: normal # lsmod | grep -c loop 0 # modprobe loop max_part=8 # dd if=/dev/zero of=/tmp/fs bs=1M count=1 1+0 records in 1+0 records out 1048576 bytes (1.0 MB) copied, 0.00407344 s, 257 MB/s # mke2fs -F -q /tmp/fs # mkdir /tmp/mnt/ # mount -o loop /tmp/fs /tmp/mnt/ # umount /tmp/mnt/ [ 284.509864] BUG: unable to handle kernel NULL pointer dereference at 0060 [ 284.509902] IP: [c01f6f27] blkdev_ioctl+0x25/0x842 [ 284.509929] *pde = [ 284.509944] Oops: [#1] SMP [ 284.509963] last sysfs file: /sys/devices/virtual/block/loop0/removable [ 284.509980] Modules linked in: loop ext2 tun kvm_amd kvm binfmt_misc nf_conntrack_ipv6 ip6table_filter ip6_tables nvidiafb fb_ddc vgastate xt_MARK iptable_mangle iptable_nat nf_nat ipt_REJECT xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack iptable_filter ip_tables x_tables fuse snd_hda_codec_realtek tvaudio tda7432 tuner_simple tuner_types tuner arc4 ecb snd_hda_intel snd_hda_codec bttv ir_common snd_hwdep i2c_algo_bit v4l2_common videodev v4l1_compat snd_pcm videobuf_dma_sg snd_seq snd_timer snd_seq_device rt61pci crc_itu_t rt2x00pci snd videobuf_core btcx_risc rt2x00lib soundcore snd_page_alloc led_class input_polldev mac80211 tveeprom cfg80211 eeprom_93cx6 i2c_nforce2 i2c_core evdev processor button k8temp serio_raw psmouse ext3 jbd mbcache ide_gd_mod ide_cd_mod cdrom ata_generic libata scsi_mod ide_pci_generic amd74xx forcedeth ide_core ohci_hcd ehci_hcd usbcore floppy thermal fan thermal_sys [last unloaded: loop] [ 284.510570] [ 284.510581] Pid: 3328, comm: umount Not tainted (2.6.30-1-686 #1) M61SME-S2 [ 284.510600] EIP: 0060:[c01f6f27] EFLAGS: 00010287 CPU: 1 [ 284.510617] EIP is at blkdev_ioctl+0x25/0x842 [ 284.510630] EAX: EBX: 125f ECX: 125f EDX: [ 284.510645] ESI: EDI: EBP: ESP: c3fefe08 [ 284.510662] DS: 007b ES: 007b FS: 00d8 GS: 0033 SS: 0068 [ 284.510677] Process umount (pid: 3328, ti=c3fee000 task=c3d2e750 task.ti=c3fee000) [ 284.510694] Stack: [ 284.510704] c011dda9 c04ca6ec c3d2e750 c3cacc80 c3cacc80 c3cacc80 c04951c0 [ 284.510756] c031ce8e c38630c0 0b00 c04951c0 0212 c3d2e904 [ 284.510814] 0001 0246 3e1b71e2 0042 c040c840 000c c017160e 000c [ 284.510876] Call Trace: [ 284.510886] [c011dda9] ? pick_next_task_fair+0x80/0x87 [ 284.510909] [c031ce8e] ? __schedule+0x719/0x746 [ 284.510931] [c017160e] ? release_pages+0x11c/0x124 [ 284.510953] [c011cc82] ? update_curr+0x58/0x178 [ 284.510973] [c031cec0] ? schedule+0x5/0x13 [ 284.510991] [c031cfeb] ? schedule_timeout+0x14/0xbd [ 284.511011] [c011cf9e] ? check_preempt_wakeup+0x139/0x173 [ 284.511031] [c031c6c7] ? wait_for_common+0xc1/0x112 [ 284.511051] [c0121ee3] ? default_wake_function+0x0/0x8 [ 284.511075] [c01a9eac] ? ioctl_by_bdev+0x20/0x2f [ 284.511096] [f8463f90] ? loop_clr_fd+0x186/0x1a2 [loop] [ 284.59] [f8463fdb] ? lo_release+0x2f/0x53 [loop] [ 284.511141] [c01aa955] ? __blkdev_put+0x7a/0x10f [ 284.511160] [c01ba4dd] ? vfs_quota_off+0x0/0xd [ 284.511183] [c018f4ad] ? deactivate_super+0x4a/0x61 [ 284.511204] [c019e6d5] ? sys_umount+0x29a/0x2c0 [ 284.511225] [c019e706] ? sys_oldumount+0xb/0xe [ 284.511243] [c0103014] ? sysenter_do_call+0x12/0x28 [ 284.511264] Code: 40 e9 30 57 f2 ff 55 89 d5 57 56 89 c6 53 89 cb 81 ec f0 00 00 00 81 f9 65 12 00 00 89 44 24 38 8b bc 24 04 01 00 00 89 44 24 10 8b 50 60 0f 84 cb 03 00 00 77 79 81 f9 60 12 00 00 0f 84 77 07 [ 284.511591] EIP: [c01f6f27] blkdev_ioctl+0x25/0x842 SS:ESP 0068:c3fefe08 [ 284.511618] CR2: 0060 [ 284.511631] ---[ end trace 35bc3eb2ec9cc947 ]--- Killed -- Package-specific info: ** Version: Linux version 2.6.30-1-686 (Debian 2.6.30-1) (wa...@debian.org) (gcc version 4.3.3 (Debian 4.3.3-11) ) #1 SMP Sun Jun 14 16:11:32 UTC 2009 -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (900, 'unstable'), (500, 'experimental') Architecture:
Bug#444182: Reopen as there is no 2.6.33 in the archive
Hi, I'm reopening #444182 as there is no 2.6.33-1~experimental.1 or newer in the archive and the fix is not mentioned in the 2.6.32-3 changelog. Yours, Martin -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225203052.gf16...@anguilla.debian.or.at
Bug#571096: marked as done (Badness after waking up on iBook G4)
maximilian, On Wed, Feb 24, 2010 at 11:57:16AM +0100, maximilian attems wrote: On Tue, 23 Feb 2010, Philipp Kern wrote: maximilian, am Tue, Feb 23, 2010 at 05:42:28PM +0100 hast du folgendes geschrieben: the double resume happened a lot on gnome desktops afaik. this points to gnome-power-manager or such, are you running latest 2.6.28.3-2 ?? I do. hmm strange, this one fixed it for me, do you want this reassigned to it so that gnome maintainer can ask for specific hints? yes, a clone and reassign to the proper package would be appreciated. I just confirmed that it does not double suspend when no gnome session is started (i.e. on a vt with gdm running in the background with nobody logged in). Thanks a lot, Philipp Kern -- .''`. Philipp KernDebian Developer : :' : http://philkern.de Stable Release Manager `. `' xmpp:p...@0x539.de Wanna-Build Admin `-finger pkern/k...@db.debian.org signature.asc Description: Digital signature
Processed: tagging 508460
Processing commands for cont...@bugs.debian.org:
# Automatically generated email from bts, devscripts version 2.10.35lenny7
tags 508460 + pending
Bug #508460 {Done: Moritz Muehlenhoff j...@inutil.org} [linux-2.6] ipv6:
add/up results in permanent 'tentative' flag, up/add works
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
Archive:
http://lists.debian.org/handler.s.c.126713393224196.transcr...@bugs.debian.org
Bug#571533: marked as done (Lenny's Kernel does not support ICH8 SATA controller)
Your message dated Thu, 25 Feb 2010 22:43:48 +0100 with message-id 20100225214348.ga5...@galadriel.inutil.org and subject line Re: Lenny's Kernel does not support ICH8 SATA controller has caused the Debian Bug report #571533, regarding Lenny's Kernel does not support ICH8 SATA controller 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.) -- 571533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=571533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-2-686 Version: 2.6.26-21lenny3 We have a IBM server (IBM Systemx 3250M3) which have an Intel ICH8 SATA controller. When I try to install Debian Lenny on this server, the running kernel doesn't see the hard drives. I've install another GNU Linux System with a kernel more recent and I've take this information. PCI-ID of this controller : 8086:3B20 This is the result of lshw command for the SATA controller : *-ide:0 description: IDE interface product: 5 Series/3400 Series Chipset 4 port SATA IDE Controller [8086:3B20] vendor: Intel Corporation [8086] physical id: 1f.2 bus info: p...@:00:1f.2 logical name: scsi0 logical name: scsi1 version: 05 width: 32 bits clock: 66MHz capabilities: ide pm bus_master cap_list emulated configuration: driver=ata_piix latency=0 resources: irq:19 ioport:3078(size=8) ioport:308c(size=4) ioport:3070(size=8) ioport:3088(size=4) ioport:3050(size=16) ioport:3040(size=16) In the ata_piix driver, this ID was introduced since the 2.6.27. Is it usual to ask for a driver backport into the current kernel version ? Thank you by advance. Regards, -- Laurent GUINCHARD Orange Business Services Direction Internet et Hebergement 13 rue de Javel 75015 Paris E-mail : l...@oleane.net ---End Message--- ---BeginMessage--- Version: 2.6.28-1 Laurent GUINCHARD wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-21lenny3 We have a IBM server (IBM Systemx 3250M3) which have an Intel ICH8 SATA controller. When I try to install Debian Lenny on this server, the running kernel doesn't see the hard drives. I've install another GNU Linux System with a kernel more recent and I've take this information. PCI-ID of this controller : 8086:3B20 This is the result of lshw command for the SATA controller : *-ide:0 description: IDE interface product: 5 Series/3400 Series Chipset 4 port SATA IDE Controller [8086:3B20] vendor: Intel Corporation [8086] physical id: 1f.2 bus info: p...@:00:1f.2 logical name: scsi0 logical name: scsi1 version: 05 width: 32 bits clock: 66MHz capabilities: ide pm bus_master cap_list emulated configuration: driver=ata_piix latency=0 resources: irq:19 ioport:3078(size=8) ioport:308c(size=4) ioport:3070(size=8) ioport:3088(size=4) ioport:3050(size=16) ioport:3040(size=16) In the ata_piix driver, this ID was introduced since the 2.6.27. Is it usual to ask for a driver backport into the current kernel version ? Thank you by advance. Fixed in SVN for the next Lenny point update. Please test a build, since I don't own the hardware: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official-vcs (dists/lenny/linux-2.6, commit r15279 and higher) I'm also marking this as fixed in 2.6.28 for unstable, since we have uploaded 2.6.27. Cheers, Moritz ---End Message---
failure to remove+purge debian package generated by make deb-pkg
Hello, I created and successfully installed a custom kernel package using $(make deb-pkg). Then after a failed boot test I removed it and then thought that I actually want to purge it. Here's the result: u...@host:~$ sudo dpkg --remove linux-image-2.6.33-rc8-rt (Reading database ... 153356 files and directories currently installed.) Removing linux-image-2.6.33-rc8-rt ... update-initramfs: Deleting /boot/initrd.img-2.6.33-rc8-rt u...@host:~$ sudo dpkg --purge linux-image-2.6.33-rc8-rt (Reading database ... 150555 files and directories currently installed.) Removing linux-image-2.6.33-rc8-rt ... Purging configuration files for linux-image-2.6.33-rc8-rt ... Cannot delete /boot/initrd.img-2.6.33-rc8-rt, doesn't exist. run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 1 dpkg: error processing linux-image-2.6.33-rc8-rt (--purge): subprocess installed post-removal script returned error exit status 1 Errors were encountered while processing: linux-image-2.6.33-rc8-rt I didn't check if the problem is the package or initramfs-tools (0.93.4). Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König| Industrial Linux Solutions | http://www.pengutronix.de/ | -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225213610.ga30...@pengutronix.de
Processed: Re: linux-image-2.6.26-2-686: rt2500pci module has unreliable and slow connection speed
Processing commands for cont...@bugs.debian.org: tags 554619 moreinfo Bug #554619 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: rt2500pci module has unreliable and slow connection speed Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126713448531552.transcr...@bugs.debian.org
Bug#555531: linux-image-2.6.26-2-amd64: sound not working in OSS games after update
On Thu, Nov 12, 2009 at 12:47:39PM -0800, Brandon Del Bel wrote:
If it helps at all, here's the relevant strace output:
4093 open(/dev/dsp, O_RDWR) = 7
4093 ioctl(7, SNDCTL_DSP_GETCAPS, 0xffb7a884) = 0
4093 ioctl(7, SNDCTL_DSP_SETFMT or SOUND_PCM_READ_BITS, 0xffb7a888) = 0
4093 ioctl(7, SOUND_PCM_READ_CHANNELS, 0x811b724) = 0
4093 ioctl(7, SNDCTL_DSP_SPEED or SOUND_PCM_READ_RATE, 0x811b738) = 0
4093 ioctl(7, SNDCTL_DSP_GETOSPACE, 0xffb7a874) = -1 EINVAL (Invalid
argument)
4093 dup(2)= 8
4093 fcntl64(8, F_GETFL) = 0x802 (flags O_RDWR|O_NONBLOCK)
4093 fstat64(8, {st_mode=S_IFCHR|0620, st_rdev=makedev(136, 1), ...}) = 0
4093 mmap2(NULL, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xf743a000
4093 _llseek(8, 0, 0xffb7a6cc, SEEK_CUR) = -1 ESPIPE (Illegal seek)
4093 write(8, GETOSPACE: Invalid argument\n..., 28) = 28
4093 close(8) = 0
4093 munmap(0xf743a000, 4096) = 0
4093 write(1, Um, can't do GETOSPACE?\n..., 24) = 24
-Brandon Del Bel
Does this still occur with current Lenny or has the problem
been resolved in the mean time?
Cheers,
Moritz
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100225215329.ga6...@galadriel.inutil.org
Bug#556585: marked as done (iwlagn gone bananas after a couple of hours)
Your message dated Thu, 25 Feb 2010 23:07:30 +0100 with message-id 20100225220730.ga7...@galadriel.inutil.org and subject line Re: Bug#556585: iwlagn gone bananas after a couple of hours has caused the Debian Bug report #556585, regarding iwlagn gone bananas after a couple of hours 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.) -- 556585: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=556585 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.30-2-686 Version: 2.6.30-8 This happened on a lenovo x300 using the squeeze distro, I suddendly lost the connectivity for the wireless card. I tried to reload iwlagn to no avail. Everything seems to be fine on reboot, though here is the lspci output: 00:00.0 Host bridge: Intel Corporation Mobile PM965/GM965/GL960 Memory Controller Hub (rev 0c) Subsystem: Lenovo T61 Flags: bus master, fast devsel, latency 0 Capabilities: [e0] Vendor Specific Information ? Kernel driver in use: agpgart-intel 00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) (prog-if 00 [VGA controller]) Subsystem: Lenovo T61 Flags: bus master, fast devsel, latency 0, IRQ 30 Memory at fa00 (64-bit, non-prefetchable) [size=1M] Memory at e000 (64-bit, prefetchable) [size=256M] I/O ports at 1800 [size=8] Expansion ROM at unassigned [disabled] Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [d0] Power Management version 3 00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c) Subsystem: Lenovo T61 Flags: bus master, fast devsel, latency 0 Memory at fa10 (64-bit, non-prefetchable) [size=1M] Capabilities: [d0] Power Management version 3 00:19.0 Ethernet controller: Intel Corporation 82566MM Gigabit Network Connection (rev 03) Subsystem: Lenovo ThinkPad T61 Flags: bus master, fast devsel, latency 0, IRQ 27 Memory at fa20 (32-bit, non-prefetchable) [size=128K] Memory at fa225000 (32-bit, non-prefetchable) [size=4K] I/O ports at 1840 [size=32] Capabilities: [c8] Power Management version 2 Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+ Kernel driver in use: e1000e 00:1a.0 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #4 (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo ThinkPad T61 Flags: bus master, medium devsel, latency 0, IRQ 20 I/O ports at 1860 [size=32] Kernel driver in use: uhci_hcd 00:1a.1 USB Controller: Intel Corporation 82801H (ICH8 Family) USB UHCI Controller #5 (rev 03) (prog-if 00 [UHCI]) Subsystem: Lenovo ThinkPad T60 Flags: bus master, medium devsel, latency 0, IRQ 21 I/O ports at 1880 [size=32] Kernel driver in use: uhci_hcd 00:1a.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #2 (rev 03) (prog-if 20 [EHCI]) Subsystem: Lenovo ThinkPad T61 Flags: bus master, medium devsel, latency 0, IRQ 22 Memory at fa426c00 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Kernel driver in use: ehci_hcd 00:1b.0 Audio device: Intel Corporation 82801H (ICH8 Family) HD Audio Controller (rev 03) Subsystem: Lenovo ThinkPad T61 Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at fa22 (64-bit, non-prefetchable) [size=16K] Capabilities: [50] Power Management version 2 Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+ Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00 Capabilities: [100] Virtual Channel ? Capabilities: [130] Root Complex Link ? Kernel driver in use: HDA Intel 00:1c.0 PCI bridge: Intel Corporation 82801H (ICH8 Family) PCI Express Port 1 (rev 03) (prog-if 00 [Normal decode]) Flags: bus master, fast devsel, latency 0 Bus: primary=00, secondary=02, subordinate=02, sec-latency=0 I/O behind bridge: 2000-2fff Memory behind bridge: f400-f5ff Prefetchable memory behind bridge: fa50-fa5f Capabilities: [40] Express Root Port (Slot+), MSI 00 Capabilities: [80] MSI: Enable+ Count=1/1 Maskable- 64bit- Capabilities: [90] Subsystem: Lenovo ThinkPad T61 Capabilities: [a0] Power Management version 2
Processed: Re: kernel crash
Processing commands for cont...@bugs.debian.org: tags 557068 moreinfo Bug #557068 [linux-2.6] kernel crash Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.12671358288524.transcr...@bugs.debian.org
Processed: Re: Bug#557527: (no subject)
Processing commands for cont...@bugs.debian.org: tags 557527 moreinfo Bug #557527 [linux-2.6] confusing battery charge reporting Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.12671359239432.transcr...@bugs.debian.org
Processed: tagging 558265
Processing commands for cont...@bugs.debian.org: tags 558265 wontfix Bug #558265 [linux-2.6] Warns about firmware that is not needed Added tag(s) wontfix. 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 Archive: http://lists.debian.org/handler.s.c.126713638918564.transcr...@bugs.debian.org
Processed: severity of 558265 is wishlist
Processing commands for cont...@bugs.debian.org: severity 558265 wishlist Bug #558265 [linux-2.6] Warns about firmware that is not needed Severity set to 'wishlist' from 'normal' 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 Archive: http://lists.debian.org/handler.s.c.126713639018628.transcr...@bugs.debian.org
Processed: Re: linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
Processing commands for cont...@bugs.debian.org: tags 557802 moreinfo Bug #557802 [linux-image-2.6.26-2-686] linux-image-2.6.26-2-686: No sound with snd-ens1371.ko Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126713632118216.transcr...@bugs.debian.org
Bug#555680: marked as done (System information in bug reports may be security-sensitive)
Your message dated Thu, 25 Feb 2010 23:01:20 +0100 with message-id 20100225220120.ga7...@galadriel.inutil.org and subject line Re: System information in bug reports may be security-sensitive has caused the Debian Bug report #555680, regarding System information in bug reports may be security-sensitive 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.) -- 555680: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555680 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-2.6 Version: 2.6.31-1 Severity: normal Tags: security The bug script now offers to include network configuration and status. The network configuration file /etc/network/interfaces may include encryption keys for wireless networks, which we should scrub. There is also a more general problem of sensitive information in the kernel log, but I'm not sure what we can do about that. Ben. -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (x86_64) Kernel: Linux 2.6.31-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Version: 2.6.32-1 On Thu, Nov 19, 2009 at 03:04:43PM +0100, Stefan Lippers-Hollmann wrote: Hi r14441 [1], hide wireless keys and wake-on-LAN password when including network configuration in bug reports (bug #555680). It is unfortunately not enough to prune wireless-key from bugreports, as wpasupplicant defines additional means to configure passwords for wireless links[2], namely wpa-psk and wpa-password. Additionally I suggest to prune commented out lines as well, as these might contain passwords or other sensitive information and have no relevance for bugreporting. The attached, valid, /etc/network/interfaces example illustrates the problem with these means of configuration. The following patch applies to sid and trunk of linux-2.6 (r14649). Thanks, this was fixed by Ben in linux-2.6 (2.6.32~rc8-1~experimental.1) unstable; urgency=low [..] * Hide WPA authentication parameters and comments when including network configuration in bug reports Cheers, Moritz ---End Message---
Bug#554619: linux-image-2.6.26-2-686: rt2500pci module has unreliable and slow connection speed
tags 554619 moreinfo thanks On Thu, Nov 05, 2009 at 07:23:42PM +0100, mase wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-19lenny2 Severity: normal I get very slow connection speeds with this module around 40 KB/s what should be 700 - 800 KB/s. I connect through a router with WPA encryption. Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225214754.ga5...@galadriel.inutil.org
Bug#555102: (no subject)
On Thu, Nov 12, 2009 at 12:33:56AM +0100, Stefan Hett wrote: I've just tested it with the newly available kernel image in the unstable branch (linux-image-2.6.31-1-686) and with that am getting the following dmesg output: [ 15.548007] rt2860sta: module is from the staging directory, the quality is unknown, you have been warned. [ 15.565866] rt2860 :02:0c.0: PCI INT A - GSI 20 (level, low) - IRQ 20 [ 15.568251] [ 15.568256] [ 15.568258] === pAd = e0d5, size = 580808 === [ 15.568260] [ 15.568413] -- RTMPAllocAdapterBlock, Status=0 Since I also see an entry in iwconfig I suspect the issue has been resolved with that kernel (build) (I'm not 100% sure because of the warning in the dmesg output as well as the fact that the driver seems not to be the rt61pci one as it is/was for all the older kernels)? I.e. the driver itself is functional with current kernels? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225214932.ga6...@galadriel.inutil.org
Bug#571533: Lenny's Kernel does not support ICH8 SATA controller
Version: 2.6.28-1 Laurent GUINCHARD wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-21lenny3 We have a IBM server (IBM Systemx 3250M3) which have an Intel ICH8 SATA controller. When I try to install Debian Lenny on this server, the running kernel doesn't see the hard drives. I've install another GNU Linux System with a kernel more recent and I've take this information. PCI-ID of this controller : 8086:3B20 This is the result of lshw command for the SATA controller : *-ide:0 description: IDE interface product: 5 Series/3400 Series Chipset 4 port SATA IDE Controller [8086:3B20] vendor: Intel Corporation [8086] physical id: 1f.2 bus info: p...@:00:1f.2 logical name: scsi0 logical name: scsi1 version: 05 width: 32 bits clock: 66MHz capabilities: ide pm bus_master cap_list emulated configuration: driver=ata_piix latency=0 resources: irq:19 ioport:3078(size=8) ioport:308c(size=4) ioport:3070(size=8) ioport:3088(size=4) ioport:3050(size=16) ioport:3040(size=16) In the ata_piix driver, this ID was introduced since the 2.6.27. Is it usual to ask for a driver backport into the current kernel version ? Thank you by advance. Fixed in SVN for the next Lenny point update. Please test a build, since I don't own the hardware: http://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official-vcs (dists/lenny/linux-2.6, commit r15279 and higher) I'm also marking this as fixed in 2.6.28 for unstable, since we have uploaded 2.6.27. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225214348.ga5...@galadriel.inutil.org
Re: failure to remove+purge debian package generated by make deb-pkg
Uwe Kleine-König wrote:
I created and successfully installed a custom kernel package using
$(make deb-pkg).
Then after a failed boot test I removed it and then thought that I
actually want to purge it.
Cannot delete /boot/initrd.img-2.6.33-rc8-rt, doesn't exist.
run-parts: /etc/kernel/postrm.d/initramfs-tools exited with return code 1
It has nothing to do with the kernel package itself. The problem is in the
maintainer scripts that are run as hooks from /etc/kernel/*.d.
The kernel package built by deb-pkg does not have any maintainer scripts of
itself. All it does is run whatever is in the hooks. As custom kernels may
have other requirements than distro ones it's not surprising that the
distro hooks can throw errors [1].
Personally I use a set of custom hook scripts with my deb-pkg kernels.
Simply because I don't want to have to fix issues that are the result of
the distro hook scripts in /etc/kernel.
You can simply use custom hook scripts by doing e.g:
export KDEB_HOOKDIR=/etc/kernel.custom
before calling 'make deb-pkg'. You can then create your own hook scripts
in /etc/kernel.custom/{pre,post}{inst,rm}.d/.
Cheers,
FJP
[1] Although in this case I would say that the initrd could also simply be
removed using 'rm -f' so it does not fail if it does not exist.
You could file a BR against the package that installed that particular hook
script, probably initramfs-tools.
--
To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201002252329.12338.elen...@planet.nl
Bug#557068: kernel crash
tags 557068 moreinfo thanks On Thu, Nov 19, 2009 at 12:34:05PM +0300, Vladimir Stavrinov wrote: Package: linux-2.6 Version: 2.6.31-2 Severity: normal It happens twice for a few days after upgrade with last hello before dead: Nov 17 06:41:50 foo kernel: [68763.018411] [ cut here ] Nov 17 06:41:50 foo kernel: [68763.018485] kernel BUG at /tmp/buildd/linux-2.6-2.6.31/debian/build/source_i386_none/mm/slab.c:2974! Nov 17 06:41:50 foo kernel: [68763.018545] invalid opcode: [#1] SMP Nov 17 06:41:50 foo kernel: [68763.018582] last sysfs file: /sys/devices/platform/via686a.24576/temp3_alarm Nov 17 06:41:50 foo kernel: [68763.019453] Process mandb (pid: 29989, ti=c0306000 task=de8c8650 task.ti=c0306000) Nov 17 06:41:50 foo kernel: [68763.019506] Stack: Nov 17 06:41:50 foo kernel: [68763.019743] Call Trace: Nov 17 06:41:50 foo kernel: [68763.020058] Code: 00 00 8b 33 39 de 75 14 8b 73 10 c7 43 34 01 00 00 00 3b 74 24 1c 0f 84 9f 00 00 00 8b 54 24 14 8b 46 10 3b 82 98 00 00 00 72 32 0f 0b eb fe 8b 44 24 14 8b 4d 00 8b 90 8c 00 00 00 8b 44 24 04 8:c0307d4 Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225221012.ga8...@galadriel.inutil.org
Bug#557527: (no subject)
tags 557527 moreinfo thanks On Sun, Nov 22, 2009 at 05:53:26PM +, Ben Hutchings wrote: On Sun, 2009-11-22 at 17:51 +0100, Lennert Van Alboom wrote: Package: linux-2.6 Version: 2.6.31-2 Severity: normal When the battery is being charged, its charge will rise steadily until it reaches 99%, after which its charge_now jumps to the value held by charge_full_design. This basically means that charge_now will hold a value larger than the one in charge_full, which confuses (for an example) gkrellm up to a point that it reports the battery to suddenly be at 130% full. I reported this as a bug in gkrellm initially (http://bugs.debian.org/551518) but it turned out rather quickly to be a sysfs thing. I noticed this oddity first in kernel 2.6.30-1-686, and upgraded to 2.6.31-1-686 following the gkrellm maintainer's advice. This didn't change the behaviour. The kernel basically reports what the firmware (BIOS) tells it, so this is probably a BIOS bug, but it might be reasonable to work around it. Try reporting this upstream at http://bugzilla.kernel.org and let us know the bug number so we can track it. Did you report this at http://bugzilla.kernel.org ? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225221146.ga9...@galadriel.inutil.org
Processed: Re: Bug#559342: linux-image-2.6.30-2-686: USB Devices managed by uhci_hcd fail to mount
Processing commands for cont...@bugs.debian.org: tags 559342 moreinfo Bug #559342 [linux-2.6] linux-image-2.6.30-2-686: USB Devices managed by uhci_hcd fail to mount Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126713718921879.transcr...@bugs.debian.org
Bug#557802: linux-image-2.6.26-2-686: No sound with snd-ens1371.ko
tags 557802 moreinfo thanks On Tue, Nov 24, 2009 at 03:39:44PM +0100, Tino Schmidt wrote: Package: linux-image-2.6.26-2-686 Version: 2.6.26-19lenny2 Severity: normal Two days ago I installed Debian on a 10-year-old laptop. It's a IPC Topnote G. Soundcard is a Creative Labs Ectiva EV1938. The laptop was running a few days ago with Debian Etch and OSS-modules and the output of oss-modul es1371 was quite good. I formated the harddisk to set up Lenny. If I play a music file now, it looks like the file is played without any errors. There are no messages that the hardware or alsa is corrupt. But the speakers are silent. The tool alsamixer shows that nothing is muted and all values are at maximum level. The tools `speaker-test` shows normal behaviour/output, but also with silent speakers. I checked alsa-mailinglist and found a mistake which is very similar: http://www.mail-archive.com/alsa-u...@lists.sourceforge.net/msg22930.html Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225221827.ga9...@galadriel.inutil.org
Processed: Re: inotify closing but id=0 for entry=f3dadc58 in group=f6480180 still in idr. Probably leaking memory
Processing commands for cont...@bugs.debian.org: tags 559207 moreinfo Bug #559207 [linux-2.6] inotify closing but id=0 for entry=f3dadc58 in group=f6480180 still in idr. Probably leaking memory Added tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126713695720995.transcr...@bugs.debian.org
Bug#493832: marked as done (ath5k disconnects regularly and has poor performance)
Your message dated Thu, 25 Feb 2010 23:36:38 +0100 with message-id 20100225223638.ga12...@galadriel.inutil.org and subject line Re: ath5k disconnects regularly and has poor performance has caused the Debian Bug report #493832, regarding ath5k disconnects regularly and has poor performance 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.) -- 493832: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=493832 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-image-2.6.26-1-686 Version: 2.6.26-1 Severity: normal I use kernel's ath5k driver for my Atheros AR5413 based card. I'm always quite close to the AP, and iwconfig shows Signal level=-57 dBm. Despite of it, the card often disconnects (about once in 10 min.) and reconnects again, and always works with bitrates like 1-9 Mbit/s. Trying to higher bitrate manually I get connection loss. This is not happening when I use madwifi (with 2.6.25-2-686 kernel). The antenna in both AP and station is OK, and other cards work OK with this AP, and mine also when using Windows (as MadWifi has other annoying bug, though is usable anyway). -- Package-specific info: ** Version: Linux version 2.6.26-1-686 (Debian 2.6.26-1) (wa...@debian.org) (gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23)) #1 SMP Wed Jul 30 20:02:15 UTC 2008 ** Command line: BOOT_IMAGE=Debian ro root=UUID=2ecae58f-eae1-4d67-b0d6-8f8cc0ecbae2 resume ** Tainted: P (1) ** Kernel log: [ 15.721385] EXT3-fs: mounted filesystem with ordered data mode. [ 19.799440] pci_hotplug: PCI Hot Plug PCI Core version: 0.5 [ 19.939928] Linux agpgart interface v0.103 [ 20.063928] Yenta: CardBus bridge found at :00:14.0 [1071:8351] [ 20.090227] Yenta: Using CSCINT to route CSC interrupts to PCI [ 20.118071] Yenta: Routing CardBus interrupts to PCI [ 20.144030] Yenta TI: socket :00:14.0, mfunc 0x01001022, devctl 0x66 [ 20.455428] uli526x: ULi M5261/M5263 net driver, version 0.9.3 (2005-7-29) [ 21.197674] input: Power Button (FF) as /class/input/input1 [ 21.629222] ACPI: Power Button (FF) [PWRF] [ 21.700608] Yenta: ISA IRQ mask 0x0cf8, PCI irq 17 [ 21.727227] Socket status: 3086 [ 22.060630] input: Sleep Button (CM) as /class/input/input2 [ 22.440541] ACPI: PCI Interrupt :00:15.0[A] - GSI 18 (level, low) - IRQ 18 [ 22.467714] ath5k_pci :00:15.0: registered as 'phy0' [ 22.603474] ACPI: Sleep Button (CM) [SBTN] [ 22.854694] input: Lid Switch as /class/input/input3 [ 23.081220] input: PC Speaker as /class/input/input4 [ 23.204064] ACPI: Lid Switch [LID] [ 23.356214] ACPI: AC Adapter [AC] (off-line) [ 23.558342] ACPI: Battery Slot [BAT0] (battery present) [ 23.753123] phy0: Selected rate control algorithm 'pid' [ 25.385144] ath5k phy0: Atheros AR5413 chip found (MAC: 0xa4, PHY: 0x61) [ 25.412701] ACPI: PCI Interrupt :00:1b.0[A] - GSI 20 (level, low) - IRQ 20 [ 25.466948] eth0: ULi M5263 at pci:00:1b.0, 00:40:d0:8a:93:74, irq 20. [ 25.582788] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4 [ 25.616910] ali1535_smbus :00:1e.1: ALI1535_smb region uninitialized - upgrade BIOS? [ 25.644863] ali1535_smbus :00:1e.1: ALI1535 not detected, module not inserted. [ 25.823693] Synaptics Touchpad, model: 1, fw: 6.2, id: 0xa5a0b1, caps: 0xa04713/0x0 [ 25.901840] input: SynPS/2 Synaptics TouchPad as /class/input/input5 [ 26.021893] cs: IO port probe 0x100-0x3af: clean. [ 26.059196] cs: IO port probe 0x3e0-0x4ff: clean. [ 26.092013] ali15x3_smbus :00:1e.1: ALI15X3_smb region uninitialized - upgrade BIOS or use force_addr=0xaddr [ 26.120043] ali15x3_smbus :00:1e.1: ALI15X3 not detected, module not inserted. [ 26.208382] cs: IO port probe 0x820-0x8ff: clean. [ 26.334433] cs: IO port probe 0xc00-0xcf7: clean. [ 26.450602] ACPI: PCI Interrupt :00:1d.0[A] - GSI 23 (level, low) - IRQ 23 [ 26.492009] cs: IO port probe 0xa00-0xaff: clean. [ 26.581471] intel8x0_measure_ac97_clock: measured 93116 usecs [ 26.610825] intel8x0: clocking to 48000 [ 27.952169] Adding 1012084k swap on /dev/hda4. Priority:-1 extents:1 across:1012084k [ 28.398328] EXT3 FS on hda2, internal journal [ 29.316477] powernow-k8: Found 1 AMD Turion(tm) 64 Mobile Technology ML-32 processors (1 cpu cores) (version 2.20.00) [ 29.377698] powernow-k8:0 : fid 0xa (1800 MHz), vid 0x4 [ 29.409649] powernow-k8:1 : fid 0x8 (1600 MHz), vid 0x6 [ 29.439879] powernow-k8:2 : fid 0x0 (800 MHz), vid 0x16 [ 29.768033] Clocksource tsc unstable (delta = 364052943 ns) [
Bug#558316: netinstall fails with a Realtek RTL8169 Gigabit Ethernet card
On Sat, Nov 28, 2009 at 01:27:50PM +0100, Stefan Lippers-Hollmann wrote: Hi On Saturday 28 November 2009, Emmanuel Blot wrote: Package: netinstall Version: sorry, don't know how to obtain that info, see below for the package reference and date. Hardware: Intel D945GSEJT, Atom processor N270 @1.60Ghz, 1GB DDR2 Technical specs: http://downloadmirror.intel.com/17597/eng/D945GSEJT_TechProdSpec.pdf Software: Debian netinstall dated 05-09-09 04:25, downloaded from http://ftp.nl.debian.org/debian/dists/lenny/main/installer-i386/current/images/netboot/ Linux kernel: 2.6.26-2-486 #1 Wed Aug 19 05:40:02 UTC 2009 [...] The Intel D945GSEJT mainboard ships with a RealTek rtl8168d network card, which wasn't supported before kernel 2.6.31. Be aware that starting with Debian's kernel 2.6.32, you'll need a binary firmware as well (rtl8168d-1.fw and rtl8168d-2.fw), which are not available yet. :eth0: RTL8169 at 0xf882, 00:1c:c0:xx:xx:xx, XID 281000c0 IRQ 219 this seems to be a rtl8168d-2. Emmanuel, you could try the alpha1 installer of the upcoming Squeeze release: http://lists.debian.org/debian-devel-announce/2010/02/msg00011.html (You might need to run a DVD-based installation, though. I'm not sure of the net installer is able to cope with the external non-free firmware) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225222426.ga10...@galadriel.inutil.org
Bug#530593: marked as done ([hal] My camera is not working (A4Tech ViewCam Model: PK-835))
Your message dated Thu, 25 Feb 2010 23:45:35 +0100 with message-id 20100225224535.ga13...@galadriel.inutil.org and subject line Re: [hal] My camera is not working (A4Tech ViewCam Model: PK-835) has caused the Debian Bug report #530593, regarding [hal] My camera is not working (A4Tech ViewCam Model: PK-835) 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.) -- 530593: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=530593 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: hal Version: 0.5.12~git20090406.46dc48-2 Severity: important --- Please enter the report below this line. --- My A4Tech ViewCam Model: PK-835 is not recognized. It does not work in Cheese, Skype, etc. at all. Cheese reports: No Camera Found! Reproducible: Always The same bug under Ubuntu 64-bit edition. There is no problem under the 32-bit version (the camera is working out-of-the-box). I have not tested the 32-bit version of Debian, yet, to see whether it works under it, too. This is what dmesg says after I plugged in the camera: [ 6443.389852] usb 4-2: new full speed USB device using uhci_hcd and address 3 [ 6443.578056] usb 4-2: configuration #1 chosen from 1 choice [ 6443.585047] usb 4-2: New USB device found, idVendor=0ac8, idProduct=303b [ 6443.585057] usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 6443.585061] usb 4-2: Product: PC Camera [ 6443.585065] usb 4-2: Manufacturer: Vimicro Corp. [ 6443.997743] Linux video capture interface: v2.00 [ 6444.025967] zc0301: V4L2 driver for ZC0301[P] Image Processor and Control Chip v1:1.10 [ 6444.025967] usb 4-2: ZC0301[P] Image Processor and Control Chip detected (vid/pid 0x0AC8:0x303B) [ 6444.094589] usb 4-2: No supported image sensor detected [ 6444.094589] usbcore: registered new interface driver zc0301 --- System information. --- Architecture: amd64 Kernel: Linux 2.6.26-2-amd64 Debian Release: squeeze/sid 500 testing ftp.bg.debian.org 500 stable volatile.debian.org 500 stable security.debian.org 500 stable ftp.bg.debian.org 500 stable debian.ipacct.com 500 proposed-updates ftp.bg.debian.org --- Package information. --- Depends(Version) | Installed -+- libc6 (= 2.3) | 2.9-12 libdbus-1-3 (= 1.0.2) | 1.2.12-1 libdbus-glib-1-2 (= 0.78) | 0.80-4 libexpat1(= 1.95.8) | 2.0.1-4 libgcc1 (= 1:4.1.1) | 1:4.4.0-5 libglib2.0-0 (= 2.16.0) | 2.20.1-2 libhal-storage1 (= 0.5.11~rc2) | 0.5.12~git20090406.46dc48-2 libhal1 (= 0.5.10) | 0.5.12~git20090406.46dc48-2 libpolkit2 (= 0.7) | 0.9-3 libsmbios2 | 2.0.3.dfsg-1 libstdc++6(= 4.1.1) | 4.4.0-5 libusb-0.1-4 (= 2:0.1.12) | 2:0.1.12-13 libvolume-id1 (= 0.140-1) | 0.141-1 adduser | 3.110 pciutils | 1:3.1.2-3 usbutils | 0.73-10 udev (= 0.125) | 0.141-1 dbus (= 0.61) | 1.2.12-1 lsb-base (= 3.2-14) | 3.2-22 hal-info (= 20070402) | 20090309-1 pm-utils | 1.2.5-2 mount (= 2.13) | 2.13.1.1-1 policykit (= 0.7) | 0.9-3 consolekit (= 0.3) | 0.3.0-2 acl | 2.2.47-2 Recommends (Version) | Installed -+-=== eject| 2.1.5+deb1+cvs20081104-6 libsmbios-bin| Suggests (Version) | Installed ===-+-=== gnome-device-manager| ---End Message--- ---BeginMessage--- On Tue, Aug 25, 2009 at 11:33:59PM +0200, Moritz Muehlenhoff wrote: On Fri, Jun 05, 2009 at 11:40:20PM +0100, Ben Hutchings wrote: The gspca driver may handle this camera properly. Please try installing gspca-modules-2.6-amd64 and report whether this makes the camera work. Miro, did you test this? No further feedback, closing the bug. If this can be reproduced with current kernels, please reopen this bug. Cheers, Moritz ---End Message---
Bug#500834: marked as done (linux-package: the time of day value of date is set to UTC value)
Your message dated Thu, 25 Feb 2010 23:42:25 +0100 with message-id 20100225224225.ga13...@galadriel.inutil.org and subject line Re: need more information has caused the Debian Bug report #500834, regarding linux-package: the time of day value of date is set to UTC value 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.) -- 500834: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500834 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: linux-package Version: 2.6.18-6-486 Severity: normal -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-6-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) This is a multi OS Dell Dimension E521 system with dual core AMD64. When I boot the system in Debian Linux i386 the time of the day is incorrect: it says PDT as expected, but the value is the UTC value. When I boot the system in Debian Linux amd64 everything is OK. When I boot the system in Windws Vista (32 bit) things are OK. I found the following workaround: In /etc/init.d/hwclock.sh do the following change: /etc/init.d 48 diff hwclock.sh.orig hwclock.sh 21c21 HWCLOCKPARS= --- HWCLOCKPARS=--directisa I needed to make this change only in the hwclcock.sh file of the i386 linux OS. ---End Message--- ---BeginMessage--- On Sun, Jul 26, 2009 at 02:56:45PM +0200, Moritz Muehlenhoff wrote: On Sat, Jan 03, 2009 at 03:44:50PM -0800, Peter Farkas wrote: Hello Bastian and Moritz, Sorry for not responding more promptly, I was too busy with various other things. Today I wanted to test the fix. However, I am not that familiar with finding and testing kernels, so after about an hour of trying to find the necessary information, I gave up. I would be happy to test the new kernel, but in order to do it I need to know where to get it from, and how to install it. Regards, The kernel mentioned by Bastian is the kernel from the current Debian stable (version 5.0 aka Lenny). Your report was filed against the previous release, so this would involve a system update. Closing. Please reopen if the bug persists with Lenny or later. Cheers, Moritz ---End Message---
Bug#517108: marked as done (base: Couldn't get CPU usage for each process)
Your message dated Thu, 25 Feb 2010 23:44:51 +0100 with message-id 20100225224451.ga13...@galadriel.inutil.org and subject line Re: base: Couldn't get CPU usage for each process has caused the Debian Bug report #517108, regarding base: Couldn't get CPU usage for each process 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.) -- 517108: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=517108 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: base Severity: normal I couldn't get CPU usage for each process, the column of %CPU was always showing 0.00. I first found this when using conky, then I found ps, top and xfce4-taskmanager having the same problem. By the way, I can get the total CPU usage correctly. Because ps and top are in package procps and depend on libproc, I thought there may be something wrong with the libproc. But xfce4-taskmanager doesn't depends on it, so maybe something wrong with my kernel, then I reinstalled package linux-image-2.6.26-1-686. Nothing changs. Thanks for help! -- System Information: Debian Release: 5.0 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash ---End Message--- ---BeginMessage--- On Tue, Jun 30, 2009 at 07:02:48PM +0100, Ben Hutchings wrote: Do you still see this problem in the latest stable kernel package (package name linux-image-2.6.26-2-686, version 2.6.26-17)? No further feedback, closing the bug. If this can be reproduced with current kernels, please reopen this bug. Cheers, Moritz ---End Message---
Bug#512083: marked as done (libsensors3: Troubles with CPU FAN speed control)
Your message dated Thu, 25 Feb 2010 23:43:27 +0100 with message-id 20100225224327.gb13...@galadriel.inutil.org and subject line closing has caused the Debian Bug report #512083, regarding libsensors3: Troubles with CPU FAN speed control 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.) -- 512083: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=512083 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Subject: libsensors3: Troubles with CPU FAN speed control Package: libsensors3 Version: 1:2.10.7-1 Severity: normal -- System Information: Debian Release: 5.0 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.26-1-486 Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libsensors3 depends on: ii libc6 2.7-16 GNU C Library: Shared libraries ii libsysfs2 2.1.0-5interface library to sysfs ii makedev 2.3.1-88 creates device files in /dev ii ucf 3.0011 Update Configuration File: preserv ii udev 0.125-7/dev/ and hotplug management daemo libsensors3 recommends no packages. Versions of packages libsensors3 suggests: pn lm-sensorsnone (no description available) -- no debconf information I have the next troubles with CPU FAN speed control on my notebook. I had no CPU FAN speed control (cooler works on full speed all the time) on GNU/Linux at all about a year, but on MS Windows XP FAN speed control was nice. I thinked my Linux can't see how to control FAN speed. Few days ago I tried to use Sleep mode. It works fine. But when I boot my notebook from sleep mode... FAN speed control started to work fine! I checked this effect some times and result was the same. I understand, that some more information about my hardware are needed, but I don't know what exactly I should to send. Say me, what information I should to send or what command output line I should to send. Now I can say, that almost all chips manufactured by VIA company: north and south bridges, network card, sound card, and even CPU (VIA C7-M, 1500MHz). And I think some confusion with terms is possible: In my language modes called Sleeping mode and Waiting mode (I sayd about sleeping one), but I not sure how they are called in English. Sorry for terreble English. Best regards, Ilia. ---End Message--- ---BeginMessage--- closing ---End Message---
Bug#559342: linux-image-2.6.30-2-686: USB Devices managed by uhci_hcd fail to mount
tags 559342 moreinfo thanks On Sat, Dec 19, 2009 at 11:25:40AM +0100, Eugenio M. Vigo wrote: Hi again. I've been investigating further on these issues and I'm glad to tell you that the HP DeskJet F380 scanning issue was actually about permissions, exactly the bug stated here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522848 But the SGH-L760V's issue is still open and can't spot any other symptom that may point elsewhere than a bug in the kernel. Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem with the SGH-L760V persists. It's likely not fully standards compliant and might need the selection of a few workarounds. If the problm persists we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225223256.ga11...@galadriel.inutil.org
Bug#559207: inotify closing but id=0 for entry=f3dadc58 in group=f6480180 still in idr. Probably leaking memory
tags 559207 moreinfo thanks On Wed, Dec 02, 2009 at 02:25:47PM -0500, Anthony DeRobertis wrote: Package: linux-2.6 Version: 2.6.31-2 Severity: normal This warning showed up in my kernel logs, as I either logged out or in (to a e16/KDE desktop, logged in using gdm). Hi, The next release of Debian (6.0, code name Squeeze) will be based on 2.6.32. Please test the current 2.6.32 from unstable/testing and tell us whether the problem persists. If so, we should report it upstream to the kernel.org developers. The 2.6.32 kernel is available from packages.debian.org and can be installed in both Debian stable, testing and unstable installations. Thanks, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225222905.ga11...@galadriel.inutil.org
Bug#372161: marked as done (kernel-package: README.modules: User instructions are incomplete and misleading)
Your message dated Thu, 25 Feb 2010 23:59:01 +0100 with message-id 20100225225901.ga15...@galadriel.inutil.org and subject line Re: Reopen, bug not solved has caused the Debian Bug report #372161, regarding kernel-package: README.modules: User instructions are incomplete and misleading 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.) -- 372161: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=372161 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: kernel-package Version: 10.047 Severity: normal I tried to compile third-party modules for 2.6.16, following the description in README.modules. It turned out that the descriptions could and should be improved. Below USER INSTRUCTIONS, the second item says: , | 2) Get kernel sources from your favorite location. (For | pre-packaged kernels, it may be possible to build third | party modules by getting the kernel-headers package that | corresponds to the kernel-image package you have installed, | and pointing the build system of the kernel headers -- some | packaged modules packages provide an easy way to use the | kernel-headers packages, by allowing you to specify it like so: |[cd $MODULE_LOC/$module/; | ./debian/rules KSRC=/usr/src/kernel-headers-X.Y.ZZ binary | ]) ` I'm using a debian kernel, and therefore wanted to try the headers only way. However, the command above does not work, since make-kpkg must first create the debian/ subdirectory in the modules directories. Maybe you mean prepackaged modules - but I was using the sources for three modules packaged for non-free, madwifi, thinkpad and fglrx, and those come with tarballs in /usr/src/ that do not contain a debian/ subdirectory. I don't know whether any prepackaged module debs exist that already contain a debian/ directory. Anyway, it should be explained how it's possible to compile modules with headers only for any kind of module sources. So this method does not work. I then fetched the complete kernel sources, unpacked them to /usr/src/linux-source-2.6.16/, copied /boot/config-2.6.16-2-686 to .config and further followed the instructions: , | 5) If you are building a kernel that is custom configured to your | specifications at this time, go ahead and configure the | kernel with `make config', `make menuconfig', or `make | xconfig.' To build a new kernel-image package, execute: | make-kpkg --revision number kernel_image ` So the configure part is done, but I don't want to build a new kernel-image package at all, so I skipped this part. , | 6) To build the actual module packages, execute: | make-kpkg modules_image | This will generate a name-modules-kernel version.deb file in | the parent directory. The revision you supplied while building the | kernel shall be used automatically. | | If you are using an official Debian kernel-image with specific | options (kernel-image-x.y.z-foo), you should append this version | for modules compilation: | make-kpkg --append-to-version -foo modules_image ` Since this refers to using official Debian kernels, and it doesn't make sense to recreate the kernel image then, I thought it should also work this way. But it doesn't. First, make-kpkg complains that I need to run at least make-kpkg debian first. I did that, but after that include/linux/version.h does not exist, and I get an error message that versions don't match (the one from version.h is, well, the empty string). This is the only point where I think not only README.modules needs adjustment, but also the error message from make-kpkg: It should tell me what I have to run to make the modules_image target actually work. Since I and my computer had enough time, I just compiled a (useless) kernel image along with the modules images, and that worked fine. I've also been told that I could have used module-assistant which would download the needed headers for me. But I think the information in README.modules should be better understandable and more correct. Unfortunately I don't know yet how I should have proceeded, and therefore cannot provide a better text. If this bug report leads to a discussion after which I know better how to do it, I offer to write a patch. But maybe you already have something prepared, or it can be copied from somewhere? Regards, Frank -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (99, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.16-2-686 Locale:
Processed: tagging 536183
Processing commands for cont...@bugs.debian.org: tags 536183 - moreinfo Bug #536183 [linux-2.6] Can't change CPU scaling governor after .29 to .30 upgrade. Removed tag(s) moreinfo. 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 Archive: http://lists.debian.org/handler.s.c.126713892028246.transcr...@bugs.debian.org
Bug#512083: libsensors3: Troubles with CPU FAN speed control
On Sun, Jul 26, 2009 at 02:46:03PM +0200, Moritz Muehlenhoff wrote: On Sat, Jan 17, 2009 at 02:50:45AM +0300, Ilia Lilov wrote: I have the next troubles with CPU FAN speed control on my notebook. I had no CPU FAN speed control (cooler works on full speed all the time) on GNU/Linux at all about a year, but on MS Windows XP FAN speed control was nice. I thinked my Linux can't see how to control FAN speed. Few days ago I tried to use Sleep mode. It works fine. But when I boot my notebook from sleep mode... FAN speed control started to work fine! I checked this effect some times and result was the same. I understand, that some more information about my hardware are needed, but I don't know what exactly I should to send. Say me, what information I should to send or what command output line I should to send. Now I can say, that almost all chips manufactured by VIA company: north and south bridges, network card, sound card, and even CPU (VIA C7-M, 1500MHz). And I think some confusion with terms is possible: In my language modes called Sleeping mode and Waiting mode (I sayd about sleeping one), but I not sure how they are called in English. Sorry for terreble English. Best regards, Ilia. Does this error persist with 2.6.30 from unstable? No further feedback, closing the bug. If this can be reproduced with current kernels, please reopen this bug. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100225224304.ga13...@galadriel.inutil.org
Bug#435387: marked as done (netatalk: Atalkd won't start up with Token Ring Interface)
Your message dated Fri, 26 Feb 2010 00:08:55 +0100 with message-id 20100225230855.ga16...@galadriel.inutil.org and subject line Re: Bug#435387: Redirect to Kernel? has caused the Debian Bug report #435387, regarding netatalk: Atalkd won't start up with Token Ring 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.) -- 435387: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=435387 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: netatalk Version: 2.0.3-4 Severity: important After installing netatalk, stopping, putting tr0 (as it's the only interface the machine has) and starting up again, syslog states: setifaddr: tr0 (65280-65534): Protocol not supported. try specifying a smaller net range. The above range is a range where atalk starts up every time to discover the real net range afterwards. Seems as if atalkd doesn't support Token Ring at all. Accessing AFP over IP works just fine but there's no native AppleTalk support available. -- System Information: Debian Release: 4.0 APT prefers oldstable APT policy: (500, 'oldstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-3-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages netatalk depends on: ii libc62.3.6.ds1-13GNU C Library: Shared libraries ii libcupsys2 1.2.7-4 Common UNIX Printing System(tm) - ii libdb4.2 4.2.52+dfsg-2 Berkeley v4.2 Database Libraries [ ii libgssapi4-heimdal 0.7.2.dfsg.1-10 Libraries for Heimdal Kerberos ii libkrb5-17-heimdal 0.7.2.dfsg.1-10 Libraries for Heimdal Kerberos ii libpam-modules 0.79-4 Pluggable Authentication Modules f ii libpam-runtime 0.79-4 Runtime support for the PAM librar ii libpam0g 0.79-4 Pluggable Authentication Modules l ii libslp1 1.2.1-6.2 OpenSLP libraries ii libwrap0 7.6.dbs-13 Wietse Venema's TCP wrappers libra ii netbase 4.29Basic TCP/IP networking system ii perl 5.8.8-7 Larry Wall's Practical Extraction Versions of packages netatalk recommends: pn db4.2-utilnone (no description available) pn lsof none (no description available) pn rcnone (no description available) ii slpd 1.2.1-6.2 OpenSLP Server (slpd) -- no debconf information ---End Message--- ---BeginMessage--- On Tue, Dec 01, 2009 at 02:58:11PM +0100, Bjørn Mork wrote: Patrik Schindler p...@pocnet.net writes: Good point. But Token Ring Card drivers already exist, even if there is likely not a very much bigger demand. :-) Well, they do exist but they are probably going away too. I don't see anyone really interested in hacking on them, so they are staying just as long as they continue to work. Which may not be that long... E.g. my nice triple lanstreamer card doesn't work after upgrading the rest of the system to 64bit, as the original driver does a whole lot of magic DMA access and no-one has cleaned it up for 64bit. So the driver is disabled for 64bit systems. I don't think anyone will bother to fix it. I briefly looked at it, and found that there's definitely a reason why this was just disabled. It's a mess. The card is in the attic now, with the rest of my Token Ring stuff. Except for a Cisco 2612 which serves as an Ethernet/Serial only router. Let's just close the bug, then. Cheers, Moritz ---End Message---
