Bug#292478: oops on boot with usb cdburner attached

Works fine for me booting with Kernel 2.6.8-2, IBM ThinkPad R40e type 2684, external USB Plextor PX-S2410TU using USB 1.1.

Bug#283715: kernel-image-2.6.9-1-k7: Removes /initrd.img, makes system unbootable

reassign 283715 kernel-package stop On Tue, 30 Nov 2004, Mikael Hedin wrote: > The install script removed my /initrd.img link to the, sayin "removing > dangling symlink". It was perfectly working, pointing to the img from > the last installed version. This happened when upgrading to version -3 >

Bug#295146: marked as done (kernel: can delete root directories)

Your message dated Wed, 20 Apr 2005 08:31:30 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#295146: kernel: can delete root directories 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 i

Processed: Re: Bug#283715: kernel-image-2.6.9-1-k7: Removes /initrd.img, makes system unbootable

Processing commands for [EMAIL PROTECTED]: > reassign 283715 kernel-package Bug#283715: kernel-image-2.6.9-1-k7: Removes /initrd.img, makes system unbootable Bug reassigned from package `kernel' to `kernel-package'. > stop Stopping processing here. Please contact me if you need assistance. Deb

Bug#289982: ACPI problems with kernel 2.6.x for Dell Inspiron 4100

quick note that's a dup of #289990. solved by append="pci=acpi" or append="acpi=noirq" and newer acpi since kernel-image-2.6.10. -- maks -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: Grace period for kernel-source uploads

On Sat, 2005-04-09 at 17:30 -0400, Jurij Smakov wrote: > On Sat, 9 Apr 2005, maximilian attems wrote: > > > disagreed, > > all the archs managed in the d-k svn got their updates steadily. > > problems are the trees outside of it as well d-i udebs relying > > on a stable abi, which is easily broken

Bug#283783: Kernel bug report 283783

Hi Robert, Were you able to achieve any progress on this bug by using Joshua's advice? By the way, the missing "old modprobe" is most likely due to the incorrect version of initrd used (like 2.4 initrd used with 2.6 kernel). Please make sure that in your silo.conf the initrd parameter is set to

Bug#304850: marked as done (kernel-source-2.6.11: Include software suspend 2)

Your message dated Tue, 19 Apr 2005 23:39:52 +0200 with message-id <[EMAIL PROTECTED]> and subject line Bug#304850: kernel-source-2.6.11: Include software suspend 2 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 n

Processed: Re: Bug#304639: mkext2fs: command not found

Processing commands for [EMAIL PROTECTED]: > reassign 304639 initrd-tools Bug#304639: mkext2fs: command not found Bug reassigned from package `kernel-image-2.6.8-2-386' to `initrd-tools'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system admin

Bug#304779: readjust package + severity

reassign #304779 boot-floppies severity 304779 normal stop the boot-floppy kernel is not maintained by the debian kernel team. nobody would expect 2.4.18 to work on modern hardware. you'd better use the new d-i at: http://www.debian.org/devel/debian-installer/ and if you still need a woody base

Bug#304656: kernel: usbcore oops failure

severity 304656 normal stop On Wed, 09 Jun 2004, Keith Blow wrote: > I have a Sharp Zaurus which initialises OK under 2.6.3 but on upgrade to > 2.6.5, with the same kernel options, it causes usbcore to crash. I have > attached the kernel log report: 2.6.5 is not supported for sarge, nor do i s

Bug#305123: kernel: Oops, system freeze. Unable to handle kernel NULL pointer dereference at virtual address 0000007c

severity 305123 normal stop On Mon, 18 Apr 2005, TAKAIZUMI Koichi wrote: > package: kernel-source-2.4.19 2.4.19-4.woody2 > system: IBM x335, memory 4G, Xeon x 2(4)(HT on) 2.4.19 kernels are not supported by the debian-kernel team. please upgrade to something more recent like 2.4.27 or 2.6.8 fo

Processed: Re: Bug#305123: kernel: Oops, system freeze. Unable to handle kernel NULL pointer dereference at virtual address 0000007c

Processing commands for [EMAIL PROTECTED]: > severity 305123 normal Bug#305123: kernel: Oops, system freeze. Unable to handle kernel NULL pointer dereference at virtual address 007c Severity set to `normal'. > stop Stopping processing here. Please contact me if you need assistance. Debian

Processed: Re: Bug#304656: kernel: usbcore oops failure

Processing commands for [EMAIL PROTECTED]: > severity 304656 normal Bug#304656: kernel: usbcore oops failure Severity set to `normal'. > stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) --

Processed: readjust package + severity

Processing commands for [EMAIL PROTECTED]: > reassign #304779 boot-floppies Bug#304779: impossible to install debian 3.0 r4 with bf24 kernel Bug#304780: impossible to install debian 3.0 r4 with bf24 kernel Bug#304782: impossible to install debian 3.0 r4 with bf24 kernel Bug#304783: impossible to i

kernel-image-2.6.8-amd64_2.6.8-13_i386.changes ACCEPTED

Accepted: kernel-headers-2.6.8-11-amd64-generic_2.6.8-13_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-11-amd64-generic_2.6.8-13_i386.deb kernel-headers-2.6.8-11-amd64-k8-smp_2.6.8-13_i386.deb to pool/main/k/kernel-image-2.6.8-amd64/kernel-headers-2.6.8-11-amd64-k8-sm

Bug#305187: Another alsa problem, via82xx

I have the same basic problem. 2.6.8-2-k7: sound works, 2.6.11-1-k7, sound no workie. My sounds stack looks like this under 2.6.8-2-k7: snd_via82xx29604 0 snd_ac97_codec 69508 1 snd_via82xx snd_pcm_oss54376 0 snd_mixer_oss 19904 1 snd_pcm_oss snd_pcm

kernel-image-2.6.11-amd64_2.6.11-2_i386.changes ACCEPTED

Accepted: kernel-headers-2.6.11-9-amd64-generic_2.6.11-2_i386.deb to pool/main/k/kernel-image-2.6.11-amd64/kernel-headers-2.6.11-9-amd64-generic_2.6.11-2_i386.deb kernel-headers-2.6.11-9-amd64-k8-smp_2.6.11-2_i386.deb to pool/main/k/kernel-image-2.6.11-amd64/kernel-headers-2.6.11-9-amd64-k8-

Bug#292478: More on this bug

Daniel Burrows writes... > I've run into what looks like the same thing on a new Dell Latitude x300. An I'm not convinced that the two Dell related bug reports in this bug are related to the original problem that I reported, other than the fact that they are all probably bugs due to the quali

Bug#292478: More on this bug

I've run into what looks like the same thing on a new Dell Latitude x300. An interesting twist is that this bug only manifests itself if I boot the -686 variant of the kernel; the default -386 variant boots without any problems. If I don't plug the drive in, everything works fine at first, but

2.6.8-2-686 kernel, Firewire/SCSI, PowerFile C200, errors (i.e. not working)

I finally got to testing 2.6.8-2-686 next to 2.6.10 and 2.6.11 and Debian's 2.6.8-2-686 kernel doesn't work either. Logs below. How can I be of more help in solving this problem and not just post "complaints"? :) I'd do more than just post messages if I knew where to start and where to look... Tha

Bug#257996: kernel: Fixed in 2.6.11

Package: kernel Followup-For: Bug #257996 I experience this with Sarge's 2.6.8, but not with 2.6.11. Maybe the bug should be reassigned. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.1

Bug#289250: kernel-image-2.6.8-2-386: Fixed in 2.6.11

Package: kernel-image-2.6.8-2-386 Followup-For: Bug #289250 This bug doesn't appear anymore in 2.6.11, although vesafb is still a module. See also 257996. Also note that the problem wasn't specific to 386 (at least concerned k7 too). -- System Information: Debian Release: 3.1 APT prefers testin

Bug#266674: kernel: Confirmed on 2.6.11

Package: kernel Followup-For: Bug #266674 I am again experiencing this on 2.6.11-1-k7 2.6.11-2. Device 'vesafb0' does not have a release() function, it is broken and must be fixed. Badness in device_release at drivers/base/core.c:85 [] kobject_cleanup+0x98/0xa0 [] kobject_release+0x0/0x10 [] k

Bug#305330: kernel driver starfire for the Alpha architecture

* Bob Lindell wrote: [...] > I added an additional "|| defined (__alpha__)" expression and > compiled the driver. I tested it on a PC164 running the Sarge > 2.4.27-2-generic kernel. Seems to run correctly on the Alpha. All 4 > ports of the card worked properly. > > This fix needs to make it upstre

Bug#305330: kernel driver starfire for the Alpha architecture

Package: kernel Version: 2.4.27-2-generic When I load the starfire network interface card driver on the Alpha architecture, the following message is displayed on the console: This driver has not been ported to this 64-bit architecture yet. This driver worked on the Alpha architecture in the 2.4.1

Processed: severity of 304784 is critical

Processing commands for [EMAIL PROTECTED]: > severity 304784 critical Bug#304784: impossible to install debian 3.0 r4 with bf24 kernel Bug#304779: impossible to install debian 3.0 r4 with bf24 kernel Bug#304780: impossible to install debian 3.0 r4 with bf24 kernel Bug#304782: impossible to install

Processed: impossible to install debian 3.0 r4 with bf24 kernel

Processing commands for [EMAIL PROTECTED]: > merge 305123 304784 Bug#304784: impossible to install debian 3.0 r4 with bf24 kernel Bug#305123: kernel: Oops, system freeze. Unable to handle kernel NULL pointer dereference at virtual address 007c Mismatch - only Bugs in same state can be merged: