ing, then built.
Between that and the 1.9 version of ata-queue.c, both of the problems
(the hang with ata1: resetting and the hang if atapicam is defined
in the kernel) I had been reporting have been cleared up.
Now if I could just get this darned T30 to sleep properly, all
Dnia Mon, Oct 13, 2003 at 02:51:43PM -0700, Lee Damon napisal:
> > Anyone tried going forward to 1.8?
>
> I just tried 1.8, it did not fix the problem. Symtoms are still the same,
I use 1.8 and is working without problem.
--
Jacek Serwatynski <[EMAIL PROTECTED]> | PGP_key: www.trynet.eu.org/pub
> Anyone tried going forward to 1.8?
I just tried 1.8, it did not fix the problem. Symtoms are still the same,
> > ad0: 35174MB [71465/16/63] at ata0-master UDMA100
> > ata1: resetting devices ..
> > done
Going back to 1.6 (apparently) does fix the problem.
nomad
t; ad0: 35174MB [71465/16/63] at ata0-master UDMA100
> > ata1: resetting devices ..
> > done
> >
> > Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e.
> > reverting to version 1.6) makes the problem go away.
>
> I upgraded from an Oct 1 ->
From: "Rob MacGregor" <[EMAIL PROTECTED]>
Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to
confirm that that's the last working version for me too.
Backing out to 1.6 fixes the problem for me too...
Please DO NOT send me ANY email directly unless it's a privacy issue.
From: "Steve Ames" <[EMAIL PROTECTED]>
Anyone tried going forward to 1.8?
Same result for me as with 1.7. I've just grabbed 1.6 and am rebuilding to
confirm that that's the last working version for me too.
Please DO NOT send me ANY email directly unless it's a privacy issue.
Reply-to man
> > > Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e.
> > > reverting to version 1.6) makes the problem go away.
> >
> > I upgraded from an Oct 1 -> Oct 12 kernel and saw the same hang.
> > Backing out r1.6 fixed it for me too.
> >
> "me too"
Anyone tried going forward to 1.8?
gt;
> > ad0: 35174MB [71465/16/63] at ata0-master UDMA100
> > ata1: resetting devices ..
> > done
> >
> > Backing out the most recent checkin to sys/dev/ata/ata-queue.c (i.e.
> > reverting to version 1.6) makes the problem go away.
>
> I upgraded from an
In the last episode (Oct 08), Robert Ferguson said:
> I see this problem as well. I'm running on a T40, with a DVD/CDRW in
> the ultrabay, and -CURRENT as of this morning. At boot, it hangs
> immediately after
>
> ad0: 35174MB [71465/16/63] at ata0-master UDMA100
>
I see this problem as well. I'm running on a T40, with a DVD/CDRW in
the ultrabay, and -CURRENT as of this morning. At boot, it hangs
immediately after
ad0: 35174MB [71465/16/63] at ata0-master UDMA100
ata1: resetting devices ..
done
Backing out the most recent checkin to sys/dev/at
MA100
ata1: resetting devices ..
done
Then it hangs so hard I have to power cycle it to get the system to notice
me.
The hang does not happen if the DVD/CD-RW drive is pulled from the system.
Booting an old kernel (previous to this problem) and searching the logs, I see:
O
On Tue, Sep 09, 2003 at 08:37:17PM +0300, Lefteris Chatzibarbas wrote:
> [...]
>
> Most of the time the CDRW drive is not detected and I get:
>
> [...]
After today's commit to src/sys/dev/ata/ata-lowlevel.c (1.11 2003/09/10
09:57:16 sos), the ata1-slave CDRW is alway
On Tue, Sep 09, 2003 at 06:00:12PM +, Jens Rehsack wrote:
> I detected a similar problem with yesterdays current, but giving
> it a chance I detected I a had a loosely cable.
?!
I had checked the cables and they are fine.
I should add, that I have this problem for almost a week (since I adde
Lefteris Chatzibarbas wrote:
Hello,
I have the following units on a MSI KT4V (KT400/VT8235) motherboard
(80pin cable is used for both primary and secondary controller):
ata0-master: WDC WD800JB ATA-6 disk
ata0-slave:
ata1-master: TEAC DV-516E DVDROM drive
ata1-slave: TEAC CD-W524E
Hello,
I have the following units on a MSI KT4V (KT400/VT8235) motherboard
(80pin cable is used for both primary and secondary controller):
ata0-master: WDC WD800JB ATA-6 disk
ata0-slave:
ata1-master: TEAC DV-516E DVDROM drive
ata1-slave: TEAC CD-W524E CDRW drive
For about a week
up on things. After a make world and a kernel upgrade
today, the floppy works again. (Thaks, Soren!) But, there is a new fun spot:
this time on ata1.
If I attempt to mount a CD (the CD-ROM is on ata1 as master) then it
produces an instant panic (page fault.) (Up till now it just "simply&qu
It seems Donn Miller wrote:
> In article <[EMAIL PROTECTED]> you wrote:
>
>
> > I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
>
> What's up with the fdc driver? I'm seeing the exact same thing. There was
> never any heads-up about this. Surely, the person who broke
t v1.2
npx0: on motherboard
npx0: INT 16 interface
pcib0: on motherboard
pci0: on pcib0
isab0: at device 1.0 on pci0
isa0: on isab0
atapci0: port
0xd000-0xd00f,0xd400-0xd403,0xd800-0xd807,0xe000-0xe003,0xe400-0xe407 irq 11 at device
1.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata1: at 0x170
On Fri, Sep 22, 2000 at 09:48:42AM -0500, Mark Hittinger wrote:
>
> I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
I am also seeing this with a kernel and world from today... also, are there
any issues with mount_cd9660? When I issue the following command:
# mount -t c
I am also seeing the fdc0 problem "fdc0: cannot reserve I/O port range".
The same kernel that I began to see the fdc0 problems I also lost the ability
to use devices on ata1. Ata1 seems to probe OK but I get I/O errors on the
ata1 drives all of a sudden. A kernel from a week ago is
It seems Klaus Herrmann wrote:
>
> ad0: 6197MB [12592/16/63] at ata0-master using UDMA33
> [ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1]
> [ata1-master: success setting up WDMA2 mode on VIA chip]
> ata1-master: CDROM device - NO DRIVER!
>
> Fatal trap 12
> > options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices
>
> Try removing this. According to the warning in LINT, this breaks many
> CDROMs.
>
i alreadya tried that - no change. as said, this crash appears even when
booting from boot floppies or generic.
regards,
Klaus
--
4.0-dmesg:
ad0: 6197MB [12592/16/63] at ata0-master using UDMA33
[ata1-master: piomode=4 dmamode=2 udmamode=-1 dmaflag=1]
[ata1-master: success setting up WDMA2 mode on VIA chip]
ata1-master: CDROM device - NO DRIVER!
Fatal trap 12: page fault while in kernel mode
the lines in [bracke
On Sat, 5 Feb 2000, Klaus Herrmann wrote:
> options ATA_ENABLE_ATAPI_DMA#Enable DMA on ATAPI devices
Try removing this. According to the warning in LINT, this breaks many
CDROMs.
Kris
"How many roads must a man walk down, before you call him a man?"
"Eight!"
"That was a rhetoric
>
> I just upgraded my 3.4-Stable system to a 4.0-current. It is running fine
> - with one exeption: the kernel seems to have problems with my 2nd ide/ata
> controller. when it is enabled, the system displays at boot time that it
> cannot find a driver vor the CDROM-Drive on ata1.
>
Hello!
I just upgraded my 3.4-Stable system to a 4.0-current. It is running fine
- with one exeption: the kernel seems to have problems with my 2nd ide/ata
controller. when it is enabled, the system displays at boot time that it
cannot find a driver vor the CDROM-Drive on ata1.
On the 2nd ide
It seems Alex Zepeda wrote:
> On Thu, 4 Mar 1999, oZZ!!! wrote:
> > >What exactly is 'unwanted interrupt' supposed to mean, and is it
> > > likely to be a problem in my kernel configuration? (I can send a copy
> > > of it on request...)
> > i think it tell you about not used 2nd IDE controller
> > Am I confused (yet again)?
>
>Yes ;-)
>
>I mean the time it takes to actually detect the drive.
I recently added
options IDE_DELAY=2000
on all IDE kernels I managed. The only problem with this short delay
so far was an undetected drive in an unusual configuration:
The jumper b
> >After having CVSupped to the latest 4.0-CURRENT tree
> > (just now), I noticed the amazing speed of the new ATA driver.
>
> The amazing speed of the new ATA driver? Were you using 32 bit transfers
> and multi-sector IO with the older driver?
>
> I assumed from the benchmarks posted that I
On Thu, 4 Mar 1999, oZZ!!! wrote:
> >What exactly is 'unwanted interrupt' supposed to mean, and is it
> > likely to be a problem in my kernel configuration? (I can send a copy
> > of it on request...)
> i think it tell you about not used 2nd IDE controller...
Nope. I've got three IDE/ATAPI d
On Wed, Mar 3, 1999, oZZ!!! put this into my mailbox:
> i think it tell you about not used 2nd IDE controller...
Nope, my CD ROM is on the second IDE controller ...
-Chris
--
Powered by FreeBSD 4.0-CURRENT. "The Power to Serve!"
int main(int m){main(!main(0));}
To Un
On Wed, 3 Mar 1999, Chris Costello wrote:
>After having CVSupped to the latest 4.0-CURRENT tree
> (just now), I noticed the amazing speed of the new ATA driver.
>
> BUT
>
> I noticed something in dmesg...
>
> ata1: unwanted interrupt
> ad0: ATA-3 disk at a
On Wed, Mar 3, 1999, Sheldon Hearn put this into my mailbox:
>
>
> On Wed, 03 Mar 1999 16:06:19 CST, Chris Costello wrote:
>
> >After having CVSupped to the latest 4.0-CURRENT tree
> > (just now), I noticed the amazing speed of the new ATA driver.
>
> The amazing speed of the new ATA driver
On Wed, 03 Mar 1999 16:06:19 CST, Chris Costello wrote:
>After having CVSupped to the latest 4.0-CURRENT tree
> (just now), I noticed the amazing speed of the new ATA driver.
The amazing speed of the new ATA driver? Were you using 32 bit transfers
and multi-sector IO with the older driver?
After having CVSupped to the latest 4.0-CURRENT tree
(just now), I noticed the amazing speed of the new ATA driver.
BUT
I noticed something in dmesg...
ata1: unwanted interrupt
ad0: ATA-3 disk at ata0 as master
ad0: 3090MB (6330240 sectors), 6280 cyls, 16 heads, 63 S/T, 512 B/S
ad0: 16 secs
35 matches
Mail list logo
