Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

maximilian attems wrote, on 2008-01-09 06:32: did you try 2.6.24-rc7 from trunk, see apt lines -> http://wiki.debian.org/DebianKernel No. I am about to download it and try to compile it with gcc-4.3 please report back on it, by default we currently use gcc-4.1 Same error: CC lib

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

On Wed, Jan 09, 2008 at 02:40:56AM +1030, Arthur Marsh wrote: > When compiling for Athlon using gcc-4.3: > > gcc-4.3 --version > gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk > revision 131316] Does Linux upstream already bless gcc 4.3? I doubt. > kernel/built-in.o: In fu

Bug#459767: linux-source-2.6.23: FTBFS with gcc-4.3

Bastian Blank wrote, on 09/01/08 21:32: On Wed, Jan 09, 2008 at 02:40:56AM +1030, Arthur Marsh wrote: When compiling for Athlon using gcc-4.3: gcc-4.3 --version gcc-4.3 (Debian 4.3-20080104-1) 4.3.0 20080104 (experimental) [trunk revision 131316] Does Linux upstream already bless gcc 4.3?

Bug#455899: damned ADMtek junk

Sorry for the delay in repliing, but I was expecting a proper solution could be found. Right now I find the situation hopeless. In case it helps others, this is the script I use to work around it. It's a really nasty hack, but works ~90% of the time, and with this I only need to manually attend

Bug#440807: increase CONFIG_SERIAL_8250_NR_UARTS (number of serial ports)

maximilian attems wrote: On Tue, Jan 08, 2008 at 02:50:41PM -0600, Lukasz Szybalski wrote: Currently we have 1 serial port on motherboard and 2 port pci card. I would like to add another 4 port pci card. I am not able to do it because I get a conflict on ttyS. Since regular pc pci limit is

Bug#440807: increase CONFIG_SERIAL_8250_NR_UARTS (number of serial ports)

On Wed, Jan 09, 2008 at 09:42:15AM -0600, Lukasz Szybalski wrote: > maximilian attems wrote: > > > >$ egrep NR_UARTS /boot/config-2.6.24-rc7-amd64 > >CONFIG_SERIAL_8250_NR_UARTS=16 > > > >$ egrep RUNTIME_UARTS /boot/config-2.6.24-rc7-amd64 > >CONFIG_SERIAL_8250_RUNTIME_UARTS=4 > > > >This can

Processed: tagging 440807

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.9.26 > tags 440807 + pending Bug#440807: increase CONFIG_SERIAL_8250_NR_UARTS (number of serial ports) There were no tags set. Tags added: pending > End of message, stopping processing here

Bug#459929: linux-image-2.6.23-1-xen-686 does not boot under the hypervisor

Package: linux-image-2.6.23-1-xen-686 Version: 2.6.23-2 Severity: grave Justification: renders package unusable This kernel is not recognised by update-grub as a xen kernel. There seam to be missing one or serval XEN_* options in the config. Also the file /var/lib/linux-image-2.6.23-1-xen-686/xe

Bug#455909: linux-image-2,6-iop32x: many misaligned memory accesses

2007/12/28, Martin Michlmayr <[EMAIL PROTECTED]>: > I can reproduce this problem with 2.6.18-5 and 2.6.22-3, but not with > 2.6.23-1 from unstable. Can you try 2.6.23? The 2.6.23-2 kernel package I built from source will still not boot from flash (a separate issue) but I can copy the /boot/{vmlin

Processed: severity of 459929 is normal

Processing commands for [EMAIL PROTECTED]: > # Automatically generated email from bts, devscripts version 2.10.11 > severity 459929 normal Bug#459929: linux-image-2.6.23-1-xen-686 does not boot under the hypervisor Severity set to `normal' from `grave' > End of message, stopping processing here.

Bug#459929: marked as done (linux-image-2.6.23-1-xen-686 does not boot under the hypervisor)

Your message dated Wed, 9 Jan 2008 18:03:57 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#459929: linux-image-2.6.23-1-xen-686 does not boot under the hypervisor has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt wit

Bug#455909: linux-image-2,6-iop32x: many misaligned memory accesses

* Martin Guy <[EMAIL PROTECTED]> [2008-01-09 15:50]: > load them into redboot via http. That still gives: Presumably right after boot without doing anything special? > [EMAIL PROTECTED]:/$ uname -r > 2.6.23-1-iop32x > [EMAIL PROTECTED]:/$ cat /proc/cpu/alignment > User: 0 > System:

Bug#440807: increase CONFIG_SERIAL_8250_NR_UARTS (number of serial ports)

maximilian attems wrote: On Wed, Jan 09, 2008 at 09:42:15AM -0600, Lukasz Szybalski wrote: maximilian attems wrote: $ egrep NR_UARTS /boot/config-2.6.24-rc7-amd64 CONFIG_SERIAL_8250_NR_UARTS=16 $ egrep RUNTIME_UARTS /boot/config-2.6.24-rc7-amd64 CONFIG_SERIAL_8250_RUNTIME_UARTS=4

Bug#455909: linux-image-2,6-iop32x: many misaligned memory accesses

2008/1/9, Martin Michlmayr <[EMAIL PROTECTED]>: > Presumably right after boot without doing anything special? No, after some kernel building. Right after a boot it's: n2100:~# cat /proc/cpu/alignment User: 0 System: 3928 Skipped:0 Half: 0 Word: 3928 D

Bug#440807: increase CONFIG_SERIAL_8250_NR_UARTS (number of serial ports)

On Wed, Jan 09, 2008 at 12:06:16PM -0600, Lukasz Szybalski wrote: > I run it as root on a command line? > bootparam 8250.nr_uarts=16 ?? > or? add the bootparam "8250.nr_uarts=16" to the kopt line in /boot/grub/menu.lst then run update-grub. (as already told ;) 2.6.24 wil have 32 as upper limit,

d-i support for running in a Xen guest domain

Hi, Firstly apologies for the cross post but I think this genuinely is of interest to both audiences. I'm subscribed to both lists so no need to CC me. I'm interested in getting d-i to work seamlessly inside a Xen guest domain using the paravirt_ops kernel support for Xen in 2.6.24+ (currently on

Some of your Debian packages might need attention

Dear Debian Kernel Team, The following possible problem(s) were detected in the package(s) you maintain in Debian: === linux-2.6: = This package has 3 RC bug(s) more than 20 days old: - #417121 pcmciautils: Data Corruption while using Texas Instrument PCI7420 -

Re: d-i support for running in a Xen guest domain

On Wed, Jan 09, 2008 at 09:58:45PM +, Ian Campbell wrote: > I'd like to propose enabling Xen guest support in all the native i?86 > kernel images (and eventually amd64 too), or at least in the -686-bigmem > kernel. Since paravirt ops is already enabled in all kernels (for KVM > and lguest) the

Bug#421325: marked as done (boot fsck cooked nearly the cpu)

Your message dated Thu, 10 Jan 2008 01:12:52 +0100 with message-id <[EMAIL PROTECTED]> and subject line Bug#421325: Is 421325 still reproducible? 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 n