Re: Bug#261824: time's up
On Wed, Mar 23, 2005 at 07:54:14AM -0500, Ben Collins wrote: > I did the "new upstream", so I can tell you that it was only a couple of > lines of code changes, and they were tested well before being put into the > silo repo. > I don't think it needs extensive testing. It seems that this version of silo ended up being used to build the CDs for d-i RC3 (even though the .deb *on* the CDs came from testing), so it's already getting more extensive testing than I think we bargained for. It also seems to be holding up well under it, so I'm going ahead and approving 1.4.9-1 for testing, barring the appearance of any last-minute RC bugs. Thanks, -- Steve Langasek postmodern programmer > On Wed, Mar 23, 2005 at 12:34:14AM -0800, Steve Langasek wrote: > > On Tue, Mar 22, 2005 at 05:30:55AM -0500, Ben Collins wrote: > > > Can the silo I just uploaded go into testing atleast? It does fix some > > > bugs. In fact, it may fix some of the rc silo bugs, but I need testing > > > with it to make sure (didn't want to claim the bugs were fixed without > > > testing by others first). > > > > It fixes the RC build-dependency bug, so it should probably go in; but given > > that it's a new upstream version, it should get a fair measure of testing > > first -- at least to verify it hasn't caused any major regressions, whether > > or not it fixes the outstanding bugs. > > > > Thanks, > > -- > > Steve Langasek > > postmodern programmer signature.asc Description: Digital signature
Re: Testers wanted for kernel/discover1
On Thu, 24 Mar 2005, Frans Pop wrote: I still get the errors on boot: [...] kernel: Partition check: kernel: hda:end_request: I/O error, dev 03:00 (hda), sector 0 kernel: end_request: I/O error, dev 03:00 (hda), sector 2 kernel: end_request: I/O error, dev 03:00 (hda), sector 4 kernel: end_request: I/O error, dev 03:00 (hda), sector 6 kernel: end_request: I/O error, dev 03:00 (hda), sector 8 kernel: end_request: I/O error, dev 03:00 (hda), sector 10 kernel: end_request: I/O error, dev 03:00 (hda), sector 12 kernel: end_request: I/O error, dev 03:00 (hda), sector 14 kernel: end_request: I/O error, dev 03:00 (hda), sector 0 kernel: end_request: I/O error, dev 03:00 (hda), sector 2 kernel: end_request: I/O error, dev 03:00 (hda), sector 4 kernel: end_request: I/O error, dev 03:00 (hda), sector 6 kernel: end_request: I/O error, dev 03:00 (hda), sector 8 kernel: end_request: I/O error, dev 03:00 (hda), sector 10 kernel: end_request: I/O error, dev 03:00 (hda), sector 12 kernel: end_request: I/O error, dev 03:00 (hda), sector 14 kernel: unable to read partition table Hi Frans, Thanks for testing. These errors appear to be harmless and were reported before as 273062. I don't really know what we can do about them. Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Testers wanted for kernel/discover1
On Wed, 23 Mar 2005, David S. Miller wrote: That's great that you were able to make this work. What was the exact kernel config change you made to achieve this? I ask because I hate letting things like this go and just say "great it works now", I'd like to sit down and try and figure out what the actual cause was. Thanks Jurij. Hi Dave, I used my favourite clueless poking technique and it "Just worked" :-). Below I am including the diff between the "broken" sparc64 config (currently in the archive) and the new "fixed" one. You can extract the complete config from any kernel-image .deb by unpacking it with 'dpkg -x kernel-image-.deb .' and looking in boot subdirectory. --- old/boot/config-2.4.27-2-sparc642005-02-14 22:02:21.0 -0500 +++ new/boot/config-2.4.27-2-sparc642005-03-18 22:51:10.0 -0500 @@ -415,12 +415,12 @@ # # ATA/IDE/MFM/RLL support # -CONFIG_IDE=y +CONFIG_IDE=m # # IDE, ATA and ATAPI Block devices # -CONFIG_BLK_DEV_IDE=y +CONFIG_BLK_DEV_IDE=m # # Please see Documentation/ide.txt for help/info on IDE drives @@ -428,7 +428,7 @@ # CONFIG_BLK_DEV_HD_IDE is not set # CONFIG_BLK_DEV_HD is not set CONFIG_BLK_DEV_IDEDISK=m -# CONFIG_IDEDISK_MULTI_MODE is not set +CONFIG_IDEDISK_MULTI_MODE=y # CONFIG_IDEDISK_STROKE is not set # CONFIG_BLK_DEV_IDECS is not set CONFIG_BLK_DEV_IDECD=m @@ -460,7 +460,7 @@ CONFIG_BLK_DEV_AMD74XX=m # CONFIG_AMD74XX_OVERRIDE is not set CONFIG_BLK_DEV_ATIIXP=m -CONFIG_BLK_DEV_CMD64X=y +CONFIG_BLK_DEV_CMD64X=m # CONFIG_BLK_DEV_TRIFLEX is not set CONFIG_BLK_DEV_CY82C693=m CONFIG_BLK_DEV_CS5530=m Best regards, Jurij Smakov[EMAIL PROTECTED] Key: http://www.wooyd.org/pgpkey/ KeyID: C99E03CC -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Wir stellen diese Kontakte für Sie her!
Title: Wir stellen diese Kontakte für Sie her! Guten Tagdebian-sparc@lists.debian.org Freitag, 25. März 2005Veröffentlichen Sie kostenlos Ihre Anzeige in unserem Anzeigenmarkt.Täglich besuchen 54 000 User unsere Suchportale, wer hier inseriert hat Erfolg.Ihre Zugangsdaten erhalten Sie unter Informations-Formular Unsere Meta Suchmaschine durchforstet das Internet nach aktuellen Homepages,und versucht die gefundenen Homepages dann in die Suchmaschine einzutragen.Wir wollen Sie aber nicht ohne Ihr Wissen in unsere Suchmaschine Eintragen.Deshalb bitten wir Sie, fordern Sie die Zugangsdaten kostenlos an.Ihre Zugangsdaten erhalten Sie unter Informations-Formular Kostenlos anmelden können Sie sich dann in den SuchmaschinenDeutschland, Osterreich, Schweiz, Mallorca, Branchenbuch, Webkatalog, Reisebüro und Shop.Mit freundlichen GrüssenJürgen Tomas Agentur EspañaApartado 607510 Sineu/EspañaE-Mail: [EMAIL PROTECTED]
Re: RFC and status report: Kernel upgrades for woody->sarge upgrades
Actualy the SS5 (at least the one I have got here) does have the problem for libc6 version I need a kernel above 2.4.21, and for that kernel I need that libc6 version. - Original Message - From: "Steve Langasek" <[EMAIL PROTECTED]> To: ; Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 24, 2005 11:44 PM Subject: Re: RFC and status report: Kernel upgrades for woody->sarge upgrades -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC and status report: Kernel upgrades for woody->sarge upgrades
On Thu, Mar 24, 2005 at 02:57:35PM +0100, Robin Harmsen wrote: > at this moment I am testing the Debian Installer on a SS5 (sun4m I thougt) > cause I wanted a newer kernel then 2.2.20. but it isn't working very well > I am willing to test this upgrade-kernel to get a beter kernel and be able > to do a woody->sarge upgrade > I think I will start with it right afther I finished my test with the > debian installer and filled in a report > I hope I will be able to help :) To the best of our knowledge, the SS5 is not one of the systems affected by this upgrade issue; only systems using the Cypress chips are known to be affected. -- Steve Langasek postmodern programmer signature.asc Description: Digital signature
Re: Sparc32 Floppy Eject
On Thu, 24 Mar 2005 14:27:27 +0100
Frans Pop <[EMAIL PROTECTED]> wrote:
> David: do you maybe have some ideas?
If you are referring to me here, can I ask that you CC: people
you wish to get the attention of? I only noticed this by accident
while scanning my debian-sparc folder.
I can't think of anything changed in the floppy driver that would
break this. It's a very simple ioctl (FDEJECT), so the only places
where this could be effected are:
1) arch/sparc64/kernel/ioctl32.c, and fs/compat_ioctl.c (which the former
includes), make sure FDEJECT is marked properly so that 32-bit
binaries can use this ioctl properly, if this is occuring
on a sparc64 kernel
2) check the FDEJECT handling in drivers/block/fd.c and
include/asm-sparc{,64}/floppy.h
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC and status report: Kernel upgrades for woody->sarge upgrades
I installed a minimal basic "stable" installation of Debian (no packages selected with tasksel or dselect) when doing the upgade as stated on http://higgs.djpig.de/upgrade/upgrade-kernel/ via the dpkg method. I first needed to install zlib1g, ash and stat. maby it is better to mention that those need to be installed prior. and there is no mentioning of what to change in silo.conf cause you need to specify the initrd somehow. I added: initrd=1/initrd.img is this correct? afther rebooting I get the following error(s): modprobe: Noting to load ??? Specify at least a module or a wildcard like \* pivot_root: No such file or directory /sbin/init: cannot open dev/console: no such file Kernel panic: Attempted to kill init! - Original Message - From: "Frank Lichtenheld" <[EMAIL PROTECTED]> To: ; ; Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody->sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC and status report: Kernel upgrades for woody->sarge upgrades
I installed a minimal basic "stable" installation of Debian (no packages selected with tasksel or dselect) when doing the upgade as stated on http://higgs.djpig.de/upgrade/upgrade-kernel/ via the dpkg method. I first needed to install zlib1g, ash and stat. maby it is better to mention that those need to be installed prior. and there is no mentioning of what to change in silo.conf cause you need to specify the initrd somehow. I added: initrd=1/initrd.img is this correct? afther rebooting I get the following error(s): modprobe: Noting to load ??? Specify at least a module or a wildcard like \* pivot_root: No such file or directory /sbin/init: cannot open dev/console: no such file Kernel panic: Attempted to kill init! - Original Message - From: "Frank Lichtenheld" <[EMAIL PROTECTED]> To: ; ; Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody->sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC and status report: Kernel upgrades for woody->sarge upgrades
Hi Matthew, On Thursday, 24 Mar 2005, you wrote: > On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: > > As many of you may know on some machines users will need to install > > a current kernel before they will be able to upgrade woody to sarge > > (or better: glibc of woody to glibc of sarge). I've tried to use the > > available information to provide the needed files for these kernel > > upgrades. > > To my knowledge the affected machines/architecures are currently > > hppa64, sparc sun4m (only some of them) and 80386. > > It's all hppa machines, not just hppa64. IIRC we did some upgrade tests on hppa(32) at the BSP in Frankfurt in November last year and had no problems with that, but i might be wrong. Frank, could you please confirm this, as i recall you and Uli did these tests Greetings Martin -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC and status report: Kernel upgrades for woody->sarge upgrades
On Thu, Mar 24, 2005 at 02:31:55PM +0100, Frank Lichtenheld wrote: > As many of you may know on some machines users will need to install > a current kernel before they will be able to upgrade woody to sarge > (or better: glibc of woody to glibc of sarge). I've tried to use the > available information to provide the needed files for these kernel > upgrades. > To my knowledge the affected machines/architecures are currently > hppa64, sparc sun4m (only some of them) and 80386. It's all hppa machines, not just hppa64. > I've prepared the necessary backports and some rudimentary documentation > and put it online at > http://higgs.djpig.de/upgrade/upgrade-kernel/ I'll give it a try now. -- "Next the statesmen will invent cheap lies, putting the blame upon the nation that is attacked, and every man will be glad of those conscience-soothing falsities, and will diligently study them, and refuse to examine any refutations of them; and thus he will by and by convince himself that the war is just, and will thank God for the better sleep he enjoys after this process of grotesque self-deception." -- Mark Twain -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC and status report: Kernel upgrades for woody->sarge upgrades
Frank Lichtenheld wrote: > Hi all. > > As many of you may know on some machines users will need to install > a current kernel before they will be able to upgrade woody to sarge > (or better: glibc of woody to glibc of sarge). I've tried to use the > available information to provide the needed files for these kernel > upgrades. > To my knowledge the affected machines/architecures are currently > hppa64, sparc sun4m (only some of them) and 80386. JFTR, all mips/mipsel subarchitectures are also affected. For those, however, the sarge kernel without userland backports is good enough, because modules aren't needed for basic system operation. Thiemo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFC and status report: Kernel upgrades for woody->sarge upgrades
Hi, at this moment I am testing the Debian Installer on a SS5 (sun4m I thougt) cause I wanted a newer kernel then 2.2.20. but it isn't working very well I am willing to test this upgrade-kernel to get a beter kernel and be able to do a woody->sarge upgrade I think I will start with it right afther I finished my test with the debian installer and filled in a report I hope I will be able to help :) Greetings Robin Harmsen [EMAIL PROTECTED] http://www.rharmsen.nl - Original Message - From: "Frank Lichtenheld" <[EMAIL PROTECTED]> To: ; ; Cc: <[EMAIL PROTECTED]> Sent: Thursday, March 24, 2005 2:31 PM Subject: RFC and status report: Kernel upgrades for woody->sarge upgrades Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFC and status report: Kernel upgrades for woody->sarge upgrades
Hi all. As many of you may know on some machines users will need to install a current kernel before they will be able to upgrade woody to sarge (or better: glibc of woody to glibc of sarge). I've tried to use the available information to provide the needed files for these kernel upgrades. To my knowledge the affected machines/architecures are currently hppa64, sparc sun4m (only some of them) and 80386. Because of the pain to maintain a kernel backport over the lifetime of sarge we have decided to only offer backports of the needed tools (modutils, module-init-tools and initrd-tools) to use stock sarge kernels on woody. It is planned to upload these files together with some documentation into a upgrade-kernel (or whatever else name the ftpmasters will prefer) directory in the archive. I've prepared the necessary backports and some rudimentary documentation and put it online at http://higgs.djpig.de/upgrade/upgrade-kernel/ We now need people that - test the backports - read/comment on/improve the documentation Gruesse, -- Frank Lichtenheld <[EMAIL PROTECTED]> www: http://www.djpig.de/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Sparc32 Floppy Eject
On Thursday 24 March 2005 10:13, Geert Stappers wrote: > So the question is probably: > > Where is the eject of floppies done? From googling and a look at kernel sources, it looks as if automatic ejection of the boot floppy before loading the root floppy is some kind of sparc kernel magic. To recap: - the RC3 sparc32 root floppy with kernel 2.4.27 ejects automatically - the RC3 sparc32 root floppy with kernel 2.6.8 fails to eject (see installation reports #301086 and #301088) There have been some changes in drivers/block/floppy.c between 2.4.27 and 2.6.8 kernel, but I can't tell if these could be responsible for the difference in behavior. David: do you maybe have some ideas? Cheers, FJP pgpO2TzeL0Ho4.pgp Description: PGP signature
Re: Testers wanted for kernel/discover1
On Thursday 24 March 2005 05:51, Jurij Smakov wrote: > We have a couple of pretty important bugfixes, which I would like to see > tested as soon (and as much) as possible. Those are: > > * Modular IDE in kernel 2.4.27. That change potentially may affect all > sparc machines with IDE controllers I've tested this kernel on my Ultra 10 which has the CMD64x controller. I still get the errors on boot: kernel: Uniform Multi-Platform E-IDE driver Revision: 7.00beta4-2.4 kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx kernel: CMD646: IDE controller at PCI slot 01:03.0 kernel: CMD646: chipset revision 3 kernel: CMD646: chipset revision 0x03, MultiWord DMA Force Limited kernel: CMD646: 100%% native mode on irq 4,7e0 kernel: ide0: BM-DMA at 0x1fe02c00020-0x1fe02c00027, BIOS settings: hda:pio, hdb:pio kernel: ide1: BM-DMA at 0x1fe02c00028-0x1fe02c0002f, BIOS settings: hdc:pio, hdd:pio kernel: hda: ST34342A, ATA DISK drive kernel: ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx kernel: hdc: CD-ROM 56X/AKH, ATAPI CD/DVD-ROM drive kernel: ide0 at 0x1fe02c0-0x1fe02c7,0x1fe02ca on irq 4,7e0 kernel: ide1 at 0x1fe02c00010-0x1fe02c00017,0x1fe02c0001a on irq 4,7e0 (shared with ide0) kernel: Partition check: kernel: hda:end_request: I/O error, dev 03:00 (hda), sector 0 kernel: end_request: I/O error, dev 03:00 (hda), sector 2 kernel: end_request: I/O error, dev 03:00 (hda), sector 4 kernel: end_request: I/O error, dev 03:00 (hda), sector 6 kernel: end_request: I/O error, dev 03:00 (hda), sector 8 kernel: end_request: I/O error, dev 03:00 (hda), sector 10 kernel: end_request: I/O error, dev 03:00 (hda), sector 12 kernel: end_request: I/O error, dev 03:00 (hda), sector 14 kernel: end_request: I/O error, dev 03:00 (hda), sector 0 kernel: end_request: I/O error, dev 03:00 (hda), sector 2 kernel: end_request: I/O error, dev 03:00 (hda), sector 4 kernel: end_request: I/O error, dev 03:00 (hda), sector 6 kernel: end_request: I/O error, dev 03:00 (hda), sector 8 kernel: end_request: I/O error, dev 03:00 (hda), sector 10 kernel: end_request: I/O error, dev 03:00 (hda), sector 12 kernel: end_request: I/O error, dev 03:00 (hda), sector 14 kernel: unable to read partition table (and of course the "unimplemented Sparc system call 188") However, the system boots fine and as the kernel.log is written without errors, I'm not sure if these errors can safely be ignored or are still an indication that something may fail horribly later... I never really tested older 2.4.27 kernels beyond seeing these messages, so I'm not sure is anything has actually changed. 'fdisk -l /dev/hda' returns the correct output. Cheers, FJP pgpLNdnOLtKvC.pgp Description: PGP signature
