Bug#386656: Please provide vserver flavour(s) for sparc
Package: linux-2.6 Severity: wishlist On Fri, 8 Sep 2006, Maciej Jan Broniarz wrote: Hi, Where can I find linux kernel packages with vserver enabled ? There none of those in etch/sid. I've discussed it with some other members of the kernel team, and it turned out that vserver patches are supported on sparc, and there are other people who are interested in it. It seems that there is no good reason not to provide a vserver-enabled kernel, so I'm filing this wishlist bug to keep track of the progress (I'll try to look into it in the nearest future). Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#385574: Dom0 crashes with linux-image-2.6.16-2-xen-686
Hi, Same problem here, version 2.6.16-18 gets the same trace as posted to the bug before. Version 2.6.16-16 works fine. Samuel -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386674: Dom0 crashes with linux-image-2.6.17-2-xen-686=2.6.17-8
Package: linux-image-2.6.17-2-xen-686 Version: 2.6.17-8 Severity: important Hi, I can't boot linux-image-2.6.17-2-xen-686=2.6.17-8 as Dom0 with hypervisor xen-hypervisor-3.0-i386=3.0.2+hg9697-2. I get a crash very early (seemingly before Linux prints anything). Unfortunately, I don't have any mean to get the output: the last thing I can see is the Guest stack trace, full of . Regards, Samuel -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-xen-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.17-2-xen-686 depends on: ii initramfs-tools 0.77b tools for generating an initramfs ii linux-modules-2.6.17-2-xen-68 2.6.17-8 Linux 2.6.17 modules on PPro/Celer Versions of packages linux-image-2.6.17-2-xen-686 recommends: ii libc6-xen2.3.6.ds1-4 GNU C Library: Shared libraries [X -- no debconf information -- Samuel Thibault [EMAIL PROTECTED] $ du temp.iso 2,0Ttemp.iso $ ls temp.iso -l -r-xr-xr-x1 samy thibault 16E 2003-03-22 14:44 temp.iso* -+- je vous dirai pas la marque de mon disque dur, na :p -+- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#386667: apcupsd: Causes kernel oops
Processing commands for [EMAIL PROTECTED]: reassign 386667 kernel-image-2.4.27-i386 Bug#386667: apcupsd: Causes kernel oops Bug reassigned from package `apcupsd' to `kernel-image-2.4.27-i386'. severity 386667 important Bug#386667: apcupsd: Causes kernel oops Severity set to `important' from `critical' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386674: marked as done (Dom0 crashes with linux-image-2.6.17-2-xen-686=2.6.17-8)
Your message dated Sat, 9 Sep 2006 13:35:07 +0200 with message-id [EMAIL PROTECTED] and subject line Bug#386674: Dom0 crashes with linux-image-2.6.17-2-xen-686=2.6.17-8 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: linux-image-2.6.17-2-xen-686 Version: 2.6.17-8 Severity: important Hi, I can't boot linux-image-2.6.17-2-xen-686=2.6.17-8 as Dom0 with hypervisor xen-hypervisor-3.0-i386=3.0.2+hg9697-2. I get a crash very early (seemingly before Linux prints anything). Unfortunately, I don't have any mean to get the output: the last thing I can see is the Guest stack trace, full of . Regards, Samuel -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-xen-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages linux-image-2.6.17-2-xen-686 depends on: ii initramfs-tools 0.77b tools for generating an initramfs ii linux-modules-2.6.17-2-xen-68 2.6.17-8 Linux 2.6.17 modules on PPro/Celer Versions of packages linux-image-2.6.17-2-xen-686 recommends: ii libc6-xen2.3.6.ds1-4 GNU C Library: Shared libraries [X -- no debconf information -- Samuel Thibault [EMAIL PROTECTED] $ du temp.iso 2,0Ttemp.iso $ ls temp.iso -l -r-xr-xr-x1 samy thibault 16E 2003-03-22 14:44 temp.iso* -+- je vous dirai pas la marque de mon disque dur, na :p -+- ---End Message--- ---BeginMessage--- On Sat, Sep 09, 2006 at 12:45:04PM +0200, Samuel Thibault wrote: I can't boot linux-image-2.6.17-2-xen-686=2.6.17-8 as Dom0 with hypervisor xen-hypervisor-3.0-i386=3.0.2+hg9697-2. This versions are not compatible for a dom0. Bastian -- Klingon phaser attack from front! 100% Damage to life support signature.asc Description: Digital signature ---End Message---
Bug#386674: closed by Bastian Blank [EMAIL PROTECTED] (Re: Bug#386674: Dom0 crashes with linux-image-2.6.17-2-xen-686=2.6.17-8)
Debian Bug Tracking System, le Sat 09 Sep 2006 04:49:16 -0700, a écrit : On Sat, Sep 09, 2006 at 12:45:04PM +0200, Samuel Thibault wrote: I can't boot linux-image-2.6.17-2-xen-686=2.6.17-8 as Dom0 with hypervisor xen-hypervisor-3.0-i386=3.0.2+hg9697-2. This versions are not compatible for a dom0. Ah. But which kernel package should I use then? Samuel
Bug#344375: Try skge or sky2 instead of sk98lin
The sk98lin driver is unmaintained and will be dropped from linux in the future. Try the skge or sky2 modules instead (one of them should support your card). Both modules should be available in the current version of the kernel that's available in unstable/testing Regards, Andreas Henriksson -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#386721: udev postinst should issue a warning if initrd could not be updated
Processing commands for [EMAIL PROTECTED]: reassign 386721 initramfs-tools Bug#386721: udev postinst should issue a warning if initrd could not be updated Bug reassigned from package `udev' to `initramfs-tools'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Bug#386721: udev postinst should issue a warning if initrd could not be updated
reassign 386721 initramfs-tools thanks udev postinst scripts actually _do_ try to update the initrd, but update-initramfs systematically fails because initrd was modified (or customized, I don't remember exactly what it says). -- ciao, Marco signature.asc Description: Digital signature
Bug#386667: apcupsd: Causes kernel oops
Steve Langasek wrote: reassign 386667 kernel-image-2.4.27-i386 severity 386667 important thanks On Sat, Sep 09, 2006 at 07:15:56PM +1000, Peter Dey wrote: Package: apcupsd Version: 3.10.17-2 Severity: critical Justification: breaks the whole system The kernel on my system has Oopses, on average, twice a month, since installing apcupsd. In all Oops cases, apcupsd has been listed as the process in kern.log. Since the instructions its oopsing on are fairly generic (sys_ioctl and exit_sighand), I'm guessing apcupsd is somehow managing to cause the oops... However, a kernel oops is always a kernel bug. Given that apcupsd doesn't contain any kernel modules, I'm reassigning this to the corresponding kernel package. I'm also lowering the severity, since from the kernel POV this bug doesn't make the kernel unusable, it just makes it impossible to use apcupsd with this kernel. will forward this bug to apcupsd mantainer, maybe they have some clue about it . Regards Samuele -- While various networks have become deeply rooted, and thoughts have been sent out as light and electrons in a singular direction, this era has yet to digitize/computerize to the degree necessary for individuals to become a singular complex entity. KOUKAKU KIDOUTAI Stand Alone Complex -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
