Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

kernel panic with 3ware 7850

1 view
Skip to first unread message

Clemens Hermann

unread,
Nov 26, 2001, 2:44:23 PM11/26/01
to
Hi,

While Installing a FreeBSD 4.4 release I run into trouble which is likely
caused (imho) by the 3ware controller. The installation starts as usual, I
create the slices etc., select the install type and all the files are
copied. Then, when the message "Remaking Devices" appears The machine hangs
with the following message:
"panic: pmap_enter: pte vanished, va: 0x2806b000"
Then the discs are synced and the machine reboots.

Install-media: official 4.4 Lehmann's CD
Board: Supermicro P3TDE6G
Controller: 3WARE 7850

I can reproduce the error, it happens every time I try. Sometimes the
syncing of the disks fails, sometimes not.

On de-bsd-questions Andreas reported the same problem with a 7810.

thanks in advance for any help.

/ch

To Unsubscribe: send mail to majo...@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message

Mike Smith

unread,
Nov 26, 2001, 6:07:28 PM11/26/01
to
> While Installing a FreeBSD 4.4 release I run into trouble which is likely
> caused (imho) by the 3ware controller. The installation starts as usual, I
> create the slices etc., select the install type and all the files are
> copied. Then, when the message "Remaking Devices" appears The machine hangs
> with the following message:
> "panic: pmap_enter: pte vanished, va: 0x2806b000"
> Then the discs are synced and the machine reboots.

Do you have any evidence to substantiate your claims wrt. the 3ware controller?

I allege the problem is entirely dietary, and until you change your
eating habits, you're going to see the same problems. 8)

And why are you asking on this list?

> On de-bsd-questions Andreas reported the same problem with a 7810.

There are known problems with 78xx controllers related to power supply
issues, but these manifest as I/O errors under heavy load. What
you're seeing looks like memory corruption of some sort.

I would recommend a more methodical approach to resolving your problem
than simply picking a single component and pronouncing it guilty.

0 new messages