Package: kernel-image-2.6.8-1-686
Version: 2.6.8-3
Severity: critical
Justification: breaks the whole system
I can only report this bug because I have three Debian Sid systems.
A bug in something, I suspect the kernel package, just ate two of them.
I was running fully updated Debian Sid systems on
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.4
> severity 274144 normal
Bug#274144: install freezes during network setup
Severity set to `normal'.
>
End of message, stopping processing here.
Please contact me if you need assistance
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.8.4
> reassign 274144 kernel
Bug#274144: install freezes during network setup
Bug reassigned from package `debian-installer' to `kernel'.
>
End of message, stopping processing here.
Please
On Wed, Sep 29, 2004 at 11:47:20PM +0200, Christoph Hellwig wrote:
> On Wed, Sep 29, 2004 at 10:54:21PM +0100, Luke Kenneth Casson Leighton wrote:
> > On Wed, Sep 29, 2004 at 10:33:28PM +0200, Christoph Hellwig wrote:
> > > On Wed, Sep 29, 2004 at 09:14:20PM +0100, Luke Kenneth Casson Leighton
> >
On Wed, Sep 29, 2004 at 10:54:21PM +0100, Luke Kenneth Casson Leighton wrote:
> On Wed, Sep 29, 2004 at 10:33:28PM +0200, Christoph Hellwig wrote:
> > On Wed, Sep 29, 2004 at 09:14:20PM +0100, Luke Kenneth Casson Leighton
> > wrote:
> > > it's not a severe performance penalty.
> > >
> > > especia
On Wed, Sep 29, 2004 at 10:33:28PM +0200, Christoph Hellwig wrote:
> On Wed, Sep 29, 2004 at 09:14:20PM +0100, Luke Kenneth Casson Leighton wrote:
> > it's not a severe performance penalty.
> >
> > especially when it's disabled by default with "selinux=0".
>
> Yes, all the indirect calls due to C
maks attems wrote:
tags 260971 moreinfo
thanks
On Thu, 22 Jul 2004, Daniel Burton wrote:
..
My system stops and becomes completely unresponsive, both locally and
over the network at random times, usually within two hours of booting on
this kernel version. It is okay on version 2.6.5-1-k7. Th
On Wed, Sep 29, 2004 at 09:14:20PM +0100, Luke Kenneth Casson Leighton wrote:
> it's not a severe performance penalty.
>
> especially when it's disabled by default with "selinux=0".
Yes, all the indirect calls due to CONFIG_SECURITY are a performance
penalty.
well... sort-of!
> please submit your patch upstream at the netfilter team,
> debian mostly uses vanilla linus sources.
>
> there devel list is at [EMAIL PROTECTED]
> i assume you know http://www.netfilter.org/ . ;)
>
> --
> maks
> kernel janitorhttp://janitor.kernelnewbies.org/
>
--
it's not a severe performance penalty.
especially when it's disabled by default with "selinux=0".
On Wed, Sep 29, 2004 at 08:33:08AM -0700, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> #249510: kernel-image-2.6.5-1-686: can SELinux please be
Your message dated Wed, 29 Sep 2004 21:44:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line i823650 does not have a release() function
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
Your message dated Wed, 29 Sep 2004 21:44:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line i823650 does not have a release() function
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
do you still experience mouse problems,
if yes this should probably be rassigned to xfree,
or could you fix your XF86Config-4 inbetween?
thanks for feedback.
--
maks
kernel janitor http://janitor.kernelnewbies.org/
Your message dated Wed, 29 Sep 2004 21:16:31 +0200
with message-id <[EMAIL PROTECTED]>
and subject line problem resolved
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
Hi!
> do you still experience this with current 2.6.8 kernels in testing?
The described problems came from GNOME Startup and Mozilla Proxy Auto
Configuration, as I discovered later. I didn' try if GNOME starts faster
if I disable IPv6 because I used it compiled in the kernel (as opposed
to loadin
tags 260971 moreinfo
thanks
On Thu, 22 Jul 2004, Daniel Burton wrote:
..
> My system stops and becomes completely unresponsive, both locally and
> over the network at random times, usually within two hours of booting on
> this kernel version. It is okay on version 2.6.5-1-k7. There is no
> wa
Processing commands for [EMAIL PROTECTED]:
> tags 260971 moreinfo
Bug#260971: Random System Hangs
There were no tags set.
Tags added: moreinfo
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs databa
Your message dated Wed, 29 Sep 2004 19:58:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Hairy upgrade
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 re
Christoph Hellwig a écrit :
> On Mon, Sep 13, 2004 at 09:37:23AM +0200, Milan Kuchta wrote:
>
>>Package: kernel-image
>>Version: 2.6.8-1-k7
>>Severity: critical
[...]
>>Kernel panic: Attempted to kill init!
>
> This looks very much like you're missing an initrd or something. How
> does your lilo/g
On Wed, 29 Sep 2004, Jeroen van Wolffelaar wrote:
> Hi,
>
> | Package: kernel-patch-2.4-kgdb (1.9-1)
> | GDB debugging for the kernel
> |
> | This package provides the patches for the 2.4.23 kernel (and should
> | apply to other nearby versions) for the i386 and powerpc architectures.
> | It all
On Wed, 29 Sep 2004, Marcus C. Gottwald wrote:
> maks attems wrote (Tue 2004-Sep-28 23:09:22 +0200):
> > could you try to build latest kernel-source-2.6.8
> > with belows reverted patch and boot that?
>
> All right, I did:
..
great thanks!
> - dmesg shows "broken BIOS detected" again.
> - Funct
On Wed, Sep 29, 2004 at 05:36:30PM +0200, maks attems wrote:
> retitle 272029 add xbox support to debians kernel
> thanks
>
> [...]
>
> well so keep 1 "bug" not 3.
> retitled, and i'll close the other 2.
Have you read the bug reports? I haven't sent ANY patch for Xbox support.
Why do you close
On Wed, 29 Sep 2004, Robert Millan wrote:
> On Wed, Sep 29, 2004 at 05:36:30PM +0200, maks attems wrote:
>
> Have you read the bug reports? I haven't sent ANY patch for Xbox support.
> Why do you close bug reports without even reading them to understand what the
> requests are? Please read all
Your message dated Wed, 29 Sep 2004 18:39:18 +0200
with message-id <[EMAIL PROTECTED]>
and subject line ISAPNP modem in debian kernel
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 resp
Processing commands for [EMAIL PROTECTED]:
> tags #162132 upstream
Bug#162132: kernel-source-2.4.19: awk segfault on make menuconfig to compile
kernel
There were no tags set.
Bug#147469: menuconfig: crash due to infinite recursion (gawk)
Tags added: upstream
> tags #147469 upstream
Bug#147469: m
Your message dated Wed, 29 Sep 2004 17:37:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line xbox support
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 reo
retitle 272029 add xbox support to debians kernel
thanks
On Sun, 26 Sep 2004, Robert Millan wrote:
> On Sat, Sep 25, 2004 at 12:16:55PM +0900, Horms wrote:
> > tag 272029 +wontfix
> >
> > > It's not fixed. Add a wontfix and/or upstream tags if you like.
> >
> > This is not a bug in the kernel
Processing commands for [EMAIL PROTECTED]:
> retitle 272029 add xbox support to debians kernel
Bug#272029: FATX filesystem support
Changed Bug title.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrator, Debian Bugs
Your message dated Wed, 29 Sep 2004 17:30:20 +0200
with message-id <[EMAIL PROTECTED]>
and subject line iptables patch
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 r
Your message dated Wed, 29 Sep 2004 17:27:29 +0200
with message-id <[EMAIL PROTECTED]>
and subject line No kernel-image for 586-SMP machines
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 yo
Your message dated Wed, 29 Sep 2004 17:19:57 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Wireless Driver for ADM8211 chips
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
Your message dated Wed, 29 Sep 2004 17:18:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line lfs-patch to smbfs
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
Your message dated Wed, 29 Sep 2004 17:12:42 +0200
with message-id <[EMAIL PROTECTED]>
and subject line selinux in debian kernel
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 responsib
Your message dated Wed, 29 Sep 2004 17:09:38 +0200
with message-id <[EMAIL PROTECTED]>
and subject line no more targets
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
Your message dated Wed, 29 Sep 2004 17:08:14 +0200
with message-id <[EMAIL PROTECTED]>
and subject line use make-kpkg
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 re
Your message dated Wed, 29 Sep 2004 17:05:05 +0200
with message-id <[EMAIL PROTECTED]>
and subject line old limit
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
Hi,
Sorry, if this is not directly related to the kernel mailing list, but
this has been driving me mad.
I've made several kernels using make-kpkg
(from kernel-package unstable), using the
debian kernel-source-2.6.7, with the following command:
make-kpkg --append_to_version=-k7.bootsplash --initr
On Wednesday 29 September 2004 04:58, Bluefuture wrote:
> In the meantime fbsplash will be officially introduced in debian, and
> the debian kernel maintainers introduce fbsplash patch in the official
> debian patch applied to the kernel i had founded this little howto for
> people that want to hav
Le Wed, Sep 29, 2004 at 02:11:55PM +0200, Martin Steigerwald ecrit :
> Here is stops. The machine does not react to Ctrl-Alt-Del. Nothing
> happens.
> I press the power button for some time to switch off the machine. And then
> I booted with 2.6.7-1 again.
> Hope that this helps a bit.
I had th
Hello,
now I tried booting the kernel from the package kernel-image-2.6.8-1-686
(version 2.6.8-3) without the "vga=791" parameter like this:
title Debian GNU/Linux, kernel 2.6.8-1-686
root(hd0,4)
kernel /boot/vmlinuz-2.6.8-1-686 root=/dev/hda5 ro
initrd /
maks attems wrote (Tue 2004-Sep-28 23:09:22 +0200):
> > I never used a "noacpi" command, always "acpi=off". And as far
> > as I could see, ACPI was never turned on, only the messages
> > regarding (the local?) APIC were different.
>
> could you try to build latest kernel-source-2.6.8
> with belo
* maks attems <[EMAIL PROTECTED]> [2004-09-29 00:09]:
> To: [EMAIL PROTECTED]
> do you still experience this with current 2.6.8 kernels in testing?
This mail did not go to the bug submitter. You have to CC them or use
[EMAIL PROTECTED]
--
Martin Michlmayr
[EMAIL PROTECTED]
Package: kernel-image-2.6.8-1-686
Version: 2.6.8-3
Severity: normal
After upgrading kernel-image-2.6.8-1-686 from 2.6.8-2 to 2.6.8-3, APM is
not able to power off my system after shutdown. I think it's related to
bug #273474.
Up to 2.6.8-2, the kernel was able to power down the system after
modpr
43 matches
Mail list logo
