Re: maxphys = 0??

1999-10-10 Thread Daniel C. Sobral
Poul-Henning Kamp wrote: > > Meanwhile the mystery has been solved. I was a miscommunication > between sos and me. He only committed one half of the fix for > this issue. > > He has now committed the rest along with the latest version of > his ata drivers (he claims :-) Things are fine here n

Re: maxphys = 0??

1999-10-09 Thread Poul-Henning Kamp
Meanwhile the mystery has been solved. I was a miscommunication between sos and me. He only committed one half of the fix for this issue. He has now committed the rest along with the latest version of his ata drivers (he claims :-) -- Poul-Henning Kamp FreeBSD coreteam member [EMA

Re: maxphys = 0??

1999-10-09 Thread Daniel C. Sobral
Poul-Henning Kamp wrote: > > In message <[EMAIL PROTECTED]>, "Bria > n F. Feldman" writes: > >On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: > > > >> Well, there are two options, either your sources are not up to date, > >> or your config is very special in some way... I tried again. My sources ar

Re: maxphys = 0??

1999-10-09 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, "Bria n F. Feldman" writes: >On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: > >> Well, there are two options, either your sources are not up to date, >> or your config is very special in some way... > >I am absolutely certain that my sources are up-to-date. I'll atta

Re: maxphys = 0??

1999-10-09 Thread Brian F. Feldman
On Sat, 9 Oct 1999, Poul-Henning Kamp wrote: > Well, there are two options, either your sources are not up to date, > or your config is very special in some way... I am absolutely certain that my sources are up-to-date. I'll attach my kernel config in case you can find something special there.

Re: maxphys = 0??

1999-10-08 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes: >Poul-Henning Kamp wrote: >> >> In message <[EMAIL PROTECTED]>, "Bria >> n F. Feldman" writes: >> >On Tue, 5 Oct 1999, Daniel C. Sobral wrote: >> > >> >> Poul-Henning Kamp wrote: >> >> > >> >> > You need to move your sources further forwa

Re: maxphys = 0??

1999-10-08 Thread Daniel C. Sobral
Poul-Henning Kamp wrote: > > In message <[EMAIL PROTECTED]>, "Bria > n F. Feldman" writes: > >On Tue, 5 Oct 1999, Daniel C. Sobral wrote: > > > >> Poul-Henning Kamp wrote: > >> > > >> > You need to move your sources further forward. > >> > >> Alas, it didn't help. What versions of what files I sh

Re: maxphys = 0??

1999-10-08 Thread Poul-Henning Kamp
In message <[EMAIL PROTECTED]>, "Bria n F. Feldman" writes: >On Tue, 5 Oct 1999, Daniel C. Sobral wrote: > >> Poul-Henning Kamp wrote: >> > >> > You need to move your sources further forward. >> >> Alas, it didn't help. What versions of what files I should have? The >> warnings are still appeari

Re: maxphys = 0??

1999-10-08 Thread Brian F. Feldman
On Tue, 5 Oct 1999, Daniel C. Sobral wrote: > Poul-Henning Kamp wrote: > > > > You need to move your sources further forward. > > Alas, it didn't help. What versions of what files I should have? The > warnings are still appearing, at fsck time. > Alas, similarly I get: changing root device to

Re: maxphys = 0??

1999-10-05 Thread Daniel C. Sobral
Poul-Henning Kamp wrote: > > You need to move your sources further forward. Alas, it didn't help. What versions of what files I should have? The warnings are still appearing, at fsck time. > > In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes: > >A kernel from this weekend's sources is

Re: maxphys = 0??

1999-10-04 Thread Poul-Henning Kamp
You need to move your sources further forward. In message <[EMAIL PROTECTED]>, "Daniel C. Sobral" writes: >A kernel from this weekend's sources is showing this warning message >at boot: > >WARNING: #ad/0x30005 maxphys = 0 ??WARNING: #ad/0x30004 maxphys = 0 >?? > >These are: > >brw-r- 1 root