Andriy Gapon wrote:
on 06/05/2009 14:43 Helmut Schneider said the following:
kbd1 at kbdmux0
[snip]
atkbdc0: at port 0x60,0x64 on isa0
atkbd0: irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
[snip]
ukbd0: on uhub0
kbd0 at ukbd0
It took me three passes to notice
Helmut Schneider wrote:
Marat N.Afanasyev wrote:
Helmut Schneider wrote:
I do have such thing (IBM Blade Center) but I'm looking for something
to avoid the situation above. Something that lets me at least boot
into single user mode.
if you have an ip-kvm you can drop into single-user and
On Wed, May 06, 2009 at 09:18:02PM +0200, Helmut Schneider wrote:
> Marat N.Afanasyev wrote:
> >Helmut Schneider wrote:
> >>I do have such thing (IBM Blade Center) but I'm looking for something to
> >>avoid the situation above. Something that lets me at least boot into
> >>single user mode.
>
Marat N.Afanasyev wrote:
Helmut Schneider wrote:
I do have such thing (IBM Blade Center) but I'm looking for something to
avoid the situation above. Something that lets me at least boot into
single user mode.
if you have an ip-kvm you can drop into single-user and fsck any disk you
have.
Andriy Gapon wrote:
on 06/05/2009 16:21 Helmut Schneider said the following:
(kgdb) bt
#0 doadump () at pcpu.h:196
#1 0xc081d7e7 in boot (howto=260) at
/usr/src/sys/kern/kern_shutdown.c:418 #2 0xc081dab9 in panic
(fmt=Variable "fmt" is not available. ) at
/usr/src/sys/kern/kern_shutdown.c:57
Andriy Gapon wrote:
on 06/05/2009 14:43 Helmut Schneider said the following:
kbd1 at kbdmux0
[snip]
atkbdc0: at port 0x60,0x64 on isa0
atkbd0: irq 1 on atkbdc0
kbd0 at atkbd0
atkbd0: [GIANT-LOCKED]
atkbd0: [ITHREAD]
[snip]
ukbd0: on uhub0
kbd0 at ukbd0
It took me three passes to notice
on 06/05/2009 14:43 Helmut Schneider said the following:
> kbd1 at kbdmux0
[snip]
> atkbdc0: at port 0x60,0x64 on isa0
> atkbd0: irq 1 on atkbdc0
> kbd0 at atkbd0
> atkbd0: [GIANT-LOCKED]
> atkbd0: [ITHREAD]
[snip]
> ukbd0: on uhub0
> kbd0 at ukbd0
It took me three passes to notice the above: "
on 06/05/2009 16:21 Helmut Schneider said the following:
> (kgdb) bt
> #0 doadump () at pcpu.h:196
> #1 0xc081d7e7 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:418
> #2 0xc081dab9 in panic (fmt=Variable "fmt" is not available.
> ) at /usr/src/sys/kern/kern_shutdown.c:574
> #3 0xc0b1
Andriy Gapon wrote:
on 06/05/2009 14:43 Helmut Schneider said the following:
Fatal trap 12: page fault while in kernel mode
cpuid = 0; apic id = 00
fault virtual address = 0x30
fault code = supervisor read, page not present
instruction pointer = 0x20:0xc0ad121f
stack pointer
on 06/05/2009 14:43 Helmut Schneider said the following:
> Fatal trap 12: page fault while in kernel mode
> cpuid = 0; apic id = 00
> fault virtual address = 0x30
> fault code = supervisor read, page not present
> instruction pointer = 0x20:0xc0ad121f
> stack pointer =
Helmut Schneider wrote:
after upgrading a few systems yesterday from 7.1-RELEASE to 7.2-RELEASE
on one machine I got the error above. The problem was that
- I was unable to cope with it but booting from a live CD.
- the message appeared ~ 1000 times and then the kernel paniced.
Here's the de
Greg Byshenk wrote:
On Wed, May 06, 2009 at 11:50:11AM +0200, Helmut Schneider wrote:
Marat N.Afanasyev wrote:
Helmut Schneider wrote:
after upgrading a few systems yesterday from 7.1-RELEASE to
7.2-RELEASE on one machine I got the error above. The problem was that
- I was unable to cope
Helmut Schneider wrote:
Marat N.Afanasyev wrote:
Helmut Schneider wrote:
Hi,
after upgrading a few systems yesterday from 7.1-RELEASE to
7.2-RELEASE on one machine I got the error above. The problem was that
- I was unable to cope with it but booting from a live CD.
- the message appeared
On Wed, May 06, 2009 at 11:50:11AM +0200, Helmut Schneider wrote:
> Marat N.Afanasyev wrote:
> >Helmut Schneider wrote:
> >>after upgrading a few systems yesterday from 7.1-RELEASE to 7.2-RELEASE
> >>on one machine I got the error above. The problem was that
> >>
> >>- I was unable to cope with
Marat N.Afanasyev wrote:
Helmut Schneider wrote:
Hi,
after upgrading a few systems yesterday from 7.1-RELEASE to 7.2-RELEASE
on one machine I got the error above. The problem was that
- I was unable to cope with it but booting from a live CD.
- the message appeared ~ 1000 times and then the
Helmut Schneider wrote:
Hi,
after upgrading a few systems yesterday from 7.1-RELEASE to 7.2-RELEASE
on one machine I got the error above. The problem was that
- I was unable to cope with it but booting from a live CD.
- the message appeared ~ 1000 times and then the kernel paniced.
After fsc
Hi,
after upgrading a few systems yesterday from 7.1-RELEASE to 7.2-RELEASE on
one machine I got the error above. The problem was that
- I was unable to cope with it but booting from a live CD.
- the message appeared ~ 1000 times and then the kernel paniced.
After fsck'ing / with the help of
17 matches
Mail list logo
