On Fri, 3 Apr 2009, Alexander Motin wrote:
AM> > AM> This is not actually a fix for original problem, but it may help to
avoid
AM> > AM> system crash. Can you confirm that it helps you, as I haven't tested
it on
AM> > AM> STABLE yet, I am doing it now. If it helps, I will ask r...@.
AM> >
AM> >
Dmitry Morozovsky wrote:
> On Thu, 2 Apr 2009, Alexander Motin wrote:
> AM> Dmitry Morozovsky wrote:
> AM> > On Thu, 2 Apr 2009, Alexander Motin wrote:
> AM> >
> AM> > AM> > ata7: reset tp2 stat0=50 stat1=00 devices=0x1^M
> AM> > AM> > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire^M
On Thu, 2 Apr 2009, Dmitry Morozovsky wrote:
DM> Some other hot reinserts finished successfully.
Well, a couple minutes later after hot-reinsert machine paniced again (but now
it seems related to ZFS):
Fatal trap 12: page fault while in kernel mode
cpuid = 1; apic id = 01
fault virtual address
On Thu, 2 Apr 2009, Alexander Motin wrote:
AM> Dmitry Morozovsky wrote:
AM> > On Thu, 2 Apr 2009, Alexander Motin wrote:
AM> >
AM> > AM> > ata7: reset tp2 stat0=50 stat1=00 devices=0x1^M
AM> > AM> > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire^M
AM> > AM> > ata7-master: pio=PIO4 wd
Dmitry Morozovsky wrote:
On Thu, 2 Apr 2009, Alexander Motin wrote:
AM> > ata7: reset tp2 stat0=50 stat1=00 devices=0x1^M
AM> > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire^M
AM> > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire^M
AM> > ad: ad14 already exists; skippin
On Thu, 2 Apr 2009, Alexander Motin wrote:
AM> > ata7: reset tp2 stat0=50 stat1=00 devices=0x1^M
AM> > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire^M
AM> > ata7-master: pio=PIO4 wdma=WDMA2 udma=UDMA133 cable=40 wire^M
AM> > ad: ad14 already exists; skipping it^M
AM> > ad: ad14 alrea
Dmitry Morozovsky wrote:
> On Thu, 2 Apr 2009, Dmitry Morozovsky wrote:
>
> DM> AM> > AM> > AM> > atapci3: port
> DM> AM> > AM> >
> DM> AM> >
> 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f mem
> DM> AM> > AM> > 0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0
> DM> AM>
On Thu, 2 Apr 2009, Dmitry Morozovsky wrote:
DM> AM> > AM> > AM> > atapci3: port
DM> AM> > AM> >
DM> AM> > 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f
mem
DM> AM> > AM> > 0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0
DM> AM> > AM> > AM> > AM> > atacontrol detach at
On Wed, 1 Apr 2009, Alexander Motin wrote:
AM> > AM> > AM> > atapci3: port
AM> > AM> >
AM> > 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f mem
AM> > AM> > 0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0
AM> > AM> > AM> > AM> > atacontrol detach ata7
AM> > AM> > - insert
Dmitry Morozovsky wrote:
On Wed, 1 Apr 2009, Alexander Motin wrote:
AM> Dmitry Morozovsky wrote:
AM> > Hi there colleagues,
AM> >
AM> > atapci3: port
AM> > 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f mem
AM> > 0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0
AM> >
On Wed, 1 Apr 2009, Dmitry Morozovsky wrote:
DM> AM> > atapci3: port
DM> AM> > 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f
mem
DM> AM> > 0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0
DM> AM> >
DM> AM> >
DM> AM> > atacontrol detach ata7
DM> AM> > - insert ATA disk
On Wed, 1 Apr 2009, Alexander Motin wrote:
AM> Dmitry Morozovsky wrote:
AM> > Hi there colleagues,
AM> >
AM> > atapci3: port
AM> > 0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f mem
AM> > 0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0
AM> >
AM> >
AM> > atacontrol det
Dmitry Morozovsky wrote:
Hi there colleagues,
atapci3: port
0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f mem
0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0
atacontrol detach ata7
- insert ATA disk (ad14)
atacontrol attach ata7
pinics with Fatal trap 12: page f
Hi there colleagues,
atapci3: port
0xbc00-0xbc07,0xb880-0xb883,0xb800-0xb807,0xb480-0xb483,0xb400-0xb40f mem
0xefcb3000-0xefcb3fff irq 23 at device 5.2 on pci0
atacontrol detach ata7
- insert ATA disk (ad14)
atacontrol attach ata7
pinics with Fatal trap 12: page fault while in kernel mode
"Rong-En Fan" <[EMAIL PROTECTED]> wrote:
> The ata controller and ad0 is
> atapci0: port
> 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 7.1 on
> pci0
> atapci0: Reserved 0x10 bytes for rid 0x20 type 4 at 0xffa0
> ata0: on atapci0
> atapci0: Reserved 0x8 bytes for rid 0x10 type 4 a
On 3/16/06, Scott Long <[EMAIL PROTECTED]> wrote:
> Rong-En Fan wrote:
> > Hi,
> >
> > Recently, we upgrade a 4.11 box to 6.1-BETA2 by reinstall+newfs everything.
> > After that, we found that if hw.ata.ata_dma=1 at boot, then as soon as it
> > starts fsck -p, it panics. It happens only if ad0 is
Rong-En Fan wrote:
Hi,
Recently, we upgrade a 4.11 box to 6.1-BETA2 by reinstall+newfs everything.
After that, we found that if hw.ata.ata_dma=1 at boot, then as soon as it
starts fsck -p, it panics. It happens only if ad0 is setted to UDMA66 or above.
My current solution is set hw.ata.ata_dma=
Hi,
Recently, we upgrade a 4.11 box to 6.1-BETA2 by reinstall+newfs everything.
After that, we found that if hw.ata.ata_dma=1 at boot, then as soon as it
starts fsck -p, it panics. It happens only if ad0 is setted to UDMA66 or above.
My current solution is set hw.ata.ata_dma=0 in loader.conf and
At 01:37 AM 14/03/2006, Søren Schmidt wrote:
Mike Tancsa wrote:
At 11:38 PM 13/03/2006, Mike Tancsa wrote:
Hi,
I was trying out a recent RELENG_6 on a VIA
mini ITX board with built in CF reader. If a
CF is present, the box panics at boot (tried
with 2 separate boards and different CFs just
Mike Tancsa wrote:
At 11:38 PM 13/03/2006, Mike Tancsa wrote:
Hi,
I was trying out a recent RELENG_6 on a VIA mini ITX board with built
in CF reader. If a CF is present, the box panics at boot (tried with 2
separate boards and different CFs just in case it was hardware). This
is with a RELEN
At 11:38 PM 13/03/2006, Mike Tancsa wrote:
Hi,
I was trying out a recent RELENG_6 on a VIA mini ITX board with
built in CF reader. If a CF is present, the box panics at boot
(tried with 2 separate boards and different CFs just in case it was
hardware). This is with a RELENG_6 from March 7th
Hi,
I was trying out a recent RELENG_6 on a VIA mini ITX board with built
in CF reader. If a CF is present, the box panics at boot (tried with
2 separate boards and different CFs just in case it was
hardware). This is with a RELENG_6 from March 7th
with the flash in I get a panic at bootup.
Søren Schmidt wrote:
Nate Lawson wrote:
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bu
Nate Lawson wrote:
Søren Schmidt wrote:
Nate Lawson wrote:
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested f
Nate Lawson wrote:
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bug is triggered by timeo
Søren Schmidt wrote:
Nate Lawson wrote:
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bu
On 2005.02.27 11:56:06 -0800, Nate Lawson wrote:
> If you've been having "memory modified after free" panics on -current
> and have a Thinkpad, the attached patch should fix things for you. A
> quick check of RELENG_5 indicates that the bug is probably there also
> but I haven't tested for it t
Nate Lawson wrote:
Søren Schmidt wrote:
Nate Lawson wrote:
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it
Søren Schmidt wrote:
Nate Lawson wrote:
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bug is
Søren Schmidt wrote:
Nate Lawson wrote:
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bug is
Nate Lawson wrote:
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bug is triggered by timeout
On 2005.02.27 11:56:06 -0800, Nate Lawson wrote:
> If you've been having "memory modified after free" panics on -current
> and have a Thinkpad, the attached patch should fix things for you. A
> quick check of RELENG_5 indicates that the bug is probably there also
> but I haven't tested for it t
If you've been having "memory modified after free" panics on -current
and have a Thinkpad, the attached patch should fix things for you. A
quick check of RELENG_5 indicates that the bug is probably there also
but I haven't tested for it there.
The bug is triggered by timeouts in the ata_getpar
33 matches
Mail list logo
