Re: [PATCH v2 0/4] have the vt console preserve unicode characters
[quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200] >It's meant for displaying braille to _sighted_ people. And in real world, >the main [ab]use is a way to show images that won't get corrupted by >proportional fonts. :-þ It's not abuse at all. I often use U+28xx to show sighted people what the braille for something looks like. I often need to do this when, for example, I need them to comapre what I'm showing them to what's on an actual braille display. U+28xx is the only way for me to do this without a lengthy description containing sequences of dot number combinations. Also, U+28xx is the only reasonable way to share braille music between people who use different languages. >The primary users would be: >* people who want symbols uncorrupted (especially if their language uses a > non-latin script) >* CJK people (as discussed below) Again, that's not true. Why aren't braille users included in this list? After all, it's we who motivated this enhancement. I guess actual blind people mustn't count just because there are relatively fewer of us. :-( -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 |
Re: [PATCH v2 0/4] have the vt console preserve unicode characters
[quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200] >It's meant for displaying braille to _sighted_ people. And in real world, >the main [ab]use is a way to show images that won't get corrupted by >proportional fonts. :-þ It's not abuse at all. I often use U+28xx to show sighted people what the braille for something looks like. I often need to do this when, for example, I need them to comapre what I'm showing them to what's on an actual braille display. U+28xx is the only way for me to do this without a lengthy description containing sequences of dot number combinations. Also, U+28xx is the only reasonable way to share braille music between people who use different languages. >The primary users would be: >* people who want symbols uncorrupted (especially if their language uses a > non-latin script) >* CJK people (as discussed below) Again, that's not true. Why aren't braille users included in this list? After all, it's we who motivated this enhancement. I guess actual blind people mustn't count just because there are relatively fewer of us. :-( -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 |
Re: [PATCH v2 0/4] have the vt console preserve unicode characters
[quoted lines by Adam Borowski on 2018/06/19 at 17:14 +0200] >> Not at all. We braille users, especially when working with languages other >> than >> English, need more than 256 non-braille characters. Even for those who can >> live >> with just 256 non-braille characters, it's still a major pain having to come >> up >> with a usable braille-capable font for every needed 256 non-braille >> characters >> set. I can assure you, as an actual braille user, that the limitation has >> been >> a very long-standing problem and it's a great relief that it's finally been >> resolved. > >Ok, I thought Braille is limited to 2x3 dots, recently extended to 2x4; >thanks for the explanation! Yes, that's correct, but we do things like use a single braille cell to mean more than one thing and figure out which it is by context. That', for example, is how we handle box drawing characters. Also, for another example, we can tell based on which language we're currently reading. >But those of us who are sighted, are greatly annoyed by characters that are >usually taken for granted being randomly missing. For example, no console >font+mapping shipped with Debian supports ░▒▓▄▀ (despite them being a >commonly used part of the BIOS charset), so unless you go out of your way to >beat them back they'll be corrupted (usually into ♦). Then Perl6 wants ｢｣⚛, >and so on. All these problems would instantly disappear the moment console >sheds the limit of 256/512 glyphs. Yes, it's really the very same problem. It's just a little more annoying, I think, in braille since, if we want the 256 braille cell characters, we need to give up 256 useful non-braille characters. >So I'm pretty happy seeing this patch set. So am I! :-) -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 |
Re: [PATCH v2 0/4] have the vt console preserve unicode characters
[quoted lines by Adam Borowski on 2018/06/19 at 17:14 +0200] >> Not at all. We braille users, especially when working with languages other >> than >> English, need more than 256 non-braille characters. Even for those who can >> live >> with just 256 non-braille characters, it's still a major pain having to come >> up >> with a usable braille-capable font for every needed 256 non-braille >> characters >> set. I can assure you, as an actual braille user, that the limitation has >> been >> a very long-standing problem and it's a great relief that it's finally been >> resolved. > >Ok, I thought Braille is limited to 2x3 dots, recently extended to 2x4; >thanks for the explanation! Yes, that's correct, but we do things like use a single braille cell to mean more than one thing and figure out which it is by context. That', for example, is how we handle box drawing characters. Also, for another example, we can tell based on which language we're currently reading. >But those of us who are sighted, are greatly annoyed by characters that are >usually taken for granted being randomly missing. For example, no console >font+mapping shipped with Debian supports ░▒▓▄▀ (despite them being a >commonly used part of the BIOS charset), so unless you go out of your way to >beat them back they'll be corrupted (usually into ♦). Then Perl6 wants ｢｣⚛, >and so on. All these problems would instantly disappear the moment console >sheds the limit of 256/512 glyphs. Yes, it's really the very same problem. It's just a little more annoying, I think, in braille since, if we want the 256 braille cell characters, we need to give up 256 useful non-braille characters. >So I'm pretty happy seeing this patch set. So am I! :-) -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 |
Re: [PATCH v2 0/4] have the vt console preserve unicode characters
[quoted lines by Adam Borowski on 2018/06/19 at 15:09 +0200] >You're thinking small. That 256 possible values for Braille are easily >encodable within the 512-glyph space (256 char + stolen fg brightness bit, >another CGA peculiarity). Not at all. We braille users, especially when working with languages other than English, need more than 256 non-braille characters. Even for those who can live with just 256 non-braille characters, it's still a major pain having to come up with a usable braille-capable font for every needed 256 non-braille characters set. I can assure you, as an actual braille user, that the limitation has been a very long-standing problem and it's a great relief that it's finally been resolved. -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 |
Re: [PATCH v2 0/4] have the vt console preserve unicode characters
[quoted lines by Adam Borowski on 2018/06/19 at 15:09 +0200] >You're thinking small. That 256 possible values for Braille are easily >encodable within the 512-glyph space (256 char + stolen fg brightness bit, >another CGA peculiarity). Not at all. We braille users, especially when working with languages other than English, need more than 256 non-braille characters. Even for those who can live with just 256 non-braille characters, it's still a major pain having to come up with a usable braille-capable font for every needed 256 non-braille characters set. I can assure you, as an actual braille user, that the limitation has been a very long-standing problem and it's a great relief that it's finally been resolved. -- I believe the Bible to be the very Word of God: http://Mielke.cc/bible/ Dave Mielke| 2213 Fox Crescent | WebHome: http://Mielke.cc/ EMail: d...@mielke.cc | Ottawa, Ontario | Twitter: @Dave_Mielke Phone: +1 613 726 0014 | Canada K2A 1H7 |
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
Thank you for your very helpful answer. I really do appreciate it. It's possible that this device is using high speed because it offers a feature to transfer its internal clipboard to the host, and it allows that clipboard to contain lots of data. Interestingly, though, hidden within a usage note, they do observe that, so far, they've been unable to achieve a transfer speed faster than 5,000 characters in seven minutes. It looks to me like this is exactly due to their incorrect setting of bInterval. :-) I've sent them a note about it. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
Thank you for your very helpful answer. I really do appreciate it. It's possible that this device is using high speed because it offers a feature to transfer its internal clipboard to the host, and it allows that clipboard to contain lots of data. Interestingly, though, hidden within a usage note, they do observe that, so far, they've been unable to achieve a transfer speed faster than 5,000 characters in seven minutes. It looks to me like this is exactly due to their incorrect setting of bInterval. :-) I've sent them a note about it. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
[quoted lines by Alan Stern on 2017/03/12 at 21:40 -0400] >No, I was wondering why an HID device would run at high speed. Both >you and Samuel implied that this was because it was a USB-2 device. >But that is not an adequate answer, because it is perfectly valid for a >USB-2 device to run at full speed. I think I've misunderstood something about how to interpret bInterval. I'm now suspecting that bInterval must be interpreted the new (mocro frame) way only if the device is operating at least at high speed, and that, even if the device advertizes itself as USB 2.0, bInterval must still be interpreted the old way if the device is operating at full or low speed. Is that correct? If the above is correct, how can we tell from usbfs which way to interpret bInterval? -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
[quoted lines by Alan Stern on 2017/03/12 at 21:40 -0400] >No, I was wondering why an HID device would run at high speed. Both >you and Samuel implied that this was because it was a USB-2 device. >But that is not an adequate answer, because it is perfectly valid for a >USB-2 device to run at full speed. I think I've misunderstood something about how to interpret bInterval. I'm now suspecting that bInterval must be interpreted the new (mocro frame) way only if the device is operating at least at high speed, and that, even if the device advertizes itself as USB 2.0, bInterval must still be interpreted the old way if the device is operating at full or low speed. Is that correct? If the above is correct, how can we tell from usbfs which way to interpret bInterval? -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
[quoted lines by Alan Stern on 2017/03/12 at 21:31 -0400] >A device's speed is only partially related to its USB version. A >USB-1.1 device can run at low speed or full speed. A USB-2 device can >run at low, full, or high speed. And a USB-3 device can run at low, >full, high, or Super speed. Yes, I did know this, so maybe I misunderstood what you were wondering about. Were you wondering why 64ms was too long? -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
[quoted lines by Alan Stern on 2017/03/12 at 21:31 -0400] >A device's speed is only partially related to its USB version. A >USB-1.1 device can run at low speed or full speed. A USB-2 device can >run at low, full, or high speed. And a USB-3 device can run at low, >full, high, or Super speed. Yes, I did know this, so maybe I misunderstood what you were wondering about. Were you wondering why 64ms was too long? -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
[quoted lines by Alan Stern on 2017/03/12 at 21:40 -0400] >No, I was wondering why an HID device would run at high speed. Both >you and Samuel implied that this was because it was a USB-2 device. >But that is not an adequate answer, because it is perfectly valid for a >USB-2 device to run at full speed. What should we look at to find out what speed it wants to operate at? We didn't look into it becuaase the real problem, from our perspective, was that the 64ms interval was being honoured by the host when it should be the 10ms as is literally in the endpoint descriptor. Our assumption was that since it says it's USB 2.0 then bInterval must be intterpreted in light of that regardless of the actual speed used for communication. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
[quoted lines by Alan Stern on 2017/03/12 at 21:40 -0400] >No, I was wondering why an HID device would run at high speed. Both >you and Samuel implied that this was because it was a USB-2 device. >But that is not an adequate answer, because it is perfectly valid for a >USB-2 device to run at full speed. What should we look at to find out what speed it wants to operate at? We didn't look into it becuaase the real problem, from our perspective, was that the 64ms interval was being honoured by the host when it should be the 10ms as is literally in the endpoint descriptor. Our assumption was that since it says it's USB 2.0 then bInterval must be intterpreted in light of that regardless of the actual speed used for communication. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
[quoted lines by Alan Stern on 2017/03/12 at 17:18 -0400] >Interesting. This is a high-speed device that mistakenly uses the >low/full-speed encoding for an interrupt bInterval value? Yes. >That's pretty unusual. Most HID devices (which includes the Braille >devices I have heard of) run at low speed, and a few of them run at >full speed. I can't remember any running at high speed. According to my collection of data, 5 say 1.00, 15 say 1.1, and 21 say 2.0. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
[quoted lines by Alan Stern on 2017/03/12 at 17:18 -0400] >Interesting. This is a high-speed device that mistakenly uses the >low/full-speed encoding for an interrupt bInterval value? Yes. >That's pretty unusual. Most HID devices (which includes the Braille >devices I have heard of) run at low speed, and a few of them run at >full speed. I can't remember any running at high speed. According to my collection of data, 5 say 1.00, 15 say 1.1, and 21 say 2.0. -- Dave Mielke | 2213 Fox Crescent | The Bible is the very Word of God. Phone: 1-613-726-0014 | Ottawa, Ontario | http://Mielke.cc/bible/ EMail: d...@mielke.cc | Canada K2A 1H7 | http://FamilyRadio.org/
Re: nfs mount by label not working.
[quoted lines by Philipp Matthias Hahn on May 24, 2001, at 09:31] >Do you realy mean what you wrote in the Subject line: > >Subject : Re: *nfs* mount by label not working. No, I mean ext2. It would appear that my mount command was a little old. A newer version of mount works. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. - 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: nfs mount by label not working.
[quoted lines by Philipp Matthias Hahn on May 24, 2001, at 09:31] Do you realy mean what you wrote in the Subject line: Subject : Re: *nfs* mount by label not working. No, I mean ext2. It would appear that my mount command was a little old. A newer version of mount works. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. - 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: nfs mount by label not working.
[quoted lines by Guest section DW on May 23, 2001, at 23:12] >(i) Your version is ancient, but it might be good enough. mount -V mount: mount-2.9u >(ii) Labels as used in "mount -L label" are ext2 labels only >(well, xfs also works if I recall correctly) I set the labels with e2label. >(iii) I forgot to implement a crystal ball, so mount is not >very good in divining [yes, that is related to the old >indoeuropean words for god] where the devices are with a >given label. However, it will try everything mentioned in /proc/partitions. >In your case that is a very short list. I presume that you're assuming that my /proc/partitions is empty because its size shows as 0: ls -l /proc/partitions -r--r--r-- 1 root root0 May 23 17:31 /proc/partitions It does, however, have several lines in it. cat /proc/partitions major minor #blocks name rio rmerge rsect ruse wio wmerge wsect wuse running use aveq 3 06297480 hda 119 141 520 1790 0 0 0 0 0 1180 1790 3 11534176 hda1 0 0 0 0 0 0 0 0 0 0 0 3 2 1 hda2 1 0 2 20 0 0 0 0 0 20 20 3 3 96358 hda3 0 0 0 0 0 0 0 0 0 0 0 3 41534207 hda4 0 0 0 0 0 0 0 0 0 0 0 3 51052226 hda5 0 0 0 0 0 0 0 0 0 0 0 3 61052226 hda6 1 0 2 10 0 0 0 0 0 10 10 3 7 208813 hda7 1 0 2 20 0 0 0 0 0 20 20 3 8 819283 hda8 115 141 512 1730 0 0 0 0 0 1120 1730 22646297480 hdd 29218 300606 783536 808790 42553 89013 382004 2952210 0 599630 3763620 2265 522081 hdd1 0 0 0 0 0 0 0 0 0 0 0 2266 1 hdd2 1 0 2 10 0 0 0 0 0 10 10 2269 80293 hdd5 0 0 0 0 0 0 0 0 0 0 0 2270 401593 hdd6 161 30 382 2570 55 6 122 10590 0 7470 13160 22711004031 hdd7 3000 54712 115428 76420 213 34 520 25520 0 60270 101940 2272 200781 hdd8 1 0 2 20 0 0 0 0 0 20 20 2273 120456 hdd9 1 0 2 10 0 0 0 0 0 10 10 2274 883543 hdd104320 35159 78992 101950 8704 20252 59014 838820 0 149590 943220 2275 128488 hdd112943 17697 165114 91090 2662 16775 155496 212510 0 143130 303600 2276 208813 hdd121 0 2 10 0 0 0 0 0 10 10 22771542208 hdd1317758 192335 420202 515170 16930 5075 44786 1281640 0 363310 1796970 2278 514048 hdd141031 673 3408 21500 13989 46871 122066 583130 0 166600 604640 Might my problem be that the kernel is showing its size as 0 even though it actually does contain data? -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. - 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/
nfs mount by label not working.
Using kernel 2.2.17-14 as supplied by RedHat, and using mount from mount-2.9u-4, mounting by label using the -L option does not work. mount -L backup1 /a mount: no such partition found The mount man page says that "/proc/partitions" must exist. ls -l /proc/partitions -r--r--r-- 1 root root0 May 23 15:10 /proc/partitions Does something need to be enabled to make this work? What else might I be doing wrong? -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. - 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/
nfs mount by label not working.
Using kernel 2.2.17-14 as supplied by RedHat, and using mount from mount-2.9u-4, mounting by label using the -L option does not work. mount -L backup1 /a mount: no such partition found The mount man page says that /proc/partitions must exist. ls -l /proc/partitions -r--r--r-- 1 root root0 May 23 15:10 /proc/partitions Does something need to be enabled to make this work? What else might I be doing wrong? -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. - 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: nfs mount by label not working.
[quoted lines by Guest section DW on May 23, 2001, at 23:12] (i) Your version is ancient, but it might be good enough. mount -V mount: mount-2.9u (ii) Labels as used in mount -L label are ext2 labels only (well, xfs also works if I recall correctly) I set the labels with e2label. (iii) I forgot to implement a crystal ball, so mount is not very good in divining [yes, that is related to the old indoeuropean words for god] where the devices are with a given label. However, it will try everything mentioned in /proc/partitions. In your case that is a very short list. I presume that you're assuming that my /proc/partitions is empty because its size shows as 0: ls -l /proc/partitions -r--r--r-- 1 root root0 May 23 17:31 /proc/partitions It does, however, have several lines in it. cat /proc/partitions major minor #blocks name rio rmerge rsect ruse wio wmerge wsect wuse running use aveq 3 06297480 hda 119 141 520 1790 0 0 0 0 0 1180 1790 3 11534176 hda1 0 0 0 0 0 0 0 0 0 0 0 3 2 1 hda2 1 0 2 20 0 0 0 0 0 20 20 3 3 96358 hda3 0 0 0 0 0 0 0 0 0 0 0 3 41534207 hda4 0 0 0 0 0 0 0 0 0 0 0 3 51052226 hda5 0 0 0 0 0 0 0 0 0 0 0 3 61052226 hda6 1 0 2 10 0 0 0 0 0 10 10 3 7 208813 hda7 1 0 2 20 0 0 0 0 0 20 20 3 8 819283 hda8 115 141 512 1730 0 0 0 0 0 1120 1730 22646297480 hdd 29218 300606 783536 808790 42553 89013 382004 2952210 0 599630 3763620 2265 522081 hdd1 0 0 0 0 0 0 0 0 0 0 0 2266 1 hdd2 1 0 2 10 0 0 0 0 0 10 10 2269 80293 hdd5 0 0 0 0 0 0 0 0 0 0 0 2270 401593 hdd6 161 30 382 2570 55 6 122 10590 0 7470 13160 22711004031 hdd7 3000 54712 115428 76420 213 34 520 25520 0 60270 101940 2272 200781 hdd8 1 0 2 20 0 0 0 0 0 20 20 2273 120456 hdd9 1 0 2 10 0 0 0 0 0 10 10 2274 883543 hdd104320 35159 78992 101950 8704 20252 59014 838820 0 149590 943220 2275 128488 hdd112943 17697 165114 91090 2662 16775 155496 212510 0 143130 303600 2276 208813 hdd121 0 2 10 0 0 0 0 0 10 10 22771542208 hdd1317758 192335 420202 515170 16930 5075 44786 1281640 0 363310 1796970 2278 514048 hdd141031 673 3408 21500 13989 46871 122066 583130 0 166600 604640 Might my problem be that the kernel is showing its size as 0 even though it actually does contain data? -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. - 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/
Swap space deallocation speed.
Ever since I've upgraded to the 2.2.17-14 i386 kernel as provided by RedHat, I've had several hard crashes. One allowed "/var/log/messages" to be synced, so I was able to capture those details (which are attached to this message as the file "crash.log"). Once, instead of crashing, the system stayed up but all of the respawn processes in "/etc/inittab" began to respawn to rapidly, I couldn't create a shell process to poke around, and the keyboard eventually became unresponsive. The relevant line in the log, as you can find in the attached "crash.log" file, appears to be: Unable to handle kernel paging request at virtual address 00020024 My guess is that, for whatever reason, I may now be running out of swap space fairly often. If this is true, then either my children have altered their usage habits around the same time that I upgraded the kernel, or something about swap space management has changed between the 2.2.16-3 and 2.2.17-14 kernels. To this end, I've asked my children to be careful about not opening too many windows at the same time, and the system now stays up longer but still, on occasion, without requesting my permission, still goes down hard. I've also been watching the amount of available swap space with the "free" command. It predictably goes down quite quickly when a hog like netscape is started, but, when that same application exits, the available swap space goes back up very slowly. This would seem to make it very easy to inadvertently run out of swap space, i.e. quitting and restarting an application still, without the user realizing it, appears to be a bad thing to do because of the as yet unreclaimed swap space which is still being counted. Do any of you have any ideas? If I'm right about the slow reclamation of the swap space, is there anything I can do, e.g. alter something in "/proc", to speed up swap space reclamation? Thanks. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. Apr 16 11:23:06 dave kernel: Unable to handle kernel paging request at virtual address 00020024 Apr 16 11:23:06 dave kernel: current->tss.cr3 = 00101000, %%cr3 = 00101000 Apr 16 11:23:06 dave kernel: *pde = Apr 16 11:23:06 dave kernel: Oops: Apr 16 11:23:06 dave kernel: CPU:0 Apr 16 11:23:06 dave kernel: EIP:0010:[locks_remove_posix+43/140] Apr 16 11:23:06 dave kernel: EFLAGS: 00010206 Apr 16 11:23:06 dave kernel: eax: c3e6a6d0 ebx: c03e5c70 ecx: c3e6a660 edx: c03e5c70 Apr 16 11:23:06 dave kernel: esi: 0002 edi: c14ff5d0 ebp: c3e6a6d0 esp: c142ff30 Apr 16 11:23:06 dave kernel: ds: 0018 es: 0018 ss: 0018 Apr 16 11:23:06 dave kernel: Process ppp-watch (pid: 7528, process nr: 81, stackpage=c142f000) Apr 16 11:23:06 dave kernel: Stack: c14ff5d0 0001 c3e6a6d0 c3e6a660 0001 c011c9a1 0019 0032 Apr 16 11:23:06 dave kernel:c011ca40 bfffc000 c15147c0 0286 c15147c0 1d00 001d Apr 16 11:23:06 dave kernel:bd68 c151483c 1d00 c012768a c03e5c70 c203a280 00100047 0001 Apr 16 11:23:06 dave kernel: Call Trace: [check_pgt_cache+17/24] [clear_page_tables+152/160] [filp_close+70/88] [do_exit+293/624] [sys_exit+14/16] [system_call+52/56] Apr 16 11:23:06 dave kernel: Code: f6 46 24 01 74 49 8b 4c 24 5c 39 4e 14 75 40 8b 4c 24 58 8b
Swap space deallocation speed.
Ever since I've upgraded to the 2.2.17-14 i386 kernel as provided by RedHat, I've had several hard crashes. One allowed /var/log/messages to be synced, so I was able to capture those details (which are attached to this message as the file crash.log). Once, instead of crashing, the system stayed up but all of the respawn processes in /etc/inittab began to respawn to rapidly, I couldn't create a shell process to poke around, and the keyboard eventually became unresponsive. The relevant line in the log, as you can find in the attached crash.log file, appears to be: Unable to handle kernel paging request at virtual address 00020024 My guess is that, for whatever reason, I may now be running out of swap space fairly often. If this is true, then either my children have altered their usage habits around the same time that I upgraded the kernel, or something about swap space management has changed between the 2.2.16-3 and 2.2.17-14 kernels. To this end, I've asked my children to be careful about not opening too many windows at the same time, and the system now stays up longer but still, on occasion, without requesting my permission, still goes down hard. I've also been watching the amount of available swap space with the free command. It predictably goes down quite quickly when a hog like netscape is started, but, when that same application exits, the available swap space goes back up very slowly. This would seem to make it very easy to inadvertently run out of swap space, i.e. quitting and restarting an application still, without the user realizing it, appears to be a bad thing to do because of the as yet unreclaimed swap space which is still being counted. Do any of you have any ideas? If I'm right about the slow reclamation of the swap space, is there anything I can do, e.g. alter something in /proc, to speed up swap space reclamation? Thanks. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. Apr 16 11:23:06 dave kernel: Unable to handle kernel paging request at virtual address 00020024 Apr 16 11:23:06 dave kernel: current-tss.cr3 = 00101000, %%cr3 = 00101000 Apr 16 11:23:06 dave kernel: *pde = Apr 16 11:23:06 dave kernel: Oops: Apr 16 11:23:06 dave kernel: CPU:0 Apr 16 11:23:06 dave kernel: EIP:0010:[locks_remove_posix+43/140] Apr 16 11:23:06 dave kernel: EFLAGS: 00010206 Apr 16 11:23:06 dave kernel: eax: c3e6a6d0 ebx: c03e5c70 ecx: c3e6a660 edx: c03e5c70 Apr 16 11:23:06 dave kernel: esi: 0002 edi: c14ff5d0 ebp: c3e6a6d0 esp: c142ff30 Apr 16 11:23:06 dave kernel: ds: 0018 es: 0018 ss: 0018 Apr 16 11:23:06 dave kernel: Process ppp-watch (pid: 7528, process nr: 81, stackpage=c142f000) Apr 16 11:23:06 dave kernel: Stack: c14ff5d0 0001 c3e6a6d0 c3e6a660 0001 c011c9a1 0019 0032 Apr 16 11:23:06 dave kernel:c011ca40 bfffc000 c15147c0 0286 c15147c0 1d00 001d Apr 16 11:23:06 dave kernel:bd68 c151483c 1d00 c012768a c03e5c70 c203a280 00100047 0001 Apr 16 11:23:06 dave kernel: Call Trace: [check_pgt_cache+17/24] [clear_page_tables+152/160] [filp_close+70/88] [do_exit+293/624] [sys_exit+14/16] [system_call+52/56] Apr 16 11:23:06 dave kernel: Code: f6 46 24 01 74 49 8b 4c 24 5c 39 4e 14 75 40 8b 4c 24 58 8b
Re: 2.2.19 Realaudio masq problem
[quoted lines by Whit Blauvelt on April 25, 2001, at 13:38] >On Tue, Apr 24, 2001 at 06:01:05PM -0700, Tim Moore wrote: >> Try '# strace /usr/bin/X11/realplay On24ram.asp > log' and see where the >> connect fails if you aren't getting specific error messages. > >Unfortunately this spits out a bunch of stuff and then totally freezes up my >KDE 2.1.1 desktop. strace writes to standard error, not standard output, by default. Better yet, though, use the -o option of strace to direct its output to a file, which leaves the standard output streams alone for the aplication being traced. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. - 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.2.19 Realaudio masq problem
[quoted lines by Whit Blauvelt on April 25, 2001, at 13:38] On Tue, Apr 24, 2001 at 06:01:05PM -0700, Tim Moore wrote: Try '# strace /usr/bin/X11/realplay On24ram.asp log' and see where the connect fails if you aren't getting specific error messages. Unfortunately this spits out a bunch of stuff and then totally freezes up my KDE 2.1.1 desktop. strace writes to standard error, not standard output, by default. Better yet, though, use the -o option of strace to direct its output to a file, which leaves the standard output streams alone for the aplication being traced. -- Dave Mielke | 2213 Fox Crescent | I believe that the Bible is the Phone: 1-613-726-0014 | Ottawa, Ontario | Word of God. Please contact me EMail: [EMAIL PROTECTED] | Canada K2A 1H7 | if you're concerned about Hell. - 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/
