x0e, buttons: 3/3
>[ 42.038076] hda: lost interrupt
>[ 72.060069] hda: lost interrupt
> [ 102.070870] hda: lost interrupt
> [ 132.077265] hda: lost interrupt
> [ 162.088454] hda: lost interrupt
> [ 192.146202] hda: lost interrupt
> [ 222.277767] hda: lost
: hda: Vpp = 0.0
[ 11.992912] hda: max request size: 128KiB
[ 12.002171] hda: 63438848 sectors (32480 MB) w/1KiB Cache, CHS=65535/15/63
[ 12.014230] hda:<6>IBM TrackPoint firmware: 0x0e, buttons: 3/3
[ 42.038076] hda: lost interrupt
[ 72.060069] hda: lost interrupt
[
'noapic' solved the problem. Thanks!
On 5/11/07, Bob McGowan <[EMAIL PROTECTED]> wrote:
Dallas Clement wrote:
> Hello All,
>
> I just installed the Debian Etch 4.0 on my system. It will not
> complete bootup however. It keeps hanging on "hda: lost interrup
Bob McGowan wrote:
>
> My laptop Turion 64 requires using 'noapic' to boot and run. You can
> add this to the kernel 'command line' (at the boot prompt) for a one
> time test to see if it helps. If it does, edit your boot loader 'menu'
> to append this string to the entries for your kernel. You
Dallas Clement wrote:
Hello All,
I just installed the Debian Etch 4.0 on my system. It will not
complete bootup however. It keeps hanging on "hda: lost interrupt"
and eventually fails to boot entirely.
I previously had Debian Etch "Testing" installed. It has been worki
Hello All,
I just installed the Debian Etch 4.0 on my system. It will not
complete bootup however. It keeps hanging on "hda: lost interrupt"
and eventually fails to boot entirely.
I previously had Debian Etch "Testing" installed. It has been working
fine for the past mo
I was getting this also. The smartd daemon would trigger it but that would
simply time out. Trying to mount the thing hung the system up--big red switch
time. The Western Digital drive would click click click when this problem was
occuring which was not always but enough to be annoying.
I repla
> Also my system suspends even for a several minutes.
> Does it mean my hdd is going to crash?
try with: smartmontools
[...]
Description: control and monitor storage systems using S.M.A.R.T.
The smartmontools package contains two utility programs (smartctl and smartd)
to control and monitor storag
Michał Chruściel wrote:
on Debian I get really a lot of these messages:
hda: lost interrupt
Also my system suspends even for a several minutes.
Does it mean my hdd is going to crash?
If yes, is it hardware problem, or because of misuse of fsck or mkfs?
Did you Google for this already? On a
Michał Chruściel wrote:
on Debian I get really a lot of these messages:
hda: lost interrupt
Also my system suspends even for a several minutes.
Does it mean my hdd is going to crash?
If yes, is it hardware problem, or because of misuse of fsck or mkfs?
Did you Google for this already? On a
Hello,
on Debian I get really a lot of these messages:
hda: lost interrupt
Also my system suspends even for a several minutes.
Does it mean my hdd is going to crash?
If yes, is it hardware problem, or because of misuse of fsck or mkfs?
Regards,
Michal Ch.
--
To UNSUBSCRIBE, email to [EMAIL
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Thursday 06 January 2005 21:20, Joe wrote:
Is it a "defect" that requires the noapic option?
I think so. I don't believe a mere absence of a feature should stop a
kernel booting, particularly a Knoppix one. I think it must be
On Thursday 06 January 2005 21:20, Joe wrote:
>>Is it a "defect" that requires the noapic option?
>>
>>
> I think so. I don't believe a mere absence of a feature should stop a
> kernel booting, particularly a Knoppix one. I think it must be a
> hardware bug.
>
> In fact a quick Google on 'k7s8x n
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Tuesday 04 January 2005 20:40, Joe wrote:
The motherboard is an ASRock K7S8X. (I don't know what chips are on
it.)
I didn't see the beginning of this. I have one of these and I've yet
to see any Linux boot without noapic. In
On Tuesday 04 January 2005 20:40, Joe wrote:
>>The motherboard is an ASRock K7S8X. (I don't know what chips are on
>>it.)
> I didn't see the beginning of this. I have one of these and I've yet
> to see any Linux boot without noapic. Including Knoppix, and Woody on
> 2.4.18, and the current Sarge
In message <[EMAIL PROTECTED]>, Adam Funk <[EMAIL PROTECTED]>
writes
On Wednesday 29 December 2004 00:10, Roberto Sanchez wrote:
Thanks. I added that to the append="..." in /etc/lilo.conf and it
fixed the problem.
Just out of curiosity, why did this become necessary (for my hardware
at least) bet
On Wednesday 29 December 2004 00:10, Roberto Sanchez wrote:
>> Thanks. I added that to the append="..." in /etc/lilo.conf and it
>> fixed the problem.
>>
>> Just out of curiosity, why did this become necessary (for my hardware
>> at least) between the 2.4.23 and 2.4.26 kernels?
>>
> What motherbo
.26-1-386
kernel-image-2.4.26-1-k7
and they all get stuck on "hda: lost interrupt" while trying to boot. I
thought any 386 kernel ought to be upward-compatible with an Athlon,
and a k7 ought to be ideally suited for it. Any ideas what's wrong?
Try booting with noapic.
Thanks. I a
-image-2.4.25-1-386
> > kernel-image-2.4.26-1-386
> > kernel-image-2.4.26-1-k7
> >
> > and they all get stuck on "hda: lost interrupt" while trying to boot. I
> > thought any 386 kernel ought to be upward-compatible with an Athlon,
> > and a k7 ought to be
-k7
>
> and they all get stuck on "hda: lost interrupt" while trying to boot. I
> thought any 386 kernel ought to be upward-compatible with an Athlon,
> and a k7 ought to be ideally suited for it. Any ideas what's wrong?
Try booting with noapic.
--
Visit Openswan at h
On Friday 14 May 2004 10:41 am, Adam Funk wrote:
> On Friday 14 May 2004 17:10, Roberto Sanchez wrote:
> > What motherboard do you have?
>
> ASRock K7S8X
>
> > Are you loading the module for your
> > IDE chipset?
>
> Here's some info about the kernel that works. AFAIK all the kernels
> I've tried
On Friday 14 May 2004 17:10, Roberto Sanchez wrote:
> What motherboard do you have?
ASRock K7S8X
> Are you loading the module for your
> IDE chipset?
Here's some info about the kernel that works. AFAIK all the kernels
I've tried would use the same modules.conf file, so I can't see why
changi
Adam Funk wrote:
I'm running Debian testing on an Athlon 1100 and currently using the
2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
kernel-image-2.4.25-1-386
kernel-image-2.4.26-1-386
kernel-image-2.4.26-1-k7
and they all get stuck on "hda: lost interrupt&q
I'm running Debian testing on an Athlon 1100 and currently using the
2.4.23-1-386 kernel. I've tried to upgrade to the following packages:
kernel-image-2.4.25-1-386
kernel-image-2.4.26-1-386
kernel-image-2.4.26-1-k7
and they all get stuck on "hda: lost interrupt" whil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Es Diumenge Febrer 8 2004 22:58, en Adam va escriure:
> hda: attached ide-disk driver.
> hda: lost interrupt
Try starting with noapic option
- --
Joan Tur (aka Quini), Eivissa-Spain
Jabber: [EMAIL PROTECTED]
Yahoo & AI
On Monday 09 February 2004 13:00, Andreas Janssen wrote:
>> 3. pray|chant|sacrifice and reboot
>> 4. stop messing with these things on my important workstation (that's
>>what the spare computer is for)
That all worked and everything is fine now! (Except that it
mysteriously switched my main
Hello
Adam (<[EMAIL PROTECTED]>) wrote:
> Once I manage to boot from the CD with the correct kernel, is this the
> correct procedure for fixing my problem?
>
> 1. change the /vmlinuz and /initrd symlinks to point to the i386
>kernel images
> 2. check lilo.conf and run /sbin/lilo
While check
Andreas Janssen wrote:
>> I don't have one of those -- I used the Debian sarge installer CD
>> (about 100 MB) and that option doesn't work with it. But I'll get
>> one!
>
> I only have a set of Woody CDs, but maybe there is the normal rescue
> kernel available on your CD (I don't know which Kern
Andreas Janssen wrote:
>> Any ideas on what I broke and how to fix it once I get through the
>> rescue boot? I think that i686 is a correct kernel for an Athlon
>> 1100, isn't it?
>
> No, you need the k7 Kernel. The i386 and i586 and k6 Kernel packages
> will also work, as well as the bf kernels
Hello
Adam (<[EMAIL PROTECTED]>) wrote:
> Andreas Janssen wrote:
>
>> You can boot from one of the Debian CDs. For example, insert CD1 and
>> type:
>
> Any ideas on what I broke and how to fix it once I get through the
> rescue boot? I think that i686 is a correct kernel for an Athlon
> 1100,
Hello
Adam (<[EMAIL PROTECTED]>) wrote:
> Andreas Janssen wrote:
>
>> You can boot from one of the Debian CDs. For example, insert CD1 and
>> type:
>>
>> rescbf24 root=/dev/hdsomething
>
> I don't have one of those -- I used the Debian sarge installer CD
> (about 100 MB) and that option doesn'
Andreas Janssen wrote:
> You can boot from one of the Debian CDs. For example, insert CD1 and
> type:
Any ideas on what I broke and how to fix it once I get through the rescue
boot? I think that i686 is a correct kernel for an Athlon 1100, isn't it?
Thanks,
Adam
--
To UNSUBSCRIBE, email to [
Andreas Janssen wrote:
> You can boot from one of the Debian CDs. For example, insert CD1 and
> type:
>
> rescbf24 root=/dev/hdsomething
I don't have one of those -- I used the Debian sarge installer CD (about 100
MB) and that option doesn't work with it. But I'll get one!
> Or try to boot wit
kernel (from 2.4.23) to 2.4.20. I then removed kernel-image-2.4.20
> and added kernel-image 2.4.23-i686.
>
> Now my machine won't finish booting. It appears to load the kernel,
> recognizes all the drives, then goes into this:
>
> hda: attached ide-disk driver.
> hda: lost
kernel-image 2.4.23-i686.
Now my machine won't finish booting. It appears to load the kernel,
recognizes all the drives, then goes into this:
hda: attached ide-disk driver.
hda: lost interrupt
hda: lost interrupt
hda: dma_timer_recovery: dma status = 0x64
hda: DMA interrupt recovery
hda:
> >I have a 486DX4/100 (Overdrive) with 32MB of RAM that I run Debian on..
> >
> >Up until yesterday it was running like a dream.. Now it does stuff like
> >"Unknown vector 67 in CPU#0" and after that and something about idling says
> >"hda interrupt lost" over and over and over again.
>
> I had th
At 12:06 PM 16/10/00 -0200, Christoph Simon wrote:
>No, no ideas. But I'm suffering from very similar problems. It's a
>network with 19 new computers, which tend to break down as often as
>once a day. All of them have Asus motherboards, some have Pentium III
>others have AMD K6 3D. Also, there are
At 12:10 AM 17/10/00 +1100, hogan wrote:
>I have a 486DX4/100 (Overdrive) with 32MB of RAM that I run Debian on..
>
>Up until yesterday it was running like a dream.. Now it does stuff like
>"Unknown vector 67 in CPU#0" and after that and something about idling says
>"hda interrupt lost" over and ov
On Mon, 16 Oct 2000, Samuel Hathaway wrote:
> hogan wrote:
>
> > I have a 486DX4/100 (Overdrive) with 32MB of RAM that I run Debian on..
> >
> > Up until yesterday it was running like a dream.. Now it does stuff like
> > "Unknown vector 67 in CPU#0" and after that and something about idling says
hogan wrote:
> I have a 486DX4/100 (Overdrive) with 32MB of RAM that I run Debian on..
>
> Up until yesterday it was running like a dream.. Now it does stuff like
> "Unknown vector 67 in CPU#0" and after that and something about idling says
> "hda interrupt lost" over and over and over again.
My
I had a very similar situation with the 2.2.16 kernel, and it only affected hda
in a system with hda and hdc. (debian was on hdc, win98 on hda). in my case,
it only happened when running debian. over a period of months, i drove my
computer store owner bezerk, we checked the components with a dia
On Mon, Oct 16, 2000 at 12:06:48PM -0200, Christoph Simon wrote:
> No, no ideas. But I'm suffering from very similar problems. It's a
> network with 19 new computers, which tend to break down as often as
> once a day. All of them have Asus motherboards, some have Pentium III
> others have AMD K6 3D
> I have a 486DX4/100 (Overdrive) with 32MB of RAM that I run Debian on..
>
> Up until yesterday it was running like a dream.. Now it does stuff like
> "Unknown vector 67 in CPU#0" and after that and something about idling says
> "hda interrupt lost" over and over and over again.
[...]
>
> Any
I have a 486DX4/100 (Overdrive) with 32MB of RAM that I run Debian on..
Up until yesterday it was running like a dream.. Now it does stuff like
"Unknown vector 67 in CPU#0" and after that and something about idling says
"hda interrupt lost" over and over and over again.
The motherboard is ISA/PCI
On Wed, Sep 01, 1999 at 05:25:32PM -0500, Stephen R. Gore wrote:
> Jim McCloskey wrote:
> >
> > Achim Bohnet <[EMAIL PROTECTED]> wrote about:
> >
> > |> hda: lost interrupt
> > |> hda: read_intr: status=0x50 { DriveReady SeekComplete }
> >
>
Jim McCloskey wrote:
>
> Achim Bohnet <[EMAIL PROTECTED]> wrote about:
>
> |> hda: lost interrupt
> |> hda: read_intr: status=0x50 { DriveReady SeekComplete }
>
---end quoted text---
This looks to me like the message I get when I use a kernel with
DMA enabled with
Achim Bohnet <[EMAIL PROTECTED]> wrote about:
|> hda: lost interrupt
|> hda: read_intr: status=0x50 { DriveReady SeekComplete }
I've had this error-message repeatedly over the years on a laptop that
I first got early in 1995. Then it ran Slackware with a 1.2.0 kernel;
now it r
Hello,
on my laptop with one IBM-DADA-26480, running potato and 2.2.10 kernel I get
hda: lost interrupt
hda: read_intr: status=0x50 { DriveReady SeekComplete }
Every lost intrrupt mean a IO gets suspended for ~ 5 secs.
I've checked the mail archives and suses and redhats (shame
48 matches
Mail list logo
