Re: Scheduling 2.6.17-1
On Mon, 19 Jun 2006, Frederik Schueler wrote:
Hello,
I would like to reschedule the uploads:
Unless someone objects, we will upload both linux-2.6.16 and linux-2.6
to unstable tomorrow, 20th of June.
- linux-2.6 2.6.17-1 is what we have in dists/trunk/linux-2.6 now.
- linux-2.6.16 2.6.16-15 is what we have in dists/sid/linux-2.6 now,
Bastian will apply the needed changes to the build system later today
and rename the source package accordingly.
If someone needs more time for the one or the other kernel version,
please raise your voice so we can reschedule again.
On sparc 2.6.17 SMP kernel is broken, and at the moment I don't have a
clue how to fix it. I can try git-bisecting it, but it will probably take
at least few more days before it even becomes clear what causes the breakage.
There are a couple of patches for 2.6.16 which I would love to see
included. There is a D-cache memory corruption fix included in 2.6.17
(attached as sparc64-dcache.patch), which did not appear in a 2.6.16
point release as I hoped. As it also affect the mips arch, perhaps mips
maintainer should also have a look at it. The other patch
(sparc32-iotlb.patch, posted today) addresses current sparc32 breakage,
so it would be great to include that as well.
I'm currently building the kernel with these patches, and should be able
to test it tomorrow (at least on sparc64), so please don't upload before
that. If tests work out, I hope to be able to commit them to svn tomorrow
morning, as tonight my network access is extremely flaky :-(
Best regards,
Jurij Smakov[EMAIL PROTECTED]
Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CCFrom [EMAIL PROTECTED] Thu Jun 1 21:51:17 2006
Date: Thu, 01 Jun 2006 17:52:58 -0700 (PDT)
From: David Miller <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED], [EMAIL PROTECTED], sparclinux@vger.kernel.org
Subject: [PATCH]: Fix D-cache corruption in mremap() (was Re: 2.6.17-rc3+git
seems to corrupt dpkg databases)
Thanks to some excellent corrupted status and available files
Daniel sent to me, I was able to track down the bug. This
bug has been around basically forever, just minor data layout
changes due to arbitrary unrelated kernel and userland library
modifications make the bug go away for some time and then
reappear. It was always there.
Anyways, give this patch below a test, it should fix things.
It is against the current 2.6.17 tree.
I'll also post a little reproducer program that can be used to
accurately see if the patch really fixes the problem on your
machine or not, which should help with the variability of the
dpkg corruption case.
Please test this, I need to know if this works for everyone
or not.
Thanks.
diff-tree 0b0968a3e691771bf87e1ce747b2c7d23b5526c8 (from
951bc82c53f30ec6b4c2d04a051e74ea9a89b669)
Author: David S. Miller <[EMAIL PROTECTED]>
Date: Thu Jun 1 17:47:25 2006 -0700
[SPARC64]: Fix D-cache corruption in mremap
If we move a mapping from one virtual address to another,
and this changes the virtual color of the mapping to those
pages, we can see corrupt data due to D-cache aliasing.
Check for and deal with this by overriding the move_pte()
macro. Set things up so that other platforms can cleanly
override the move_pte() macro too.
Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
diff --git a/include/asm-generic/pgtable.h b/include/asm-generic/pgtable.h
index 358e4d3..c2059a3 100644
--- a/include/asm-generic/pgtable.h
+++ b/include/asm-generic/pgtable.h
@@ -159,17 +159,8 @@ static inline void ptep_set_wrprotect(st
#define lazy_mmu_prot_update(pte) do { } while (0)
#endif
-#ifndef __HAVE_ARCH_MULTIPLE_ZERO_PAGE
+#ifndef __HAVE_ARCH_MOVE_PTE
#define move_pte(pte, prot, old_addr, new_addr)(pte)
-#else
-#define move_pte(pte, prot, old_addr, new_addr)
\
-({ \
- pte_t newpte = (pte); \
- if (pte_present(pte) && pfn_valid(pte_pfn(pte)) && \
- pte_page(pte) == ZERO_PAGE(old_addr)) \
- newpte = mk_pte(ZERO_PAGE(new_addr), (prot)); \
- newpte; \
-})
#endif
/*
diff --git a/include/asm-mips/pgtable.h b/include/asm-mips/pgtable.h
index 702a28f..69cebbd 100644
--- a/include/asm-mips/pgtable.h
+++ b/include/asm-mips/pgtable.h
@@ -70,7 +70,15 @@ extern unsigned long zero_page_mask;
#define ZERO_PAGE(vaddr) \
(virt_to_page(empty_zero_page + (((unsigned long)(vaddr)) &
zero_page_mask)))
-#define __HAVE_ARCH_MULTIPLE_ZERO_PAGE
+#define __HAVE_ARCH_MOVE_PTE
+#define move_pte(pte, prot, old_addr, new_addr)
\
+({ \
+ pte_t newpte = (pte
Bug#357236: linux-image-2.6.16-rc5-686: no sound on Lifebook P2120
reassign 357236 linux-image-2.6.16-2-686 forwarded 357236 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1943 thanks Hadn't noticed that the forward tag didn't work last time, sorry about that. Okay, it's been three months and upstream hasn't touched my bug. I'm wondering if I can get some help here, or at least vague ideas about what might be going wrong. On this laptop, fn-F3 toggles mute; when mute is turned off, there's an audible beep. When repeatedly toggling "mute unmute mute unmute", I noticed that this audible beep capability stops during the boot. By booting with init=/bin/bash and carefully going through things, I've managed to narrow it down to when the /etc/init.d/udev script runs udevtrigger. If I reboot and load the modules which udevtrigger would load, that does not cause the beeps to stop, but then running udevtrigger does stop them. I think something in udevtrigger somehow disables sound output. Any ideas? Could this be a Debian-specific problem? What do I test next? Do I stick a bunch of printfs and sleep commands into the udevtrigger source to pin things down further? I've had no sound on this laptop for a year, and finally have some time to put into this, but would rather not just flail about blindly... Thanks, -Adam -- GPG fingerprint: D54D 1AEE B11C CE9B A02B C5DD 526F 01E8 564E E4B6 Welcome to the best software in the world today cafe! http://www.take6.com/albums/greatesthits.html -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#357236: linux-image-2.6.16-rc5-686: no sound on Lifebook P2120
Processing commands for [EMAIL PROTECTED]: > reassign 357236 linux-image-2.6.16-2-686 Bug#357236: linux-image-2.6.16-rc5-686: no sound on Lifebook P2120 Bug reassigned from package `linux-2.6' to `linux-image-2.6.16-2-686'. > forwarded 357236 https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1943 Bug#357236: linux-image-2.6.16-rc5-686: no sound on Lifebook P2120 Noted your statement that Bug has been forwarded to https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1943. > thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#374545: linux-image-2.6.16-2-686: Sound recording fails with DSP-500 / snd-usb-audio
Package: linux-image-2.6.16-2-686
Version: 2.6.16-14
Severity: normal
Using linux-image-2.6.16-2-686 on my laptop, sound recording fails using
the Plantronics DSP-500 USB headset. (Output is fine.) Changing only the
kernel to 2.6.15-1-486, it works (both on my laptop and on my Etch system).
This is always reproducible. The less severe result that I've dug into
is from arecord:
$ arecord 1234.wav
Recording WAVE '1234.wav' : Unsigned 8 bit, Rate 8000 Hz, Mono
arecord: xrun:1089: read/write error, state = PREPARED
$
(This happens with (all?) other recording modes as well, but that's not
the point here - using 2.6.15-1-486, I can run the same command and have
a successful recording with the same parameters.)
I have only one card (i.e. the headset) configured:
$ lsusb | grep Plan
Bus 004 Device 005: ID 047f:0ca1 Plantronics, Inc.
$ cat /proc/asound/cards
0 [Headset]: USB-Audio - Plantronics Headset
Plantronics Plantronics Headset at
usb-:00:1d.7-3.3, full speed
$ cat /proc/asound/modules
0 snd_usb_audio
$
As you can see from the attached strace output, the device file for
recording, /dev/snd/pcmC0D0c does in fact exist and is opened
read-write, but after that it fails.
Thank you in advance.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-2-686
Locale: LANG=sv_SE, LC_CTYPE=sv_SE (charmap=ISO-8859-1)
Versions of packages linux-image-2.6.16-2-686 depends on:
ii module-init-tools 3.2.2-3tools for managing Linux
kernel mo
ii yaird [linux-initramfs-tool] 0.0.12-14 Yet Another mkInitRD
Versions of packages linux-image-2.6.16-2-686 recommends:
pn libc6-i686 (no description available)
-- debconf information excluded
execve("/usr/bin/arecord", ["arecord", "1234.wav"], [/* 28 vars */]) = 0
uname({sys="Linux", node="debbie", ...}) = 0
brk(0) = 0x8054000
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
mmap2(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7fb1000
access("/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=120756, ...}) = 0
mmap2(NULL, 120756, PROT_READ, MAP_PRIVATE, 3, 0) = 0xa7f93000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/usr/lib/libasound.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0p\365\1"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=790752, ...}) = 0
mmap2(NULL, 793828, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xa7ed1000
mmap2(0xa7f8e000, 20480, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xbc) = 0xa7f8e000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/tls/libm.so.6", O_RDONLY)= 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0`3\0\000"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=149264, ...}) = 0
mmap2(NULL, 151712, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xa7eab000
mmap2(0xa7ecf000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x23) = 0xa7ecf000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/tls/libdl.so.2", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\20\f\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=9592, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0xa7eaa000
mmap2(NULL, 12404, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xa7ea6000
mmap2(0xa7ea8000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x1) = 0xa7ea8000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/tls/libpthread.so.0", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340G\0"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=85770, ...}) = 0
mmap2(NULL, 70104, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0xa7e94000
mmap2(0xa7ea2000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0xd) = 0xa7ea2000
mmap2(0xa7ea4000, 4568, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0xa7ea4000
close(3)= 0
access("/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or directory)
open("/lib/tls/libc.so.6", O_RDONLY)= 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260O\1"..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1270928, ...}) = 0
mmap2(NULL, 1276892, PROT_READ|PROT_
Re: Bug#374278: Install report: 12" PowerBook G4 1.33Ghz
On Mon, Jun 19, 2006 at 11:26:18PM +0200, Sven Luther wrote: > On Mon, Jun 19, 2006 at 09:18:39PM +0200, Wouter Verhelst wrote: > > Nothing else, the yaboot.conf built with the installer. > > Ah, sorry, this is the already installed system, you are not trying to boot > the d-i image, right ? Yes. > As such, i would like the content of your /boot file (ls -l /boot preferably), > and it would probably be best to move this to debian-kernel. config-2.6.15-1-powerpc initrd.img initrd.img-2.6.15-1-powerpc System.map-2.6.15-1-powerpc vmlinux vmlinux-2.6.15-1-powerpc > If this is not the case, i seriously misundersood something. You didn't. Cc set accordingly. Occasionally, now that you mention it, I have recently begun to have issues booting 2.6.15 kernels with yaird-generated initrd images. This might be related? -- Fun will now commence -- Seven Of Nine, "Ashes to Ashes", stardate 53679.4 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367125: ext2_get_inode: bad inode number
"Peter Kruse" <[EMAIL PROTECTED]> writes: > Hello Goswin, > > > On 6/16/06, Goswin von Brederlow <[EMAIL PROTECTED]> wrote: > I noticed this and can reproduce it by running exportfs -u, > umount, > resize2fs, mount, exportfs and then accessing some previously used > file on the nfs clients. The client (or server?) still has the old > inode numbers cached and directly access the inodes while the > resize2fs has removed it. The ext2-fs gives an error and remounts it > read-only. > > > That's interesting, didn't think it was so easy to reproduce - > have to try that. > Does it also remount the filesystem read-only when mounted > with the errors=continue mount option? I would think not. I prefer to mount read-only on errors. MfG Goswin
Bug#372523: linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Frans Pop wrote: > On Monday 19 June 2006 18:23, FRLinux wrote: >> The IDE controller seems to be a secondary controller from the looks of >> it therefore explaining that devices are being *moved* to hde and hdg. > > The question is: what is being seen as the primary IDE controller in this > case (which claims hda-hdd). The IDE controllers on the box are : 00:05.0 IDE interface: Silicon Image, Inc. PCI0680 Ultra ATA-133 Host Controller (rev 02) 00:0f.1 IDE interface: Broadcom CSB6 RAID/IDE Controller (rev a0) On normal debian install/kernel, the broadcom gets loaded first. On the Xen kernel; the Sil controller gets in first. Interestingly, the only way i got the Xen kernel to boot was to use yaird rather than the standard mkinitrd, that is the only one which compiles a proper list of my modules. > This is also the reason behind the erratum for d-i listed on: > http://www.us.debian.org/devel/debian-installer/errata Nice one, i had forgotten about that one, that would indeed explain the behavior. I have to paste this in, this is the boot from the Xen kernel : SiI680: IDE controller at PCI slot :00:05.0 SiI680: chipset revision 2 SiI680: BASE CLOCK == 133 SiI680: 100% native mode on irq 16 ide0: MMIO-DMA , BIOS settings: hda:pio, hdb:pio ide1: MMIO-DMA , BIOS settings: hdc:pio, hdd:pio Probing IDE interface ide0... hda: SAMSUNG SP2014N, ATA DISK drive ide0 at 0xf4802080-0xf4802087,0xf480208a on irq 16 Probing IDE interface ide1... hdc: SAMSUNG SP2014N, ATA DISK drive [snip] SvrWks CSB6: IDE controller at PCI slot :00:0f.1 SvrWks CSB6: chipset revision 160 SvrWks CSB6: not 100% native mode: will probe irqs later ide2: BM-DMA at 0x08b0-0x08b7, BIOS settings: hde:DMA, hdf:pio ide3: BM-DMA at 0x08b8-0x08bf, BIOS settings: hdg:pio, hdh:pio Probing IDE interface ide2... hde: TEAC CD-ROM CD-224E, ATAPI CD/DVD-ROM drive It actually booted up properly BUT (that's the important bit here), GRUB wanted this to be able to start : title Xen 3.0 / XenLinux 2.6 kernel /xen-3.0-i386.gz noreboot module /vmlinuz-2.6.16-2-xen-686 root=/dev/hde1 ro module /initrd.img-2.6.16-2-xen-686 Steph - -- Mail sent on Gentoo Linux (http://www.gentoo.org) http://frlinux.net - [EMAIL PROTECTED] public key : http://frlinux.net/files/frlinux_public_key.asc -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFElv7xplbM2wjOZgMRAkp3AJ9P+Hi/Fm50tE4NBBhSVxDi0qMkpwCgs1zh dy6ScXWtuJDlVod6JDI/I7s= =yWS5 -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Scheduling 2.6.17-1
On Mon, Jun 19, 2006 at 06:56:50PM +0200, Bastian Blank wrote: > On Sun, Jun 18, 2006 at 04:10:30PM -0600, dann frazier wrote: > > The only technical issue is getting the meta packages to play well. I > > think rough consensus was to leave the metapackages as-is in > > linux-2.6.16 and either 1) drop meta packages from linux-2.6 >= 2.6.17 > > or 2) create separate metapackages for linux-2.6 (linux-image-2.6-686-sid, > > for example). > > AFAIK the plan is the following: > - linux-2.6 remains the metapackages, the point to the last available > one. > - linux-2.6.16 contains no metapackages. > - linux-latest-2.6 or so contains the metapackages to match linux-2.6.16 > and have to go through t-p-u. fwiw, this doesn't provide a way for people to track the proposed etch kernel in sid, which may reduce the number of testers of that kernel prior to migration. -- dann frazier -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
linux-image-2.6.12-1-386
Hello All; I have "debian testing" installed on an old dell machine. It has linux-image-2.6.12-1-386 on it and since I was having trouble iptables, I was checking to see if there was an update. There appears to be packages for linux-image-2.6.15-1-* (486, 686, etc.) but there is nothing for "386". Is 386 package no longer supported? BTW, the issue with iptables is: # iptables -A FORWARD -p udp --match length --length 39 --match u32 -- u32 '27&0x8f=7' --u32 '31=0x48ae0568' -j DROP iptables: No chain/target/match by that name I'm fairly certain the syntax is correct though maybe its from an older/different version of "u32". I've also tried simpler expressions with the same results. ie -u32 '0=1' Regards, dcj -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372523: linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0)
On Monday 19 June 2006 18:23, FRLinux wrote: > The IDE controller seems to be a secondary controller from the looks of > it therefore explaining that devices are being *moved* to hde and hdg. The question is: what is being seen as the primary IDE controller in this case (which claims hda-hdd). This is all about the order in which device driver modules are being loaded and, basically, you cannot depend on any order. This is also the reason behind the erratum for d-i listed on: http://www.us.debian.org/devel/debian-installer/errata Cheers, FJP pgpWiXayWFTmP.pgp Description: PGP signature
Re: I was banned from #debian-kernel ? ...
On Mon, Jun 19, 2006 at 06:26:36PM +0100, Thiemo Seufer wrote: > Sven Luther wrote: > > Hi all, > > > > I would like to know why i was banned from #debian-kernel and by whom, > > By waldi, because your client disconnected/connected continuously for > several hours. Ah, ok. Can i be allowed back now ? Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Scheduling 2.6.17-1
Joey Hess wrote: > Bastian Blank wrote: > > On Sun, Jun 18, 2006 at 04:10:30PM -0600, dann frazier wrote: > > > The only technical issue is getting the meta packages to play well. I > > > think rough consensus was to leave the metapackages as-is in > > > linux-2.6.16 and either 1) drop meta packages from linux-2.6 >= 2.6.17 > > > or 2) create separate metapackages for linux-2.6 (linux-image-2.6-686-sid, > > > for example). > > > > AFAIK the plan is the following: > > - linux-2.6 remains the metapackages, the point to the last available > > one. > > - linux-2.6.16 contains no metapackages. > > - linux-latest-2.6 or so contains the metapackages to match linux-2.6.16 > > and have to go through t-p-u. > > As mentioned on #debian-boot, this is going to cause a lot of pain for > d-i. Why not do it dannf's way? Excuse me, I missed the first point. If the linux-2.6 metapackages are still in testing and point to the right kenrel for testing, we're good to go. -- see shy jo signature.asc Description: Digital signature
Re: I was banned from #debian-kernel ? ...
Sven Luther wrote: > Hi all, > > I would like to know why i was banned from #debian-kernel and by whom, By waldi, because your client disconnected/connected continuously for several hours. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I was banned from #debian-kernel ? ...
Hi all, I would like to know why i was banned from #debian-kernel and by whom, and if this was a decision taken by all of the debian kernel team, and if so, why i was not informed on it, and what the plan is now ? Troubled, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Scheduling 2.6.17-1
On Sun, 18 Jun 2006 15:28:29 -0700 (PDT) Jurij Smakov wrote: > On Sun, 18 Jun 2006, Frederik Schueler wrote: > > Linux 2.6.17 has been released today, and I would like to upload it > > to unstable tomorrow (Monday 19.06). > > http://kernel-archive.buildserver.net/debian-kernel/pool/main/l/linux-2.6/ > > sparc kernel downloaded from there currently does not work. I've > tried it and it appears to randomly hang while loading modules. It is > not clear at the moment what the problem is, as I've tested > 2.6.16-rc6 (I believe) successfully before. I'm currently running my > own build, well see what happens with it. Wild guess: Did you make sure to use GCC 4.0? - Jonas -- * Jonas Smedegaard - idealist og Internet-arkitekt * Tlf.: +45 40843136 Website: http://dr.jones.dk/ - Enden er nær: http://www.shibumi.org/eoti.htm pgprMmei0iSqK.pgp Description: PGP signature
Re: Scheduling 2.6.17-1
Bastian Blank wrote: > On Sun, Jun 18, 2006 at 04:10:30PM -0600, dann frazier wrote: > > The only technical issue is getting the meta packages to play well. I > > think rough consensus was to leave the metapackages as-is in > > linux-2.6.16 and either 1) drop meta packages from linux-2.6 >= 2.6.17 > > or 2) create separate metapackages for linux-2.6 (linux-image-2.6-686-sid, > > for example). > > AFAIK the plan is the following: > - linux-2.6 remains the metapackages, the point to the last available > one. > - linux-2.6.16 contains no metapackages. > - linux-latest-2.6 or so contains the metapackages to match linux-2.6.16 > and have to go through t-p-u. As mentioned on #debian-boot, this is going to cause a lot of pain for d-i. Why not do it dannf's way? -- see shy jo signature.asc Description: Digital signature
Re: Scheduling 2.6.17-1
On Sun, Jun 18, 2006 at 04:10:30PM -0600, dann frazier wrote: > The only technical issue is getting the meta packages to play well. I > think rough consensus was to leave the metapackages as-is in > linux-2.6.16 and either 1) drop meta packages from linux-2.6 >= 2.6.17 > or 2) create separate metapackages for linux-2.6 (linux-image-2.6-686-sid, > for example). AFAIK the plan is the following: - linux-2.6 remains the metapackages, the point to the last available one. - linux-2.6.16 contains no metapackages. - linux-latest-2.6 or so contains the metapackages to match linux-2.6.16 and have to go through t-p-u. Bastian -- She won' go Warp 7, Cap'n! The batteries are dead! signature.asc Description: Digital signature
Re: Scheduling 2.6.17-1
On Mon, Jun 19, 2006 at 01:59:29PM +0200, Frederik Schueler wrote: > Hello, > > I would like to reschedule the uploads: > > Unless someone objects, we will upload both linux-2.6.16 and linux-2.6 > to unstable tomorrow, 20th of June. > > - linux-2.6 2.6.17-1 is what we have in dists/trunk/linux-2.6 now. > > - linux-2.6.16 2.6.16-15 is what we have in dists/sid/linux-2.6 now, > Bastian will apply the needed changes to the build system later today > and rename the source package accordingly. My preference would have gone to a linux-2.6-etch package instead of linux-2.6.16. Friendly, Sven Luther -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372523: linux-image-2.6.16-2-xen-686: kernel panic on software raid (md0)
Hello, I actually found what the problem is, and i wonder if it is related to your kernel settings. When i perform an install of Debian, the installer sees two IDE drives as hda and hdc (they are indeed connected as primary and secondary master) and a CDrom drive. When your Xen kernel boots, it then sees the two drives as hde and hdg, which doesn't really make sense. The server is a Dell PowerEdge 650 which has been stripped of all SCSI drives and being used with IDE instead. The IDE controller seems to be a secondary controller from the looks of it therefore explaining that devices are being *moved* to hde and hdg. Now, why would the Debian installer see them as hda and hdc puzzles me a bit. I hope that will help you out, i'm surely not the only one wanting to install Xen on such a configuration. Steph -- Mail sent under Debian GNU/Linux http://frlinux.net - Site d'aide a Linux en Francais http://frlinux.net/files/frlinux_public_key.asc
Re: Scheduling 2.6.17-1
* Frederik Schueler <[EMAIL PROTECTED]> [2006-06-19 15:18]: > mipsel was broken by a kernel-package change, which should have been > fixed too by now. For the record, kernel-package didn't change. The kernel package introduced new functionality which relied on a feature kernel-package didn't yet have (or on a bug that has always been there, depending on your perspective ;). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Scheduling 2.6.17-1
* Frans Pop <[EMAIL PROTECTED]> [2006-06-19 14:34]: > On Monday 19 June 2006 13:59, Frederik Schueler wrote: > > - linux-2.6.16 2.6.16-15 is what we have in dists/sid/linux-2.6 now, > > Will this fix the build problems for both hppa and mipsel? mipsel should build with the new kernel-package (10.049). -- Martin Michlmayr http://www.cyrius.com/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Scheduling 2.6.17-1
On Mon, Jun 19, 2006 at 02:34:39PM +0200, Frans Pop wrote: > On Monday 19 June 2006 13:59, Frederik Schueler wrote: > > - linux-2.6.16 2.6.16-15 is what we have in dists/sid/linux-2.6 now, > > Will this fix the build problems for both hppa and mipsel? > What about the RC bugs that have also been keeping 2.6.16 out of testing? I fixed the hppa build problems... -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Scheduling 2.6.17-1
Hi, On Mon, Jun 19, 2006 at 02:34:39PM +0200, Frans Pop wrote: > Will this fix the build problems for both hppa and mipsel? > What about the RC bugs that have also been keeping 2.6.16 out of testing? hppa seems fixed in svn. mipsel was broken by a kernel-package change, which should have been fixed too by now. Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
Re: Scheduling 2.6.17-1
On Monday 19 June 2006 13:59, Frederik Schueler wrote: > - linux-2.6.16 2.6.16-15 is what we have in dists/sid/linux-2.6 now, Will this fix the build problems for both hppa and mipsel? What about the RC bugs that have also been keeping 2.6.16 out of testing? pgp4U7f1aBAOa.pgp Description: PGP signature
Re: Scheduling 2.6.17-1
Hello, I would like to reschedule the uploads: Unless someone objects, we will upload both linux-2.6.16 and linux-2.6 to unstable tomorrow, 20th of June. - linux-2.6 2.6.17-1 is what we have in dists/trunk/linux-2.6 now. - linux-2.6.16 2.6.16-15 is what we have in dists/sid/linux-2.6 now, Bastian will apply the needed changes to the build system later today and rename the source package accordingly. If someone needs more time for the one or the other kernel version, please raise your voice so we can reschedule again. Best regards Frederik Schueler -- ENOSIG signature.asc Description: Digital signature
Re: Scheduling 2.6.17-1
On Sunday 18 June 2006 23:58, Frederik Schueler wrote: > The problem is: we need a kernel >> 2.6.15 in testing ASAP (2.6.15 is > really old, and d-i needs a new kernel for the next release candidate). That is correct. Now that the testing archive for amd64 is complete (for the purposed of new installations), we'd like to prepare a new beta release of d-i ASAP. The main blocker for this is the lack of 2.6.16 in testing. From that point of view a (last?) 2.6.16 upload that builds for all arches and the opportunity to build kernel udebs from that upload would be very much appreciated. Looking at other posts to this thread it seems to me that having to wait for 2.6.17 would mean a delay of at least a month which would also hurt the commitments the d-i team has made for the release of Etch. Whether or not to do that in parallel to a 2.6.17 upload is up to the kernel team. Cheers, FJP pgpc0ycjOQAzS.pgp Description: PGP signature
Processed: really adjust severity
Processing commands for [EMAIL PROTECTED]: > severity 374378 important Bug#374378: initramfs-tools: Fails to initialize LVM if pvmove was ran without completing Severity set to `important' from `critical' > End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#367125: ext2_get_inode: bad inode number
Hello Goswin,On 6/16/06, Goswin von Brederlow <[EMAIL PROTECTED]> wrote: Did you reboot the nfs server while clients had the fs mounted? Orstoped the nfsd and run fsck or a resize? Anything that could change the inode numbers without the clients getting any notice?Yes, we rebooted and recreated the filesystem from a backup.We suspect that the inode numbers must have changed. I noticed this and can reproduce it by running exportfs -u, umount,resize2fs, mount, exportfs and then accessing some previously usedfile on the nfs clients. The client (or server?) still has the oldinode numbers cached and directly access the inodes while the resize2fs has removed it. The ext2-fs gives an error and remounts itread-only.That's interesting, didn't think it was so easy to reproduce -have to try that.Does it also remount the filesystem read-only when mounted with the errors=continue mount option? I even have fears that this is caused solely by the client caching the inode for the file. If that is the case then a malicious client couldsend requests for faked inodes causing ext2-fs errors on the serverand forcing the nfs share into read-only mode. An ugly DOS attack. Yes, that's what i think as well.Regards, Peter
Re: Scheduling 2.6.17-1
On Mon, Jun 19, 2006 at 08:12:06AM +0200, Bastian Blank wrote: > On Sun, Jun 18, 2006 at 04:44:01PM -0600, dann frazier wrote: > > Yeah, istr having an issue like that as well. We should probably keep the > > 2.6.16 compiler hardcoded to whatever is the default in etch when we > > upload (its still gcc-4.0 today, right)? > > It will be hardcoded to -4.0 with the next upload. And no, going to -4.1 > is no solution. Is there a way to override this? m68k kernels were built with gcc-3.3, I never even tried to use gcc-4.0. Also, is the fix for cross-building header packages in now as well? When cross-building those, the package ended up having i386 binaries, which obviously do not run on m68k, causing several packages to fail building. Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
