Re: forced umount?
On Sun, Mar 18, 2007 at 08:16:19PM +0100, Arjan van de Ven wrote: > On Fri, 2007-03-16 at 23:06 -0500, Mike Snitzer wrote: > > I'm interested in understanding the state of Linux with regard to > > _really_ forcing a filesystem to unmount. > > > > There is a (stale) project at OSDL that has various implementations: > > http://developer.osdl.org/dev/fumount/ > > > the problem with the people who say they want forced umount is.. that > most of the time they either want > 1) get rid of the namespace entry > or > 2) want to stop any and all IO to a certain device/partition > > 1) is already supported with lazy umount (umount -l) > for 2), it's not forced umount that they want, it's really an IO > disconnect (which scsi supports btw in 2.6 kernels). Could please tell me more about this IO disconnect? How to trigger it etc, any pointers welcome. thanks, -- pozsy - 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: forced umount?
On Sun, Mar 18, 2007 at 08:16:19PM +0100, Arjan van de Ven wrote: On Fri, 2007-03-16 at 23:06 -0500, Mike Snitzer wrote: I'm interested in understanding the state of Linux with regard to _really_ forcing a filesystem to unmount. There is a (stale) project at OSDL that has various implementations: http://developer.osdl.org/dev/fumount/ the problem with the people who say they want forced umount is.. that most of the time they either want 1) get rid of the namespace entry or 2) want to stop any and all IO to a certain device/partition 1) is already supported with lazy umount (umount -l) for 2), it's not forced umount that they want, it's really an IO disconnect (which scsi supports btw in 2.6 kernels). Could please tell me more about this IO disconnect? How to trigger it etc, any pointers welcome. thanks, -- pozsy - 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/
[PATCH] another id for cp2101 driver
This patch adds another usb id to the cp2101. It seems to work well.
Please apply, thanks.
Signed-off-by: Pozsar Balazs <[EMAIL PROTECTED]>
diff -Naurd a/drivers/usb/serial/cp2101.c b/drivers/usb/serial/cp2101.c
--- a/drivers/usb/serial/cp2101.c 2006-07-15 21:00:43.0 +0200
+++ b/drivers/usb/serial/cp2101.c 2007-02-16 12:41:47.0 +0100
@@ -65,6 +65,7 @@
{ USB_DEVICE(0x10C4, 0x813D) }, /* Burnside Telecom Deskmobile */
{ USB_DEVICE(0x10C4, 0x815E) }, /* Helicomm IP-Link 1220-DVM */
{ USB_DEVICE(0x10C4, 0xEA60) }, /* Silicon Labs factory default */
+ { USB_DEVICE(0x10C5, 0xEA61) }, /* Silicon Labs MobiData GPRS USB Modem
*/
{ USB_DEVICE(0x16D6, 0x0001) }, /* Jablotron serial interface */
{ } /* Terminating Entry */
};
--
pozsy
-
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/
[PATCH] another id for cp2101 driver
This patch adds another usb id to the cp2101. It seems to work well.
Please apply, thanks.
Signed-off-by: Pozsar Balazs [EMAIL PROTECTED]
diff -Naurd a/drivers/usb/serial/cp2101.c b/drivers/usb/serial/cp2101.c
--- a/drivers/usb/serial/cp2101.c 2006-07-15 21:00:43.0 +0200
+++ b/drivers/usb/serial/cp2101.c 2007-02-16 12:41:47.0 +0100
@@ -65,6 +65,7 @@
{ USB_DEVICE(0x10C4, 0x813D) }, /* Burnside Telecom Deskmobile */
{ USB_DEVICE(0x10C4, 0x815E) }, /* Helicomm IP-Link 1220-DVM */
{ USB_DEVICE(0x10C4, 0xEA60) }, /* Silicon Labs factory default */
+ { USB_DEVICE(0x10C5, 0xEA61) }, /* Silicon Labs MobiData GPRS USB Modem
*/
{ USB_DEVICE(0x16D6, 0x0001) }, /* Jablotron serial interface */
{ } /* Terminating Entry */
};
--
pozsy
-
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/
[PATCH] Re: msdos/vfat defaults are annoying
On Sun, Feb 06, 2005 at 07:06:59AM +, Christoph Hellwig wrote: > On Sun, Feb 06, 2005 at 12:33:43AM -0500, John Richard Moser wrote: > > I dunno. I can never understand the innards of the kernel devs' minds. > > filesystem detection isn't handled at the kerne level. Yeah, but the link order could be changed... Patch inlined. -- pozsy diff -Naurd a/fs/Makefile b/fs/Makefile --- a/fs/Makefile 2004-08-04 10:52:28.0 +0200 +++ b/fs/Makefile 2004-08-04 11:32:04.510913663 +0200 @@ -57,8 +57,8 @@ obj-$(CONFIG_MINIX_FS) += minix/ obj-$(CONFIG_FAT_FS) += fat/ obj-$(CONFIG_UMSDOS_FS)+= umsdos/ -obj-$(CONFIG_MSDOS_FS) += msdos/ obj-$(CONFIG_VFAT_FS) += vfat/ +obj-$(CONFIG_MSDOS_FS) += msdos/ obj-$(CONFIG_BFS_FS) += bfs/ obj-$(CONFIG_ISO9660_FS) += isofs/ obj-$(CONFIG_DEVFS_FS) += devfs/ Signed-off-by: Pozsar Balazs <[EMAIL PROTECTED]> - 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/
[PATCH] Re: msdos/vfat defaults are annoying
On Sun, Feb 06, 2005 at 07:06:59AM +, Christoph Hellwig wrote: On Sun, Feb 06, 2005 at 12:33:43AM -0500, John Richard Moser wrote: I dunno. I can never understand the innards of the kernel devs' minds. filesystem detection isn't handled at the kerne level. Yeah, but the link order could be changed... Patch inlined. -- pozsy diff -Naurd a/fs/Makefile b/fs/Makefile --- a/fs/Makefile 2004-08-04 10:52:28.0 +0200 +++ b/fs/Makefile 2004-08-04 11:32:04.510913663 +0200 @@ -57,8 +57,8 @@ obj-$(CONFIG_MINIX_FS) += minix/ obj-$(CONFIG_FAT_FS) += fat/ obj-$(CONFIG_UMSDOS_FS)+= umsdos/ -obj-$(CONFIG_MSDOS_FS) += msdos/ obj-$(CONFIG_VFAT_FS) += vfat/ +obj-$(CONFIG_MSDOS_FS) += msdos/ obj-$(CONFIG_BFS_FS) += bfs/ obj-$(CONFIG_ISO9660_FS) += isofs/ obj-$(CONFIG_DEVFS_FS) += devfs/ Signed-off-by: Pozsar Balazs [EMAIL PROTECTED] - 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: VM Requirement Document - v0.0
> Rik> ... but I fail to see this one. If we get a low cache hit rate, > Rik> couldn't that just mean we allocated too little memory for the > Rik> cache ? > Or that we're doing big sequential reads of file(s) which are larger > than memory, in which case expanding the cache size buys us nothing, > and can actually hurt us alot. I've got an idea about how to handle this situation generally (without sending 'tips' to kernel via madvice() or anything similar). Instead of sorting chached pages (i mean blocks of files) by last touch time, and dropping the oldest page(s) if we're sort on memory, i would propose this nicer algorithm: (i this is relevant only to the read cache) Suppose that f1,f2,...fN files cached, their sizes are s1,s2,...sN and that they were last touched t1,t2,...tN seconds ago. (t1 I personally don't feel that the cache should be allowed to grow over > 50% of the system's memory at all, we've got so much in the cache at > that point, that we're probably not hitting it all that much. > > This is why the discussion on the other cache scanning algorithm > (2Q+?) was so interesting, since it looked to handle both the LRU > vs. FIFO tradeoffs very nicely. -- - 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: VM Requirement Document - v0.0
Rik ... but I fail to see this one. If we get a low cache hit rate, Rik couldn't that just mean we allocated too little memory for the Rik cache ? Or that we're doing big sequential reads of file(s) which are larger than memory, in which case expanding the cache size buys us nothing, and can actually hurt us alot. I've got an idea about how to handle this situation generally (without sending 'tips' to kernel via madvice() or anything similar). Instead of sorting chached pages (i mean blocks of files) by last touch time, and dropping the oldest page(s) if we're sort on memory, i would propose this nicer algorithm: (i this is relevant only to the read cache) Suppose that f1,f2,...fN files cached, their sizes are s1,s2,...sN and that they were last touched t1,t2,...tN seconds ago. (t1t2...tN) Now we shouldn't automatically choose pages of fN to drop, instead a probability (chance) could be assigned to each file, for example: fI*sI*tI/SUM where I is one of 1,2,...,N, and SUM is the SUM of fI*sI*tI. With this, mostly newer files would stay in cache, but older files would still have a chance. This could also be tuned, for example to take into account 't' more, the fI*sI*tI*tI could be used... and so on, we have infinite possibilities. have a nice day, Balazs Pozsar. ps: If 'my' idea is the which is already used in the kernel, then tell me :) and give me some points were to read more before telling stupid things. I personally don't feel that the cache should be allowed to grow over 50% of the system's memory at all, we've got so much in the cache at that point, that we're probably not hitting it all that much. This is why the discussion on the other cache scanning algorithm (2Q+?) was so interesting, since it looked to handle both the LRU vs. FIFO tradeoffs very nicely. -- - 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: very strange (semi-)lockups in 2.4.5
First I thought this was an X-issue, but now I'm 100% sure that it isn't, as I met the desscribed hangup while working on the console too. The NMI card would be interesting, if anyone tells me how to make one, and how to patch the kernel to show useable information i'm looking forward to do it, and send reports. regards Balazs Pozsar. On Mon, 18 Jun 2001, Albert D. Cahalan wrote: > Pozsar Balazs writes: > > > I'm having ~2 lockups a day. The following happens: > > If I was under X, i only can use the magic-key, but no other keyboard (eg > > numlock) or mouse response, the screen freezes, processes stop. > > If i was using textmode: > > numlock still works > > cursor blinks > > processess stop (eg, gpm doesn't work, outputs freeze) > > i can still switch vt's. > > BUT, i can only type into a few vt's, last time into 3,5,6,7,8, but not > > into 1,2 or 4! > > > > I cannot give you any traces, as i dont have any. > > > > Also note that magic-key works, and it says that it umounts filesystems if > > i press magic-u, but next time at mount i see that reiserfs is replaying > > transactions. > > > > > > Any ideas? > > > > The machine is a P3-750, 512M ram, abit vp6 mb. No overclocking, and it > > passes memtest86. > > I think I'm getting the same thing, but I don't have the magic-key > compiled in. I'm going to hook up a VT510 to the serial port, in case > this is just XFree86 crashing. For anyone collecting statistics: > > kernels 2.4.4-pre6 (?) and now 2.4.6-pre3 > plain Pentium MMX @ 200 MHz > Intel motherboard -- see below > stable since 1996, on a UPS, dust-free, and the fan works > one lockup per day with desktop usage > > In case the serial console doesn't work, could someone post plans > for a safe NMI board? (both ISA and PCI) The best I found: > http://www.sandelman.ottawa.on.ca/linux-ipsec/html/2000/02/msg00425.html > http://www.sandelman.ottawa.on.ca/linux-ipsec/html/2000/02/msg00391.html > (for PCI you're supposed to assert SERR# on the clock -- how?) > > 00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01) > 00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 01) > 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) > 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) > 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 01) > 00:11.0 Ethernet controller: Digital Equipment Corporation DECchip 21040 [Tulip] >(rev 23) > 00:13.0 Ethernet controller: Lite-On Communications Inc LNE100TX Fast Ethernet >Adapter (rev 25) > 00:14.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) > -- - 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/
very strange (semi-)lockups in 2.4.5
Hi all. I'm having ~2 lockups a day. The following happens: If I was under X, i only can use the magic-key, but no other keyboard (eg numlock) or mouse response, the screen freezes, processes stop. If i was using textmode: numlock still works cursor blinks processess stop (eg, gpm doesn't work, outputs freeze) i can still switch vt's. BUT, i can only type into a few vt's, last time into 3,5,6,7,8, but not into 1,2 or 4! I cannot give you any traces, as i dont have any. Also note that magic-key works, and it says that it umounts filesystems if i press magic-u, but next time at mount i see that reiserfs is replaying transactions. Any ideas? The machine is a P3-750, 512M ram, abit vp6 mb. No overclocking, and it passes memtest86. Balazs Pozsar. -- - 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/
very strange (semi-)lockups in 2.4.5
Hi all. I'm having ~2 lockups a day. The following happens: If I was under X, i only can use the magic-key, but no other keyboard (eg numlock) or mouse response, the screen freezes, processes stop. If i was using textmode: numlock still works cursor blinks processess stop (eg, gpm doesn't work, outputs freeze) i can still switch vt's. BUT, i can only type into a few vt's, last time into 3,5,6,7,8, but not into 1,2 or 4! I cannot give you any traces, as i dont have any. Also note that magic-key works, and it says that it umounts filesystems if i press magic-u, but next time at mount i see that reiserfs is replaying transactions. Any ideas? The machine is a P3-750, 512M ram, abit vp6 mb. No overclocking, and it passes memtest86. Balazs Pozsar. -- - 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: very strange (semi-)lockups in 2.4.5
First I thought this was an X-issue, but now I'm 100% sure that it isn't, as I met the desscribed hangup while working on the console too. The NMI card would be interesting, if anyone tells me how to make one, and how to patch the kernel to show useable information i'm looking forward to do it, and send reports. regards Balazs Pozsar. On Mon, 18 Jun 2001, Albert D. Cahalan wrote: Pozsar Balazs writes: I'm having ~2 lockups a day. The following happens: If I was under X, i only can use the magic-key, but no other keyboard (eg numlock) or mouse response, the screen freezes, processes stop. If i was using textmode: numlock still works cursor blinks processess stop (eg, gpm doesn't work, outputs freeze) i can still switch vt's. BUT, i can only type into a few vt's, last time into 3,5,6,7,8, but not into 1,2 or 4! I cannot give you any traces, as i dont have any. Also note that magic-key works, and it says that it umounts filesystems if i press magic-u, but next time at mount i see that reiserfs is replaying transactions. Any ideas? The machine is a P3-750, 512M ram, abit vp6 mb. No overclocking, and it passes memtest86. I think I'm getting the same thing, but I don't have the magic-key compiled in. I'm going to hook up a VT510 to the serial port, in case this is just XFree86 crashing. For anyone collecting statistics: kernels 2.4.4-pre6 (?) and now 2.4.6-pre3 plain Pentium MMX @ 200 MHz Intel motherboard -- see below stable since 1996, on a UPS, dust-free, and the fan works one lockup per day with desktop usage In case the serial console doesn't work, could someone post plans for a safe NMI board? (both ISA and PCI) The best I found: http://www.sandelman.ottawa.on.ca/linux-ipsec/html/2000/02/msg00425.html http://www.sandelman.ottawa.on.ca/linux-ipsec/html/2000/02/msg00391.html (for PCI you're supposed to assert SERR# on the clock -- how?) 00:00.0 Host bridge: Intel Corporation 430TX - 82439TX MTXC (rev 01) 00:07.0 ISA bridge: Intel Corporation 82371AB PIIX4 ISA (rev 01) 00:07.1 IDE interface: Intel Corporation 82371AB PIIX4 IDE (rev 01) 00:07.2 USB Controller: Intel Corporation 82371AB PIIX4 USB (rev 01) 00:07.3 Bridge: Intel Corporation 82371AB PIIX4 ACPI (rev 01) 00:11.0 Ethernet controller: Digital Equipment Corporation DECchip 21040 [Tulip] (rev 23) 00:13.0 Ethernet controller: Lite-On Communications Inc LNE100TX Fast Ethernet Adapter (rev 25) 00:14.0 VGA compatible controller: ATI Technologies Inc 3D Rage Pro 215GP (rev 5c) -- - 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: [test-PATCH] Re: [QUESTION] 2.4.x nice level
On Wed, Apr 11, 2001 at 12:53:16PM -0300, Rik van Riel wrote: > On Wed, 11 Apr 2001, Rik van Riel wrote: > > > OK, here it is. It's nothing like montavista's singing-dancing > > scheduler patch that does all, just a really minimal change that > > should stretch the nice levels to yield the following CPU usage: > > > > Nice05 10 15 19 > > %CPU 100 56 2561 > > PID USER PRI NI SIZE SWAP RSS SHARE STAT %CPU %MEM TIME COMMAND > 980 riel 17 0 2960 296 240 R54.1 0.5 54:19 loop > 1005 riel 16 5 2960 296 240 R N 27.0 0.5 0:34 loop > 1006 riel 17 10 2960 296 240 R N 13.5 0.5 0:16 loop > 1007 riel 18 15 2960 296 240 R N 4.5 0.5 0:05 loop > 987 riel 20 19 2960 296 240 R N 0.4 0.5 0:25 loop How does this scale to negative nice levels? Afaik it should, in some way. (I don't mean that it's wrong in this state, i'm just asking). regards, Balazs. - 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: [test-PATCH] Re: [QUESTION] 2.4.x nice level
On Wed, Apr 11, 2001 at 12:53:16PM -0300, Rik van Riel wrote: On Wed, 11 Apr 2001, Rik van Riel wrote: OK, here it is. It's nothing like montavista's singing-dancing scheduler patch that does all, just a really minimal change that should stretch the nice levels to yield the following CPU usage: Nice05 10 15 19 %CPU 100 56 2561 PID USER PRI NI SIZE SWAP RSS SHARE STAT %CPU %MEM TIME COMMAND 980 riel 17 0 2960 296 240 R54.1 0.5 54:19 loop 1005 riel 16 5 2960 296 240 R N 27.0 0.5 0:34 loop 1006 riel 17 10 2960 296 240 R N 13.5 0.5 0:16 loop 1007 riel 18 15 2960 296 240 R N 4.5 0.5 0:05 loop 987 riel 20 19 2960 296 240 R N 0.4 0.5 0:25 loop How does this scale to negative nice levels? Afaik it should, in some way. (I don't mean that it's wrong in this state, i'm just asking). regards, Balazs. - 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: problem in drivers/block/Config.in (PATCH)
On Fri, Mar 30, 2001 at 10:17:08PM +0200, Herbert Rosmanith wrote: > > hi, > > I noticed that the option CONFIG_PARIDE_PARPORT will always be "y", > even if CONFIG_PARIDE_PARPORT="n". I checked with kernels 2.2.18 > and 2.2.19. > > the file responsible is "drivers/block/Config.in", around line 126. > it reads: > > # PARIDE doesn't need PARPORT, but if PARPORT is configured as a module, > # PARIDE must also be a module. The bogus CONFIG_PARIDE_PARPORT option > # controls the choices given to the user ... > > if [ "$CONFIG_PARPORT" = "y" -o "$CONFIG_PARPORT" = "n" ] ; then >define_bool CONFIG_PARIDE_PARPORT y > else >define_bool CONFIG_PARIDE_PARPORT m > fi > > so, as you can see, CONFIG_PARIDE_PARPORT will be set to "yes" even > if CONFIG_PARPORT="no". > > why not simply write: > > define_bool CONFIG_PARIDE_PARPORT $CONFIG_PARPORT > > instead? In fact, if we want to get what is said in the comment, we should write: if [ "$CONFIG_PARPORT" = "m" -a "$CONFIG_PARIDE_PARPORT" = "y" ] ; then define_bool CONFIG_PARIDE_PARPORT m fi regards, Balazs Pozsar. - 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: problem in drivers/block/Config.in (PATCH)
On Fri, Mar 30, 2001 at 10:17:08PM +0200, Herbert Rosmanith wrote: hi, I noticed that the option CONFIG_PARIDE_PARPORT will always be "y", even if CONFIG_PARIDE_PARPORT="n". I checked with kernels 2.2.18 and 2.2.19. the file responsible is "drivers/block/Config.in", around line 126. it reads: # PARIDE doesn't need PARPORT, but if PARPORT is configured as a module, # PARIDE must also be a module. The bogus CONFIG_PARIDE_PARPORT option # controls the choices given to the user ... if [ "$CONFIG_PARPORT" = "y" -o "$CONFIG_PARPORT" = "n" ] ; then define_bool CONFIG_PARIDE_PARPORT y else define_bool CONFIG_PARIDE_PARPORT m fi so, as you can see, CONFIG_PARIDE_PARPORT will be set to "yes" even if CONFIG_PARPORT="no". why not simply write: define_bool CONFIG_PARIDE_PARPORT $CONFIG_PARPORT instead? In fact, if we want to get what is said in the comment, we should write: if [ "$CONFIG_PARPORT" = "m" -a "$CONFIG_PARIDE_PARPORT" = "y" ] ; then define_bool CONFIG_PARIDE_PARPORT m fi regards, Balazs Pozsar. - 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: esound (esd), 2.4.[12] chopped up sound
> On my home machine playing sound through esd has worked beautifully on various > kernels from 2.2.5 and up to 2.2.18. > On 2.4.1 and 2.4.2 it stinks. > > It sounds like there are small pauses or repetitions in the sound, as if esd > doesn't get > the data quickly enough from the client or something. Music and voices > (realaudio radio) still easy to understand but it does get on my nerves after a > few minutes :( Are you sure that the problem isn't at the mp3->raw conversino point? In mandrake for example, mpg123 is badly compiled, and plays nicely on 2.2, but awfully on 2.4. I suggest you trying another (meybe self-compiled) version of mpg123. bye, Balazs Pozsar. - 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: esound (esd), 2.4.[12] chopped up sound
On my home machine playing sound through esd has worked beautifully on various kernels from 2.2.5 and up to 2.2.18. On 2.4.1 and 2.4.2 it stinks. It sounds like there are small pauses or repetitions in the sound, as if esd doesn't get the data quickly enough from the client or something. Music and voices (realaudio radio) still easy to understand but it does get on my nerves after a few minutes :( Are you sure that the problem isn't at the mp3-raw conversino point? In mandrake for example, mpg123 is badly compiled, and plays nicely on 2.2, but awfully on 2.4. I suggest you trying another (meybe self-compiled) version of mpg123. bye, Balazs Pozsar. - 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/
LDT allocated for cloned task!
hi all, When I was starting X, I got this in the syslog: Mar 17 10:19:20 brefatox kernel: LDT allocated for cloned task! _What is this?_. A grep on /var/log/messages shows that I had this several times. I'm using ext2fs on an IDE drive. Tell me what more info I can provide. Balazs Pozsar. - 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/
LDT allocated for cloned task!
hi all, When I was starting X, I got this in the syslog: Mar 17 10:19:20 brefatox kernel: LDT allocated for cloned task! _What is this?_. A grep on /var/log/messages shows that I had this several times. I'm using ext2fs on an IDE drive. Tell me what more info I can provide. Balazs Pozsar. - 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/
ide-scsi: CoD != 0 in idescsi_pc_intr... -- what is this?
Hi all,
While copying a CD into harddisk, I got the following in the syslog (and
on the console):
Mar 15 14:36:23 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:36:23 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:36:23 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:36:23 brefatox kernel: hde: status error: error=0x00
Mar 15 14:36:23 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:36:46 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:36:46 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:36:46 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:36:46 brefatox kernel: hde: status error: error=0x00
Mar 15 14:36:46 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:02 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:02 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:02 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:02 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:02 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:17 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:17 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:17 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:17 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:17 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:27 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:27 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:27 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:27 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:27 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:28 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:29 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:29 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:29 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:29 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:32 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:32 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:32 brefatox kernel: hde: status error: status=0x08 {
DataRequest }
Mar 15 14:37:32 brefatox kernel: hde: drive not ready for command
Mar 15 14:37:42 brefatox kernel: spurious 8259A interrupt: IRQ7.
Mar 15 14:37:49 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:49 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:49 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:49 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:49 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:38:23 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:38:23 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:38:23 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:38:23 brefatox kernel: hde: status error: error=0x00
Mar 15 14:38:23 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
The copy finished successfully. What is this? Should I care about it? Why
is it? :) (so many questions...)
I was copying copying from hde to hdg. dmesg is at the end.
The cdrom is connected to via a 80c udma66 cable to the first port of the
HPT370 on my Abit VP6 motherboard.
dmesg:
Linux version 2.4.2 ([EMAIL PROTECTED]) (gcc version 2.95.3 19991030 (prerelease)) #1
SMP Wed Mar 7 22:58:36 CET 2001
BIOS-provided physical RAM map:
BIOS-e820: 0009fc00 @ (usable)
BIOS-e820: 0400 @ 0009fc00 (reserved)
BIOS-e820: 0001 @ 000f (reserved)
BIOS-e820: 1000 @ fec0 (reserved)
BIOS-e820: 1000 @ fee0 (reserved)
BIOS-e820: 0001 @ (reserved)
BIOS-e820: 17ef @ 0010 (usable)
BIOS-e820: d000 @ 17ff3000 (ACPI data)
BIOS-e820: 3000 @ 17ff (ACPI NVS)
Scan SMP from c000 for 1024 bytes.
Scan SMP from c009fc00 for 1024 bytes.
Scan SMP from c00f for 65536 bytes.
found SMP MP-table at 000f5770
hm, page 000f5000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f1000 reserved twice.
hm, page 000f2000 reserved twice.
On node 0 totalpages: 98288
zone(0): 4096 pages.
zone(1): 94192 pages.
zone(2): 0 pages.
Intel MultiProcessor Specification v1.1
Virtual Wire compatibility mode.
OEM ID:
ide-scsi: CoD != 0 in idescsi_pc_intr... -- what is this?
Hi all,
While copying a CD into harddisk, I got the following in the syslog (and
on the console):
Mar 15 14:36:23 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:36:23 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:36:23 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:36:23 brefatox kernel: hde: status error: error=0x00
Mar 15 14:36:23 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:36:46 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:36:46 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:36:46 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:36:46 brefatox kernel: hde: status error: error=0x00
Mar 15 14:36:46 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:02 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:02 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:02 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:02 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:02 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:17 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:17 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:17 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:17 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:17 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:27 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:27 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:27 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:27 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:27 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:28 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:29 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:29 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:29 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:29 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:37:32 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:32 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:32 brefatox kernel: hde: status error: status=0x08 {
DataRequest }
Mar 15 14:37:32 brefatox kernel: hde: drive not ready for command
Mar 15 14:37:42 brefatox kernel: spurious 8259A interrupt: IRQ7.
Mar 15 14:37:49 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:37:49 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:37:49 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:37:49 brefatox kernel: hde: status error: error=0x00
Mar 15 14:37:49 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
Mar 15 14:38:23 brefatox kernel: ide-scsi: CoD != 0 in idescsi_pc_intr
Mar 15 14:38:23 brefatox kernel: hde: ATAPI reset complete
Mar 15 14:38:23 brefatox kernel: hde: status error: status=0x51 {
DriveReady SeekComplete Error }
Mar 15 14:38:23 brefatox kernel: hde: status error: error=0x00
Mar 15 14:38:23 brefatox kernel: ide-scsi: Strange, packet command
initiated yet DRQ isn't asserted
The copy finished successfully. What is this? Should I care about it? Why
is it? :) (so many questions...)
I was copying copying from hde to hdg. dmesg is at the end.
The cdrom is connected to via a 80c udma66 cable to the first port of the
HPT370 on my Abit VP6 motherboard.
dmesg:
Linux version 2.4.2 ([EMAIL PROTECTED]) (gcc version 2.95.3 19991030 (prerelease)) #1
SMP Wed Mar 7 22:58:36 CET 2001
BIOS-provided physical RAM map:
BIOS-e820: 0009fc00 @ (usable)
BIOS-e820: 0400 @ 0009fc00 (reserved)
BIOS-e820: 0001 @ 000f (reserved)
BIOS-e820: 1000 @ fec0 (reserved)
BIOS-e820: 1000 @ fee0 (reserved)
BIOS-e820: 0001 @ (reserved)
BIOS-e820: 17ef @ 0010 (usable)
BIOS-e820: d000 @ 17ff3000 (ACPI data)
BIOS-e820: 3000 @ 17ff (ACPI NVS)
Scan SMP from c000 for 1024 bytes.
Scan SMP from c009fc00 for 1024 bytes.
Scan SMP from c00f for 65536 bytes.
found SMP MP-table at 000f5770
hm, page 000f5000 reserved twice.
hm, page 000f6000 reserved twice.
hm, page 000f1000 reserved twice.
hm, page 000f2000 reserved twice.
On node 0 totalpages: 98288
zone(0): 4096 pages.
zone(1): 94192 pages.
zone(2): 0 pages.
Intel MultiProcessor Specification v1.1
Virtual Wire compatibility mode.
OEM ID:
IDE poweroff -> hangup
Hi all, I was courious, and I tried what happens if I power down my harddisk (ie manually pull the power plug out), and then power it on again after a few secs (put the plug back). I do not know if the system should survive happily such an 'accident', but it hadn't: A few secs after the next access to the disc, I got the following on the console: hdg: timeout waiting for DMA ide_dmaproc: chipset supported ide_dma_timeout func only: 14 and the machine froze the hard way (no respond to sysrq). Tell me if this shouldn't be honoured by the kernel, but if there's a bug around, here's some info: Linux version 2.4.2 ([EMAIL PROTECTED]) (gcc version 2.95.3 19991030 (prerelease)) #1 SMP Wed Mar 7 22:58:36 CET 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 0001 @ 000f (reserved) BIOS-e820: 1000 @ fec0 (reserved) BIOS-e820: 1000 @ fee0 (reserved) BIOS-e820: 0001 @ (reserved) BIOS-e820: 17ef @ 0010 (usable) BIOS-e820: d000 @ 17ff3000 (ACPI data) BIOS-e820: 3000 @ 17ff (ACPI NVS) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. found SMP MP-table at 000f5770 hm, page 000f5000 reserved twice. hm, page 000f6000 reserved twice. hm, page 000f1000 reserved twice. hm, page 000f2000 reserved twice. On node 0 totalpages: 98288 zone(0): 4096 pages. zone(1): 94192 pages. zone(2): 0 pages. Intel MultiProcessor Specification v1.1 Virtual Wire compatibility mode. OEM ID: OEM0 Product ID: PROD APIC at: 0xFEE0 Processor #0 Pentium(tm) Pro APIC version 17 Floating point unit present. Machine Exception supported. 64 bit compare & exchange supported. Internal APIC present. SEP present. MTRR present. PGE present. MCA present. CMOV present. Bootup CPU Bus #0 is PCI Bus #1 is PCI Bus #2 is ISA I/O APIC #2 Version 17 at 0xFEC0. Int: type 3, pol 0, trig 0, bus 2, IRQ 00, APIC ID 2, APIC INT 00 Int: type 0, pol 0, trig 0, bus 2, IRQ 01, APIC ID 2, APIC INT 01 Int: type 0, pol 0, trig 0, bus 2, IRQ 00, APIC ID 2, APIC INT 02 Int: type 0, pol 0, trig 0, bus 2, IRQ 03, APIC ID 2, APIC INT 03 Int: type 0, pol 0, trig 0, bus 2, IRQ 04, APIC ID 2, APIC INT 04 Int: type 0, pol 0, trig 0, bus 2, IRQ 06, APIC ID 2, APIC INT 06 Int: type 0, pol 0, trig 0, bus 2, IRQ 07, APIC ID 2, APIC INT 07 Int: type 0, pol 1, trig 1, bus 2, IRQ 08, APIC ID 2, APIC INT 08 Int: type 0, pol 0, trig 0, bus 2, IRQ 0c, APIC ID 2, APIC INT 0c Int: type 0, pol 0, trig 0, bus 2, IRQ 0d, APIC ID 2, APIC INT 0d Int: type 0, pol 0, trig 0, bus 2, IRQ 0e, APIC ID 2, APIC INT 0e Int: type 0, pol 0, trig 0, bus 2, IRQ 0f, APIC ID 2, APIC INT 0f Int: type 0, pol 3, trig 3, bus 2, IRQ 09, APIC ID 2, APIC INT 09 Int: type 0, pol 3, trig 3, bus 2, IRQ 05, APIC ID 2, APIC INT 05 Int: type 0, pol 3, trig 3, bus 2, IRQ 0b, APIC ID 2, APIC INT 0b Int: type 0, pol 3, trig 3, bus 2, IRQ 0a, APIC ID 2, APIC INT 0a Lint: type 3, pol 0, trig 0, bus 2, IRQ 00, APIC ID ff, APIC LINT 00 Lint: type 1, pol 0, trig 0, bus 2, IRQ 00, APIC ID ff, APIC LINT 01 Processors: 1 mapped APIC to e000 (fee0) mapped IOAPIC to d000 (fec0) Kernel command line: root=/dev/hdg4 apm=power-off noapic mem=393152K Initializing CPU#0 Detected 434.815 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 865.07 BogoMIPS Memory: 384580k/393152k available (856k kernel code, 8184k reserved, 294k data, 184k init, 0k highmem) Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes) Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) CPU: Before vendor init, caps: 0183fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 128K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0183fbff CPU: After generic, caps: 0183fbff CPU: Common caps: 0183fbff Enabling fast FPU save and restore... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel CPU: Before vendor init, caps: 0183fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 128K Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0183fbff CPU: After generic, caps: 0183fbff CPU: Common caps: 0183fbff CPU0: Intel Celeron (Mendocino) stepping 05
IDE poweroff - hangup
Hi all, I was courious, and I tried what happens if I power down my harddisk (ie manually pull the power plug out), and then power it on again after a few secs (put the plug back). I do not know if the system should survive happily such an 'accident', but it hadn't: A few secs after the next access to the disc, I got the following on the console: hdg: timeout waiting for DMA ide_dmaproc: chipset supported ide_dma_timeout func only: 14 and the machine froze the hard way (no respond to sysrq). Tell me if this shouldn't be honoured by the kernel, but if there's a bug around, here's some info: Linux version 2.4.2 ([EMAIL PROTECTED]) (gcc version 2.95.3 19991030 (prerelease)) #1 SMP Wed Mar 7 22:58:36 CET 2001 BIOS-provided physical RAM map: BIOS-e820: 0009fc00 @ (usable) BIOS-e820: 0400 @ 0009fc00 (reserved) BIOS-e820: 0001 @ 000f (reserved) BIOS-e820: 1000 @ fec0 (reserved) BIOS-e820: 1000 @ fee0 (reserved) BIOS-e820: 0001 @ (reserved) BIOS-e820: 17ef @ 0010 (usable) BIOS-e820: d000 @ 17ff3000 (ACPI data) BIOS-e820: 3000 @ 17ff (ACPI NVS) Scan SMP from c000 for 1024 bytes. Scan SMP from c009fc00 for 1024 bytes. Scan SMP from c00f for 65536 bytes. found SMP MP-table at 000f5770 hm, page 000f5000 reserved twice. hm, page 000f6000 reserved twice. hm, page 000f1000 reserved twice. hm, page 000f2000 reserved twice. On node 0 totalpages: 98288 zone(0): 4096 pages. zone(1): 94192 pages. zone(2): 0 pages. Intel MultiProcessor Specification v1.1 Virtual Wire compatibility mode. OEM ID: OEM0 Product ID: PROD APIC at: 0xFEE0 Processor #0 Pentium(tm) Pro APIC version 17 Floating point unit present. Machine Exception supported. 64 bit compare exchange supported. Internal APIC present. SEP present. MTRR present. PGE present. MCA present. CMOV present. Bootup CPU Bus #0 is PCI Bus #1 is PCI Bus #2 is ISA I/O APIC #2 Version 17 at 0xFEC0. Int: type 3, pol 0, trig 0, bus 2, IRQ 00, APIC ID 2, APIC INT 00 Int: type 0, pol 0, trig 0, bus 2, IRQ 01, APIC ID 2, APIC INT 01 Int: type 0, pol 0, trig 0, bus 2, IRQ 00, APIC ID 2, APIC INT 02 Int: type 0, pol 0, trig 0, bus 2, IRQ 03, APIC ID 2, APIC INT 03 Int: type 0, pol 0, trig 0, bus 2, IRQ 04, APIC ID 2, APIC INT 04 Int: type 0, pol 0, trig 0, bus 2, IRQ 06, APIC ID 2, APIC INT 06 Int: type 0, pol 0, trig 0, bus 2, IRQ 07, APIC ID 2, APIC INT 07 Int: type 0, pol 1, trig 1, bus 2, IRQ 08, APIC ID 2, APIC INT 08 Int: type 0, pol 0, trig 0, bus 2, IRQ 0c, APIC ID 2, APIC INT 0c Int: type 0, pol 0, trig 0, bus 2, IRQ 0d, APIC ID 2, APIC INT 0d Int: type 0, pol 0, trig 0, bus 2, IRQ 0e, APIC ID 2, APIC INT 0e Int: type 0, pol 0, trig 0, bus 2, IRQ 0f, APIC ID 2, APIC INT 0f Int: type 0, pol 3, trig 3, bus 2, IRQ 09, APIC ID 2, APIC INT 09 Int: type 0, pol 3, trig 3, bus 2, IRQ 05, APIC ID 2, APIC INT 05 Int: type 0, pol 3, trig 3, bus 2, IRQ 0b, APIC ID 2, APIC INT 0b Int: type 0, pol 3, trig 3, bus 2, IRQ 0a, APIC ID 2, APIC INT 0a Lint: type 3, pol 0, trig 0, bus 2, IRQ 00, APIC ID ff, APIC LINT 00 Lint: type 1, pol 0, trig 0, bus 2, IRQ 00, APIC ID ff, APIC LINT 01 Processors: 1 mapped APIC to e000 (fee0) mapped IOAPIC to d000 (fec0) Kernel command line: root=/dev/hdg4 apm=power-off noapic mem=393152K Initializing CPU#0 Detected 434.815 MHz processor. Console: colour VGA+ 80x25 Calibrating delay loop... 865.07 BogoMIPS Memory: 384580k/393152k available (856k kernel code, 8184k reserved, 294k data, 184k init, 0k highmem) Dentry-cache hash table entries: 65536 (order: 7, 524288 bytes) Buffer-cache hash table entries: 32768 (order: 5, 131072 bytes) Page-cache hash table entries: 131072 (order: 7, 524288 bytes) Inode-cache hash table entries: 32768 (order: 6, 262144 bytes) CPU: Before vendor init, caps: 0183fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 128K Intel machine check architecture supported. Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0183fbff CPU: After generic, caps: 0183fbff CPU: Common caps: 0183fbff Enabling fast FPU save and restore... done. Checking 'hlt' instruction... OK. POSIX conformance testing by UNIFIX mtrr: v1.37 (20001109) Richard Gooch ([EMAIL PROTECTED]) mtrr: detected mtrr type: Intel CPU: Before vendor init, caps: 0183fbff , vendor = 0 CPU: L1 I cache: 16K, L1 D cache: 16K CPU: L2 cache: 128K Intel machine check reporting enabled on CPU#0. CPU: After vendor init, caps: 0183fbff CPU: After generic, caps: 0183fbff CPU: Common caps: 0183fbff CPU0: Intel Celeron (Mendocino) stepping 05
Ide Hot-swaping?
Is it possible to hot-swap ide drives and re-detect them? Does 'normal' Pc-hardware allow it? thanks, Balazs Pozsar. - 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/
Ide Hot-swaping?
Is it possible to hot-swap ide drives and re-detect them? Does 'normal' Pc-hardware allow it? thanks, Balazs Pozsar. - 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: can't read DVD (under 2.4.[12] & 2.2.17)
Adding the cgc.buflen = 20; line into drivers/cdrom/cdrom.c: dvd_read_physical(...) solves my problem. I don't know the difference, but first you mentioned cgc.buflen = 16; so i tried that also, and it worked the same. I'll write again if i'm having problems. :) Thanks for the fast patch. I think you should also check 2.2. Balazs Pozsar. On Wed, 7 Mar 2001, Jens Axboe wrote: > On Wed, Mar 07 2001, Jens Axboe wrote: > > On Wed, Mar 07 2001, Jens Axboe wrote: > > > Really good question, I sent this patch in the private thread between > > > me and Pozsar just in case the length is what the drive complains about. > > > > Agrh, that's not all. I will fix this properly, sorry about the noise. > > This should work. Pozsar, could you test? > > I suspect that Derik is right though, that the 05/24/00 is because > the dvdinfo is requesting info for a non-existant physical layer. > I've attempted to quiet that error. You dvdinfo output did look > very odd. > > - 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: can't read DVD (under 2.4.[12] & 2.2.17)
Details: (dmesg)
Linux version 2.4.2-3mdk ([EMAIL PROTECTED]) (gcc version
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Feb 27 02:14:17
CET 2001
...
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:DMA
HPT370: IDE controller on PCI bus 00 dev 70
PCI: Found IRQ 11 for device 00:0e.0
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio
hdd: Pioneer DVD-ROM ATAPIModel DVD-105S 012, ATAPI CD/DVD-ROM drive
hdg: QUANTUM FIREBALLlct20 20, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide3 at 0xe400-0xe407,0xe802 on irq 11
hdg: 39876480 sectors (20417 MB) w/418KiB Cache, CHS=39560/16/63,
UDMA(100)
hdd: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Partition check:
hdg: hdg1 hdg2 hdg3 hdg4
...
When I run "dvdinfo /dev/hdd" I get:
Disc is encrypted.
Layer 0[3]
Book Version: 0
Book Type: 13
Min Rate: 0
Disc Size: 0
Layer Type: 0
Track Path: 1
Num Layers: 2
Track Density: 0
Linear Density: 0
BCA:1
Start Sector0xd000
End Sector 0xd000
End Sector L0 0xd000
Layer 1[3]
Book Version: 0
Book Type: 13
Min Rate: 0
Disc Size: 0
Layer Type: 0
Track Path: 1
Num Layers: 2
Track Density: 0
Linear Density: 0
BCA:1
Start Sector0xd000
End Sector 0x1d000
End Sector L0 0xd000
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x50
ATAPI device hdd:
Error: Illegal request -- (Sense key=0x05)
Invalid field in command packet -- (asc=0x24, ascq=0x00)
The failed "Send DVD Structure" packet command was:
"ad 00 00 00 00 00 02 00 00 54 00 00 "
Could not read Physical layer 2
Copyright: CPST=1, RMI=0xfd
I also get this in syslog:
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x50
ATAPI device hdd:
Error: Illegal request -- (Sense key=0x05)
Invalid field in command packet -- (asc=0x24, ascq=0x00)
The failed "Send DVD Structure" packet command was:
"ad 00 00 00 00 00 02 00 00 54 00 00 "
Tell me i can give you any more info.
Balazs Pozsar.
On Wed, 7 Mar 2001, Jens Axboe wrote:
> On Wed, Mar 07 2001, Pozsar Balazs wrote:
> >
> > hi all,
> >
> > Whatever I tried, I couldn't get my DVDs read. I get:
> > sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
> > or, I don't use ide-scsi, i get the ATAPI equivalent.
> > I have udf support compiled in, i have successfully authenticated the
> > disk(s), but lo luck.
> >
> > The drive is:
> >Vendor: PIONEER Model: DVD-ROM DVD-105 Rev: 1.22
> >
> > I tried 2.2.17, 2.4.1 & 2.4.2 (and a few different compiled versions of
> > them)
> >
> > What might be the problem?
>
> I don't know, you provide virtually no information. Use the ATAPI
> driver, and dump dmesg info when this happens. Then send that along.
>
>
-
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/
can't read DVD (under 2.4.[12] & 2.2.17)
hi all, Whatever I tried, I couldn't get my DVDs read. I get: sr0: CDROM (ioctl) reports ILLEGAL REQUEST. or, I don't use ide-scsi, i get the ATAPI equivalent. I have udf support compiled in, i have successfully authenticated the disk(s), but lo luck. The drive is: Vendor: PIONEER Model: DVD-ROM DVD-105 Rev: 1.22 I tried 2.2.17, 2.4.1 & 2.4.2 (and a few different compiled versions of them) What might be the problem? Balazs Pozsar. - 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: tts/0: 1 input overrun(s)
On Tue, 6 Mar 2001, James Stevenson wrote: > with the serial port it has a buffer when it recives data the > serial port buffer will fill up if data is not read quickly enough > the buffer will overflow hence the 1 input overrun > > to fix it your could try to reduce the data rate to the serial port > and what type of UART do you have in that port ? I don't think this should be normal. The relevant dmesg part: Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A I am using 115200. Balazs Pozsar. > >Hi all, > > > >I get the following message: > > tts/0: 1 input overrun(s) > > > >each time while downloading pictures from my digital camera via ttyS0, > >_and_ switching between an X session and textmode console. > >(ie, 1 switch -> 1 error) > > > >This is with 2.4.1. I don't remember getting these with 2.2 > >This error also means a transmit error (gphoto reports error and a packet > >has to be retransferred.) > > > >What is this? Why I'm getting it? What should I do? :) > > > >bye, > >Balazs Pozsar. > > > >- > >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/ > > > > > - 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: tts/0: 1 input overrun(s)
On Tue, 6 Mar 2001, James Stevenson wrote: with the serial port it has a buffer when it recives data the serial port buffer will fill up if data is not read quickly enough the buffer will overflow hence the 1 input overrun to fix it your could try to reduce the data rate to the serial port and what type of UART do you have in that port ? I don't think this should be normal. The relevant dmesg part: Serial driver version 5.02 (2000-08-09) with MANY_PORTS SHARE_IRQ SERIAL_PCI ISAPNP enabled ttyS00 at 0x03f8 (irq = 4) is a 16550A ttyS01 at 0x02f8 (irq = 3) is a 16550A I am using 115200. Balazs Pozsar. Hi all, I get the following message: tts/0: 1 input overrun(s) each time while downloading pictures from my digital camera via ttyS0, _and_ switching between an X session and textmode console. (ie, 1 switch - 1 error) This is with 2.4.1. I don't remember getting these with 2.2 This error also means a transmit error (gphoto reports error and a packet has to be retransferred.) What is this? Why I'm getting it? What should I do? :) bye, Balazs Pozsar. - 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/ - 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/
can't read DVD (under 2.4.[12] 2.2.17)
hi all, Whatever I tried, I couldn't get my DVDs read. I get: sr0: CDROM (ioctl) reports ILLEGAL REQUEST. or, I don't use ide-scsi, i get the ATAPI equivalent. I have udf support compiled in, i have successfully authenticated the disk(s), but lo luck. The drive is: Vendor: PIONEER Model: DVD-ROM DVD-105 Rev: 1.22 I tried 2.2.17, 2.4.1 2.4.2 (and a few different compiled versions of them) What might be the problem? Balazs Pozsar. - 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: can't read DVD (under 2.4.[12] 2.2.17)
Details: (dmesg)
Linux version 2.4.2-3mdk ([EMAIL PROTECTED]) (gcc version
egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #1 Tue Feb 27 02:14:17
CET 2001
...
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: IDE controller on PCI bus 00 dev 39
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with
idebus=xx
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci00:07.1
ide0: BM-DMA at 0xc000-0xc007, BIOS settings: hda:pio, hdb:pio
ide1: BM-DMA at 0xc008-0xc00f, BIOS settings: hdc:pio, hdd:DMA
HPT370: IDE controller on PCI bus 00 dev 70
PCI: Found IRQ 11 for device 00:0e.0
HPT370: chipset revision 3
HPT370: not 100% native mode: will probe irqs later
ide2: BM-DMA at 0xec00-0xec07, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0xec08-0xec0f, BIOS settings: hdg:DMA, hdh:pio
hdd: Pioneer DVD-ROM ATAPIModel DVD-105S 012, ATAPI CD/DVD-ROM drive
hdg: QUANTUM FIREBALLlct20 20, ATA DISK drive
ide1 at 0x170-0x177,0x376 on irq 15
ide3 at 0xe400-0xe407,0xe802 on irq 11
hdg: 39876480 sectors (20417 MB) w/418KiB Cache, CHS=39560/16/63,
UDMA(100)
hdd: ATAPI 40X DVD-ROM drive, 512kB Cache, UDMA(33)
Uniform CD-ROM driver Revision: 3.12
Partition check:
hdg: hdg1 hdg2 hdg3 hdg4
...
When I run "dvdinfo /dev/hdd" I get:
Disc is encrypted.
Layer 0[3]
Book Version: 0
Book Type: 13
Min Rate: 0
Disc Size: 0
Layer Type: 0
Track Path: 1
Num Layers: 2
Track Density: 0
Linear Density: 0
BCA:1
Start Sector0xd000
End Sector 0xd000
End Sector L0 0xd000
Layer 1[3]
Book Version: 0
Book Type: 13
Min Rate: 0
Disc Size: 0
Layer Type: 0
Track Path: 1
Num Layers: 2
Track Density: 0
Linear Density: 0
BCA:1
Start Sector0xd000
End Sector 0x1d000
End Sector L0 0xd000
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x50
ATAPI device hdd:
Error: Illegal request -- (Sense key=0x05)
Invalid field in command packet -- (asc=0x24, ascq=0x00)
The failed "Send DVD Structure" packet command was:
"ad 00 00 00 00 00 02 00 00 54 00 00 "
Could not read Physical layer 2
Copyright: CPST=1, RMI=0xfd
I also get this in syslog:
hdd: packet command error: status=0x51 { DriveReady SeekComplete Error }
hdd: packet command error: error=0x50
ATAPI device hdd:
Error: Illegal request -- (Sense key=0x05)
Invalid field in command packet -- (asc=0x24, ascq=0x00)
The failed "Send DVD Structure" packet command was:
"ad 00 00 00 00 00 02 00 00 54 00 00 "
Tell me i can give you any more info.
Balazs Pozsar.
On Wed, 7 Mar 2001, Jens Axboe wrote:
On Wed, Mar 07 2001, Pozsar Balazs wrote:
hi all,
Whatever I tried, I couldn't get my DVDs read. I get:
sr0: CDROM (ioctl) reports ILLEGAL REQUEST.
or, I don't use ide-scsi, i get the ATAPI equivalent.
I have udf support compiled in, i have successfully authenticated the
disk(s), but lo luck.
The drive is:
Vendor: PIONEER Model: DVD-ROM DVD-105 Rev: 1.22
I tried 2.2.17, 2.4.1 2.4.2 (and a few different compiled versions of
them)
What might be the problem?
I don't know, you provide virtually no information. Use the ATAPI
driver, and dump dmesg info when this happens. Then send that along.
-
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: can't read DVD (under 2.4.[12] 2.2.17)
Adding the cgc.buflen = 20; line into drivers/cdrom/cdrom.c: dvd_read_physical(...) solves my problem. I don't know the difference, but first you mentioned cgc.buflen = 16; so i tried that also, and it worked the same. I'll write again if i'm having problems. :) Thanks for the fast patch. I think you should also check 2.2. Balazs Pozsar. On Wed, 7 Mar 2001, Jens Axboe wrote: On Wed, Mar 07 2001, Jens Axboe wrote: On Wed, Mar 07 2001, Jens Axboe wrote: Really good question, I sent this patch in the private thread between me and Pozsar just in case the length is what the drive complains about. Agrh, that's not all. I will fix this properly, sorry about the noise. This should work. Pozsar, could you test? I suspect that Derik is right though, that the 05/24/00 is because the dvdinfo is requesting info for a non-existant physical layer. I've attempted to quiet that error. You dvdinfo output did look very odd. - 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/
tts/0: 1 input overrun(s)
Hi all, I get the following message: tts/0: 1 input overrun(s) each time while downloading pictures from my digital camera via ttyS0, _and_ switching between an X session and textmode console. (ie, 1 switch -> 1 error) This is with 2.4.1. I don't remember getting these with 2.2 This error also means a transmit error (gphoto reports error and a packet has to be retransferred.) What is this? Why I'm getting it? What should I do? :) bye, Balazs Pozsar. - 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/
tts/0: 1 input overrun(s)
Hi all, I get the following message: tts/0: 1 input overrun(s) each time while downloading pictures from my digital camera via ttyS0, _and_ switching between an X session and textmode console. (ie, 1 switch - 1 error) This is with 2.4.1. I don't remember getting these with 2.2 This error also means a transmit error (gphoto reports error and a packet has to be retransferred.) What is this? Why I'm getting it? What should I do? :) bye, Balazs Pozsar. - 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: binfmt_script and ^M
On Mon, 5 Mar 2001, Robert Read wrote: > On Mon, Mar 05, 2001 at 07:58:52PM +0100, Pozsar Balazs wrote: > > > > And what does POSIX say about "#!/bin/sh\r" ? > > In other words: should the kernel look for the interpreter between the ! > > and the newline, or [the first space or newline] or the first whitespace? > > > > IMHO, the first whitespace. Which means that "#!/bin/sh\r" should invoke > > /bin/sh. (though it is junk). > > The line terminator, '\n', is what terminates the interpreter. White > space (in this case, only ' ' and '\t') is used to seperate the ^ > arguments to the interpreter. The last little tiny thing that bothers me: why? Why only ' ' and '\t' _in this case_? As someone mentioned, even isspace() returns whitespace. A possible answer (that i can think of), is that those ar the whitespaces, which are in IFS (as said previously), taking out us from kernel-space into userspace. But imho we shouldn't define another set whitespace for this case, can't we just use what isspace() says? (okay, I'm not for this '\r' thingy, I just want to see the reasons.) -- Balazs Pozsar. - 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: binfmt_script and ^M
On Mon, 5 Mar 2001, Paul Flinders wrote:
> Jeff Mcadams wrote:
>
> > Also sprach Rik van Riel
> > >On Mon, 5 Mar 2001, John Kodis wrote:
> > >> On Mon, Mar 05, 2001 at 08:40:22AM -0500, Richard B. Johnson wrote:
> > >> > Somebody must have missed the boat entirely. Unix does not, never
> > >> > has, and never will end a text line with '\r'.
> >
> > >> Unix does not, never has, and never will end a text line with ' ' (a
> > >> space character) or with \t (a tab character). Yet if I begin a
> > >> shell script with '#!/bin/sh ' or '#!/bin/sh\t', the training white
> > >> space is striped and /bin/sh gets exec'd. Since \r has no special
> > >> significance to Unix, I'd expect it to be treated the same as any
> > >> other whitespace character -- it should be striped, and /bin/sh
> > >> should get exec'd.
> >
> > >Makes sense, IMHO...
> >
> > That only makes sense if:
> > #!/bin/shasdf\n
> > would also exec /bin/sh.
>
> POSIX disagrees with you (accd to the manual page)
>
> $ man isspace
>
>isspace()
> checks for white-space characters. In the "C" and
> "POSIX" locales, these are: space, form-feed
> ('\f'), newline ('\n'), carriage return ('\r'),
> horizontal tab ('\t'), and vertical tab ('\v').
And what does POSIX say about "#!/bin/sh\r" ?
In other words: should the kernel look for the interpreter between the !
and the newline, or [the first space or newline] or the first whitespace?
IMHO, the first whitespace. Which means that "#!/bin/sh\r" should invoke
/bin/sh. (though it is junk).
--
-
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: binfmt_script and ^M
On Mon, 5 Mar 2001, Paul Flinders wrote:
Jeff Mcadams wrote:
Also sprach Rik van Riel
On Mon, 5 Mar 2001, John Kodis wrote:
On Mon, Mar 05, 2001 at 08:40:22AM -0500, Richard B. Johnson wrote:
Somebody must have missed the boat entirely. Unix does not, never
has, and never will end a text line with '\r'.
Unix does not, never has, and never will end a text line with ' ' (a
space character) or with \t (a tab character). Yet if I begin a
shell script with '#!/bin/sh ' or '#!/bin/sh\t', the training white
space is striped and /bin/sh gets exec'd. Since \r has no special
significance to Unix, I'd expect it to be treated the same as any
other whitespace character -- it should be striped, and /bin/sh
should get exec'd.
Makes sense, IMHO...
That only makes sense if:
#!/bin/shasdf\n
would also exec /bin/sh.
POSIX disagrees with you (accd to the manual page)
$ man isspace
isspace()
checks for white-space characters. In the "C" and
"POSIX" locales, these are: space, form-feed
('\f'), newline ('\n'), carriage return ('\r'),
horizontal tab ('\t'), and vertical tab ('\v').
And what does POSIX say about "#!/bin/sh\r" ?
In other words: should the kernel look for the interpreter between the !
and the newline, or [the first space or newline] or the first whitespace?
IMHO, the first whitespace. Which means that "#!/bin/sh\r" should invoke
/bin/sh. (though it is junk).
--
-
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: binfmt_script and ^M
On Mon, 5 Mar 2001, Robert Read wrote: On Mon, Mar 05, 2001 at 07:58:52PM +0100, Pozsar Balazs wrote: And what does POSIX say about "#!/bin/sh\r" ? In other words: should the kernel look for the interpreter between the ! and the newline, or [the first space or newline] or the first whitespace? IMHO, the first whitespace. Which means that "#!/bin/sh\r" should invoke /bin/sh. (though it is junk). The line terminator, '\n', is what terminates the interpreter. White space (in this case, only ' ' and '\t') is used to seperate the ^ arguments to the interpreter. The last little tiny thing that bothers me: why? Why only ' ' and '\t' _in this case_? As someone mentioned, even isspace() returns whitespace. A possible answer (that i can think of), is that those ar the whitespaces, which are in IFS (as said previously), taking out us from kernel-space into userspace. But imho we shouldn't define another set whitespace for this case, can't we just use what isspace() says? (okay, I'm not for this '\r' thingy, I just want to see the reasons.) -- Balazs Pozsar. - 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: APIC error on CPU0 (UP APIC kernel)
I'm having similar messages, about 2-3 per day. So far I saw these variants: APIC error on CPU0: 00(04) APIC error on CPU0: 00(02) APIC error on CPU0: 02(02) APIC error on CPU0: 02(04) APIC error on CPU0: 04(02) This is a Abit VP6, with 1 Celeron 433(66). (machine passes memtest). What does this mean? Note that everything seems to go on fine, no hangups etc. Balazs Pozsar. On Thu, 1 Mar 2001, Chaskiel M Grundman wrote: > I have some single-processr Dell Poweredge 2450 servers that I'm trying > to move to 2.4. They have been running 2.2 SMP kernels for a while with > no problem (to take advantage of the supposed benefit of using the > ioapic). > > 2.4 SMP kernels seem to work fine, but using a 2.4.1 or 2.4.2 UP kernel > with CONFIG_X86_UP_IOAPIC does not. At some point before the real root > filesystem is mounted, the system begins spewing > > APIC error on CPU0: 08(08) > > at a high rate and eventually either locks up, or is killed by the > watchdog nmi (at which point control-alt-delete _works_) > > 2450's use a serverworks chipset. I don't know what other information > might be useful... > > Here's an excerpt of the SMP 2.4.2 dmesg output, in case it's of any use: > > ENABLING IO-APIC IRQs > ...changing IO-APIC physical APIC ID to 1 ... ok. > ...changing IO-APIC physical APIC ID to 2 ... ok. > Synchronizing Arb IDs. > init IO_APIC IRQs > IO-APIC (apicid-pin) 1-0, 1-2, 1-3, 1-5, 1-10, 1-11, 1-13, 2-3, 2-8, > 2-9, 2-10, > 2-11, 2-12, 2-13 not connected. > ..TIMER: vector=49 pin1=-1 pin2=0 > ...trying to set up timer (IRQ0) through the 8259. (found pin 0) ...works. > activating NMI Watchdog ... done. > number of MP IRQ sources: 27. > number of IO-APIC #1 registers: 16. > number of IO-APIC #2 registers: 16. > testing the IO APIC... > > IO APIC #1.. > register #00: 0100 > ...: physical APIC id: 01 > register #01: 000F0011 > ... : max redirection entries: 000F > ... : IO APIC version: 0011 > register #02: > ... : arbitration: 00 > IRQ redirection table: > NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > 00 001 01 000 0 01131 > 01 001 01 000 0 01139 > 02 000 00 100 0 00000 > 03 000 00 100 0 00000 > 04 001 01 000 0 01141 > 05 000 00 100 0 00000 > 06 001 01 000 0 01149 > 07 001 01 000 0 01151 > 08 001 01 000 0 01159 > 09 001 01 000 0 01161 > 0a 000 00 100 0 00000 > 0b 000 00 100 0 00000 > 0c 001 01 000 0 01169 > 0d 000 00 100 0 00000 > 0e 001 01 000 0 01171 > 0f 001 01 000 0 01179 > IO APIC #2.. > register #00: 0200 > ...: physical APIC id: 02 > register #01: 000F0011 > ... : max redirection entries: 000F > ... : IO APIC version: 0011 > register #02: 0200 > ... : arbitration: 02 > IRQ redirection table: > NR Log Phy Mask Trig IRR Pol Stat Dest Deli Vect: > 00 001 01 110 1 01181 > 01 001 01 110 1 01189 > 02 001 01 110 1 01191 > 03 000 00 100 0 00000 > 04 001 01 110 1 01199 > 05 001 01 110 1 011A1 > 06 001 01 110 1 011A9 > 07 001 01 110 1 011B1 > 08 000 00 100 0 00000 > 09 000 00 100 0 00000 > 0a 000 00 100 0 00000 > 0b 000 00 100 0 00000 > 0c 000 00 100 0 00000 > 0d 000 00 100 0 00000 > 0e 001 01 110 1 011B9 > 0f 001 01 110 1 011C1 > IRQ to pin mappings: > IRQ1 -> 1 > IRQ4 -> 4 > IRQ6 -> 6 > IRQ7 -> 7 > IRQ8 -> 8 > IRQ9 -> 9 > IRQ12 -> 12 > IRQ14 -> 14 > IRQ15 -> 15 > IRQ16 -> 0 > IRQ17 -> 1 > IRQ18 -> 2 > IRQ20 -> 4 > IRQ21 -> 5 > IRQ22 -> 6 > IRQ23 -> 7 > IRQ30 -> 14 > IRQ31 -> 15 > done. > calibrating APIC timer ... > . CPU clock speed is 731.0440 MHz. > . host bus clock speed is 132.9169 MHz. > cpu: 0, clocks: 1329169, slice: 664584 > CPU0 > Setting commenced=1, go go go > PCI: PCI BIOS revision 2.10 entry at 0xfc79e, last bus=3 > PCI: Using configuration type 1 > PCI: Probing PCI hardware > PCI: ServerWorks host bridge: last bus ff > Unknown bridge resource 0: assuming transparent > Unknown bridge resource 1: assuming transparent > Unknown bridge resource 2: assuming transparent > Unknown bridge resource 0: assuming transparent > Unknown bridge resource 1: assuming transparent
2.4.1 hangup: Unable to handle kernel paging request... (maybereiserfs problem?)
The most important thing first: afaik this is not a hw problem, the machine passed memtests. I was compiling a gcc on one terminal and extracting a kernel on an other. When i came back, thing message was waiting me: Unable to handle kernel paging request at virtual address 5c8d0018 printing eip: c0179990 *pde = Oops: CPU:0 EIP:0010:[] EFLAGS: 00010246 eax: d5c42e00 ebx: 5c8d ecx: edx: 5be3ef36 esi: 0001 edi: 000112db ebp: d5c42c00 esp: c5ebdbd4 ds: 0018 es: 0018 ss: 0018 Process rm (pid: 10670, stackpage=c5ebd000) Stack: d5c42e00 896d896d c015d7e7 d5c42e00 5c8d 0001 c5ebdf3c d5c42e00 896d896d c0066ba0 c8c4dec8 896d896d 004d 096d cf2fa310 cf228000 c0172dfb c5ebdf3c 896d896d c5ebdcb4 c5ebde94 0001 c5ebde54 0001 Call Trace: [] [] [] [] [] [] [] [] [] [] [] Code: 8b 43 18 a9 00 00 10 00 74 b6 85 f6 74 06 f6 43 18 04 75 ac It was still responding, but if tried any io on disk, it hang that process. (i could still switch to another terminal, but i couldn't do anything useful there, though i could see what i type). I pressed SYSRQ+S a few times, but i'm not sure if it could sync (I don't remember the 'OK'.) Then is pressed SYSRQ+U, then SYSRQ+B. When it rebooted it had to do fsck, so the umount was unsuccessful. When i wanted to mount my secondary partition (holding only data) which is reiserfs, i got this: # mount -t reiserfs /dev/hda4 /mnt/hda4 reiserfs: checking transaction log (device 03:04) ... journal-1226: REPLAY FAILURE, fsck required! buffer write failed Replay Failure, unable to mount reiserfs_read_super: unable to initialize journal space mount: wrong fs type, bad option, bad superblock on /dev/hda4, or too many mounted file systems As it said above, i ran reiserfsck: <-reiserfsck, 2000-> reiserfsprogs 3.x.0b Will read-only check consistency of the partition Will put log info to stderr Do you want to run this program?[N/Yes] (note need to type Yes):Yes Analyzing journal..last flushed trans 63, mount_id 11, will replay from 64 up to 66:Yes?Mount_id 11, transaction 64, desc block 1320, commit block 1400: ( 262144 16 8391 8407 8377 8378 8417 8390 8418 8409 8380 8404 8375 8414 8384 8402 8374 8405 8376 8406 8413 8412 8382 8411 8381 8383 8410 8408 8385 8415 8423 8396 8400 8370 17 8420 8401 8373 8372 8387 8379 8421 8394 8437 8365 8325 8371 8294 8213 8280 8278 8300 8295 8293 8288 8287 8315 8327 8347 8397 8398 8340 8363 8299 8426 8427 8428 8429 8430 8431 8433 8361 8422 8424 8388 8425 8362 8442 8443) Mount_id 11, transaction 65, desc block 1401, commit block 1431: ( 262144 16 8433 8391 17 8420 8300 8213 8434 8418 8423 8448 8402 8340 8415 8299 8449 8450 8451 8361 8452 8453 8362 8454 8455 8426 8435 8436 8302) Mount_id 11, transaction 66, desc block 1432, commit block 1471: ( 8436 262144 16 8391 8418 8423 8402 8340 8361 8302 8213 8299 8435 17 8438 8420 8428 8429 8433 8278 8452transaction 66, block 21 could not be replayed (554115335) transaction 66, block 22 could not be replayed (551493855) transaction 66, block 23 could not be replayed (551952614) transaction 66, block 24 could not be replayed (552083688) transaction 66, block 25 could not be replayed (549724356) transaction 66, block 26 could not be replayed (552149225) transaction 66, block 27 could not be replayed (554246409) transaction 66, block 28 could not be replayed (554311946) transaction 66, block 29 could not be replayed (554377483) transaction 66, block 30 could not be replayed (554443020) transaction 66, block 31 could not be replayed (554574094) transaction 66, block 32 could not be replayed (554639631) transaction 66, block 33 could not be replayed (554508557) transaction 66, block 34 could not be replayed (547889320) transaction 66, block 35 could not be replayed (548020394) transaction 66, block 36 could not be replayed (554705168) transaction 66, block 37 could not be replayed (554049798) ) Journal replaied Checking S+tree../ 1 (of 2)/ 1 (of 88) pass_through_tree: unable to read 538124307 block on device 0x3 Okay, lets try again: # reiserfsck /dev/hda4 <-reiserfsck, 2000-> reiserfsprogs 3.x.0b Will read-only check consistency of the partition Will put log info to stderr Do you want to run this program?[N/Yes] (note need to type Yes):Yes Analyzing journal..nothing to replay (no transactions older than last flushed one found) Checking S+tree../ 1 (of 2)/ 1 (of 88) pass_through_tree: unable to read 538124307 block on device 0x3 When i repeat, i get exactly the same. I can now mount the partition: # mount -o ro -t reiserfs /dev/hda4 /mnt/hda4 reiserfs: checking transaction log (device 03:04) ... Warning, log replay starting on readonly filesystem is_tree_node: node level 0 does not match to the expected one 1 vs-5150: search_by_key: invalid format found in block 538124307. Fsck? vs-13070: reiserfs_read_inode2: i/o failure occurred trying to find stat data of [1 2 0x0
2.4.1 hangup: Unable to handle kernel paging request... (maybereiserfs problem?)
The most important thing first: afaik this is not a hw problem, the machine passed memtests. I was compiling a gcc on one terminal and extracting a kernel on an other. When i came back, thing message was waiting me: Unable to handle kernel paging request at virtual address 5c8d0018 printing eip: c0179990 *pde = Oops: CPU:0 EIP:0010:[c0179990] EFLAGS: 00010246 eax: d5c42e00 ebx: 5c8d ecx: edx: 5be3ef36 esi: 0001 edi: 000112db ebp: d5c42c00 esp: c5ebdbd4 ds: 0018 es: 0018 ss: 0018 Process rm (pid: 10670, stackpage=c5ebd000) Stack: d5c42e00 896d896d c015d7e7 d5c42e00 5c8d 0001 c5ebdf3c d5c42e00 896d896d c0066ba0 c8c4dec8 896d896d 004d 096d cf2fa310 cf228000 c0172dfb c5ebdf3c 896d896d c5ebdcb4 c5ebde94 0001 c5ebde54 0001 Call Trace: [c015d7e7] [c0172dfb] [c0173944] [c017407c] [c0173573] [c016305d] [c014afae] [c01497e6] [c01428e0] [c01429b8] [c0109157] Code: 8b 43 18 a9 00 00 10 00 74 b6 85 f6 74 06 f6 43 18 04 75 ac It was still responding, but if tried any io on disk, it hang that process. (i could still switch to another terminal, but i couldn't do anything useful there, though i could see what i type). I pressed SYSRQ+S a few times, but i'm not sure if it could sync (I don't remember the 'OK'.) Then is pressed SYSRQ+U, then SYSRQ+B. When it rebooted it had to do fsck, so the umount was unsuccessful. When i wanted to mount my secondary partition (holding only data) which is reiserfs, i got this: # mount -t reiserfs /dev/hda4 /mnt/hda4 reiserfs: checking transaction log (device 03:04) ... journal-1226: REPLAY FAILURE, fsck required! buffer write failed Replay Failure, unable to mount reiserfs_read_super: unable to initialize journal space mount: wrong fs type, bad option, bad superblock on /dev/hda4, or too many mounted file systems As it said above, i ran reiserfsck: -reiserfsck, 2000- reiserfsprogs 3.x.0b Will read-only check consistency of the partition Will put log info to stderr Do you want to run this program?[N/Yes] (note need to type Yes):Yes Analyzing journal..last flushed trans 63, mount_id 11, will replay from 64 up to 66:Yes?Mount_id 11, transaction 64, desc block 1320, commit block 1400: ( 262144 16 8391 8407 8377 8378 8417 8390 8418 8409 8380 8404 8375 8414 8384 8402 8374 8405 8376 8406 8413 8412 8382 8411 8381 8383 8410 8408 8385 8415 8423 8396 8400 8370 17 8420 8401 8373 8372 8387 8379 8421 8394 8437 8365 8325 8371 8294 8213 8280 8278 8300 8295 8293 8288 8287 8315 8327 8347 8397 8398 8340 8363 8299 8426 8427 8428 8429 8430 8431 8433 8361 8422 8424 8388 8425 8362 8442 8443) Mount_id 11, transaction 65, desc block 1401, commit block 1431: ( 262144 16 8433 8391 17 8420 8300 8213 8434 8418 8423 8448 8402 8340 8415 8299 8449 8450 8451 8361 8452 8453 8362 8454 8455 8426 8435 8436 8302) Mount_id 11, transaction 66, desc block 1432, commit block 1471: ( 8436 262144 16 8391 8418 8423 8402 8340 8361 8302 8213 8299 8435 17 8438 8420 8428 8429 8433 8278 8452transaction 66, block 21 could not be replayed (554115335) transaction 66, block 22 could not be replayed (551493855) transaction 66, block 23 could not be replayed (551952614) transaction 66, block 24 could not be replayed (552083688) transaction 66, block 25 could not be replayed (549724356) transaction 66, block 26 could not be replayed (552149225) transaction 66, block 27 could not be replayed (554246409) transaction 66, block 28 could not be replayed (554311946) transaction 66, block 29 could not be replayed (554377483) transaction 66, block 30 could not be replayed (554443020) transaction 66, block 31 could not be replayed (554574094) transaction 66, block 32 could not be replayed (554639631) transaction 66, block 33 could not be replayed (554508557) transaction 66, block 34 could not be replayed (547889320) transaction 66, block 35 could not be replayed (548020394) transaction 66, block 36 could not be replayed (554705168) transaction 66, block 37 could not be replayed (554049798) ) Journal replaied Checking S+tree../ 1 (of 2)/ 1 (of 88) pass_through_tree: unable to read 538124307 block on device 0x3 Okay, lets try again: # reiserfsck /dev/hda4 -reiserfsck, 2000- reiserfsprogs 3.x.0b Will read-only check consistency of the partition Will put log info to stderr Do you want to run this program?[N/Yes] (note need to type Yes):Yes Analyzing journal..nothing to replay (no transactions older than last flushed one found) Checking S+tree../ 1 (of 2)/ 1 (of 88) pass_through_tree: unable to read 538124307 block on device 0x3 When i repeat, i get exactly the same. I can now mount the partition: # mount -o ro -t reiserfs /dev/hda4 /mnt/hda4 reiserfs: checking transaction log (device 03:04) ... Warning, log replay starting on readonly filesystem is_tree_node: node level 0 does not match to the expected one 1 vs-5150: search_by_key: invalid format found in block 538124307. Fsck?
sudden console lockups (keyb+mouse)
This was about the fifth time when i experienced the following: all of a sudden, my keyboard and mouse (both together, at exactly the same time), stop responding, ie i can't type or move the mouse around. As the keyboard stop responding, i also can't use the Magic-key. All other things go on, process continue to run, i can see everything, but the only thing i can do is to press the reset button. (It seems that if had an other machine i could log in via network and shut it down.) Last time i had this problem about 10 seconds after starting X, but i also met this whitout X (while running for example mc). It might hw related, but i have no idea how could i go for sure (please don't tell me to try it under win :)) I'm running 2.4.1, the mainboard is an Abit VP6, with PS/2 keyboard and mouse. Balazs Pozsar. - 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/
sudden console lockups (keyb+mouse)
This was about the fifth time when i experienced the following: all of a sudden, my keyboard and mouse (both together, at exactly the same time), stop responding, ie i can't type or move the mouse around. As the keyboard stop responding, i also can't use the Magic-key. All other things go on, process continue to run, i can see everything, but the only thing i can do is to press the reset button. (It seems that if had an other machine i could log in via network and shut it down.) Last time i had this problem about 10 seconds after starting X, but i also met this whitout X (while running for example mc). It might hw related, but i have no idea how could i go for sure (please don't tell me to try it under win :)) I'm running 2.4.1, the mainboard is an Abit VP6, with PS/2 keyboard and mouse. Balazs Pozsar. - 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/
[IDE] meaningless #ifndef?
from drivers/ide/ide-features.c:
/*
* All hosts that use the 80c ribbon mus use!
*/
byte eighty_ninty_three (ide_drive_t *drive)
{
return ((byte) ((HWIF(drive)->udma_four) &&
#ifndef CONFIG_IDEDMA_IVB
(drive->id->hw_config & 0x4000) &&
#endif /* CONFIG_IDEDMA_IVB */
(drive->id->hw_config & 0x6000)) ? 1 : 0);
}
If i see well, then this is always same whether CONFIG_IDEDMA_IVB is
defined or not.
What's the clue?
--
pozsy.
-
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: Maybe a bug (unexpected IO-APIC)
> > Feb 19 19:37:17 delphin kernel: testing the IO APIC... > Feb 19 19:37:17 delphin kernel: > Feb 19 19:37:17 delphin kernel: WARNING: unexpected IO-APIC, please mail > Feb 19 19:37:17 delphin kernel: to [EMAIL PROTECTED] > Feb 19 19:37:17 delphin kernel: done. This is the same for me on a Abit VP6 running 1 Intel Celeron 433 (mendocino). Should i care about it? pozsy. - 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: Maybe a bug (unexpected IO-APIC)
Feb 19 19:37:17 delphin kernel: testing the IO APIC... Feb 19 19:37:17 delphin kernel: Feb 19 19:37:17 delphin kernel: WARNING: unexpected IO-APIC, please mail Feb 19 19:37:17 delphin kernel: to [EMAIL PROTECTED] Feb 19 19:37:17 delphin kernel: done. This is the same for me on a Abit VP6 running 1 Intel Celeron 433 (mendocino). Should i care about it? pozsy. - 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/
[IDE] meaningless #ifndef?
from drivers/ide/ide-features.c:
/*
* All hosts that use the 80c ribbon mus use!
*/
byte eighty_ninty_three (ide_drive_t *drive)
{
return ((byte) ((HWIF(drive)-udma_four)
#ifndef CONFIG_IDEDMA_IVB
(drive-id-hw_config 0x4000)
#endif /* CONFIG_IDEDMA_IVB */
(drive-id-hw_config 0x6000)) ? 1 : 0);
}
If i see well, then this is always same whether CONFIG_IDEDMA_IVB is
defined or not.
What's the clue?
--
pozsy.
-
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/
