Bug 53481
| Summary: | 5.1R does not recognise xl0 at every startup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Base System | Reporter: | plexus <plexus> | ||||
| Component: | kern | Assignee: | Bruce M Simpson <bms> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | ||||||
| Priority: | Normal | ||||||
| Version: | 5.1-RELEASE | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
State Changed From-To: open->feedback Does FreeBSD 4.8 work on this system? Does 5.1 work if you disable ACPI during the boot process? State Changed From-To: feedback->closed Feedback timeout State Changed From-To: closed->open Re-opened at users request. Responsible Changed From-To: freebsd-bugs->bms I'll take ownership of this, as I have hardware which is affected by the same bug. I think this is a hardware bug so I don't hold out much hope for a solution, but I'll speak to wpaul anyway. State Changed From-To: open->feedback As far as I know this is a hardware bug which I can't seem to work around other than by following the steps documented in xl(4). What do you think, submitter? State Changed From-To: feedback->closed Yep, it's a hardware issue. With workaround. 3com suckiness. On Mon, Dec 15, 2003 at 10:25:42PM +0100, Oliver Fischer wrote: > >Try disabling 'PCI power management' in the ThinkPad BIOS and see if > >that has an effect. The issue doesn't appear to be with the driver; > >sometimes Windows will place the card in the S3 ACPI power state and > >it loses some of its PCI configuration when this happens. > > I disabled 'PCI power management'. Since then the problem didn't appear > anymore. Thanks for getting back to me on this; I've closed the PR. Note Cc: on gnats-submit to make sure the info on the workaround gets picked up. Regards, BMS |
The system can't always initialise xl0 on my IBM T20. Sometimes I have to reboot up to three times. Fix: Reboot the system until xl0 is initialised. How-To-Repeat: Simply boot the laptop.