On Fri, 5 Sep 2003, Lukas Ertl wrote:
> vga0: at port 0x3c0-0x3df iomem 0xa-0xb on isa0
> Timecounter "TSC" frequency 2387622296 Hz quality 800
> Timecounters tick every 10.000 msec
>
> And then... silence. Any ideas?
My sources indicate that you should try upgrading the system BIOS.
-
On Fri, 5 Sep 2003, Lukas Ertl wrote:
> I'm currently having the problem that newer kernels won't boot anymore on
> a HP Proliant DL380G3. The latest kernel I can boot is from Sun Aug 31
> 15:22:44 CEST 2003.
>
> Every attempt to boot a newer one (regardless whether UP or SMP) hangs at:
>
> vga0:
Hi,
I'm currently having the problem that newer kernels won't boot anymore on
a HP Proliant DL380G3. The latest kernel I can boot is from Sun Aug 31
15:22:44 CEST 2003.
Every attempt to boot a newer one (regardless whether UP or SMP) hangs at:
vga0: at port 0x3c0-0x3df iomem 0xa-0xb on
It seems Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
> Soren, I did a bit of experimenting with my CVS archive and found that
> version
> 1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed
> out errors about unexpected interrupts whilst probing and eventual
Soren, I did a bit of experimenting with my CVS archive and found that version
1.8 of ata-all.c was the last one that worked on my problem box. 1.9 spewed
out errors about unexpected interrupts whilst probing and eventually hung, and
1.10 gave the unable to mount wd0s2a errors we all love.
(trimmed spaghetti CC: list...)
On Fri, 30 Apr 1999, Soren Schmidt wrote:
> Unfortunately they dont tell me much :(
>
> I'll have to rearrange some disks here and try to make some new installs
> see if I can get the problem to appear then..
Is there any info I can dig out for you? Some useful p
It seems Soren Schmidt wrote:
> >
> > As I said before, I can make some tests, but unfortunately my machine
> > doesn't want to mount disks at all with the new ATA code... Please take a
> > look at the message I sent about a week ago.
>
> Unfortunately they dont tell me much :(
>
> I'll have to
It seems Andrzej Bialecki wrote:
> > >Ever going to help with my atapi-fd problems? I found examples of the
> > >corruptions, including lots of NULLs...
> >
> > Well, so long as I cannot get my hands on the problem, its real hard
> > to solve it. I'm trying to get ahold of the same LS120 drive her
On Thu, 29 Apr 1999, Soren Schmidt wrote:
> It seems Brian Feldman wrote:
>
> >Ever going to help with my atapi-fd problems? I found examples of the
> >corruptions, including lots of NULLs...
>
> Well, so long as I cannot get my hands on the problem, its real hard
> to solve it. I'm trying to ge
On Thu, 29 Apr 1999, Soren Schmidt wrote:
> It seems Brian Feldman wrote:
>
> >Ever going to help with my atapi-fd problems? I found examples of the
> >corruptions, including lots of NULLs...
>
> Well, so long as I cannot get my hands on the problem, its real hard
> to solve it. I'm trying to ge
It seems Brian Feldman wrote:
>Ever going to help with my atapi-fd problems? I found examples of the
>corruptions, including lots of NULLs...
Well, so long as I cannot get my hands on the problem, its real hard
to solve it. I'm trying to get ahold of the same LS120 drive here
but so far I havn't
On Wed, 28 Apr 1999, Soren Schmidt wrote:
> > Hi,
> > I have three hosts with -current, all with the new ATA in function.
> > Booting the same kernel produces different results on all of them wrt
> > root file system mounting:
> >
> > - one reports 'changing root device to wd0s3a'
> > - one repor
Soren Schmidt wrote:
> Hmm, could you mail me the output of fdisk & disklabel from those tree
> machines, with indication of how they behave ??
>
> I'm unable to reproduce those errors here, but this might bring the
> details I need to figure it out...
Certainly. First the working machine (report
> Hi,
> I have three hosts with -current, all with the new ATA in function.
> Booting the same kernel produces different results on all of them wrt
> root file system mounting:
>
> - one reports 'changing root device to wd0s3a'
> - one reports 'changing root device to wd0s3a' followed by 'changing
Hi,
In the great new ATA device driver framework (thanks Soren) there seems
to be a problem reported before by Stephen:
Stephen Hocking-Senior Programmer PGS Tensor Perth wrote:
>
> On my machine, a kernel newer than one built on the 22nd will not complete
> booting, panicing about not being a
On my machine, a kernel newer than one built on the 22nd will not complete
booting, panicing about not being able to mount root. Another machine with a
very similar config is fine. The main difference is that the faulty machine
has its FreeBSD partition in an odd spot on the disk. Below is the
16 matches
Mail list logo
