Re: Mounting Root fails with error 22 (EINVAL)
[EMAIL PROTECTED] wrote: Can somebody please use "cvs update -D " to do a binary search and identify which exact commit caused the problem ? Hello, I am getting the following result: A Kernel check out with the following command works: cvs -d /space/CVSROOT co -D "2003-02-20 00:00"-P src the one check out with the following command does not work cvs -d /space/CVSROOT co -D "2003-02-20 11:00" -P src Unfortunately I have to leave now and cannot dig deeper into this. The system I am doing this on is on MET timzone (and I am not sure on the implications on the cvs command ...). Michael -- ----- michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mounting Root fails with error 22 (EINVAL)
On Sun, 23 Feb 2003, Soeren Schmidt wrote: > It seems Michael Class wrote: > > Hello Soeren, > > > > I am sorry, but the last demsg output I have sent was not complete. I > > had captured that from /var/log/messages which does not seem to contain > > everything... > > > > Enclosed is a new one done with a serial console. Here I think the > > culprit can be seen as lines like: > > > > (probe2:ata2:0:0:0): CAM Status 0x39 > > > > Anything I can do to help investigate this further? > > Loose atapi-cam please and let me know if that helps > > -Søren Been there, done that. No change! Michael To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Mounting Root fails with error 22 (EINVAL)
Hello Soeren,
I am sorry, but the last demsg output I have sent was not complete. I
had captured that from /var/log/messages which does not seem to contain
everything...
Enclosed is a new one done with a serial console. Here I think the
culprit can be seen as lines like:
(probe2:ata2:0:0:0): CAM Status 0x39
Anything I can do to help investigate this further?
Michael
Soeren Schmidt wrote:
It seems Anders Andersson wrote:
On Sat, Feb 22, 2003 at 01:02:33PM +0100, [EMAIL PROTECTED] wrote:
If you say int broke in the 20feb timeframe I think sos@' ATA megacommit
is the main suspect...
Yes, sos ATA commit is what broke my sparc64 also (already informed sos
in private mail), but he didnt have any direct ideas about the cause.
Your problem is different, you dont see the disks due to missing interrupts,
here the disks are found and read from but it falls apart later...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
--
-----
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-
Console: serial port
BIOS drive A: is disk0
BIOS drive C: is disk1
BIOS drive D: is disk2
BIOS drive E: is disk3
BIOS 639kB/1047488kB available memory
FreeBSD/i386 bootstrap loader, Revision 1.1
([EMAIL PROTECTED], Sat Feb 15 14:17:10 MET 2003)
Loading /boot/defaults/loader.conf
Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel] in 9 seconds... Booting [/boot/kernel/kernel] in 8
seconds... Booting [/boot/kernel/kernel] in 7 seconds... Booting [/boot/kernel/kernel]
in 6 seconds...
Type '?' for a list of commands, 'help' for more detailed help.
OK unload
OK load /boot/kernel.test/kernel
OK load /boot/kernel.test/acpi.ko
OK boot -v
SMAP type=01 base= len= 0009fc00
SMAP type=02 base= 0009fc00 len= 0400
SMAP type=02 base= 000f len= 0001
SMAP type=01 base= 0010 len= 3fef
SMAP type=03 base= 3fff len= 8000
SMAP type=04 base= 3fff8000 len= 8000
SMAP type=02 base= fec0 len= 1000
SMAP type=02 base= fee0 len= 1000
SMAP type=02 base= len= 0001
Copyright (c) 1992-2003 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 23 08:59:21 MET 2003
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MCSMP2
Preloaded elf kernel "/boot/kernel.test/kernel" at 0xc0566000.
Preloaded elf module "/boot/kernel.test/acpi.ko" at 0xc05660bc.
Calibrating clock(s) ... i8254 clock: 1193225 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254" frequency 1193182 Hz
Calibrating TSC clock ... TSC clock: 996558899 Hz
CPU: Intel Pentium III (996.56-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x68a Stepping = 10
Features=0x383fbff
real memory = 1073676288 (1023 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0059 - 0x3ffd, 1067778048 bytes (260688 pages)
avail memory = 1037332480 (989 MB)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0
cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0
io0 (APIC): apic id: 2, version: 0x00178011, at 0xfec0
bios32: Found BIOS32 Service Directory header at 0xc00fdad0
bios32: Entry = 0xfdae0 (c00fdae0) Rev = 0 Len = 1
pcibios: PCI BIOS entry at 0xf+0xdb01
pnpbios: Found PnP BIOS data at 0xc00f6e40
pnpbios: Entry = f:5c04 Rev = 1.0
Other BIOS signatures found:
null:
random:
mem:
Pentium Pro MTRR support enabled
SMP: CPU0 bsp_apic_configure():
lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff
npx0: on motherboard
npx0: INT 16 interface
acpi0: on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
pci_open(1):mode 1 addr port (0x0cf8) is 0x80010048
pci_open(1a): mode1res=0x8000 (0x8000)
pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06911106)
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00f7530
PCI-Only Interrupts: none
Location Bus Device Pin Link IRQs
embedded01A 0x01 3 4 5 7 9 10 11 12 14 15
embedded01B 0x02 3 4 5 7 9 10 11 12 14 15
embedded01C 0x03 3 4 5 7 9 10 11 12 14 15
embedded01D 0x05 3 4 5 7 9 10 11 12 14 15
embedded0
Re: Mounting Root fails with error 22 (EINVAL)
Please try "boot -v" and send dmesg.
Also, please try entering "?" to root device prompt to see what devices
are available.
Hello, enclosed is the boot -v output that you were asking for.
Michael
--
---------
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-
Copyright (c) 1992-2003 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: Sat Feb 22 08:29:29 MET 2003
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MCSMP2
Preloaded elf kernel "/boot/kernel.test/kernel" at 0xc0565000.
Preloaded elf module "/boot/kernel.test/acpi.ko" at 0xc05650bc.
Calibrating clock(s) ... i8254 clock: 1193225 Hz
CLK_USE_I8254_CALIBRATION not specified - using default frequency
Timecounter "i8254" frequency 1193182 Hz
Calibrating TSC clock ... TSC clock: 996553246 Hz
CPU: Intel Pentium III (996.55-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x68a Stepping = 10
Features=0x383fbff
real memory = 1073676288 (1023 MB)
Physical memory chunk(s):
0x1000 - 0x0009efff, 647168 bytes (158 pages)
0x0058f000 - 0x3ffd, 1067782144 bytes (260689 pages)
avail memory = 1037225984 (989 MB)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0
cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0
io0 (APIC): apic id: 2, version: 0x00178011, at 0xfec0
bios32: Found BIOS32 Service Directory header at 0xc00fdad0
bios32: Entry = 0xfdae0 (c00fdae0) Rev = 0 Len = 1
pcibios: PCI BIOS entry at 0xf+0xdb01
pnpbios: Found PnP BIOS data at 0xc00f6e40
pnpbios: Entry = f:5c04 Rev = 1.0
Other BIOS signatures found:
null:
random:
mem:
Pentium Pro MTRR support enabled
SMP: CPU0 bsp_apic_configure():
lint0: 0x00010700 lint1: 0x0400 TPR: 0x SVR: 0x01ff
npx0: on motherboard
npx0: INT 16 interface
acpi0: on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
pci_open(1):mode 1 addr port (0x0cf8) is 0x80010048
pci_open(1a): mode1res=0x8000 (0x8000)
pci_cfgcheck: device 0 [class=06] [hdr=00] is there (id=06911106)
pcibios: BIOS version 2.10
Using $PIR table, 8 entries at 0xc00f7530
PCI-Only Interrupts: none
Location Bus Device Pin Link IRQs
embedded01A 0x01 3 4 5 7 9 10 11 12 14 15
embedded01B 0x02 3 4 5 7 9 10 11 12 14 15
embedded01C 0x03 3 4 5 7 9 10 11 12 14 15
embedded01D 0x05 3 4 5 7 9 10 11 12 14 15
embedded07A 0xfe 14
embedded07B 0xff 15
embedded07C 0x03 3 4 5 7 9 10 11 12 14 15
embedded07D 0x05 3 4 5 7 9 10 11 12 14 15
slot 1 09A 0x02 3 4 5 7 9 10 11 12 14 15
slot 1 09B 0x03 3 4 5 7 9 10 11 12 14 15
slot 1 09C 0x05 3 4 5 7 9 10 11 12 14 15
slot 1 09D 0x01 3 4 5 7 9 10 11 12 14 15
slot 2 0 10A 0x03 3 4 5 7 9 10 11 12 14 15
slot 2 0 10B 0x05 3 4 5 7 9 10 11 12 14 15
slot 2 0 10C 0x01 3 4 5 7 9 10 11 12 14 15
slot 2 0 10D 0x02 3 4 5 7 9 10 11 12 14 15
slot 3 0 11A 0x05 3 4 5 7 9 10 11 12 14 15
slot 3 0 11B 0x01 3 4 5 7 9 10 11 12 14 15
slot 3 0 11C 0x02 3 4 5 7 9 10 11 12 14 15
slot 3 0 11D 0x03 3 4 5 7 9 10 11 12 14 15
slot 4 0 12A 0x01 3 4 5 7 9 10 11 12 14 15
slot 4 0 12B 0x02 3 4 5 7 9 10 11 12 14 15
slot 4 0 12C 0x03 3 4 5 7 9 10 11 12 14 15
slot 4 0 12D 0x05 3 4 5 7 9 10 11 12 14 15
slot 5 0 13A 0x02 3 4 5 7 9 10 11 12 14 15
slot 5 0 13B 0x03 3 4 5 7 9 10 11 12 14 15
slot 5 0 13C 0x05 3 4 5 7 9 10 11 12 14 15
slot 5 0 13D 0x01 3 4 5 7 9 10 11 12 14 15
embedded0 14A 0x03 3 4 5 7 9 10 11 12 14 15
embedded0 14B 0x05 3 4 5 7 9 10 11 12 14 15
embedded0 14C 0x01 3 4 5 7 9 10 11 12 14 15
embedded0 14D 0x02 3 4 5 7 9 10 11 12 14 15
acpi0: power button is handled as a fixed feature programming model.
ACPI timer looks GOOD min = 1, max = 2, width = 2
ACPI timer looks GOOD min = 1, max = 2, width = 2
ACPI timer looks GOOD min = 1, max = 2, width = 2
ACPI timer looks GOOD min = 1, max = 2, width = 2
ACPI timer looks GOOD min = 1, max = 2, width = 2
ACPI timer looks GOOD min = 1, max = 2, width = 2
ACPI timer looks GOOD min = 1, max = 2, width = 2
ACPI timer looks GOOD min = 1, max = 2, width = 2
ACPI timer looks GOOD min = 1, m
Re: Mounting Root fails with error 22 (EINVAL)
Christian Gusenbauer wrote:
Hi!
I've just cvsupped current and rebuilt world and now I'm getting this error
when I boot with the new kernel. I had a look at the archives and found out
that such a problem existed in January, too and I verified, that I do have
the right revision of src/sys/ufs/ffs/fs.h (1.38). A kernel dated Feb. 14th
boots without problems. Did I miss something?
Hello,
just as a data-point. I am seeing the same behaviour. It started with a
kernel from Feb 21th. The kernel from Feb. 20th works o.k.
Enclosed is the dmesg out, if that helps.
Michael
--
-
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-
Copyright (c) 1992-2003 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: Mon Feb 17 19:59:15 MET 2003
[EMAIL PROTECTED]:/usr/src/sys/i386/compile/MCSMP2
Preloaded elf kernel "/boot/kernel/kernel" at 0xc0566000.
Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05660a8.
Timecounter "i8254" frequency 1193182 Hz
CPU: Intel Pentium III (996.55-MHz 686-class CPU)
Origin = "GenuineIntel" Id = 0x68a Stepping = 10
Features=0x383fbff
real memory = 1073676288 (1023 MB)
avail memory = 1037221888 (989 MB)
Programming 24 pins in IOAPIC #0
IOAPIC #0 intpin 2 -> irq 0
FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0
cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0
io0 (APIC): apic id: 2, version: 0x00178011, at 0xfec0
Pentium Pro MTRR support enabled
npx0: on motherboard
npx0: INT 16 interface
acpi0: on motherboard
ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15
Using $PIR table, 8 entries at 0xc00f7530
acpi0: power button is handled as a fixed feature programming model.
Timecounter "ACPI-fast" frequency 3579545 Hz
acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
acpi_cpu0: port 0x530-0x537 on acpi0
acpi_cpu1: port 0x530-0x537 on acpi0
acpi_tz0: port 0x530-0x537 on acpi0
acpi_button0: on acpi0
pcib0: port 0xcf8-0xcff on acpi0
pci0: on pcib0
agp0: mem 0xe000-0xe3ff at device
0.0 on pci0
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 0xb800-0xb81f irq 9 at device 7.2 on pci0
uhci0: LegSup = 0xa000
usb0: on uhci0
usb0: USB revision 1.0
uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub0: 2 ports with 2 removable, self powered
ulpt0: Hewlett-Packard DeskJet 990C, rev 1.10/1.00, addr 2, iclass 7/1
ulpt0: using bi-directional mode
uhci1: port 0xbc00-0xbc1f irq 9 at device 7.3 on pci0
usb1: on uhci1
usb1: USB revision 1.0
uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
uhub1: 2 ports with 2 removable, self powered
uhub1: port error, restarting port 1
uhub1: port error, giving up port 1
uhub1: port error, restarting port 2
uhub1: port error, giving up port 2
viapropm0: SMBus I/O base at 0x400
viapropm0: port 0x400-0x40f at device 7.4 on pci0
viapropm0: SMBus revision code 0x40
smb0: on smbus0
pcm0: port 0xc000-0xc003,0xc400-0xc403,0xc800-0xc8ff irq 10 at device
7.5 on pci0
pcm0:
xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xb400-0xb47f mem 0xdffdff80-0xdffd
irq 5 at device 9.0 on pci0
xl0: Ethernet address: 00:10:5a:d7:dd:9c
miibus0: on xl0
xlphy0: <3Com internal media interface> on miibus0
xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
atapci1: port
0xcc00-0xccff,0xd000-0xd003,0xd400-0xd407,0xd800-0xd803,0xdc00-0xdc07 irq 10 at device
10.0 on pci0
ata2: at 0xdc00 on atapci1
ata3: at 0xd400 on atapci1
bktr0: mem 0xdedfe000-0xdedfefff irq 9 at device 11.0 on pci0
bktr0: Hauppauge Model 61344 D121
bktr0: Detected a MSP3410D-B4 at 0x80
bktr0: Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, remote
control.
pci0: at device 11.1 (no driver attached)
sym0: <875> port 0xa800-0xa8ff mem 0xdffde000-0xdffdefff,0xdffdfe00-0xdffdfeff irq 11
at device 12.0 on pci0
sym0: Symbios NVRAM, ID 7, Fast-20, SE, parity checking
sym0: open drain IRQ line driver, using on-chip SRAM
sym0: using LOAD/STORE-based firmware.
sym0: SCAN FOR LUNS disabled for targets 0 1 2 3 4 5 6 8 9 10 11 12 13 14 15.
acpi_button1: on acpi0
atkbdc0: port 0x64,0x60 irq 1 on acpi0
atkbd0: flags 0x1 irq 1 on atkbdc0
kbd0 at atkbd0
psm0: irq 12 on atkbdc0
psm0: model MouseMan+, device ID 0
fdc0: port 0x3f7,0x3f2-0x3f5
irq 6 drq 2 on acp
Re: USB and Kodak DC4800 Camera
Marc Butler wrote: On Thu, Jan 02, 2003 at 02:11:16PM +0100, Michael Class wrote: >Hello, > >I am facing a problem that my Kodak DC4800 Camera is not recognized by a >current FreeBSD-current system (I do not have release systems around, so >I can not test aginst them, but I suspect that it would not work their >either) (and yes, it works on the same system with L***x and W*e :-( > >I have compiled a kernel with USB_DEBUG and switched on debugging. The >result from a connection of the camera to the system and a deconnect is >in the enclosed errorlog. Anyone here able to interpret this? > Michael, I'm not absolutely certain, but I believe the Kodak DC4800 Camera uses the Picture Transfer Protocol. I'm not sure it will be recognized as a storage device, however I have no experience with current and this particular issue. You may also want to make sure that the camera is plugged in or in it's cradle. The attempts to reset port 2 in your error output may indicate the device is not responding; it seems to be with a lot of these devices that they need external power when connected to the computer. (I'm not very confident in this as you state it works withWindows and Linux, and I assume it is the same setup.) Thank you for the answer! Yes, I can download pictures without additional power on Windows and Linux, so this does not seem to be the problem. Yes the device uses the PTP protocol. I do not expect it to appear as umass. But: I want to see it as ugen, so that higher level programs can access it. On Lx I am using jPhoto (a java program using libusb) to access the camera via PTP. And now I have read that recent versions of gphoto2 have PTP support too. But unfortunately our USB support drops the device totally, so I am stuck here. (Any yes I have, for obvious reasons, not yet tested if these programs work on FreeBSD) Michael -- --------- michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB and Kodak DC4800 Camera
Hello, I am facing a problem that my Kodak DC4800 Camera is not recognized by a current FreeBSD-current system (I do not have release systems around, so I can not test aginst them, but I suspect that it would not work their either) (and yes, it works on the same system with L***x and W*e :-( I have compiled a kernel with USB_DEBUG and switched on debugging. The result from a connection of the camera to the system and a deconnect is in the enclosed errorlog. Anyone here able to interpret this? The system uses uhci (VIA chipset): uhci0: port 0xcc00-0xcc1f irq 12 at device 7.2 on pc i0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered uhci1: port 0xd800-0xd81f irq 12 at device 7.3 on pc i0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered Any help would be nice. Btw. is there a special mailinglist for USB? Michael -- - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - Jan 2 13:34:35 pc-micha kernel: usb_needs_explore Jan 2 13:34:35 pc-micha kernel: usb_event_thread: woke up Jan 2 13:34:35 pc-micha kernel: usb_discover Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control type=0xa3 request=00 Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control type=0xa3 request=00 Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control type=0x23 request=01 Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control: UR_CLEAR_PORT_FEATURE port=2 feature=17 Jan 2 13:34:35 pc-micha kernel: uhub0: port error, restarting port 2 Jan 2 13:34:35 pc-micha kernel: uhub0: port error, giving up port 2 Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control type=0x23 request=01 Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control: UR_CLEAR_PORT_FEATURE port=2 feature=16 Jan 2 13:34:35 pc-micha kernel: usb_needs_explore Jan 2 13:34:35 pc-micha kernel: usb_event_thread: woke up Jan 2 13:34:35 pc-micha kernel: usb_discover Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control type=0xa3 request=00 Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control type=0xa3 request=00 Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control type=0x23 request=01 Jan 2 13:34:35 pc-micha kernel: uhci_root_ctrl_control: UR_CLEAR_PORT_FEATURE port=2 feature=16 Jan 2 13:34:36 pc-micha kernel: uhci_root_ctrl_control type=0x23 request=03 Jan 2 13:34:36 pc-micha kernel: usb_needs_explore Jan 2 13:34:36 pc-micha kernel: uhci port 2 reset, status = 0x0495 Jan 2 13:34:36 pc-micha kernel: usbd_reset_port: port 2 reset done, error=NORMAL_COMPLETION Jan 2 13:34:36 pc-micha kernel: uhci_root_ctrl_control type=0xa3 request=00 Jan 2 13:34:36 pc-micha kernel: uhci_root_ctrl_control type=0x23 request=01 Jan 2 13:34:36 pc-micha kernel: uhci_root_ctrl_control: UR_CLEAR_PORT_FEATURE port=2 feature=20 Jan 2 13:34:36 pc-micha kernel: uhci_root_ctrl_control type=0xa3 request=00 Jan 2 13:34:36 pc-micha kernel: usbd_new_device bus=0xc615e000 port=2 depth=1 speed=2 Jan 2 13:34:36 pc-micha kernel: usbd_setup_pipe: dev=0xc65eb900 iface=0 ep=0xc65eb924 pipe=0xc65eb904 Jan 2 13:34:36 pc-micha kernel: uhci_open: pipe=0xc664a980, addr=0, endpt=0 (1) Jan 2 13:34:36 pc-micha kernel: usbd_get_desc: type=1, index=0, len=8 Jan 2 13:34:36 pc-micha kernel: uhci_device_control type=0x80, request=0x06, wValue=0x0100, wIndex=0x len=8, addr=0, endpt=0 Jan 2 13:34:36 pc-micha kernel: uhci_alloc_std_chain: addr=0 endpt=0 len=8 speed=2 flags=0x2 Jan 2 13:34:36 pc-micha kernel: uhci_alloc_std_chain: maxp=8 ntd=1 Jan 2 13:34:36 pc-micha kernel: uhci_alloc_std_chain: nexttog=0 Jan 2 13:34:36 pc-micha kernel: uhci_device_request: before transfer Jan 2 13:34:36 pc-micha kernel: TD(0xc61a4f00) at 007f8f00 = link=0x007f8ec4 status=0x1880 token=0x00e0002d buffer=0x022eb390 Jan 2 13:34:36 pc-micha kernel: 7f8ec4 1880,errcnt=3,actlen=1 pid=2d,addr=0,endpt=0,D=0,maxlen=8 Jan 2 13:34:36 pc-micha kernel: TD(0xc61a4ec0) at 007f8ec0 = link=0x007f8ee4 status=0x188003ff token=0x00e80069 buffer=0x022eb160 Jan 2 13:34:36 pc-micha kernel: 7f8ee4 188003ff,errcnt=3,actlen=0 pid=69,addr=0,endpt=0,D=1,maxlen=8 Jan 2 13:34:36 pc-micha kernel: TD(0xc61a4ee0) at 007f8ee0 = link=0x0001 status=0x1980 token=0xffe800e1 buffer=0x Jan 2 13:34:36 pc-micha kernel: 1 1980,errcnt=3,actlen=1 pid=e1,addr=0,endpt=0,D=1,maxlen=0 Jan 2 13:34:36 pc-micha kernel: uhci_add_ctrl: sqh=0xc6159f00 Jan 2 13:34:36 pc-micha kernel: uhci_enter_ctl_q: follow from [0] Jan 2 13:34:36 pc-micha kernel: TD(0xc615cfc0) at 00730fc0 = link=0x0072ff62 status=0x0200 token=0x buffer=0x
sym0 not working any more / Interrupt problem
Hello, with a current current kernel, my system can not allocate an interrupt for an symbios 875 SCSIcontroller any more. This worked (without any changes on the hardware inbetween with a kernel from Dec 2nd.) Enclosed is the complete dmesg output. Any hints what I could try? Michael -- - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - 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: Sat Dec 21 12:00:24 MET 2002 [EMAIL PROTECTED]:/usr/src/sys/i386/compile/MCSMP2 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0552000. Preloaded elf module "/boot/kernel/acpi.ko" at 0xc05520a8. Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (996.55-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x68a Stepping = 10 Features=0x383fbff real memory = 1073676288 (1023 MB) avail memory = 1037541376 (989 MB) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00178011, at 0xfec0 Initializing GEOMetry subsystem Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface acpi0: on motherboard ACPI-0625: *** Info: GPE Block0 defined as GPE0 to GPE15 Using $PIR table, 8 entries at 0xc00f7530 acpi0: power button is handled as a fixed feature programming model. Timecounter "ACPI-fast" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0 acpi_cpu0: on acpi0 acpi_cpu1: on acpi0 acpi_tz0: on acpi0 acpi_button0: on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 agp0: mem 0xe000-0xe3ff at device 0.0 on pci0 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 0xcc00-0xcc1f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ulpt0: Hewlett-Packard DeskJet 990C, rev 1.10/1.00, addr 2, iclass 7/1 ulpt0: using bi-directional mode uhci1: port 0xd800-0xd81f irq 10 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered uhub1: port error, restarting port 1 uhub1: port error, giving up port 1 uhub1: port error, restarting port 2 uhub1: port error, giving up port 2 pci0: at device 7.4 (no driver attached) xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xc800-0xc87f mem 0xde80-0xdeff irq 9 at device 9.0 on pci0 xl0: Ethernet address: 00:10:5a:d7:dd:9c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcm0: port 0xc400-0xc41f irq 5 at device 10.0 on pci0 bktr0: mem 0xdedfe000-0xdedfefff irq 10 at device 11.0 on pci0 bktr0: Hauppauge Model 61344 D121 bktr0: Detected a MSP3410D-B4 at 0x80 bktr0: Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, remote control. pci0: at device 11.1 (no driver attached) sym0: <875> port 0x82000134-0x82000137,0xdffe-0xdffe00ff mem 0xf1020-0xf103f,0xdfffe000-0xdfffefff,0xdf00-0xdfff at device 12.0 on pci0 sym0: failed to allocate IRQ resource device_probe_and_attach: sym0 attach returned 6 acpi_button1: on acpi0 atkbdc0: port 0x64,0x60 irq 1 on acpi0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model MouseMan+, device ID 0 fdc0: port 0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 sio0 port 0x3f8-0x3ff irq 4 on acpi0 sio0: type 16550A sio1 port 0x2f8-0x2ff irq 3 on acpi0 sio1: type 16550A ppc0 port 0x778-0x77b,0x378-0x37f irq 7 drq 3 on acpi0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port orm0: at iomem 0xc-0xc7fff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 Timecounters tick every 10.000 msec APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intp
Re: GEOM and SCSI-cd: mount not working any more / fix
Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Michael Class writes:
>
>
>>>Can I get you to insert printfs like the one below all places
>>>in vfs_mount.c and cd9660_vfsops.c where you see it using EINVAL
>>>and try to find out which particular one it is ?
>>>
>>> printf("EINVAL HERE %s %d\n", __FILE__, __LINE__):
>>>
>>
>>It is in cd9660_vfsops.c in iso_mountfs at line 340.
>
>
> That sounds really odd in my ears.
>
> The only think I can think off is if there is a block-size
> conversion issue I have overlooked.
>
> Can you try in line 1372 of scsi_cd.c to change:
> /* lba */ bp->bio_blkno,
> to
> /* lba */ bp->bio_blkno / 4,
>
> and see if that helps ?
Hello Poul,
Yes this solves the problem!
Thanks a lot for the fast response.
Michael
--
-
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
GEOM and SCSI-cd: mount not working any more
Hello, just another input for a current system (with GEOM): now it seems inpossible for me to mount a SCSI-CD pc-micha:/# mount -t cd9660 /dev/cd0 /cdrom cd9660: /dev/cd0: Invalid argument Th system has two SCSI-CD-drives (a DVD and a CD-Burner) both have the same behavior. The CD is known to be o.k., as it can be mounted with a pre-GEOM kernel or with Lx. This is the dmesg fragment for the drives: cd0 at sym0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at sym0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed Michael -- - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
xl networking not working any more!
Hello, after the recent changes in if_xl.c (from rev. 1.106 to 1.107) my 3COM 3C905B interface card does not work any more. It is still recognized and the interface comes up, but the media is not detected any more: ifconfig xl0 (with if_xl.c rev. 1.107): xl0: flags=8943 mtu 1500 options=3 inet 172.16.81.200 netmask 0xff00 broadcast 172.16.81.255 inet6 fe80::210:5aff:fed7:dd9c%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:d7:dd:9c media: Ethernet 100baseTX status: no carrier ifconfig xl0 (with if_xl.c rev. 1.106): xl0: flags=8943 mtu 1500 options=3 inet 172.16.81.200 netmask 0xff00 broadcast 172.16.81.255 inet6 fe80::210:5aff:fed7:dd9c%xl0 prefixlen 64 scopeid 0x1 ether 00:10:5a:d7:dd:9c media: Ethernet autoselect (100baseTX ) status: active pciconf -l | fgrep xl0 xl0@pci0:9:0: class=0x02 card=0x905510b7 chip=0x905510b7 rev=0x30 hdr=0x00 Michael -- - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: ATA errors on recent -current
tialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging IPsec: Initialized Security Association Processing. acpi_cpu: CPU throttling enabled, 16 steps from 100% to 6.2% --> at this point I am getting the panic with tagging enabled! ad0: 32634MB [66305/16/63] at ata0-master UDMA66 ad1: 43979MB [89355/16/63] at ata0-slave UDMA100 ad2: 32634MB [66305/16/63] at ata1-master UDMA66 Waiting 2 seconds for SCSI devices to settle (noperiph:sym0:0:-1:-1): SCSI BUS reset delivered. sa0 at sym0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 16) pass0 at sym0 bus 0 target 2 lun 0 pass0: Fixed Scanner SCSI-2 device pass0: 3.300MB/s transfers Mounting root from ufs:/dev/ad0s4a SMP: AP CPU #1 Launched! cd0 at sym0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-570 $ /dev/vmmon: Module vmmon: initialized xl0: promiscuous mode enabled vmnet1: promiscuous mode enabled cd1 at sym0 bus 0 target 5 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 10.000MB/s transfers (10.000MHz, offset 15) cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed On Sun, 14 Apr 2002, Alexander Leidinger wrote: > On 14 Apr, David W. Chapman Jr. wrote: > > I updated to -current today and am now getting these errors > > > > ad0: READ command timeout tag=1 serv=1 - resetting > > ata0: resetting devices .. ad0: invalidating queued requests > > done > > Turn off tagged queing. Søren knows about this error and tries to > reproduce it (but fails as far as I know). > > Bye, > Alexander. - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Recent USB problems
Hello, with current of yesterday everything seems to be ok for me again. But I do not see any reason for this (code has not changed inbetween). Michael Alexander Kabaev wrote: >>Sorry, no hint by my side, but I can report exactly the same problem >>on an Athlon-C System equipped with a VIA-KT133A chipset. >>(actually it has the same USB controller, so it was expectable) >> >>Riggs >> > I am seeing the same symptoms while using Microsoft USB mouse with >KT133A-based computer. In my case, initial probe for ums, uhid and then >ugen fails. This is not consistent, though. Sometimes, probe will report >failing ums attach, sometimes it will not even detect device as mouse >and will start probing uhid or even ugen instead. Later in the boot >process, right after the "Waiting for SCSI messages to settle" message, >ums gets probed again and this time it attaches and works flawlessly >100% of the time. > >To Unsubscribe: send mail to [EMAIL PROTECTED] >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Recent USB problems
Hello, after the following patch: joe 2002/02/15 16:51:26 PST Modified files: sys/dev/usb ohci.c uhci.c usb.h usb_subr.c usbdivar.h Log: Merge from NetBSD: Pave the way for USB2, by replacing 'lowspeed' with 'speed', so that it can take the values USB_SPEED_LOW, USB_SPEED_FULL or in time USB_SPEED_HIGH. my USB-mouse quits working. Normal dmesg output looks like this: uhci0: port 0xcc00-0xcc1f irq 12 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0: KYE Genius USB Wheel Mouse, rev 1.00/0.00, addr 2, iclass 3/1 ums0: 3 buttons and Z dir. uhci1: port 0xd800-0xd81f irq 12 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered Now the system pauses for approx. 15 second during boot and the output looks like this: uhci0: port 0xcc00-0xcc1f irq 12 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered << here pause >> usbd_new_device: addr=2, getting first desc failed uhub0: device problem, disabling port 1 uhci1: port 0xd800-0xd81f irq 12 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered The system is a dual PIII Gigabyte system with VIA-Chipset. Any hints? Michael To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
new module-references compile error
Hello current,
with source from today(Jan 12th, 9am CET) I am getting the following error
with a statically compiled kernel including:
# Enable Linux ABI emulation
options COMPAT_LINUX
options PSEUDOFS
options LINPROCFS
pc-micha:/sys/i386/compile/MCSMP2# make
linking kernel.debug
linprocfs.o: In function `linprocfs_donetdev':
/sys/i386/compile/MCSMP2/../../../compat/linprocfs/linprocfs.c(.text+0xfe9): undefined
reference to `linux_ifname'
*** Error code 1
Any hints?
Michael
-
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
USB and SMP
Hello, just a question. Has anyone usb-devices working on a current-smp (very recent current, but problem exists since I can remember) system? On my Abit VP6 (Via-Chipset) a USB-Mouse and USB-Printer do work fine if I boot a single-CPU kernel. With a SMP-Kernel I am getting messages like: Nov 10 15:53:38 pc-micha /boot/kernel/kernel: uhub0: device problem, disabling p ort 2 Nov 10 15:53:56 pc-micha /boot/kernel/kernel: uhub1: device problem, disabling p ort 2 and obviously the USB-Devices do not work. With a single CPU-Kernel usbdevs delivers pc-micha:/home/michaelc# usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev 0x0100 port 1 powered port 2 addr 2: self powered, config 1, DeskJet 990C(0x3304), Hewlett-Packard(0x03f0), rev 0x0100 Controller /dev/usb1: addr 1: self powered, config 1, UHCI root hub(0x), VIA(0x), rev 0x0100 port 1 addr 2: low speed, power 100 mA, config 1, Genius USB Wheel Mouse(0x0003), KYE(0x0458), rev 0x port 2 powered This is the dmesg-frgment from a single CPU-Kernel for usb: uhci0: port 0xc400-0xc41f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhci1: port 0xc800-0xc81f irq 10 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 ums0: KYE Genius USB Wheel Mouse, rev 1.00/0.00, addr 2, iclass 3/1 Any Ideas? Michael - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: boot() called on cpu #1 - hang
On Mon, 10 Sep 2001 [EMAIL PROTECTED] wrote:
> > Hello Tor,
> >
> > thank you for your quick response, unfortunately your patch did
> > not fix the problem.
>
>
> Your machine seems to hang too early for the patch to have any effect.
> (the patch affects a hang that occurs after the kernel has printed
> cpu reset called on cpu#1
> cpu_reset: Stopping other CPUs
> )
>
> > I have now tested a little bit more with the following sequence:
> >
> > boot machine to single-user
> > reboot
> >
> > I did this more then 10 times. It now got stuck every time
> > Approx. 8 time with
> >
> > boot() called on cpu #1
> > W
> >
> > And 3 times with
> >
> > boot() called on cpu #0
> > Wa
> >
> > or
> >
> > boot() called on cpu #0
> > Waiting (max
> >
> > It looks to me that the kernel-printf gets somehow stuck.
>
>
> Did you use -O2 when compiling the kernel ? That sometimes causes
> strange problems.
>
> The kernel doesn't appear do do much before printing the
>
> Waiting (max %d seconds) for system process `%s' to stop
>
> message in kproc_shutdown.
>
>
> boot() in /usr/src/sys/kern/kern_shutdown.c contains
>
> #ifdef SMP
> if (smp_active)
> printf("boot() called on cpu#%d\n", PCPU_GET(cpuid));
> #endif
> /*
> * Do any callouts that should be done BEFORE syncing the filesystems.
> */
> EVENTHANDLER_INVOKE(shutdown_pre_sync, howto);
>
>
> where the EVENTHANDLER_INVOKE macro expands to a lockmgr() call and
> invocation of the two events associated with shutdown_pre_sync:
>
> kproc_shutdown(bufdaemonproc, howto)
> kproc_shutdown(updateproc, howto)
>
> The normal output is
>
> Waiting (max 60 seconds) for system process `bufdaemon' to stop...stopped
> Waiting (max 60 seconds) for system process `syncer' to stop...stopped
>
> If the lockmgr lock for the event list is damaged, further damage
> elsewhere might occur due to the lockmgr call. If a debug printf
> before the lockmgr call in EVENTHANDLER_INVOKE() works while a debug
> printf after the lockmgr call isn't properly printed, then the
> probability for the problem being related to the lockmgr call is
> increased (cf. /usr/src/sys/sys/eventhandler.h)
>
> - Tor Egge
>
>
Hello Tor,
I have added a printf right before and after the lockmgr call in the
EVENTHANDLER_INVOKE() Macro in /usr/src/sys/sys/eventhandler.h.
But both of these printf do work! The output I am getting then is:
Boot() called on cpu #1
before lockmgr
after lockmgr
W
What else could I test?
Michael
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Re: boot() called on cpu #1 - hang
Hello Tor, thank you for your quick response, unfortunately your patch did not fix the problem. I have now tested a little bit more with the following sequence: boot machine to single-user reboot I did this more then 10 times. It now got stuck every time Approx. 8 time with boot() called on cpu #1 W And 3 times with boot() called on cpu #0 Wa or boot() called on cpu #0 Waiting (max It looks to me that the kernel-printf gets somehow stuck. Michael On Sun, 9 Sep 2001 [EMAIL PROTECTED] wrote: > > Hello, > > > > on a 5.0-current i386-SMP system of today I am still getting on about > > every second reboot the message: > > > > boot() called on cpu #1 > > W > > Try applying the enclosed patch. > > - Tor Egge > > > --------- michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
boot() called on cpu #1 - hang
0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present SMP: AP CPU #1 Launched! - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
recent acpi-autoloading results in panic during boot on SMP-System
0 at sym0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present SMP: AP CPU #1 Launched! - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: X in free(): error: recursive call.
Hello, I was running in the same problem early this year. Probably you have found my mails in the archive. Unfortunately I was not able solve the problem. I am running now 3.3.6 on my laptop (which furtunately supports the graphics chips that my laptop has). Just as a datapoint: My understanding of the problem is that it is really a problem of XFree (as opposed to FreeBSD) There seems to be a situation where malloc is called within a signal handler. It was explained to me that malloc cannot be recursively called. Therefore, if a signal interrupts Xfree when it is in the libc *alloc-functions, this can crash the server. The following trace shows this scenario: #0 0x2820a9e8 in kill () from /usr/lib/libc.so.5 #1 0x2825bb3d in abort () from /usr/lib/libc.so.5 #2 0x2825a682 in isatty () from /usr/lib/libc.so.5 #3 0x2825a6b0 in isatty () from /usr/lib/libc.so.5 #4 0x2825b6a6 in malloc () from /usr/lib/libc.so.5 #5 0x80d19ff in Xalloc (amount=16) at utils.c:1225 #6 0x80cc30c in TimerSet (timer=0x0, flags=0, millis=50, func=0x8788ef0, arg=0x88a0b00) at WaitFor.c:744 #7 0x87890fa in ?? () #8 0x878927d in ?? () #9 0x8788bf0 in ?? () #10 0x807da23 in xf86SigioReadInput (fd=7, closure=0x88a0b00) at xf86Events.c:1039 #11 0x8093d48 in xf86SIGIO (sig=23) at sigio.c:99 #12 0xbfbfffac in ?? () #13 0x2825b1b0 in isatty () from /usr/lib/libc.so.5 #14 0x2825b901 in realloc () from /usr/lib/libc.so.5 #15 0x80d1b18 in Xrealloc (ptr=0x8eb3000, amount=4096) at utils.c:1322 #16 0x80ceef4 in StandardReadRequestFromClient (client=0x8a0d100) at io.c:403 #17 0x80ac00c in Dispatch () at dispatch.c:438 #18 0x80bc395 in main (argc=3, argv=0xbfbffdc0, envp=0xbfbffdd0) at main.c:439 #19 0x806b31d in _start () My understanding is that the problem is with XFree using malloc in a signal-handler. Strange enough, my system at home (with a Matrox G400-Card and Xfree86-4.1.0) does not show this symptom. Michael On Tue, 31 Jul 2001, Michael Robinson wrote: > On Sun, Jul 29, 2001 at 04:38:06PM +0200, Sheldon Hearn wrote: > > On Sun, 29 Jul 2001 22:29:40 +0800, Michael Robinson wrote: > > > I'd like to get advice on which of the following courses of action to take: > > > > > > 1. Isolate and fix the problem. I would need some help here. > > > > Try a better-proven release of XFree86, namely 3.3.6. > > Based on my preliminary efforts to isolate the problem, it seems pretty > clear that A) the code path required to reach the error is not exposed by > the malloc API to applications (after all, how could an application call > "free" recursively?), and B) it likely has something to do with an overlooked > race condition in the thread safety retrofit of libc late last year. > > But, as was mentioned previously, XFree86 3.3.6 doesn't have the required > chip support for the Dell 5000e, so that's not an option, regardless. > > I welcome further suggestions, though. > > -Michael Robinson > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: problems with ps2-mouse with current
Hello, maybe it was the confg-changes, it simply happend during the last couple of days. Michael On Fri, 15 Jun 2001, Alexander Leidinger wrote: > On 15 Jun, Michael Class wrote: > > > after the recent linker_set-changes on my system the ps2-mouse > > I thought the recent change to config was the problem (forgetting the > hints also disables the mouse). > > > is not working any more. It seems that a second (virtual ;-) > > keyboard is detected (atkbd1) and that this messes up things. > --------- michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
problems with ps2-mouse with current
Hello all, after the recent linker_set-changes on my system the ps2-mouse is not working any more. It seems that a second (virtual ;-) keyboard is detected (atkbd1) and that this messes up things. I can reproduce this with a GENERIC-kernel (output of dmesg is appended). The system is a dual-prox ABIT VP6 with VIA-Chipset. Any ideas? Micha Copyright (c) 1992-2001 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: Fri Jun 15 09:46:42 MEST 2001 [EMAIL PROTECTED]:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 998363727 Hz CPU: Pentium III/Pentium III Xeon/Celeron (998.36-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x686 Stepping = 6 Features=0x383fbff real memory = 671023104 (655296K bytes) avail memory = 646905856 (631744K bytes) Preloaded elf kernel "kernel" at 0xc056f000. Pentium Pro MTRR support enabled WARNING: Driver mistake: destroy_dev on 154/0 Using $PIR table, 8 entries at 0xc00fdbc0 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 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xc000-0xc00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xc400-0xc41f irq 10 at device 7.2 on pci0 usb0: on uhci0 usb0: USB revision 1.0 uhub0: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ulpt0: Hewlett-Packard DeskJet 990C, rev 1.10/1.00, addr 2, iclass 7/1 uhci1: port 0xc800-0xc81f irq 10 at device 7.3 on pci0 usb1: on uhci1 usb1: USB revision 1.0 uhub1: VIA UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub1: 2 ports with 2 removable, self powered pci0: at 7.4 (no driver attached) pci0: at 9.0 (no driver attached) pci0: at 9.1 (no driver attached) sym0: <810> port 0xd400-0xd4ff mem 0xda003000-0xda0030ff irq 5 at device 10.0 on pci0 sym0: No NVRAM, ID 7, Fast-10, SE, parity checking pci0: at 12.0 (no driver attached) pci0: at 12.1 (no driver attached) xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd800-0xd87f mem 0xda002000-0xda00207f irq 11 at device 13.0 on pci0 xl0: Ethernet address: 00:10:5a:d7:dd:9c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: port 0xec00-0xecff,0xe800-0xe803,0xe400-0xe407,0xe000-0xe003,0xdc00-0xdc07 irq 11 at device 14.0 on pci0 ata2: at 0xdc00 on atapci1 ata3: at 0xe400 on atapci1 orm0: at iomem 0xc-0xc7fff,0xc8000-0xcb7ff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 atkbd1: flags 0x1 irq 1 on atkbdc0 kbd1 at atkbd1 psm1: unable to allocate the IRQ resource (12). 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 pmtimer0 on isa0 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode 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 fdc1: cannot reserve I/O port range ppc1: parallel port not found. 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: 32634MB [66305/16/63] at ata0-master tagged UDMA66 ad4: 43979MB [89355/16/63] at ata2-master tagged UDMA100 ad6: 32634MB [66305/16/63] at ata3-master tagged UDMA66 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/ad0s4a cd0 at sym0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 8) cd0: cd present [335988 x 2048 byte records] linprocfs registered IP packet filtering initialized, divert disabled, rule-based forwarding disabled, default to deny, logging disabled lock order reversal 1st 0xc04dfee0 mntvnode @ ../../ufs/ffs/ffs_vfsops.c:1007 2nd 0xd667e10c vnode interlock @ ../../ufs/ffs/ffs_vfsops.c:1016 link_elf: symbol linux_ioctl_register_handler undefined link_elf: symbol linux_ioctl_register_handler undefined xl0: promiscuous mode enabled vmnet1: promiscuous mode enabled - michael class, viktor-renner str. 39, 72074 tuebingen, frg
malloc not recurseable?
Hello, on a FBSD-5.0-current (as of yesterday) system I am having a question about the way malloc works. The manpage states that malloc cannot be recursed. Does this mean that our malloc is not thread safe? I checked the manpage on HPUX and there it explicitely states that malloc is thread-safe. The reason I am asking is that my X-Server is crashing randomly (not very often though, approx. once a day) with the following trace: (This is XFree86-4.0.3 from ports) #0 0x2820a9e8 in kill () from /usr/lib/libc.so.5 #1 0x2825bb3d in abort () from /usr/lib/libc.so.5 #2 0x2825a682 in isatty () from /usr/lib/libc.so.5 #3 0x2825a6b0 in isatty () from /usr/lib/libc.so.5 #4 0x2825b6a6 in malloc () from /usr/lib/libc.so.5 #5 0x80d19ff in Xalloc (amount=16) at utils.c:1225 #6 0x80cc30c in TimerSet (timer=0x0, flags=0, millis=50, func=0x8788ef0, arg=0x88acb00) at WaitFor.c:744 #7 0x87890fa in ?? () #8 0x878927d in ?? () #9 0x8788bf0 in ?? () #10 0x807da23 in xf86SigioReadInput (fd=7, closure=0x88acb00) at xf86Events.c:1039 #11 0x8093d48 in xf86SIGIO (sig=23) at sigio.c:99 #12 0xbfbfffac in ?? () #13 0x2825ad74 in isatty () from /usr/lib/libc.so.5 #14 0x2825afcd in isatty () from /usr/lib/libc.so.5 #15 0x2825b6f1 in malloc () from /usr/lib/libc.so.5 #16 0x80d19ff in Xalloc (amount=256) at utils.c:1225 #17 0x87578ac in ?? () #18 0x8757a98 in ?? () #19 0x8758f13 in ?? () #20 0x8759e26 in ?? () #21 0x80c8b6d in QueryFont (pFont=0x8c22a00, pReply=0xbfbfeba4, nProtoCCIStructs=256) at dixfonts.c:580 #22 0x80ad639 in ProcQueryFont (client=0x8b52d00) at dispatch.c:1388 #23 0x80ac045 in Dispatch () at dispatch.c:456 #24 0x80bc395 in main (argc=3, argv=0xbfbffdc0, envp=0xbfbffdd0) at main.c:439 #25 0x806b31d in _start () To me this looks like malloc is called in a signal-handler. But I am not sure, if this is the right interpretation. Any comments? TIA Michael ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newcard/cardbus instabilities
ryone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] >V I C T O R Y N O T V E N G E A N C E > > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > > ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
USB-Devices working on 5.0-current?
Hi, on the weekend I was trying to play with two USB-devices on my FBSD-5.0-current (cvsupped 3.2.2001) without success. The first device is a HP DeskJet 990-Printer that is recognized by the ulpt-driver. (Unfortunately I am here at work and do not have the dmesg-output at my hands, if needed I can deliver that tonight from home). When I try to send something to /dev/ulpt0, it hangs in the open for about 5 minutes and thats it. But usbdevs shows the device! The other device I tried was a Kodak DC4800-Camera. It is not displayed by usbdevs at all. (I know it is not supported, but there is a linux-java-program that supports it, that I hoped to port to FBSD). So my question right now is, has anyone USB-devices running on a 5.0-current SMP-system these days? I just wanted to make sure that I am not digging in already know problems. TIA Michael P.S. the system I am using is a SMP-System 2x350Mhz-PII on an Intel BX-Board (Gigabyte) using UHCI for USB. ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Network performance-problem
Matthew Thyer wrote: > > Michael Class wrote: > > i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM > > 3CCFE575CT Lancard (pc-cardbus) using the xl-driver. > > > Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas? > > Make sure you are running with the TCP/IP NewReno optimisation turned > off. There are bugs in the TCP/IP NewReno code that result in bad > packets and hence lots of retransmission with generally reduced network > performance. It seems that NewReno is switched on by default in current. Unfortunately switching off NewReno does not change the problem. In times of very high network-traffic I am still unable to use the network. The system does not even respond to a ping where as all other systems I have (HPUX 10.20, 11.0 and NT4) behave as expected: slow response-times, but still working and ping-able. At home I am using this Laptop in a 100MB-Network and am able to almost saturate the link without any problems. Could it be that this is just happening for multicast-packets (that's what the high network-traffic is)? Anything else I could check? TIA Michael -- _______ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division Phone: +49 7031 14-3707 Fax:+49 7031 14-4505 ___ Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen Managing Directors: Rainer Geissel (Chairman),Rainer Erlat, Heribert Schmitz, Hans-Jochen Lueckefett, Fritz Schuller Chairman of the Supervisory Board: Joerg Menno Harms Commercial register: Amtsgericht Boeblingen HRB 4081 ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Network performance-problem
Hello, i am seeing a problem with 5.0-current (from 14.12.00) and a 3COM 3CCFE575CT Lancard (pc-cardbus) using the xl-driver. It goes as follows: I am using the 3COM-card in a 10MB-switched network. Occasionally someone is doing big network installs via multicast IP-packets. This is done with almost the full 10MB-Bandwidth. On all the other computers I have, I do see a big network-performance degration during that times, but they are still somewhat usable. This is true for HPUX 10.20 , 11.0 and NT 4.0 machines. My Laptop (HP OB4150) unfortunately is network- wise totally blocked during these times. In addition I am getting messages like: xl0: watchdog timeout xl0: watchdog timeout xl0: no carrier - transceiver cable problem? xl0: watchdog timeout xl0: watchdog timeout xl0: no carrier - transceiver cable problem? Why behaves my FreeBSD-machines worse then the other boxes? Any Ideas? TIA Michael Attached are the Kernel-Config-file and the dmesg output. -- ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division Phone: +49 7031 14-3707 Fax:+49 7031 14-4505 ___ Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen Managing Directors: Rainer Geissel (Chairman),Rainer Erlat, Heribert Schmitz, Hans-Jochen Lueckefett, Fritz Schuller Chairman of the Supervisory Board: Joerg Menno Harms Commercial register: Amtsgericht Boeblingen HRB 4081 ___ Copyright (c) 1992-2000 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 #2: Thu Dec 14 11:13:18 CET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/MCOBTEST Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (397.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 201326592 (196608K bytes) avail memory = 191971328 (187472K bytes) Preloaded elf kernel "kernel" at 0xc03a5000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 6 entries at 0xc00fdf60 apm0: on motherboard apm0: found APM BIOS v1.2, connected at v1.2 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 vga_pci0: mem 0xfec0-0xfecf,0xfe80-0xfebf,0xfd00-0xfdff irq 9 at device 0.0 on pci1 pci1: at 0.1 (no driver attached) pccbb0: at device 4.0 on pci0 pccbb0: PCI Memory allocated: 1802 pci_cfgintr_unique: hard-routed to irq 10 pci_cfgintr: 0:4 INTA routed to irq 10 cardbus0: on pccbb0 pccard0: <16-bit PCCard bus> on pccbb0 pccbb1: at device 4.1 on pci0 pccbb1: PCI Memory allocated: 18021000 pci_cfgintr_unique: hard-routed to irq 10 pci_cfgintr: 0:4 INTB routed to irq 10 cardbus1: on pccbb1 pccard1: <16-bit PCCard bus> on pccbb1 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xfcf0-0xfcff at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: irq 10 at device 7.2 on pci0 uhci0: Could not map ports device_probe_and_attach: uhci0 attach returned 6 pci0: at 7.3 (no driver attached) 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: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 pmtimer0 on isa0 unknown: can't assign resources unknown: can't assign resources pcm0: at port 0x220-0x22f,0x530-0x537,0x388-0x38f,0x120-0x121 irq 5 drq 0,1 on isa0 unknown: can't assign resources unknown: can't assign resources IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging ata1-slave: ata_command: timeout waiting for intr ata1-slave: identify failed ad0: 9590MB [19485/16/63] at ata0-master UDMA33 acd0: DVD-ROM at ata1-master using PIO4 Mounting root from ufs:/dev/ad0s1a pccbb0: card inserted: event=0x, state=3820 pccbb0: pccbb_power: CARD_VCC_0V and CARD_VPP_0V [44] pccbb0: pccbb_power: CARD_VCC_3V and CARD_VPP_VCC [11] TUPLE: LINKTARGET [3]: 43 49 53 Manufacturer ID: 01015752 TUPLE: CONFIG_CB [6]: 03 01 00 00 00 00 TUPLE: CFTABLE_ENTRY_CB [13]: 41 9a 01 b5 1e 01 b5 1e 02 30 ff ff 0
Addendum: ES1370 not working on current
Hi,
I have just built a kernel with /usr/src/sys/dev/sound checked out
from "2000-10-25 00:00". With these files the Soundblaster PCI128
works. So it must be the changes on Oct 26th. that broke it for me.
Michael
-
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
No sound in current from ES1370
Hello, recent 5.0-current versions do not generate sound any more on my Soundblaster PCI128 (Ensoniq 1370-Chip). On a kernel build from sources from Oct. 17th everything was o.k. So I guess it must be the changes that went in on Oct. 26th. I will try to backout these. Anyways if someone wants to look into this, I have enclosed the kernel-config-file and the dmesg output. TIA Michael - michael class, viktor-renner str. 39, 72074 tuebingen, frg E-Mail: [EMAIL PROTECTED] Phone: +49 7031 14-3707 (work) +49 7071 81950 (private) - Copyright (c) 1992-2000 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 Oct 29 10:35:44 MET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/MCSMP Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Pentium II Xeon/Celeron (349.07-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping = 2 Features=0x183fbff real memory = 268369920 (262080K bytes) avail memory = 256327680 (250320K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee0 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee0 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec0 Preloaded elf kernel "kernel" at 0xc04a5000. Pentium Pro MTRR support enabled md0: Malloc disk Using $PIR table, 7 entries at 0xc00fde10 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 isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xf000-0xf00f at device 7.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0xd000-0xd01f irq 11 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 intpm0: port 0x5000-0x500f irq 9 at device 7.3 on pci0 intpm0: I/O mapped 5000 intpm0: intr IRQ 9 enabled revision 0 smbus0: on intsmb0 smb0: on smbus0 intpm0: PM I/O mapped 4000 pci0: at 8.0 irq 16 pcm0: port 0xd400-0xd43f irq 17 at device 9.0 on pci0 xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xd800-0xd87f mem 0xe2003000-0xe200307f irq 18 at device 10.0 on pci0 xl0: Ethernet address: 00:10:5a:d7:dd:9c miibus0: on xl0 xlphy0: <3Com internal media interface> on miibus0 xlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto bktr0: mem 0xe200-0xe2000fff irq 19 at device 11.0 on pci0 bti2c0: iicbb0: on bti2c0 iicbus0: on iicbb0 master-only smbus1: on bti2c0 smb1: on smbus1 bktr0: Hauppauge Model 61344 D121 bktr0: Detected a MSP3410D-B4 at 0x80 bktr0: Hauppauge WinCast/TV, Philips FR1216 PAL FM tuner, msp3400c stereo, remote control. pci0: (vendor=0x109e, dev=0x0878) at 11.1 irq 19 ahc0: port 0xdc00-0xdcff mem 0xe2002000-0xe2002fff irq 16 at device 12.0 on pci0 aic7895C: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0xe000-0xe0ff mem 0xe2004000-0xe2004fff irq 16 at device 12.1 on pci0 aic7895C: Wide Channel B, SCSI Id=7, 32/255 SCBs 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: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> 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 ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus0 lpt0: Interrupt-driven port unknown: can't assign resources atspeaker0: at port 0x61 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 APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging ad0: 32253MB [65531/16/63] at ata0-master tagged UDMA33 ad1: 32253MB [65531/16/63] at ata1-master tagged UDMA33 Waiting 10 seconds for SCSI devices to settle vinum: loaded Mounting root from ufs:/dev/ad0s1a da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s tra
Re: Neomagic Sounddriver hangs HP OB4150
On Mon, 10 Jan 2000, Bill Fumerola wrote: > On Mon, 10 Jan 2000, #Michael Class wrote: > > > The Laptop is equipped with the following Neomagic-Chip: > > chip1: irq 10 at device 0.1 on pci1 > > > > The Stack-Backtrace looks exactly the same as the other mail mentioned. A > > little bit further digging into this shows me that on this Laptop every > > read access to the second memory-area of the chip in the range of 0x600-0x8ff > > brings the machine to a halt. I can read successfully from the areas with > > offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O > > Area starts at offset 0x600. This access brings the machine to a halt during > > boot. > > > > Any suggestions of what I could try? > > Try providing us with real data. The boot message you gave us is when > pcisupport.c matches it, not when neomagic. matches it. It is impossible > to recieve the above message and then have the neomagic code fall on > its face. I am sorry, but the obove message was just copied from a kernel without the neomagic driver to show which chip (256AX instead of 256 Zsomething) the Laptop has. It was not intended to be the message during boot with the new driver. Given the fact that someone else already gave an exact stack-backtrace which is identical of what I am getting (ac97_init calls nm_rd with an argument of 0x600 and size 2 which then does a bus_space_read2 where it hangs. (Names unfortunately not exact, I do have the code not at my hands)) I have not yet setup a serial console on this machine, so I am not able to provide you with the boot-messages of the kernel that hangs. Here is the bootmessage of the kernel without the neomagic-sound-driver (Jan 7th.) Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #0: Fri Jan 7 14:04:10 MET 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/MCOB4150 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Celeron (397.05-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x66a Stepping = 10 Features=0x183f9ff real memory = 201326592 (196608K bytes) avail memory = 191954944 (187456K bytes) Preloaded elf kernel "kernel" at 0xc02eb000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface apm0: on motherboard apm: found APM BIOS v1.2, connected at v1.2 pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 vga-pci0: irq 9 at device 0.0 on pci1 chip1: irq 10 at device 0.1 on pci1 pcic-pci0: at device 4.0 on pci0 pcic-pci1: at device 4.1 on pci0 isab0: at device 7.0 on pci0 isa0: on isab0 ata-pci0: at device 7.1 on pci0 ata-pci0: Busmastering DMA supported ata0 at 0x01f0 irq 14 on ata-pci0 ata1 at 0x0170 irq 15 on ata-pci0 pci0: Intel 82371AB/EB (PIIX4) USB controller (vendor=0x8086, dev=0x7112) at 7.2 irq 10 chip2: at device 7.3 on pci0 fdc0: at port 0x3f0-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-0x6f on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 psm0: irq 12 on atkbdc0 psm0: model Generic PS/2 mouse, device ID 0 vga0: at port 0x3b0-0x3df iomem 0xa-0xb on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=0x200> pcic0: at irq 3 on isa0 pccard0: on pcic0 pccard1: on pcic0 sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1: configured irq 3 not in bitmap of probed irqs 0 IP packet filtering initialized, divert enabled, rule-based forwarding enabled, default to accept, unlimited logging ad0: ATA-4 disk at ata0 as master ad0: 9590MB (19640880 sectors), 19485 cyls, 16 heads, 63 S/T, 512 B/S ad0: 16 secs/int, 1 depth queue, UDMA33 acd0: DVD-ROM drive at ata1 as master acd0: read 4134KB/s (4134KB/s), 128KB buffer, ??? acd0: Reads: CD-R, CD-RW, CD-DA stream, DVD-ROM, DVD-R acd0: Audio: play, 16 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked pccard: card inserted, slot 0 pccard: card inserted, slot 1 ata_command: timeout waiting for interrupt Mounting root from ufs:/dev/ad0s3a /dev/vmmon: Module vmmon: registered with major=200 minor=0 tag=$Name: build-364 $ /dev/vmmon: Module vmmon: initialized sio2 at port 0x3e8-0x3ef irq 7 slot 0 on pccard0 sio2: type 16550A ed0 at port 0x340-0x35f irq 11 slot 1 on pccard1 ed0: address 00:e0:98:03:a4:ad, type Linksys (16 bit) And here the kernel-configuration: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # http://www.FreeBSD
Neomagic Sounddriver hangs HP OB4150
Hello, as someone already has mentioned for another Laptop, the new Neomagic Audio-Driver (btw. thank you for creating one) hangs my HP Omnibook 4150 during boot. The Laptop is equipped with the following Neomagic-Chip: chip1: irq 10 at device 0.1 on pci1 The Stack-Backtrace looks exactly the same as the other mail mentioned. A little bit further digging into this shows me that on this Laptop every read access to the second memory-area of the chip in the range of 0x600-0x8ff brings the machine to a halt. I can read successfully from the areas with offset 0x0-0x5ff and 0x900-0xFFF. The Header-File states that the mixer-I/O Area starts at offset 0x600. This access brings the machine to a halt during boot. Any suggestions of what I could try? Michael ___ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division Phone: +49 7031 14-3707 Fax:+49 7031 14-4505 ___ Hewlett-Packard GmbH, PO Box 1430, Mailstop ESD2, 71004 Boeblingen Sitz der Gesellschaft: Böblingen, Amtsgericht Böblingen HRB 4081 Geschäftsführer: Jörg Menno Harms (Vorsitzender),Rainer Erlat, Hans-Joachim Lueckefett,Heribert Schmitz,Fritz Schuller ___ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: (vinum?) lockups in strategy routines?
Hello, just another datapoint. I just installed two new IBM DPTA-343740 discs into my System at home. They are configured with striping in vinum. Within a day I got two solid lockups with the new ata-drivers. After that I switchied to the old wd-driver. Everythings works fine since then. I do not have the exact configuration here. The system is at home and I am here at my workplace. The General setup is as follows: Gigabyte 6BXDS-MoBo with 2x350Mhz PII, 256MB-Ram, 2 SCSI-Disks, 2 DPTA 343740, each as master on a seperate (internal) IDE bus. No other IDE/ATAPI devices. Everything is on 4.0-current of (around) Oct. 22th. (Btw. I had to set the jumper that clips the disk-size to below 32GB on these drives to make the Gigabyte Mobo recognize them). If someone is interessted in more details, I will be able to send them when I am at home. Michael On Fri, 29 Oct 1999, Alfred Perlstein wrote: > > Anyone running -current as of Oct 28, 1999 getting lockups in > device strategy routines? > > I thought I'd be able to get a dump but it didn't work. > > Specifically I'm running vinum in striping mode and the new ata-drivers. > > 10 Aug 1999 14:27:51.389915 stripe /dev/da0e /dev/da1e > > A kernel from Wed Oct 6 seems fine (able to buildworld). _______ Michael ClassE-Mail: [EMAIL PROTECTED] E-Business Solution Division Phone: +49 7031 14-3707 Fax:+49 7031 14-4505 ___ Hewlett-Packard GmbH, PO Box 1430, Mailstop SERC2, 71004 Boeblingen To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
current state of if_ed.c
Hello,
as already someone mentioned on this list, pcmcia-cards don´t
work any more with the current ed-driver.
All the referenzes for NCARD habe been changed to:
#if NCARDxx > 0
(obviously with reason, the whole thing is in not compiling any more!)
First of all a small hint in the commit message about this would
have been helpfull!
And now my question: Is there a short-time cure planned, or is this
more like the breakage of pcmcia-modem cards that happend in april
which lasts now for half a year waiting for the newbus-pc-card
(cardbus???) integration?
Michael
-
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
current-APM causes panic on SMP-System
Hello,
since the apm-code was changed to use the generic bios-call interface
(dated around 1999/07/28) my FreeBSD-4.0-current system panics when I do
an "apmconf -e". This has not changed since then. I reproduced it with
a very current System (1999/08/25) today.
The system is a Dual-Proc GigaByte 6BXDS-MB with 2x350Mhz PII and 256MB-RAM.
For further information I have added the Config-File and dmesg-output.
When calling apmconf -e i am getting the following panic:
(written down by hand, so there might be some typos)
---
Fatal trap 12: page fault while in kernel mode
mp_lock=0102; cpuid=1; lapic.id=0100
fault virtual address = 0x8380
fault code = supervisor read, page not present
ip = 0x50:0x8380
stack = 0x10:0xff80df24
frame = 0x10:0xc02bde80
code= base 0xc00f, limit 0x, type 0x1b
= DPL 0, pres 1, def32 1, gran 0
proc flags = intr enabled, resume, iopl=0
current proc= idle
interrupt mask = <-- SMP: XXX
---
The Adress 0x8380 seems to be the one from the APM-BIOS-Call.
What can I do to track this further down?
Michael
-
michael class, viktor-renner str. 39, 72074 tuebingen, frg
E-Mail: [EMAIL PROTECTED]
Phone: +49 7031 14-3707 (work) +49 7071 81950 (private)
-
#
# SMP-GENERIC -- Smp machine with WD/AHx/NCR/BTx family disks
#
# For more information read the handbook part System Administration ->
# Configuring the FreeBSD Kernel -> The Configuration File.
# The handbook is available in /usr/share/doc/handbook or online as
# latest version from the FreeBSD World Wide Web server
# http://www.FreeBSD.ORG/>
#
# An exhaustive list of options and more detailed explanations of the
# device lines is present in the ./LINT configuration file. If you are
# in doubt as to the purpose or necessity of a line, check first in LINT.
#
# $Id: SMP-GENERIC,v 1.20 1998/10/22 13:49:51 bde Exp $
machine i386
cpu I686_CPU
ident MCSMP
maxusers64
#makeoptionsDEBUG=-g#Build kernel with gdb(1) debug symbols
# Create a SMP capable kernel (mandatory options):
options SMP # Symmetric MultiProcessor Kernel
options APIC_IO # Symmetric (APIC) I/O
# Optional, these are the defaults:
#optionsNCPU=2 # number of CPUs
#optionsNBUS=4 # number of busses
#optionsNAPIC=1 # number of IO APICs
#optionsNINTR=24# number of INTs
# Lets always enable the kernel debugger for SMP.
options DDB
# SMP shouldn't need x87 emulation, disable by default.
#optionsMATH_EMULATE#Support for x87 emulation
options INET#InterNETworking
options FFS #Berkeley Fast Filesystem
options FFS_ROOT#FFS usable as root device [keep this!]
options MFS #Memory Filesystem
options MFS_ROOT#MFS usable as root device, "MFS" req'ed
options NFS #Network Filesystem
options NFS_ROOT#NFS usable as root device, "NFS" req'ed
options MSDOSFS #MSDOS Filesystem
options CD9660 #ISO 9660 Filesystem
options CD9660_ROOT #CD-ROM usable as root. "CD9660" req'ed
options PROCFS #Process filesystem
options KERNFS
options COMPAT_LINUX
options COMPAT_43 #Compatible with BSD 4.3 [KEEP THIS!]
options SCSI_DELAY=1#Be pessimistic about Joe SCSI device
options UCONSOLE#Allow users to grab the console
#optionsFAILSAFE#Be conservative
options USERCONFIG #boot -c editor
options VISUAL_USERCONFIG #visual boot -c editor
# Enable the following (IPFIREWALL_VERBOSE optional) to enable the IP firewall
# code. This is used in conjunction with the ipfw(1) command. See the
# man page for more details.
options IPFIREWALL #firewall
options IPFIREWALL_VERBOSE #print information about
# dropped packets
options IPFIREWALL_FORWARD #enable xparent proxy support
#options IPFIREWALL_VERBOSE_LIMIT=1
