* Re: problems with ALSA
From: pa3gcu @ 2002-12-13 7:00 UTC (permalink / raw)
To: r4mz3z, linux-newbie
In-Reply-To: <200212110750.08044.r4mz3z@yahoo.es>
On Wednesday 11 December 2002 07:49, r4mz3z wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi friends...
> I have a VIA sound card and I've supossed ALSA drivers can give sound...
> I follow the instructions but when (been root) run modprobe receive an
> error... just like this:
> - -------------------------------------------------------------
> [root@localhost root]# modprobe snd-via82xx
> /lib/modules/.../snd.o: unresolved symbol __get_free_pages_Rsmp_4784e424
> /lib/modules/.../snd.o: unresolved symbol try_inc_mod_count_Rsmp_e6105b23
> /lib/modules/2.4.18-3/kernel/drivers/sound/snd.o: insmod snd-via82xx failed
> [root@localhost root]#
> - -------------------------------------------------------------
> The path complete is: /lib/modules/2.4.18-3/kernel/drivers/sound/
> I'm using RedHat 7.3.
>
Nowhere do you mention which version of alsa you are using, you need at least
0.9.0rc5 which can be obtained at;
http://www.alsa-project.org/
I had to use the above version to get my via8233 Southbridge working.
--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* Re: problems with dmesg
From: pa3gcu @ 2002-12-13 7:11 UTC (permalink / raw)
To: r4mz3z, linux-newbie
In-Reply-To: <200212120015.51006.r4mz3z@yahoo.es>
On Thursday 12 December 2002 00:15, r4mz3z wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi friends..
> I'm using RedHat 7.3 and when I try to run "dmesg" receive this message:
>
> no more MTRRs available
> mtrr: no more MTRRs available
> mtrr: no more MTRRs available
You have processor problems, i think you can change the MTRR settings in
/proc/mtrr
The above is caused by memory type registers in/for your processor, depending
on which video card you use and whats running under X can make a lot of
differance.
Read /usr/src/linux/Documentation/Configure.help grep for MTRR for an
explanation on what MTRR is/does and then read mtrr.txt (same dir) on howto
change the settings.
>
> thanks 4 your help
>
--
Regards Richard
pa3gcu@zeelandnet.nl
http://people.zeelandnet.nl/pa3gcu/
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
^ permalink raw reply
* Re: [Fault-injection-developer] [ANNOUNCE] Fault-Injection Test HarnessProject
From: Yasunori Goto @ 2002-12-13 7:25 UTC (permalink / raw)
To: rusty; +Cc: linux-kernel, fault-injection-developer, lclaudio, acme, olive,
riel
In-Reply-To: <000901c2a265$3ad3a260$6901a8c0@amr.corp.intel.com>
Hello Rusty and all.
I was a developer of LKST, and I know about GKHI's implementation.
rusty> Fault-Injection Test Harness Project
rusty> -------------------------------------
Now, I am interested in your project, and I read white paper for
investigation.
I think that following development items haven't been completed yet.
Is it correct?
- Interceptor of PCI configuration.
- Caller of Code Segment.
If these aren't completed yet, I want to develop it.
Best Regards.
---------------五島康文 (GOTO Yasunori)-------------------
富士通(株)BCCプロジェクト推進部
e-mail: y-goto@jp.fujitsu.com
tel 0559-24-6178(7551-5725) fax 0559-24-6195(7551-6547)
^ permalink raw reply
* Re: 2.5.51 -- rivafb is whacky (characters flipped on vertical axis, 640x480 usable area shown inside a higher-res area, etc).
From: Miles Lane @ 2002-12-13 6:55 UTC (permalink / raw)
To: Antonino Daplas; +Cc: James Simmons, Linux Fbdev development list
In-Reply-To: <1039770362.1025.18.camel@localhost.localdomain>
On Friday, December 13, 2002, at 01:34 AM, Antonino Daplas wrote:
> How extensive is the color problem? Does it just affect the logo, or
> everything? Also, is the color problem present in both hardware and
> software mode (just do fbset -accel true/false to find out)? Is the
> vertical mirroring as reported by Miles still present? How about bpp16
> or bpp32?
I have had mixed results with 2.5.51 (vanilla). I have booted
once where I didn't see the mirroring.
I have not had a chance to test your patch. Hopefully I'll have
time tomorrow. Sorry for the delay.
Miles
-------------------------------------------------------
This sf.net email is sponsored by:
With Great Power, Comes Great Responsibility
Learn to use your power at OSDN's High Performance Computing Channel
http://hpc.devchannel.org/
^ permalink raw reply
* Re: bandwidth
From: Blizzards @ 2002-12-13 7:24 UTC (permalink / raw)
To: Rob Sterenborg; +Cc: netfilter
In-Reply-To: <000001c2a212$a0f05050$0401000a@robbysan.org>
Rob Sterenborg wrote:
>>There are a couple of situations where I need to limit
>>bandwidth on some of my machines. Can anyone share some
>>solutions they have used? Here are a couple of examples of
>>
>>
>
>HTB with iproute2 tc utility.
>http://luxik.cdi.cz/~devik/qos/htb/
>
>Works just fine, easy to configure.
>
>
>Rob
>
>
>
>
>
You can use iptables USER SPACE with SHAPERED.
http://webs.sinectis.com.ar/lesanti/shaperd.
Bye.
G.
^ permalink raw reply
* [BENCHMARK] AIM benchmark result for kernel 2.5.51 with mm2 patch .
From: Sowmya Adiga @ 2002-12-13 7:37 UTC (permalink / raw)
To: linux-kernel
Hi,
Here are the AIM benchmark result for kernel 2.5.51 with mm2 patch.
kernel 2.5.51 with mm2 patch performed better in following tests,when
compared with kernel 2.5.51mm1 patch:-
1)File Creations and Closes/second 2) System Memory Allocations/second
3) Task Creations/second 4) Shared Memory Operations/second
5) TCP/IPMessages/second 6) Pipe Messages/second.7) Program
Loads/second.on the other side kernel 2.5.51mm2 could not do better in
Dynamic Memory Operations/second when compared to kernel 2.5.51mm1
patch.
kernel 2.5.51mm2 patch performed better in following tests,when
compared with kernel 2.5.51 :-
1) Program Loads/second 2)Task Creations/second 3) File Creations and
Closes/second 4) Pipe Messages/second
At the same time 2.5.51mm2 patch had a drop in following performance
when compared with kernel 2.5.51:-
1) System Memory Allocations/second 2) Dynamic Memory
Operations/second 3) UDP/IP DataGrams/second 4) FIFO Messages/second
------------------------------------------------------------------------
---------------------------------------------------
AIM Independent Resource Benchmark - Suite IX v1.1, January 22, 1996
Copyright (c) 1996 - 2001 Caldera International, Inc.
All Rights Reserved
Machine's name :
access1
Machine's configuration
:PIII/868MHZ/128MB
Number of seconds to run each test [2 to 1000] : 60
Path to disk files :
/tmp
------------------------------------------------------------------------
------------------------------------
Test Test Elapsed
Iteration Iteration Operation
Number Name Time (sec) Count
Rate (loops/sec) Rate (ops/sec)
------------------------------------------------------------------------
------------------------------------
1 add_double Thousand Double Precision
Additions/second
linux-2.5.51 60.02 716
11.92936 214728.42
linux-2.5.51[mm1] 60.02 716
11.92936 214728.42
linux-2.5.51[mm2] 60.01 716
11.93134 214764.21
2 add_float Thousand Single
Precision Additions/second
linux-2.5.51 60.05 1075
17.90175 214820.98
linux-2.5.51[mm1] 60.00 1074
17.90000 214800.00
linux-2.5.51[mm2] 60.05 1075
17.90175 214820.98
3 add_long Thousand Long Integer
Additions/second
linux-2.5.51 60.01 1768
29.46176 1767705.38
linux-2.5.51[mm1] 60.01 1768
29.46176 1767705.38
linux-2.5.51[mm2] 60.01 1768
29.46176 1767705.38
4 add_int Thousand Integer
Additions/second
linux-2.5.51 60.02 1768
29.45685 1767410.86
linux-2.5.51[mm1] 60.01 1768
29.46176 1767705.38
linux-2.5.51[mm2] 60.01 1768
29.46176 1767705.38
5 add_short Thousand Short Integer
Additions/second
linux-2.5.51 60.00 4419
73.65000 1767600.00
linux-2.5.51[mm1] 60.01 4419
73.63773 1767305.45
linux-2.5.51[mm2] 60.00 4419
73.65000 1767600.00
6 creat-clo File Creations and
Closes/second
linux-2.5.51 60.02 2157
35.93802 35938.02
linux-2.5.51[mm1] 60.02 2142
35.68810 35688.10
linux-2.5.51[mm2] 60.02 2176
36.25458 36254.58
7 page_test System Allocations &
Pages/second
linux-2.5.51 60.00 8822
147.03333 249956.67
linux-2.5.51[mm1] 60.01 8546
142.40960 242096.32
linux-2.5.51[mm2] 60.00 8606
143.43333 243836.67
8 brk_test System Memory
Allocations/second
linux-2.5.51 60.01 3404
56.72388 964305.95
linux-2.5.51[mm1] 60.01 3236
53.92435 916713.88
linux-2.5.51[mm2] 60.01 3327
55.44076 942492.92
9 jmp_test Non-local gotos/second
linux-2.5.51 60.00 318154
5302.56667 5302566.67
linux-2.5.51[mm1] 60.00 318197
5303.28333 5303283.33
linux-2.5.51[mm2] 60.00 318115
5301.91667 5301916.67
10 signal_test Signal Traps/second
linux-2.5.51 60.00 9573
159.55000 159550.00
linux-2.5.51[mm1] 60.01 9517
158.59023 158590.23
linux-2.5.51[mm2] 60.00 9529
158.81667 158816.67
11 exec_test Program Loads/second
linux-2.5.51 60.03 2054
34.21623 171.08
linux-2.5.51[mm1] 60.00 2082
34.70000 173.50
linux-2.5.51[mm2] 60.01 2101
35.01083 175.05
12 fork_test Task Creations/second
linux-2.5.51 60.04 1016
16.92205 1692.21
linux-2.5.51[mm1] 60.03 1022
17.02482 1702.48
linux-2.5.51[mm2] 60.01 1099
18.31361 1831.36
13 link_test Link/Unlink Pairs/second
linux-2.5.51 60.01 9963
166.02233 10459.41
linux-2.5.51[mm1] 60.00 9857
164.28333 10349.85
linux-2.5.51[mm2] 60.00 9929
165.48333 10425.45
14 disk_rr Random Disk Reads
(K)/second
linux-2.5.51 60.00 496
8.26667 42325.33
linux-2.5.51[mm1] 60.06 501
8.34166 42709.29
linux-2.5.51[mm2] 60.06 489
8.14186 41686.31
15 disk_rw Random Disk Writes
(K)/second
linux-2.5.51 60.12 394
6.55356 33554.22
linux-2.5.51[mm1] 60.17 387
6.43178 32930.70
linux-2.5.51[mm2] 60.07 387
6.44248 32985.52
16 disk_rd Sequential Disk Reads
(K)/second
linux-2.5.51 60.02 2813
46.86771 239962.68
linux-2.5.51[mm1] 60.01 2795
46.57557 238466.92
linux-2.5.51[mm2] 60.01 2822
47.02550 240770.54
17 disk_wrt Sequential Disk Writes
(K)/second
linux-2.5.51 60.07 646
10.75412 55061.10
linux-2.5.51[mm1] 60.07 644
10.72083 54890.63
linux-2.5.51[mm2] 60.06 633
10.53946 53962.04
18 disk_cp Disk Copies (K)/second
linux-2.5.51 60.10 509
8.46922 43362.40
linux-2.5.51[mm1] 60.06 501
8.34166 42709.29
linux-2.5.51[mm2] 60.00 499
8.31667 42581.33
19 sync_disk_rw Sync Random Disk Writes
(K)/second
linux-2.5.51 60.91 1
0.01642 42.03
linux-2.5.51[mm1] 60.11 1
0.01664 42.59
linux-2.5.51[mm2] 60.21 1
0.01661 42.52
20 sync_disk_wrt Sync Sequential Disk Writes
(K)/second
linux-2.5.51 76.81 2
0.02604 66.66
linux-2.5.51[mm1] 76.42 2
0.02617 67.00
linux-2.5.51[mm2] 76.85 2
0.02602 66.62
21 sync_disk_cp Sync Disk Copies (K)/second
linux-2.5.51 77.63 2
0.02576 65.95
linux-2.5.51[mm1] 77.86 2
0.02569 65.76
linux-2.5.51[mm2] 77.57 2
0.02578 66.00
22 disk_src Directory Searches/second
linux-2.5.51 60.00
10811 180.18333 13513.75
linux-2.5.51[mm1] 60.01 10741
178.98684 13424.01
linux-2.5.51[mm2] 60.01 10715
178.55357 13391.52
23 div_double Thousand Double Precision
Divides/second
linux-2.5.51 60.01 1322
22.02966 66088.99
linux-2.5.51[mm1] 60.01 1322
22.02966 66088.99
linux-2.5.51[mm2] 60.01 1322
22.02966 66088.99
24 div_float Thousand Single Precision
Divides/second
linux-2.5.51 60.00 1322
22.03333 66100.00
linux-2.5.51[mm1] 60.00 1322
22.03333 66100.00
linux-2.5.51[mm2] 60.00 1322
22.03333 66100.00
25 div_long Thousand Long Integer
Divides/second
linux-2.5.51 60.03
1592 26.52007 23868.07
linux-2.5.51[mm1] 60.03 1592
26.52007 23868.07
linux-2.5.51[mm2] 60.04 1592
26.51566 23864.09
26 div_int Thousand Integer
Divides/second
linux-2.5.51 60.03
1592 26.52007 23868.07
linux-2.5.51[mm1] 60.03 1592
26.52007 23868.07
linux-2.5.51[mm2] 60.01 1591
26.51225 23861.02
27 div_short Thousand Short Integer
Divides/second
linux-2.5.51 60.01
1591 26.51225 23861.02
linux-2.5.51[mm1] 60.03 1592
26.52007 23868.07
linux-2.5.51[mm2] 60.03 1592
26.52007 23868.07
28 fun_cal Function Calls (no
arguments)/second
linux-2.5.51 60.01
4362 72.68789 37216197.30
linux-2.5.51[mm1] 60.01 4362
72.68789 37216197.30
linux-2.5.51[mm2] 60.01 4362
72.68789 37216197.30
29 fun_cal1 Function Calls (1
argument)/second
linux-2.5.51 60.00
10231 170.51667 87304533.33
linux-2.5.51[mm1] 60.00 10230
170.50000 87296000.00
linux-2.5.51[mm2] 60.00 10231
170.51667 87304533.33
30 fun_cal2 Function Calls (2
arguments)/second
linux-2.5.51 60.00
7971 132.85000 68019200.00
linux-2.5.51[mm1] 60.00 7968
132.80000 67993600.00
linux-2.5.51[mm2] 60.00 7970
132.83333 68010666.67
31 fun_cal15 Function Calls (15
arguments)/second
linux-2.5.51 60.03
2455 40.89622 20938863.90
linux-2.5.51[mm1] 60.03 2455
40.89622 20938863.90
linux-2.5.51[mm2] 60.03 2455
40.89622 20938863.90
32 sieve Integer Sieves/second
linux-2.5.51 60.47 41
0.67802 3.39
linux-2.5.51[mm1] 60.49 41
0.67780 3.39
linux-2.5.51[mm2] 60.46 41
0.67813 3.39
33 mul_double Thousand Double Precision
Multiplies/second
linux-2.5.51 60.01 833
13.88102 166572.24
linux-2.5.51[mm1] 60.05 838
13.95504 167460.45
linux-2.5.51[mm2] 60.07 837
13.93374 167204.93
34 mul_float Thousand Single Precision
Multiplies/second
linux-2.5.51 60.03 836
13.92637 167116.44
linux-2.5.51[mm1] 60.02 835
13.91203 166944.35
linux-2.5.51[mm2] 60.05 837
13.93838 167260.62
35 mul_long Thousand Long Integer
Multiplies/second
linux-2.5.51 60.00
75687 1261.45000 302748.00
linux-2.5.51[mm1] 60.00 75693
1261.55000 302772.00
linux-2.5.51[mm2] 60.00 75675
1261.25000 302700.00
36 mul_int Thousand Integer
Multiplies/second
linux-2.5.51 60.00
76015 1266.91667 304060.00
linux-2.5.51[mm1] 60.00 76013
1266.88333 304052.00
linux-2.5.51[mm2] 60.00 75978
1266.30000 303912.00
37 mul_short Thousand Short Integer
Multiplies/second
linux-2.5.51 60.00
60527 1008.78333 302635.00
linux-2.5.51[mm1] 60.00 60564
1009.40000 302820.00
linux-2.5.51[mm2] 60.00 60624
1010.40000 303120.00
38 num_rtns_1 Numeric Functions/second
linux-2.5.51 60.00
32603 543.38333 54338.33
linux-2.5.51[mm1] 60.00 32602
543.36667 54336.67
linux-2.5.51[mm2] 60.00 32587
543.11667 54311.67
39 new_raph Zeros Found/second
linux-2.5.51 60.00
79903 1331.71667 266343.33
linux-2.5.51[mm1] 60.00 79905
1331.75000 266350.00
linux-2.5.51[mm2] 60.00 79890
1331.50000 266300.00
40 trig_rtns Trigonometric Functions/second
linux-2.5.51 60.01 2160
35.99400 359940.01
linux-2.5.51[mm1] 60.02 2168
36.12129 361212.93
linux-2.5.51[mm2] 60.01 2168
36.12731 361273.12
41 matrix_rtns Point Transformations/second
linux-2.5.51 60.00
349540 5825.66667 582566.67
linux-2.5.51[mm1] 60.00 349593
5826.55000 582655.00
linux-2.5.51[mm2] 60.00 349515
5825.25000 582525.00
42 array_rtns Linear Systems Solved/second
linux-2.5.51 60.00 959
15.98333 319.67
linux-2.5.51[mm1] 60.05 960
15.98668 319.73
linux-2.5.51[mm2] 60.03 959
15.97535 319.51
43 string_rtns String Manipulations/second
linux-2.5.51 60.01 851
14.18097 1418.10
linux-2.5.51[mm1] 60.06 852
14.18581 1418.58
linux-2.5.51[mm2] 60.06 852
14.18581 1418.58
44 mem_rtns_1 Dynamic Memory Operations/second
linux-2.5.51 60.00 1640
27.33333 820000.00
linux-2.5.51[mm1] 60.02 1910
31.82273 954681.77
linux-2.5.51[mm2] 60.04 1530
25.48301 764490.34
45 mem_rtns_2 Block Memory Operations/second
linux-2.5.51 60.00
131025 2183.75000 218375.00
linux-2.5.51[mm1] 60.00 131053
2184.21667 218421.67
linux-2.5.51[mm2] 60.00 131034
2183.90000 218390.00
46 sort_rtns_1 Sort Operations/second
linux-2.5.51 60.02 2425
40.40320 404.03
linux-2.5.51[mm1] 60.02 2425
40.40320 404.03
linux-2.5.51[mm2] 60.01 2424
40.39327 403.93
47 misc_rtns_1 Auxiliary Loops/second
linux-2.5.51 60.00
32379 539.65000 5396.50
linux-2.5.51[mm1] 60.00 31628
527.13333 5271.33
linux-2.5.51[mm2] 60.00 31911
531.85000 5318.50
48 dir_rtns_1 Directory Operations/second
linux-2.5.51 60.00
13181 219.68333 2196833.33
linux-2.5.51[mm1] 60.00 12621
210.35000 2103500.00
linux-2.5.51[mm2] 60.00 13128
218.80000 2188000.00
49 shell_rtns_1 Shell Scripts/second
linux-2.5.51 60.02 2472
41.18627 41.19
linux-2.5.51[mm1] 60.01 2479
41.30978 41.31
linux-2.5.51[mm2] 60.00 2470
41.16667 41.17
50 shell_rtns_2 Shell Scripts/second
linux-2.5.51 60.00 2479
41.31667 41.32
linux-2.5.51[mm1] 60.01 2478
41.29312 41.29
linux-2.5.51[mm2] 60.02 2480
41.31956 41.32
51 shell_rtns_3 Shell Scripts/second
linux-2.5.51 60.01 2479
41.30978 41.31
linux-2.5.51[mm1] 60.02 2480
41.31956 41.32
linux-2.5.51[mm2] 60.00 2478
41.30000 41.30
52 series_1 Series Evaluations/second
linux-2.5.51 60.00
1464266 24404.43333 2440443.33
linux-2.5.51[mm1] 60.00 1464388
24406.46667 2440646.67
linux-2.5.51[mm2] 60.00 1464074
24401.23333 2440123.33
53 shared_memory Shared Memory Operations/second
linux-2.5.51 60.00
168202 2803.36667 280336.67
linux-2.5.51[mm1] 60.00 157980
2633.00000 263300.00
linux-2.5.51[mm2] 60.00 166154
2769.23333 276923.33
54 tcp_test TCP/IPMessages/second
linux-2.5.51 60.01 11200
186.63556 16797.20
linux-2.5.51[mm1] 60.00 10780
179.66667 16170.00
linux-2.5.51[mm2] 60.00 10927
182.11667 16390.50
55 udp_test UDP/IP DataGrams/second
linux-2.5.51 60.00 49319
821.98333 82198.33
linux-2.5.51[mm1] 60.00 47033
783.88333 78388.33
linux-2.5.51[mm2] 60.00 46617
776.95000 77695.00
56 fifo_test FIFO Messages/second
linux-2.5.51 60.00 92331
1538.85000 153885.00
linux-2.5.51[mm1] 60.00 88371
1472.85000 147285.00
linux-2.5.51[mm2] 60.00 89477
1491.28333 149128.33
57 stream_pipe Stream Pipe Messages/second
linux-2.5.51 60.00 70959
1182.65000 118265.00
linux-2.5.51[mm1] 60.00 70192
1169.86667 116986.67
linux-2.5.51[mm2] 60.00 70782
1179.70000 117970.00
58 dgram_pipe DataGram Pipe Messages/second
linux-2.5.51 60.00 69617
1160.28333 116028.33
linux-2.5.51[mm1] 60.00 68397
1139.95000 113995.00
linux-2.5.51[mm2] 60.00 70214
1170.23333 117023.33
59 pipe_cpy Pipe Messages/second
linux-2.5.51 60.00 248370
4139.50000 413950.00
linux-2.5.51[mm1] 60.00 236957
3949.28333 394928.33
linux-2.5.51[mm2] 60.00 253724
4228.73333 422873.33
60 ram_copy Memory to Memory Copy/second
linux-2.5.51 60.00 1496002
24933.36667 623832834.00
linux-2.5.51[mm1] 60.00 1495745
24929.08333 623725665.00
linux-2.5.51[mm2] 60.00 1495977
24932.95000 623822409.00
------------------------------------------------------------------------
------------------------------------
Regards
Sowmya Adiga
^ permalink raw reply
* Re: [Linux-ia64] [PATCH] fix /proc/.../vm_info
From: Christian Hildner @ 2002-12-13 7:45 UTC (permalink / raw)
To: linux-ia64
In-Reply-To: <marc-linux-ia64-105590709805552@msgid-missing>
David Mosberger schrieb:
> >>>>> On Thu, 12 Dec 2002 14:49:10 +0100, Christian Hildner <christian.hildner@hob.de> said:
>
> Christian> Hi, in vm_info the information about the supported memory
> Christian> attributes is wrong. The patch is based on 2.4.18, but it
> Christian> should also work for 2.4.20 and 2.5.x. Please apply.
>
> I'd like to keep the output a bit more concise. How about the attached
> patch (untested)?
I agree. But I would like a distinction between both UCs like "UC (001)" and "UC (100)".
Christian
>
>
> --david
>
> === arch/ia64/kernel/palinfo.c 1.7 vs edited ==> --- 1.7/arch/ia64/kernel/palinfo.c Sun Dec 1 22:17:31 2002
> +++ edited/arch/ia64/kernel/palinfo.c Thu Dec 12 11:54:24 2002
> @@ -101,26 +101,15 @@
>
> #define RSE_HINTS_COUNT (sizeof(rse_hints)/sizeof(const char *))
>
> -/*
> - * The current revision of the Volume 2 (July 2000) of
> - * IA-64 Architecture Software Developer's Manual is wrong.
> - * Table 4-10 has invalid information concerning the ma field:
> - * Correct table is:
> - * bit 0 - 001 - UC
> - * bit 4 - 100 - UC
> - * bit 5 - 101 - UCE
> - * bit 6 - 110 - WC
> - * bit 7 - 111 - NatPage
> - */
> static const char *mem_attrib[]={
> - "Write Back (WB)", /* 000 */
> - "Uncacheable (UC)", /* 001 */
> - "Reserved", /* 010 */
> - "Reserved", /* 011 */
> - "Uncacheable (UC)", /* 100 */
> - "Uncacheable Exported (UCE)", /* 101 */
> - "Write Coalescing (WC)", /* 110 */
> - "NaTPage" /* 111 */
> + "WB", /* 000 */
> + "UC", /* 001 */
> + "010", /* 010 */
> + "011", /* 011 */
> + "UC", /* 100 */
> + "UCE", /* 101 */
> + "WC", /* 110 */
> + "NaTPage" /* 111 */
> };
>
> /*
> @@ -315,6 +304,7 @@
> pal_vm_info_2_u_t vm_info_2;
> pal_tc_info_u_t tc_info;
> ia64_ptce_info_t ptce;
> + const char *sep;
> int i, j;
> s64 status;
>
> @@ -339,7 +329,14 @@
>
> if (ia64_pal_mem_attrib(&attrib) != 0) return 0;
>
> - p += sprintf(p, "Supported memory attributes : %s\n", mem_attrib[attrib&0x7]);
> + p += sprintf(p, "Supported memory attributes : ");
> + sep = "";
> + for (i = 0; i < 8; i++) {
> + if (attrib & (1 << i)) {
> + p += sprintf(p, "%s%s\n", sep, mem_attrib[i]);
> + sep = ", ";
> + }
> + }
>
> if ((status=ia64_pal_vm_page_size(&tr_pages, &vw_pages)) !=0) {
> printk("ia64_pal_vm_page_size=%ld\n", status);
^ permalink raw reply
* RE: Is the preemptive kernel patch unsafe for 8xx/PPC?
From: Joakim Tjernlund @ 2002-12-13 7:47 UTC (permalink / raw)
To: Eugene Surovegin; +Cc: linuxppc-dev, acurtis
In-Reply-To: <5.1.0.14.2.20021212214102.02bf1338@mail.attbi.com>
Hi Eugene
> From: Eugene Surovegin [mailto:ebs@innocent.com]
> Joakim,
>
> At 12:35 PM 12/12/2002, you wrote:
> >Was that the 2.4.19-2 patch? What were the bugs and have you fixed them?
>
> I had the following issues with 2.4.19-2 (2.4.20-1 is identical in this
> regard):
>
> 1) arch/ppc/kernel.entry.S
>
> diff -urN linux-2.4.20/arch/ppc/kernel/entry.S linux/arch/ppc/kernel/entry.S
> --- linux-2.4.20/arch/ppc/kernel/entry.S 2002-11-28
> 18:53:11.000000000 -0500
> +++ linux/arch/ppc/kernel/entry.S 2002-12-11 02:34:47.000000000 -0500
> @@ -278,6 +278,41 @@
> */
> cmpi 0,r3,0
> beq restore
> +#ifdef CONFIG_PREEMPT
> + lwz r3,PREEMPT_COUNT(r2)
> + cmpi 0,r3,1
> + bge ret_from_except
> + lwz r5,_MSR(r1)
> + andi. r5,r5,MSR_PR
> + bne do_signal_ret
>
> <rest of the diff is skipped>
>
> I had to change the last command to "bne ret_from_except".
> I checked MontaVista tree, and they have "ret_from_except" there also.
This I can not comment on, but my 8xx runs fine with it.
>
> Without this change trivial code:
>
> while (true) ;
>
> locked the box completely.
>
> 2) include/asm-ppc/pgalloc.h There are curly brackets missing in
> get_pgd_fast()
Yes, they are missing in the else part.
>
> 3) to support 440GP you have to modify arc/ppc/kernel/irc.c:preempt_intercept:
>
> #if !defined(CONFIG_4xx) || defined(CONFIG_440)
> case 0x900:
> #else
> case 0x1000:
> #endif
OK, this does not affect 8xx so this I can not test.
>
> With these changes (an maybe some others I forgot to mention here :),
> I have pretty stable preemptable kernel (2.4.19, PPC440GP & 405GP, also
> with rtsched patch by George Anzinger)
>
Can you run the above changes by Robert Love so he can comment/update the patch?
Jocke
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
^ permalink raw reply
* Re: 2.5.51 ide module problem
From: Adam J. Richter @ 2002-12-13 7:59 UTC (permalink / raw)
To: Jeff Chua, alan; +Cc: linux-kernel, rusty
In-Reply-To: <Pine.LNX.4.50.0212111711180.4632-200000@boston.corp.fedex.com>
[-- Attachment #1: Type: text/plain, Size: 1867 bytes --]
On Wed, Dec 11, 2002 at 05:29:03PM +0800, Jeff Chua wrote:
> On Wed, 11 Dec 2002, Adam J. Richter wrote:
> > Here is a quick diff of my drivers/ide subdirectory versus stock 2.5.51.
>
> +++ linux/drivers/ide/pci/cmd640.c 2002-11-27 18:24:00.000000000
> -int cmd640_vlb = 0;
>
> These lines must "stay" in cmd640.c, else it won't compile.
>
> "depmod -a" works now, but encounter a new problem when I tried to load
> ide ...
>
> # modprobe ide-mod
> FATAL: Error inserting ide_mod (/lib/modules/2.5.51/kernel/ide-mod.ko):
> Unknown symbol in module
> ide_mod: Unknown symbol pci_enable_device_bars
Jeff: Sorry, I forgot to include diffs for include/linux/ide.h
and drivers/pci/pci.c. Here is a corrected patch. I am running the
code on that machine on which I'm composing this email, and I have
also verified that cmd640.c compiled without complaint (well,
actually, I've modified the patch slightly to eliminate some unrelated
diffs).
Alan: If you want, please feel free to merge this change.
Alternatively, if you're stepping away from 2.5 while waiting for
modules to stabilize, I'd appreciate knowing what you'd prefer be done
with incoming IDE patches (submit them to Andre and Jens, just wait,
something else?). For what it's worth, 2.5.51 +
init-module-tools-0.9.3 is the first kernel-based module loader
configuration which works enough so that I'm able to work on other
things. For the past few releases, I had been restoring user level
module loading. There still are a lot of quirks with the kernel based
module loading, but you might find it sufficient to get things done.
Adam J. Richter __ ______________ 575 Oroville Road
adam@yggdrasil.com \ / Milpitas, California 95035
+1 408 309-6081 | g g d r a s i l United States of America
"Free Software For The Rest Of Us."
[-- Attachment #2: ide.diff --]
[-- Type: text/plain, Size: 4999 bytes --]
--- linux-2.5.51/include/linux/ide.h 2002-12-09 18:45:54.000000000 -0800
+++ linux/include/linux/ide.h 2002-11-27 18:24:04.000000000 -0800
@@ -1742,8 +1742,12 @@
extern void ide_toggle_bounce(ide_drive_t *drive, int on);
extern int ide_set_xfer_rate(ide_drive_t *drive, u8 rate);
+/* ide.c */
+extern int ide_probe_init(void);
+extern void ide_probe_cleanup(void);
+extern int cmd640_vlb;
extern spinlock_t ide_lock;
#define local_irq_set(flags) do { local_save_flags((flags)); local_irq_enable(); } while (0)
--- linux-2.5.51/drivers/pci/pci.c 2002-12-09 18:45:52.000000000 -0800
+++ linux/drivers/pci/pci.c 2002-12-09 19:03:18.000000000 -0800
@@ -736,6 +736,7 @@
EXPORT_SYMBOL(isa_bridge);
#endif
+EXPORT_SYMBOL(pci_enable_device_bars);
EXPORT_SYMBOL(pci_enable_device);
EXPORT_SYMBOL(pci_disable_device);
EXPORT_SYMBOL(pci_max_busnr);
diff -r -u linux-2.5.51/drivers/ide/Kconfig linux/drivers/ide/Kconfig
--- linux-2.5.51/drivers/ide/Kconfig 2002-12-09 18:45:56.000000000 -0800
+++ linux/drivers/ide/Kconfig 2002-11-27 18:23:46.000000000 -0800
@@ -199,7 +199,7 @@
depends on BLK_DEV_IDE
config BLK_DEV_CMD640
- bool "CMD640 chipset bugfix/support"
+ tristate "CMD640 chipset bugfix/support"
depends on BLK_DEV_IDE && X86
---help---
The CMD-Technologies CMD640 IDE chip is used on many common 486 and
@@ -247,7 +247,7 @@
default BLK_DEV_IDEDMA_PMAC if ALL_PPC && BLK_DEV_IDEDMA_PMAC
config BLK_DEV_GENERIC
- bool "Generic PCI IDE Chipset Support"
+ tristate "Generic PCI IDE Chipset Support"
depends on PCI && BLK_DEV_IDEPCI
config IDEPCI_SHARE_IRQ
diff -r -u linux-2.5.51/drivers/ide/Makefile linux/drivers/ide/Makefile
--- linux-2.5.51/drivers/ide/Makefile 2002-12-09 18:45:59.000000000 -0800
+++ linux/drivers/ide/Makefile 2002-11-29 12:01:33.000000000 -0800
@@ -14,21 +14,22 @@
# Core IDE code - must come before legacy
-obj-$(CONFIG_BLK_DEV_IDE) += ide-io.o ide-probe.o ide-geometry.o ide-iops.o ide-taskfile.o ide.o ide-lib.o
+obj-$(CONFIG_BLK_DEV_IDE) += ide-mod.o
+ide-mod-objs += ide-io.o ide-probe.o ide-geometry.o ide-iops.o ide-taskfile.o ide.o ide-lib.o
obj-$(CONFIG_BLK_DEV_IDEDISK) += ide-disk.o
obj-$(CONFIG_BLK_DEV_IDECD) += ide-cd.o
obj-$(CONFIG_BLK_DEV_IDETAPE) += ide-tape.o
obj-$(CONFIG_BLK_DEV_IDEFLOPPY) += ide-floppy.o
-obj-$(CONFIG_BLK_DEV_IDEPCI) += setup-pci.o
-obj-$(CONFIG_BLK_DEV_IDEDMA_PCI) += ide-dma.o
-obj-$(CONFIG_BLK_DEV_IDE_TCQ) += ide-tcq.o
-obj-$(CONFIG_BLK_DEV_ISAPNP) += ide-pnp.o
-
-ifeq ($(CONFIG_BLK_DEV_IDE),y)
-obj-$(CONFIG_PROC_FS) += ide-proc.o
-endif
+obj-ide-$(CONFIG_BLK_DEV_IDEPCI) += setup-pci.o
+obj-ide-$(CONFIG_BLK_DEV_IDEDMA_PCI) += ide-dma.o
+obj-ide-$(CONFIG_BLK_DEV_IDE_TCQ) += ide-tcq.o
+obj-ide-$(CONFIG_BLK_DEV_ISAPNP) += ide-pnp.o
+obj-ide-$(CONFIG_PROC_FS) += ide-proc.o
+
+ide-mod-objs += $(obj-ide-y)
+obj-m += $(obj-ide-m)
obj-$(CONFIG_BLK_DEV_IDE) += legacy/ ppc/ arm/
diff -r -u linux-2.5.51/drivers/ide/ide.c linux/drivers/ide/ide.c
--- linux-2.5.51/drivers/ide/ide.c 2002-12-09 18:45:52.000000000 -0800
+++ linux/drivers/ide/ide.c 2002-12-09 19:03:20.000000000 -0800
@@ -2375,7 +2375,7 @@
ide_init_builtin_drivers();
initializing = 0;
- return 0;
+ return ide_probe_init();
}
#ifdef MODULE
diff -r -u linux-2.5.51/drivers/ide/pci/cmd640.c linux/drivers/ide/pci/cmd640.c
--- linux-2.5.51/drivers/ide/pci/cmd640.c 2002-12-09 18:46:22.000000000 -0800
+++ linux/drivers/ide/pci/cmd640.c 2002-11-27 18:24:00.000000000 -0800
@@ -102,6 +102,7 @@
#define CMD640_PREFETCH_MASKS 1
#include <linux/config.h>
+#include <linux/module.h>
#include <linux/types.h>
#include <linux/kernel.h>
#include <linux/delay.h>
@@ -118,11 +119,6 @@
#include "ide_modes.h"
/*
- * This flag is set in ide.c by the parameter: ide0=cmd640_vlb
- */
-int cmd640_vlb = 0;
-
-/*
* CMD640 specific registers definition.
*/
@@ -723,7 +719,7 @@
/*
* Probe for a cmd640 chipset, and initialize it if found. Called from ide.c
*/
-int __init ide_probe_for_cmd640x (void)
+static int ide_probe_for_cmd640x (void)
{
#ifdef CONFIG_BLK_DEV_CMD640_ENHANCED
int second_port_toggled = 0;
@@ -883,4 +879,4 @@
#endif
return 1;
}
-
+module_init(ide_probe_for_cmd640x);
--- linux-2.5.51/drivers/ide/ide-probe.c 2002-12-09 18:46:10.000000000 -0800
+++ linux/drivers/ide/ide-probe.c 2002-12-12 23:50:58.000000000 -0800
@@ -831,7 +831,8 @@
ide_toggle_bounce(drive, 1);
#ifdef CONFIG_BLK_DEV_IDE_TCQ_DEFAULT
- HWIF(drive)->ide_dma_queued_on(drive);
+ if (HWIF(drive)->ide_dma_queued_on)
+ HWIF(drive)->ide_dma_queued_on(drive);
#endif
}
@@ -1221,10 +1222,9 @@
return 0;
}
-#ifdef MODULE
extern int (*ide_xlate_1024_hook)(struct block_device *, int, int, const char *);
-int init_module (void)
+int ide_probe_init (void)
{
unsigned int index;
@@ -1236,10 +1236,9 @@
return 0;
}
-void cleanup_module (void)
+void ide_probe_cleanup (void)
{
ide_probe = NULL;
ide_xlate_1024_hook = 0;
}
MODULE_LICENSE("GPL");
-#endif /* MODULE */
^ permalink raw reply
* RE: [Fault-injection-developer] [ANNOUNCE] Fault-Injection Test H arnessProject
From: Lynch, Rusty @ 2002-12-13 8:01 UTC (permalink / raw)
To: 'y-goto@jp.fujitsu.com', rusty
Cc: linux-kernel, fault-injection-developer, lclaudio, acme, olive,
riel
We currently have some infrastructure and a MMIO interceptor implemented so
an interceptor for PCI configuration data is fare game.
Join the mailing list at
http://lists.sourceforge.net/lists/listinfo/fault-injection-developer
and start hacking. :->
-rusty
> -----Original Message-----
> From: y-goto@jp.fujitsu.com [mailto:y-goto@jp.fujitsu.com]
> Sent: Thursday, December 12, 2002 11:26 PM
> To: rusty@linux.co.intel.com
> Cc: linux-kernel@vger.kernel.org;
> fault-injection-developer@sourceforge.net;
> lclaudio@conectiva.com.br; acme@conectiva.com.br;
> olive@conectiva.com.br; riel@conectiva.com.br
> Subject: Re: [Fault-injection-developer] [ANNOUNCE]
> Fault-Injection Test HarnessProject
>
>
> Hello Rusty and all.
>
> I was a developer of LKST, and I know about GKHI's implementation.
>
> rusty> Fault-Injection Test Harness Project
> rusty> -------------------------------------
>
> Now, I am interested in your project, and I read white paper for
> investigation.
> I think that following development items haven't been completed yet.
> Is it correct?
> - Interceptor of PCI configuration.
> - Caller of Code Segment.
> If these aren't completed yet, I want to develop it.
>
> Best Regards.
>
> ---------------五島康文 (GOTO Yasunori)-------------------
> 富士通(株)BCCプロジェクト推進部
> e-mail: y-goto@jp.fujitsu.com
> tel 0559-24-6178(7551-5725) fax 0559-24-6195(7551-6547)
>
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Fault-injection-developer mailing list
> Fault-injection-developer@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fault-injection-developer
>
^ permalink raw reply
* Re: separation of sysctl and tcp-window-tracking patch?
From: James Ralston @ 2002-12-13 8:14 UTC (permalink / raw)
To: netfilter-devel
In-Reply-To: <Pine.LNX.4.33.0212120955290.14108-100000@blackhole.kfki.hu>
On Thu, 12 Dec 2002, Jozsef Kadlecsik wrote:
> Please note, that the timeout settings via /proc introduced in the
> tcp-window-tracking patch are global. You cannot raise the UDP
> timeout values just for DNS.
That's true. But on dedicated nameservers (the situation I care
about), I don't care if all UDP connections on the system receive the
higher limit.
> Also, we have to handle the backward compatibility issue of
> /proc/sys/net/ipv4/ip_conntrack_max, if the introduction of
> /proc/sys/net/ipv4/netfilter/ is accepted.
True.
--
James Ralston, Information Technology
Software Engineering Institute
Carnegie Mellon University, Pittsburgh, PA, USA
^ permalink raw reply
* Re: Memory Measurements and Lots of Files and Inodes
From: David Schwartz @ 2002-12-13 8:39 UTC (permalink / raw)
To: mcmanus, linux-kernel
In-Reply-To: <20021211235258.GA10857@ducksong.com>
>Can anybody provide a better metric for "ram free for userspace
>allocations"?
This is a constant battle for programmers trying to develop sophisticated
applications for sophisticated operating systems.
If all of the applications are cooperating, you can do it fairly easily.
First, ask the kernel how much physical memory there is. Then fudge a
reduction based on kernel usage. Then subtract the amount of RAM each
application is 'really using' by asking it.
If you write all the applications, this isn't hard to do. If you have to
cooperate with other applications you didn't write, things get trickier. If
you're the only application, things are really easy.
There are any number of heuristics and guesstimates. Ultimately, I recommend
mostly leaving your memory usage user-configurable.
DS
^ permalink raw reply
* Re: [lvm-devel] Re: "bio too big" error
From: Joe Thornber @ 2002-12-13 8:41 UTC (permalink / raw)
To: lvm-devel; +Cc: Joe Thornber, Wil Reichert, Greg KH, kernel list
In-Reply-To: <02121215511604.05277@boiler>
On Thu, Dec 12, 2002 at 03:51:16PM -0600, Kevin Corry wrote:
> I believe we have tracked the problem down to the call to dm_get_device() in
> dm-linear.c.
Yes, that'll be it. Well done.
- Joe
^ permalink raw reply
* 2 internet link problem (forwarding help i think?)
From: louie miranda @ 2002-12-13 8:36 UTC (permalink / raw)
To: netfilter
In-Reply-To: <3DF98B3D.5010104@libero.it>
Hi things i have to clear first!
DEFAULT GATEWAY = 203.100.100.1
MACHINE's (primary) IP = 203.100.100.2 - NIC1
MACHINE's (secondary) IP = 203.100.100.3 - NIC2
MASQ BLOCK = 10.0.0.0/16 - NIC3
I have 3 NIC Cards, My only problem is i want to route all my MASQ BLOCK
that when they
access IP BLOCK 203.100.200.0/24 they will come out on NIC2 (Secondary IP of
my machine)
And all other packets to its default route.
Is this possible? Im currently mixed up also when i tried to add the `route`
on linux when i ping
that ip, the secondary IP will not work anymore but my default route to NIC1
will be still the same.
Its like this, I can access 203.100.100.3 (Im not yet adding my secondary
ip/route) When i add
my secondary ip/route 203.100.100.3 "ifconfig eth2 203.100.100.3 netmask
255.255.255.240 up"
I can no longer access 203.100.100.3 But all of my other connections are
working except for that.
my kernel routing table after adding.. (not real ip's)
panic:/# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
Iface
203.100.100.* 0.0.0.0 255.255.255.248 U 0 0 0 eth0
203.100.100.* 0.0.0.0 255.255.255.240 U 0 0 0 eth2
10.0.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth1
0.0.0.0 203.100.100.1 0.0.0.0 UG 0 0 0 eth0
Hope someone can help!
--
thanks,
louie miranda
--
thanks,
louie miranda
^ permalink raw reply
* Re: pci-skeleton duplex check
From: David S. Miller @ 2002-12-13 9:17 UTC (permalink / raw)
To: Donald Becker
Cc: Jeff Garzik, Roger Luethi, netdev, Linux Kernel Mailing List
In-Reply-To: <Pine.LNX.4.44.0212121743500.10674-100000@beohost.scyld.com>
On Thu, 2002-12-12 at 17:18, Donald Becker wrote:
> Or perhaps recognizing that when someone that has been a significant,
> continuous contributer since the early days of Linux
Until you learn to play nice with people and mesh within the
fabric of Linux development, I adamently do not classify you
as you appear to self-classify yourself. You don't contribute,
you sit in your sandbox and then point fingers at the people who
do know how to work with other human beings and say "see how much
that stuff sucks? well my stuff works, nyah!"
I fear you will hold a grudge about this forever.
If Linux itself is worse off and went backwards in time for a while, it
is because of your inability to work together with people.
I know it may be hard for you to accept this fact, but I can tell you
that continuing to point the fingers elsewhere is going to be a repeated
dead end.
^ permalink raw reply
* Re: atyfb in 2.5.51
From: Geert Uytterhoeven @ 2002-12-13 8:49 UTC (permalink / raw)
To: David S. Miller
Cc: James Simmons, Benjamin Herrenschmidt, Paul Mackerras,
Linux Kernel Mailing List, Linux Fbdev development list
In-Reply-To: <1039596149.24691.2.camel@rth.ninka.net>
On 11 Dec 2002, David S. Miller wrote:
> On Tue, 2002-12-10 at 22:18, James Simmons wrote:
> > > AFAIK, the X "mach64" driver in XF 4.* doesn't care about UseFBDev.
> > > Marc Aurele La France (maintainer of this driver) is basically allergic
> > > to kernel fbdev support.
> >
> > :-(
>
> I've always stated that the whole fbdev model was flawed, it makes
> basic assumptions about how a video card's memory and registers are
> accessed (ie. the programming model) and many popular cards absolutely
> do not fit into that model.
Could you please elaborate so we have a chance to improve the model? Thanks!
In case you just mean graphics hardware (e.g. Creator) where you don't want to
provide direct access to the frame buffer, but do everything through the
acceleration engine, just set smem_start and smem_len both to 0.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply
* Re: atyfb in 2.5.51
From: Geert Uytterhoeven @ 2002-12-13 8:53 UTC (permalink / raw)
To: Alan Cox
Cc: David S. Miller, James Simmons, Benjamin Herrenschmidt,
Paul Mackerras, Linux Kernel Mailing List,
Linux Frame Buffer Device Development
In-Reply-To: <1039642510.18467.40.camel@irongate.swansea.linux.org.uk>
On 11 Dec 2002, Alan Cox wrote:
> On Wed, 2002-12-11 at 20:43, David S. Miller wrote:
> > fbdev is nice, in the specific cases where the device fits the fbdev
> > model, because once you have the kernel bits you have X support :)
>
> fbdev also can't be used in some situations on x86. Deeply fascinating
> things happen on some x86 processors if you execute a loop of code with
> an instruction that crosses two different memory types.
Do you mean one load/store access to memory where the first and the last part
(e.g. first 2 and last 2 bytes for a 32-bit word) are to different memory types
(e.g. main RAM and video RAM on PCI)? If yes, where does that happen? If no,
can you please clarify?
(At first I thought you meant an instruction where the opcode crosses those
two memory types, but we don't put code in video RAM...)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply
* Re: separation of sysctl and tcp-window-tracking patch?
From: James Ralston @ 2002-12-13 8:58 UTC (permalink / raw)
To: netfilter-devel
In-Reply-To: <1039702486.2373.17.camel@pc>
On 12 Dec 2002, Brian J. Murrell wrote:
> I had this problem with the Amanda protocol, but it was with the UDP
> streaming timeout. It was not long enough to allow an Amanda client
> to go do it's work and still respond to the server when it was done.
>
> Fortunately (for this situation), the Amanda protocol requires a
> helper, so I just upped the timeout on the connection in the helper.
> But this led me to think about UDP timeouts in general.
Well, the best way to solve this particular problem for DNS traffic
would be to use a helper. Have the helper use a table to track the
state of DNS queries and replies via the 16-bit identifiers. That
way, a DNS response that took more than 30 seconds could still be
permitted as RELATED traffic, by matching the ID of reply to the ID of
the query.
> # insmod ip_conntrack.o udp_timeouts="53=60,123=10"
>
> [...]
>
> This could be done via proc too however. Maybe something like:
>
> # cat /proc/sys/net/ipv4/netfilter/udp_timeout
> default=30
> 53=60
> 123=10
>
> [...]
>
> Of course we have two udp timeouts to deal with, initial UDP
> connection setup timeout and the UDP streaming timeout. Perhaps two
> different /proc nodes.
While this will work, I suspect that a fair number of protocols could
be adequately supported by using helpers.
Failing a helper, I'm unable to come up with anything better than
adjusting timeouts on a per-port basis...
--
James Ralston, Information Technology
Software Engineering Institute
Carnegie Mellon University, Pittsburgh, PA, USA
^ permalink raw reply
* Query.... redirecting traffic
From: Paul Gibson @ 2002-12-13 9:02 UTC (permalink / raw)
To: netfilter
In-Reply-To: <000601c2a23f$619ffef0$0100a8c0@zultys.com>
Hello,
I am wondering if netfilter can do the following.....
http connection comes in on 10.10.10.10 port 80, can iptables then redirect
this to go to 192.168.1.1 port 12345 & also allow the returning data to go
back the opposite way ???
We are currently using "redir" to do it and are having some porblems with it
due to an application we run.
TIA
Paul.
^ permalink raw reply
* Re: 486 laptop apm problems
From: Felix Triebel @ 2002-12-13 9:12 UTC (permalink / raw)
To: John Bradford; +Cc: linux-kernel
In-Reply-To: <200212091350.gB9DouN1000766@darkstar.example.net>
[-- Attachment #1: Type: text/plain, Size: 3155 bytes --]
On Mon, Dec 09, 2002 at 01:50:56PM +0000, John Bradford wrote:
> > why does apmd frequently crash?
> > what do all these ide and apm messages mean?
> > how should I use such an old apm bios?
>
> The IDE messages are warning messages, not critical errors - you can
> ignore them.
>
> Please run the oops through ksymoops and post the output.
sorry for the delay, but this thing is SLOW and there was some work
after it had a hard drive head crash. By the way - does ide taskfile
access correct problems silently or give me a message?
here is the requested ksymoops output, I hope it is useful:
--------------------------------------------------------------------------
ksymoops 2.4.5 on i486 2.4.20-rc4-ac1. Options used
-V (specified)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o lib/modules/2.4.20-rc4-ac1/ (specified)
-m System.map-ac (specified)
CPU: 486
Unable to handle kernel NULL pointer dereference at virtual address 000000d8
c011dd5f
*pde = 00000000
Oops: 0000
CPU: 0
EIP: 0010:[<c011dd5f>] Not tainted
Using defaults from ksymoops -t elf32-i386 -a i386
EFLAGS: 00010246
eax: c1030080 ebx: c101f320 ecx: 00000400 edx: 00000000
esi: c0999000 edi: c10731e8 ebp: c1030080 esp: c0a97ed0
ds: 0018 es: 0018 ss: 0018
Process 00hwclock (pid: 759, stackpage=c0a97000)
Stack: c10731cc c10731cc c10731e8 080c1078 c011dee3 c10731cc c0ebeebc 080c1078
00000001 c0db5304 c10731cc 080c1078 c10731e8 c0ebeebc c0b6e080 c010cdf7
c10731cc c0ebeebc 080c1078 00000001 c0a96000 ffff0006 c010cce0 bffffbec
Call Trace: [<c011dee3>] [<c010cdf7>] [<c010cce0>] [<c0117c49>] [<c0114a0a>]
[<c0114936>] [<c010e03d>] [<c0106d34>]
Code: 2b 82 d8 00 00 00 69 c0 c5 4e ec c4 c1 f8 02 c1 e0 0c 03 82
>>EIP; c011dd5f <do_no_page+ef/190> <=====
>>eax; c1030080 <_end+e1a454/1dea3d4>
>>ebx; c101f320 <_end+e096f4/1dea3d4>
>>esi; c0999000 <_end+7833d4/1dea3d4>
>>edi; c10731e8 <_end+e5d5bc/1dea3d4>
>>ebp; c1030080 <_end+e1a454/1dea3d4>
>>esp; c0a97ed0 <_end+8822a4/1dea3d4>
Trace; c011dee3 <handle_mm_fault+e3/160>
Trace; c010cdf7 <do_page_fault+117/434>
Trace; c010cce0 <do_page_fault+0/434>
Trace; c0117c49 <process_timeout+9/10>
Trace; c0114a0a <bh_action+1a/50>
Trace; c0114936 <tasklet_hi_action+46/70>
Trace; c010e03d <schedule+20d/230>
Trace; c0106d34 <error_code+34/40>
Code; c011dd5f <do_no_page+ef/190>
00000000 <_EIP>:
Code; c011dd5f <do_no_page+ef/190> <=====
0: 2b 82 d8 00 00 00 sub 0xd8(%edx),%eax <=====
Code; c011dd65 <do_no_page+f5/190>
6: 69 c0 c5 4e ec c4 imul $0xc4ec4ec5,%eax,%eax
Code; c011dd6b <do_no_page+fb/190>
c: c1 f8 02 sar $0x2,%eax
Code; c011dd6e <do_no_page+fe/190>
f: c1 e0 0c shl $0xc,%eax
Code; c011dd71 <do_no_page+101/190>
12: 03 82 00 00 00 00 add 0x0(%edx),%eax
--------------------------------------------------------------------------
regards,
Felix
--
/"\ ASCII RIBBON CAMPAIGN
\ / AGAINST HTML MAIL
X AND POSTINGS :)
/ \ http://www.dcoul.de/
[-- Attachment #2: Type: application/pgp-signature, Size: 155 bytes --]
^ permalink raw reply
* another seagate for the black-list?
From: Aryix @ 2002-12-12 10:56 UTC (permalink / raw)
To: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 291 bytes --]
hdparm say: max udma capable 2
the disk is udma5
/root/.gnupg/pubring.gpg
------------------------
pub 1024D/BE8E00BE 2002-12-06 Aryix Berius (nothing.........) <aryix@softhome.net>
Key fingerprint = 249D C5BC 8B9A C46A C7F4 397D 2A6D 9FF6 BE8E 00BE
sub 2048g/C1C6CB29 2002-12-06
[-- Attachment #2: sea --]
[-- Type: application/octet-stream, Size: 20262 bytes --]
kernel-2.4.20
hdparm-v5.2
hdparm -iI /dev/hdc
/dev/hdc:
Model=ST36421A, FwRev=6.01, SerialNo=5BE0EC1N
Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs RotSpdTol>.5% }
RawCHS=13330/15/63, TrkSize=0, SectSize=0, ECCbytes=4
BuffType=unknown, BuffSize=256kB, MaxMultSect=16, MultSect=16
CurCHS=13330/15/63, CurSects=12596850, LBA=yes, LBAsects=12596850
IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
PIO modes: pio0 pio1 pio2 pio3 pio4
DMA modes: mdma0 mdma1 mdma2
UDMA modes: udma0 udma1 udma2
AdvancedPM=no WriteCache=enabled
Drive conforms to: device does not report version: 1 2 3 4
ATA device, with non-removable media
Model Number: ST36421A
Serial Number: 5BE0EC1N
Firmware Revision: 6.01
Standards:
Supported: 4 3 2 1
Likely used: 5
Configuration:
Logical max current
cylinders 13330 13330
heads 15 15
sectors/track 63 63
--
CHS current addressable sectors: 12596850
LBA user addressable sectors: 12596850
device size with M = 1024*1024: 6150 MBytes
device size with M = 1000*1000: 6449 MBytes (6 GB)
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 256.0kB bytes avail on r/w long: 4 Queue depth: 1
Standby timer values: spec'd by Standard
R/W multiple sector transfer: Max = 16 Current = 16
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 *udma3 udma4
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
* Security Mode feature set
* SMART feature set
* DOWNLOAD MICROCODE cmd
Security:
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- below Vih
Device num = 1
lspci -vvv
00:00.0 Host bridge: VIA Technologies, Inc. VT8371 [KX133] (rev 02)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR+
Latency: 0
Region 0: Memory at da000000 (32-bit, prefetchable) [size=32M]
Capabilities: [a0] AGP version 2.0
Status: RQ=31 SBA+ 64bit- FW+ Rate=x1,x2
Command: RQ=0 SBA- AGP+ 64bit- FW- Rate=<none>
00:01.0 PCI bridge: VIA Technologies, Inc. VT8371 [KX133 AGP] (prog-if 00 [Normal decode])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort+ >SERR- <PERR-
Latency: 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000f000-00000fff
Memory behind bridge: d8000000-d9ffffff
Prefetchable memory behind bridge: d0000000-d7ffffff
BridgeCtl: Parity- SERR- NoISA+ VGA+ MAbort- >Reset- FastB2B-
Capabilities: [80] Power Management version 2
Flags: PMEClk- DSI- D1+ D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 21)
Subsystem: VIA Technologies, Inc. VT82C686/A PCI to ISA Bridge
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping+ SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 0
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10) (prog-if 8a [Master SecP PriP])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32
Region 4: I/O ports at d000 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.4 Host bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 30)
Control: I/O- Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin ? routed to IRQ 9
Capabilities: [68] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:07.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller (rev 20)
Subsystem: VIA Technologies, Inc.: Unknown device 4511
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Interrupt: pin C routed to IRQ 12
Region 0: I/O ports at dc00 [size=256]
Region 1: I/O ports at e000 [size=4]
Region 2: I/O ports at e400 [size=4]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139 (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (8000ns min, 16000ns max)
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at e800 [size=256]
Region 1: Memory at dc000000 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00:09.0 SCSI storage controller: Adaptec AHA-7850 (rev 01)
Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
Status: Cap- 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1000ns min, 1000ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at ec00 [disabled] [size=256]
Region 1: Memory at dc001000 (32-bit, non-prefetchable) [size=4K]
01:00.0 VGA compatible controller: nVidia Corporation NV11 (GeForce2 MX) (rev b2) (prog-if 00 [VGA])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop+ ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 248 (1250ns min, 250ns max)
Interrupt: pin A routed to IRQ 10
Region 0: Memory at d8000000 (32-bit, non-prefetchable) [size=16M]
Region 1: Memory at d0000000 (32-bit, prefetchable) [size=128M]
Expansion ROM at <unassigned> [disabled] [size=64K]
Capabilities: [60] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
Capabilities: [44] AGP version 2.0
Status: RQ=31 SBA- 64bit- FW+ Rate=x1,x2
Command: RQ=31 SBA- AGP+ 64bit- FW- Rate=<none>
ksymoops -d
DEBUG (convert_uname): /lib/modules/*r/ in
DEBUG (convert_uname): /lib/modules/2.4.20/ out
DEBUG (convert_uname): /boot/System.map-*r in
DEBUG (convert_uname): /boot/System.map-2.4.20 out
ksymoops 2.4.5 on i686 2.4.20. Options used
-V (default)
-k /proc/ksyms (default)
-l /proc/modules (default)
-o /lib/modules/2.4.20/ (default)
-m /boot/System.map-2.4.20 (default)
Warning: You did not tell me where to find symbol information. I will
assume that the log matches the kernel and modules that are running
right now and I'll use the default options above for symbol resolution.
If the current kernel and/or modules do not match the log, you can get
more accurate output by telling me the kernel version and where to find
map, modules, ksyms etc. ksymoops -h explains the options.
DEBUG (main): level 1
DEBUG (read_env): default KSYMOOPS_NM=/usr/bin/nm
DEBUG (read_env): default KSYMOOPS_FIND=/usr/bin/find
DEBUG (read_env): default KSYMOOPS_OBJDUMP=/usr/bin/objdump
DEBUG (re_compile): '^([0-9a-fA-F]{4,}) +([^ ]) +([^ ]+)( +\[([^ ]+)\])?$' 5 sub expression(s)
DEBUG (re_compile): '^ *\[*<([0-9a-fA-F]{4,})>\]* *' 1 sub expression(s)
DEBUG (re_compile): '^ *<\[([0-9a-fA-F]{4,})\]> *' 1 sub expression(s)
DEBUG (re_compile): '^ *([0-9a-fA-F]{4,}) *' 1 sub expression(s)
DEBUG (read_ksyms): /proc/ksyms
DEBUG (re_compile): '^([0-9a-fA-F]{4,}) +([^ ]+)( +\[([^ ]+)\])?$' 4 sub expression(s)
DEBUG (re_compile): '^(.*)_R.*[0-9a-fA-F]{8,}$' 1 sub expression(s)
DEBUG (re_compile): '^(__insmod_.*)(_O(.*)_M([0-9a-fA-F]+)_V(-?[0-9]+)|_S(.*)_L([0-9]+))' 7 sub expression(s)
DEBUG (ss_sort_na): ipx
DEBUG (ss_sort_na): ext3
DEBUG (ss_sort_na): jbd
DEBUG (ss_sort_na): NVdriver
DEBUG (ss_sort_na): sg
DEBUG (ss_sort_na): 8139too
DEBUG (ss_sort_na): mii
DEBUG (ss_sort_na): via82cxxx_audio
DEBUG (ss_sort_na): uart401
DEBUG (ss_sort_na): ac97_codec
DEBUG (ss_sort_na): sound
DEBUG (ss_sort_na): sd_mod
DEBUG (ss_sort_na): sr_mod
DEBUG (ss_sort_na): aic7xxx
DEBUG (ss_sort_na): scsi_mod
DEBUG (ss_sort_na): ksyms_base
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/net/ipx/ipx.o for ipx
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/fs/ext3/ext3.o for ext3
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/fs/jbd/jbd.o for jbd
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/video/NVdriver for NVdriver
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/scsi/sg.o for sg
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/net/8139too.o for 8139too
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/net/mii.o for mii
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/sound/via82cxxx_audio.o for via82cxxx_audio
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/sound/uart401.o for uart401
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/sound/ac97_codec.o for ac97_codec
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/sound/sound.o for sound
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/scsi/sd_mod.o for sd_mod
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/scsi/sr_mod.o for sr_mod
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/scsi/aic7xxx/aic7xxx.o for aic7xxx
DEBUG (expand_objects): using /lib/modules/2.4.20/kernel/drivers/scsi/scsi_mod.o for scsi_mod
DEBUG (expand_objects): all ksyms modules map to specific object files
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/net/ipx/ipx.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/fs/ext3/ext3.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/fs/jbd/jbd.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/video/NVdriver
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/scsi/sg.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/net/8139too.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/net/mii.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/sound/via82cxxx_audio.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/sound/uart401.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/sound/ac97_codec.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/sound/sound.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/scsi/sd_mod.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/scsi/sr_mod.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/scsi/aic7xxx/aic7xxx.o
DEBUG (ss_sort_na): /lib/modules/2.4.20/kernel/drivers/scsi/scsi_mod.o
DEBUG (read_lsmod): /proc/modules
DEBUG (re_compile): '^ *([^ ]+) *([^ ]+) *([^ ]+) *(.*)$' 4 sub expression(s)
DEBUG (ss_sort_na): lsmod
DEBUG (read_system_map): /boot/System.map-2.4.20
DEBUG (ss_sort_na): System.map
DEBUG (merge_maps):
DEBUG (ss_sort_na): System.map
DEBUG (ss_sort_na): Version_
DEBUG (compare_Version): Version 2.4.20
DEBUG (map_ksyms_to_modules): ksyms ipx matches to /lib/modules/2.4.20/kernel/net/ipx/ipx.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms ext3 matches to /lib/modules/2.4.20/kernel/fs/ext3/ext3.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms jbd matches to /lib/modules/2.4.20/kernel/fs/jbd/jbd.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms NVdriver matches to /lib/modules/2.4.20/kernel/drivers/video/NVdriver based on modutils assist
Warning (compare_maps): mismatch on symbol __nvsym03120 , NVdriver says d0a4f3a0, /lib/modules/2.4.20/kernel/drivers/video/NVdriver says d0975000. Ignoring /lib/modules/2.4.20/kernel/drivers/video/NVdriver entry
DEBUG (map_ksyms_to_modules): ksyms sg matches to /lib/modules/2.4.20/kernel/drivers/scsi/sg.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms 8139too matches to /lib/modules/2.4.20/kernel/drivers/net/8139too.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms mii matches to /lib/modules/2.4.20/kernel/drivers/net/mii.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms via82cxxx_audio matches to /lib/modules/2.4.20/kernel/drivers/sound/via82cxxx_audio.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms uart401 matches to /lib/modules/2.4.20/kernel/drivers/sound/uart401.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms ac97_codec matches to /lib/modules/2.4.20/kernel/drivers/sound/ac97_codec.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms sound matches to /lib/modules/2.4.20/kernel/drivers/sound/sound.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms sd_mod matches to /lib/modules/2.4.20/kernel/drivers/scsi/sd_mod.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms sr_mod matches to /lib/modules/2.4.20/kernel/drivers/scsi/sr_mod.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms aic7xxx matches to /lib/modules/2.4.20/kernel/drivers/scsi/aic7xxx/aic7xxx.o based on modutils assist
DEBUG (map_ksyms_to_modules): ksyms scsi_mod matches to /lib/modules/2.4.20/kernel/drivers/scsi/scsi_mod.o based on modutils assist
DEBUG (ss_sort_atn): merged
DEBUG (ss_sort_atn): merged
DEBUG (ss_sort_atn): merged
Reading Oops report from the terminal
cat /proc/ide/hdc/*
256
12596850
ide-disk version 1.12
physical 13330/15/63
logical 784/255/63
0c5a 3412 0000 000f 0000 0000 003f 0000
0000 0000 3542 4530 4543 314e 2020 2020
2020 2020 2020 2020 0000 0200 0004 362e
3031 2020 2020 5354 3336 3432 3141 2020
2020 2020 2020 2020 2020 2020 2020 2020
2020 2020 2020 2020 2020 2020 2020 8010
0000 2f00 0000 0200 0200 0007 3412 000f
003f 3672 00c0 0110 3672 00c0 0000 0007
0003 0078 0078 00f0 0078 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
001e 0000 346b 4001 4000 346b 0001 4000
081f 0000 0000 0000 0000 4000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0001 6636 00c1 3672 00c0 2e30 0002 0000
0000 0000 0001 0001 0801 0101 0401 0001
3c24 0001 0001 3cb4 0100 0100 0120 0000
0001 1300 0000 9fe7 0014 0a0c 00e2 9020
0048 0700 0f13 8005 f7ff 80ff 0010 8000
0120 0040 ffff 0001 1901 1e24 0000 0005
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
3850 3932 3330 2d30 3032 2e30 3100 0000
disk
ST36421A
name value min max mode
---- ----- --- --- ----
acoustic 0 0 254 rw
address 0 0 2 rw
bios_cyl 784 0 65535 rw
bios_head 255 0 255 rw
bios_sect 63 0 63 rw
breada_readahead 8 0 255 rw
bswap 0 0 1 r
current_speed 67 0 69 rw
failures 0 0 65535 rw
file_readahead 124 0 16384 rw
ide_scsi 0 0 1 rw
init_speed 12 0 69 rw
io_32bit 1 0 3 rw
keepsettings 0 0 1 rw
lun 0 0 7 rw
max_failures 1 0 65535 rw
max_kb_per_request 128 1 255 rw
multcount 16 0 16 rw
nice1 1 0 1 rw
nowerr 0 0 1 rw
number 2 0 3 rw
pio_mode write-only 0 255 w
slow 0 0 1 rw
unmaskirq 1 0 1 rw
using_dma 1 0 1 rw
wcache 0 0 1 rw
0009 1901 0000 0000 0000 0000 0000 0003
0000 0000 0000 0000 0000 0004 0000 0000
0000 0000 0000 2405 0000 0000 0000 0000
0000 1e07 0000 0000 0000 0000 0000 000a
0000 0000 0000 0000 0000 000c 0000 0000
0000 0000 0000 00c5 0000 0000 0000 0000
0000 00c6 0000 0000 0000 0000 0000 00c7
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 2000
0009 0b01 6400 80fd 000c 0000 0000 0603
6000 0060 0000 0000 0000 1204 6300 b763
0006 0000 0000 1305 5100 cb51 0000 0000
0000 0b07 3200 bd28 eb3a eb00 0002 120a
6400 0045 0000 0000 0000 120c 6200 5b62
0008 0000 0000 12c5 5800 0058 0000 0000
0000 12c6 5800 0058 0000 0000 0000 0ac7
c800 3bc4 0003 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0002 0960 1300
0002 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0404 0404 0404 0404 0004
0000 0000 0000 0100 2dfd 00a4 0101 0000
ba94 0023 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 0000
0000 0000 0000 0000 0000 0000 0000 4200
^ permalink raw reply
* Re: Is this going to be true ?
From: David Schwartz @ 2002-12-13 9:18 UTC (permalink / raw)
To: root; +Cc: linux-kernel
In-Reply-To: <Pine.LNX.3.95.1021211214435.28053A-100000@chaos.analogic.com>
On Wed, 11 Dec 2002 22:16:19 -0500 (EST), Richard B. Johnson wrote:
>I wish to hell it was FUD. I have watched all the Sun Workstations
>at work be replaced with Windows/2000/Professional PCs. I have watched
>all the 'nix programmers leave, replaced by Internet junkies who
>don't (can't) write any code. In spite of the fact that don't actually
>use their machines for any work, about 10 percent out of 600++ are
>down at any one moment, most always to "reload Windows".
I think an idiot can screw up a Linux machine as easily as one can screw up
a Windows machine.
>Just to get this Windows machine up at home, tonight, I had to reconfigure
>the network because it "forgot" everything it knew last night
>about the LAN.
Hmm, IP address, netmask, default router. Maybe nameservers too. Did that
take you more than a minute?
>I use Windows at home only because I compose music
>using Cake-walk and it hasn't been ported to Linux. It is a corrupt,
>defective, dastardly, incredibly obnoxious operating system that
>has no redeeming qualities at all.
What about I/O completion ports? What about operating-system code to
automatically keep the number of running threads close to the number of CPUs?
>Virtually every Windows program
>has horrible bugs that make it barely usable.
This is largely because they're written by one of two types of people:
1) Inexperienced programmers. They're attracted to Windows because it really
is easier to get things up and running. (Of course, this ease is deceptive.
Hence the crappy software.)
2) Experienced UNIX programmers who aren't willing to learn how to do things
right on Windows. An example of this is any Windows application that uses
'select'.
Microsoft has made it easier for people to write software, so more people
do. Since there's more software of all kinds, there's going to be more junk.
90% of anything is crap.
>Even Microsoft Visual
>C/C++ will take down the whole machine when it encounters source files
>that don't have a CR/LF sequence as an end-of-line (accidental Unix LF
>files).
I have used Visual C++ for about 4 years now on a weekly basis at least. The
vast majority of my source files have Unix line endings. I've never had it
take down my machine. In any event, there are things you can do that will
take down a Linux machine. Fix it or don't do that. ;)
>It is the worse programming environment, ever, and I have even
>used a MDS-200 "Green Monster" during my 35 years as an Engineer.
I like joe/make/gcc best myself. But I develop mostly server apps, so a GUI
is just in the way.
>This machine used to have two CPUs. I had to take one out when I
>changed it from a Linux machine to a Windows machine. Two CPUs under
>Windows will trash the file-system so it won't boot if it's been
>up for over an hour.
I've used a dual-CPU Windows 2000 machine as my primary desktop machine
(though mostly to run two rxvt's into a Linux machine.) since Windows 2000
came out. I have not lost a single file. I can't say the same for my Linux
machine which has lost quite a few. (Though none since ext3 became stable and
I started using it.)
>I have reloaded Windows on my two Windows machines
>at least once per week, usually more often than that. My Linux machines
>run until I break them by installing a buggy driver. Even then, I
>can reboot and nothing bad happens to the file-systems.
NTFS has been totally stable for me. I've never heard anyone report any
repeatable problems with it (though I have heard tales of a very small number
of spactacular events). Your experiences don't seem to be common.
My three kids have 98SE and ME machines. They beat the heck out of them.
None of them have ever lost a file that wasn't modified within seconds of a
power loss or crash. (Though they have accidentally installed SpyWare that
has taken me *many* hours to worm out of the OS. *ugh* Linux at least has
sane permissions.)
>Once Windows fails to boot, you can reinstall from a CD/ROM, but
>it won't boot after the reinstall! You need to make Windows "think"
>that the boot disk is new by deleting all partitions before you
>"reinstall" Windows or the new installation won't boot.
Huh? You can do a repair installation of NT or 2000 from the CDROM and it
just works, though you may lose all your security updates and whatnot. I
reinstalled ME in place over a previous installation about two weeks ago and
it just worked.
>Microsoft has trained the "new breed" of Engineer that bugs are
>normal and a natural consequence of using computers. This has
>helped destroy software development as an Engineering endeavor and
>substituted in its place, a developmental crap-game.
Absolutely. I entirely agree with that paragraph. But it says nothing about
the OS. This is very similar to blaming AOL for the condition of USENET. Yes,
they lowered the bar so anyone can post on USENET and as a result there's a
lot of crap there. Does this mean it's bad to make it easy to get online?
Should it be difficult to develop software? So that this way only those who
are really competent can do it?
By the way, just as an off-the-cuff guesstimate, how many bugs do you think
there are in the Linux kernel? Say the latest 2.4 series stable release. If I
order the latest version of RedHat or Slackware, how many bugs would you
estimate are in it, total?
DS
^ permalink raw reply
* via82cxxx probable incorrect detection (urgency=low)........
From: Aryix @ 2002-12-12 11:14 UTC (permalink / raw)
To: linux-kernel
I am Argentino <- i don't speak english, please be patient
Kernel-2.4.20-final
lspci -vvv
00:07.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev 10) (prog-if 8
a [Master SecP PriP])
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort
- <MAbort- >SERR- <PERR-
Latency: 32
Region 4: I/O ports at d000 [size=16]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot
-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
cat /proc/pci
Bus 0, device 7, function 0:
ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 33).
Bus 0, device 7, function 1:
IDE interface: VIA Technologies, Inc. VT82C586B PIPC Bus Master IDE (rev 16).
Master Capable. Latency=32.
I/O at 0xd000 [0xd00f].
dmesg
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 16
VP_IDE: not 100% native mode: will probe irqs later
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx <- is my error?
VP_IDE: VIA vt82c686a (rev 21) IDE UDMA66 controller on pci00:07.1
ide0: BM-DMA at 0xd000-0xd007, BIOS settings: hda:DMA, hdb:pio
ide1: BM-DMA at 0xd008-0xd00f, BIOS settings: hdc:DMA, hdd:DMA
hda: QUANTUM FIREBALLlct20 30, ATA DISK drive
hdc: ST36421A, ATA DISK drive
hdd: ATAPI 44X CDROM, ATAPI CD/DVD-ROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
ide1 at 0x170-0x177,0x376 on irq 15
blk: queue c030a5c4, I/O limit 4095Mb (mask 0xffffffff)
hda: 58633344 sectors (30020 MB) w/418KiB Cache, CHS=3649/255/63, (U)DMA <- ??????????
blk: queue c030a928, I/O limit 4095Mb (mask 0xffffffff)
hdc: 12596850 sectors (6450 MB) w/256KiB Cache, CHS=13330/15/63, UDMA(66) <- this is ok
hdd: ATAPI 40X CD-ROM drive, 128kB Cache, UDMA(33) <- ok!
i have a chip via82c686a (Epox 7-kxa)
at boot time is been detected via82c686a
proc says via82c586b
lspci -vvv no says
the udma capabilities is not work propetly i set manually with "hdparm -m 8 -W 1 -X udma5 /dev/hda"
whats happening here?
--
/root/.gnupg/pubring.gpg
------------------------
pub 1024D/BE8E00BE 2002-12-06 Aryix Berius (nothing.........) <aryix@softhome.net>
Key fingerprint = 249D C5BC 8B9A C46A C7F4 397D 2A6D 9FF6 BE8E 00BE
sub 2048g/C1C6CB29 2002-12-06
^ permalink raw reply
* CRC Error when reading a file?
From: Xu Kegang @ 2002-12-13 9:44 UTC (permalink / raw)
To: linux-mtd
Hi,sir
We met a problem about CRC error when reading a file. It seemed that
it will run smoothly in case of a smaller file ,such as 5k byte. But it will
occur when a bigger file,
such as 800KB. We have used mkfs.jffs2 (Version 1.26, 2.4.18 -rmk3 for arm)
in a big-endian way.
Another question is the size of uesed percent varies when we use "df
" to list every device on system. But we can come to a stable value after
several commands "df".
How can I fix this problem.
Thanks a lot
Tos
Dec 13 2002
^ permalink raw reply
* Re: Intel P6 vs P7 system call performance
From: Terje Eggestad @ 2002-12-13 9:21 UTC (permalink / raw)
To: J.A. Magallon; +Cc: Mark Mielke, H. Peter Anvin, linux-kernel, Dave Jones
In-Reply-To: <20021212205655.GA1658@werewolf.able.es>
On tor, 2002-12-12 at 21:56, J.A. Magallon wrote:
> On 2002.12.12 Mark Mielke wrote:
> >On Thu, Dec 12, 2002 at 10:42:56AM +0100, Terje Eggestad wrote:
> >> On ons, 2002-12-11 at 19:50, H. Peter Anvin wrote:
> >> > Terje Eggestad wrote:
> >> > > PS: rdtsc on P4 is also painfully slow!!!
> >> > Now that's just braindead...
> >> It takes about 11 cycles on athlon, 34 on PII, and a whooping 84 on P4.
> >> For a simple op like that, even 11 is a lot... Really makes you wonder.
> >
> >Some of this discussion is a little bit unfair. My understanding of what
> >Intel has done with the P4, is create an architecture that allows for
> >higher clock rates. Sure the P4 might take 84, vs PII 34, but how many
> >PII 2.4 Ghz machines have you ever seen on the market?
> >
> >Certainly, some of their decisions seem to be a little odd on the surface.
> >
> >That doesn't mean the situation is black and white.
> >
>
> No. The situation is just black. Each day Intel processors are a bigger
> pile of crap and less intelligent, but MHz compensate for the average
> office user. Think of what could a P4 do if the same effort put on
> Hz was put on getting cheap a cache of 4Mb or 8Mb like MIPSes have. Or
> closer, 1Mb like G4s.
> If syscalls take 300% time but processor is also 300% faster 'nobody
> notices'.
Well, it does make sense if Intel optimized away rdtsc for more commonly
used things, but even that don't seem to be the case. I'm measuring the
overhead of doing a syscall on Linux (int 80) to be ~280 cycles on PIII,
and Athlon, while it's 1600 cycles on P4.
TJ
--
_________________________________________________________________________
Terje Eggestad mailto:terje.eggestad@scali.no
Scali Scalable Linux Systems http://www.scali.com
Olaf Helsets Vei 6 tel: +47 22 62 89 61 (OFFICE)
P.O.Box 150, Oppsal +47 975 31 574 (MOBILE)
N-0619 Oslo fax: +47 22 62 89 51
NORWAY
_________________________________________________________________________
^ permalink raw reply
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.