Bug#443979: CONFIG_FIRMWARE_EDID=n fixes this (Bug#443979: Linux boot hangs on AMD Geode GX systems)

Hi, we hit this bug with Geode systems "PC Engines ALIX.3C3 LX800" and "IEI PCISA-LX-800-R11". We can avoid the early hang of the kernel if recompile it with CONFIG_FIRMWARE_EDID disabled. Steven, can you test if this solves the problem for you too? best regards, Timo Lindfors -- To UNSUBSCR

Bug#517347: linux-image-2.6.28-1-686 writing to swap disk

Package: linux-image-2.6.28-1-686 Version: 2.6.28-1: i386 (debian/unstable) System: Debian/sid Processor: Intel Pentium M 1.70 GHz (Family 6 Model 13 Stepping 6) Memory: 995.30 MB physical, 494.15 MB virtual After upgrading kernel 2.6.26-1-686 to 2.6.28-1-686 the system starts writing to the sw

Bug#517344: mkinitramfs-kpkg misspells "deprecation" as "depreciation"

Package: initramfs-tools Version: 0.93 Severity: minor Tags: patch mkinitramfs-kpkg outputs the following warning: Depreciation WARNING: use update-initramfs(8) "Depreciation" should be "Deprecation". -- Matt http://ftbfs.org/ diff -ru initramfs

Bug#517236: linux-image-2.6.28-1-amd64: Post Inst fails - /usr/sbin/mkinitramfs

(dropping all cc's; hope that is all right.) maximilian attems said on Thu, Feb 26, 2009 at 06:15:12PM +0100,: > > please post output of: > cat /etc/kernel-img.conf $ cat /etc/kernel-img.conf do_symlinks = yes relative_links = yes do_bootloader = no do_bootfloppy = no do_initrd = yes link_in

Bug#517201: marked as done (bttv "disagrees about version of symbol dump_stack" when )

Your message dated Fri, 27 Feb 2009 03:02:12 + with message-id <1235703732.3017.14.ca...@hashbaz.i.decadent.org.uk> and subject line Re: bttv "disagrees about version of symbol dump_stack" when has caused the Debian Bug report #517201, regarding bttv "disagrees about version of symbol dump_sta

Bug#517181: linux-image-2.6.28-1-amd64: bnx2 driver not shipped

On Thu, 2009-02-26 at 14:20 +0530, Ritesh Raj Sarraf wrote: > Package: linux-image-2.6.28-1-amd64 > Version: 2.6.28-1 > Severity: important > > *** Please type your report below this line *** > > The bnx2 driver is not available in 2.6.28. > The same is available in 2.6.26 We have been patching

Re: Re: dmesg timestamps vs uptime

On Wed, 2009-02-25 at 23:06 -0500, Yaroslav Halchenko wrote: > Hi Ben, > > Thanks -- that is a nice pointer (i.e. /proc/sched_debug), but I still > can't match everything up in my mind... could you gimme a little hint? > > I guess the .clock (in sched_debug) is the interesting one, but it > doesn

Bug#493832: ath5k disconnects regularly and has poor performance

My card worked correctly with Madwifi in Etch (stable). Lenny (stable) replaced it by ath5k and is really bad. Also it worked bad in other distributions with a kernel more updated. It was a chaos until I discovered the problem: ath5k. The speed and response of the ADSL connection are terribly b

Bug#517330: linux-image-2.6.26-1-686: ide-tape hangs for 180s on boot and disables the cdrom

Package: linux-image-2.6.26-1-686 Version: 2.6.26-13 Severity: normal Upgrade from Etch to Lenny. The computer has an IDE tape attached to hdd (slave). The cdrom is at hdc (master). It all worked fine under 2.6.18. Under 2.6.26 ide-tape hangs during boot at: "[5.776016] ide-tape: hdd <-> ht

Bug#517329: linux-libc-dev: file conflict with libdrm-dev

Package: linux-libc-dev Version: 2.6.28-1 Severity: serious Justification: fails to install/upgrade Hi, I'm running xorg from experimental, my libdrm-dev version is 2.4.4+git+20090205+8b88036-1 Upgrade of linux-libc-dev fails with Unpacking replacement linux-libc-dev ... dpkg: error processing

Bug#513915: firmware-bnx: no network device with xen kernel

I experienced the same: The xen kernel can't load the module on my Dell PE 2950. I think this is because the postinst file does "update-initramfs -u" This only builds the 2.6.26-1-amd64 initramfs image. The solution is to manually do build the initramfs image for the xen kernel using "update-ini

Bug#517260: Do Debian Policy 3.5 not apply to unstable?!?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Feb 26, 2009 at 10:39:17PM +0100, maximilian attems wrote: >On Thu, Feb 26, 2009 at 10:14:42PM +0100, Jonas Smedegaard wrote: >> Please reopen this bug. >> >> Debian Policy 3.5 mandates correct package dependencies. >> >> Debian Policy also a

Bug#517260: Do Debian Policy 3.5 not apply to unstable?!?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thu, Feb 26, 2009 at 10:26:26PM +0100, Luk Claes wrote: >Jonas Smedegaard wrote: >> Please reopen this bug. >> >> Debian Policy 3.5 mandates correct package dependencies. >> >> Debian Policy also applies to Debian unstable too. >> >> The "unstabl

Bug#517260: Do Debian Policy 3.5 not apply to unstable?!?

On Thu, Feb 26, 2009 at 10:14:42PM +0100, Jonas Smedegaard wrote: > Please reopen this bug. > > Debian Policy 3.5 mandates correct package dependencies. > > Debian Policy also applies to Debian unstable too. > > The "unstable" refer to the collection of packages - each individual > package rele

Bug#517260: Do Debian Policy 3.5 not apply to unstable?!?

Jonas Smedegaard wrote: > Please reopen this bug. > > Debian Policy 3.5 mandates correct package dependencies. > > Debian Policy also applies to Debian unstable too. > > The "unstable" refer to the collection of packages - each individual > package released to "unstable" should itself be non-br

curative monarchistic keratinized fasted

proofreader amoristic glycerinize ccystoscope -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#517260: Do Debian Policy 3.5 not apply to unstable?!?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please reopen this bug. Debian Policy 3.5 mandates correct package dependencies. Debian Policy also applies to Debian unstable too. The "unstable" refer to the collection of packages - each individual package released to "unstable" should itself be

Bug#517260: marked as done (linux-kbuild-2.6.28: Broken packages)

Your message dated Thu, 26 Feb 2009 21:28:08 +0100 with message-id <20090226202807.gc3...@baikonur.stro.at> and subject line Re: Bug#517260: linux-kbuild-2.6.28: Broken packages has caused the Debian Bug report #517260, regarding linux-kbuild-2.6.28: Broken packages to be marked as done. This mea

Bug#517260: linux-kbuild-2.6.28: Broken packages

Package: linux-kbuild-2.6.28 Severity: serious Justification: Policy 3.5 Package linux-headers-2.6.28-1-amd64 depends on linux-kbuild-2.6.28 but it is not installable: $ sudo apt-get install linux-headers-2.6.28-1-amd64 linux-image-2.6.28-1-amd64 The following packages have unmet dependenc

Processed: Re: Bug#517260: linux-kbuild-2.6.28: Broken packages

Processing commands for cont...@bugs.debian.org: > reassign 517260 linux-headers-2.6.28-1-amd64 Bug#517260: linux-kbuild-2.6.28: Broken packages Warning: Unknown package 'linux-kbuild-2.6.28' Bug reassigned from package `linux-kbuild-2.6.28' to `linux-headers-2.6.28-1-amd64'. > -- Stopping proce

Bug#517236: linux-image-2.6.28-1-amd64: Post Inst fails - /usr/sbin/mkinitramfs

On Thu, Feb 26, 2009 at 09:06:21PM +0530, Mahesh T. Pai wrote: > Package: linux-image-2.6.28-1-amd64 > Version: 2.6.28-1 > Severity: normal > > > This is what I get after installing the new kernel. > > o...@home:~# aptitude -f install > Reading package lists... Done > Building dependency tree >

Bug#511334: debian-installer: S390 boot fails on Flex-ES machine

Actually, a 100 Hz timer seems to work. Then I hang because I didn't load the DASD driver, but I think that's very likely just a problem with my generated RAMDISK. So my recommendation would be to use a 100Hz timer pop for s390 31-bit at least. I wonder if this has anything to do with tr

pllea synchronism kangaroos arsines

celibatess oratorizes miraged unterminated -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64

Aioanei Rares wrote: Is it the standard Debian .config? Same here what? Well, with both 2.6.26-x and 2.6.28 I am unable to boot my amd64 anymore. First my network card stopped working (e100), so I plugged in a rt8139too and now the e100 works but I get random kernel oops at boot

Bug#517243: linux-image-2.6.26-1-parisc64: tg3 probe triggers HPMC

Package: linux-image-2.6.26-1-parisc64 Version: 2.6.26-13 Severity: normal Booting lenny's kernel with a known working Tigon3 card (BCM5701) in the box triggers an HPMC during driver probe. I couldn't capture the console output yet, but ISTR the box crashing before the driver's output of DMA se

Processed: Re: Bug#517201: bttv "disagrees about version of symbol dump_stack" when

Processing commands for cont...@bugs.debian.org: > reassign 517201 linux-2.6 Bug#517201: bttv "disagrees about version of symbol dump_stack" when Warning: Unknown package 'linux-source' Warning: Unknown package 'module' Warning: Unknown package 'bttv' Bug reassigned from package `linux-source mod

Bug#517241: linux-image-2.6.28-1-amd64: Audio (Intel Corporation 82801H (ICH8 Family)) broken

Package: linux-image-2.6.28-1-amd64 Version: 2.6.28-1 Severity: normal Under the 2.6.28 kernel, audio does not work properly on my laptop. If I plug in some headphones, audio still comes out of the main laptop speakers. Audio out of the headphone port is very quiet, and adjusting the volume does

Bug#517236: linux-image-2.6.28-1-amd64: Post Inst fails - /usr/sbin/mkinitramfs

Package: linux-image-2.6.28-1-amd64 Version: 2.6.28-1 Severity: normal This is what I get after installing the new kernel. o...@home:~# aptitude -f install Reading package lists... Done Building dependency tree Reading state information... Done Reading extended state information Initializing pac

Re: [Lenny] linux-image-2.6.26-1-openvz-amd64 kernel panic on boot

Hi Cedric I agree that "can not boot" is a big problem. But there is a workaround for the problem and at the point of analysis of the bug report I understood that it was not on all systems. Best regards, // Ola Quoting Cedric Jeanneret : "not a big bug" ? ermm system can't boot... if

Bug#517215: 2.6.26 does not detect JMicron SATA controller while 2.6.25 did

On Thu, Feb 26, 2009 at 01:56:54PM +0100, Christian Hammers wrote: > Package: linux-image-2.6.26-1-amd64 > Version: 2.6.26-11 > Severity: important > > Hello > > After upgrading to linux-image-2.6.26-1-amd64 my computer does not boot > anymore. It seems that the SATA hard drive is beeing detected

Bug#517158: linux-source-2.6.28: PGP ".sign" file remained in sources

On Wed, Feb 25, 2009 at 05:43:25PM -0800, Kushal Koolwal wrote: > Package: linux-source-2.6.28 > Version: 2.6.28-1 > Severity: minor > > Not sure if this is intential or not, but after unpacking linux-source-2.6.28, > I found a file patch-2.6.28.5-6.bz2.sign in the root of source directory. > > N

Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64

On Thu, Feb 26, 2009 at 02:34:44PM +0200, Aioanei Rares wrote: > On Thu, Feb 26, 2009 at 12:26 PM, Roger Leigh wrote: > > > Package: linux-image-2.6.28-1-amd64 > > Version: 2.6.28-1 > > Severity: grave > > Justification: renders package unusable > > > > System: ASUS P5Q-E mainboard with an Intel

Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64

Same here, okthxbye Aioanei Rares wrote: On Thu, Feb 26, 2009 at 12:26 PM, Roger Leigh > wrote: Package: linux-image-2.6.28-1-amd64 Version: 2.6.28-1 Severity: grave Justification: renders package unusable System: ASUS P5Q-E mainboard with an In

Bug#517215: 2.6.26 does not detect JMicron SATA controller while 2.6.25 did

Package: linux-image-2.6.26-1-amd64 Version: 2.6.26-11 Severity: important Hello After upgrading to linux-image-2.6.26-1-amd64 my computer does not boot anymore. It seems that the SATA hard drive is beeing detected but not recognised as block device. The only suspicious line I could find was: [

Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64

On Thu, Feb 26, 2009 at 2:54 PM, Amaya wrote: > Same here, okthxbye > > > Aioanei Rares wrote: > > > > On Thu, Feb 26, 2009 at 12:26 PM, Roger Leigh wrote: > >> Package: linux-image-2.6.28-1-amd64 >> Version: 2.6.28-1 >> Severity: grave >> Justification: renders package unusable >> >> System: AS

had to add irqpoll for Lenny kernel; irqpoll breaks Lenny kernel

[Originally posted to debian-user where there weren't any replies. More details of hardware etc can be supplied if requested. Please Cc replies to me.] I have a machine that was running Etch (and using the 2.6.18-k7 kernel) for the entire release. It had uptimes over 100 days a few times during

Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64

On Thu, Feb 26, 2009 at 12:26 PM, Roger Leigh wrote: > Package: linux-image-2.6.28-1-amd64 > Version: 2.6.28-1 > Severity: grave > Justification: renders package unusable > > System: ASUS P5Q-E mainboard with an Intel Q9550 core2 quad 2.83 GHz > processor. > > After booting with GRUB (transcribed

Bug#517193: linux-image-2.6.28-1-amd64 fails to boot on amd64

Package: linux-image-2.6.28-1-amd64 Version: 2.6.28-1 Severity: grave Justification: renders package unusable System: ASUS P5Q-E mainboard with an Intel Q9550 core2 quad 2.83 GHz processor. After booting with GRUB (transcribed by hand, there may be typos): Booting 'Debian GNU/Linux, kernel 2.6

Re: [Lenny] linux-image-2.6.26-1-openvz-amd64 kernel panic on boot

"not a big bug" ? ermm system can't boot... if that's not a "grave bug"... we'll use the old deprecated fza-kernel until the new patched kernel is out... Regards, C. On Thu, 26 Feb 2009 10:58:15 +0100 Ola Lundqvist wrote: > Hi Cedric > > There are two answers for that question: > 1) The

Re: [Lenny] linux-image-2.6.26-1-openvz-amd64 kernel panic on boot

Hi Cedric There are two answers for that question: 1) The patch seems to be a potential ABI breaker. I do not say it is an ABI breaker, but it needs some analysis before telling that. ABI breakers has not been allowed for a quite long time during the lenny freeze period. 2) It has not bee

Re: [Lenny] linux-image-2.6.26-1-openvz-amd64 kernel panic on boot

Hi again, After some poking arround, my bug is exactly this one : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=500876 I just tried to boot the server with "maxcpus=4", and all works... Now the question is : why is the patch provided in this bug NOT applied to lenny stable kernel ?? Regards,