> In <[EMAIL PROTECTED]>
> Chris Faulhaber <[EMAIL PROTECTED]> wrote:
> > Could you try this patch and get back to me with the result please:
> >
> Works for me:
> GEOM: create disk ad0 dp=0xc6972c60
> ad0: 57241MB [116301/16/63] at ata0-master UDMA100
> GEOM: create disk ad1 dp=0xc
On Wed, Dec 03, 2003 at 09:55:56AM +0100, Soren Schmidt wrote:
> It seems Chris Faulhaber wrote:
> > I have been seeing the same issue since August with a different,
> > but similiar, set of drives:
> >
> > ad0: 57241MB [116301/16/63] at ata0-master UDMA100
> > ad1: 57241MB [116301/16/63] at ata
It seems Chris Faulhaber wrote:
> I have been seeing the same issue since August with a different,
> but similiar, set of drives:
>
> ad0: 57241MB [116301/16/63] at ata0-master UDMA100
> ad1: 57241MB [116301/16/63] at ata0-slave UDMA100
>
> Under -CURRENT only the first drive is seen; RELENG_4
On Wed, Nov 26, 2003 at 01:00:47PM +0900, NAKAJI Hiroyuki wrote:
> Hi,
>
> I'm preparing new machine with 5-current. First, I installed a snapshot on
> Feb 21 2003. It works well. From the beginning of this week, I started
> updating it to the latest, and found the problem.
>
...
> ad0: 38166MB
Hi,
I'm preparing new machine with 5-current. First, I installed a snapshot on
Feb 21 2003. It works well. From the beginning of this week, I started
updating it to the latest, and found the problem.
The box is built with following parts.
o ASUS P4G8X
o P4 2.53GHz
o 2GB memory
o Seagate ST340810
st to record, no stopping is available, no serial
VN> console.
VN> Previous 5-current on this machine was of 2003-05-23.
VN> How to diagnose?
Well, I restricted time interval to between 2003-08-18 and 2003-08-25, so it is
ATAng. Also tested 2003-11-20 and 2003-10-06 with the same result.
Di
Soren Schmidt wrote:
FYI, this is still an issue:
s = ioctl(fd, CDIOCCLOSE, 0)
IOError: [Errno 16] Device busy
Hmm, if the call to do the close fails there isn't much I can do...
I can't reproduce the problem on any of the dozens of ATAPI CDROM's
I have in the closet, so if you want to get f
It seems Lars Eggert wrote:
> Lars Eggert wrote:
> > Soren Schmidt wrote:
> >
> >>> Is there any other patch I can try? I've just confirmed that this bug
> >>> still exists with today's kernel.
> >>
> >> I cant reproduce the no matter what I try, sorry...
> >
> > Would remote access to the machi
Lars Eggert wrote:
Soren Schmidt wrote:
Is there any other patch I can try? I've just confirmed that this bug
still exists with today's kernel.
I cant reproduce the no matter what I try, sorry...
Would remote access to the machine in question help you?
FYI, this is still an issue:
s = ioctl(
I've also had problems with CF cards and ATAng :-(
Warner
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
i_startup() at mi_startup+0xb5
begin() at begin+0x2c
db>
If I insert the card after the system is up and running the
panic does not appear, probably because ATAng does not get
the information about a newly inserted drive?
At least atacontrol list does not display any drives:
desire:~>sudo
-current (cvsup'd about 3 hours ago) doesn't like my ATA disk anymore :(
5.1-RELEASE says (during 'boot -v'):
ata0: pre reset mask=03 ostat0=50 ostat2=00
ata0-master: ATAPI 00 00
ata0-slave: ATAPI 00 00
ata0: after reset mask=03 stat0=50 stat1=00
ata0-master: ATA 01 a5
ata0: devices=01
ata0 at
Hi
I have a rather old Dell laptop that I'd like to run current on.
A few months back current booted, but the PCIC stuff was broken so
I had to back out. I thought I'd give it another try this week.
After it probes the disk and GEOM does some stuff it stops responding
to keyboard with the harddis
at
> the drive is reading increased errors due to the solar flares as a need to
> thermally recalibrate more often.
>
> Other than tossing the drives, ATAng, like Windows, would have to be more
> aggressive about retrying even uncorrectable errors for up to a minute or
> s
> Date: Sun, 09 Nov 2003 22:43:47 -0700
> From: Scott Long <[EMAIL PROTECTED]>
>
> Kevin Oberman wrote:
> > Tested. It's much better, although ATA request keeps adding more
> > memory all the time when mplayer is playing, but it's now increasing
> > at about 20K/minute which is a huge improvement.
Kevin Oberman wrote:
Tested. It's much better, although ATA request keeps adding more
memory all the time when mplayer is playing, but it's now increasing
at about 20K/minute which is a huge improvement. Still, I don't
understand why it should just continue to grow all of the time. The
data rate is
Tested. It's much better, although ATA request keeps adding more
memory all the time when mplayer is playing, but it's now increasing
at about 20K/minute which is a huge improvement. Still, I don't
understand why it should just continue to grow all of the time. The
data rate is about constant. I wo
> Date: Mon, 10 Nov 2003 11:37:00 +1030
> From: Alex Wilkinson <[EMAIL PROTECTED]>
>
> On Thu, Nov 06, 2003 at 08:08:31AM -0800, Kevin Oberman wrote:
>
> Any ideas on where I can look for more information? I'm going to try
> doing some monitoring with vmstat while running
On Thu, Nov 06, 2003 at 08:08:31AM -0800, Kevin Oberman wrote:
Any ideas on where I can look for more information? I'm going to try
doing some monitoring with vmstat while running to see if I can spot
anything, but I am not sure just what I am looking for. T
Fixed. Please retest.
Scott Long wrote:
Kevin Oberman wrote:
Date: Thu, 6 Nov 2003 11:23:30 -0500 (EST)
From: Robert Watson <[EMAIL PROTECTED]>
On Thu, 6 Nov 2003, Kevin Oberman wrote:
I have learned a bit more about the problems I have been having with
the DVD drive on my T30 laptop. When I h
at
> the drive is reading increased errors due to the solar flares as a need to
> thermally recalibrate more often.
>
> Other than tossing the drives, ATAng, like Windows, would have to be more
> aggressive about retrying even uncorrectable errors for up to a minute or
> so befo
ly
helped my Deathstars before I got rid of them all.
Also, given the touchiness of PRML detectors, it is entirely possible that
the drive is reading increased errors due to the solar flares as a need to
thermally recalibrate more often.
Other than tossing the drives, ATAng, like Windows, woul
On Fri, Nov 07, 2003 at 10:10:07AM -0800, Kris Kennaway wrote:
> ad0: FAILURE - READ_DMA status=51 error=40
> ad0: FAILURE - READ_DMA status=51 error=40
> ad0: TIMEOUT - READ_DMA retrying (2 retries left)
> ata0: resetting devices ..
> ad0: FAILURE - already active DMA on this device
> ad0: settin
On Fri, Nov 07, 2003 at 07:33:41PM +0100, Soren Schmidt wrote:
> > 1) All my drives have performed mass suicide at once
>
> You know, with deathstar's you cant really rule that out :)
:-)
> > Furthermore, I'd like to know why the panic occurred above.
>
> Is this on a brand new -current ? lots
ndition from the drive...
>
> > 1) All my drives have performed mass suicide at once
>
> You know, with deathstar's you cant really rule that out :)
>
> > 2) ATAng is detecting errors that the ATAog did not
>
> That is true, the error detection is better in
nd they were correctable for another month
> or two by /dev/zero'ing the drive.
>
> To suddenly start receiving errors on 5 out of 7 drives in the past
> few weeks is a significant anomaly. Perhaps one of the following is
> happening:
>
> 1) All my drives have performed
> Date: Fri, 07 Nov 2003 00:45:47 -0700
> From: Scott Long <[EMAIL PROTECTED]>
>
> Kevin Oberman wrote:
> >>Date: Thu, 6 Nov 2003 11:23:30 -0500 (EST)
> >>From: Robert Watson <[EMAIL PROTECTED]>
> >>
> >>
> >>On Thu, 6 Nov 2003, Kevin Oberman wrote:
> >>
> >>
> >>>I have learned a bit more about t
) All my drives have performed mass suicide at once
You know, with deathstar's you cant really rule that out :)
> 2) ATAng is detecting errors that the ATAog did not
That is true, the error detection is better in ATAng.
> 3) ATAng is not trying as hard as ATAog to recover from the error
e drive.
To suddenly start receiving errors on 5 out of 7 drives in the past
few weeks is a significant anomaly. Perhaps one of the following is
happening:
1) All my drives have performed mass suicide at once
2) ATAng is detecting errors that the ATAog did not
3) ATAng is not trying as hard as
Kevin Oberman wrote:
Date: Thu, 6 Nov 2003 11:23:30 -0500 (EST)
From: Robert Watson <[EMAIL PROTECTED]>
On Thu, 6 Nov 2003, Kevin Oberman wrote:
I have learned a bit more about the problems I have been having with
the DVD drive on my T30 laptop. When I have run the drive for an
extended time (lik
> Date: Thu, 6 Nov 2003 11:23:30 -0500 (EST)
> From: Robert Watson <[EMAIL PROTECTED]>
>
>
> On Thu, 6 Nov 2003, Kevin Oberman wrote:
>
> > I have learned a bit more about the problems I have been having with
> > the DVD drive on my T30 laptop. When I have run the drive for an
> > extended time
On Thu, 6 Nov 2003, Kevin Oberman wrote:
> I have learned a bit more about the problems I have been having with
> the DVD drive on my T30 laptop. When I have run the drive for an
> extended time (like 2 or 3 hours), I invariably have my system lock up
> because it can't malloc kernel memory for t
;m hoping that this
might help, but, if there really is a memory leak, tuning will not fix
it.
FWIW, this problem did not exist a few month ago prior to ATAng.
--
R. Kevin Oberman, Network Engineer
Energy Sciences Network (ESnet)
Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
I hate following up my own post, but I manages to get some significant
information.
The console (previously inaccessible after the crash) was "on screen"
for the last event and I get the the following:
FAILURE - malloc ATA request failed
cannot allocate ATAPI/CAM request
(cd0:ata1:0:0:0): out of m
I suspect that I have a system losing interrupts from the disk. I get
fairly random lock-ups where the system totally freezes and the disk
access LED is on continuously until I power cycle the system.
It's an IBM T30 with an IBM 40 GB disk. The only thing I have noticed
is that the lock-ups only s
Soren Schmidt wrote:
Is there any other patch I can try? I've just confirmed that this bug
still exists with today's kernel.
I cant reproduce the no matter what I try, sorry...
Would remote access to the machine in question help you?
Lars
--
Lars Eggert <[EMAIL PROTECTED]> USC Informati
It seems Lars Eggert wrote:
> Bruce Evans wrote:
> > On Thu, 30 Oct 2003, Soren Schmidt wrote:
> >>
> >>Anyhow if you loose the test for error in atapi-cd.c::acd_tray in the
> >>close case, does it work then ? Problem is that the call to read toc
> >>might fail early, but its worth a shot..
>
> I
Bruce Evans wrote:
On Thu, 30 Oct 2003, Soren Schmidt wrote:
Anyhow if you loose the test for error in atapi-cd.c::acd_tray in the
close case, does it work then ? Problem is that the call to read toc
might fail early, but its worth a shot..
I tried this, but it didn't change anything. (See my mail
On Sunday 02 November 2003 17:01, Soren Schmidt wrote:
> It seems Harald Schmalzbauer wrote:
> > Ha, stop. Today it doesn't work as non-root anymore.
> > I'm sure with -current some days ago and the same patch it worked without
> > root privileges.
> > I can't follow that.
>
> Thats a feature of at
It seems Harald Schmalzbauer wrote:
>
> Ha, stop. Today it doesn't work as non-root anymore.
> I'm sure with -current some days ago and the same patch it worked without root
> privileges.
> I can't follow that.
Thats a feature of atapi-cd now being under GEOM..
The device nodes are now mode 640
On Saturday 01 November 2003 23:06, Artem 'Zazoobr' Ignatjev wrote:
> On Sat, 01.11.2003, at 11:08, Harald Schmalzbauer ÐÉÛÅÔ:
*SNIP*
> > There were great tools which could do that automatically but they don't
> > work any more for a reason I cannot follow.
>
> I've ran accross this one some time
On Saturday 01 November 2003 16:54, Arjan van Leeuwen wrote:
> On Saturday 01 November 2003 09:08, Harald Schmalzbauer wrote:
> > Hi all,
> >
> > in the archive I found a discussion about some implementation changes
> > with ATAng which breakes CDDA support for (all?) c
On Saturday 01 November 2003 09:08, Harald Schmalzbauer wrote:
> Hi all,
>
> in the archive I found a discussion about some implementation changes with
> ATAng which breakes CDDA support for (all?) common programs.
> Will it ever be possible to use FreeBSD with e.g. kaudi
Hi all,
in the archive I found a discussion about some implementation changes with
ATAng which breakes CDDA support for (all?) common programs.
Will it ever be possible to use FreeBSD with e.g. kaudiocreator (needs
cdparanoia)?
I'm no friend of copying audiotracks by hand, give them a mo
On Thu, 30 Oct 2003, Soren Schmidt wrote:
> It seems Lars Eggert wrote:
> > > I've already committed a solution that works on all the drives I
> > > could test on (some of which failed before), if this still
> > > fails for you I'd like a more detailed description of what
> > > exactly goes wrong.
Soren Schmidt wrote:
Anyhow if you loose the test for error in atapi-cd.c::acd_tray in the
close case, does it work then ?
If you mean as below, no, that didn't help:
Index: atapi-cd.c
===
RCS file: /home/ncvs/src/sys/dev/ata/atapi-cd
V čt, 30. 10. 2003 v 20:43, Lars Eggert píše:
> >>FYI, the issue is still present with yesterday's -current. Will Pav
> >>Lucistnik's patch be committed soon?
> >
> > I've already committed a solution that works on all the drives I
> > could test on (some of which failed before), if this still
It seems Lars Eggert wrote:
> > I've already committed a solution that works on all the drives I
> > could test on (some of which failed before), if this still
> > fails for you I'd like a more detailed description of what
> > exactly goes wrong...
>
> I must have missed that commit message, sor
On 30-Oct-2003 Lars Eggert wrote:
> Soren Schmidt wrote:
>> It seems Lars Eggert wrote:
>>
>>>FYI, the issue is still present with yesterday's -current. Will Pav
>>>Lucistnik's patch be committed soon?
>>
>> I've already committed a solution that works on all the drives I
>> could test on (som
Soren Schmidt wrote:
It seems Lars Eggert wrote:
FYI, the issue is still present with yesterday's -current. Will Pav
Lucistnik's patch be committed soon?
I've already committed a solution that works on all the drives I
could test on (some of which failed before), if this still
fails for you I'd
It seems Lars Eggert wrote:
> FYI, the issue is still present with yesterday's -current. Will Pav
> Lucistnik's patch be committed soon?
I've already committed a solution that works on all the drives I
could test on (some of which failed before), if this still
fails for you I'd like a more deta
Soren Schmidt wrote:
It seems Pav Lucistnik wrote:
This patch works for me. Any chance to get it committed?
I'll look at it...
FYI, the issue is still present with yesterday's -current. Will Pav
Lucistnik's patch be committed soon?
Lars
--
Lars Eggert <[EMAIL PROTECTED]> USC Informatio
It seems David Gilbert wrote:
> I have tried several times in recent days to burn DVDs with burncd,
> growisofs and cdrecord ... all of which worked before atang.
> Growisofs complains that it can't flush it's buffers. Burncd doesn't
> complain ... but the resulting di
I have tried several times in recent days to burn DVDs with burncd,
growisofs and cdrecord ... all of which worked before atang.
Growisofs complains that it can't flush it's buffers. Burncd doesn't
complain ... but the resulting disk is not mountable.
I thought at one point that
Hello Janet,
Sunday, October 26, 2003, 1:52:52 PM, you wrote:
> Gabriel Ambuehl wrote:
>> Further, 4.9RC3 also gives me headaches with HPT370 but seems to work ok with
>> Promise RAID, didn't try SATA or VT8325 so far. I'd definitely vote
>> for delaying 4.9 until some more people have beaten on
ATAng seems to cause nothing but trouble for me. It won't recognize
HPT370 arrays at all (whereas older 5.1 Kernels work perfectly) and
just goes on complaining it can't mount root from it. Promise RAID is
somewhat better (can mount root from it but goes on telling me one of
the subdis
;ll try to
>> > get more info.
I'm getting "missing interrupt" messages from ATAng on one of my older
PPro200 machines that was stable with a June kernel, but is not with
an October 22 kernel. I don't know that they're related, and I
haven't had a chance to
Saturday, October 25, 2003, 7:51:58 AM, you wrote:
>>> * Resume fails, hanging with drive light on. Last event: 2003/10/2
>>> Appears to be a lost interrupt during reset.
>>
>> I've just committed some changes that makes suspend/resume work just
>> fine on the notebooks I have access to.
>
> This
gt; > > get more info.
> >
> > No idea about that on.
>
> It's gone as well. I can't reproduce any more whereas before I could
> reproduce often. So now I have no problems with ATAng and I can run
> it on all [EMAIL PROTECTED] panic
Okies, so you are a happy camper :)
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
On Fri, 10 Oct 2003, Soren Schmidt wrote:
> It seems Nate Lawson wrote:
> > Here is an updated status of ATAng for me. I periodically test it to see
> > if any of the following problems go away.
> >
> > * Panic occurs after ATAFD fails to probe. Last event: 2003/10/6
>>>>> "Pierre" == Pierre Beyssac <[EMAIL PROTECTED]> writes:
Pierre> On Mon, Oct 20, 2003 at 09:10:39PM -0400, David Gilbert wrote:
>> This all started screwing up with ATAng. At first, ATAng didn't
>> support atapicam, but that was rectified.
On Mon, Oct 20, 2003 at 09:10:39PM -0400, David Gilbert wrote:
> This all started screwing up with ATAng. At first, ATAng didn't
> support atapicam, but that was rectified. Now the dvd+rw port
> (growisofs) doesn't work at all ... it finishes with an error that I'm
>
, DVD+R (which is
always disk-at-once) doesn't entirely burn properly. I havn't been
able to nail it down, but certain ISO images work and certain ones
don't.
This all started screwing up with ATAng. At first, ATAng didn't
support atapicam, but that was rectified. Now the dv
First of all, as someone noted with disk-at-once, DVD+R (which is
always disk-at-once) doesn't entirely burn properly. I havn't been
able to nail it down, but certain ISO images work and certain ones
don't.
This all started screwing up with ATAng. At first, ATAng didn't
s
> Maybe there is need to adjust wait DELAY time.
>
> Please test and replace ata_reset().
Hold your horses just a bit please, I suggest that you try to understand
the current code first, then we can talk about improving it..
> I hope this solve ATAng troubles.
It will probably solve
Hi,
I'm trying to setup vinum on 2 identical 30G HD's.
The MB I'm using has a built in Raid 0 controller, so
i have 6 ATA Slots. My Main HD is hooked up to the
primary non-raid. and the other 2 are hooked up to
primary 1 and primary 2 on the raid. I can get vinum
up and running, but when i forc
annel.
> Maybe there is need to adjust wait DELAY time.
>
> Please test and replace ata_reset().
>
> I hope this solve ATAng troubles.
I applied your patch and rebuilt my kernel on my ThinkPad T30 and the
behavior is changed, but not really improved.
Now, instead of hanging afte
t test ATAPI devices and ATA-slave channel.
> Maybe there is need to adjust wait DELAY time.
>
> Please test and replace ata_reset().
>
> I hope this solve ATAng troubles.
>
> --
> Hiroyuki Aizu
> [2 ata-lowlevel.c.diff ]
This patch fixes resume problem of my laptop (
hope this solve ATAng troubles.
--
Hiroyuki Aizu
ata-lowlevel.c.diff
Description: Binary data
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Further details:
The ATA drive in questions is:
ad0: 114473MB [232581/16/63] at ata0-master PIO4
The PIO4 comes from booting with 'hw.ata.ata_dma="0"'; it would otherwise be
"UDMA66".
Basically, if I use atacontrol to set that channel to WDMA2 or below, then I
get no errors (but performanc
nf.local.
The IDE bus in question is:
atapci0: port 0xd800-0xd80f at device 4.1 on pci0
I understand that there may be a few bugs left in ATAng, and as a user of
-CURRENT, I'm OK with that. Is there anything I can do that would probably
let me run my system a bit faster than PIO4 will allow
В ср, 08.10.2003, в 12:04, Soren Schmidt пишет:
> > Does not help, another panic in ad_attach:
>
> ARGH, try this instead:
Yes, it helps, thank you.
> -Søren
--
Vladimir B. Grebenschikov <[EMAIL PROTECTED]>
SWsoft Inc.
___
[EMAIL PROTECTED] mailing
It seems Radko Keves wrote:
> hi
>
> this verbosed dmesg is from my box maybe it help you
Uhm, and what exactly is the problem ?
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send an
hi
this verbosed dmesg is from my box maybe it help you
have a nice day
--
Archeologists near mount Sinai have discovered what is believed to be a
missing page from the Bible. The page is currently being carbon dated
in Bonn. If genuine it belongs at the beginning of the Bible and is
bel
It seems Vladimir B. Grebenschikov wrote:
> Does not help, another panic in ad_attach:
ARGH, try this instead:
diff -u -r1.191 ata-all.c
--- ata-all.c 7 Oct 2003 13:44:15 - 1.191
+++ ata-all.c 8 Oct 2003 08:03:09 -
@@ -35,6 +35,7 @@
#include
#include
#include
+#include
В вт, 07.10.2003, в 23:26, Soren Schmidt пишет:
> It seems Vladimir B. Grebenschikov wrote:
> > > Any solution or workaround ?
>
> Try this patch please:
>
> diff -u -r1.191 ata-all.c
Does not help, another panic in ad_attach:
...
GEOM: create disk ad1 dp=0xc2358a70
ad1: ATA-0 disk at ata1-mas
I have a repeatable ATAng panic. The panic string is "vm_map_wire:
lookup failed" and it's caused by using cdrdao on my ATAPICAM
connected DVD writer. In this particular case, I'm trying to write a
bin/cue format file onto a writeable CD.
The panic goes roughly like this:
It seems Vladimir B. Grebenschikov wrote:
> > Any solution or workaround ?
Try this patch please:
diff -u -r1.191 ata-all.c
--- ata-all.c 7 Oct 2003 13:44:15 - 1.191
+++ ata-all.c 7 Oct 2003 19:15:03 -
@@ -35,6 +35,7 @@
#include
#include
#include
+#include
#include
#in
Here is an updated status of ATAng for me. I periodically test it to see
if any of the following problems go away.
* Panic occurs after ATAFD fails to probe. Last event: 2003/10/6
I have no ATAFD device on my system and normally no messages are printed
about it on boot. However, periodically
В пн, 06.10.2003, в 22:48, Vladimir B. Grebenschikov пишет:
> Soren, please help.
>
> I can't boot kernel after ATAng. It founds one extra ATA device
> (I have no ata1-slave attached) and then panics.
>
> All details in PR kern/57156.
I have workarounded problem by disa
Hi
Soren, please help.
I can't boot kernel after ATAng. It founds one extra ATA device
(I have no ata1-slave attached) and then panics.
All details in PR kern/57156.
In short:
ad0: setting UDMA33 on Intel PIIX4 chip
GEOM: create disk ad0 dp=0xc1d00970
ad0: ATA-5 disk at ata0-maste
None of the previous posts on this seem to describe exactly what I'm
seeing:
5.1-REL always detects the secondary drive.
5.1-CUR never detects the secondary.
5.1-CUR + ata-lowlevel 1.11 detects it the FIRST time it's booted
immediately after 5.1-REL. Always. On subsequent boots, no luck.
A = 1s
After yesterday's cvsup and kernel/world build my primary slave harddisk
not longer gets detected (once again).
If I revert to src/sys/dev/ata/ata-lowlevel.c 1.11 it is detected
properly. (It might also work with later versions. If you need the exact
revision where it stopped working please tell m
It seems Christoph Sold wrote:
> I set up a box
>
>(FreeBSD 5.1-CURRENT #0: Tue Sep 23 00:21:31 CEST 2003
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC,
> compiled from the sources the day before)
>
> showing the erratic behaviour. Verbose boot logs are available at
>
>http://
I have been getting a similar panic for several weeks
now. I cvsup-ed and built a new kernel yesterday
(9/29) and it still doesn't see it. This is with a
SIS 630 chipset UDMA controller.
--- Tilman Linneweh <[EMAIL PROTECTED]> wrote:
> Hi,
> Updated my -CURRENT yesterday and got the following
Hello All,
I set up a box
(FreeBSD 5.1-CURRENT #0: Tue Sep 23 00:21:31 CEST 2003
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC,
compiled from the sources the day before)
showing the erratic behaviour. Verbose boot logs are available at
http://cheasy.dyndns.org/bootlogs/ .
If anybody
is is probably an ATAng
issue, not an ACPI one.)
System resumes with the following messages:
pcib0: slot 29 INTA is routed to irq 11
pcib0: slot 29 INTB is routed to irq 11
pcib0: slot 29 INTC is routed to irq 11
pcib0: slot 31 INTB is routed to irq 11
pcib0: slot 31 INTB is routed to irq 11
pcib0: sl
It seems Michael McGoldrick wrote:
> I haven't been able to boot a -current kernel since the ATAng import.
> They all die after (in a boot -v) a message from GEOM about creating ad0.
> If any further info would be helpful, just let me know what you need.
I know there are a prob
I haven't been able to boot a -current kernel since the ATAng import.
They all die after (in a boot -v) a message from GEOM about creating ad0.
If any further info would be helpful, just let me know what you need.
--
Michael McGoldrick: [EMAIL PROTECTED]
Copyright (c) 1992-2003 The Fr
Hi,
Updated my -CURRENT yesterday and got the following panic:
[...]
atapci0: port 0xb800-0xb80f at
device 15.0 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
ata1: at 0x170 irq 15 on atapci0
ata1: [MPSAFE]
fdc0: port
0x3f7,0x3f2-0x3f5 irq 6 drq 2 on acpi0
fdc0: FIFO enabled, 8 bytes th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sunday 21 September 2003 03:30 pm, you wrote:
> I'm getting intermittent problems on boot, sometimes it boots, most
of
> the time not. When it stop it's at:
> ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin
>
> dmesg -v from a full boot:
>
Le 2003-09-22, Dan Naumov écrivait :
> Speaking of failing, should I completely disregard the probe2:ata1
> warnings during boot which you saw in the dmesg output I sent you ?
Yes, these messages are perfectly inocuous, they mean that your CD drive
does not provide serial number information. You
On Mon, 2003-09-22 at 00:07, Thomas Quinot wrote:
> Le 2003-09-21, Bryan Liesner écrivait :
>
> > Thanks, the hang problems are fixed now.
>
> That's great news!
I am also very grateful for your fix. I now seem to be able to run
-CURRENT on my home desktop without any issues whatsoever :)
>
>
Le 2003-09-21, Bryan Liesner écrivait :
> Thanks, the hang problems are fixed now.
That's great news!
> No one told me that I was barking up the wrong tree...
Ah, computers are fragile and playful things that always find creative
and unexcepted ways of failing... :)
Thomas.
--
[EMAIL PRO
On Sun, 21 Sep 2003, Daniel Eischen wrote:
> On Sun, 21 Sep 2003, Thomas Quinot wrote:
>
> > Le 2003-09-21, Daniel Eischen écrivait :
> >
> > > Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error
> > > Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check
I'm getting intermittent problems on boot, sometimes it boots, most of
the time not. When it stop it's at:
ata0-master: pio=0x0c wdma=0x22 udma=0x45 cable=80pin
dmesg -v from a full boot:
http://am-productions.biz/docs/dmesg.txt
--
Anish Mistry
pgp0.pgp
Description: signature
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt,
On Mon, 22 Sep 2003 03:01:28 +0900, Shin-ichi Yoshimoto wrote:
> Ok, I will try it.
I tried to cvsup and make build & installkernel. This kernel said:
[snip]
acpi_cpu: throttling enabled, 2 steps (100%
ree up-to-date?
> Several fixes have been committed to both the ATA and the CAM subsystems
> recently, that address problems uncovered by the transition to ATAng.
>
> > Did anyone read _any_ of my previous posts?
>
> Certainly so, since you already received answers to some
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing
interrupt,
On Sun, 21 Sep 2003 18:57:43 +0200, Thomas Quinot wrote:
> Can't you drop into DDB at that point?
Ok, I will try it.
> Also, do you have up-to-date sources?
Yes, of course. I have recent ones.
--
On Sun, 21 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-21, Daniel Eischen écrivait :
>
> > Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): CAM Status: SCSI Status Error
> > Sep 21 12:40:28 sirius kernel: (cd0:ata0:0:0:0): SCSI Status: Check Condition
> > Sep 21 12:40:28 sirius kernel: (cd0:ata0:
1 - 100 of 375 matches
Mail list logo
