Menu
▾
▴
linux-apus-devel
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(210) |
Jun
(169) |
Jul
(167) |
Aug
(128) |
Sep
(218) |
Oct
(120) |
Nov
(86) |
Dec
(71) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(91) |
Feb
(179) |
Mar
(52) |
Apr
(56) |
May
(183) |
Jun
(62) |
Jul
(63) |
Aug
(49) |
Sep
(36) |
Oct
(35) |
Nov
(72) |
Dec
(30) |
| 2002 |
Jan
(53) |
Feb
(61) |
Mar
(56) |
Apr
(13) |
May
(1) |
Jun
(7) |
Jul
(80) |
Aug
(73) |
Sep
(30) |
Oct
(29) |
Nov
(8) |
Dec
(40) |
| 2003 |
Jan
(10) |
Feb
(2) |
Mar
(4) |
Apr
(9) |
May
(3) |
Jun
(19) |
Jul
(64) |
Aug
(53) |
Sep
(28) |
Oct
(7) |
Nov
(3) |
Dec
(21) |
| 2004 |
Jan
(11) |
Feb
(30) |
Mar
(18) |
Apr
(1) |
May
(13) |
Jun
(18) |
Jul
(13) |
Aug
|
Sep
(9) |
Oct
(5) |
Nov
|
Dec
|
| 2005 |
Jan
(1) |
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(10) |
Aug
(21) |
Sep
(7) |
Oct
(10) |
Nov
(6) |
Dec
|
| 2006 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(2) |
Aug
(2) |
Sep
(6) |
Oct
(10) |
Nov
(8) |
Dec
(3) |
| 2007 |
Jan
(3) |
Feb
(6) |
Mar
(1) |
Apr
(6) |
May
(10) |
Jun
(7) |
Jul
(13) |
Aug
(8) |
Sep
|
Oct
(2) |
Nov
|
Dec
|
|
From: Glenn H. <gh...@c2...> - 2001-02-12 10:13:39
|
Michel Dänzer wrote: > > Glenn Hisdal wrote: > > > >> The glint driver for XFree86 runs fine. There is no corruption on the > > >> console after exiting X like it was in 2.4.0-test10. > > > > > So everything is fine now basically? :) > > > > Maybe. Exiting X quite often hangs the system completely. > > I don't know if that's our fault or an error in the glint driver. > > I haven't had any crashes when I only use FBDev, but maybe that's just luck > > as I use glint most of the time... > > Also: the color in console sometimes is wrong after exiting X. > > Switching consoles brings it back to normal. > > Is this all with the UseFBDev option? Yes. without UseFBDev the display in X is messed up iirc. I don't remember exactly. I'll have to check later. > > > >> PCI: Resource ef000000-ef01ffff (f=200, d=0, p=0) > > >> PCI: Cannot allocate resource region 0 of device 00:01.0 > > >> PCI: Resource e0000000-e07fffff (f=200, d=0, p=0) > > >> PCI: Cannot allocate resource region 1 of device 00:01.0 > > >> PCI: Resource e1000000-e17fffff (f=200, d=0, p=0) > > >> PCI: Cannot allocate resource region 2 of device 00:01.0 > > > > I have managed to remove these errors. > > I'll try to make a diff... > > > > basically I added the line > > bus->resource[1] = &pci_mem; > > to the end of apus_pcibios_fixup_bus(...) > > (as done in chrp_pci.c) > > D'oh! That was actually the point of my change, but I had it in the printk and > accidentally removed it. Good catch! thanks :-) - glenn |
|
From: Alan B. <al...@ms...> - 2001-02-12 10:01:17
|
hi, > sorry. Have to correct myself ! > /proc/pci is NOT empty. I thought it was a directory, but when I looked > closer, it was a file (ooops). > > contents of /proc/pci : > > PCI devices found: > Bus 0, device 1, function 0: > Display controller: Texas Instruments TVP4020 [Permedia 2] (rev 1). > Master Capable. Latency=255. Min Gnt=192.Max Lat=192. > Non-prefetchable 32 bit memory at 0x10000000 [0x1001ffff]. > Non-prefetchable 32 bit memory at 0x11000000 [0x11ffffff]. > Non-prefetchable 32 bit memory at 0x10800000 [0x10ffffff]. > Prefetchable 64 bit memory at 0x3d071040 [0x3d07107f]. excellent. whats the output of 'lspci' ? alan |
|
From: Michel <da...@re...> - 2001-02-12 09:59:31
|
Glenn Hisdal wrote: > >> The glint driver for XFree86 runs fine. There is no corruption on th= e > >> console after exiting X like it was in 2.4.0-test10. >=20 > > So everything is fine now basically? :) >=20 > Maybe. Exiting X quite often hangs the system completely. > I don't know if that's our fault or an error in the glint driver. > I haven't had any crashes when I only use FBDev, but maybe that's just = luck > as I use glint most of the time... > Also: the color in console sometimes is wrong after exiting X. > Switching consoles brings it back to normal. Is this all with the UseFBDev option? > >> PCI: Resource ef000000-ef01ffff (f=3D200, d=3D0, p=3D0) > >> PCI: Cannot allocate resource region 0 of device 00:01.0 > >> PCI: Resource e0000000-e07fffff (f=3D200, d=3D0, p=3D0) > >> PCI: Cannot allocate resource region 1 of device 00:01.0 > >> PCI: Resource e1000000-e17fffff (f=3D200, d=3D0, p=3D0) > >> PCI: Cannot allocate resource region 2 of device 00:01.0 >=20 > I have managed to remove these errors. > I'll try to make a diff... >=20 > basically I added the line > bus->resource[1] =3D &pci_mem; > to the end of apus_pcibios_fixup_bus(...) > (as done in chrp_pci.c) D'oh! That was actually the point of my change, but I had it in the print= k and accidentally removed it. Good catch! --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Alan B. <al...@ms...> - 2001-02-12 09:49:29
|
hi, > > BTW have you enabled the additional debugging code as suggested by Geert? > > ooops. I forgot to enable debug in drivers/pci/pci.c > When I enable debug there, the kernel panics rigth after startup > dmesg output: sounds familiar > Bus scan for 00 returning with max=00 > Zorro: Probing AutoConfig expansion devices: 3 devices > Oops: kernel access of bad area, sig: 11 > NIP: C00177DC XER: 00000000 LR: C001786C SP: C01C9ED0 REGS: c01c9e20 TRAP: 0300 > MSR: 00009072 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 > DAR: 00009076, DSISR: 40000000 > TASK = c01c8000[1] 'swapper' Last syscall: -1 > last math 00000000 last altivec 00000000 > GPR00: 01000000 C01C9ED0 C01C8000 00009072 C0134134 00000001 801E069E 00000000 > GPR08: FF000000 C01C9BCC FFFFFFFF C012C85C 44848024 08171B74 0807E0CC 3C8AB800 > GPR16: 0928F000 0000004C 00000000 00000000 003FF000 FFFFFD6C 0000001D 08910000 > GPR24: 08910000 00000000 C0170000 C0140000 C0170000 00000002 C0130000 C0134134 > Call backtrace: > 00007F00 C014ABC0 C013F834 C00039F0 C0006438 > Kernel panic: Attempted to kill init! > Rebooting in 180 seconds..<<<<<<<<<<<<<<<<<<<< nah, slightly different place...its still the 'swapper' that crashes though. In my case, its a 2.4 kernel with different options enabled (to get 'user-ready' 2.4 kernel the same config as the 2.2.10 kernel. I've started to disable bits and pieces. I was just going to get the module from sourceforge and compare the two configs...and then isolate which option causes the kernel to oooops on startup :-| alan |
|
From: Michel <da...@re...> - 2001-02-12 09:46:33
|
Robert Ramiega wrote: >=20 > On Mon, Feb 12, 2001 at 10:37:58AM +0100, Michel D=E4nzer wrote: > > Robert Ramiega wrote: > > > > > Machine check in kernel mode. > > > Caused by (from SRR1=3D49070): Transfer error ack signal > > [...] > > > CONFIG_FB_PM2_PCI=3Dy > > > > Disable this. > I just noticed that i had it also enabled 2.4.0 that i'm running now..= . I > guess this didn't show up until Glenn fixed PCI =3Do)) Right, the generic PCI code in pm2fb only comes in when PCI support works= . ;) --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Robert R. <ro...@pl...> - 2001-02-12 09:41:29
|
On Mon, Feb 12, 2001 at 10:37:58AM +0100, Michel Dänzer wrote: > Robert Ramiega wrote: > > > Machine check in kernel mode. > > Caused by (from SRR1=49070): Transfer error ack signal > [...] > > CONFIG_FB_PM2_PCI=y > > Disable this. I just noticed that i had it also enabled 2.4.0 that i'm running now... I guess this didn't show up until Glenn fixed PCI =o)) I'm already recompiling kernel with this option disabled. Thanks! -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Michel <da...@re...> - 2001-02-12 09:38:07
|
Robert Ramiega wrote: > Machine check in kernel mode. > Caused by (from SRR1=3D49070): Transfer error ack signal [...] > CONFIG_FB_PM2_PCI=3Dy Disable this. Dunno if it's a bug in pm2fb or our PCI code or whatever. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Robert R. <ro...@pl...> - 2001-02-12 09:31:15
|
Hi! I just tried to boot 2.4.1 with both fixes of Glen (the one with bus->resource i;ve added before printk but i don't think it matters). Anyway i failed to boot. There wasn't even anyoutput (except for the bootstrap). I've started it with bootstrap --apus -k vmapus-2.4.1 root=/dev/hda3 video=pm2fb:mode:1024x768-90 video=amifb:off nobats 60nsram My config: A1200, PPC603@160MHz, 64 MB RAM, Ariadne, BVision PPC Here is dmesg output: Searching for SAVEKMSG magic... Found 6546 bytes at 0x001e0010 >>>>>>>>>>>>>>>>>>>> Total memory = 63MB; using 0kB for hash table (at 00000000) Linux version 2.4.1 (ro...@yo...) (gcc version 2.95.2 20000220 (Debian GNU/Linux)) #2 nie lut 11 23:10:31 CET 2001 Amiga hardware found: [A1200] VIDEO BLITTER AUDIO FLOPPY A1200_IDE KEYBOARD MOUSE SERIAL PARALLEL A2000_CLK CHIP_RAM PAULA LISA ALICE_PAL PCMCIA ZORRO On node 0 totalpages: 16256 zone(0): 16256 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda3 debug debug=mem video=pm2fb:1024x768-90 video=amifb:off nobats 60nsram apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. amiga_enable_irq: Trying to enable auto-vector IRQ 1 amiga_enable_irq: Trying to enable auto-vector IRQ 3 amiga_enable_irq: Trying to enable auto-vector IRQ 4 amiga_enable_irq: Trying to enable auto-vector IRQ 5 amiga_enable_irq: Trying to enable auto-vector IRQ 7 amiga_enable_irq: Trying to enable auto-vector IRQ 2 amiga_enable_irq: Trying to enable auto-vector IRQ 6 APUS: BATs=0, BUS=67MHz, RAM=60ns, PCI bridge=1 time_init: decrementer frequency = 16.670731 MHz Console: colour dummy device 80x25 Calibrating delay loop... 111.00 BogoMIPS Memory: 62160k available (1016k kernel code, 468k data, 212k init, 0k highmem) Dentry-cache hash table entries: 8192 (order: 4, 65536 bytes) Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes) Page-cache hash table entries: 16384 (order: 4, 65536 bytes) Inode-cache hash table entries: 4096 (order: 3, 32768 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware apus_pci: apus_pcibios_read_config_byte: readbb: 0x0, d: 0x1, f: 0x0, o: 0xe, v: 0x0 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x0, v: 0x3d07104c apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x8, v: 0x3800001 apus_pci: apus_pcibios_read_config_byte: readbb: 0x0, d: 0x1, f: 0x0, o: 0x3d, v: 0x1 apus_pci: apus_pcibios_read_config_byte: readbb: 0x0, d: 0x1, f: 0x0, o: 0x3c, v: 0x0 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0xef000000 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0xffffffff apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0xfffe0000 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0xef000000 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xe0000000 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xffffffff apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xff800000 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xe0000000 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0xe1000000 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0xffffffff apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0xff800000 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0xe1000000 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x1c, v: 0x0 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x1c, v: 0xffffffff apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x1c, v: 0x0 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x1c, v: 0x0 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x20, v: 0x0 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x20, v: 0xffffffff apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x20, v: 0x0 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x20, v: 0x0 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x24, v: 0x0 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x24, v: 0xffffffff apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x24, v: 0x0 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x24, v: 0x0 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xe2000001 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xfffffffe apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xffff0000 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xe2000001 apus_pci: apus_pcibios_read_config_word: readwb: 0x0, d: 0x1, f: 0x0, o: 0x2c, v: 0x2424 apus_pci: apus_pcibios_read_config_word: readwb: 0x0, d: 0x1, f: 0x0, o: 0x2e, v: 0x2424 Fixup mem res, dev: 0.1, res_start: ef000000->ef000000 Fixup mem res, dev: 0.1, res_start: e0000000->e0000000 Fixup mem res, dev: 0.1, res_start: e1000000->e1000000 Fixup mem res, dev: 0.1, res_start: e2000000->e2000000 apus_pcibios_fixup_bus: PCI mem resource requested apus_pci: apus_pcibios_read_config_word: readwb: 0x0, d: 0x1, f: 0x0, o: 0x4, v: 0x6 PCI: Resource ef000000-ef01ffff (f=200, d=0, p=0) PCI: Resource e0000000-e07fffff (f=200, d=0, p=0) PCI: Resource e1000000-e17fffff (f=200, d=0, p=0) PCI: Switching off ROM of 00:01.0 apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xe2000001 apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xe2000000 apus_pci: apus_pcibios_read_config_word: readwb: 0x0, d: 0x1, f: 0x0, o: 0x4, v: 0x6 Zorro: Probing AutoConfig expansion devices: 2 devices Linux NET4.0 for Linux 2.4 Based upon Swansea University Computer Society NET3.039 Starting kswapd v1.8 Machine check in kernel mode. Caused by (from SRR1=49070): Transfer error ack signal Oops: machine check, sig: 7 NIP: C00B1C40 XER: 00000000 LR: C014B4E4 SP: C02E3E70 REGS: c02e3dc0 TRAP: 0200 MSR: 00049070 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 TASK = c02e2000[1] 'swapper' Last syscall: 120 last math 00000000 last altivec 00000000 GPR00: 5529103A C02E3E70 C02E2000 C018F8A4 C4810000 000003AD 00000000 00000010 GPR08: 00000C48 C4801000 C02C8E60 00000000 C0122C48 76171434 76081EC4 3C8A4A00 GPR16: 10101010 11111111 12121212 13131313 003FF000 763569CC FFFFFD6C 7601A6C0 GPR24: FFFFFD3C FFFFFFFF FFFFFD2A 00000018 FFFFFFEF C0170000 C0134058 C018F8A4 Call backtrace: C0170000 C014B4E4 C01496F0 C01457E4 C0143FF0 C0142B50 C013D7EC C013D894 C00039F0 C0006438 Kernel panic: Attempted to kill init! Rebooting in 180 seconds..<<<<<<<<<<<<<<<<<<<< Kernel config is basicaly the same as with 2.4.0 i'm running now. Here are the PCI and PM2 settings: CONFIG_PCI=y CONFIG_PCI_NAMES=y # CONFIG_BLK_DEV_IDEPCI is not set # CONFIG_DMA_NONPCI is not set # CONFIG_NET_PCI is not set # CONFIG_RCPCI is not set CONFIG_FB_PM2_PCI=y # CONFIG_SOUND_CMPCI is not set CONFIG_FB_PM2=y # CONFIG_FB_PM2_FIFO_DISCONNECT is not set CONFIG_FB_PM2_PCI=y CONFIG_FB_PM2_CVPPC=y Can 'Generic Permedia2 PCI support' interfere in anyway? -- Robert Ramiega | ro...@pl... IRC: _Jedi_ | Don't underestimate UIN: 13201047 | http://www.plukwa.net/ | the power of Source |
|
From: Geert U. <ge...@li...> - 2001-02-12 08:08:03
|
On Sat, 10 Feb 2001, Glenn Hisdal wrote:
> PCI: Resource ef000000-ef01ffff (f=200, d=0, p=0)
> PCI: Cannot allocate resource region 0 of device 00:01.0
> PCI: Resource e0000000-e07fffff (f=200, d=0, p=0)
> PCI: Cannot allocate resource region 1 of device 00:01.0
> PCI: Resource e1000000-e17fffff (f=200, d=0, p=0)
> PCI: Cannot allocate resource region 2 of device 00:01.0
This usually means that those regions are not inside the bus resource regions
(or the bus doesn't have any bus resources filled in).
> PCI: Error while updating region 00:01.0/1 (10800000 != e1000000)
> got res[10800000:10ffffff] for resource 1 of Texas Instruments TVP4020 [Permedia 2]
> apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0x11000000
> apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0x11000000
> got res[11000000:117fffff] for resource 2 of Texas Instruments TVP4020 [Permedia 2]
And thus the PCI assignment code tries to assign new regions from the bus
resource, or from pci_mem if the bus resources are empty (it looks like they
are empty, 0x10000000 is the default start of pci mem).
I guess the errors come from the hardcoded CyberVision PCI bridge?
On Sun, 11 Feb 2001, Glenn Hisdal wrote:
> On 11-Feb-01, Glenn wrote:
> > On 11-Feb-01, Michel wrote:
> >> Glenn Hisdal wrote:
>
> >>> PCI: Resource ef000000-ef01ffff (f=200, d=0, p=0)
> >>> PCI: Cannot allocate resource region 0 of device 00:01.0
> >>> PCI: Resource e0000000-e07fffff (f=200, d=0, p=0)
> >>> PCI: Cannot allocate resource region 1 of device 00:01.0
> >>> PCI: Resource e1000000-e17fffff (f=200, d=0, p=0)
> >>> PCI: Cannot allocate resource region 2 of device 00:01.0
>
> > I have managed to remove these errors.
> > I'll try to make a diff...
>
> ok. there should be a diff attached to this mail (i hope).
> I don't know if it's any good, but it stopped complaining about the resource
> allocation.
> I just did a little cut and paste from chrp_pci.c
>
> - glenn
>
> Index: 2.3/arch/ppc/kernel/apus_pci.c
> ===================================================================
> RCS file: /cvsroot/linux-apus/2.3/arch/ppc/kernel/apus_pci.c,v
> retrieving revision 1.6
> diff -r1.6 apus_pci.c
> 106a107
> > static struct resource pci_mem = { "B/CVisionPPC PCI mem", CVPPC_FB_APERTURE_ONE, CVPPC_PCI_CONFIG, IORESOURCE_MEM };
> 115a117,119
> >
> > request_resource(&iomem_resource, &pci_mem);
> > printk("%s: PCI mem resource requested\n", __FUNCTION__);
> 120,123c124
> < struct resource pci_mem = { "B/CVisionPPC PCI mem", CVPPC_FB_APERTURE_ONE, CVPPC_PCI_CONFIG, IORESOURCE_MEM };
> <
> < request_resource(&iomem_resource, &pci_mem);
> < printk("%s: PCI mem resource requested\n", __FUNCTION__);
> ---
> > bus->resource[1] = &pci_mem;
This looks fine to me. BTW, please use `diff -u' next time (or add the line
diff -u
to your ~/.cvsrc to make it the default).
Now please install pciutils and post the output of `lspci -vv'. Thx!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
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
|
|
From: Geert U. <ge...@li...> - 2001-02-12 07:51:40
|
On Fri, 9 Feb 2001 no...@so... wrote:
> Summary: Catweasel MKII (Budha) IDE Controller hangs with 2.4.0
So it's not APUS specific. Christian Steigies reported this on Linux/m68k as
well.
Sorry, I don't have the hardware :-(
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
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
|
|
From: Glenn H. <gh...@c2...> - 2001-02-11 22:48:47
|
On 11-Feb-01, Glenn wrote: > On 11-Feb-01, Michel wrote: >> Glenn Hisdal wrote: >>> PCI: Resource ef000000-ef01ffff (f=200, d=0, p=0) >>> PCI: Cannot allocate resource region 0 of device 00:01.0 >>> PCI: Resource e0000000-e07fffff (f=200, d=0, p=0) >>> PCI: Cannot allocate resource region 1 of device 00:01.0 >>> PCI: Resource e1000000-e17fffff (f=200, d=0, p=0) >>> PCI: Cannot allocate resource region 2 of device 00:01.0 > I have managed to remove these errors. > I'll try to make a diff... ok. there should be a diff attached to this mail (i hope). I don't know if it's any good, but it stopped complaining about the resource allocation. I just did a little cut and paste from chrp_pci.c - glenn |
|
From: Glenn H. <gh...@c2...> - 2001-02-11 20:00:14
|
On 11-Feb-01, Michel wrote:
> Glenn Hisdal wrote:
>> I found an error in apus_pci.c
> Thanks for the fix! (Next time please provide a diff (cvs does it) instead
> of just the fixed code, that makes it easier for us to spot the changes)
ok. I'll try to do that.
How does diff work ?
I don't know the correct options to create a diff file...
>> The glint driver for XFree86 runs fine. There is no corruption on the
>> console after exiting X like it was in 2.4.0-test10.
> So everything is fine now basically? :)
Maybe. Exiting X quite often hangs the system completely.
I don't know if that's our fault or an error in the glint driver.
I haven't had any crashes when I only use FBDev, but maybe that's just luck
as I use glint most of the time...
Also: the color in console sometimes is wrong after exiting X.
Switching consoles brings it back to normal.
>> PCI: Calling quirk c000b8f0 for 00:01.0
> Do you have PCI quirks enabled in your .config?
???
I can't find any option for that...
>> PCI: Resource ef000000-ef01ffff (f=200, d=0, p=0)
>> PCI: Cannot allocate resource region 0 of device 00:01.0
>> PCI: Resource e0000000-e07fffff (f=200, d=0, p=0)
>> PCI: Cannot allocate resource region 1 of device 00:01.0
>> PCI: Resource e1000000-e17fffff (f=200, d=0, p=0)
>> PCI: Cannot allocate resource region 2 of device 00:01.0
I have managed to remove these errors.
I'll try to make a diff...
basically I added the line
bus->resource[1] = &pci_mem;
to the end of apus_pcibios_fixup_bus(...)
(as done in chrp_pci.c)
I also moved the request_resource code that you added up to
apus_pcibios_fixup() to make it look more similar to chrp_pci.c, but that
wasn't really needed, I guess.
>> PCI devices found:
>> Bus 0, device 1, function 0:
>> Display controller: Texas Instruments TVP4020 [Permedia 2] (rev 1).
>> Master Capable. Latency=255. Min Gnt=192.Max Lat=192.
>> Non-prefetchable 32 bit memory at 0x10000000 [0x1001ffff].
>> Non-prefetchable 32 bit memory at 0x11000000 [0x11ffffff].
>> Non-prefetchable 32 bit memory at 0x10800000 [0x10ffffff].
>> Prefetchable 64 bit memory at 0x3d071040 [0x3d07107f].
> The last line here looks suspicious to me ('prefetchable 64 bit memory'?).
Yes, don't know where it came from. It's not there anymore...
- glenn
|
|
From: Michel <mic...@ii...> - 2001-02-11 19:23:30
|
Glenn Hisdal wrote:
> I found an error in apus_pci.c
Thanks for the fix! (Next time please provide a diff (cvs does it) instea=
d of
just the fixed code, that makes it easier for us to spot the changes)
> The glint driver for XFree86 runs fine. There is no corruption on the
> console after exiting X like it was in 2.4.0-test10.
So everything is fine now basically? :)
> PCI: Calling quirk c000b8f0 for 00:01.0
Do you have PCI quirks enabled in your .config?
> Fixup mem res, dev: 0.1, res_start: ef000000->ef000000
> Fixup mem res, dev: 0.1, res_start: e0000000->e0000000
> Fixup mem res, dev: 0.1, res_start: e1000000->e1000000
> Fixup mem res, dev: 0.1, res_start: e2000000->e2000000
[...]
> PCI: Resource ef000000-ef01ffff (f=3D200, d=3D0, p=3D0)
> PCI: Cannot allocate resource region 0 of device 00:01.0
> PCI: Resource e0000000-e07fffff (f=3D200, d=3D0, p=3D0)
> PCI: Cannot allocate resource region 1 of device 00:01.0
> PCI: Resource e1000000-e17fffff (f=3D200, d=3D0, p=3D0)
> PCI: Cannot allocate resource region 2 of device 00:01.0
> PCI: Switching off ROM of 00:01.0
[...]
> got res[10000000:1001ffff] for resource 0 of Texas Instruments TVP402=
0
> [Permedia 2]
[...]
> PCI: Error while updating region 00:01.0/1 (10800000 !=3D e1000000)
> got res[10800000:10ffffff] for resource 1 of Texas Instruments TVP402=
0
> [Permedia 2]
[...]
> got res[11000000:117fffff] for resource 2 of Texas Instruments TVP402=
0
> [Permedia 2]
Geert, what does this all mean and does it look good?
> PCI devices found:
> Bus 0, device 1, function 0:
> Display controller: Texas Instruments TVP4020 [Permedia 2] (rev 1).
> Master Capable. Latency=3D255. Min Gnt=3D192.Max Lat=3D192.
> Non-prefetchable 32 bit memory at 0x10000000 [0x1001ffff].
> Non-prefetchable 32 bit memory at 0x11000000 [0x11ffffff].
> Non-prefetchable 32 bit memory at 0x10800000 [0x10ffffff].
> Prefetchable 64 bit memory at 0x3d071040 [0x3d07107f].
The last line here looks suspicious to me ('prefetchable 64 bit memory'?).
--=20
Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de=
veloper
CS student, Free Software enthusiast \ XFree86 and DRI project m=
ember
|
|
From: Roman Z. <zi...@fh...> - 2001-02-11 14:04:15
|
Hi, On Sat, 10 Feb 2001, Glenn Hisdal wrote: > The error was in apus_pcibios_##rw##_config_##size(...) > can someone (Michel ? ) fix it and put it in the cvs ? Great, thanks for the fix. It's committed. bye, Roman |
|
From: Roman Z. <zi...@us...> - 2001-02-11 13:44:03
|
CVSROOT: /cvsroot/linux-apus Module name: 2.3 Repository: 2.3/arch/ppc/kernel/ Changes by: zippel@usw-pr-cvs1. 01/02/11 05:44:35 Modified files: 2.3/arch/ppc/kernel/: apus_pci.c Log message: pci fix by Glenn Hisdal |
|
From: Glenn H. <gh...@c2...> - 2001-02-10 16:48:45
|
On 10-Feb-01, Glenn wrote:
> Hi,
> I found an error in apus_pci.c
> PCI is sort of working now. /proc/pci exists but is empty.
sorry. Have to correct myself !
/proc/pci is NOT empty. I thought it was a directory, but when I looked
closer, it was a file (ooops).
contents of /proc/pci :
PCI devices found:
Bus 0, device 1, function 0:
Display controller: Texas Instruments TVP4020 [Permedia 2] (rev 1).
Master Capable. Latency=255. Min Gnt=192.Max Lat=192.
Non-prefetchable 32 bit memory at 0x10000000 [0x1001ffff].
Non-prefetchable 32 bit memory at 0x11000000 [0x11ffffff].
Non-prefetchable 32 bit memory at 0x10800000 [0x10ffffff].
Prefetchable 64 bit memory at 0x3d071040 [0x3d07107f].
- glenn
|
|
From: Glenn H. <gh...@c2...> - 2001-02-10 14:04:12
|
Hi,
I found an error in apus_pci.c
PCI is sort of working now. /proc/pci exists but is empty.
The glint driver for XFree86 runs fine. There is no corruption on the
console after exiting X like it was in 2.4.0-test10.
The error was in apus_pcibios_##rw##_config_##size(...)
can someone (Michel ? ) fix it and put it in the cvs ?
here's the fixed code:
__apus int \
apus_pcibios_##rw##_config_##size(struct pci_dev *dev, int offset, type val) \
{ \
int fnno = FNNO(dev->devfn); \
int devno = DEVNO(dev->devfn); \
if (dev->bus->number > 0 || devno != 1) { \
cfg_##rw##_bad; \
return PCIBIOS_DEVICE_NOT_FOUND; \
} \
/* base address + function offset + offset ^ endianness conversion */ \
cfg_##rw(val, apus_hose->cfg_data + (fnno<<5) + (offset ^ mask), \
type, op); \
\
DPRINTK(#op "b: 0x%x, d: 0x%x, f: 0x%x, o: 0x%x, v: 0x%x\n", \
dev->bus->number, dev->devfn>>3, dev->devfn&7, \
offset, cfg_##rw##_val(val)); \
return PCIBIOS_SUCCESSFUL; \
}
Here's the dmesg output I get now:
Searching for SAVEKMSG magic...
Found 8457 bytes at 0x001e0010
>>>>>>>>>>>>>>>>>>>>
Total memory = 127MB; using 512kB for hash table (at c0200000)
Linux version 2.4.1 (ro...@gu...d) (gcc version 2.95.2 19991024 (release/franzo)) #34 Sat Feb 10 14:35:05 GMT 2001
Amiga hardware found: [A4000] VIDEO BLITTER AUDIO FLOPPY A4000_IDE KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA LISA ALICE_PAL ZORRO3
On node 0 totalpages: 32512
zone(0): 32512 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/hda7 video=pm2fb:mode:1024x768-75 debug debug=mem
apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected.
amiga_enable_irq: Trying to enable auto-vector IRQ 1
amiga_enable_irq: Trying to enable auto-vector IRQ 3
amiga_enable_irq: Trying to enable auto-vector IRQ 4
amiga_enable_irq: Trying to enable auto-vector IRQ 5
amiga_enable_irq: Trying to enable auto-vector IRQ 7
amiga_enable_irq: Trying to enable auto-vector IRQ 2
amiga_enable_irq: Trying to enable auto-vector IRQ 6
APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1
time_init: decrementer frequency = 16.503734 MHz
Console: colour dummy device 80x25
Calibrating delay loop... 460.39 BogoMIPS
Memory: 125572k available (1024k kernel code, 432k data, 188k init, 0k highmem)
Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes)
Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes)
Page-cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 8192 (order: 4, 65536 bytes)
POSIX conformance testing by UNIFIX
PCI: Probing PCI hardware
apus_pci: apus_pcibios_read_config_byte: readbb: 0x0, d: 0x1, f: 0x0, o: 0xe, v: 0x0
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x0, v: 0x3d07104c
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x8, v: 0x3800001
apus_pci: apus_pcibios_read_config_byte: readbb: 0x0, d: 0x1, f: 0x0, o: 0x3d, v: 0x1
apus_pci: apus_pcibios_read_config_byte: readbb: 0x0, d: 0x1, f: 0x0, o: 0x3c, v: 0x0
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0xef000000
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0xffffffff
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0xfffe0000
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0xef000000
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xe0000000
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xffffffff
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xff800000
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xe0000000
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0xe1000000
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0xffffffff
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0xff800000
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0xe1000000
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x1c, v: 0x0
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x1c, v: 0xffffffff
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x1c, v: 0x0
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x1c, v: 0x0
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x20, v: 0x0
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x20, v: 0xffffffff
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x20, v: 0x0
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x20, v: 0x0
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x24, v: 0x0
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x24, v: 0xffffffff
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x24, v: 0x0
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x24, v: 0x0
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xe2000001
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xfffffffe
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xffff0000
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xe2000001
apus_pci: apus_pcibios_read_config_word: readwb: 0x0, d: 0x1, f: 0x0, o: 0x2c, v: 0xe4e4
apus_pci: apus_pcibios_read_config_word: readwb: 0x0, d: 0x1, f: 0x0, o: 0x2e, v: 0xe4e4
PCI: Calling quirk c000b8f0 for 00:01.0
Fixup mem res, dev: 0.1, res_start: ef000000->ef000000
Fixup mem res, dev: 0.1, res_start: e0000000->e0000000
Fixup mem res, dev: 0.1, res_start: e1000000->e1000000
Fixup mem res, dev: 0.1, res_start: e2000000->e2000000
apus_pcibios_fixup_bus: PCI mem resource requested
apus_pci: apus_pcibios_read_config_word: readwb: 0x0, d: 0x1, f: 0x0, o: 0x4, v: 0x6
PCI: Resource ef000000-ef01ffff (f=200, d=0, p=0)
PCI: Cannot allocate resource region 0 of device 00:01.0
PCI: Resource e0000000-e07fffff (f=200, d=0, p=0)
PCI: Cannot allocate resource region 1 of device 00:01.0
PCI: Resource e1000000-e17fffff (f=200, d=0, p=0)
PCI: Cannot allocate resource region 2 of device 00:01.0
PCI: Switching off ROM of 00:01.0
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xe2000001
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x30, v: 0xe2000000
apus_pci: apus_pcibios_read_config_word: readwb: 0x0, d: 0x1, f: 0x0, o: 0x4, v: 0x6
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0x10000000
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x10, v: 0x10000000
got res[10000000:1001ffff] for resource 0 of Texas Instruments TVP4020 [Permedia 2]
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0x10800000
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x14, v: 0xe1000000
PCI: Error while updating region 00:01.0/1 (10800000 != e1000000)
got res[10800000:10ffffff] for resource 1 of Texas Instruments TVP4020 [Permedia 2]
apus_pci: apus_pcibios_write_config_dword: writelb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0x11000000
apus_pci: apus_pcibios_read_config_dword: readlb: 0x0, d: 0x1, f: 0x0, o: 0x18, v: 0x11000000
got res[11000000:117fffff] for resource 2 of Texas Instruments TVP4020 [Permedia 2]
Zorro: Probing AutoConfig expansion devices: 3 devices
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Starting kswapd v1.8
Unhandled interrupt 18, disabled
amiga_disable_irq: Trying to disable auto-vector IRQ 0
Console: switching to colour frame buffer device 128x48
fb0: CVisionPPC/BVisionPPC (Permedia2), using 8192K of video memory.
pty: 256 Unix98 ptys configured
block: queued sectors max/low 83325kB/27775kB, 256 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
loop: enabling 8 loop devices
Uniform Multi-Platform E-IDE driver Revision: 6.31
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
ide0: Gayle IDE interface (A4000 style)
hda: probing with STATUS(0x50) instead of ALTSTATUS(0xe0)
hda: WDC AC313000R, ATA DISK drive
hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0)
hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0)
hdb: probing with STATUS(0x51) instead of ALTSTATUS(0xe0)
hdb: CRD-8240B, ATAPI CD/DVD-ROM drive
ide0 at 80dd2020 on irq 0x0000000c
hda: 25429824 sectors (13020 MB) w/512KiB Cache, CHS=25228/16/63
hdb: ATAPI 24X CD-ROM drive, 128kB Cache
Uniform CD-ROM driver Revision: 3.12
Partition check:
hda: RDSK hda1 hda2 hda3 hda4 hda5 hda6 hda7 hda8 hda9 hda10 hda11
Amiga-builtin serial driver version 4.30
ttyS00 is the amiga builtin serial port
Amiga mouse installed.
PPP generic driver version 2.4.1
NET4: Linux TCP/IP 1.0 for NET4.0
IP Protocols: ICMP, UDP, TCP
IP: routing cache hash table of 512 buckets, 4Kbytes
TCP: Hash tables configured (established 8192 bind 8192)
NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.
VFS: Mounted root (ext2 filesystem) readonly.
Freeing unused kernel memory: 188k init
Warning: unable to open an initial console.
Restarting system.
<<<<<<<<<<<<<<<<<<<<
- glenn
|
|
From: Glenn H. <gh...@c2...> - 2001-02-10 12:11:21
|
Hi, I added a some output in apus_pcibios_##rw##_config_##size(...) just before it returns PCIBIOS_DEVICE_NOT_FOUND. Here's the result: Kernel command line: root=/dev/hda7 video=pm2fb:mode:1024x768-75 debug debug=mem apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. amiga_enable_irq: Trying to enable auto-vector IRQ 1 amiga_enable_irq: Trying to enable auto-vector IRQ 3 amiga_enable_irq: Trying to enable auto-vector IRQ 4 amiga_enable_irq: Trying to enable auto-vector IRQ 5 amiga_enable_irq: Trying to enable auto-vector IRQ 7 amiga_enable_irq: Trying to enable auto-vector IRQ 2 amiga_enable_irq: Trying to enable auto-vector IRQ 6 APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 time_init: decrementer frequency = 16.503712 MHz Console: colour dummy device 80x25 Calibrating delay loop... 460.39 BogoMIPS Memory: 125572k available (1024k kernel code, 432k data, 188k init, 0k highmem) Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware Scanning bus 00 apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found apus_pci: apus_pcibios_read_config_byte: PCI_Bios Device not found Fixups for bus 00 apus_pcibios_fixup_bus: PCI mem resource requested Bus scan for 00 returning with max=00 - glenn |
|
From: Ken T. <ke...@us...> - 2001-02-10 09:18:06
|
CVSROOT: /cvsroot/linux-apus Module name: 2.2 Repository: 2.2/drivers/video/ Changes by: kent@usw-pr-cvs1. 01/02/10 01:18:35 Modified files: 2.2/drivers/video/: virgefb.c virgefb.c remove *some* debugging prints Log message: |
|
From: <no...@so...> - 2001-02-10 02:19:24
|
Bug #131813, was updated on 2001-Feb-09 18:19 Here is a current snapshot of the bug. Project: Linux/APUS Kernel Category: 2.4 Kernel Status: Open Resolution: None Bug Group: None Priority: 5 Submitted by: paul-albert Assigned to : nobody Summary: Catweasel MKII (Budha) IDE Controller hangs with 2.4.0 Details: I have a problem with my IDE HD on the Catweasel.When I start Linux,it hangs by the Partition Check ( Checking Partition hdc: ) Normaly Checking Partition hdc: hdc1 hdc2 hdc3 hdc4 is right.With the Kernel 2.2.10 it work fine.I have change the HD to the old A4000T IDE Controller and there it work.( Checking hda: hda1 hda2 hda3 hda4 ) I have rechange the HD to the Catweasel,because I want not work on this old controller.What is the problem? Can anybody help me? My config=A4000T,2MB Chip and 96MB Fast Ram,CyberstormPPC 200 + 68060,CVisionPPC,2x 32x SCSI CDROM,HypercomIV,Catweasel MKII,20GB IDE and OS3.9 with CGX V4 installed. For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=131813&group_id=5907 |
|
From: Glenn H. <gh...@c2...> - 2001-02-09 21:05:41
|
On 09-Feb-01, Michel wrote: > Glenn Hisdal wrote: >>> Log message: >>> some additions inspired by chrp_pci.c (thanks Geert :) - someone >>> please test and post dmesg output >> >> dmesg output (only the lines that mentioned pci) : >> >> apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. >> APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 >> PCI: Probing PCI hardware >> apus_pcibios_fixup_bus: PCI mem resource requested > Cool, at least the new bus fixup function gets called... > BTW have you enabled the additional debugging code as suggested by Geert? ooops. I forgot to enable debug in drivers/pci/pci.c When I enable debug there, the kernel panics rigth after startup dmesg output: Searching for SAVEKMSG magic... Found 2414 bytes at 0x001e0010 >>>>>>>>>>>>>>>>>>>> Total memory = 127MB; using 512kB for hash table (at c0200000) Linux version 2.4.1 (ro...@gu...d) (gcc version 2.95.2 19991024 (release/franzo)) #15 Fri Feb 9 21:56:12 GMT 2001 Amiga hardware found: [A4000] VIDEO BLITTER AUDIO FLOPPY A4000_IDE KEYBOARD MOUSE SERIAL PARALLEL A3000_CLK CHIP_RAM PAULA LISA ALICE_PAL ZORRO3 On node 0 totalpages: 32512 zone(0): 32512 pages. zone(1): 0 pages. zone(2): 0 pages. Kernel command line: root=/dev/hda7 video=pm2fb:mode:1024x768-75 debug debug=mem apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. amiga_enable_irq: Trying to enable auto-vector IRQ 1 amiga_enable_irq: Trying to enable auto-vector IRQ 3 amiga_enable_irq: Trying to enable auto-vector IRQ 4 amiga_enable_irq: Trying to enable auto-vector IRQ 5 amiga_enable_irq: Trying to enable auto-vector IRQ 7 amiga_enable_irq: Trying to enable auto-vector IRQ 2 amiga_enable_irq: Trying to enable auto-vector IRQ 6 APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 time_init: decrementer frequency = 16.503734 MHz Console: colour dummy device 80x25 Calibrating delay loop... 460.39 BogoMIPS Memory: 125556k available (1024k kernel code, 432k data, 204k init, 0k highmem) Dentry-cache hash table entries: 16384 (order: 5, 131072 bytes) Buffer-cache hash table entries: 4096 (order: 2, 16384 bytes) Page-cache hash table entries: 32768 (order: 5, 131072 bytes) Inode-cache hash table entries: 8192 (order: 4, 65536 bytes) POSIX conformance testing by UNIFIX PCI: Probing PCI hardware Scanning bus 00 Fixups for bus 00 apus_pcibios_fixup_bus: PCI mem resource requested Bus scan for 00 returning with max=00 Zorro: Probing AutoConfig expansion devices: 3 devices Oops: kernel access of bad area, sig: 11 NIP: C00177DC XER: 00000000 LR: C001786C SP: C01C9ED0 REGS: c01c9e20 TRAP: 0300 MSR: 00009072 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11 DAR: 00009076, DSISR: 40000000 TASK = c01c8000[1] 'swapper' Last syscall: -1 last math 00000000 last altivec 00000000 GPR00: 01000000 C01C9ED0 C01C8000 00009072 C0134134 00000001 801E069E 00000000 GPR08: FF000000 C01C9BCC FFFFFFFF C012C85C 44848024 08171B74 0807E0CC 3C8AB800 GPR16: 0928F000 0000004C 00000000 00000000 003FF000 FFFFFD6C 0000001D 08910000 GPR24: 08910000 00000000 C0170000 C0140000 C0170000 00000002 C0130000 C0134134 Call backtrace: 00007F00 C014ABC0 C013F834 C00039F0 C0006438 Kernel panic: Attempted to kill init! Rebooting in 180 seconds..<<<<<<<<<<<<<<<<<<<< - glenn |
|
From: Glenn H. <gh...@c2...> - 2001-02-09 19:43:24
|
On 09-Feb-01, Michel wrote: > Glenn Hisdal wrote: >>> Log message: >>> some additions inspired by chrp_pci.c (thanks Geert :) - someone >>> please test and post dmesg output >> >> dmesg output (only the lines that mentioned pci) : >> >> apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. >> APUS: BATs=1, BUS=67MHz, RAM=70ns, PCI bridge=1 >> PCI: Probing PCI hardware >> apus_pcibios_fixup_bus: PCI mem resource requested > Cool, at least the new bus fixup function gets called... > BTW have you enabled the additional debugging code as suggested by Geert? yes. At least I think so. >> <<<<<<< apus_pci.c >> >> ======= >> >> What the hell is this? > It's a merge conflict, you obviously had local modifications in that file. oh, great. I had a blank line :-) - glenn |
|
From: Iain S. <ia...@sa...> - 2001-02-09 19:06:14
|
Hello sound testers et. al. replacement for dmasound ed 21 (which won't work against recent kernels). ====== The following set of patches has been submitted to Paulus for (hopefully) inclusion in 2.4.2. They include (most) of the stuff that was hacked in dmasound ed21 - but now in a non-hacked version and against an up-to-date kernel version [BK linuxppc_2_4 2.4.2pre1]. The current BK kernel also includes preliminary iBook DACA support (merged from _2_5 by Paulus) but only sound out (no mixer capability yet). I've tried to protect iBook against someone trying read() or other stuff... we shall see. ... and there are people working on the mixer ... ========== ftp://ftp.penguinppc.org/users/iain/kernel/2_4_x/2.4.2p1-dmasound-patches/ ... dmasnd-2.4.2p1ix.diff.bz2 ... + discussion.txt ix refers to the patch number and the discussion text says what each one does. Or you can apply all of them (xxx_all.diff) and just try it... Kernel Gurus: ============= M68K & APUS - please read the discussion text file if you have an interest in dmasound (especially if you are able to provide any input on the individual low-level drivers). Note I am subscribed to m68k & linuxppc but not APUS - so please copy mail to me from the latter list. I have tried very hard not to affect (other than fixing bugs + adding facilities I can see "by eye") m68k & APUS - but I can't build or test... so any testing would be appreciated. Sound Testers: ============== If you just want to test it (and I believe it really *is* stable in record & under heavy CPU load)... ftp://ftp.penguinppc.org/users/iain/kernel/2_4_x/2.4.2p1-dmasound-patches/dm asnd-2.4.2p1_all.diff.bz2 It is missing some of the "glitzy" bits that were in dmasound ed21 - sorry - that's a subsequent patch (when I get time - I'll merge it). in particular, there are no additional LE soft swapping functions. However, I believe that the machine capabilities are now reported correctly via the SNDCTL_DSP_XXX ioctls... and therefore if an app doesn't work with Pismo - it (the app) is broken... and you should bang on the app's maintainer. there's a new version of the stest program (which fixes an inability on my part to RTFM ;-) at : ftp://ftp.penguinppc.org/users/iain/sound_test/sound_test.tgz ciao, Iain. |
|
From: Michel <mic...@ii...> - 2001-02-09 18:54:32
|
Glenn Hisdal wrote: > > Log message: > > some additions inspired by chrp_pci.c (thanks Geert :) - someone > > please test and post dmesg output >=20 > dmesg output (only the lines that mentioned pci) : >=20 > apus_pci: apus_setup_pci_ptrs: Phase5 B/CVisionPPC PCI bridge detected. > APUS: BATs=3D1, BUS=3D67MHz, RAM=3D70ns, PCI bridge=3D1 > PCI: Probing PCI hardware > apus_pcibios_fixup_bus: PCI mem resource requested Cool, at least the new bus fixup function gets called... BTW have you enabled the additional debugging code as suggested by Geert? > apus_pci.c line 179 iirc : >=20 > <<<<<<< apus_pci.c >=20 > =3D=3D=3D=3D=3D=3D=3D >=20 > What the hell is this? > CVS messed up ? It's a merge conflict, you obviously had local modifications in that file= . The part between the '<'s and the '=3D's is what you had and the part between= the '=3D's and the '>'s is the new revision in the repository (IIRC, may be v= ice versa). If you haven't added anything substantial, choose the latter. ;) > PCI still doesn't work btw... D'oh. Geert, help! :) Thanks Glenn for testing. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
|
From: Michel <mic...@ii...> - 2001-02-09 18:49:01
|
Alan Buxey wrote: > beware, the main tree is 210Mb and the 4.0.2 branch is 223Mb You don't need to get the whole tree to build a server. There is a servon= ly module which unfortunately is a bit outdated, but the missing parts can e= asily be added with cvs up. --=20 Earthling Michel D=E4nzer (MrCooper) \ Debian GNU/Linux (powerpc) de= veloper CS student, Free Software enthusiast \ XFree86 and DRI project m= ember |
107 messages has been excluded from this view by a project administrator.
