Re: 2.4.5-ac13, APM, and Dell Inspiron 8000
Juri Haberland wrote: > > You wrote: > > > > I've been running 2.4.5 on my new Dell I8000 without too many > > problems. Last night I built -ac13 (on my porch) and booted it > > without incident. Later, going inside and re-connecting the AC I > > notice that the thing's hung. I play around a bit and discover that > > the act of plugging or unplugging the power cord will hang the box. > > > > This lead me to disable all power manglement in the BIOS. No joy. > > > > This problem does not exist using straight 2.4.5. > > > > Has anybody else seen this? Any debugging suggestions? Or stated > > differently, has anybody with this machine arrived at a configuration > > that avoids weirdness in the power management framework? > > Ok, I just tried that and my i8000 locked up as well. No problems with > 2.4.5 as well. I have also another problem: > Running with -ac13 it doesn't poweroff properly - but it did running > 2.4.5. Sometimes it just stops where it should poweroff and locks hard, > sometimes it blanks the display before locking up hard. The Dell i5000e crashes when switching between mains and battery when the disk is active, so you might try to plug/unplug with the system quiet. If this works, you'll be in a *little* better spot. As for hanging, you might try suspending it (i.e., close the display) and opening it back up. This works for the i5000e; it also clears the display that sometimes goes *nuts* when switching video modes. This last behavior has only surfaced with the latest A06 BIOS. -- David N. Lombard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: 2.4.5-ac13, APM, and Dell Inspiron 8000
Juri Haberland wrote: You wrote: I've been running 2.4.5 on my new Dell I8000 without too many problems. Last night I built -ac13 (on my porch) and booted it without incident. Later, going inside and re-connecting the AC I notice that the thing's hung. I play around a bit and discover that the act of plugging or unplugging the power cord will hang the box. This lead me to disable all power manglement in the BIOS. No joy. This problem does not exist using straight 2.4.5. Has anybody else seen this? Any debugging suggestions? Or stated differently, has anybody with this machine arrived at a configuration that avoids weirdness in the power management framework? Ok, I just tried that and my i8000 locked up as well. No problems with 2.4.5 as well. I have also another problem: Running with -ac13 it doesn't poweroff properly - but it did running 2.4.5. Sometimes it just stops where it should poweroff and locks hard, sometimes it blanks the display before locking up hard. The Dell i5000e crashes when switching between mains and battery when the disk is active, so you might try to plug/unplug with the system quiet. If this works, you'll be in a *little* better spot. As for hanging, you might try suspending it (i.e., close the display) and opening it back up. This works for the i5000e; it also clears the display that sometimes goes *nuts* when switching video modes. This last behavior has only surfaced with the latest A06 BIOS. -- David N. Lombard - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Boot Problem
Patric Mrawek wrote: > > Hi, > > sometimes one of my servers doesn't boot correctly. Lilo reads the > kernel-image, but doesn't decompress it. So the system won't > continue booting. > > Looks like: > Loading linux... > (at this point the machine freezes) Our experience of this has been with suspect hardware. It was our first (pre-release) P4 system, so we puzzled over it for a short while; later testing on other P4 systems showed no such problem. -- David N. Lombard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: Boot Problem
Patric Mrawek wrote: Hi, sometimes one of my servers doesn't boot correctly. Lilo reads the kernel-image, but doesn't decompress it. So the system won't continue booting. Looks like: Loading linux... (at this point the machine freezes) Our experience of this has been with suspect hardware. It was our first (pre-release) P4 system, so we puzzled over it for a short while; later testing on other P4 systems showed no such problem. -- David N. Lombard - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] s_maxbytes handling
Linus Torvalds wrote: > [deletia] > > So returning 0 for write() is usually a bad idea - exactly because it > does not have very well-defined semantics. So -EFBIG is certainly the > preferable return value, and seems to be what SuS wants, too. And what LFS wants too: 2.2.1.27 write() and writev() DESCRIPTION For regular files, no data transfer will occur past the offset maximum established in the open file description associated with fildes. ERRORS These functions will fail if: [EFBIG] The file is a regular file, nbyte is greater than 0 and the starting position is greater than or equal to the offset maximum established in the open file description associated with fildes. Note: This is an additional EFBIG error condition. -- David N. Lombard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: New XFS, ReiserFS and Ext2 benchmarks
Rik van Riel wrote: > > On Tue, 22 May 2001, Daniel Phillips wrote: > > On Tuesday 22 May 2001 12:29, Daniel Phillips wrote: > > > > http://nl.linux.org/~phillips/htree > > > > Oops, nl.linux.org was down for 'unscheduled maintainance' and seems > > to have come back up with some some http issues. > > > > Rik? > > [/home]# chmod a+x * > > Things seem to work again now ;) > Not so much: Forbidden You don't have permission to access /~phillips/htree/ on this server. Apache/1.3.14 Server at nl.linux.org Port 80 -- David N. Lombard - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: New XFS, ReiserFS and Ext2 benchmarks
Rik van Riel wrote: On Tue, 22 May 2001, Daniel Phillips wrote: On Tuesday 22 May 2001 12:29, Daniel Phillips wrote: http://nl.linux.org/~phillips/htree Oops, nl.linux.org was down for 'unscheduled maintainance' and seems to have come back up with some some http issues. Rik? [/home]# chmod a+x * Things seem to work again now ;) Not so much: Forbidden You don't have permission to access /~phillips/htree/ on this server. Apache/1.3.14 Server at nl.linux.org Port 80 -- David N. Lombard - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [patch] s_maxbytes handling
Linus Torvalds wrote: [deletia] So returning 0 for write() is usually a bad idea - exactly because it does not have very well-defined semantics. So -EFBIG is certainly the preferable return value, and seems to be what SuS wants, too. And what LFS wants too: 2.2.1.27 write() and writev() DESCRIPTION For regular files, no data transfer will occur past the offset maximum established in the open file description associated with fildes. ERRORS These functions will fail if: [EFBIG] The file is a regular file, nbyte is greater than 0 and the starting position is greater than or equal to the offset maximum established in the open file description associated with fildes. Note: This is an additional EFBIG error condition. -- David N. Lombard - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: [PATCH] Boot Logo - cleanup and configuration
Rick Miller wrote: > > Axel, are these changes to the kernel configuration options okay with > you? > > Kernel Developers, please try this one out. I don't have any non-i386 > architecture machines to try this out on. > > Various changes to unify and automate the frame buffer boot graphic and > to offer kernel configuration options for quelling printk()'s and > centering the graphic to make a nice, professional-looking first > impression on all those consumer-device users. :-) [deletia] > The url: http://execpc.com/~rdmiller/Linux/kernel-bootlogo.patch.gz > (It's about 380k.) Are you sure about this patch? Take a look a list of the patches files; also look at the last four lines of the patch file. -- David N. Lombard MSC.Software - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Booting new kernel from running kernel
Frank Smith wrote: > > Hi, > > I'm trying to figure out a way to immediately boot a > new kernel from within a running system. I do not > care about gracefully shutting down the first kernel.. > once I decide to run the new kernel, I'll abandon the > first. Take a look at http://www.scyld.com/software/monte.html -- David N. Lombard MSC.Software - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
Re: Booting new kernel from running kernel
Frank Smith wrote: Hi, I'm trying to figure out a way to immediately boot a new kernel from within a running system. I do not care about gracefully shutting down the first kernel.. once I decide to run the new kernel, I'll abandon the first. Take a look at http://www.scyld.com/software/monte.html -- David N. Lombard MSC.Software - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
