I've got a 6.1 server that's panicing and I'd like to debug it. The
problem is that I can't get a kernel dump on to my gmirror device. It
looks like since 6.1 this has been supported (it says so in the release
notes). In my rc.conf I have:
dumpdev="/dev/mirror/gm0s1b"$a
Which is my swap p
I've got a 6.1 server that's panicing and I'd like to debug it. The
problem is that I can't get a kernel dump on to my gmirror device. It
looks like since 6.1 this has been supported (it says so in the release
notes). In my rc.conf I have:
dumpdev="/dev/mirror/gm0s1b"$a
Which is my swap partitio
it seems I can not add pipes with releng6 sources from the last days
ipfw add pipe 1 ip from any to any
ipfw: getsockopt(IP_FW_ADD): Invalid argument
or any similar add pipe command does not work (sure I have options DUMMYNET in
kernel)
world and kernel from march 29 works still fine
anything
with new sources I get an mpt error which is not present with sources from
march 28
mpt0: port 0xdc00-0xdcff mem
0xfd7e-0xfd7f,0xfd7c-0xfd7d irq 16 at device 4.0 on pci1
mpt0: [GIANT-LOCKED]
mpt0: MPI Version=1.2.14.0
...
(xpt0:mpt0:0:-1:-1): reset bus
...
da0 at mpt0 bus 0 tar
At 10:07 AM 4/1/2007, JoaoBR wrote:
it seems I can not add pipes with releng6 sources from the last days
ipfw add pipe 1 ip from any to any
ipfw: getsockopt(IP_FW_ADD): Invalid argument
or any similar add pipe command does not work
(sure I have options DUMMYNET in
kernel)
world and kernel f
Matthew Jacob wrote:
On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote:
Matthew Jacob wrote:
> It's been seen before but the fix isn't know yet.
>
> On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote:
>> I'm suffering from very slow write performance on a Dell PowerEdge
860
>> with the SAS
On Sunday 01 April 2007 12:04, Mike Tancsa wrote:
> At 10:07 AM 4/1/2007, JoaoBR wrote:
> >it seems I can not add pipes with releng6 sources from the last days
> >
> >ipfw add pipe 1 ip from any to any
> >ipfw: getsockopt(IP_FW_ADD): Invalid argument
> >
> >or any similar add pipe command does not
On Sun, 1 Apr 2007, Richard Tector wrote:
A perhaps unrealted issue:
I've noticed a large number of messages being produced by the mpt driver
after boot occuring approximately every 90 seconds.
Apr 1 15:51:43 moses kernel: mpt0: mpt_cam_event: 0x14
Apr 1 15:51:43 moses kernel: mpt0: Unhandl
On 4/1/07, Richard Tector <[EMAIL PROTECTED]> wrote:
Matthew Jacob wrote:
> On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote:
>> Matthew Jacob wrote:
>> > It's been seen before but the fix isn't know yet.
>> >
>> > On 3/27/07, Richard Tector <[EMAIL PROTECTED]> wrote:
>> >> I'm suffering from
pleasep pooint out what the error is, and are you booting verbose?
On 4/1/07, JoaoBR <[EMAIL PROTECTED]> wrote:
with new sources I get an mpt error which is not present with sources from
march 28
mpt0: port 0xdc00-0xdcff mem
0xfd7e-0xfd7f,0xfd7c-0xfd7d irq 16 at device 4.0 on
On Sunday 01 April 2007 14:02, Matthew Jacob wrote:
> pleasep pooint out what the error is, and are you booting verbose?
>
> On 4/1/07, JoaoBR <[EMAIL PROTECTED]> wrote:
> > with new sources I get an mpt error which is not present with sources
> > from march 28
> >
> > mpt0: port 0xdc00-0xdcff mem
TB --- 2007-04-01 16:16:03 - tinderbox 2.3 running on freebsd-stable.sentex.ca
TB --- 2007-04-01 16:16:03 - starting RELENG_6 tinderbox run for i386/pc98
TB --- 2007-04-01 16:16:03 - cleaning the object tree
TB --- 2007-04-01 16:16:21 - checking out the source tree
TB --- 2007-04-01 16:16:21 - cd /
this reset bus didn't and do not happen with some day older sources:
> > (xpt0:mpt0:0:-1:-1): reset bus
Well, don't worry about it. It's always been happening.
no, I do not boot verbose
Thanks. I'll make this message show up under 'bootverbose' only.,
> > ...
> > da0 at mpt0 bus 0 tar
On Sunday 01 April 2007 14:49, Matthew Jacob wrote:
> > this reset bus didn't and do not happen with some day older sources:
> > > > (xpt0:mpt0:0:-1:-1): reset bus
>
> Well, don't worry about it. It's always been happening.
>
> > no, I do not boot verbose
>
> Thanks. I'll make this message show up
On 3/31/07, Maxim Khitrov <[EMAIL PROTECTED]> wrote:
Right now I don't even mount it. I boot the system up, insert the drive,
give it a few seconds, and then remove it. After I've done this once,
attaching the drive a second time doesn't work.
- Max
Ok, I think I figured it out. Here's basic
> > > > (xpt0:mpt0:0:-1:-1): reset bus
periph:sim:channel:target:lun
target == lun == -1 == wildcard, so the initial bus reset applies to a
nexus for all targets and luns on that channel on that sim (mpt0) on
that periph (xpt0)
would you mind to tell why it happens and this "-1" values ?
___
At 11:55 AM 4/1/2007, JoaoBR wrote:
by all respect to Julians work but with ipfw broken and sunday fucked up ...
kind of scaring when seeing "I have no time to check, I do it on tuesday"
or "I need to do the userland ipfw too to add some new features, but, not
today.."
please do it all or don't
Bjoern A. Zeeb wrote:
On Sun, 1 Apr 2007, Richard Tector wrote:
A perhaps unrealted issue:
I've noticed a large number of messages being produced by the mpt
driver after boot occuring approximately every 90 seconds.
Apr 1 15:51:43 moses kernel: mpt0: mpt_cam_event: 0x14
Apr 1 15:51:43 moses
On Sunday 01 April 2007 15:22, Mike Tancsa wrote:
> At 11:55 AM 4/1/2007, JoaoBR wrote:
> >by all respect to Julians work but with ipfw broken and sunday fucked up
> > ...
> >
> >kind of scaring when seeing "I have no time to check, I do it on tuesday"
> >or "I need to do the userland ipfw too to a
I just finished installing my new silent router with 6.2R and took
freebsd-update for a spin, just wanting to try it out as I usually
compile a kernel with ALTQ
Notice the advertised p3 and the p2 I got in the end:
C3# freebsd-update fetch
Looking up update.FreeBSD.org mirrors... 1 mirrors found
Joao Barros wrote:
> I just finished installing my new silent router with 6.2R and took
> freebsd-update for a spin...
>
> C3# uname -a
> FreeBSD C3.bsdtech.org 6.2-RELEASE-p2 FreeBSD 6.2-RELEASE-p2 #0: Tue
> Feb 27 22:41:06 UTC 2007
> [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
>
> C3#
I have opened a:
"KDE Kontrol Center" => "Peripherials" => "Storage Media" => "A
certain action" => "Propertias"
and have almost simultaneously pressed the button "eject" on a DVD-drive
- that has led to crash of system.
How next time to avoid crash of system at ejection of a DVD-disk?
===
22 matches
Mail list logo