> 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
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(
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 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
Nate Lawson <[EMAIL PROTECTED]> writes:
>> > * Lost interrupt for ATA-SLAVE on reboot. Last event: 2003/10/7
>> > I'm unsure if this is actually a problem but occasionally it prints a
>> > message right before rebooting about loosing an interrupt. I'll try to
>> > get more info.
I'm getting "m
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
It seems Nate Lawson wrote:
> > > * 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 ATAFD will print a bunch of
> > > messages on console about failing to pr
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
> > I have no ATAFD device on
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
В ср, 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
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
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
В пн, 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 disabling slave ATA devices
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
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 problem with *some* Acer
-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
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%
On Sun, 21 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-21, Bryan Liesner écrivait :
>
> > The patch doesn't take care of the hang for me.
>
> Does it change anything, or do you still see the 'REQUEST_SENSE
> recovered from missing interrupt'? Is your source tree up-to-date?
> Several fixes have be
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:
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:0:0:0): Recovered Sense
> Sep 21 12:40:28 sirius kern
On Sun, 21 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-21, Bryan Liesner écrivait :
>
> > The patch doesn't take care of the hang for me.
>
> Does it change anything, or do you still see the 'REQUEST_SENSE
> recovered from missing interrupt'? Is your source tree up-to-date?
> Several fixes have
Le 2003-09-21, Shin-ichi Yoshimoto écrivait :
> I could not get a backtrace because infinite loop occured like this:
Can't you drop into DDB at that point? Also, do you have up-to-date
sources?
Thomas.
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] m
Le 2003-09-21, Bryan Liesner écrivait :
> The patch doesn't take care of the hang for me.
Does it change anything, or do you still see the 'REQUEST_SENSE
recovered from missing interrupt'? Is your source tree up-to-date?
Several fixes have been committed to both the ATA and the CAM subsystems
rec
Le 2003-09-21, Dan Naumov écrivait :
> (probe2:ata1:0:0:0): Recovered Sense
> (probe2:ata1:0:0:0): INQUIRY. CDB: 12 1 80 0 ff 0
> (probe2:ata1:0:0:0): CAM Status: SCSI Status Error
> (probe2:ata1:0:0:0): SCSI Status: Check Condition
> (probe2:ata1:0:0:0): ILLEGAL REQUEST asc:24,0
> (probe2:ata1:0
On Sat, 2003-09-20 at 22:53, Thomas Quinot wrote:
> Le 2003-09-20, Daniel Eischen écrivait :
>
> > No, using latest sources, with or without atapicam, does
> > not solve the problem. It still hangs.
>
> Please try the patch below, it should at least work around the problem.
I have rebuilt world
On Sat, 20 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-20, Daniel Eischen écrivait :
>
> > No, using latest sources, with or without atapicam, does
> > not solve the problem. It still hangs.
>
> Please try the patch below, it should at least work around the problem.
>
> > http://people.freebsd.
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing interrupt,
On Sun, 21 Sep 2003 00:23:36 +0200, Thomas Quinot wrote:
> Can you get a backtrace at that point?
I could not get a backtrace because infinite loop occured like this:
[snip]
ata0-master: pio=0x0c wdma=0x22 u
Le 2003-09-20, Shin-ichi Yoshimoto écrivait :
> > acd0: WARNING - REQUEST_SENSE recovered from missing interrupt
> This message disappeared, but It still hang
Can you get a backtrace at that point?
--
[EMAIL PROTECTED]
___
[EMAIL PROTECTED] maili
Subject: Re: ATAng no good for me/REQUEST_SENSE recovered from missing
interrupt,
On Sat, 20 Sep 2003 21:53:11 +0200, Thomas Quinot wrote:
> Please try the patch below, it should at least work around the problem.
I tried your patch.
> acd0: WARNING - REQUEST_SENSE recovered from m
Le 2003-09-19, Dan Naumov écrivait :
> Disabling atapicam in the kernel or detaching the drive from the system
> works around the problem.
Please try the patch I posted a few moments ago under "ATAng no good for
me/REQUEST_SENSE recovered from missing interrupt".
Thomas.
--
[EMAIL PROTECTE
Le 2003-09-20, David R. Colyer écrivait :
> Is atapicam a kernel config option?
It is a device (cf. man atapicam): you can enable it with
"device atapicam" in your kernel config file.
> I can't seem to find it, and now since a cvsup up on the 17h, my plextor scsi
> cdrw locks my system and then
Le 2003-09-20, Daniel Eischen écrivait :
> No, using latest sources, with or without atapicam, does
> not solve the problem. It still hangs.
Please try the patch below, it should at least work around the problem.
> http://people.freebsd.org/~deischen/ata_hang.091903
Interesting, the last 2 l
On Sat, 20 Sep 2003, Lars Eggert wrote:
> Daniel Eischen wrote:
> > On Sat, 20 Sep 2003, Soren Schmidt wrote:
> >>It seems Daniel Eischen wrote:
> >>
> >>>On a kernel built just a few hours ago, it hangs on boot
> >>>right after:
> >>>
> >>>acd0: CDROM at ata0-master PIO4
> >>
> >>Get atapicam ou
Daniel Eischen wrote:
On Sat, 20 Sep 2003, Soren Schmidt wrote:
It seems Daniel Eischen wrote:
On a kernel built just a few hours ago, it hangs on boot
right after:
acd0: CDROM at ata0-master PIO4
Get atapicam out and see if that helps..
No, using latest sources, with or without atapicam, does
no
It seems Daniel Eischen wrote:
> > It seems Daniel Eischen wrote:
> > > On a kernel built just a few hours ago, it hangs on boot
> > > right after:
> > >
> > > acd0: CDROM at ata0-master PIO4
> >
> > Get atapicam out and see if that helps..
>
> No, using latest sources, with or without atapicam
On Sat, 20 Sep 2003, Soren Schmidt wrote:
> It seems Daniel Eischen wrote:
> > On a kernel built just a few hours ago, it hangs on boot
> > right after:
> >
> > acd0: CDROM at ata0-master PIO4
>
> Get atapicam out and see if that helps..
No, using latest sources, with or without atapicam, does
On Sat, 2003-09-20 at 12:32, David R. Colyer wrote:
> Is atapicam a kernel config option?
[14:11]-[jago]-[~]: cat /usr/src/sys/i386/conf/JAGO | grep atapicam
#device atapicam# BROKEN in -CURRENT !!!
Hope this helps.
Sincerely,
Dan Naumov
Is atapicam a kernel config option?
I can't seem to find it, and now since a cvsup up on the 17h, my plextor scsi
cdrw locks my system and then reboots immediately after a burning program,
(i've tried several) initializes the drive. It worked several weeks ago just
fine. Any suggestions would
It seems Daniel Eischen wrote:
> On a kernel built just a few hours ago, it hangs on boot
> right after:
>
> acd0: CDROM at ata0-master PIO4
Get atapicam out and see if that helps..
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/ma
On Fri, 19 Sep 2003, Kris Kennaway wrote:
> On Fri, Sep 19, 2003 at 07:09:03PM -0400, Daniel Eischen wrote:
> > ATA (atapicam also in kernel) doesn't seem to work after the
> > changes in the last 24 hours or so. I have a SCSI system
> > with one ATAPI CD-ROM drive, which gets probed on a good
>
On Sat, Sep 20, 2003 at 01:47:44AM +0100, Bruce M Simpson wrote:
> On Sat, Sep 20, 2003 at 02:17:21AM +0200, Marius Strobl wrote:
> > > Isn't it still a kernel bug if a user process can trigger a panic?
> >
> > Yes, it seems to be a bug in the mlockall(2) implementation. Backing
> > it out or hind
On Sat, Sep 20, 2003 at 02:17:21AM +0200, Marius Strobl wrote:
> > Isn't it still a kernel bug if a user process can trigger a panic?
>
> Yes, it seems to be a bug in the mlockall(2) implementation. Backing
> it out or hindering cdrecord to use it avoids the panic. I already
> wrote an email to bm
On Fri, Sep 19, 2003 at 04:36:32PM -0700, Kris Kennaway wrote:
> On Fri, Sep 19, 2003 at 06:21:52PM +0200, Marius Strobl wrote:
> > On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> > >
> > > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > > triggered by:
> > >
Who-hoo, it works!!! Thanks a bunch!!!
On Fri, 19 Sep 2003, Marius Strobl wrote:
> On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> >
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
> >
>
> This panic i
On Fri, Sep 19, 2003 at 06:21:52PM +0200, Marius Strobl wrote:
> On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> >
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
> >
>
> This panic isn't ATAPICAM re
On Fri, Sep 19, 2003 at 07:09:03PM -0400, Daniel Eischen wrote:
> ATA (atapicam also in kernel) doesn't seem to work after the
> changes in the last 24 hours or so. I have a SCSI system
> with one ATAPI CD-ROM drive, which gets probed on a good
> kernel as:
sos will probably ask for boot -v outpu
On Fri, 19 Sep 2003, Marius Strobl wrote:
> On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> >
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
> >
>
> This panic isn't ATAPICAM related. Could you try the
On Fri, 19 Sep 2003, Dan Naumov wrote:
> On Fri, 2003-09-19 at 19:21, Marius Strobl wrote:
> > On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> > >
> > > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > > triggered by:
> > >
> > > cdrecord dev=1,1,0 /some/track
On Fri, 2003-09-19 at 19:21, Marius Strobl wrote:
> On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
> >
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
> >
>
> This panic isn't ATAPICAM related. Could
On Thu, Sep 18, 2003 at 05:51:25PM +0200, Jan Srzednicki wrote:
>
> Anyway, here's backtrace for atapicam panic I've mentioned. It's
> triggered by:
>
> cdrecord dev=1,1,0 /some/track
>
This panic isn't ATAPICAM related. Could you try the patch below? It's
against the cdrtools-devel port but sh
It seems Jan Srzednicki wrote:
> > dd if=/dev/acdXtY of=trackY bs=2352
>
> Cool. ;)
Yes, and that has worked for ages...
> Could you give me a hint what to put in devd.conf to get acdXtY files
> created automatically when a CD is inserted?
You just need something to open the acdX device (so the
On Fri, Sep 19, 2003 at 08:02:31AM +0200, Soren Schmidt wrote:
> It seems Jan Srzednicki wrote:
> > > As far as problems with dagrab and cdda2wav are conserned - this is
> > > because of removal of CDIOCREADAUDIO ioctl in ATAng (see recent thread
> > > "What's happened to CDIOCREADAUDIO & friends")
It seems Jan Srzednicki wrote:
> > As far as problems with dagrab and cdda2wav are conserned - this is
> > because of removal of CDIOCREADAUDIO ioctl in ATAng (see recent thread
> > "What's happened to CDIOCREADAUDIO & friends")
>
> I've seen it (after posting the original mail, though;). Is there
On Fri, Sep 19, 2003 at 01:32:45AM +0300, Vladimir Kushnir wrote:
> > Um. Do you see the same crash if both drives contain CDs at boot time?
> > If not, this could be a consequence of the error condition corruption
> > problem others have been reporting.
> >
> > Thomas.
> >
>
> These crashes start
On Thu, 18 Sep 2003, Thomas Quinot wrote:
> Le 2003-09-18, Jan Srzednicki ?crivait :
>
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
>
> Um. Do you see the same crash if both drives contain CDs at boot time?
> If not
It seems Thomas Quinot wrote:
> Le 2003-09-18, Jan Srzednicki écrivait :
>
> > Anyway, here's backtrace for atapicam panic I've mentioned. It's
> > triggered by:
> >
> > cdrecord dev=1,1,0 /some/track
>
> Um. Do you see the same crash if both drives contain CDs at boot time?
> If not, this could
Le 2003-09-18, Jan Srzednicki écrivait :
> Anyway, here's backtrace for atapicam panic I've mentioned. It's
> triggered by:
>
> cdrecord dev=1,1,0 /some/track
Um. Do you see the same crash if both drives contain CDs at boot time?
If not, this could be a consequence of the error condition corrupt
On Thu, Sep 18, 2003 at 11:00:56AM -0600, Scott Long wrote:
> > Anyone know how to make the message buffer larger? I don't have
> > a serial console hooked up currently and a boot verbose is way
> > over the 32K default buffer size so only get the last 32K once
> > the system is booted up.
>
> >Fr
On Thu, Sep 18, 2003 at 06:55:07PM +0200, Jan Srzednicki wrote:
> On Thu, Sep 18, 2003 at 11:46:35AM -0500, Steve Ames wrote:
> > On Thu, Sep 18, 2003 at 06:38:25PM +0200, Soren Schmidt wrote:
> > > Anyhow, what I need to be able to tell what may be going on, is that
> > > you boot verbose and get
On Thu, 18 Sep 2003, Steve Ames wrote:
> On Thu, Sep 18, 2003 at 06:38:25PM +0200, Soren Schmidt wrote:
> > Anyhow, what I need to be able to tell what may be going on, is that
> > you boot verbose and get me the output from dmesg from a boot that
> > found all device, and from a boot that misse
On Thu, Sep 18, 2003 at 11:46:35AM -0500, Steve Ames wrote:
> On Thu, Sep 18, 2003 at 06:38:25PM +0200, Soren Schmidt wrote:
> > Anyhow, what I need to be able to tell what may be going on, is that
> > you boot verbose and get me the output from dmesg from a boot that
> > found all device, and from
On Thu, Sep 18, 2003 at 06:38:25PM +0200, Soren Schmidt wrote:
> Anyhow, what I need to be able to tell what may be going on, is that
> you boot verbose and get me the output from dmesg from a boot that
> found all device, and from a boot that missed.
Anyone know how to make the message buffer lar
It seems Jan Srzednicki wrote:
> > > First of all, the drive still does not get detected properly. Funny
> > > thing is that after some playing with atacontrol attach/detach, it
> > > finally gets detected. And later on, it is normally detected, before.
> > > Same scenario happened like 3 times wit
Soren,
I've noticed the same thing with the last two builds.
After detaching and then re-attaching the second channel,
both my slave dvdrom and my truant master cdrw show up and appear
to work ok. I just tried your patch (didn't apply cleanly
so I edited the file myself). No apparent change.
Att
On Thu, Sep 18, 2003 at 03:54:36PM +0200, Soren Schmidt wrote:
> It seems Jan Srzednicki wrote:
> > First of all, the drive still does not get detected properly. Funny
> > thing is that after some playing with atacontrol attach/detach, it
> > finally gets detected. And later on, it is normally dete
It seems Jan Srzednicki wrote:
> First of all, the drive still does not get detected properly. Funny
> thing is that after some playing with atacontrol attach/detach, it
> finally gets detected. And later on, it is normally detected, before.
> Same scenario happened like 3 times with ATAng and newe
It seems Dag-Erling Smørgrav wrote:
> Soren Schmidt <[EMAIL PROTECTED]> writes:
> > Well, the ATA driver has just grown more standard compliant :)
> > You *must* hang around for 31secs to wait for slow devices to come ready,
> > according to the ATA specs. Now I've gone to great length before to
>
Soren Schmidt <[EMAIL PROTECTED]> writes:
> Well, the ATA driver has just grown more standard compliant :)
> You *must* hang around for 31secs to wait for slow devices to come ready,
> according to the ATA specs. Now I've gone to great length before to
> get around this by using clever heuristics,
Aloha!
Terry Lambert wrote:
Joachim Strömbergson wrote:
So now the tousand dollar question becomes "What in the boot contains a
timeout around 30 seconds, a timout that lately has been
committed/ctivated in the kernel code?"
SCSI has one of these; are you compiling with ATAPICAM?
Nope. No ATAPICA
Joachim Strömbergson wrote:
> So now the tousand dollar question becomes "What in the boot contains a
> timeout around 30 seconds, a timout that lately has been
> committed/ctivated in the kernel code?"
SCSI has one of these; are you compiling with ATAPICAM?
-- Terry
_
It seems Joachim Strömbergson wrote:
> > Thanks! I guess I'm too impatient these days... Yes, it works after waiting
> > for about 30 seconds. So a correction, it doesn't hang, it's just slow when
> > detecting :).
>
> So now the tousand dollar question becomes "What in the boot contains a
> ti
--On Wednesday, September 17, 2003 00:24:06 +0200 Arjan van Leeuwen
<[EMAIL PROTECTED]> wrote:
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
Aloha!
Arjan van Leeuwen wrote:
> If I start my kernel from september 15, my computer hangs after this
> message:
>
> atapci0: port 0x
On Mon, 8 Sep 2003, Soren Schmidt wrote:
> It seems Nate Lawson wrote:
> > With a fresh checkout of last night's -current, I cannot boot my laptop.
> > ATAFD panics the box by reusing freed memory. I do not have a floppy
> > drive in the laptop and when I do, it's a legacy floppy, not atapi. Here
Aloha!
Arjan van Leeuwen wrote:
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
Try again and see if it is a real, solid hang, or if it just takes a while.
Thanks! I guess I'm too impatient these days... Yes, it works after waiting
for about 30 seconds. So a correction, it doesn't
On Tuesday 16 September 2003 23:33, Joachim Strömbergson wrote:
> Aloha!
>
> Arjan van Leeuwen wrote:
> > If I start my kernel from september 15, my computer hangs after this
> > message:
> >
> > atapci0: port 0xa400-0xa40f at device
> > 7.1 on pci0
> > ata0: at 0x1f0 irq 14 on atapci0
> > ata0: [
Aloha!
Arjan van Leeuwen wrote:
If I start my kernel from september 15, my computer hangs after this message:
atapci0: port 0xa400-0xa40f at device 7.1 on
pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
Did you wait a while? I just completed my system update (getting the
OpenSSH patch in
--On Tuesday, September 16, 2003 23:09:57 +0200 Arjan van Leeuwen
<[EMAIL PROTECTED]> wrote:
If I start my kernel from september 15, my computer hangs after this
message:
atapci0: port 0xa400-0xa40f at device
7.1 on pci0
ata0: at 0x1f0 irq 14 on atapci0
ata0: [MPSAFE]
A kernel from september
It seems Pav Lucistnik wrote:
>
> This patch works for me. Any chance to get it committed?
I'll look at it...
-Søren
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "[EMAIL P
1 - 100 of 183 matches
Mail list logo
