Just a follow up.
I've since been able to get my -CURRENT system running under the new build.
However the booting process is still slow around those ata?: [MPSAFE]
messages. Any ideas on getting a speed up?
-Al
___
[EMAIL PROTECTED] mailing list
It seems Alastair G. Hogge wrote:
Just a follow up.
I've since been able to get my -CURRENT system running under the new build.
However the booting process is still slow around those ata?: [MPSAFE]
messages. Any ideas on getting a speed up?
I'm working on it...
-Søren
Hi...
Sorry to do a me too, but I have a similar problem after a cvsup midday
on the 13th September. The previous kernel was pre-ATAng.
The machine panic'd after inserting a friends wireless PCMCIA card
(but that's probably another unrelated issue), rebooted and left
me in single user after
I've seen that too, although my problem was with my Alcatel Speedtouch
330 which routinely panics the system.
I'djust retrieved usr from a backup to get round it, and put it down to
the perils of -current, but if there is really a problem, I can
investigate further here.
Mark
Simon Brown
Hello list,
I've recently cvsup'd current (14th of Sep). After a build and install
world/kernel I rebooted to find some new and interesting kernel messages
about ata? MPSAFE. Well as the booting continued I notcied the machine was
going through more disk activity then usal. It was also taking
With a -current kernel ( cvsupped today ) I can no longer boot.
It hangs on the drives connected to the promis controller built into my
MSI KT266 mobo.
The messages are like
ad2: READ command timeout tag=0 serv=0 - resetting
Same for ad3. It tries falling back to pio mode but after that it
try hw.ata.ata_dma=0 in /boot/loader.conf to disable DMA, it is
currently broken but worked on
On Sat, 5 Apr 2003, Paul van der Zwan wrote:
With a -current kernel ( cvsupped today ) I can no longer boot.
It hangs on the drives connected to the promis controller built into my
MSI KT266 mobo.
It seems Dag-Erling Smorgrav wrote:
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
No tags, like you said. Previously, with a tags-capable kernel,
enabling tags would cause a continuous stream of timeouts and resets
on both disks.
Just for kicks, I removed the #if 0 in ata-disk.c and got
Scotty [EMAIL PROTECTED] writes:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
Disable tags (add hw.ata.tags=0 to /boot/loader.conf). Never worked
for me either (ASUS P5A, ALi M1543 southbridge, IBM DTTA and IC35L
disks)
DES
--
Dag-Erling Smorgrav - [EMAIL
It seems Dag-Erling Smorgrav wrote:
Scotty [EMAIL PROTECTED] writes:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
Disable tags (add hw.ata.tags=0 to /boot/loader.conf). Never worked
for me either (ASUS P5A, ALi M1543 southbridge, IBM DTTA and IC35L
Soeren Schmidt [EMAIL PROTECTED] writes:
Tags are disabled in -current in ata-disk.c so if the sources are
up to date that cannot be the problem.
Please update and then at least provide a dmesg if it still fails.
top-of-tree:
[EMAIL PROTECTED] /home/des# egrep '(ata|ad)[0-9]'
Dag-Erling Smorgrav [EMAIL PROTECTED] writes:
No tags, like you said. Previously, with a tags-capable kernel,
enabling tags would cause a continuous stream of timeouts and resets
on both disks.
Just for kicks, I removed the #if 0 in ata-disk.c and got exactly the
same symptoms as before:
Soeren Schmidt [EMAIL PROTECTED] writes:
It seems Dag-Erling Smorgrav wrote:
ad0: READ command timeout tag=0 serv=1 - resetting
ad0: invalidating queued requests
That why it is disabled, its not working for the time being.
For me, the time being == since it was introduced in the tree. It
On Tue, Mar 04, 2003 at 04:59:33PM +0100, Dag-Erling Smorgrav
[EMAIL PROTECTED] wrote:
Soeren Schmidt [EMAIL PROTECTED] writes:
It seems Dag-Erling Smorgrav wrote:
ad0: READ command timeout tag=0 serv=1 - resetting
ad0: invalidating queued requests
That why it is disabled, its not
I am getting the same
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
error messages, and disk io pauses when it resets the devices for around
3 seconds (estimated from mpg123 pause in play),
a brief description of my system until i reboot and submit a verbose
This morning I booted a kernel built last night, and it panicked when
trying to mount the root filesystem after this:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
ad0: removed from configuration
done
cvsup'd, built a new kernel, and now instead of a panic I get
It seems Wesley Morgan wrote:
This morning I booted a kernel built last night, and it panicked when
trying to mount the root filesystem after this:
ad0: READ command timeout tag=0 serv=0 - resetting
ata0: resetting devices ..
ad0: removed from configuration
done
cvsup'd, built a new
hello,
i couldnt decide from reading the list if there should or shouldnt
be problems with promise ata/100 controller with current.
anyway, i have problems with it.
i've tried several current versions from the devel snapshot to apr 22nd
and all of those fail after installation.
in the floppy
It seems mika ruohotie wrote:
hello,
i couldnt decide from reading the list if there should or shouldnt
be problems with promise ata/100 controller with current.
I dont think so...
anyway, i have problems with it.
i've tried several current versions from the devel snapshot to apr
On Wed, Apr 24, 2002 at 02:17:27PM +0200, Søren Schmidt wrote:
It seems mika ruohotie wrote:
i might be able to provide more information if this sounds like
something which shouldnt be happening. (trace, whatever needed)
That would be most helpfull, where does it panic, what is the
panic
On 8 Apr, David O'Brien wrote:
yesterday I've made a new world. After booting it, ld-elf-so.1 complains
about every library (libc, libutil, ...). My -current is not usable
anymore because of this.
Defined complains. freebsd-current readers should know to spend EXACT
error messages.
It seems Alexander Leidinger wrote:
Something about a missing or wrong ELF header. I thought it was a
general problem so everyone would see it, but it turned out to be a
problem in the ata driver. After turning off tagged queuing everything
was fine. I'm not the only one with problems with
On 9 Apr, Søren Schmidt wrote:
Søren, as a data point: a Mar 12 kernel was fine for me, a Mar 27 kernel
too, but a Apr 6-8 kernel spills alot of tag related errors (I think you
already have those errors from someone else, no need to repeat them
here) and goes into PIO mode after some time.
It seems Alexander Leidinger wrote:
On 9 Apr, Søren Schmidt wrote:
Søren, as a data point: a Mar 12 kernel was fine for me, a Mar 27 kernel
too, but a Apr 6-8 kernel spills alot of tag related errors (I think you
already have those errors from someone else, no need to repeat them
Wierd, I turned the computer off and turned it back on again and the
problem is solved... sorry bout that.
Ken
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
Maybe this is a silly suggestion, but could someone with a card like
that boot it in a Windows environment and tell us what that hardware
manager tells us about hardware requirements the card would have if it
is configured for the '0x160' address (whatever that configuration is
on the card I
On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote:
atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
isic0: Error allocating io at 0x160 for Teles S0/16.3!
While I was able to use the Teles
Jose Gabriel Marcelino wrote:
This obviously conflicts with the secondary IDE controller which lies at
0x170, however this has not been a problem till this day and no driver
complained about this. Now, with the newer kernel I get this:
atapci0: VIA 82C586 ATA33 controller port
Doug Rabson wrote:
atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
isic0: Error allocating io at 0x160 for Teles S0/16.3!
While I was able to use the Teles again by changing it's
On Sun, 20 Feb 2000, Hellmuth Michaelis wrote:
Doug Rabson wrote:
atapci0: VIA 82C586 ATA33 controller port 0xe000-0xe00f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170 irq 15 on atapci0
...
isic0: Error allocating io at 0x160 for Teles S0/16.3!
From the keyboard of Martin Husemann:
In case there is is already an IDE controller allocated at 0x170 and a
Teles 16.3 tries to allocate a range of 0x40 at 0x160 it cannot do so.
This is a PnP card, right?
No.
hellmuth
--
Hellmuth MichaelisTel +49
On Sat, Feb 19, 2000 at 10:39:42AM -0500, Bryan Liesner wrote:
Jose, the problem seems to be resolved by rebuilding the boot
loader. Or bypass the loader altogether.
cd /usr/src/sys/boot
make obj
make all install
and you'll be able to boot the kernel with the latest ata stuff.
Do
It seems Bryan Liesner wrote:
On Sat, 19 Feb 2000, Soren Schmidt wrote:
Have you rebuild your modules lately ??
-Søren
Yes. My world is current as of a few hours ago. I did a make world
right after finding out about the loader problem to rule that
possibility out. The disk probes
Hi again,
After remaking the loader (unnecessary since it's still broken), I've
removed my KLDs from loader.conf (I was loading a splash screen) and it
now boots as Bryan noticed.
However it seems another problem showed up, and I'm not sure where the
problem is.
I have a Teles ISDN card on
On Sat, 19 Feb 2000, Philipp Mergenthaler wrote:
On Sat, Feb 19, 2000 at 10:39:42AM -0500, Bryan Liesner wrote:
Jose, the problem seems to be resolved by rebuilding the boot
loader. Or bypass the loader altogether.
cd /usr/src/sys/boot
make obj
make all install
and you'll be able to
It seems Bryan Liesner wrote:
Do you use KLMs?
Yes, I do! I was loading a screen saver with the boot loader. And
now I see I am wrong about rebuilding the loader! When I had success
loading the kernel directly, I moved loading the screensaver into
rc.conf instead. Then I thought that
On Sat, 19 Feb 2000, Soren Schmidt wrote:
Have you rebuild your modules lately ??
-Søren
Yes. My world is current as of a few hours ago. I did a make world
right after finding out about the loader problem to rule that
possibility out. The disk probes still fail when loading today's
On Sat, 19 Feb 2000, Soren Schmidt wrote:
It seems Bryan Liesner wrote:
The latest ata commits left my system completely unbootable. No disks
were probed.
He, you always seem to be lucky when I change something :)
I always hold my breath when I cvsup and see changes to ata*:)
Hmm,
It seems Bryan Liesner wrote:
On Sat, 19 Feb 2000, Soren Schmidt wrote:
It seems Bryan Liesner wrote:
The latest ata commits left my system completely unbootable. No disks
were probed.
He, you always seem to be lucky when I change something :)
I always hold my breath when I
hi Soren,
The latest ata commits left me unbootable too, the patch you provided
below didn't help this too. I have a very different configuration from
Bryan's (much simpler too):
- DFI K6XV3+ mb with VIA MVP3 chipset
ata-pci0: VIA 82C586 ATA-33 controller port 0xe000-0xe00f at device 7.1
on
It seems Jose Gabriel Marcelino wrote:
Well, rebuild the loader, that helped Bryan, apparently it has
nothing to do with the ata driver
The latest ata commits left me unbootable too, the patch you provided
below didn't help this too. I have a very different configuration from
Bryan's
On Sat, 19 Feb 2000, Jose Gabriel Marcelino wrote:
hi Soren,
The latest ata commits left me unbootable too, the patch you provided
below didn't help this too. I have a very different configuration from
Bryan's (much simpler too):
Jose, the problem seems to be resolved by rebuilding the boot
The latest ata commits left my system completely unbootable. No disks
were probed.
I have on the motherboard's Alladin controller:
HP 4x4x24 CD burner as master primary channel
40x CD as slave primary channel
HP Colorado 8 Gig ATAPI tape as master secondary channel
On a Promise Ultra66:
WDC
I am still having problems with the ATA driver.
I am seeing the same error messages as has been reported on the lists during
the last few weeks, both on i386 and alpha platforms.
On the i386, the problem is just an irritating itch, but it seems to be
far more serious on the alpha, where the
It seems Erik H. Bakke wrote:
I am still having problems with the ATA driver.
I am seeing the same error messages as has been reported on the lists during
the last few weeks, both on i386 and alpha platforms.
On the i386, the problem is just an irritating itch, but it seems to be
far more
45 matches
Mail list logo
