At the Partition Check stage, I start getting "hde: lost interrupt"
messages. /dev/hde is an IBM DTLA-307030, sitting on an HPT370
controller (motherboard is KA7-100). Eventually the partitions appear
in the list, interspersed with these lost interrupt messages, but very
slowly. Then there was
At the Partition Check stage, I start getting hde: lost interrupt
messages. /dev/hde is an IBM DTLA-307030, sitting on an HPT370
controller (motherboard is KA7-100). Eventually the partitions appear
in the list, interspersed with these lost interrupt messages, but very
slowly. Then there was a
This seems to be a return of the problem I was having a while ago
relating to the USB drivers. The Oops happens when I move the mouse
with the usb-uhci driver. The alternate driver (uhci) does not load
properly (message in syslog - uhci: host controller halted. very bad)
System:
K7 800
KA7-100
This seems to be a return of the problem I was having a while ago
relating to the USB drivers. The Oops happens when I move the mouse
with the usb-uhci driver. The alternate driver (uhci) does not load
properly (message in syslog - uhci: host controller halted. very bad)
System:
K7 800
KA7-100
> The other changes in pre12 aren't likely to be all that noticeable, unless
> you happen to be hit by just that detail.. As always, fedback is
> appreciated.
>
> Linus
>
>
>
> pre12:
> - Get non-cpuid Cyrix probing right (it's not a NexGen)
> - Jens Axboe: cdrom tray
System is a KA7-100, sole USB peripheral is a Logitech MouseMan Wheel.
If I use the uhci driver, it doesn't initialise properly (there is a
message along the lines of "something bad happened". If I use the
usb-uhci driver, I frequently get an oops if I move the mouse during
bootup.
If anyone
System is a KA7-100, sole USB peripheral is a Logitech MouseMan Wheel.
If I use the uhci driver, it doesn't initialise properly (there is a
message along the lines of "something bad happened". If I use the
usb-uhci driver, I frequently get an oops if I move the mouse during
bootup.
If anyone
This Oops happened with mutt as the only active user process.
I'd been using uhci for a while with test kernels, as usb-uhci had
been oopsing on first mouse use. However, with test12 I found a
problem with uhci:
Dec 13 12:13:24 bloch kernel: PCI: Found IRQ 5 for device 00:07.2
Dec 13 12:13:24
This Oops happened with mutt as the only active user process.
I'd been using uhci for a while with test kernels, as usb-uhci had
been oopsing on first mouse use. However, with test12 I found a
problem with uhci:
Dec 13 12:13:24 bloch kernel: PCI: Found IRQ 5 for device 00:07.2
Dec 13 12:13:24
The Oops happens during startup immediately after:
ACPI: System description tables loaded
It's definitely using the correct System.map.
This is on RedHat 7.0, Athlon 800, Abit KA7-100 m/b
ksymoops 2.3.4 on i686 2.4.0-test11-ac4. Options used
-V (default)
-k /proc/ksyms (default)
The Oops happens during startup immediately after:
ACPI: System description tables loaded
It's definitely using the correct System.map.
This is on RedHat 7.0, Athlon 800, Abit KA7-100 m/b
ksymoops 2.3.4 on i686 2.4.0-test11-ac4. Options used
-V (default)
-k /proc/ksyms (default)
This has suddenly started happening tonight. Also happens with test9
and test10-pre1 but they lock-up hard, to the extent that Atl-SysRQ+B is
needed, box doesn't respond to pings etc.
The only thing that's changed recently is the addition of a new PS/2
keyboard.
My first Oops report so
This has suddenly started happening tonight. Also happens with test9
and test10-pre1 but they lock-up hard, to the extent that Atl-SysRQ+B is
needed, box doesn't respond to pings etc.
The only thing that's changed recently is the addition of a new PS/2
keyboard.
My first Oops report so
This has happened three times now, when dd'ing a boot image to a floppy.
The screen goes blank, Alt+SysRq don't seem to have any effect.
System:
Athlon 800
KA7-100
RedHat 7.0
The first time there was a data CRC error listed in /var/log/messages,
so I tried with a different floppy, but the
This has happened three times now, when dd'ing a boot image to a floppy.
The screen goes blank, Alt+SysRq don't seem to have any effect.
System:
Athlon 800
KA7-100
RedHat 7.0
The first time there was a data CRC error listed in /var/log/messages,
so I tried with a different floppy, but the
On Sat, 09 Sep 2000, Mark Hindley wrote:
>
>
> No joy with specifying the memory size. I have 64MB. I have tried mem=64M and
> 32/16/8. Still just reboots.
>
> Any other suggestions?
>
> Mark
>
I've been having a similar problem with an i430TX m/b, P5-233MMX with
both stable and
16 matches
Mail list logo
