Bug#297232: kernel-image-2.6.10-1-k7: kernel panic on boot, now all installed kernels fail (backup recovery required)

2005-02-27 Thread Oliver Lange
Package: kernel-image Version: 2.6.10-1-k7 Hello everyone, After installing kernel-image-2.6.10-1-k7, i tried to reboot, but the following error occurs: pivot_root: No such file or directory /sbin/init: 431: cannot open dev/console: No such file kernel panic: Attempted to kill init! The s

Bug#268583: pciehp hotplug error

2005-02-27 Thread Matt Taggart
I'm also seeing the problem with hotplug trying to load pciehp/shpchp. pciehp: acpi_pciehprm:\_SB_.PCI0 evaluate _BBN fail=0x5 pciehp: acpi_pciehprm:get_device PCI ROOT HID fail=0x5 pciehp: can't be loaded missing kernel or user mode driver pciehp shpchp: acpi_shpchprm:\_SB_.PCI0 e

Bug#288787: IPTables does not work with kernel 2.6.8 - reassign to iptables and merge with other bugs

2005-02-27 Thread Frederik Schueler
severity 288787 wishlist reassign 288787 iptables merge 282474 288787 thanks -- ENOSIG

Processed: IPTables does not work with kernel 2.6.8 - reassign to iptables and merge with other bugs

2005-02-27 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 288787 wishlist Bug#288787: IPTables does not work with kernel 2.6.8 Severity set to `wishlist'. > reassign 288787 iptables Bug#288787: IPTables does not work with kernel 2.6.8 Bug reassigned from package `kernel-image-2.6.8-10-amd64-k8' to `i

Bug#287934: marked as done (kernel-image-2.6.9-9-amd64-k8: kernel: drivers/usb/input/hid-core.c: input irq status -84 received)

2005-02-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Feb 2005 23:25:29 +0100 with message-id <[EMAIL PROTECTED]> and subject line kernel-image-2.6.9-9-amd64-k8: kernel: drivers/usb/input/hid-core.c: input irq status -84 received has caused the attached Bug report to be marked as done. This means that you claim that the pr

Bug#297203: kernel-source-2.6.8: race which could allow for privilege escalation on Radeon

2005-02-27 Thread Stefan Fritsch
Package: kernel-source-2.6.8 Version: 2.6.8-13 Severity: critical Tags: security Justification: root security hole There is a race condition in the radeon driver which has been fixed in 2.6.11-rc4. This is part of BID-12555: http://www.securityfocus.com/bid/12555 The same code is already in 2.6.8

A custom Logo that expresses your company! (13943913)

2005-02-27 Thread Domingo Hardy
Have our designers creates a custom logo for you, with a step-by-step process based on your needs. Our extensive experience allows us to create a logo that makes a statement that is unique to you. In a professional manner we learn about your image and how you would like the world to perceive

Bug#297196: Dummy bug to keep kernel-image-2.6.10-amd64 out of sarge

2005-02-27 Thread Frederik Schueler
package: kernel-image-2.6.10-amd64 version: 2.6.10-2

Bug#296623: kernel-image-2.6.8-amd64: 2.6.8 kernel images panic on quad Opteron box

2005-02-27 Thread Frederik Schueler
severity 296623 important thanks downgrading this bug to important, since you got the kernel working by booting with "nomce". Kind regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature

Processed: RE: kernel-image-2.6.8-amd64: 2.6.8 kernel images panic on quad Opteron box

2005-02-27 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 296623 important Bug#296623: kernel-image-2.6.8-amd64: 2.6.8 kernel images panic on quad Opteron box Severity set to `important'. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system admini

Bug#297166: hard freeze when starting X

2005-02-27 Thread Frederik Schueler
Hello, can you please try booting with noexec=off? Kind regards Frederik Schueler On Sun, Feb 27, 2005 at 11:39:46AM -0600, Stephen Waters wrote: > I use 32-bit sid with an amd64 kernel. This set up works fine with > 2.6.9-9 (2.6.9-4). Rebooting into 2.6.10-9 (2.6.10-2) caused a hard > freeze o

Processed: merge 287403 293938

2005-02-27 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 287403 wishlist Bug#287403: kernel-image-2.6.8-9-amd64-k8-smp - iptables does not work Severity set to `wishlist'. > reassign 287403 iptables Bug#287403: kernel-image-2.6.8-9-amd64-k8-smp - iptables does not work Bug reassigned from package `k

Processed: please add amd64 support to i386 alsa package

2005-02-27 Thread Debian Bug Tracking System
Processing commands for [EMAIL PROTECTED]: > severity 286915 wishlist Bug#286915: kernel-image-2.6.9-9-amd64-k8: 32 bit Alsa utilities do not work against 64 bit kernel Severity set to `wishlist'. > retitle 286915 please add amd64 32bit-ioctl modules support to i386 alsa > package Bug#286915: k

Bug#297166: hard freeze when starting X

2005-02-27 Thread Stephen Waters
Package: kernel-image-2.6.10-9-amd64-k8-smp Version: 2.6.10-2 I use 32-bit sid with an amd64 kernel. This set up works fine with 2.6.9-9 (2.6.9-4). Rebooting into 2.6.10-9 (2.6.10-2) caused a hard freeze once X got started, although there are no helpful log messages. I have a Radeon VE (7000) that

Bug#270134: marked as done (kernel-source-2.6.8: please add liqt3-mt-dev to the libqt3-dev suggest)

2005-02-27 Thread Debian Bug Tracking System
Your message dated Sun, 27 Feb 2005 18:23:20 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#270134: kernel-source-2.6.8: please add liqt3-mt-dev to the libqt3-dev suggest has caused the attached Bug report to be marked as done. This means that you claim that the problem has been d

Bug#268621: Reproducable in parts

2005-02-27 Thread Eduard Bloch
Moin Joerg! Joerg Schilling schrieb am Sonntag, den 27. Februar 2005: > If you like to have a decent CDDA extraction you need to use > generic SCSI and this is done by using the SCSI address syntax > instead of filnames. Oh my... man causality man partial_order You try to force you own design

Bug#268621: Reproducable in parts

2005-02-27 Thread Joerg Schilling
Andreas Metzler <[EMAIL PROTECTED]> wrote: > On 2005-02-26 Joerg Schilling <[EMAIL PROTECTED]> wrote: > > dev=ATA and dev=/dev/hdX are definitely not supposed to do the same thing. > > Hello, > What is the correct devicename on Linux 2.6, if I want DMA? This is the wrong question: If you like to

Bug#296544: 3w-xxxx "scsi: unknown opcode 0x80" bug repeatable

2005-02-27 Thread Matt Taggart
I am now seeing the same problem as Florian reported with the tons of "scsi: unknown opcode 0x80". It doesn't seem to be related to having smartd running. Horms writes > Thanks, this might be caused by the new scsi ioctl whitelist > that was added around 2.6.8. Which kernel were you upgradin

Bug#292478: more info on #292478: oops on boot with usb cdburner attached

2005-02-27 Thread Matt Taggart
I tried a few tests: 1) I have another mainboard (brand is FIC) that uses the SiS746 southbridge so I tested on it as well. I can repeat the same problem as in the original report. 2) I tried a couple other USB mass storage devices, * a memory card reader with memory card, non-bootable * a fl

Bug#268621: Reproducable in parts

2005-02-27 Thread Andreas Metzler
On 2005-02-26 Joerg Schilling <[EMAIL PROTECTED]> wrote: > dev=ATA and dev=/dev/hdX are definitely not supposed to do the same thing. Hello, What is the correct devicename on Linux 2.6, if I want DMA? > Check the cdda2wav(1) man page. dev=ATA is not documented in cdda2wav(1) (from 2.01.01a01).