Re: [Patch: clarity] Re: can't assign resources
Alfred Perlstein wrote: > * Terry Lambert <[EMAIL PROTECTED]> [020224 13:12] wrote: > > Try the following patch; the failure message will be > > somewhat less cryptic, since it will tell you the > > proximal reason for failure out of the 5 possibles > > for the message you are seeing. 8-). > > Cool explanation, the attached patch was committed but had to > be modified because it wouldn't apply cleanly. Was it meant for > -stable? Ugh. Should have done a context diff. Yeah, it was against 4.5-stable on my machine here. I can't upgrade that particular machine for you-know-why. -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Patch: clarity] Re: can't assign resources
* Terry Lambert <[EMAIL PROTECTED]> [020224 13:12] wrote: > > Try the following patch; the failure message will be > somewhat less cryptic, since it will tell you the > proximal reason for failure out of the 5 possibles > for the message you are seeing. 8-). Cool explanation, the attached patch was committed but had to be modified because it wouldn't apply cleanly. Was it meant for -stable? -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Patch: clarity] Re: can't assign resources
In the last episode (Feb 24), Terry Lambert said: > zhuravlev alexander wrote: > > vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 > > unknown: can't assign resources > > unknown: can't assign resources > > unknown: can't assign resources > > unknown: can't assign resources > > unknown: can't assign resources > > unknown: can't assign resources > > ad0: 4125MB [8940/15/63] at ata0-master UDMA33 > > acd0: CDROM at ata0-slave PIO4 > > Mounting root from ufs:/dev/ad0s2a > > - end > > > > is this normal ? > > It is if you have your BIOS configured incorrectly with > regard to whether you are running a "PNP OS". Not many BIOSes even give you this option anymore.. -- Dan Nelson [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Patch: clarity] Re: can't assign resources
Michael Smith wrote: > > It is if you have your BIOS configured incorrectly with > > regard to whether you are running a "PNP OS". > > It's also normal if you have hints loaded for things that could have been > autoconfigured, which is what the above seems to suggest. OK. 8-). I've always seen it when my "PNP OS" setting was wrong. The card IDs made me pretty sure it wasn't 8 muti-I/O cards. 8-). -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: [Patch: clarity] Re: can't assign resources
> This is a multi-part message in MIME format. > --741846253D1D9002AE8EAD96 > Content-Type: text/plain; charset=us-ascii > Content-Transfer-Encoding: 7bit > > zhuravlev alexander wrote: > > vga0: at port 0x3c0-0x3df iomem 0xa-0xbffff on isa0 > > unknown: can't assign resources > > unknown: can't assign resources > > unknown: can't assign resources > > unknown: can't assign resources > > unknown: can't assign resources > > unknown: can't assign resources > > ad0: 4125MB [8940/15/63] at ata0-master UDMA33 > > acd0: CDROM at ata0-slave PIO4 > > Mounting root from ufs:/dev/ad0s2a > > - end > > > > is this normal ? > > It is if you have your BIOS configured incorrectly with > regard to whether you are running a "PNP OS". It's also normal if you have hints loaded for things that could have been autoconfigured, which is what the above seems to suggest. -- To announce that there must be no criticism of the president, or that we are to stand by the president, right or wrong, is not only unpatriotic and servile, but is morally treasonable to the American public. - Theodore Roosevelt To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
[Patch: clarity] Re: can't assign resources
zhuravlev alexander wrote:
> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> unknown: can't assign resources
> ad0: 4125MB [8940/15/63] at ata0-master UDMA33
> acd0: CDROM at ata0-slave PIO4
> Mounting root from ufs:/dev/ad0s2a
> - end
>
> is this normal ?
It is if you have your BIOS configured incorrectly with
regard to whether you are running a "PNP OS".
It's also normal if you have more hardware in a box
than it's possible to handle simultaneously, e.g. if
you had a bunch of slots full of resource hungry
hardware.
Probably you will need to fiddle with your BIOS.
Try the following patch; the failure message will be
somewhat less cryptic, since it will tell you the
proximal reason for failure out of the 5 possibles
for the message you are seeing. 8-).
-- Terry
Index: isa_common.c
===
RCS file: /usr/cvs/src/sys/isa/isa_common.c,v
retrieving revision 1.16.2.1
diff -u -r1.16.2.1 isa_common.c
--- isa_common.c16 Sep 2000 15:49:52 - 1.16.2.1
+++ isa_common.c24 Feb 2002 21:07:23 -
@@ -387,15 +387,20 @@
struct isa_device *idev = DEVTOISA(child);
struct isa_config_entry *ice;
struct isa_config config;
+ char *reason = "Empty ISA id_configs";
bzero(&config, sizeof config);
TAILQ_FOREACH(ice, &idev->id_configs, ice_link) {
+ reason = "memory";
if (!isa_find_memory(child, &ice->ice_config, &config))
continue;
+ reason = "port";
if (!isa_find_port(child, &ice->ice_config, &config))
continue;
+ reason = "irq";
if (!isa_find_irq(child, &ice->ice_config, &config))
continue;
+ reason = "drq";
if (!isa_find_drq(child, &ice->ice_config, &config))
continue;
@@ -403,6 +408,7 @@
* A working configuration was found enable the device
* with this configuration.
*/
+ reason = "no callback";
if (idev->id_config_cb) {
idev->id_config_cb(idev->id_config_arg,
&config, 1);
@@ -414,7 +420,7 @@
* Disable the device.
*/
bus_print_child_header(device_get_parent(child), child);
- printf(" can't assign resources\n");
+ printf(" can't assign resources (%s)\n", reason);
if (bootverbose)
isa_print_child(device_get_parent(child), child);
bzero(&config, sizeof config);
can't assign resources
hi ! [zaa:/u/zaa]>uname -a FreeBSD zaa.ulstu.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Sun Feb 24 22:38:36 MSK 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/GENERIC i386 - /var/run/dmesg.boot --- sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 4125MB [8940/15/63] at ata0-master UDMA33 acd0: CDROM at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s2a - end is this normal ? full dmesg.boot attached. -- zhuravlev alexander u l s t u n o c e-mail:[EMAIL PROTECTED] Copyright (c) 1992-2002 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-CURRENT #0: Sun Feb 24 22:38:36 MSK 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc052a000. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 266616007 Hz CPU: Pentium II/Pentium II Xeon/Celeron (266.62-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping = 4 Features=0x80fbff real memory = 134217728 (131072K bytes) avail memory = 125222912 (122288K bytes) Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: at pcibus 0 on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xdf80-0xdf9f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered pci0: at device 7.3 (no driver attached) ata: ata0 already exists; skipping it ata: ata1 already exists; skipping it sc: sc0 already exists; skipping it vga: vga0 already exists; skipping it atkbdc0: at port 0x64,0x60 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 fdc0: at port 0x3f7,0x3f0-0x3f5 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 pmtimer0 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (ECP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/16 bytes threshold plip0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port ppi0: on ppbus0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources unknown: can't assign resources ad0: 4125MB [8940/15/63] at ata0-master UDMA33 acd0: CDROM at ata0-slave PIO4 Mounting root from ufs:/dev/ad0s2a
Re: unknown: can't assign resources
Julian Elischer <[EMAIL PROTECTED]> writes: > Msmith mailed me a PNP device list. > I include it here for your assistance in identifying these. That list is from Microsoft's web site and only lists generic devices. A better list can be found at the following URL: http://home.hyperlink.net.au/~chart/download/pnpid.txt DES -- Dag-Erling Smorgrav - [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: unknown: can't assign resources
On Fri, Feb 23, 2001 at 11:33:42AM -0500, Guillaume wrote: > Hello, > > I'm running FreeBSD 5.0-CURRENT since 2 days. > > When I boot FreeBSD I get this error: > > Feb 22 23:21:13 unix /boot/kernel/kernel: vga0: at port > 0x3c0-0x3df iomem 0xa-0xb on isa0 > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > > What is that and how can I fix this error? Check the archives so someone doesn't have to answer this question all over again. Kris PGP signature
Re: unknown: can't assign resources
Guillaume wrote: > > Hello, > > I'm running FreeBSD 5.0-CURRENT since 2 days. > > When I boot FreeBSD I get this error: > > Feb 22 23:21:13 unix /boot/kernel/kernel: vga0: at port > 0x3c0-0x3df iomem 0xa-0xb on isa0 > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign > resources > > What is that and how can I fix this error? The BIOS's PNP table i sreporting devices that you are also mentionning in either your kernel config hints file, or in /boot/device.hints. (or maybe even PCI devices). In either case, the one you mention in your config gets allocated the ports and interrupts etc. so when the kernel tries to allocate them for the PNP device, it can't. Since they are refering to the same device, this doesn;t matter, in fact it's good. (Or you'd have two driver instances pointing at teh same hardware). if you remove the entries in /boot/device.hints that refer to the same device, and let the PNP table be used instead to attach drivers (for those that are recognised) you'll get less of these. Msmith mailed me a PNP device list. I include it here for your assistance in identifying these. > > Guillaume > [EMAIL PROTECTED] > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message -- __--_|\ Julian Elischer / \ [EMAIL PROTECTED] ( OZ) World tour 2000-2001 ---> X_.---._/ v This document is the ultimate source for Windows Generic Device IDs and Plug and Play BIOS device type codes. CONTENTS: Plug and Play Vendor IDs and Device IDs Generic Device IDs Device Type Codes == PLUG AND PLAY VENDOR IDs AND DEVICE IDs All non-BIOS enumerated devices must not use "PNP" in their Vendor and Device codes. The vendor must register with EISA and have a vendor code assigned (for example, CTL for Creative Labs). The "PNP" vendor code is reserved for Microsoft and can only be used when defining a devices CompatibleID after indicating the devices HardwareID in the Plug and Play header. Use of CompatibleIDs is strongly recommended for devices that use device drivers provided with Microsoft Windows 95, such as a "Standard PC COM Port" (PNP0500) or "Sound Blaster 16 Sound Device" (PNPB003). The following example output from ISOLATE.EXE of a Plug and Play header is provided for your reference: Vendor ID: XXX Serial Number: 0001 Checksum (reported): 0x5E PNP Version: 1.0 Vendor Ver.: 10 Device Description: IDE Port Device ID: XXX0001 Doesn't Support I/O Range Checking Vendor Defined Logical Device Control Registers: None Compatible Device ID: PNP0600 Device Description: IDE Dependent Function 0 ... Dependent Function 1 ... End of Dependent Functions When the user is installing devices that use this method, a dialog box appears at the beginning of the enumeration sequence to suggest use of the default driver provided with Windows 95. Windows 95 also provides the option for using a disk from the manufacturer, in case the user wants to choose a manufacturer-supplied driver. For multifunction adapters, you should supply an INF file that chooses the appropriate drivers (including default drivers) for all the adapters devices. This prevents additional dialog boxes from again requesting the default driver or a manufactures disk for the rest of the devices on the adapter. When an INF file is used in this manner for default driver selection, it must link the HardwareID (XXX) to the appropriate compatible device driver from the Windows 95 distribution compact disc or installation disks. If this is not done, Windows 95 will continue to query the user for either the default driver or a new driver, thus defeating the purpose of using the INF file in this way. == WINDOWS GENERIC DEVICE IDs -- Many devices have no standard EISA ID, such as the interrupt controller or keyboard controller. Also, a set of compatible devices, such as VGA and Super VGA, are not actually devices, but define a compatibility hardware subset. Yet another set of IDs needs to be used to identify buses. Microsoft has reserved an
unknown: can't assign resources
Hello, I'm running FreeBSD 5.0-CURRENT since 2 days. When I boot FreeBSD I get this error: Feb 22 23:21:13 unix /boot/kernel/kernel: vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources Feb 22 23:21:13 unix /boot/kernel/kernel: unknown: can't assign resources What is that and how can I fix this error? Guillaume [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't assign resources
> > Could someone please either take a look at this, or give an > > authoritative comment as to why it's happening. This is the ISA PnP code reporting devices enumerated via the PnP BIOS. At the moment, our support code isn't smart enough to use either the PnP interface or the resource manager, so the unknown device claims these resources to prevent anyone else trying to use them. It's quite harmless, and once things are cleaned up, you won't even see the messages. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ [EMAIL PROTECTED] \\ and he'll hate you for a lifetime. \\ [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't assign resources
tes threshold May 4 12:20:03 telecast /kernel: fd0: <1440-KB 3.5" drive> on fdc0 drive 0 May 4 12:20:03 telecast /kernel: atkbdc0: at port 0x60,0x64 on isa0 May 4 12:20:03 telecast /kernel: atkbd0: irq 1 on atkbdc0 May 4 12:20:03 telecast /kernel: psm0: irq 12 on atkbdc0 May 4 12:20:03 telecast /kernel: psm0: model MouseMan+, device ID 0 May 4 12:20:03 telecast /kernel: vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 May 4 12:20:03 telecast /kernel: sc0: on isa0 May 4 12:20:03 telecast /kernel: sc0: VGA <16 virtual consoles, flags=0x200> May 4 12:20:03 telecast /kernel: sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 May 4 12:20:03 telecast /kernel: sio0: type 16550A May 4 12:20:03 telecast /kernel: ppc0: at port 0x378-0x37f irq 7 on isa0 May 4 12:20:03 telecast /kernel: ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode May 4 12:20:03 telecast /kernel: lpt0: on ppbus0 May 4 12:20:03 telecast /kernel: lpt0: Interrupt-driven port May 4 12:20:03 telecast /kernel: unknown0: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 May 4 12:20:03 telecast /kernel: unknown1: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 May 4 12:20:03 telecast /kernel: unknown2: at port 0x40-0x43 irq 0 on isa0 May 4 12:20:03 telecast /kernel: unknown3: at port 0x70-0x71 irq 8 on isa0 May 4 12:20:03 telecast /kernel: unknown: can't assign resources May 4 12:20:03 telecast /kernel: unknown4: at port 0x61 on isa0 May 4 12:20:03 telecast /kernel: unknown5: at port 0xf0-0xff irq 13 on isa0 May 4 12:20:03 telecast /kernel: unknown6: at iomem 0-0x9,0xfffe-0x,0xfec00000-0xfec0,0xfee0-0xfee0,0x10-0x3ff on isa0 May 4 12:20:03 telecast /kernel: unknown7: at iomem 0xf-0xf3fff,0xf4000-0xf7fff,0xf8000-0xf,0xd1800-0xd3fff on isa0 May 4 12:20:03 telecast /kernel: unknown: can't assign resources May 4 12:20:03 telecast /kernel: unknown: can't assign resources May 4 12:20:03 telecast /kernel: unknown: can't assign resources May 4 12:20:03 telecast /kernel: unknown: can't assign resources May 4 12:20:03 telecast /kernel: unknown: can't assign resources May 4 12:20:03 telecast /kernel: APIC_IO: Testing 8254 interrupt delivery May 4 12:20:03 telecast /kernel: APIC_IO: routing 8254 via IOAPIC #0 intpin 2 May 4 12:20:03 telecast /kernel: SMP: AP CPU #1 Launched! May 4 12:20:03 telecast /kernel: ad4: 9765MB [19841/16/63] at ata2-master using UDMA33 May 4 12:20:03 telecast /kernel: acd0: CDROM at ata1-master using UDMA33 May 4 12:20:03 telecast /kernel: Mounting root from ufs:/dev/ad4s2a May 4 12:20:03 telecast /kernel: ed0: starting DAD for fe80:0001::0260:67ff:fe22:c884 May 4 12:20:03 telecast /kernel: ed0: DAD complete for fe80:0001::0260:67ff:fe22:c884 - no duplicates found May 4 12:20:05 telecast sshd[179]: Listener created on port 22. May 4 12:20:05 telecast sshd[180]: Daemon is running. May 4 12:20:12 telecast login: ROOT LOGIN (root) ON ttyv0
Re: can't assign resources
PNP0400 (0004d041) PNP0700: adding io range 0x3f0-0x3f5, size=0x6, align=0x1 PNP0700: adding irq mask 0x40 PNP0700: adding dma mask 0x4 PNP0700: end config pnpbios: handle 14 device ID PNP0700 (0007d041) PNP0f13: adding irq mask 0x1000 PNP0f13: end config pnpbios: handle 15 device ID PNP0f13 (130fd041) PNP0a03: end config pnpbios: handle 16 device ID PNP0a03 (030ad041) Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 ata-: ata0 exists, using next available unit number ata-: ata1 exists, using next available unit number isa_probe_children: disabling PnP devices isa_probe_children: probing non-PnP devices fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 atkbd: the current kbd controller command byte 0065 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa kbd0: atkbd0, AT 101/102 (2), config:0x0, flags:0x3d psm0: current command byte:0065 kbdc: TEST_AUX_PORT status: kbdc: RESET_AUX return code:00fa kbdc: RESET_AUX status:00aa kbdc: RESET_AUX ID: psm: status 00 02 64 psm: status 00 00 64 psm: status 00 03 64 psm: status 00 03 64 psm: data 08 00 00 psm: status 10 00 64 psm: status 00 02 64 psm: data 08 00 00 psm: status 00 02 64 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0-00, 2 buttons psm0: config:, flags:, packet size:3 psm0: syncmask:c0, syncbits:00 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3c0-0x3df, crtc:0x3d4, mem:0xa 0x2 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xc00b8000 size:32k gran:32k, buf:0 size:32k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 05 50 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sc0: fb0, kbd0, terminal emulator: sc (syscons terminal) sio0: irq maps: 0x41 0x51 0x41 0x41 sio0 at port 0x3f8-0x3ff irq 4 flags 0x1 on isa0 sio0: type 16550A ppc0: parallel port found at 0x378 ppc0: EPP SPP ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode nTppb1284: error=3 status=0xd8 event=24 1Tppbus0: IEEE1284 device found n1/NIBBLETn2ppb1284: error=1 status=0xe8 event=7 TnTppb1284: error=3 status=0xd8 event=24 8ppb1284: error=1 status=0xe8 event=7 TnTppb1284: error=3 status=0xd8 event=24 8ppb1284: error=1 status=0xe8 event=7 TnTppb1284: error=3 status=0xd8 event=24 4ppb1284: error=1 status=0xe8 event=7 TnTppb1284: error=3 status=0xd8 event=24 1/NIBBLE_IDTn2ppb1284: error=1 status=0xe8 event=7 TnTppb1284: error=3 status=0xd8 event=24 8ppb1284: error=1 status=0xe8 event=7 TnTppb1284: error=3 status=0xd8 event=24 8ppb1284: error=1 status=0xe8 event=7 TnTppb1284: error=3 status=0xd8 event=24 0T/Extensibility LinkTppb1284: error=3 status=0xd8 event=24 Probing for PnP devices on ppbus0: nTppb1284: error=3 status=0xd8 event=24 1BBTppb: 102 characters: (0x0) f(0x66) M(0x4d) F(0x46) G(0x47) :(0x3a) C(0x43) a(0x61) n(0x6e) o(0x6f) n(0x6e) ;(0x3b) C(0x43) M(0x4d) D(0x44) :(0x3a) B(0x42) J(0x4a) ,(0x2c) L(0x4c) Q(0x51) ,(0x2c) B(0x42) J(0x4a) L(0x4c) ,(0x2c) B(0x42) J(0x4a) R(0x52) a(0x61) s(0x73) t(0x74) e(0x65) r(0x72) ,(0x2c) B(0x42) S(0x53) C(0x43) C(0x43) ;(0x3b) M(0x4d) D(0x44) L(0x4c) :(0x3a) B(0x42) J(0x4a) C(0x43) -(0x2d) 2(0x32) 6(0x36) 5(0x35) S(0x53) P(0x50) ;(0x3b) C(0x43) L(0x4c) S(0x53) :(0x3a) P(0x50) R(0x52) I(0x49) N(0x4e) T(0x54) E(0x45) R(0x52) ;(0x3b) D(0x44) E(0x45) S(0x53) :(0x3a) C(0x43) a(0x61) n(0x6e) o(0x6f) n(0x6e) (0x20) B(0x42) J(0x4a) C(0x43) -(0x2d) 2(0x32) 6(0x36) 5(0x35) S(0x53) P(0x50) ;(0x3b) V(0x56) E(0x45) R(0x52) :(0x3a) 1(0x31) .(0x2e) 0(0x30) 0(0x30) ;(0x3b) S(0x53) T(0x54) A(0x41) :(0x3a) 1(0x31) 0(0x30) ;(0x3b) ppbus0: PRINTER BJ,LQ,BJL,BJRaster,BSCC lpt0: on ppbus0 lpt0: Interrupt-driven port isa_probe_children: probing PnP devices unknown0: at iomem 0-0x9fbff,0x9fc00-0x9ffff,0xe-0xf,0x3fe-0x3ff7fff,0x3ff8000-0x3ff,0xfec0-0xfec00fff,0xfee0-0xfee00fff,0xfff80
Re: can't assign resources
Trent Nelson wrote: > > Ted Sikora wrote: > > > > I have been getting these messages from my kernel for some time now. > > Could the culprit be these 2 isa cards: > > non-pnp SB16 sbc0 > > ne2000 ed0 > > They are on a SMP BP6 > > I've posted a message both to current and questions about this now. I'm > experiencing the same thing with roughly the same I/O addresses being > claimed. I doubt it has anything to do with the ISA cards you mention as > many of the addresses relate to things like the DMA registers/timer and > other associated resources. > > Could someone please either take a look at this, or give an > authoritative comment as to why it's happening. > > If someone points me in the direction of the particular code where the > unknown driver is claiming the devices; I'll make an attempt to take a > look at it myself. > > > May 3 14:53:19 telecast /kernel: unknown0: at port > > 0x20-0x21,0xa0-0xa1 irq 2 on isa0 > > May 3 14:53:19 telecast /kernel: unknown1: at port > > 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 Your right the addresses seem to be standard machine resources. Are you using SMP? The irq's are remapped on a SMP machine so maybe that's were the trouble lies? The PNP tag is what has me stumped. I replaced the isa cards with pci this evening out of curiosity...same thing. -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: can't assign resources
Ted Sikora wrote: > > I have been getting these messages from my kernel for some time now. > Could the culprit be these 2 isa cards: > non-pnp SB16 sbc0 > ne2000 ed0 > They are on a SMP BP6 I've posted a message both to current and questions about this now. I'm experiencing the same thing with roughly the same I/O addresses being claimed. I doubt it has anything to do with the ISA cards you mention as many of the addresses relate to things like the DMA registers/timer and other associated resources. Could someone please either take a look at this, or give an authoritative comment as to why it's happening. If someone points me in the direction of the particular code where the unknown driver is claiming the devices; I'll make an attempt to take a look at it myself. > May 3 14:53:19 telecast /kernel: unknown0: at port > 0x20-0x21,0xa0-0xa1 irq 2 on isa0 > May 3 14:53:19 telecast /kernel: unknown1: at port > 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 > Ted Sikora > Jtl Development Group > [EMAIL PROTECTED] Regards, Trent. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
can't assign resources
I have been getting these messages from my kernel for some time now. Could the culprit be these 2 isa cards: non-pnp SB16 sbc0 ne2000 ed0 They are on a SMP BP6 May 3 14:53:19 telecast /kernel: unknown0: at port 0x20-0x21,0xa0-0xa1 irq 2 on isa0 May 3 14:53:19 telecast /kernel: unknown1: at port 0-0xf,0x81-0x83,0x87,0x89-0x8b,0x8f-0x91,0xc0-0xdf drq 4 on isa0 May 3 14:53:19 telecast /kernel: unknown2: at port 0x40-0x43 irq 0 on isa0 May 3 14:53:19 telecast /kernel: unknown3: at port 0x70-0x71 irq 8 on isa0 May 3 14:53:19 telecast /kernel: unknown: can't assign resources May 3 14:53:19 telecast /kernel: unknown4: at port 0x61 on isa0 May 3 14:53:19 telecast /kernel: unknown5: at port 0xf0-0xff irq 13 on isa0 May 3 14:53:19 telecast /kernel: unknown6: at iomem 0-0x9,0xfffe-0x,0xfec0-0xfec0,0xfee0-0xfee0,0x10-0x3ff on isa0 May 3 14:53:19 telecast /kernel: unknown7: at iomem 0xf-0xf3fff,0xf4000-0xf7fff,0xf8000-0xf,0xd1800-0xd3fff on isa0 May 3 14:53:19 telecast /kernel: unknown: can't assign resources May 3 14:53:19 telecast /kernel: unknown: can't assign resources May 3 14:53:19 telecast /kernel: unknown: can't assign resources May 3 14:53:19 telecast /kernel: unknown: can't assign resources May 3 14:53:19 telecast /kernel: unknown: can't assign resources -- Ted Sikora Jtl Development Group [EMAIL PROTECTED] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
