It seems Alexander Leidinger wrote:
> On Sun, 23 Feb 2003 17:41:07 +0100 (CET)
> Soeren Schmidt <[EMAIL PROTECTED]> wrote:
>
> >
> > It seems that I managed to break the tagged queueing support somehow,
> > so please disable tags while I look hunt for the problem..
>
> For some of us it is broke
On Sun, 23 Feb 2003 17:41:07 +0100 (CET)
Soeren Schmidt <[EMAIL PROTECTED]> wrote:
>
> It seems that I managed to break the tagged queueing support somehow,
> so please disable tags while I look hunt for the problem..
For some of us it is broken since long ago... as you know. I hope you
find the
[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
It seems that I managed to break the tagged queueing support somehow,
so please disable tags while I look hunt for the problem..
I'll commit a disable tags patch to -current in a few...
-Søren
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the m
At Sat, 22 Feb 2003 08:08:59 +0100,
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, tha
On Sunday, 23. February 2003 14:46, [EMAIL PROTECTED] wrote:
> Can somebody please use "cvs update -D " to do a binary search and
> identify which exact commit caused the problem ?
The kernel of '2/20/2003 19:55 GMT' boots fine, but the kernel of '2/20/2003
20:03 GMT' doesn't. The commits in betw
Can somebody please use "cvs update -D " to do a binary search and
identify which exact commit caused the problem ?
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice
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 don
Hi!
Here on my system it does not help :-(, I've never had atapicam configured.
Christian.
On Sunday, 23. February 2003 11:17, 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 th
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
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):
On Saturday, 22. February 2003 12:31, [EMAIL PROTECTED] wrote:
> In message <[EMAIL PROTECTED]>, Michael Class writes:
> >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
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 mai
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
In message <[EMAIL PROTECTED]>, Michael Class writes:
>> 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.
>Mounting root from ufs:/dev/ad0s4a
>Ro
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,
In message <[EMAIL PROTECTED]>, Michael Class writes:
>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.
Please try "boot -v" and send dmesg.
Also, please try
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/ff
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 date
19 matches
Mail list logo
